1. Downlink Control Design for 16m Hierarchical Frame Structure Document Number: S802.16m-08/134 Date Submitted: March 10, 2008 Source: Ming-Hung Tao (mhtao@itri.org.tw) Mamadou Kone (itri404759@itri.org.tw) Ying-Chuan Hsiao (ychsiao@itri.org.tw) Richard Li (itri404759@itri.org.tw) ITRI Venue: Orlando, USA Base Contribution: IEEE C802.16m-08/134r1 Purpose: For discussion and approval by TGm. 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 S802.16m-08/134

2. Scope This contribution proposes a downlink control design for IEEE 802.16m frame structure. The proposed design tries to minimize the control overhead. The proposed design may also facilitate other functions such as synchronization, power saving, and handover, which are FFS.

3. Super-MAP and Sub-MAP Super-frame #1Super-frame #2Super-frame #1 #1#2#3#4#5#6#7#8#9#10#11#12#13#14#15#16#29#30#31#32 ….. Data Super-MAP Sub-frame New Preamble SFCH Super-MAP Sub-MAP Data 16m DL Sub-frame Sub-MAP Data 16e DL Sub-frame Legacy Preamble FCH DL MAP Data High Mobility Sub-frame Sub-MAP Data Ranging 16m/e UL Sub-frame 20 ms 5 ms 0.617 ms Switching point

4. Super-MAP Design Concept To state the system and synchronization information. To describe the Sub-MAP information. To indicate the usage and properties of each Sub-frame by assigning a Sub-frame Usage Code (SUC). SUC could be one of the following: –16m Short-distance DL Sub-frame –16m Mid-distance DL Sub-frame –16m Long-distance DL Sub-frame –16m UL Sub-frame –16e DL Sub-frame –16e UL Sub-frame –DCD/UCD Sub-frame –High mobility Sub-frame –Relay Sub-frame –Ad hoc Sub-frame –E-MBS Sub-frame

5. Super-MAP Design SyntaxSize (bits)Notes Super-MAP_message_format() {-- Management Message TypeTBD- PHY Synchronization FieldVariable- DCD Count8- Base Station ID48- No. Sub-framesTBDNumber of Sub-frames. Sub-frame LengthTBDNumber of OFDMA symbols in a Sub- frame. for (i=0; i<No. Sub-frames; i++) {-- SUC4Sub-frame usage code. }-- No. Sub-MAPsTBDNumber of Sub-MAPs. for (i=0; i<No. Sub-MAPs; i++) {-- Sub-MAP_Info()Variable- }-- if !(byte boundary) {-- Padding Nibble4Padding to reach byte boundary. }-- }-- System Information Sub-frame configuration Sub-MAP indication

6. Super-MAP Design (cont.) SyntaxSize (bits)Notes Sub-MAP_Info() { -- FEC Code and Modulation Type6The FEC code and modulation type used by a Sub-MAP. Repetition_Coding_Indication2- MAP_PositionTBDIndicate which Sub-frame the Sub- MAP is located at. No. Sub-frames_Under_Control3Number of Sub-frames controlled by the Sub-MAP. for (i=0; i<No. Sub-frames_Under_Contro; i++) {-- Sub-frame_Sequence_No.TBDThe sequence number of the Sub- frame controlled by this Sub-MAP. }-- Sub-MAP_Length8- }-- The FCH before each Sub-MAP is contained by Sub-MAP_Info()

7. SUC Profile Concept SyntaxSize (bits)Notes Super-MAP_message_format() {-- Management Message TypeTBD- PHY Synchronization FieldVariable- DCD Count8- Base Station ID48- No. Sub-framesTBDNumber of Sub-frames. Sub-frame LengthTBDNumber of OFDMA symbols in a Sub-frame. for (i=0; i<No. Sub-frames; i++) {-- SUC4Sub-frame usage code. }-- No. Sub-MAPsTBDNumber of Sub-MAPs. for (i=0; i<No. Sub-MAPs; i++) {-- Sub-MAP_Info()Variable- }-- if !(byte boundary) {-- Padding Nibble4Padding to reach byte boundary. }-- SUC_Profile

8. SUC Profile SeeeeUUUmeeeUUUmeeU ….. SUC Profile = 1 : Legacy support profile (32 Sub-frames) e SUC Profile = 2 : E-MBS profile (32 Sub-frames) SMMMMMU ….. UMMMMMMUMM SUC Profile = 3 : High mobility profile (32 Sub-frames) Smmm M Legacy frame HHUU HHUU U ….. MM SUC Profile = 4 : Relay support profile (32 Sub-frames) SmmmRRUU mmm RRUUm mm m ….. R S SuperMAP Sub-frame e 16e DL Sub-frame U Uplink Sub-frame M E-MBS Sub-frame m 16m DL Sub-frame H High-mobility Sub-frame R Relay Sub-frame mmm m mmm

9. Super-MAP with SUC Profile SyntaxSize (bits)Notes Super-MAP_message_format() {-- Management Message TypeTBD- PHY Synchronization FieldVariable- DCD Count8- Base Station ID48- Available_Profile1 Available_Profile (1 bit) indicates whether SUC_Profile is available or not. If (Available_Profile == 1) {- - SUC_ProfileTBDPredefined combinations of different Sub-frame configurations and SUCs. } else {-- No. Sub-framesTBDNumber of Sub-frames. Sub-frame LengthTBDNumber of OFDMA symbols in a Sub-frame. for (i=0; i<No. Sub-frames; i++) {-- SUC4Sub-frame usage code. }-- } No. Sub-MAPsTBDNumber of Sub-MAPs. for (i=0; i<No. Sub-MAPs; i++) {-- Sub-MAP_Info()VariableSee Table 2. }-- if !(byte boundary) {-- Padding Nibble4Padding to reach byte boundary. }-- }--

10. Embed SUC Profile in DCD NameType (1 byte)LengthValue (variable length) Downlink_Burst_Profile1variableMay appear more than once. BS EIRP22Signed in units of 1 dBM. ………… ………… SUC Profile MappingTBD-Describes the mapping between SUC profiles and the predefined configurations. May appear more than once. SyntaxSize (bit)Note SUC Profile Mapping {-- Type = TBD8 Length8 SUC_Profile4 TLV_Encoded_Information80 = Default profile 1 = Legacy support profile 2 = 16m Short-distance profile 3 = 16m Mid-distance profile 4 = 16m Long-distance profile 5 = High mobility profile 8 = E-MBS profile 9 = Relay support profile 10 = Coexistence profile 11…255 = Reserved }

11. Benefits from SUC Profile Reduce the overhead for Super-MAP. Facilitate mobile stations to select targeted base stations during network entry or handoff procedures. May facilitate the synchronization between base stations, FFS.

12. Proposed Text (see contribution C80216m-08_134r1)

17. References [1] IEEE 802.16m-07/002r4, “IEEE 802.16m System Requirements”, October 2007. [2] IEEE C802.16m-08/118r1, “Proposed 802.16m Frame Structure Baseline Content suitable for use in the 802.16m SDD”, February 2008. [3] IEEE C80216m-07/320r1, “Draft Table of Content for the IEEE 802.16m System Description Document”, November 2007.