IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 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): Abstract: 21-05-0812-00-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-0812-00-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 functionality Any missing functionality 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-0812-00-0000

Candidate Access Network 2 MIP_Proxy_Router_Adv Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2 MIH User MIHF MAC-1 MAC-2 POA-S Serving POS MIH User MIIS Server POA-C1 Candidate POS1 MIH User POA-C2 Candidate POS2 MIH User Traffic Flow between MN and Serving Network Link_Parameters_Report.IND MIH_Handover_Initiate.REQ MIH_Handover_Initiate.IND MIH_Handover_Prepare.REQ MIH_Handover_Prepare.REQ MIH_Handover_Prepare.REQ MIH_Handover_Prepare.IND MIH_Handover_Prepare.IND MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.CFM MIH_Handover_Initiate.RESP MIH_Handover_Initiate.RESP MIH_Handover_Initiate.CFM MIH_Handover_Commit.REQ MIH_Handover_Commit.REQ MIH_Handover_Commit.IND MIP_Proxy_Router_Adv MIH_Handover_Commit.RESP MIH_Handover_Commit.RESP MIH_Handover_Commit.CFM MIP_Fast_BU MIP_Handover_initiate.REQ MIP_Handover_initiate.ACK 21-05-0812-00-0000 * Commit can be possibly be done after link establishment in target.

a) Link Establishment MIP_Fast_BAck MIP_Fast_BAck Tunnel Packets Mobile Node Serving Access Network Candidate Access Network 1 Candidate Access Network 2 MIH User MIHF MAC-1 MAC-2 POA-S Serving POS MIH User MIIS Server POA-C1 Candidate POS1 MIH User POA-C2 Candidate POS2 MIH User MIP_Fast_BAck MIP_Fast_BAck “Link-Connect” Link Establishment MIH_Link_Up MIH_Link_Up Tunnel Packets MIP_Fast_BU Forward Packets MIP_Fast_BU MIH_Handover_Complete.REQ This can be optional since there is equivalent mobility signaling MIH_Handover_Complete.REQ MIH_Handover_Complete.IND MIH_Handover_Complete.REQ MIH_Handover_Complete.REQ MIH_Handover_Complete.IND MIH_Handover_Complete.RESP MIH_Handover_Complete.RESP MIH_Handover_Complete.CFM MIH_Handover_Complete.RESP MIH_Handover_Complete.RESP MIH_Handover_Complete.CFM Replace with MIH_Handover_Complete.IND?? 21-05-0812-00-0000

Candidate Access Network 2 MIP_Proxy_Router_Adv b) Mobile Node Serving Network Candidate Network 1 Candidate Access Network 2 MIH User MIHF MAC-1 MAC-2 POA-S Serving POS MIH User MIIS Server POA-C1 Candidate POS1 MIH User POA-C2 Candidate POS2 MIH User Traffic Flow between MN and Serving Network Link_Parameters_Report.IND MIH_Link_Parameters_Report.IND MIH_Link_Parameters_Report.IND MIH_Handover_Initiate.REQ MIH_Handover_Initiate.REQ MIH_Handover_Initiate.IND MIH_Handover_Initiate.RESP MIH_Handover_Initiate.RESP MIH_Handover_Initiate.CFM MIH_Handover_Prepare.REQ MIH_Handover_Prepare.REQ MIH_Handover_Prepare.REQ MIH_Handover_Prepare.IND MIH_Handover_Prepare.IND MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.RESP MIH_Handover_Prepare.CFM MIP_Proxy_Router_Adv MIH_Handover_Commit.REQ MIH_Handover_Commit.REQ MIH_Handover_Commit.IND MIP_Fast_BU MIP_Handover_initiate.REQ MIH_Handover_Commit.RESP MIP_Handover_initiate.ACK 21-05-0812-00-0000

b) Link Establishment MIP_Fast_BAck MIP_Fast_BAck Mobile Node Serving Access Network Candidate Access Network 1 Candidate Access Network 2 MIH User MIHF MAC-1 MAC-2 POA-S Serving POS MIH User MIIS Server POA-C1 Candidate POS1 MIH User POA-C2 Candidate POS2 MIH User MIP_Fast_BAck MIP_Fast_BAck “Link-Connect” Link Establishment MIH_Handover_Commit.RESP MIH_Handover_Commit.CFM MIH_Link_Up MIH_Link_Up Forward Packets MIP_Fast_BU Tunnel Packets MIP_Fast_BU MIH_Handover_Complete.REQ This can be optional since there is equivalent mobility signaling MIH_Handover_Complete.REQ MIH_Handover_Complete.IND MIH_Handover_Complete.REQ MIH_Handover_Complete.REQ MIH_Handover_Complete.IND MIH_Handover_Complete.RESP MIH_Handover_Complete.RESP MIH_Handover_Complete.CFM MIH_Handover_Complete.RESP MIH_Handover_Complete.RESP MIH_Handover_Complete.CFM Replace with MIH_Handover_Complete.IND?? 21-05-0812-00-0000