21-08-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: XXXX Title: MIH_MN_HO_Commit Revisited Date Submitted: March, 2008 Presented at IEEE session #25 in Orlando Authors or Source(s): Junghoon Jee Abstract:

21-08-xxxx IEEE 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 IEEE The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6

21-08-xxxx Overview History of MIH_MN_HO_Commit From Remote to Local in D8.0 Deleted it in D9.0 Duplicated functionality with the MIH_Link_Actions The #2217 in this round of SB The need of the MIH_MN_HO_Commit and making it as remote command mih-mn-ho-commit.doc

21-08-xxxx Principle Main motivation in revisiting the MIH_MN_HO_Commit is to provide the way for MN to notify Serving PoS of the decided target network information. Two main functions by commanding through MIH_Link_Actions/MIH_MN_HO_Commit Link Switching Target Network Notification which enables the Resource Reservation at the target network Decide whether to couple the link switching with the resource reservation: 1) Loose coupling: The link switching may happen without the resource reservation. 2) Tight coupling: The link switching shall happen after identifying the resource reservation results.

21-08-xxxx Principle (2) Define the way to notify Serving PoS of the target info: 1) MIH Command In the form of Request and Response The MN shall wait until receiving the response message from the peer. Does the MN have to wait until the resource is reserved at the target? 2) MIH Event In the form of unidirectional Indication The MN does not need wait the peer’s response The MN can proceed the following actions. What We Defined: MIH Event: MIH_Link_Handover_Imminent MIH Command: MIH_MN_HO_Commit Any other facility?

21-08-xxxx Conclusion We have three options 1) Amend the MIH_Link_Handover_Imminent for inter-tech handover 2) Add the MIH_MN_HO_Commit as remote command and amend the MIH_Link_Handover_Imminent for inter-tech handover 3) Leave as it is