1. Text Proposal for E-MBS MAP Configuration Update (16.9.3.1) Document Number: IEEE C802.16m-09/2918 Date Submitted: 2009-12-31 Source: Chun-Yuan Chiu, Chun-Yen Wang, Yan-Xiu Zheng, E-mail:{ccy, ChunYen, zhengyanxiu, frank_ren} Fang-Ching (Frank) Ren @itri.org.tw ITRI Wern-Ho Sheen whsheen@itri.org.tw Chaoyang University of Technology / ITRI Information and Communications Research Laboratories, 195 Chung Hsing Rd., Sec.4 Chu Tung, Hsin Chu, Taiwan 310, R.O.C. * http://standards.ieee.org/faqs/affiliationFAQ.html Re: IEEE 802.16-09/0073, “IEEE 802.16 Working Group Letter Ballot#30b”, Target topic: “IEEE P802.16m/D3, section 16.9.3.1”. Venue: IEEE Session#65, San-Diego Purpose: To be discussed and adopted by TGm for 802.16m LB#30b. 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. E-MBS MAP Configuration In IEEE P802.16m/D3: –The information regarding E-MBS configuration is transmitted periodically using a MAC management message called the AAI_E-MBS-CFG message. –AAI_E-MBS-CFG includes: E-MBS-Zone_ID, MSI Length, E-MBS MAP resource Index, E-MBS MAP I sizeoffset …

3. No Method for E-MBS MAP Configuration Updating When an AMS requests to receive an E-MBS service or transits from an E- MBS Zone to another E-MBS Zone, the AMS needs to: –Obtain the new E-MBS Zone ID –Receive AAI_E-MBS-CFG and use E-MBS Zone ID to find E-MBS MAP –Receive E-MBS MAP and find the data of the desired E-MBS service –Receive the E-MBS MAP of the next MSI by MSI Length –… No method for the case of E-MBS MAP configuration updating!

4. Proposed Solution Add a 1-bit Change Indicator in E-MBS MAP: –If the Change Indicator is set to ‘1’, it implies the configuration of E- MBS MAP in next MSI will change –If the Change Indicator is set to ‘1’, an extended filed shall be concatenated after E-MBS MAP to specify the new configuration of E- MBS MAP in next MSI –The extended filed of E-MBS MAP is decoded separately from E-MBS MAP (the size of extended filed is predictable) enable MSI MAP MSI MAP MSI MAP MSI new MAP MSI MAP AAI_E-MBS-CFG Change Indicator extended filed

5. The Reason of Our Proposal (1/2) Why do we need Change Indicator in E-MBS MAP ? –An ABS may belong to multiple E-MBS Zones. –The configuration of E-MBS MAP change is a zone-specific event. –So we need one indicator for one E-MBS zone. MSI MAP MSI MAP MSI new MAP MSI MAP AAI_E-MBS-CFG zone1 MSI MAP MSI MAP zone2 When the configuration of E-MBS MAP of Zone 1 changes, the AMSs which do not receive E-MBS services of Zone do not update the configuration of E-MBS MAP.

6. The Reason of Our Proposal (2/2) Why do we not specify the new configuration in AAI_E-MBS- CFG ? –In general, the periodicity of AAI_E-MBS-CFG is longer than MSI MSI: 40ms, 80ms, 160ms, or 320ms The periodicity of AAI_E-MBS-CFG depends on the requirements of service initial time and zone transition time. –We may need one “offset” to specify when the new configuration will be valid if we specify the new configuration in AAI_E-MBS-CFG MSI MAP MSI MAP MSI new MAP MSI MAP AAI_E-MBS-CFG zone1

7. Proposed Text (1/2) Modify Table 798: SyntaxSize in bits Description/Notes E-MBS-MAP () {-- E-MBS_DATA_IE()-- E-MBS MAP Configuration Change Indication 1 0b0: E-MBS MAP Configuration in next MSI does not change 0b1: E-MBS MAP Configuration in next MSI is going to change, and an extended E-MBS MAP is concatenated after E-MBS MAP to specify the new configuration E-MBS_DATA_IE()-- } PaddingvariablePadding to reach byte boundary

8. Proposed Text (1/2) Add an new Table xxx: SyntaxSize in bits Description/Notes Extended E-MBS-MAP () {-- E-MBS MAP Resource Index[TBD] Resource index includes location and allocation size ReservedTBD- }