Presentation on theme: "IEEE MEDIA INDEPENDENT HANDOVER DCN:"— Presentation transcript:
1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: Title: LB 1a, Handover example flow with MIPDate Submitted: November, 2006Presented at IEEE session #NN in Dallas, TXAuthors or Source(s):Abstract:
2 IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 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 IEEEThe contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual < and in Understanding Patent Issues During IEEE Standards Development
3 MotivationAn example to capture current understanding of MIH interworking with IP mobility signalingIntent is to utilize the flow for following purposes, to identifyAny superfluous functionalityAny missing functionalityHow do we deal with superfluous functionality?May be there are other IP mobility mechanisms that may find it usefulBut, mechanisms that already has this functionality should not be forced to use itLogical approach is to make them optional for efficient interworking related to known mobility mechanismsTwo flows are shown a) MN Initiated b) Network Initiated
4 Candidate Access Network 2 MIP_Proxy_Router_Adv Mobile NodeServing NetworkCandidate Network 1Candidate Access Network 2MIH UserMIHFMAC-1MAC-2POA-SServing POSMIH UserMIIS ServerPOA-C1Candidate POS1MIH UserPOA-C2Candidate POS2MIH UserTraffic Flow between MN and Serving NetworkLink_Parameters_Report.INDMIH_Handover_Initiate.REQMIH_Handover_Initiate.INDMIH_Handover_Prepare.REQMIH_Handover_Prepare.REQMIH_Handover_Prepare.REQMIH_Handover_Prepare.INDMIH_Handover_Prepare.INDMIH_Handover_Prepare.RESPMIH_Handover_Prepare.RESPMIH_Handover_Prepare.RESPMIH_Handover_Prepare.RESPMIH_Handover_Prepare.CFMMIH_Handover_Initiate.RESPMIH_Handover_Initiate.RESPMIH_Handover_Initiate.CFMMIH_Handover_Commit.REQMIH_Handover_Commit.REQMIH_Handover_Commit.INDMIP_Proxy_Router_AdvMIH_Handover_Commit.RESPMIH_Handover_Commit.RESPMIH_Handover_Commit.CFMMIP_Fast_BUMIP_Handover_initiate.REQMIP_Handover_initiate.ACK* Commit can be possibly be done after link establishment in target.
5 a) Link Establishment MIP_Fast_BAck MIP_Fast_BAck Tunnel Packets Mobile NodeServing Access NetworkCandidate Access Network 1Candidate Access Network 2MIH UserMIHFMAC-1MAC-2POA-SServing POSMIH UserMIIS ServerPOA-C1Candidate POS1MIH UserPOA-C2Candidate POS2MIH UserMIP_Fast_BAckMIP_Fast_BAck“Link-Connect”Link EstablishmentMIH_Link_UpMIH_Link_UpTunnel PacketsMIP_Fast_BUForward PacketsMIP_Fast_BUMIH_Handover_Complete.REQThis can beoptional since thereis equivalentmobility signalingMIH_Handover_Complete.REQMIH_Handover_Complete.INDMIH_Handover_Complete.REQMIH_Handover_Complete.REQMIH_Handover_Complete.INDMIH_Handover_Complete.RESPMIH_Handover_Complete.RESPMIH_Handover_Complete.CFMMIH_Handover_Complete.RESPMIH_Handover_Complete.RESPMIH_Handover_Complete.CFMReplace withMIH_Handover_Complete.IND??