Transcript No Slide Title

MUSE Summer School
Mobility Management in FMC
Arkadiusz Sitek
June 5th, 2007
Muse confidential
Agenda

Need for mobility management in FMC
 Standard Internet mobility solutions
 SIP
 MIP

MUSE mobility management solutions
 Enhanced SIP-mobility
 MIP-based mobility

Conclusions
Muse confidential
Need for mobility management in FMC
Muse confidential
FMC

Multiple access networks
 WiFi
 3G, 3G/LTE
 WiMAX
 Wired Ethernet, …

Multiprovider environment
 Different parts of network (NAP, RNP, CP, NSP, ASP) possibly
managed by independent entities
 There are integrated operators on the FMC playground as well

Converged AAA mechanisms
 Policy Control and QoS
 Mobility Management
Muse confidential
Need for mobility management

What services require mobility management?
 Real-time services (VoIP, Videotelephony, …)
 Streaming services (podcast, vodcast, IP radio, IPTV, …)
 Non real-time data services (web browsing, e-mail, IM&P, …)

Solutions
 Application layer mobility management
o
SIP
 Network layer mobility management
o
MIP
 No mobility management
o
Applications designed to work with no session continuity
Muse confidential
Flavours of mobility
Movement
Session
Loss of data
Handover
Nomadism
Discrete
Terminated
Not applicable
Not possible
Session
Continuity
Continous
Break / Resume
Limited
possible
Continuous
Mobility
Continous
Continuous
Minimal / not
perceptible
Optional
Handover /
Seamless
Handover
Nomadism: “Ability of the user to change his network access point on moving; when changing the
network access point, the user's service session is completely stopped and then started again, i.e.,
there is no session continuity or handover possible. It is assumed that normal usage pattern is that
users shutdown their service session before moving to another access point.” Definition from
ETSI/TISPAN
Session Continuity: “The ability of a user or terminal to change the network access point while
maintaining the ongoing session. This may include a session break and resume, or a certain degree of
service interruption or loss of data while changing to the new access point.”. Definition from
ETSI/TISPAN.
Continuous Mobility: “The ability of a mobile user/terminal/network to change location while media
streams are active”. Definition from ITU-T.
Muse confidential
Roaming
Roaming
Nomadism
Session Continuity
Continuous Mobility
Handover
Seamless Handover
Roaming: “This is the ability of the users to access services according their user profile while moving
outside of their subscribed home network, i.e. by using an access point of a visited network. This requires
the ability of the user to get access in the visited network, the existence of an interface between home
network and visited network, as well as a roaming agreement between the respective network operators.”.
Definition from ETSI/TISPAN.
 Roaming requires business (in the first place) agreement between Home
and Visited Networks.
 Various modes of mobility can be managed during Roaming
 Roaming is an orthogonal notion to Nomadism, Session Continuity,
Continuous Mobility, …
Muse confidential
Standard Internet mobility methods
SIP & MIP
Muse confidential
Standard SIP mobility
RFC 3261 – re-INVITE
 RFC 3515 – REFER
 Explicit signalling of IP address, ports, codec changes to the
communication peer

Muse confidential
Standard SIP mobility summary
Advantages
Drawbacks
Application layer solution - works
across operators’ boundaries
No continuous mobility
Personal, Terminal, Session, Service
mobility support
Privacy is not guaranteed
IP version agostic
Access network agnostic
Incorporated by 3GPP as a call
control protocol
Provides AAA functionalities

Candidate protocol for mobility management in FMC
 Need for SIP mobility enhancements
Muse confidential
Mobile IP
RFC 3344 & 3024 – MIPv4 & Reverse Tunnelling
 RFC 3775 – MIPv6
 Generic network layer mobility management solution
 Hide IP address changes from the applications and
communications peer


Mobile Node (MN) is always reachable by means of the single
Home Address (HoA)
 MN uses IP address assigned by the foreign (visited) network
to enable IP routing -> Care-of-Address (CoA)
 Home Agent (HA) takes care of the the HoA to CoA binding
Muse confidential
Flavours of MIP

MIP client implemented in the MN
 MN is MIP-aware
