1. IEEE C80216m-08/828r1 1 Grouping broadcasting Information into deployment wide and sector specific Document Number: IEEE C80216m-08/828r1 Date Submitted: 2008-07-11 Source: Xiaoyi Wang, Shashikant Maheshwari Yousuf Saifullah Nokia Siemens Networks E-mail: xiaoyi.wang@nsn.comxiaoyi.wang@nsn.com Andrea Bacioccola Zexian Li Nokia Heping Li Dongjie, No.11 Beijing, China Venue: IEEE 802.16m-08/024: Reply to SDD comments. Base Contribution: N/A Purpose: Discussion and approval by TGm for the 802.16m SDD Notice: This document does not represent the agreed views of the IEEE 802.16 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 802.16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2. IEEE C80216m-08/828r1 2 Introduction In the comments database to current SDD, (802.16m-08/025), there are several comments against to classifying broadcast information into deployment wide common and sector specified, comment #237,238,239. Classifying broadcast information into deployment wide common and sector specified is based on DL ctrl RG report in last meeting. (802.16m-08/297r1). PBCH is designed for deployment wide common messages to obtain macro diversity and higher spectrum efficiency.

3. IEEE C80216m-08/828r1 3 Possible deployment wide common messages For deployment wide messages, since the information are common among neighboring BSs, we can use frequency reuse=1 for transmisssion. Besides higher spectrum efficiency, cell edge user obtains diversity on PBCH reception. Here is a list of possible deployment wide common messages. –CP length 2 bits –DL/UL 3 bits –TTG 16 bits –RTG 8 bits –OperatorID 24 bits –Switching point number 2 bits –System Bandwidth 3 bits –Super frame number 12/24 bits –Mac Version 8 bits –paging Group 16 bits –Cell Type 2 bits –Nsp ID 16 bits or even more –Burst Profile 8 bits –UL frequency(FDD only) 8 bits –UL/DL PHY mode 8bits (including FFT size, etc.) –Totally : 134 bits or more. These messages are normally common in deployment wide areas. If we don't group them out, and transmit in PBCH, then we have to use FR=3 for transmission at each sector. So the resource consumption is: 134*3*4/88=~18 RB. (one RB is consist of 88 tones for data, QPSK1/2, 4 repetitaion, FR=3) If we group those common message and transmit at PBCH, then the resource consumption is: 134*4/88=~6 RBs Considering in 5Mhz, we only have 24 RBs altogether, such gain is remarkable.

4. IEEE C80216m-08/828r1 4 Grouping Broadcast Information into deployment wide common and sector specific messages

5. IEEE C80216m-08/828r1 5 Pros and conclusion Cell edge MS could combine the signal from multiple BSs to decode the deployment wide common information (macro diversity) Less frequency resources are used for deployment wide common information. (FR=1 rather than 3) To conclude, grouping the broadcasting information brings obvious gain, and should be adopted by SDD.