xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Information Service Flow Update Date Submitted: October 22, 2006 Presented at IEEE session in Dallas Authors or Source(s): Jing Liu, Ting Yang, Yan Peng Abstract: This document clarifies the MIIS information flow and gives the detailed description about how to get these information elements over L2 transport.

xxx 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

xxx Background The MIHF uses MIH_Get_Information primitive to get MIH information service. The corresponding message may be carried over appropriate transport(L2 or L3) and is delivered to the remote MIHF. Remote MIHF returns the necessary information to the MN via the appropriate response frame. It is important to note that before an MN is authenticated with the PoA, the MN should be able to obtain all the related information elements available, if needed. In order to enable the information query before authentication, individual link technologies may provide an L2 or media specific transport or a protocol message exchange that makes this MIIS query exchange possible between the UE and a certain MIHF in the network.

xxx Problems Description In the current draft, the figure 23 (in 6.3.8) gives the MIIS information flow. It only describes the message (or primitives) between MIHF User/MIHF & MIHF/MIHF. There is no clear message exchange between MIHF and transport layer (L2 or L3). The messages (or primitives) between them need to be clarified, otherwise this protocol is difficult to be implemented and widely used.

xxx Suggested Remedy Modify figure 23 by adding a new procedure to show how to get Information Service over L2 transport.

xxx Media Specific Example In IEEE g, the MIH Control Primitives provide carriage of MIHF Frames between the entity and the NMCS. This enables the NMCS to map between MIHF frames and primitives on the MIH-SAP. –The entity may send or receive the MOB_MIH-MSG message to or from the peer entity in order to convey MIHF Frames carrying the MIH protocol messages. –The primitive C-MIH-NOTFY on the C-SAP is to indicate the reception of MOB_MIH_MSG on the air interface, or to request the entity transmits a MOB_MIH-MSG message containing the MIHF frame carried in the primitive.

xxx Media Specific Example – cont. In IEEE g, the MIH Control Primitives provide carriage of