Femto Network Gateway (FNG)

download report

Transcript Femto Network Gateway (FNG)

Subject: Femto Network Gateway (FNG) Architecture
Date:
Source:
Contact:
15 October 2007
Airvana
Baw Ch’ng, Minsh Den, Woojune Kim, Doug Knisely, Balaji Raghothaman
{baw, mden, wkim, dknisely, braghothaman}@airvana.com
cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2.
Airvana, Inc., grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution
and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards
publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part
such contribution or the resulting Organizational Partner's standards publication. Airvana, Inc., is also willing to grant licenses under such contributor copyrights to third
parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.
This document has been prepared by Airvana, Inc., to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is
not to be construed as a binding proposal on Airvana, Inc. Airvana, Inc., specifically reserves the right to amend or modify the material contained herein and to any
intellectual property of Airvana, Inc.,other than provided in the copyright statement above.
1
Focus of Contribution (1)
• Existing circuit or IP-based
telephony services
• Supplementary Services (e.g.,
SMS)
Cable, DSL, or
other Broadband
Internet Service
• Emergency Services, etc.
Public
Internet
Femtocells
(Home Base Stations)
Operator’s
Core Network
Femto
Network Gateway
(FNG)
• Radio Interface to mobile devices
• Firewall/security from public Internet
• Interface to the broadband Internet
• Security data transport to femtos
• Management capabilities
• Scalability to support large numbers
of femtos
• Security against tampering
• Security for data transport
“The Phone
Network”
• Scalability toward Core Network
• Topology hiding
2
The Internet
• Packet Data
Services
Focus of Contribution (2)
• Packet Data Service architectures also fall into two
broad categories:
– Legacy Packet Data Service architecture
• Legacy IOSs (e.g., A10/A11 from the femtocell to the legacy
PDSN)
– All-IP Packet Data Service architecture
• Most PDS Termination (PDST) functions performed in the
femtocell
• FNG follows a PDIF-like architecture and interfaces to the
Packet Data Core Network
3
Outline
• Femto Network Gateway (FNG) Architecture
• Tunnel Structure
– Tunnels for 1x Voice
• Femto/FNG Packet Data Services Functional Split
• FNG Packet Data Services
– Simple IP, Mobile IP, Proxy-MIP
• Authentication
– Femto device, A12, and user authentications
•
•
•
•
QoS
Accounting
A-Interface Proxy Functions
Detailed Call Flows
4
Conceptual Deployment Model
Untrusted
Network
Very large
number of
femtocells
Trusted
Network
Wireless Operator’s
Core Network
Internet
(not controlled by wireless operator,
assume untrusted, unsecured)
Femto
Cell
Femto
Cell
Femto
Cell
Femto
Cells
(controlled by wireless operator,
assumed trusted, secured)
IMS
1xMSC/xLR
AAA
Security
MIP-HA
Scalability
AGW
NAT Traversal
Databases
Efficiency
Very large
number of
femtocells
Femto
Cell
Femto
Cell
Femto
Cell
Femto
Cells
Access Network
(owned by same operator as wireless
service provider, or broadband ISP
networks that have direct peering with
wireless operator’s network)
5
etc.
Femto Network Gateway Architecture (1)
• What is the Femto Network Gateway (FNG) Architecture?
– PDIF-like architecture that provides highly scalable
•
•
•
•
•
Secure access to core network services from untrusted networks
Mobility support
QoS support
Re-use existing PDIF
Accounting support
standards and protocols
NAT traversal support
– … and addresses femto network specific scalability issues
• Concentrator or Proxy functions to allow large number of femtocells
to inter-operate with legacy macro and core network elements not
originally designed to interface with a large number of other network
elements.
Re-use existing A13, A16-A19,
– Example: A13 Proxy
A21 standards and protocols
» FNG proxies A13 interfaces from femtocells so a macro RNC
needs to deal with only one A13 interface proxy instead of one
million A13 interfaces from one million femtocells
6
Femto Network Gateway Architecture (2)
•
PDIF-like secure access architecture
•
IKEv2 & IPSec provides authentication, security, NAT traversal support
Untrusted Trusted
Network Network
VoIP capable
EV-DO Device
Femto
EV-DO
IPSec tunnels
1xRTT
IP Network
(Assume unsecure, untrusted)
Legacy
1x Device
Home Router / Residential Gateway
NAT/Firewall
7
Femto
Network
Gateway
(FNG)
Operator’s Core Network
Common Aspects of Femto Networks
(Technology Independent)
Circuit Traffic
Femtocell
Public
Internet
Legacy
Circuit
Network
Femto
Network Gateway
Operator’s
Core Network
Secure IPSec
tunnels for
signaling,
voice, and
packet data
Packet Data
Services
Packet Data
Traffic
8
Tunnel Structure (1)
1xVoice-Tunnel
1x-TCH
to
AT
EVRC/RTP for user 1
EVRC
1x-TCH
to
AT
EVRC
EVRC/RTP for user 2
1x-TCH
to
AT
EVRC
EVRC/RTP for user N
Base-Tunnel
SIP, Management
Signaling (A13, A16-A19, A21, etc.)
Femtocell
PPP
to
AT
FNG
Per-user Data-Tunnel (1x-Data or EV-DO)
Mobile IP or Simple IP
PPP
to
AT
Mobile IP or Simple IP
PPP
to
AT
Mobile IP or Simple IP
9
Tunnel Structure (2)
• “Base-Tunnel”
Color Code (to be used in all future call flows):
* RED = Base-Tunnel (per Femto-cell permanent tunnel)
* BLUE = 1xVoice-Tunnel (per Femto-cell permanent tunnel)
* GREEN = Data-Tunnel (per AT, tunnel life time same as corresponding PPP session)
– For signaling
FNG
Mobile IP or Simple IP
Mobile IP or Simple IP
Mobile IP or Simple IP
Per-user Data-Tunnel (1x-Data or EV-DO)
– For user packet data
– Per-user tunnels consistent
with PDIF model
Base-Tunnel
SIP, Management
Signaling (A13, A16-A19, A21, etc.)
EVRC/RTP for user N
EVRC/RTP for user 2
to
AT
10
to
AT
to
AT
to
AT
PPP
PPP
EVRC
1x-TCH
EVRC
1x-TCH
EVRC
1x-TCH
Femtocell
PPP
• “Data-Tunnel”
1xVoice-Tunnel
– For 1x voice transported
over RTP
EVRC/RTP for user 1
• “1xVoice-Tunnel”
to
AT
to
AT
Tunnels for 1x Voice
• “Base-Tunnel”
– Used for SIP signaling
– Tunnel Inner Address (TIA) is SIP UA’s address
• “1xVoice-Tunnel”
– Used for RTP transported 1x voice traffic
– Tunnel Inner Address (TIA) is RTP media termination point’s
address
– Separate streams using different port numbers
• Motivation to use separate tunnels for signaling and
media traffic
– Support differentiated QoS without running into IPSec “antireplay window” issue
11
“Base” and “1xVoice” Tunnel Setup
Femtocell
Home Ruoter
(NAT + DHCP)
FNG
AAA
• PDIF-like IPSec tunnel setup
Re-use existing PDIF
tunnel setup call flow
1: IKE_SA_INIT exchange
2: IKE_AUTH
CFG_REQUEST(INTERNAL_IP4_ADDRESS)
• Separate IKE sessions for
“Base” and “1xVoice” tunnels
– Future optimization: setting
up “1xVoice” tunnel as child
of “Base” tunnel
3: RADIUS
Access-Request or
DIAMETER
EAP-Request
4b: IKE_AUTH
EAP message
4a: RADIUS
Access-Challenge or
DIAMETER
EAP-Answer
5a: IKE_AUTH
EAP message
5b: RADIUS
Access-Request or
DIAMETER
EAP-Request
7: IKE_AUTH
EAP Success
6: RADIUS
Access-Accept or
DIAMETER
EAP-Answer
8: IKE_AUTH
AUTH
TIA
allocation
9: IKE_AUTH
CFG_REPLY(TIA), AUTH
12
IPSec tunnel established
All-IP PDST/FNG-Based Femto Network
Architecture for 1x and DO Packet Services
(Proxy-)
MIP
VoIP capable
EV-DO Device
Femto
EV-DO
IPSec
Tunnels
Internet
IP Core
Network
Femto Network
Gateway
(FNG)
HA
1xRTT
Legacy
1x Device
RTP
SIP
MGW
IP in
IPSec
• Terminate 1x Packet Data Service Option (SO33)
• Provides NULL 1x PCF function
• Provide EV-DO Packet Data Service termination
• Terminate PPP
• ROHC (for DO VoIP)
• Authentication Agent for PDS-AAA
• Accounting Agent
• AN-AAA authentication agent for EV-DO (AN-AAA)
• Exchange IP packets within IPSec with FNG
SIP/IMS
Core
• Proxy (mux/demux) functions for scalability:
• Access Authentication (AN-AAA) – IKE to Radius Proxy
• A13/A16 for EV-DO handoff
• A21 (optional; required only if A21-based handoff is
chosen)
• AAA for accounting (more details to follow…)
• IPSec Terminations
13
Femto Network Gateway Functions (1)
• Security
– Security for Core Network (firewall function)
– Security for User Media (encrypted tunnel function, i.e., IPSec)
• Authentication
– Facilitate Femtocell Device Authentication
– Facilitate EV-DO Terminal Authentication
– Facilitate Packet Data User Authentication
• Mobility
– Packet Data IP Layer (L3) Mobility
• MIP-FA (v4) and Attendant (v6)
• Simple IP (v4 & v6)
• Proxy-MIP (v4 & v6) support
– Packet Data Link Layer (L2) Mobility
• “A-Interface Proxy” functions for A13, A16(-A19), A21
14
Femto Gateway Functions (2)
• Billing and Accounting
– IP level accounting performed by FNG
– Aggregates air link accounting information from femtocells
– Generates accounting records for AAA
• QoS
– IP level traffic profile transfer and enforcement
15
Femtocell and FNG Functional Split
Functionality
Femtocell and FNG Division of Responsibility
PPP and ROHC
PPP terminated by femtocell
ROHC performed by femtocell
IPSec
IPSec tunnels terminated by femtocell and FNG.
Mobility
MIP-FA and PMIP mobility agent functionalities in FNG.
Authentication
Mutual authentication between femtocell and FNG
A12 Terminal Authentication via IKE/EAP relay through FNG
PPP-CHAP/PAP user authentication via IKE/EAP relay through FNG.
Mobile IP user authentication done as part of MIP Registration process through MIPFA in FNG.
Accounting
Air link accounting done by femtocell and relay accounting records to FNG
FNG does IP level accounting and provide AAA with consolidated accounting records
QoS policy enforcement
Airlink QoS handled by femtocell
IP level reverse link QoS handled by femtocell
IP level forward link QoS handled by FNG
IP routing
When reverse tunneled (P)MIP is required, user traffic is always routed through
PDIF.
16
FNG Packet Data – Simple IP
Simple IP / PPP
Simple IP / IPSec
Simple IP
CN
Mobile Station
AT
Internet
FNG
Femto
Femtocell
FNG
CN
Apps
Apps
IP
IP Relay
IP Relay
PPP
PPP
ESP
ESP
RLP
RLP
UDP
UDP
MAC
MAC
IP
IP
PHY
PHY
L2
L2
IP
17
L2
L2
FNG Packet Data – Client Mobile IP
Mobile IP / PPP
Mobile IP / IPSec
Mobile IP
Mobile Station
AT
HA
FNG
(MIP-FA)
Femto
Femtocell
FNG
HA
CN
Apps
Apps
IP
IP Relay
IP Relay
PPP
PPP
ESP
ESP
RLP
RLP
UDP
UDP
MAC
MAC
IP
IP
PHY
PHY
L2
L2
IP Relay
IP
18
IP (tunnel)
IP (tunnel)
L2
L2
L2
L2
FNG Packet Data – Proxy Mobile IP
Simple IP / PPP
Simple IP / IPSec
Proxy-MIP
Mobile Station
AT
HA
FNG
(PMIP)
Femto
Femtocell
FNG
HA
CN
Apps
Apps
IP
IP Relay
IP Relay
PPP
PPP
ESP
ESP
RLP
RLP
UDP
UDP
MAC
MAC
IP
IP
PHY
PHY
L2
L2
IP Relay
IP
19
IP (tunnel)
IP (tunnel)
L2
L2
L2
L2
Authentication (1)
• Have to account for
– Femto  FNG mutual authentication
– A12 Terminal Authentication with AN-AAA (omitted for 1x)
– Packet data user authentication
• Use IKE Multiple-Authentication
– Use one IKE session to perform multiple authentications
• Femto  FNG mutual authentication
• A12 Terminal Authentication with AN-AAA (omitted for 1x)
• Packet data user authentication
– References:
• X50-20070212-016 (WLAN Enhancement) and RFC 4739
• Already approved for PDIF
20
Authentication (2)
EAP / IKEv2
Use Femto Cell’s credential
Femto-FNG
Mutual Authentication
(Use Femto’s Credential)
PPP-CHAP
(Use AT’s credential)
IKEv2/EAP-MD5
Relay AT’s credential
RADIUS or
DIAMETER
AT
Simple IP & Proxy-MIP
Packet Data User
Authentication
(Use AT’s
AT
Credential)
PPP-CHAP/PAP
(Use AT’s credential)
AAA
FNG
Femto
IKEv2/EAP-MD5/GTC
Relay AT’s credential
RADIUS or
DIAMETER
AAA
FNG
Femto
Mobile IP
Packet Data User
Authentication
(Use AT’s
Credential)
AAA
FNG
Femto
A12 Terminal
Authentication
(Use AT’s
Credential)
RADIUS or
DIAMETER
Mobile IP Registration
(Use AT’s credential, MN-NAI, MN-FA, MN-AAA extensions)
RADIUS or
DIAMETER
AT
FNG
Femto
21
AAA
Authentication – High Level Call Flow
Simple IP / Proxy-MIP
AT
Femto
0. Data Call or Session
setup
Home Ruoter
(NAT + DHCP)
FNG
Femto-AAA
Femto-FNG
Authentication
1b. RADIUS or
DIAMETER
1a. IKEv2/EAP-AKA or EAP-TLS
HA
IKE_AUTH
(ANOTHER_AUTH_FOLLOWS)
2. PPP-LCP
AN-AAA
A12 Terminal
Authentication
3a. PPP-CHAP
3b. IKEv2/EAP-MD5
3c. RADIUS
IKE_AUTH
(ANOTHER_AUTH_FOLLOWS)
4. PPP-LCP
5a. PPP-CHAP/PAP
AAA
5b. IKEv2/EAP-MD5 (for CHAP)
IKEv2/EAP-GTC (for PAP)
User
Authentication
(Simple IP or
Proxy-MIP)
5c. RADIUS
SimpleIP/
PMIP
decision
7: Proxy-Mobile IP Registration - RRQ
(CoA=FNG)
8b: Proxy-Mobile IP Registration - RRP
(HoA, DNS addresses, ...)
9. IKEv2/EAP Success
(CFG_REPLY assigns HoA as TIA)
10. PPP-IPCP
Femto gives TIA to AT as link address and gives DNS
server addresses from IKEv2 to AT during PPP-IPCP
11a: User Traffic
Flowing
11b: User Traffic Flowing
22
11c: User Traffic Flowing
Authentication – High Level Call Flow
Mobile IP (MIP-FA Mode)
AT
Femto
0. Data Call or Session
setup
Home Ruoter
(NAT + DHCP)
FNG
1a. IKEv2/EAP-AKA or EAP-TLS
Femto-AAA
HA
Femto-FNG
Authentication
1b. RADIUS or
DIAMETER
IKE_AUTH
(ANOTHER_AUTH_FOLLOWS)
2. PPP-LCP
AN-AAA
A12 Terminal
Authentication
3a. PPP-CHAP
3b. IKEv2/EAP-MD5
3c. RADIUS
IKE_AUTH
(CFG_REPLY assigns temp TIA)
4. PPP-LCP
AAA
User
Authentication
(Mobile IP)
5a. PPP-IPCP
5a. MIP Registraton
MIP-RRP
11b: Mobile IP Registration (Agent Solicitation,
Agent Advertisement, MIP-RRQ)
MIP-RRQ
([HA], HoA, DNS addresses, etc.)
5c. RADIUS
5c. MIP-RRQ/RRP
IKE CREATE_CHILD_SA
(TS=HoA, …)
IKE INFORMATIONAL
Delete(old SA)
11a: User Traffic
Flowing
11b: User Traffic Flowing
23
11c: User Traffic Flowing
All-IP PDST/FNG-Based Femto Network QoS, Policy, and
Accounting Architecture for Packet Services
AAA
IP Usage
Accounting
(Radius)
Internet
Femto Network
Gateway
(FNG)
VoIP capable
EV-DO Device
Femto
EV-DO
IP Core
Network
IPSec
Tunnel(s)
HA
1xRTT
PCRF
Legacy
1x Device
Policy
(Ty)
Airlink
Accounting
(Radius)
24
Packet Data QoS Support
• QoS:
– During authentication, FNG receives QoS Profile from AAA
(common for PDIF)
– FNG shares the QoS Profile with the femtocell (required
whenever the RNC function is in the femtocell)
– EV-DO multi-flow QoS is implemented in the femtocell
• Terminates RSVP-like protocol; passes packet filters to FNG for
enforcement on forward traffic and accounting purposes
• Femtocell implements EV-DO over-the-air QoS as part of its
RNC/air interface functions
25
Packet Data QoS Support
• Air Link QoS
– Enforced in femtocell
– Have dependency on QoS Profile
• Today, user’s QoS Profile obtained from AAA
– FNG needs to transfer QoS Profile to femtocell
• QoS Profile to be transferred during user authentication
• In the future, expects to obtain QoS profile through Ty interface
from PCRF
• Backhaul/IP Level QoS
– Enforced by both femtocell and FNG
• Femtocell enforces QoS on the up link
• FNG enforces QoS on the down link
– Both femtocell and FNG must be aware of and enforce
user’s QoS Profile
26
QoS Support and IPSec Tunnels
•
In theory
– Need one IPSec tunnel per user per QoS class to support differentiated
QoS and to avoid IPSec “anti-replay attack window” issue
•
In practice
– Expect to maintain only two QoS classes on the backhaul
• One for “delay sensitive” traffic (e.g., for EV-DO VoIP)
• One for “best effort” traffic (e.g., everything else)
– Use child tunnels (child SAs) to accommodate QoS-differentiated tunnels
•
QoS Management over Untrusted Backhaul:
– Femtocell establishes IPSec child tunnels as needed for differentiated QoS
– Femtocell performs packet filtering and mapping to IPSec tunnels for
reverse traffic
– FNG performs packet filtering and mapping to IPSec tunnes for forward
traffic
27
Packet Data Accounting Support
• Prepaid, Rescinding of Services, etc., Performed by
Radius Interface between AAA and FNG
– Re-use from PDIF; may need to supplement some features
that have not been specified for PDIF yet
• FNG has AAA interface for basic usage accounting
– Re-use from PDIF
• Air-link accounting comes from AAA client in
femtocell
– Standard Radius interface
– FNG provides proxy mux/demux function for scalability
28
Secure A-Interface Proxy Functions
• Certain A-interfaces are terminated by macro RAN
elements that are not meant to scale to very large
number of peers
– E.g., “hundreds” instead of “millions” of A-interface peers
• These macro RAN elements are deployed in
operator’s secure, private networks
– Should not allow elements coming from the public Internet to
interface with macro RAN elements directly
• Use mux/demux “proxies” to solve scalability and
security issues for femto to inter-operate with macro
RAN elements using (proxied) A-interfaces
29
Secure A13 Proxy Architecture
Untrusted
Network
Femto
PBS
Femto
PBS
Femto
PBS
Femto
PBS
A13
Trusted
Network
Appear to Macro EV-DO RNC
as one EV-DO Subnet
A13
Macro EV-DO RNC
A13
A13
A13
A13
Security
Gateway
Macro EV-DO RNC
A13
Proxy
Internet
FNG
A13
A13
Macro EV-DO RNC
Femto
PBS
•
A16(-A19) treatment is similar
30
Secure A21 Proxy Architecture
Untrusted
Network
Femto
PBS
Femto
PBS
Femto
PBS
Femto
PBS
Trusted
Network
Appear to Macro BSC as one
A21 interface
BSC
A21
A21
A21
A21
A21
Security
Gateway
Function
A21
BSC
A21
Proxy
Internet
FNG
A21
A21
BSC
Femto
PBS
31
FNG Architecture Recap
EV-DO RAN
A13, A16-A19
Proxies
6-A19
RNC
PDSN
MIP-FA/PMIP/
Attendant
(P)MIP
SIP
Home Agent
A21 Proxy
Packet Data Services +
SIP/IMS Core Network
(MMD)
AAA
HSS
Cx
CSRV
ISC
ipVLR/IMS-AS
CSCF
ISC
PSTN MGW
HLR / AuC
Sh
AN
SI
-4 1
SIP
BSC
SGW/MGCF
M
ISUP / PC
MSC
MGW
IMS-AS /
SMS GW
PSTN
“Home Network”
32
“Visited Network”
1
A13, A
A21
Femto Cell
BSC/ SIP UA
RNC
PDST
Security Gateway
FNG
Thank you!
Specific details on proposed femto network architecture,
Stage 2 description, and high-level call flows can be found
in Airvana contributions to TSG-A and TSG-X.
A40-20070723-006_Airvana_Femto Overview Architecture and Stage 2 Aspects R2 0 Final.pdf
X10-20070723-012_Airvana_Femto Overview Architecture and Stage 2 Aspects R2 0 Final.pdf
X30-20070723-043 Airvana_Femto Overview Architecture and Stage 2 Aspects R2 0 Final.pdf
X50-20070723-030 Airvana_Femto Overview Architecture and Stage 2 Aspects R2 0 Final.pdf
33
Backup
34
Detailed Call Flows – Tunnel Setup (1)
• Femto-FNG mutual authentication
• A12 Terminal Authentication (optional, omitted for 1x)
AT
Home Ruoter
(NAT + DHCP)
Femtocell
0. Data Call or
Session setup
FNG
CHAP-ID from EAP header
9. PPP-CHAP.
challenge
10. PPP-CHAP
(NAI, challenge-rsp)
2. IKE_SA_INIT.rsp
(MULTIPLE_AUTH_SUPPORTED)
3b. RADIUS or
DIAMETER
Femto-FNG
Authentication
5. IKE_AUTH.req
(AUTH,N(ANOTHER_AUTH_FOLLOWS))
6. IKE_AUTH.rsp
7. IKE_AUTH.req
8. IKE_AUTH.rsp
(EAP.req(MD5-Challenge))
A12 Terminal
Authentication
AN-AAA
11. IKE_AUTH.req
(EAP.rsp(MD5-Challenge))
12. Access-Request
(NAI, CHAP-rsp,
CHAP-ID, challenge)
NAI in NAME field of MD5-Challenge
15. PPP-CHAP.
success
HA
1. IKE_SA_INIT.req
3a. IKEv2/EAP-AKA
(mutual auth between femtocell and FNG)
4. PPP-LCP
Femto-AAA
14. IKE_AUTH.rsp (EAP-Success)
16. PPP-LCP
35
13. ACCESS.Accept
User
Authentication
& Per-AT
Tunnel Setup
Detailed Call Flow – Tunnel Setup (2)
•
Simple IP user authentication & PMIP (continued from previous slide)
AT
Femto
16. PPP-LCP
FNG
HA
User
Authentication
& Per-AT
Tunnel Setup
17. IKE_AUTH.req
(AUTH,N(ANOTHER_AUTH_FOLLOWS))
18. IKE_AUTH.rsp
19. IKE_AUTH.req
20. IKE_AUTH.rsp
(EAP.req(MD5-Challenge))
21. PPP-CHAP.
challenge
AAA
CHAP-ID from EAP header
SimpleIP/PMIP, AAA-selection based on
locally configured profile keyed by NAI.
22. PPP-CHAP
(NAI, challenge-rsp)
23. IKE_AUTH.req
(EAP.rsp(MD5-Challenge))
24. Access-Request
(NAI, CHAP-rsp,
CHAP-ID, challenge)
NAI in NAME field of MD5-Challenge
25. ACCESS.Accept
(QoS Profile,
[HA])
26. IKE INFORMATIONAL
(Notification(QoSProfile))
27. IKE INFORMATIONAL
29. PPP-CHAP
success
30. PPP-IPCP
(Config-Req)
37. PPP-IPCP
(Config-Ack)
28. IKE_AUTH.rsp
(EAP-Success)
31. IKE_AUTH.req
(AUTH)
36. IKE_AUTH.rsp
(CFG_REPLY(TIA=HoA), DNS addresses…)
32: Proxy-Mobile IP Registration - RRQ
(CoA=FNG)
33. ACCESS.Request
(MN-HA SPI, ...)
34. ACCESS.Accept
(MN-HA key, Auth, …)
35: Proxy-Mobile IP Registration - RRP
(HoA, DNS addresses, ...)
22. Accounting-Start
Femtocell gives new HoA to AT as link address and gives
DNS server addresses from IKEv2 to AT in PPP-IPCP phase
38a: User Traffic
Flowing
38b: User Traffic Flowing
38c: User Traffic Flowing
36
Detailed Call Flow – Tunnel Setup (3)
A12 Terminal
Authentication
• Mobile IP user authentication (continued from slide before last)
AT
Femto
FNG
HA
16: PPP-LCP
(AT rejects CHAP)
17: PPP-IPCP
(no address config)
AAA
18. IKE_AUTH.req
(AUTH)
User
Authentication
& Per-AT
Tunnel Setup
TIA
allocation
19. IKE_AUTH.rsp
(CFG_REPLY(TIA=tmp))
20a: MIP Agent Sol.
20b: MIP Agent Solicitation
21b: MIP Agent Adv.
(MN-FA challenge.,
CoA={FNG, ...})
21a: MIP Agent Advertisement
(MN-FA challenge, CoA={FNG, …})
22a: MIP-RRQ
(MN-NAI, MN-AAA,
MN-FA, MN-HA)
22b: MIP-RRQ
(MN-NAI, MN-AAA, MN-FA, MN-HA)
Assign temporary TIA
23. Access-Request
(NAI, CHAP-rsp,
CHAP-ID, challenge)
24. ACCESS.Accept
(QoS Profile,
[dynamic-HA])
25. IKE INFORMATIONAL
(Notification(QoSProfile))
26. IKE INFORMATIONAL
30: MIP-RRP
([HA], HoA, DNS
addresses...)
27: MIP-RRQ
(MN-NAI, MN-HA)
29: MIP-RRP.
([HA], HoA, DNS IP addresses, ...)
28: MIP-RRP.
(HoA, DNS IP addresses, ...)
31. IKE CREATE_CHILD_SA.req
(TS=HoA, …)
Create new SA
that uses the new
HoA in Traffic
Selector, then
delete old SA
32. IKE CREATE_CHILD_SA.rsp
33. IKE INFORMATIONAL
(Delete(old SA))
34. IKE INFORMATIONAL
35. Accounting-Start
36a: User Traffic
Flowing
36b: User Traffic Flowing
36c: User Traffic Flowing
37
Detailed Call Flow – Tunnel Disconnect (1)
AT
Femtocell
Home Ruoter
(NAT + DHCP)
FNG
HA
AAA
AT Initiated Termination
1. PPP-LCP.
Terminate-Request
2. IKE INFORMATIONAL.req
(Delete)
3. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
4. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
5. MIP-RRQ
(lifetime=0)
For PMIP only
6. MIP-RRP
8. PPP-LCP
Terminate-Ack
7. IKE INFORMATIONAL.rsp
(Delete)
1. RADIUS Disconnect-Req(stop)/
Abort-Session-Request(ASR)
AAA Initiated Termination
4. PPP-LCP.
Terminate-Request
5. PPP-LCP
Terminate-Ack
3. IKE INFORMATIONAL.req
(Delete)
6. IKE INFORMATIONAL.rsp
(Delete)
MIP-HA Initiated Termination (PMIP only)
3. PPP-LCP.
Terminate-Request
4. PPP-LCP
Terminate-Ack
2. IKE INFORMATIONAL.req
(Delete)
5. IKE INFORMATIONAL.rsp
(Delete)
2. RADIUS Disconnect-Rsp(stop)/
Abort-Session-Answer(ASA)
7. MIP-RRQ
(lifetime=0)
For PMIP only
8. MIP-RRP
1. MIP-Revocation
For PMIP only
6. MIP Revocation
Acknowledgement
7. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
8. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
1. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
FNG Initiated Termination
4. PPP-LCP.
Terminate-Request
5. PPP-LCP
Terminate-Ack
3. IKE INFORMATIONAL.req
(Delete)
6. IKE INFORMATIONAL.rsp
(Delete)
2. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
7. MIP-RRQ
(lifetime=0)
For PMIP only
8. MIP-RRP
38
Detailed Call Flow – Tunnel Disconnect (2)
AT
Home Ruoter
(NAT + DHCP)
Femtocell
AAA Initiated Termination
FNG
HA
1. RADIUS Disconnect-Req(stop)/
Abort-Session-Request(ASR)
2. RADIUS Disconnect-Rsp(stop)/
Abort-Session-Answer(ASA)
3. MIP Revocation
6. MIP Agent Adv.
(seq # = 0)
8. PPP-LCP.
Terminate-Request
9. PPP-LCP
Terminate-Ack
5. MIP Agent Advertisement [unicast]
(sequence number = 0)
4. MIP Revocation
Acknowledgement
7. IKE INFORMATIONAL.req
(Delete)
10. IKE INFORMATIONAL.rsp
(Delete)
MIP-HA Initiated Termination (CMIP4 Registration Revocation case)
3. MIP Agent Adv.
(seq # = 0)
6. PPP-LCP.
Terminate-Request
7. PPP-LCP
Terminate-Ack
2. MIP Agent Advertisement [unicast]
(sequence number = 0)
1. MIP Revocation
5. IKE INFORMATIONAL.req
(Delete)
4. MIP Revocation
Acknowledgement
9. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
8. IKE INFORMATIONAL.rsp
(Delete)
10. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
FNG/MIP-FA Initiated Termination (CMIP4 Registration Revocation case)
1. MIP Revocation
4. MIP Agent Adv.
(seq # = 0)
6. PPP-LCP.
Terminate-Request
7. PPP-LCP
Terminate-Ack
3. MIP Agent Advertisement [unicast]
(sequence number = 0)
2. MIP Revocation
Acknowledgement
5. IKE INFORMATIONAL.req
(Delete)
9. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
8. IKE INFORMATIONAL.rsp
(Delete)
10. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
39
AAA
Detailed Call Flow – Tunnel Disconnect (3)
AT
Femtocell
Home Ruoter
(NAT + DHCP)
FNG
HA
AAA
MIP-HA Initiated Termination (CMIP4 [Re-]Registration Failure case)
3. MIP-RRQ
4. MIP-RRP
(Fail)
2. MIP-RRQ
1. MIP-RRQ
6. MIP-RRP
(Fail)
5. MIP-RRP
(Fail)
Timer,
counter
8. PPP-LCP.
Terminate-Request
9. PPP-LCP
Terminate-Ack
FNG starts timer/counter after MIPRRP(Fail). AT may retry MIP-Registration. If
no retry is attempted before timer expiration
or retries exceed certain maximum number,
proceed to disconnect IPSec tunnel.
7. IKE INFORMATIONAL.req
(Delete)
11. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
10. IKE INFORMATIONAL.rsp
(Delete)
12. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
FNG/MIP-FA Initiated Termination (CMIP4 [Re-]Registration Failure case)
3. MIP-RRQ
4. MIP-RRP
(Fail)
8. PPP-LCP.
Terminate-Request
9. PPP-LCP
Terminate-Ack
2. MIP-RRQ
5. MIP-RRP
(Fail)
Timer,
counter
FNG starts timer/counter after MIPRRP(Fail). AT may retry MIP-Registration. If
no retry is attempted before timer expiration
or retries exceed certain maximum number,
proceed to disconnect IPSec tunnel. No MIP4
signaling to MIP-HA (state clean-up depends
on time-out on MIP-HA).
7. IKE INFORMATIONAL.req
(Delete)
11. RADIUS Accounting-Req(stop)/
Session-Termination-Request(STR)
10. IKE INFORMATIONAL.rsp
(Delete)
12. RADIUS Accounting-Rsp(stop)/
Session-Termination-Answer(STA)
40