20
Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: [email protected] GSIFI #5, June 20 – 22, Hyderabad, India IOT5- 20110014

Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: [email protected]

Embed Size (px)

Citation preview

Page 1: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobility Management Requirements for NGN

Ashutosh Dutta NIKSUN

PrincetonNew Jersey, 08540

Prepared for GISFI #5 IOT - Hyderabad

1

Contact: [email protected]

GSIFI #5, June 20 – 22, Hyderabad, India

IOT5-20110014

Page 2: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

What are Characteristics of Next Generation Networks?

• Heterogeneous networks, many access networks– Access-independent converged IP network

• Order-of-magnitude increases in bandwidth– MIMO, smart antennas– Increase in video and other high bandwidth traffic

• New terminals• New services and service enabling platforms• Large range of cell sizes, coverage areas

– PAN, LAN, WAN– Pico-cellular, micro-cellular, cellular

• Changes in traffic and traffic patterns– Rise in video on demand? Requires good high-bandwidth multicast

GSIFI #5

IOT5-20110014

Page 3: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobile Wireless Internet: A Scenario

802.11a/b/g

BluetoothIPv6Network

UMTS/CDMA Network

InternetDomain1

Domain2

UMTS/CDMA

PSTN gateway

Hotspot

CHRoaming User

Ad HocNetwork

PAN

LAN

WAN

WAN

LAN

PSTN

802.11 a/b/g

GSIFI #5IOT5-20110014

Page 4: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Backbone

AdministrativeDomain B

L2 PoA

Corresponding Host

128.59.10.7

IPch

207.3.232.10

210.5.240.10

128.59.11.8

N2

N1N1

N2

N1- Network 1 (802.11)N2- Network 2 ( CDMA/GPRS)

ConfigurationAgent

L3 PoA 207.3.232.10

MobileHost

AuthenticationAgent

Authorization Agent

RegistrationAgent

RegistrationAgent

Administrative Domain A

ConfigurationAgent

Authorization Agent

SignalingProxy

AuthenticationAgent

SignalingProxy

Layer 3 PoA

L2 PoA Layer 2 PoA

Layer 2 PoA

L3 PoA

Case Study I - Mobility Illustration in a sample IP-based network

128.59.9.6

L3 PoA

A

BC

D

900 ms media interruption

802.11 802.11

h/o delay900 ms

802.11 802.11

4 Seconds media interruption h/o delay 4 s

Handoff Delay~ 18 s

802.11 CDMA

18 Seconds media interruptionh/o delay18 s

4GSIFI #5

Page 5: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

5

Case Study II - P-CSCF Fast-handoff Experimental Results

Figure 1: Levels of MMD Optimization

Components Optimized

0 3000 6000 9000 12000

Proactive

Reactive

Non-Optimized

Type

s of

Han

doff

Time in ms

PPP TerminationLayer 2 DelayPPP ActivationMIP-SolicitationMIP-Binding Update

DHCP TriggerDHCP InformSIP TriggerSIP+Security

Media Redirection

Components Optimized

GSIFI #5IOT5-20110014

Page 6: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Motivation• It is desirable to limit the jitter, delay and packet loss

for VoIP and Streaming traffic– 150 ms end-to-end delay for interactive traffic such as

VoIP, 2% packet loss is allowed• Delay due to handoff takes place at several layers

– Layer 2 (handoff between AP), – Layer 3 (IP address acquisition, Configuration) – Authentication, Authorization– Binding Update – Media Redirection

• Rapid handoff will contribute to overall delay and packet loss

• Thus, it is essential to reduce the handoff delay introduced at different layers to provide better QoE to end users GSIFI #5IOT5-20110014

Page 7: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Objective• Develop Best Current Practices for Mobility

Management in NGN– Applicable to Rural Environment

• Develop general rules of optimization for several handoff functions

.7

GSIFI #5

IOT5-20110014

Page 8: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Key Functions Characteristics

Handoff • May take place between cell, subnet or domain• Need to optimize the handoff delay and transient data loss ( e.g., end-to-delay up to 200 ms, 3%-5% packet loss, jitter, for real-time VoIP traffic)• May use soft-handoff feature of CDMA, but need fast-handoff mechanisms for other technologies (e.g., 802.11)• Need to support session based applications for TCP and RTP traffic

