Presentation on theme: "-1- Management for M2M Devices [IEEE 802.16 Presentation Submission Template (Rev. 9.2)] Document Number: IEEE C802.16p-10/0039 Date Submitted: 2011-01-07."— Presentation transcript:
-1- Management for M2M Devices [IEEE 802.16 Presentation Submission Template (Rev. 9.2)] Document Number: IEEE C802.16p-10/0039 Date Submitted: 2011-01-07 Source: Yu-Chuan Fang, Zheng Yan-Xiu E-mail: YCFang@itri.org.twYCFang@itri.org.tw ITRI Re: 80216p-10_0009: Call for Contributions on Project 802.16p Amendment Working Document Content 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. 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..html#6sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat
-2- Background Three types of communications Machine to Machine (M2M) communication Human to Human (H2H) communication Human to Machine (H2M) communication M2M features Large number of devices Extreme fast response time than human Unexpected large amount of devices may access the network M2M devices may have different priority in accessing network, e.g. smart meter with lower priority Time tolerance may be feasible for M2M devices 2
-3- 3 Motivation (1/2) M2M communications require management mechanisms to regulate initial network entry or bandwidth request Large number of M2M devices may access network at the same time Concurrent network accesses cause collision if the amount is significant large M2M devices will retry concurrently and cause traffic congestion Dead lock may occur and crash the network Human communications will encounter unnecessary traffic congestion and can not access the network User experience degrades M2M devices must be regulated in case of interfering human communications
-4- 4 Motivation (2/2) M2M devices shall be distinguished with human communications M2M devices could be supported with different priorities Smart meter can be served with lower priority Lower priority, Larger back-off window size M2M devices should avoid degrading the performance of human communications Exclusive ranging opportunity may be temporarily introduced Appropriate configuration and control commands may be only for M2M devices
-5- 5 Proposal 1: Regulation Command To manage M2M devices through multicast message The BS transmits control message to command or configure a group of devices such as: STOP: The BS can stop M2M devices sending signal to BS, e.g. ranging, bandwidth request, scheduling request, etc. CHANGE: The BS can change some parameters to adjust and organize M2M devices temporarily or specifically, e.g. ranging backoff window, ranging opportunities, location for random access, etc. Ranging backoff to increase the ranging opportunity and avoid congestion Allocation periodicity and subframe offset of the ranging channel to provide ranging opportunity for high prior or specific devices TERMINATE: The BS can terminate the existing command, e.g. STOP or CHANGE. TERMINATE may imply return to system configuration.
-6- Proposal 2: Exclusive Resource Allocation The resource allocated to M2M devices should be different to human communication. The existing ranging opportunities may be not enough for large numbers of devices. Additional ranging opportunities may be increased for specific group with priority or for congestion resolution. The BS may reuse existing message format for M2M but M2M devices may not send ranging on the opportunities which has been allocated to human communication. 6
-7- Proposed Text 1 3 M2M air interface 3.3Medium access control (MAC) layer 3.3.3 Support of management message of large number of devices 18.104.22.168 Group resource management The BS may manage M2M devices through multicast message. The BS can transmit regulation message to command or configure a group of devices temporarily or specifically. The regulation message can stop ranging for M2M devices. The regulation message can reconfigure the ranging parameters for M2M devices. The regulation message can terminate the configured message different to system configuration.
-8- Proposed Text 2 3 M2M air interface 3.3Medium access control (MAC) layer 3.3.3 Support of management message of large number of devices 22.214.171.124Network entry and initialization The BS may interleave M2M communication with existing AMSs or MSs. Additional ranging opportunities may be allocated for specific group with priority or for congestion resolution. However, in some cases, M2M devices may not send ranging on the opportunities which has been allocated to human communication to avoid interfering human communication.
-9- 999 References  IEEE 802.16p-10/0004r1, IEEE 802.16p Machine to Machine (M2M) System Requirements Document (SRD).  IEEE P802.16m/D10, Draft Amendment to IEEE Standard for Local and Metropolitan Area NetworksPart 16: Air Interface for Broadband Wireless Access Systems, Nov. 2010.  IEEE 802.16p-10/0031, Table of Contents for IEEE 802.16p Amendment Working Document.