1. 21-07-0205-02-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-07-0205-02-0000 Title: Handover Flow Diagrams Update Date Submitted: May 14, 2007 Presented at IEEE 802.21 session in Montreal, QC, Canada Authors or Source(s): Junghoon Jee

2. 21-07-0205-02-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 and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html> Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 http://standards.ieee.org/board/pat/guide.html

3. 21-07-0205-02-0000 Overview IEEE P802.21/D05.00 specifies handover procedures in the Annex A. A.1 Mobile-initiated handover procedure A.2 Network-initiated handover procedure A.3 Network-initiated handover from 802.16 to 3G (Single PoS) A.4 Handover from 3G to WLAN A.5 Example handover flow chart between 802.11 and 802.16 A.6 Example handover flow charts for Mobile IP A.7 Handover flow diagram for abnormal cases

4. 21-07-0205-02-0000 Problems Statement Protocol message naming inconsistency with the normative part. Use of obsolete MIH_Switch. Different assumption about the relationship MIH primitive and lower layer connection setup or higher layer execution. Relationship between MIH_Net(MN)_HO_Commit and L2 connection setup. Relationship between MIH_MIH_MN_HO_Complete and higher layer handover execution. Related contributions 21-07-0110-01-0000-HO_SignallingDiagrams (A2, A3, A4.1, A4.2) 21-07-0181-00-0000-Optimization about A.4.1 and A.4.2 (A4.1, A4.2)

5. 21-07-0205-02-0000 Resolution Guideline Follow the protocol name as defined in the normative section. With the form of MIH_Net_HO_Candidate_Query “Request” Four Steps Step 1. Resource Availability Check MIH_(MN)Net_HO_Candiate_Query MIH_N2N_HO_Candidate_Query Step 2. Resource Preparation MIH_N2N_HO_Commit Step 3. Handover Commitment MIH_(MN)Net_HO_Commit MIH_Configure_Link Step 4. Resource Release MIH_MN_HO_Complete MIH_N2N_HO_Complete

6. 21-07-0205-02-0000 Mobile-initiated case

7. 21-07-0205-02-0000 Network-initiated case

8. 21-07-0205-02-0000 Working Status Contributors Juan-Carlos Zuniga Yoshihiro Ohba Junxiang Guo Junghoon Jee Amendment role A.1 and A.2 : Junghoon Jee by updating 21-07-0010 A.3 and A.4 : Juan-Carlos by updating 21-07-0110 A.4 – A.7 : Junxiang Guo