Transcript Localized Mobility Management for Super 3G

Edge Mobility Protocol (EMP)
(draft-wood-netlmm-emp-base-00.txt)
Jonathan Wood
Katsutoshi Nishida
Vancouver, November 2005
IETF 64th – netlmm BOF
Vancouver, November 2005
Logical Network Architecture and
Functional Entities
Edge Mobility Domain1
(EMD1)
IETF 64th – netlmm BOF
EMAP
EMAP
AAR
AAR
AAR
AP
AP
AP
AP
MN
MN
MN
MN
Intra link Mobility
Local Mobility
EMD2
Global Mobility
Functional entities defined by EMP
 EMAP: Edge Mobility Anchor Point
 Manages MN’s location and forwards packet for MN
 AAR: Advanced Access Router
 Sends L3 location information to EMAP, instead of MN
2
Vancouver, November 2005
Scope of Edge Mobility Protocol
~ what is specified in our proposal ~
CN or
GMAP
Standard IP
or GMP
EMD
EMAP
EMP
AAR
AP
EMP
Binding*
IETF 64th – netlmm BOF
What is in scope
 Basic Routing Management within the EMD
 i.e. between AAR and EMAP
What is not specified
 EMP Binding
 Interactions between the MN and AAR
 Depends on the actual link layer used
EMP is the protocol for
AAR-EMAP routing path management
MN
*Triggers to initiate EMP protocol
e.g. link dependent signaling, IPv6 ND signaling
3
Vancouver, November 2005
Characteristics of Edge Mobility
Protocol
IETF 64th – netlmm BOF
Allows the MN to keep using the same IP
address within the EMD
 MN IP address has the EMAP prefix
 AARs advertise the same prefix owned by the EMAP
Tunnels packets from EMAP to AAR
 EMAP tunnels packet to the correct AAR where MN locates
 Bidirectional tunneling is also supported
 EMAP manages the location of the MN by AAR
4
Vancouver, November 2005
Characteristics of Edge Mobility
Protocol (Cont’d)
IETF 64th – netlmm BOF
Uses the MNID for MN routing info management
 EMAP and AAR manage the routing info by the MNID
 MNID is not change while it is in the EMD
 e.g. NAI, MIPv6 HoA
Address Management (DAD function)
 EMAP manages IP addresses used in the EMD
IP version independent signaling
 EMP signaling can be both IPv6/IPv4
 Also, support IPv6/IPv4 packet tunneling
5
Vancouver, November 2005
IETF 64th – netlmm BOF
Protocol Overview
Edge Mobility Domain
3) UPDATE
(MNID, IP Addr)
AAR
2) EMP Binding
(e.g. L2 trigger)
AP
EMAP
4) Setup Tunnel
AAR
AP
MN
1) Boot up
6
Vancouver, November 2005
IETF 64th – netlmm BOF
Protocol Overview
Edge Mobility Domain
EMAP
AAR
4) Tunnel Switch
3) Query
(MNID, IP Addr)
AAR
AP
AP
MN
MN
1) Handover
2) EMP Binding
(e.g. L2 trigger)
7
Vancouver, November 2005
Use Case of NETLMM Protocol
IETF 64th – netlmm BOF
Operator Core Network
EMAP
NETLMM Protocol
3G UMTS
(UTRAN)
NodeB
NodeB
…
…
WLAN
Access
New Radio
/Fix Accesses
…
…
3G Evolved
UTRAN
Evolved
NodeB
MN
Radio dependent
Mobility Management
Evolved
NodeB
AP
AP
AP
AP
MN
Operators can benefit from NETLMM Protocol
since it provides IP Mobility meeting requirements
8