MN terminates MIP signalling
o MN terminates IP-in-IP tunnel
o
 MIPv4
 MIPv6
 DS-MIPv4
 DS-MIPv6

MIP client is implemented in the network (Proxy Mobile Agent)
 MN is MIP-unaware
MIP signalling terminated at PMA
o IP-in-IP tunnel terminated at PMA
o
 PMIPv4
 PMIPv6
Muse confidential
MIP summary
Advantages
Drawbacks
Well established protocol
No continuous mobility
Terminal mobility support
Depends on IP version
Mobility transparent to applications
Access network agnostic
Incorporated by 3GPP as a MM
protocol for non-3GPP accesses
Provides AAA functionalities

Candidate protocol for mobility management in FMC (3GPP
standardisation pressure)
Muse confidential
Towards continuous mobility – performance comparison

Testbeds:
 WLAN <-> WLAN
 WLAN <-> GPRS
MM protocol
Min. Disruption time
Max. Disruption time
SIP
1,4 sec.
40 sec.
MIP (v4 and v6)
3,5 sec.
9 sec.

Real-time services (e.g. VoIP) require handover disruption time
to be less that 400ms (ITU-T G.114)
 Neither standard SIP nor MIP do assure such behaviour
Muse confidential
Mobility Management for FMC
SIP-based enhanced mobility
Muse confidential
Enhanced SIP mobility
Session Border Controller (SBC) is the solution’s central
network element
 SBC represents the combination of the P-CSCF and C-BGF
IMS functions:

 P-CSCF
o
B2BUA
 C-BGF
NAT
o RTP proxy
o Conferencing module
o

Key concepts
 SIP controlled IP Soft Handover
 SBCs Daisy Chaining
Muse confidential
SIP controlled IP Soft Handover

Soft handover
 Definition: „The service with the target BS starts before
disconnection of the service with the previous serving BS” (IEEE
Std 802.16e-2005)
 During transition from one BS to another, multihomed terminal is
simultaneously connected to both BSs.

SBC handles the traffic during handover (conferencing module)
 SBC sends duplicated IP traffic downstream via both network
interfaces
 SBC filters and mixes received upstream IP traffic

Application Service (AS) controls mobility
 instructs SBC to activate RTP proxy and conferencing module

Multihomed terminal
Muse confidential
SBCs Daisy Chaining

SBCs Daisy Chain
 When terminal moves from one network served by one SBC to
another network served by different SBC, IP Soft Handover
capable SBCs are Daisy Chained to provide continuous mobility

Application Service (AS) controls mobility
 Sets up Daisy Chain
 IP Soft Handover is kept operational
Muse confidential
Enhanced SIP-based mobility for FMC
BYE
REGISTER
INVITE
200 OK
ACK
AAA
server
AAA
proxy
DHCP
server
Packager
CP1
AAA
proxy
Bob’s home
Access
EN
NAP1
SBC
RNP1
EN
AAA
server
CP2
GGSN
3GPP
NAP2
SBC
RNP2
NSP2
re-INVITE
BYE
REGISTER
200 OK
ACK
AAA
server
AAA
proxy
Bob’s office
AAA
server
CP3
Access
EN
NAP3
S-CSCF
EN
DHCP
server
AAA
proxy
AS
Peering
point
between NSP
SBC
RNP3
Muse confidential
NSP3
EN
AAA
ASP
SGSN
Peering
point
between NSP
(single ASP in overlay to NSP)
re-INVITE
REGISTER
BYE
200 OK
ACK
NSP1 (Home NSP)
Enhanced SIP-based mobility summary

Provides mobility to SIP-controlled (IMS) services
 Based on standard SIP protocol
 Novel access network architecture

Mobility enabler for fixed networks
 Interworking with 3GPP possible, but
 SIP mobility is not targeted by 3GPP

Advantages:
 Privacy Protection
 Inter domain continuous mobility (both session and terminal)

Disadvantages:
 Network resource utilization is not optimal (more than one SBC
involved in the session)
Muse confidential
Fixed networks interworking with 3GPP
MIP-based mobility
Muse confidential
3GPP FMC view