Configuration •Should be configured within few milliseconds•Configures IP address and other server parameters (e.g, DNS, SIP server, Gateway)

Registration • Assist pre-session mobility• Hierarchical nature will make the registration faster• Helps location management functionality

Quality of Service

•Need to maintain same QoS during its subnet/domain movement

Location Management

•Allow user to maintain same URI irrespective of point of attachment

Technical issues for mobility management

IOT5-20110014

Page 9: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobility TaxonomyIP Mobility

PersonalTerminal Service

ApplicationLayer

NetworkLayer

Session

• Systems Optimization

MIPv4 Cellular IPHAWAIIIDMP MIP-LR MIPV6ProxyMIPv6

SIPMMMIP-LR(M)Proxy

TransportLayer

MSOCKS, MigratemSCTP

Shim Layer

HIP

Issues

• Host controlled vs. Mobile Controlled

• Mobility pattern

GSIFI #5IOT5-20110014

Page 10: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Framework Requirements for Mobility Management • It supports means of personal, service, and terminal mobility• It supports global roaming (e.g., Inter-operator roaming)• It is wireless "technology-independent”

– CDMA, WiFi, LTE• It supports single interface and multi-interface mobility• It supports both real-time and non-real-time multimedia services

– mobile telephony, mobile web access, and mobile data services• It allows a mobile station/user to maintain privacy and confidentiality• It supports multicast and anycast trees efficiently as mobile stations/users

move around– IPv6, IPTV

• It provides Secure Signaling for the mobile users• It interworks smoothly with PSTN and today's 1G/2G wireless telephony to

facilitate interworking of new operators' all IP platforms

GSIFI #5IOT5-20110014

Page 11: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobility Functions • Handoff

– Need to support Cell, Subnet and Domain– Need to support Hard handoff, Soft Handoff– Ensure the integrity, privacy and confidentiality of user’s information– All three hand-off processes ensure service mobility

• Maintain QoS of the ongoing sessions• Ensure that the mobile has access to all of its subscribed network

services and features– Domain hand-off latency should include AAA interaction– Domain handoff should not exceed MAHT to ensure continuity of real-

time sessions– Need to support both TCP and RTP/UDP protocols

• Registration– Supports complete registration for domain handoff - AAA– Supports partial registration for subnet handoff– Supports hierarchical registration when the user is far away

GSIFI #5IOT5-20110014

Page 12: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobility Functions (contd.)

• Configuration – Should not take more than a few hundred milli-seconds – Should update DNS to reflect the current address to

name mapping (Dynamic DNS)• Dynamic Address Binding

– Allows a user to maintain a universal identifier (e.g., SIP URI) regardless of its point of attachment to the network

• Location Management– Should be accurate, up-to-date– Should only be disclosed to authorized users and

relevant users

GSIFI #5IOT5-20110014

Page 13: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Mobility Optimization• Use of cross layer triggers to expedite handoff

operations– Layer 2 assisted fast-handoff

• Policy-based mobility management– Use the optimized protocol suitable for a specific application

• SIP for real-time, MIP for Non-real-time

• Pre-authentication, Pre-configuration to reduce the handoff time

• Parallelize among handoff functions– Layer 3 discovery while doing layer 2 discovery

• Proactive Discovery of Networks– IEEE 802.21

GSIFI #5IOT5-20110014

Page 14: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Next Steps• Deployment case studies with mobility

protocols (e.g., Network layer, application layer)

• Best Current Practices for mobility optimization

• Familiarize with other SDOs (e.g., IETF)

.14IOT5-20110014

Page 15: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

MobilityEvent

Network discovery &selection

Networkattachment

Configuration Securityassociation

Bindingupdate

Mediareroute

Channeldiscovery L2

association

Routersolicitation

DomainAdvertisement

Identifieracquisition

DuplicateAddressDetection

AddressResolution

Authentication(L2 and L3)

Keyderivation

Identifierupdate

