1

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0677-01-0000Title: Amendment of the MIH Handover Procedure:

LB Issue-# 18 : Comment 495, 915 Date Submitted: September 2006Presented at IEEE 802.21 session in Melbourne, AustraliaAuthors or Source(s):  Junghoon Jee, Eunah Kim, Hongseok Jeon, Vivek GuptaAbstract: This contribution proposes mobile-initiated and network-

initiated media independent handover procedures to guide how to use the various handover messages which are defined in the IEEE P802.21/D01.00

2

IEEE 802.21 presentation release statementsThis 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> 

3

Overview

Related Comments : 495, 915 P802-21-D01-00 specifies the handover related

messages: MIH_Handover_Initiate Request/Response MIH_Handover_Prepare Request/Response MIH_Handover_Commit Request/Response MIH_Handover_Complete Request/Response

P802-21 allocates an Annex A-1 to specify the handover procedures

Currently, only one handover procedure between 802.11 and 3GPP2 is described

4

Issues

We need to have a common view regarding how to utilize the MIH handover related messages.

How do these messages complement mobility management protocols such as MIP/SIP?

Who is the sender and receiver for each message? When each message is delivered? What effect does a sender expect the receiver to perform

by sending a specific message? General MIH handover procedure needs to be

specified. It shall guide how to use the various handover messages.

5

Discussion

MN needs to indicate to Network the QoS requirements MIH_Handover_Initiate.request/response need to be updated

appropriately MIH_Handover_Prepare should happen after

MIH_Handover_Initiate.request

MIH_Switch needs to be deleted Redundant with MIH_Handover_Initiate

MIH_Commit needs to be exchanged between serving PoS and Target PoS as well

Do we need MIH_Handover_Complete? Is Link_Up on new link not adequate?

Rename commands as follows: MIH_Handover_Initiate => MIH_Candidate_Suggest MIH_Handover_Prepare => MIH_Query_Target_QoS MIH_Handover_Commit => MIH_Candidate_Select

6

Resolutions

-The need for MIH_Handover_Complete Resolution) The MIH_Handover_Complete message exchange between MN

and Target PoS is described as "Optional".

-Delete MIH_Switch Resolution) The MIH_Switch will be kept as it is. Any modification and

amendment or deletion will be dealt throughout the separate comment resolution process.

Related with that, Ulises is preparing the "Link_Switch" command in the upcoming September meeting.

-Description of the Handover procedure Resolution) Basically, definitive languages will be used in describing the

handover procedure regarding the exchange of MIH_Handover_Initiate, MIH_Handover_Prepare and MIH_Handover_Commit.

This covers the message exchange between the MN and Serving PoS. Moreover, it also applies the message exchange among PoSs. However, when describing the message exchange between Serving PoS and Target PoS, we will use somewhat more flexible language.

Naming of the protocol messages Resolution) We took the "Option 3" which keeps the current naming like

MIH_Handover_Initiate, MIH_Handover_Prepare and MIH_Handover_Commit and will add more clarify and precise meaning. More tuning about the message naming can be dealt with separate comment in LB process.

7

Proposal

Accept the remedies as specified in 21-06-06-0677-Handover_Command_Update.doc