1 Consideration on the Update Procedure of the System Information for M2M IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C80216p-10/0023r1 Date Submitted: Source: Jinsoo Choi, HanGyu Cho, Kiseon Ryu, Jin Sam Kwak LG Electronics Re: For ToC of “802.16p amendment text” Purpose: To be discussed and adopted in ToC for p amendment text 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.

Outline  Introduction  Investigation based on the Advanced Air Interface system  Current update procedure of AAI-SCD message  Consideration on applying update procedure to M2M  Investigation based on the WirelessMAN-OFDMA system  Current update procedure of DCD/UCD message  Consideration on applying update procedure to M2M  Proposed text

Introduction  System configuration information should be informed and updated to AMSs(/MSs) safely for correct system operation.  For supporting this, followings are inevitable  Sufficient time-frequency resources for robust transmission  Well scheduled procedure for assuring the correct update  For M2M requirement of low power consumption  It is need to take care of whether existing informing/update procedure of the system configuration information can be reused or need to be enhanced to support M2M devices with low power consumption.  It should avoid any critical impact on the existing system.  In this contribution, followings are provided  Existing update procedures of the system configuration information based on the Advanced Air Interface system and the WirelessMAN- OFDMA system  Recommended approaches for efficient support for M2M 3

Investigation based on the Advanced Air Interface system 4  Current update procedure of AAI-SCD message  Update procedure  The AAI-SCD message is updated based on following system configuration parameters - Configuration change count (CCC) in AAI-SCD message - SCD count in S-SFH SP3  AMS compares values among SCD counts b/w the previous and new ones and knows when the updated system information should be applied. Apply updated information Compare values

Investigation based on the Advanced Air Interface system (cont’d)  In fail to acquire the updated information  Except some critical parameters such as periodic ranging and sounding allocation information, AMSs can maintain most operations even in case of fail to get the updated information.  About above critical parameters, to avoid preventing other AMS’s correct operation, the standard let the related operation stop until the next successful acquisition.  Consideration on applying update procedure to M2M  Assurance of reliable transmission and update  In Advanced Air Interface system, because we define the update procedure for AAI- SCD message based on SCD count conveyed in S-SFH SP3 that is accurately transmitted with a reference cycle applied by S-SFH update procedure, AMSs can know the exact transmission and applying time of the updated system information. In addition, even in case of fail to acquire the updated information, the AMSs can know which system operations they should stop to prevent impact on other AMSs.  Recommendations  In Advanced Air Interface system, it seems that we can maintain applying the current update procedure of system information to M2M service.  It’s FFS whether all the system information in AAI-SCD message is required or not to M2M support. Some compact message for system information transmission/update to M2M devices could be considered later if needed. 5

Investigation based on the WirelessMAN-OFDMA system  Current update procedure of DCD/UCD message  The DCD/UCD is updated based on following system configuration parameters  DCD/UCD count in MAP  Configuration change count in DCD/UCD 6 First transmission E.g. Update procedure of UCD

Investigation based on the WirelessMAN-OFDMA system (cont’d) 7 Waiting time for applying updated information Second transmission

Investigation based on the WirelessMAN-OFDMA system (cont’d)  Consideration on applying update procedure to M2M  Problem on current update procedure  As presented in previous slides, in case of Advanced Air Interface system, we define the update procedure for AAI-SCD message based on exact reference cycle by S- SFH update procedure.  Thus there is no ambiguity for AMSs to know the exact transmission and applying time of the updated system information. Even in case of fail to acquire the updated information, there is an assurance to prevent critical impact the system.  However, in the update procedure of DCD/UCD in WirelessMAN-OFDMA system, there is no fixed reference cycle so MSs should get the some control IE to catch the updated message when they miss the time of message transmission after some unavailable duration for power saving - M2M devices can have various operation cycles, i.e. various available/unavailable intervals based on different applications (e.g. some application would require very long unavailable interval for power saving) so it is difficult for ABS to schedule and indicate all DCD/UCD transmissions for successful update of each M2M device. - Even if M2M devices get the control IE to indicate the DCD/UCD transmission, they shall continue decoding all subsequent frames until acquiring the updated DCD/UCD message if they fail to decode DCD/UCD or no DCD/UCD was transmitted by the BS. 8

Investigation based on the WirelessMAN-OFDMA system (cont’d)  Recommendations  The update procedure of DCD/UCD message should be enhanced considering power-efficient M2M support. The approach should not affect on the existing system/operation, thus followings are recommended. - Procedure/transmission enhancement with no critical impact/modification of the existing operation. - Power-efficient response procedure by M2M devices to acquire the updated information. 9 Figure 1: Exemplary update procedure of UCD For example, assuming sleep or some unavailable interval existing for power saving, when DCD/UCD transmission periodicity was changed or M2M devices have some difficulty to catch the updated DCD/UCD transmission, the devices should maintain to try to decode MAPs until acquiring the updated message. If these devices require very long unavailable interval and should wake up in short duration, this kind of situation will be a burden in power utilization.

Proposed text Start of the proposed text Inserts new subsections to address M2M support in the p amendment document as following MAC Support of M2M Application x Update procedure of DCD/UCD message for M2M application x.1 The DCD/UCD transmission for M2M devices x.2 The response procedure by M2M devices End of the proposed text