Edge Mobility Protocol (EMP)Edge Mobility Protocol (EMP)(draft-wood-netlmm-emp-base-00.txt)(draft-wood-netlmm-emp-base-00.txt)

Jonathan Wood

Katsutoshi Nishida

Vancouver, November 2005

IETF 64th – netlmm BOF

2

Vancouver, November 2005

IETF 64th – netlmm BOFLogical Network Architecture and Logical Network Architecture and Functional EntitiesFunctional EntitiesLogical Network Architecture and Logical Network Architecture and Functional EntitiesFunctional Entities

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

EMAPEMAP

MNMN

AARAAR AARAAR

AP AP

MNMN MNMN

AP

EMAPEMAP

AARAAR

AP

MNMN

Edge Mobility Domain1

(EMD1)

EMD2

Intra link Mobility Local MobilityLocal Mobility Global Mobility

Functional entities defined by EMPFunctional entities defined by EMP

3

Vancouver, November 2005

IETF 64th – netlmm BOFScope of Edge Mobility Protocol Scope of Edge Mobility Protocol ~ what is specified in our proposal ~~ what is specified in our proposal ~Scope of Edge Mobility Protocol Scope of Edge Mobility Protocol ~ what is specified in our proposal ~~ what is specified in our proposal ~

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

EMAPEMAP

AARAAR

AP

MNMN

EMP

Standard IP

EMP Binding*

EMD or GMP

*Triggers to initiate EMP protocol

e.g. link dependent signaling, IPv6 ND signaling

CN or GMAPCN or GMAP

EMP is the protocol for

AAR-EMAP routing path management

4

Vancouver, November 2005

IETF 64th – netlmm BOFCharacteristics of Edge MobilityCharacteristics of Edge MobilityProtocolProtocolCharacteristics of Edge MobilityCharacteristics of Edge MobilityProtocolProtocol

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

5

Vancouver, November 2005

IETF 64th – netlmm BOFCharacteristics of Edge Mobility Characteristics of Edge Mobility Protocol (Cont’d) Protocol (Cont’d) Characteristics of Edge Mobility Characteristics of Edge Mobility Protocol (Cont’d) Protocol (Cont’d)

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

6

Vancouver, November 2005

IETF 64th – netlmm BOF

Protocol OverviewProtocol OverviewProtocol OverviewProtocol Overview

EMAPEMAP

AARAAR AARAAR

AP

MNMN

AP

Edge Mobility Domain

2) EMP Binding

(e.g. L2 trigger)

3) UPDATE (MNID, IP Addr)

1) Boot up

4) Setup Tunnel

7

Vancouver, November 2005

IETF 64th – netlmm BOF

Protocol OverviewProtocol OverviewProtocol OverviewProtocol Overview

EMAPEMAP

AARAAR AARAAR

AP

MNMN MNMN

AP

Edge Mobility Domain

1) Handover

2) EMP Binding

(e.g. L2 trigger)

3) Query (MNID, IP Addr)

4) Tunnel Switch

8

Vancouver, November 2005

IETF 64th – netlmm BOF

……

NodeB EvolvedNodeB

AP AP AP AP

3G UMTS(UTRAN)

3G EvolvedUTRAN

WLANAccess

New Radio/Fix Accesses

NETLMM Protocol

… …

EMAP Operator Core Network

MNMN MNMN

Radio dependentMobility Management

Use Case of NETLMM ProtocolUse Case of NETLMM ProtocolUse Case of NETLMM ProtocolUse Case of NETLMM Protocol

Operators can benefit from NETLMM Protocol since it provides IP Mobility meeting requirements

NodeB EvolvedNodeB