I-WLAN
 Introduced in 3GPP Release 6
 3GPP subscriber in fixed access network
 No session continuity -> nomadic access
 WLAN access authentication and authorization through the mobile
core network (AAA server, HSS)

I-WLAN Direct IP Access
 Access to the IP network (i.e. Internet) directly via WLAN access
network

I-WLAN 3GPP IP Access
 Utilizes IPSec to establish secure tunnel between MN and 3GPP
core network through untrusted access network
 Access to the IP network (i.e. Internet) via 3GPP core network
 Access to 3GPP PS-based services
Muse confidential
 QoS assurance
I-WLAN 3GPP Direct IP Access
Legend
User IP traffic
Packager
AAA
server
AAA
proxy
DHCP
server
CP1
AAA
server
EN
Access
EN
AAA
proxy
NSP1
Bob’s home
NAP1
AN
RNP1
DHCP
server
AS
GRX
nodeB
SGSN
UTRAN/GERAN
E-UTRAN
WLAN
BS
WAG
AAA
server/
proxy
GGSN
[PDG]
3GPP CORE (release 6)
WLAN Access
Muse confidential
NSP2
GRX NSP1
ASP
eNodeB
HLR/
HSS
(single ASP in overlay to NSP)
Peering
point
between
NSP
I/S-CSCF
RNC
Packet Data Gateway:
I-WLAN 3GPP Direct IP Access
• IPsec tunnel endpoint
• QoS handling
Legend
• policy enforcement point
IPSec tunnel
• IP address management
Packager
• charging
User IP traffic
AAA
server
AAA
proxy
DHCP
server
CP1
I-WLAN PDG
EN
WAG
Access
EN
AAA
proxy
AAA
server
NSP1
Bob’s home
NAP1
AN
RNP1
DHCP
server
GRX
Wireless Access Gateway:
nodeB
• QoS handling
HLR/
HSS
eNodeB
WAG
AS
GGSN
[I-WLAN PDG]
NSP2
E-UTRAN
WLAN
BS
WLAN Access
I/S-CSCF
AAA
server/
proxy
3GPP CORE (release 6)
Muse confidential
GRX NSP1
ASP
UTRAN/GERAN
• charging
SGSN
Peering
point
between NSP
(single ASP in overlay to NSP)
RNC
• routing to PDG enforcement
MUSE interworking with 3GPP: session continuity

3GPP employs SIP solely as a call control protocol
 MIP introduced in 3GPP System Architecture Evolution
 3GPP Release 8
 All IP 4G network
fully IP network
o simplified network architecture
o distributed control
o
 Integration of the non-3GPP access networks
 MIP as a session continuity enabler for non-3GPP accesses
3GPP access to non-3GPP access
o non-3GPP access to non-3GPP access
o
Muse confidential
Fixed networks interworking with 3GPP:
session continuity

SAE addresses the case where 3GPP subscriber roams in
fixed network
 3GPP subscriber in a fixed access network

Case when fixed network subscriber roams in 3GPP access is
not covered
 MUSE addresses the latter one
 Fixed network subscriber in 3GPP access
