1. DL/UL data transmission for M2M devices IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16p-10/0020 Date Submitted: 2010-12-30 Source: Jeongki Kim, Jin Lee, Giwon Park, Youngsoo Yuk, Kiseon Ryu,Email: {jeongki.kim, jin1.lee} @lge.com Jinsam Kwak LG Electronics Re: 80216p-10_0009: Call for Contributions on Project 802.16p Amendment Working Document Content Venue: IEEE Session #71 Base Contribution: N/A Purpose: To be discussed and adopted by TGp. 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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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. Introduction & motivation In most M2M applications such as smart metering DL traffic happens as a type of multicast transmission (e.g., software/firmware update) and UL traffic happens as a type of short burst transmission (e.g., periodic reporting) * Use case : Smart metering

3. Introduction & motivation DL data transmission The application (e.g., firmware, software, etc.) update procedure for M2M devices will be usually performed remotely because most M2M devices are not always carried by M2M subscriber In this case the application update data had better be transmitted by multicast method rather than the unicast method in terms of resource efficiency Paging and DL traffic reception in idle mode in 16-2009/16m To reduce power consumption of M2M devices and access congestion M2M devices in idle mode should be able to receive the DL data without the network reentry procedure To receive DL traffic addressed to MS in idle mode, it has to perform network re-entry.

4. Introduction & motivation UL data transmission If a M2M device usually generates the short size UL data and sends the data, it may be not efficient for the M2M device in idle mode to send the UL data after the network re-entry For AMSs in legacy system the efficient method to sends the short message service is defined For UL short message an AMS in idle mode sends the data via RNG-REQ message during location update procedure without network reentry For low power consumption of M2M devices M2M devices in idle mode should be able to send the UL data without the network reentry procedure similar to legacy system

5. Multicast transmission for M2M devices in Idle mode Multicast traffic notification When an ABS (or paging controller) receives the multicast data belonging to a M2M multicast group (e.g., subscriber), the ABS (or paging controller) will inform M2M devices of it The M2M devices belongs to the multicast group (or subscriber) The notification is delivered during the paging listening interval of M2M devices (e.g., Group paging method indicating no network reentry) DL traffic reception without network reentry When a M2M device in idle mode receives the multicast data notification (e.g., Group paging w/o network reentry), the M2M device monitors the DL channels until the AMS receives the designated DL data without network reentry

6. UL short data transmission When a M2M device is in idle mode, if short UL data happens, the M2M device can sends the UL data without the network reentry procedure

7. Proposed text [Suggested Remedy : Add the new Section in the 16p amendment document as follows:] 16.2.29.x Support of M2M multicast service 18.2.29.x.1 Multicast operation in idle mode When an ABS receives the multicast data from network, the ABS informs the M2M devices in idle mode belonging to the multicast group of the multicast traffic existence during the paging listening intervals of the M2M devices. When an M2M device in idle mode receives the multicast traffic notification (i.e., Group paging indicating no network reentry) during its paging listening interval, the M2M device monitors the downlink channels without performing network reentry procedure until the device receives the multicast data for the group which the M2M device belongs to. 16.2.29.y Support of M2M short packet transmission 16.2.29.y.1 Short packet transmission in idle mode When a M2M device is in idle mode, if short UL data happens, the M2M device will send the UL data without the network reentry procedure