1. Operational states for M2M device
Document Number: IEEE C802.16p-10_0027
Date Submitted:
December 31, 2010
Source:
Jin Lee,Youngsoo Yuk, Jeongki Kim, Giwon Park
Kiseon Ryu, JinSam Kwak
LG Electronics {jin1.lee, youngsoo.yuk,
*<
Re:
802.16p amendment texts
Base Contribution:
Purpose:
Discuss and adopt proposed texts
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.
Copyright Policy:
The contributor is familiar with the IEEE-SA Copyright Policy <
Patent Policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
< and <
Further information is located at < and < >.

2. Motivation In 802.16p SRD, the following requirements are agreed
The p system shall support longer inactive periods for increased power savings for M2M devices associated with certain M2M applications
The p system shall support optimized operation for time controlled, time tolerant and in-frequent traffic to conserve power.
The p system shall support large numbers of M2M devices in connected state as well as in idle state. Signaling shall be optimized for transitions between the two states.
A new operational state diagram needs to be considered based on the specific M2M device characteristics. Also, signaling for state transitions shall be optimized from large numbers of devices.

3. Background
Fig1. 16m MS State Transition Diagram
A new power saving state shall be considered for M2M devices producing in-frequent , time controlled traffic. Some M2M applications may only require a very short period of time to send/receive data . Also, access distribution for those devices shall be considered.
State transition shall be optimized between the existing state and the new power saving state .

4. Proposal Available Time Unavailable Time Connected State Idle State
Unavailable State
DL/UL available
DL traffic monitor (paging)
UL access available during paging available duration
Device context is kept in paging controller.
No DL traffic monitor (no paging)
UL access unavailable
Device context is kept in a network entity.
Table1. 16p device State
Unavailable State (UAS)
In order to avoid access congestion and distribute network load, M2M device shall not be allowed UL access.
Network allocates Unavailable Time Interval. Or, the Unavailable Time Interval can be negotiated between device and network for a certain M2M application.
Transition between Idle State and UAS can be triggered based on timer values.
For example, use Available Time , Unavailable Time.

5. Proposal State Transition
Fig2. 16p device operational states
State Transition
Initial Available time is started after completion of registration .
When Available timer expires, M2M devices transit to UAS and start Unavailable timer. Its context is kept in a network entity. M2M device should keep its DID used for Idle State.
When Unavailable timer expires, M2M devices transit to Idle State and start Available timer.
Unless Unavailable timer expires, M2M device shall not try access for data transmission and shall defer its access.

6. Proposed Texts
[Insert the following texts in 16p amendment document] :
MAC Support of M2M
Introduction
p device operational states
Unavailable Time Interval (UTI) : Interval of unavailable time that an M2M device is not allowed to access network. UTI is used for Unavailable State.
Available Time Interval (ATI) : Interval of available time that an M2M device is allowed to access network. It is valid during connected and idle states.
Unavailable State (UAS): When the M2M device is in Unavailable State, the M2M device is not permitted to send data and p BS should not schedule the device to receive data. State transition between idle state and unavailable state is based on expiration of (un)available time interval.

7. Proposed Texts
[Insert the entire figure in 16p amendment document as following] :
Fig x. 16p device operational states