Encapsulate LE MAC management messages into CXP-REQ/RSP-MAC message IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16h-07/074 Date Submitted: Source: Shulan FengVoice: Bld.17, No.8, Dongbeiwang West Road, Hai-Dian District, Beijing, P. R. China Venue: hD2b Base Contribution: None. Purpose: Decision. Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. Release: 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 Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Further information is located at and.

Why do we need Encapsulate MAC management messages MAC management message type may be exhausted by so many amendment –IEEE e-2005[1] has used 0~66 –16j baseline document[2] updated June has used 67~97 More messages will be accepted this session –16h draft document[3] has used 67~81 –16m may use more management type The messages used by different TG may conflict –Message type used by 16j conflict with 16h –16m may face same problem Encapsulating messages may be make standard clearer and easy to implement –Such as CXP-REQ/RSP-MAC message

Two Encapsulation mechanisms First Solution –Some intersystem communication messages are encapsulated into CXP-REQ/RSP-MAC messages –Others remain Second Solution – Encapsulate all additional LE MAC management messages into CXP-REQ/RSP-MAC messages –All additional LE MAC management messages can be look as messages used for intersystem communication Second Solution seem to be better –Clearer, simple, low possibility to conflict with other TGs, easy to be accepted by WG

General Procedure of Intersystem communication over air

Two directions From source to destination: CXP-REQ-MAC –Form source BS to forward SS –From forward SS to destination BS –These two links can be combined or alone From destination to source: CXP-RSP-MAC –From destination BS to forward SS –From forward SS to source BS –These two links can be combined or alone Source BS can be the forward SS’s serving BS or not Destination BS can be the forward SS’s serving BS or not

Connection ID CXP message may be broadcast message or multicast message or dedicate message –BSD is broadcast message –ADPD is multicast message –RA-REQ is dedicate message CXP-REQ/RSP-MAC messages can be transmitted used by broadcast CID or basic CID –Based on the property of encapsulated messages

Some Examples Message TypeFromToCID BSDSource BS ( Foreign BS) Forward SSsBroadcast BS_CCID_REQForward SSDestination BS (Serving BS) Basic SSURFForward SSDestination BS (Foreign BS) Basic ADPDSource BSForward SSsMulticast ADV-REQDestination BSForward SSsBroadcast NotificationSource BSForward SSBasic ADV-RSPForward SSDestination BSBasic RS-REQDestination BSForward SSBasic ADV-RSPForward SSDestination BSBasic

Conclusion and Further Work For TG Decision: All additional LE MAC message may be encapsulated into CXP-REQ/RSP-MAC message. If TG agree this suggestion, then some further work needed –Identify the transmission direction, transmission CID for all LE MAC messages, including MAC information in section 15.5 –Rewrite the CXP-REQ/RSP-MAC message –Review all MAC messages ( including section and 15.5) –An ad hoc on MAC messages should be set up to do further work

Reference [1] IEEE e-2005 [2] 80216j-06_026r4 [3] P80216h_D2b