IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0797-00-0000 Title: MIH Registration Amendments Date Submitted: Nov.1, 2006 Submitted for discussion and possible inclusion in the draft against LB_1a comment Authors or Source(s): Xiaoyu Liu Abstract: This contribution proposes MIH protocol registration amendments, mainly for reregistration

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> 

Technical Issues regarding MIH Registration between MIHF in MN and MIHF in a serving network. between MIHF in a serving network and detected network. Deregistration Re-Registration procedure…

Re-Registration – What? A mechanism between peer MIHF entities to indicate that the MN is still registered to the network. The difference between registration and re-registration Registration establishes a new session; a new Session ID is created; Re-registration refreshes an existing session; no need to create a new session ID

Re-Registration – When? Two cases: When the information pertaining to the joined POA has changed E.g., POA changes due to homogeneous handovers Periodic transmission (lifetime of a session) The MN determines that the peer MIHF is still available using the currently established lower layer connection.

Re-Registration – Proposed Texts The related texts in D2.0 Section 7.4.1.1, pp.93, line#29: ‘Re-Registration scope to be defined. Comment #266 to propose the primitives for MIH Re-registration Remedy #3 in contribution 21-06-0797-00-0000 Key points: existing session ID in the semantics of requests Comment #378 to propose the messages for MIH Re-registration Remedy #4 in contribution 21-06-0797-00-0000

Other Amendments Comment #215 to propose texts for section 6.4.4 Remedy 1 in contribution 21-06-0797-00-0000 Comment #267 to add Session ID in the deregistration primitives.

Other Issues to be discussed The indication and confirm primitives shall be added. Abnormal cases in MIH registration shall be considered: Registration failure cases, e.g., registration rejected. Lifetime expiry for active sessions Link layer failure due to unreliable lower layer links