Muse confidential
Packet Data Network Gateway:
Fixed network – 3GPP rel.8 interworking
• Mobility Anchor between 3GPP and non-3GPP accesses
MIP-based session continuity – functional view
• Mobility Anchor between non-3GPP accesses
Could
beHA
provided by
• MIP
either by fixed
• Policy Enforcement
operator or 3rd party
• Per-user packet filtering (e.g. DPI)
S2a:
PMIPv6
or CMIPv4 FA
Co@is
3GPP
operator
that
•S2b:
Lawful
Intercept
PMIPv6
contracted
by HPLFN
S8b becomes S5 and can be both GTP
and PMIPv6
Wx*
Non-3GPP
AAA server
HSS
Rx+
PCRF-h
•S2c:
Charging
DS-MIPv6 or CMIPv4 CCo@
S7
S6a
HPLFN
SGi
PDN
GW-h
S8b: PMIPv6
Serving Gateway:
S9
Wd*
• Mobility Anchor for inter-3GPP mobility
Rx+
VPLMN
• Lawful Intercept
S7
PCRF-v
GERAN
MS
S7
S4
SGSN
UTRAN
SGi
GW-v
S2c
S2b
S5
S2a
S8b
S3
S11
S1-MME
IP service networks
(IMS, PSS etc.)
PDN
• Packet
routing and forwarding
3GPP
AAA
proxy
S6d
Serving
GW-v
MME
MS
For non-roaming case VPLMN
becomes HPLMN and S2a, S2b, S2c
are terminated in PDN GW-v (which
becomes PDN GW-h).
S1-U
S2b
EUTRAN
S1-U: GTP-U
Wm*
ePDG-v
S2c
S1-MME: GTP-C+GTP’
Wa*
S2a
Wn*
ePDG-v
S3: GTP
S4: GTP
Trusted
Trusted/Untrusted
Non-3GPP IP Access
Trusted
Non-3GPP IP Access
Untrusted
Non-3GPP IP Access
Ta*
MS
Muse confidential
Can be avoided
since
S5: GTP
MUSE enforces
strong
S8a: GTP
and secure
authentication
GTP = GTP-U+GTP-C+GTP’
and access control
Mobile subscriber in fixed access
Relocation to 3GPP EUTRAN rel. 8: PMIPv6 mobility
Legend
PMIPv6 tunnel
Packager
GTP-U tunnel
AAA
server
User IP traffic
AAA
proxy
DHCP
server
CP1
EN
[PMA]
AAA
proxy
Bob’s home
Access
EN
AAA
server
NSP1
RNP1
NAP1
AN
DHCP
server
GRX
nodeB
SGSN
HSS
MME
UTRAN/GERAN
AS
E-UTRAN
WLAN
BS
NSP2
AAA
server/
proxy
I/S-CSCF
3GPP SAE CORE (release 8)
WLAN Access
Muse confidential
GRX NSP1
ASP
Serving GW
[PMA]
eNodeB
PDN GW
[MIP HA]
(single ASP in overlay to NSP)
Peering
point
between NSP
RNC
Fixed subscriber in 3GPP access
Relocation to fixed access: PMIPv6 mobility
Legend
PMIPv6 tunnel
Packager
GTP-U tunnel
AAA
server
User IP traffic
AAA
proxy
DHCP
server
CP1
PDN GW
[MIP HA,
I-WLAN PDG]
EN
[PMA]
AAA
proxy
Bob’s home
Access
EN
HSS
NSP1
RNP1
NAP1
AN
AAA
server
DHCP
server AS
GRX
nodeB
SGSN
HSS
MME
UTRAN/GERAN
E-UTRAN
WLAN
BS
AAA
server/
proxy
NSP2
PDN GW
[MIP HA]
3GPP SAE CORE (release 8)
WLAN Access
Muse confidential
GRX NSP1
ASP
Serving GW
[PMA]
eNodeB
(single ASP in overlay to NSP)
Peering
point
between
NSP
I/S-CSCF
RNC
MIP-based mobility summary

3GPP Release 6 (I-WLAN) provides nomadic access only
 3GPP Release 8 (SAE) aims session continuity for non-3GPP
access networks
 PMIPv6 pushed by 3GPP
 Network based mobility
 Support for non-MIP enabled terminals
 Architectural similarities to GTP

SAE architecture is still a „moving target”
Muse confidential
Mobility management for FMC summary

Mobility management is the key enabler for FMC
 Two approaches:
 SIP-based for IMS services
Novel access network architecture (standard SIP protocol)
o Mobility enabler for fixed networks
o Facilitates integration with IMS
o
 MIP-based for all (including IMS) services
Supported by 3GPP standardization
o Facilitates mobility support for legacy terminals (PMIP)
o

Generic mechanisms for session continuity will increase both
terminal and network complexity and entail large investments
 It is still to be justified
