1. Introduction considering comments from: 21-05-0413-00-0000-General_MIH_ref_model.doc (ref 1) 21-05-0423-00-0000-GeneralModel5_5_v1.doc (ref 2) 21-05-0425-00-0000-InterDigital3GPPAmendments.doc (ref 3) 2. Figure 3: General MIH Reference Model Direction of the arrows to be discussed CS Higher Layer (eg. mobility management apps.) ES CS IS MIH Function CS CS ES IS IS MIH Function E S C S I S Lower layer Transport ES IS Higher Layer Transport ES Upper Layers E S C S I S MIH Function E S C S I S E S C S I S CS 3 GPP 3 GPP2 802.x ( 11,16) ES Lower Layers IS Network Side Terminal Side Legend Layer 3 Transport ES: Event Service Layer 2 Transport CS: Command Service Local Interactions IS: Information Service Our Comments : compared to orignial figure, the management plane is substituted with “Media Independent L2 Transport”. Management plane is technology specific and is already covered by the respective boxes The direction of ES, CS, IS locally between MIHF and L2-Transport box is bidirectional. It is because, just like higher layer, this transport is used to carry the information between the peers. Since the L2-Transport box is situated in the terminal, it is local communication between MIHF and itself The intention of remaining ES, CS and IS pointing to lower layers is to extract the information from the respective technology locally. It is also valid for IS as some information is already available and can be acquired directly instead of contacting the server (eg. QoS support in .11, is being discussed in .11e and can be extracted directly if it is integrated) Comments from e-mail: 1) Ref (1) shows the transport of MIH services between Lower Layer at the network side and 802.21 MIH function as a local interface. However there are other cases to consider. For example, in ref (3) we show this scenario as the collocated case. However we also show that these services can transported over higher layer transport (L3) or layer 2 as well. Furthermore in ref (3) we stress that at the network side there is no direct communication between 3GPP/3GPP2 lower layers and the MIH function. 2) In ref (3) 3GPP and 3GPP2 communicate toward a MIH Network Entity using higher layer transport. This is not described in ref (1) 3) Ref (1) shows communication from MIH function in the client station to its peer at the Network through a higher layer transport. This is consistent with ref (3). Then the interface goes through what it is referred to as 'Higher Layer' before it communicates with the MIH peer. This is very similar to ref (3) for case where the interface goes through the MIH Network Entity (e.g., the Upper Layer being part of the MIH Network Entity). However the scenario where just a L3 interface is used to communicate between two MIH peers is not described. This is depicted in ref (3) as double-headed arrow that goes from MIH to MIH simply using a Higher Layer Transport. 4) You also indicate that the management plane has been replaced by what it is referred to as L2 transport and that the Management Plane is technology specific and therefore it is already covered in the corresponding box. Here I have a comment and a question: If it is already included in the box, why would we need to specify a L2 transport? Also from ref (1) the common layer 2 transport (or lower layer) depicted in the figure indicates that both 3GPP/3GPP2 and 802 components used the same L2 transport, this is not accurate. Furthermore, we have discussed two different mechanisms to send MIH information both peer to peer and localy: 1) Over the management plane (e.g.,through the introduction of a new action frame format), and 2) Over the Data Plane using LSAP (e.g.,through the introduction of a new ethertype). It is not obvious how the "Lower layer Transport" handles these two mechanism, in particular considering that they interface between the LLT and the MIH function is depicted as a local interface. This might be accurate for locally generated events but not for peer to peer remote events Leyend: ES/CS/IS: Event Service/Command Service/Information Service CS: Convergence Sublayer LLC: Logical Link Control MAC: Medium Access Control MIH: Media Independent Handover PHY: Physical Layer MIH Network En (E.g., MIH Server Con IS/CS/ES over Higher Layer Transport Layer 3 Transport Layer 2 Transport Local Interactions Media Media Independent Independent Handover HandoverUser User Higher Layer Transport (E.g.,IP) ES/ CS/ IS Client Station Media Independent Handover Function ES/ CS/ IS Media Independent Handover Function Higher Layer Transport/L2/Colocated with MIH Higher Tran ES/ CS/ IS ES ES LLC/CS CS 3GPP/ 3GPP2 Interface LLC/CS CS IS IS MAC PHY MAC PHY MGMT 802 Interface MGMT IS/ES/CS over L2 Transport 802 Network 3GPP/ 3GPP2 Networ