MAC Management Messages for Reliable Inter-BS Communication January 2007 MAC Management Messages for Reliable Inter-BS Communication IEEE P802.22 Wireless RANs Date: 2007-01-12 Authors: Notice: This document has been prepared to assist IEEE 802.22. 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. 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 802.22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures http://standards.ieee.org/guides/bylaws/sb-bylaws.pdf including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair Carl R. Stevenson as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at patcom@iee.org. > Edward S. Zhang, Huawei Technologies

January 2007 Co-Authors: Edward S. Zhang, Huawei Technologies

January 2007 Abstract In the proposal “Connection Based Over-the-air Inter Base Station Communications” (IEEE 802.22-06/0111r1), there is no MAC management message design. In this proposal, we design four MAC messages to facilitate the reliable inter-BS communication which is proposed in that proposal. Edward S. Zhang, Huawei Technologies

General Description (1) January 2007 General Description (1) C-BS S-BS B-CPE If S-BS (Service BS) wants to transmit self-coexistence information to C-BS (Coexist BS), it can first transmit this information to B-CPE (Bridge CPE) and assign B-CPE to communicate with C-BS. B-CPE shall start to synchronize and communicate with C-BS. B-CPE should synchronize with S-BS again and feed back a report. Edward S. Zhang, Huawei Technologies

General Description (2) January 2007 General Description (2) Host BS CPE Request Response CPE communicates with the guest BS Report Acknowledgement The mechanism is detailed in “Connection Based Over-the-air Inter Base Station Communications” (IEEE 802.22-06/0111r1), Edward S. Zhang, Huawei Technologies

MAC Management Message Design January 2007 MAC Management Message Design To support inter-BS communication, four types of MAC management messages should be added to the MAC layer. Type Message Description Connection 60 BSS-REQ Base station Switch Request Primary Management Multicast Management 61 BSS-RSP Base station Switch Response 62 BSS-REP Base station Switch Report 63 BSS-ACK Base station Switch Acknowledgement Edward S. Zhang, Huawei Technologies

January 2007 BSS-REQ This message is sent by S-BS. CPEs who receive this message should begin to communicate with C-BS, which is indicated in the field of BS ID. This message may contain the CBP packet the S-BS wants to transmit to C-BS. This CBP packet is encapsulated into the field of Command. Syntax Size Notes BSS-REQ_Message_Format(){ Management Message Type = 60 8 bits Transition ID 16 bits BS ID 48 bits MAC address which uniquely identifies the C-BS Operational Channel The operational channel of the C-BS. If the S-BS does not know the this channel index, this field is set to be 0x00. Length The length of this message Confirmation Needed 1 bit 0 = No confirmation needed 1 = Confirmation needed Command variable The format of this field is vendor-dependent. It can be used to convey BS commands or the information the S-BS wants to transmit to the C-BS. } Edward S. Zhang, Huawei Technologies

January 2007 BSS-RSP This message is sent by B-CPE in response to a BSS-REQ and serves to confirm the receipt of the BSS-REQ message. Syntax Size Notes BSS-RSP_Message_Format(){ Management Message Type = 61 8 bits Transition ID 16 bits Confirmation Code Table 82 } Edward S. Zhang, Huawei Technologies

January 2007 BSS-REP This message is sent by B-CPE to S-BS after communicating with C-BS. It may contain the feedback the C-BS wants to transmit to S-BS. This feedback, if any, is encapsulated into the field of Report. Syntax Size Notes BSS-REP_Message_Format(){ Management Message Type = 62 8 bits Transition ID 16 bits Length Report variable The format of this field is vendor-dependent. } Edward S. Zhang, Huawei Technologies

January 2007 BSS-ACK This message is sent by S-BS in response to a received BSS-REP. Syntax Size Notes BSS-RSP_Message_Format(){ Management Message Type = 63 8 bits Transition ID 16 bits Confirmation Code Table 82 } Edward S. Zhang, Huawei Technologies