Muse confidential
Backup slides
Muse confidential
3GPP rel.6/8 entities in MUSE architecture
AAA
server
DHCP
server
AAA
proxy
Packager
CP1
MS
Service EN
Access
EN
Private residence
AN
Public WiFi hotspot
AAA
proxy
PDN GW
[MIP HA,
I-WLAN PDG]
RNP1
NAP1
EN
Mobility
Controller
AAA
server
DHCP
server
HSS
NSP1
RNC
nodeB
SGSN
Service EN
HSS
UTRAN/GERAN
E-UTRAN
WLAN
BS
AAA
server/
proxy
NSP2
AS
3GPP SAE CORE (release 8)
GRX NSP1
WLAN Access
RNC
Service EN
SGSN
nodeB
HSS
UTRAN/GERAN
WLAN
BS
Legend
Authenticator
(+ I-WLAN WAG)
AAA Client
WLAN Access
DHCP Relay
MIPv4 FA
AAA
server/
proxy
WAG
GGSN
[I-WLAN PDG,
PMA, MIP HA]
3GPP CORE (release 6)
PMA (PMIPv6)
Muse confidential
CMIP(v4 or v6) client
SIP Client
SIP B2BUA
I/S-CSCF
Peering
point
between NSP
NSP3
GRX NSP2
C-BGF + RTP proxy
RCEF
ASP
MS
Serving
GW
GRX
(single ASP in overlay to NSP)
MME
eNodeB
PDN GW
[ePDG,
MIP HA]
Peering
point
between NSP
WiMAX entities in MUSE architecture
AAA
proxy
AAA
server
DHCP
server
Packager
CP1
MS
Private residence
Public WiFi hotspot
NPM
AN
AAA
proxy
Service EN
Access
EN
NAP1
PDN GW
[MIP HA,
I-WLAN PDG]
RNP1
AAA
server
DHCP
server
EN
Mobility
Controller
NSP1
MIP
HA
I/S-CSCF
MS
Legend
Authenticator
(+ I-WLAN WAG)
AAA Client
WiMAX
BS
DHCP Relay
MIPv4 FA
WiMAX ASN
NAP2
DHCP
server
RNP2
EN
WiMAX CSN
PMA (PMIPv4)
CMIP(v4 or v6) client
Muse confidential
AAA
server
NSP2
SIP Client
C-BGF + RTP proxy
SIP B2BUA
RCEF
ASP
Service EN
ASN-GW
AS
(single ASP in overlay to NSP)
Peering
point
between NSP
MIPv4 CCoA & Reverse Tunnelling

MN is addressed using both CoA and HoA
 MN performs both MIP signalling and user data IP-in-IP
tunnelling
Muse confidential
MIPv4 FA CoA & Reverse Tunnelling
MN does not know its CoA (it’s managed by Foreign Agent)
 MN performs MIP signalling only
 FA takes care of user data IP-in-IP tunnelling

Muse confidential
MIPv6

No FA
 Route Optimization
 MN and CN can communicate directly
Muse confidential
Dual Stack MIP

DSMIPv4
 draft-ietf-mip4-dsmipv4-02.txt
 Mobility management based on MIPv4
 IPv4 HoA, additionally IPv6 HoA
 IPv4 CoA (IPv6 CoA not supported)
 Applicable for IPv4 and dual stack access networks

DSMIPv6
 draft-ietf-mip6-nemo-v4traversal-04.txt
 Mobility management based on MIPv6
 IPv6 HoA, additionally IPv4 HoA
 IPv4 OR IPv6 CoA
 Applicable for IPv4, IPv6 and dual stack access networks
Muse confidential
Proxy MIP






Host is not aware of mobility
Host does not participate in MIP signalling
Network element performs registration functions on the host’s
behalf
Host always obtains its HoA after authentication in PMIP
Domain
Host operates as it is always in its home network
PMIPv4
 MIPv4 mobility management
 Supports IPv4 and dual stack access networks

PMIPv6
 MIPv6 mobility management
 Supports IPv4, IPv6 and dual stack access networks
Muse confidential
PMIPv4

draft-leung-mip4-proxy-mode-02.txt
 MS (Mobility Station)
 MPA (Mobility Proxy Agent)
 Performs MIP signalling on the MS’s behalf
Muse confidential
PMIPv6

