21-05-0813-01-0000 ieee 802.21 media independent handover...
DESCRIPTION
Motivation An example to capture current understanding of MIH interworking with IP mobility signaling Intent is to utilize the flow for following purposes, to identify Any superfluous or mandatory functionality (that lead to inefficiency) Any missing functionality that is required How do we deal with superfluous functionality? May be there are other IP mobility mechanisms that may find it useful But, mechanisms that already has this functionality should not be forced to use it Logical approach is to make them optional for efficient interworking related to known mobility mechanisms Two flows are shown a) MN Initiated b) Network InitiatedTRANSCRIPT
21-05-0813-01-0000
• IEEE 802.21 MEDIA INDEPENDENT HANDOVER• DCN:21-06-0813-01-0000-LB1a-handover-big-picture.ppt• Title: LB 1a, Handover example flow with MIP• Date Submitted: November, 2006• Presented at IEEE 802.21 session #NN in Dallas, TX• Authors or Source(s): Srinivas Sreemanthula
• Abstract: Study interactions with MIP
21-05-0813-01-0000
IEEE 802.21 presentation release statements• This document has been prepared to assist the IEEE 802.21 Working Group.
It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
• The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21.
• The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual <http://standards.ieee.org/guides/opman/sect6.html#6.3> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>
21-05-0813-01-0000
Motivation• An example to capture current understanding of MIH
interworking with IP mobility signaling• Intent is to utilize the flow for following purposes, to identify
• Any superfluous or mandatory functionality (that lead to inefficiency)
• Any missing functionality that is required• How do we deal with superfluous functionality?
• May be there are other IP mobility mechanisms that may find it useful
• But, mechanisms that already has this functionality should not be forced to use it
• Logical approach is to make them optional for efficient interworking related to known mobility mechanisms
• Two flows are shown a) MN Initiated b) Network Initiated
21-05-0813-01-0000
MIH User MIHF MAC-1 MAC-2 POA-S Serving
POSMIH User
MIIS Server
POA-C1
Candidate POS1
MIH User
POA-C2
Candidate POS2
MIH User
Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2
Traffic Flow between MN and Serving NetworkLink_Parameters_Report.IND
MIH_Handover_Initiate.REQ
MIH_Handover_Commit.RESPMIH_Handover_Commit.CFM
a1)
MIH_Handover_Prepare.REQ
MIH_Handover_Prepare.REQMIH_Handover_Prepare.REQ
MIH_Handover_Prepare.INDMIH_Handover_Prepare.RESP
MIH_Handover_Prepare.IND
MIH_Handover_Prepare.RESPMIH_Handover_Prepare.RESP
MIH_Handover_Prepare.RESPMIH_Handover_Prepare.CFM
MIP_Proxy_Router_Adv
MIP_Handover_initiate.REQ
MIP_Handover_initiate.ACK
MIH_Handover_Commit.RESP
MIP_Fast_BU
MIH_Handover_Initiate.IND
MIH_Handover_Initiate.CFM
MIH_Handover_Commit.REQ
MIH_Handover_Initiate.RESP
MIH_Handover_Commit.IND
MIH_Handover_Initiate.RESP
MIH_Handover_Commit.REQ
* Commit can be possibly be done after link establishment in target.
?
This can be optional since there
is equivalent mobility signaling
Replace with
Decision Results in FBU
MN
Initiated-I
21-05-0813-01-0000
MIH_Handover_Complete.REQ
MIH_Handover_Complete.REQ
MIH_Handover_Complete.RESP
MIH_Handover_Complete.IND
MIH_Handover_Complete.REQ
MIH_Handover_Complete.IND
MIH_Handover_Complete.RESP
MIH_Handover_Complete.REQ
MIH_Handover_Complete.RESPMIH_Handover_Complete.CFM
MIH_Handover_Complete.RESP
MIH_Handover_Complete.CFM
Link Establishment“Link-Connect”
MIP_Fast_BAckMIP_Fast_BAck
MIP_Fast_BU
MIP_Fast_BU
Forward Packets
MIH_Link_Up Tunnel Packets
This can be optional since there
is equivalent mobility signaling
a2)
MIH_Link_Up
?Replace with
MIH User MIHF MAC-1 MAC-2 POA-S Serving
POSMIH User
MIIS Server
POA-C1
Candidate POS1
MIH User
POA-C2
Candidate POS2
MIH User
Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2
MN
Initiated-II
21-05-0813-01-0000
Traffic Flow between MN and Serving NetworkLink_Parameters_Report.IND
MIH_Handover_Initiate.IND
MIH_Handover_Initiate.RESP
MIH_Handover_Initiate.REQ
MIH_Handover_Initiate.RESP
MIH_Handover_Commit.REQMIH_Handover_Commit.IND
MIH_Handover_Commit.RESP
b1)
MIH_Link_Parameters_Report.INDMIH_Link_Parameters_Report.INDMIH_Handover_Initiate.REQ
MIH_Handover_Initiate.CFMMIH_Handover_Prepare.REQ
MIH_Handover_Prepare.REQMIH_Handover_Prepare.REQ
MIH_Handover_Prepare.INDMIH_Handover_Prepare.RESP
MIH_Handover_Prepare.IND
MIH_Handover_Prepare.RESPMIH_Handover_Prepare.RESP
MIH_Handover_Prepare.RESPMIH_Handover_Prepare.CFM
MIP_Proxy_Router_Adv
MIP_Handover_initiate.REQ
MIP_Handover_initiate.ACK
MIH_Handover_Commit.REQ
MIP_Fast_BU
MIH User MIHF MAC-1 MAC-2 POA-S Serving
POSMIH User
MIIS Server
POA-C1
Candidate POS1
MIH User
POA-C2
Candidate POS2
MIH User
Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2
MIH_Handover_Commit.RESPMIH_Handover_Commit.CFM
* In this case, Handover commit is useful since Proxy-Adv cannot serve as a commit
NE
T Initiated-
I
21-05-0813-01-0000
MIH_Handover_Complete.REQ
MIH_Handover_Complete.REQ
MIH_Handover_Complete.RESP
MIH_Handover_Complete.IND
MIH_Handover_Complete.REQ
MIH_Handover_Complete.IND
MIH_Handover_Complete.RESP
MIH_Handover_Complete.REQ
MIH_Handover_Complete.RESPMIH_Handover_Complete.CFM
MIH_Handover_Complete.RESP
MIH_Handover_Complete.CFM
Link Establishment“Link-Connect”
MIP_Fast_BAckMIP_Fast_BAck
MIP_Fast_BU
MIP_Fast_BU
Tunnel Packets
MIH_Link_Up Forward Packets
This can be optional since there
is equivalent mobility signaling
b2)
MIH_Link_Up
MIH User MIHF MAC-1 MAC-2 POA-S Serving
POSMIH User
MIIS Server
POA-C1
Candidate POS1
MIH User
POA-C2
Candidate POS2
MIH User
Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2
?Replace with
NE
T Initiated-
II
21-05-0813-01-0000
Conclusion• Some remote MIH HO command signaling can be optimized with
use of the necessary MIP signaling by generating local events from MIP (MIH-User) to MIHF
• Considering this optimization is MIP specific, the use of these MIH commands can be made optional
• Events or notifications from MIH-User to MIHF is missing, adding this to the MIH functionality is useful