Presentation is loading. Please wait.
Published byValerie Matthews Modified over 7 years ago
21-06-0501-02-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0501-02-0000 Title: Amendments for Event Register Date Submitted: July, 10, 2006 Presented at IEEE 802.21 session #15 in San Diego Authors or Source(s): Zhuang Hongcheng ， Zhang Jietao Abstract: This document proposes an amendment for event register. MIH users can take more appropriate actions according to the result codes when event register succeeds or fails.
21-06-0501-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
21-06-0501-02-0000 Background and Problem Background Higher layer entities can register to receive event notifications from a particular event source. These services facilitate Mobile terminal or Network controlled handover. Problem In the register process, it is possible that some events couldn’t be registered correctly, but there are no primitives or methods to notify MIH user about the failure reasons in the current draft standard. For example, link event register maybe fail because of disappearance of the event source or other reasons.
21-06-0501-02-0000 Amendment of MIH_Event_Register.response Primitives (1) Section 188.8.131.52 MIH_Event_Register Response The response indicates which of the event types were successfully registered or why they were registered unsuccessfully. NameType ResponseEventListEvent List (255) ResultCodeListResult Codes List
21-06-0501-02-0000 Result Code Reason CodeDescription 0Successful RegisteredThis code indicates that the event is registered successfully 1Event ID InvalidThe Event ID Number is invalid 2~12Reserved 13~15UnspecifiedVendor Specific reason code The Result Codes can be defined as the following.
21-06-0501-02-0000 Amendment of Link_Event_Register.confirm Primitives (2) Section7.3.4 MIH Event Register: The primitive parameters are as follows: Link_Event_Register.confirm ( ResponseEventList ResultCodeList ) NameTypeValid RangeDescription ResponseEvent List Set of Event IDsSet of valid link events List of link layer events ResultCodeListSet of Result Codes Set of valid result codes List of event registration status
© 2023 SlidePlayer.com Inc.
All rights reserved.