NSIS Signaling Protocols in Multihomed Mobile Networks

NSIS Signaling Protocols in Multihomed Mobile Networks

draft-lee-nsis-multihoming-mobility-00

Suwon Lee, Sung-Hyuck Lee, Seong-Ho JeongJong Ho Bang, Byoung-Joon Lee

Overview

Motivation • Benefits of multihoming (path-oriented signaling in mobile networks) • NSIS signaling can be used in various multihoming scenarios

This draft discusses• Basic NSIS operations in multihomed environments• NSIS applicability in multihomed scenarios

• Link/node failure• Load balancing

• Load sharing

Problem Statements (1/2)

Multihomed environment • Multiple addresses (CoAs, HoAs), multiple interfaces (homogeneous, heterogeneous), multiple paths

Registration of multiple CoAs• To provide multiple active CoAs • Out of scope of NSIS WG

Selection of the optimal path for QoS • Selection (combination) of appropriate interfaces

• Multiple NSIS messages (e.g., QUERY messages of QoS-NSLP)

Notification of alternative path• A mechanism is needed to convey alternative addresses

Problem Statements (2/2)

Path failure/media detection • To trigger NSIS operations

Interworking between resource reservation and binding update• To reduce state setup delay

Anticipated handover support• To support efficient handover

Basic NSIS operations in multihomed networks

Path selection• Gathering path information

• Selecting the best path

Receiver-initiated approach• MN: multiple QUERY messages

• CN: path selection / RESERVE message

Sender-initiated approach • MN: multiple QUERY messages

• CN: RESPONSE message

• MN: path selection / RESERVE message

• Alternative method

• MN: both QUERY messages and Binding Update messages concurrently

|--Handover-->| MN OAR AR1 AR2 AR3 CRN CRN CRN CN (OAR/AR1)(OAR/AR2)(OAR/AR3) | | | | | | | | | |---QUERY(1)->|-------------------->|---------------------->| | | | | | | | | | |---QUERY(2)-------->|--------------------->|-------------->| | | | | | | | | | |---QUERY(3)--------------->|---------------------->|------>| | | | | | | | | | | | | | | | | | Best path | | | | | | | | Selection(4) | | | | | | | | | | | | | | | |<--RESERVE(5)--| | | | |<------RESERVE(6)-----| (Flow ID | | | | | (Actual reservation) | Update) | |<----RESERVE(7)-----| | | | | | | | | | | | | | | | |<-----------TEARDOWN(8)-------------| | | | | | | | | | | | | | | | Multimedia Traffic | | | |<==================>|<====================>|<=============>| | | | | | | | | |

Basic NSIS operations in multihomed networks(Receiver-initiated approach)

NSIS Applicability in multihomed scenarios

Link/node failure • Re-directing the connection through alternative interface (path)

Load balancing• Multiple paths (interfaces) for the same application • New traffic management mechanism

• Sender: distribution of data packet to appropriate interfaces• Intermediate nodes: aggregation of flows• Receiver: assemble and re-ordering of received packets

Load sharing • Multiple paths (interfaces) for multiple applications• Intermediate nodes

• Aggregation of flows when the CN is same: BOUND_SESSION_ID

Next Steps

More details on solutions • Basic multihoming support• NSIS applicability scenarios • Site-multihoming support

Question• Should these NSIS multihoming-related issues be a WG item?