draft-ietf-netlmm-proxymip6-01.txt
 Proxy Mobile IPv6 Domain (PMIPv6-Domain)
 access network where mobility is served using PMIPv6

Local Mobility Anchor (LMA)
 HA in the PMIPv6 domain

Mobile Access Gateway (MAG)
 Emulates MN’s Home Network

Proxy Mobile Agent (PMA)
 Performs MIP signalling on the MN’s behalf
 Located in Mobile Access Gateway (MAG)
Muse confidential
Fixed subscriber in 3GPP EUTRAN rel. 8
GTP-U
S8b
PMIPv6
PMA
PDN
GW
HA
pGW_IP2@
Serving
GW
Ho@
eNodeB
sGW_IP2@
eNB_IP2@
S1-U
sGW_IP1@
Radio
bearer
pGW_IP1@
MS
eNB_IP1@
MS_IP@
= Ho@
Relocation to fixed access: PMIPv6 mobility
Topological anchor
for MS_IP@ (Ho@)
SGi
IP
IP service networks
(IMS, PSS etc.)
CP_IP@
This is also applicable for 3GPP
GERAN or UTRAN (but still with
release 8 core). There will be a
SGSN (instead of an eNodeB)
between MS and Serving GW in
that case (ref.point S4 – GTP).
CN
• Home agent in PDN GW will only
receive PMIPv6 signalling.
• When MS uses 3GPP access (GEUT-/EUTRAN) GTP will be terminated
in serving GW. PMIPv6 is instead used
between serving GW and PDN GW
(S8b instead of S8a).
IPv6 addresses since IPv6
is used in 3GPP core
HPLFN
MS
Access
link
Access
node
L2
Ethernet
Edge
node
PMA
EN_IP2@
MS_IP@
= Ho@
VPLMN
EN_IP1@
Default gateway
for MS
• MME in turn gets this information
during authentication where the HSS of
the MS signals that the PDN GW
expects PMIPv6.
S8b
PMIPv6
• Since PDN GW is not in 3GPP
network, Serving GW needs to interact
with PCRF if policies should be
obtained.
IPv6 or IPv4 addresses
depending on version
used in access
UDP/IP tunneling
if NA(P)T on path
(IPv4 case only)
Muse confidential
• Serving GW is informed by MME
when it receives the Create Default
Bearer Request message that S8b
should be used.
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
Mobile subscriber in fixed access
GTP-U
S5
PDN
GW
PMIPv6 (or GTP)
PMA
HA
pGW_IP2@
Serving
GW
Topological anchor
for MS_IP@ (Ho@)
Ho@
eNodeB
sGW_IP2@
eNB_IP2@
S1-U
sGW_IP1@
Radio
bearer
pGW_IP1@
MS
eNB_IP1@
MS_IP@
= Ho@
Relocation to 3GPP EUTRAN rel. 8: PMIPv6 mobility
SGi
IP
IP service networks
(IMS, PSS etc.)
CP_IP@
This is also applicable for 3GPP
GERAN or UTRAN (but still with
release 8 core). There will be a
SGSN (instead of an eNodeB)
between MS and Serving GW in
that case (ref.point S4 – GTP).
CN
• Home agent in PDN GW will only
receive PMIPv6 signalling.
• When MS uses 3GPP access (GEUT-/EUTRAN) GTP will be terminated
in serving GW. PMIPv6 is instead used
between serving GW and PDN GW
(S8b instead of S8a).
IPv6 addresses since IPv6
is used in 3GPP core
Default gateway
for MS
MS
Access
link
Access
node
L2
Ethernet
Edge
node
PMA
EN_IP2@
MS_IP@
= Ho@
VPLMN
EN_IP1@
HPLFN
• MME in turn gets this information
during authentication where the HSS of
the MS signals that the PDN GW
expects PMIPv6.
S8b
PMIPv6
• Since PDN GW is not in 3GPP
network, Serving GW needs to interact
with PCRF if policies should be
obtained.
IPv6 or IPv4 addresses
depending on version
used in access
UDP/IP tunneling
if NA(P)T on path
(IPv4 case only)
Muse confidential
• Serving GW is informed by MME
when it receives the Create Default
Bearer Request message that S8b
should be used.
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
GTP-U
S8b
PDN
GW
PMIPv6
PMA
HA
pGW_IP2@
Serving
GW
pGW_IP1@
eNodeB
sGW_IP2@
eNB_IP2@
S1-U
sGW_IP1@
Radio
bearer
Topological anchor
for MS_IP@ (Ho@)
Ho@
MIPv4C
MS_IP@
MS
eNB_IP1@
MS_IP@
= Ho@
Relocation to fixed access: MIPv4 with FA Co@ mobility
SGi
IP
IP service networks
(IMS, PSS etc.)
CP_IP@
Fixed subscriber in 3GPP EUTRAN rel. 8
This is also applicable for 3GPP
GERAN or UTRAN (but still with
release 8 core). There will be a
SGSN (instead of an eNodeB)
between MS and Serving GW in
that case (ref.point S4 – GTP).
CN
• Home agent in PDN GW will receive
PMIPv6 signalling when MS uses
3GPP access (EUTRAN) and MIPv4
signalling when MS uses non-3GPP
access.
IPv6 addresses since IPv6
is used in 3GPP core
HPLFN
MIPv4C
MS_IP@
MS
Access
link
Access
node
L2
Ethernet
Edge
node
FA
• Serving GW is informed by MME
when it receives the Create Default
Bearer Request message that S8b
should be used.
EN_IP2@
MS_IP@
= Ho@
VPLMN
EN_IP1@
Default gateway
for MS
• MME in turn gets this information
during authentication where the HSS of
the MS signals that the PDN GW
expects PMIPv6.
MIPv4
UDP/IP tunneling
if NA(P)T on path
and RFC3519 is
supported
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
• When MS uses 3GPP access (GEUT-/EUTRAN) GTP will be terminated
in serving GW. PMIPv6 is instead used
between serving GW and PDN GW
(S8b instead of S8a).
Muse confidential
• Since PDN GW is not in 3GPP
network, Serving GW need to interact
with PCRF if policies should be
obtained.
• MIPv4C in MS is configured to
interpret the IP address assigned to
3GPP LTE NIC as the MIPv4 Ho@.
However, the MS will not initiate MIPv4
control signalling on that NIC.
GTP-U
PMA
S8b
PDN
GW
PMIPv6
HA
pGW_IP2@
Serving
GW
pGW_IP1@
eNodeB
sGW_IP2@
eNB_IP2@
S1-U
sGW_IP1@
Radio
bearer
Topological anchor
for MS_IP@ (Ho@)
Ho@
MIPv4C
MS_IP@
MS
eNB_IP1@
MS_IP@
= Ho@
Relocation to fixed access: MIPv4 with CCo@ mobility
SGi
IP
IP service networks
(IMS, PSS etc.)
CP_IP@
Fixed subscriber in 3GPP EUTRAN rel. 8
This is also applicable for 3GPP
GERAN or UTRAN (but still with
release 8 core). There will be a
SGSN (instead of an eNodeB)
between MS and Serving GW in
that case (ref.point S4 – GTP).
CN
• Home agent in PDN GW will receive
PMIPv6 signalling when MS uses
3GPP access (EUTRAN) and MIPv4
signalling when MS uses non-3GPP
access.
IPv6 addresses since IPv6
is used in 3GPP core
MS_IP@
= Ho@
VPLMN
HPLFN
MIPv4C
MS_L_IP@
=CCo@
MS
Access
link
EN_IP1@
Default gateway
for MS
Access
node
• Serving GW is informed that S8b
should be used by MME when it
receives the Create Default Bearer
Request message.
Edge
node
L2
Ethernet
IP
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
UDP/IP tunneling
if NA(P)T on path
and RFC3519 is
supported
• When MS uses 3GPP access (GEUT-/EUTRAN) GTP will be terminated
in serving GW. PMIPv6 is instead used
between serving GW and PDN GW
(S8b instead of S8a).
Muse confidential
• MME in turn gets this information
during authentication where the HSS of
the MS signals that the PDN GW
expects PMIPv6.
• Since PDN GW is not in 3GPP
network, Serving GW need to interact
with PCRF if policies should be
obtained.
• MIPv4C in MS is configured to
interpret the IP address assigned to
3GPP LTE NIC as the MIPv4 Ho@.
However, the MS will not initiate MIPv4
control signalling on that NIC.
GTP-U
PMA
S8b
PDN
GW
PMIPv6
HA
pGW_IP2@
Serving
GW
pGW_IP1@
eNodeB
sGW_IP2@
eNB_IP2@
S1-U
sGW_IP1@
Radio
bearer
Topological anchor
for MS_IP@ (Ho@)
Ho@
DSMIPv6C
MS_IP@
MS
eNB_IP1@
MS_IP@
= Ho@
Relocation to fixed access: DS-MIPv6 mobility
SGi
IP
IP service networks
(IMS, PSS etc.)
CP_IP@
Fixed subscriber in 3GPP EUTRAN rel. 8
This is also applicable for 3GPP
GERAN or UTRAN (but still with
release 8 core). There will be a
SGSN (instead of an eNodeB)
between MS and Serving GW in
that case (ref.point S4 – GTP).
CN
• Home agent in PDN GW will receive
PMIPv6 signalling when MS uses
3GPP access (EUTRAN) and DSMIPv6 signalling when MS uses non3GPP access.
IPv6 addresses since IPv6
is used in 3GPP core
MS_IP@
= Ho@
VPLMN
HPLFN
DSMIPv6C
MS_L_IP@
=CCo@
MS
Access
link
EN_IP1@
Default gateway
for MS
Access
node
• Serving GW is informed by MME
when it receives the Create Default
Bearer Request message that S8b
should be used.
Edge
node
L2
Ethernet
IP
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
UDP/IP tunneling
if NA(P)T on path
• When MS uses 3GPP access (GEUT-/EUTRAN) GTP will be terminated
in serving GW. PMIPv6 is instead used
between serving GW and PDN GW
(S8b instead of S8a).
Muse confidential
• MME in turn gets this information
during authentication where the HSS of
the MS signals that the PDN GW
expects PMIPv6.
• Since PDN GW is not in 3GPP
network, Serving GW need to interact
with PCRF if policies should be
obtained.
• DS-MIPv6C in MS is configured to
interpret the IP address assigned to
3GPP LTE NIC as the MIPv4/v6 Ho@.
However, the MS will not initiate DSMIPv6 control signalling on that NIC.
Tunneling frenzy
DS-MIPv6, untrusted non-3GPP access & visited anchor in 3GPP
HPLFN
Topological
anchor for
MS_IP2@
MS_IP1@
Access
node
MS_IP2@ (IPSec tunnel)
MS
MS_IP3@ (IPsec tunnel)
MS_Ho@ (MIP tunnel)
AN_IP1@
ePDG-v
MS_IP2@
eP_IP1@
Topological
anchor for
MS_IP3@
MS_IP3@
Serving
GW-v
HA_IP1@
DS-MIPv6 tunnel
Local topological
anchor for
MS_HoA@
PDN
GW-h
MS_Ho@
PMIPv6 tunnel
IPSec to tunnel MS into 3GPP core
IPSec tunnel
(bootstrapped by PANA)
S=MS_IP1@
D=AN_IP1@
UDP
hdr
ESP
hdr
Resulting packet that
will leave the MS (UDP
headers in dashed
boxes only apply if
NA(P)T on path
S=MS_IP2@
D=eP_IP1@
UDP
hdr
ESP
hdr
S=MS_IP3@
D=HA_IP1@
UDP
hdr
S=Ho@
D=CN_IP@
TCP/
UDP hdr
Just to demonstrate how
complex the tunneling can be.
This is the worst case. In
practice, the ePDG-v will
probably not be there. At least,
let’s hopeMuse
so ...confidential
Overhead
becomes quite huge.
L7
data
ESP
trailer
ESP
trailer
Legend
Physical NIC
Logical NIC (”overloaded on a physical NIC)
Indicates to which NIC a logical NIC is tied