Identifiermapping

Bindingcache

Tunneling

Buffering

Forwarding

Bi-casting/Multicasting

Serverdiscovery

IdentifierVerification

Subnetdiscovery

P1 P2 P3 P4 P5 P6

P11

P13

P12

P21

P22

P23

P31

P32

P33 P41

P42P51

P52

P53

P54

P61 P62

P63

P64

System decomposition of mobility event

15IOT5-20110014

Page 16: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Use Case: Cross layer and multiple interfaces

Network

Type

SSID/ Cell ID

BSSID

Operator

Security

NW

Channel

QoS

Physical Layer

Data

Rate

GSM

13989

N/A

AT&T

NA NA 1900

N/A

N/A 9.6 kbps

802.16d

NA

NA

T-Mobile

PKM

EAP-PEA

P

11

Yes

OFDM

40 Mbp

s

Wakeup WLANDownload over WLANShutdown GPS

Café

Airport

Zone 1 Zone 2 Zone 3

Zone 4 Zone 5 Zone 6

Zone 7 Zone 9

Wi-Fi

Wi-MAX

WLAN Link Going Down.

Switch to WiMAXDownload over WiMAXShutdown WLANWakeup GPS Zone 8

Wi-Fi

Connect to WLAN

Battery level lowShutdown WiMAXDownload over GSM/GPRS

Wakeup WLAN

Wi-MAX

Shutdown GPSStart Download over WLAN

Network Type

SSID/ Cell ID

BSSID Operator Security NW Channel QoS Physical Layer

Data Rate

GSM 13989 N/A AT&T NA NA 1900 N/A N/A 9.6 kbps

Network Type

SSID/ Cell ID

BSSID Operator Security NW Channel QoS Physical Layer

Data Rate

GSM 13989 N/A AT&T NA NA 1900 N/A N/A 9.6 kbps

802.11b Café 00:00:… Café .11i EAP-PEAP

6 .11e OFDM 11 Mbps

Network Type

SSID/ Cell ID

BSSID Operator Security EAP Type

Channel QoS Physical Layer

Data Rate

GSM 13989 N/A AT&T NA NA 1900 N/A N/A 9.6 Kbps

802.11b Airport 00:00:… Airport .11i EAP-PEAP

6 .11e OFDM 11 Mbps

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

Radio StateRadio State

GSM

WLAN

WiMAX

GPS

IEEE 802.21 and MP Enabled Seamless Mobility Deployment Scenario

Courtesy: IEEE 802.21 chair

Page 17: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Personal Mobility: Registration

IP-based Network

CH

Subnet 1

Subnet 2

registrar

IP-based Network

CH

Subnet 1

Subnet 2

registrar

• When lady in red moves, she– leaves her laptop behind– Uses another machine– Logs in

• User registration performed

[email protected]

[email protected]

IOT5-20110014

Page 18: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Personal Mobility: simultaneous registration of multiple bindings

IP-based Network

CH

Subnet 1

Subnet 2

Registrar& proxy

IP-based Network

CH

Subnet 1

Subnet 2• When lady in red moves, she– leaves her laptop behind– Uses another machine

• She can still be located

[email protected]@subnet2.org

Registrar& proxy

[email protected]@subnet2.org

IOT5-20110014

Page 19: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Session Mobility

IP-based Network

CH

Subnet 1

MH

Subnet 2

IP-based Network

CH

Subnet 1

Subnet 2

INVITE2

BY

E

3

RE

FER

1

IOT5-20110014

Page 20: Mobility Management Requirements for NGN Ashutosh Dutta NIKSUN Princeton New Jersey, 08540 Prepared for GISFI #5 IOT - Hyderabad 1 Contact: adutta@niksun.com

Service Mobility• Service Mobility allows a roaming user to get the same view of

the network as when he is at home• At the time of registration

–User’s service profile is retrieved from the home network–The service profile is shared with the responsible entity at

home and in the foreign network (wholly or partially)• The foreign network provides some of the service required• The home network still retains responsibility for other services• Examples of entries in the profile of interest may be address

book, call handling features, buddy lists, etc.

IOT5-20110014