21-05-xxxx-00-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-xxxx-00-0000 Title: Support for query of the registered event at MIH Layer and Link.

Slides:



Advertisements
Similar presentations
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Handover Procedure – Redraw of Annex Figure Date Submitted: October.
Advertisements

_link_parameter_report IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Definition and enhancements to MIH Link Parameter.
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
21-06-xxxx-xx-0000 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Network Selection Date Submitted: Apr, 20, 2006 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Utilizing terminal identifier to recognize the reserved resources.
MuGM IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Group management mechanisms Date Submitted: November, 2012 Authors or Source(s): Daniel.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Clarification for Handover Primitives Date Submitted: February,
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx-00-MuGM Title: Outline of MuGM Date Submitted: January, 15th, 2013 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendments for Event Register Date Submitted: July, 10, 2006 Presented.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Information Service Flow Update Date Submitted: October 22, 2006.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Instructions to get a Free IEEE Web Account Date Submitted: January.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Message Flow Date Submitted: March 1, 2011 Authors or Source(s): Fernando Bernal-Hidalgo,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Notify high layer when events change Date Submitted: Jan, 06,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Handover Flow Diagrams Update Date Submitted: May 14, 2007 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Capability Discovery Amendment Date Submitted: April 20, 2006.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: FMCA MIH Work Item Date Submitted: March, 2009 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Comments Date Submitted: Jan, 06, 2006 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Events generated by MIH Users Date Submitted: February, 17th,
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IEEE c TG November 2012 Report and Agenda Date Submitted: November.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Optimize MIIS Get Information Message Date Submitted: February.
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: Suggestion about link parameters report Date Submitted: Jan 10,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendment-for-Link_Handover_Complete.Indication- primitive Date.
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst Title: Overview of Draft P802.21b/D0.01 Date Submitted: May 11, 2010 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Registration Amendments Date Submitted: Nov.13, 2006 Submitted for discussion.
21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendment for MIH_Handover_Initiate.request Date Submitted: April.
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Multiple MIH User Issues Date Submitted: November, 12-16, 2007.
IEEE DCN: SAUC Title: TG Closing Note Date Submitted: November 14, 2013 Presented at IEEE session #59 in Dallas, Texas,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposal for power consumption information related to different.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
21-06-xxx-LocInfo_in_IS_request
Presentation transcript:

21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Support for query of the registered event at MIH Layer and Link Layer Presented at IEEE session #17 in Dallas Authors or Source(s): Dong Peiying, Shu Guiming, Guo Junxiang Abstract: For the convenience of the implement of the MIH, the query methods for the registered events should be provided. Through the methods, MIH User can query its registered events from MIH Function and MIH Function can query its registered events from Lower link layers.

21-05-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 outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

21-05-xxxx Background In current draft, we have MIH_Event_Register.request and Link_Event_Register.request for MIH Users and MIHF to register events they concerned at MIH Layer and Link Layer, and by the primitives of MIH_Event_Register.confirm and Link_Event_Register.confirm, MIH Users and MIHF can know what events have been registered successfully. In general, there are more than one MIH Users will register events they concerned at MIH Function, for the reason of this, every MIH User has to remember their registered event status for future use, such as in some time it wants a different list of events indication, it can compare the new list to the old list then go to next step. So if there is query method of the registered event between MIH User and MIH Function, it will be much easier for the implement of the MIH User, for it can query the registered event status at any time. While there is also query requirement of registered event between MIH Function and Link Layer.

21-05-xxxx Background Now that we have methods for registering events, for convenience we should have some methods for query event registered at different layers. Through the methods, MIH Users and MIHF can query what events they have registered at target layers.

21-05-xxxx New primitives for query of the registered events Add new primitives for query of registered events at MIHF : …… MIH_RegisteredEvent_Discover MIH_RegisteredEvent_Discover.request Function This primitive is used by MIH User (the registrant) to query what events it has registered at MIH Function. The response indicates the events list which the MIH User has registered at MIH Function Semantics of the service primitive The parameters of the primitive are as follows: MIH_RegisteredEvent_Discover.request ( SourceIdentifier, DestinationIdentifier, LinkIdentifier)

21-05-xxxx New primitives for query of the registered events NameTypeValid rangeDescription Source IdentifierIdentifierAny valid individual or group identifier The identifier of entity where the request is initiated. This field may be optionally left empty if the command is local. Destination Identifier IdentifierValid MIHF identifier The destination identifier of request or response. This is the identifier of local or peer MIHF When generated This primitive is generated by a registrant such as MIH User that is seeking to query what events it has registered at MIHF Effect on receipt The recipient responds immediately with MIH_Event_Register.confirm primitive.

21-05-xxxx New primitives for query of the registered events MIH_RegisteredEvent_Discover.confirm Function This primitive return the results of the request of the query of registered event by MIH User Semantics of the service primitive The parameters of the primitive are as follows: MIH_RegisteredEvent_Discover.confirm ( SourceIdentifier, DestinationIdentifier, LinkIdentifier RegisteredEventList )

21-05-xxxx New primitives for query of the registered events NameTypeValid rangeDescription RegisteredEventList Set of Event IDs Set of valid link events The list of the registered events When generated This primitive is generated in response to a MIH_RegisteredEvent_Discover.request primitive Effect on receipt The recipient may examine the returned event list and learn about the registration status of different events.

21-05-xxxx New primitives for query of the registered events Add new primitives for query of registered events at Link Layer : …… Link_RegisteredEvent_Discover.request Function This primitive is used by MIH Function (the registrant) to query what events it has registered at Lower Layer. The response indicates the events list which the MIH Function has registered at Lower Layer Semantics of the service primitive The parameters of the primitive are as follows: Link_RegisteredEvent_Discover.request ( )

21-05-xxxx New primitives for query of the registered events When generated This primitive is generated by a registrant such as MIH Function that is seeking to query what events it has registered at Lower Layer Effect on receipt The recipient responds immediately with Link_RegisteredEvent_Discover.request primitive Link_RegisteredEvent_Discover.confirm Function This primitive return the results of the request of the query of registered event by MIH Function Semantics of the service primitive The parameters of the primitive are as follows: Link_RegisteredEvent_Discover.confirm ( RegisteredEventList )

21-05-xxxx New primitives for query of the registered events NameTypeValid rangeDescription RegisteredEventList Set of Event IDs Set of valid link events The list of the registered events of link layer When generated This primitive is generated in response to a Link_RegisteredEvent_Discover.request primitive Effect on receipt The recipient may examine the returned event list and learn about the registration status of different events.