IEEE C802.16ppc-10/0050
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Text Changes to IEEE 802.16p Machine to Machine (M2M) System
Requirements Document (SRD) (initial working document)
Date
Submitted
2010-08-25
Source(s)
Jin Lee
E-mail: jin1.lee@lge.com
Youngsoo Yuk
HanGyu Cho
Kyujin Park
JinSam Kwak
Kiseon Ryu
LG Electronics
Re:
Abstract
Initial IEEE 802.16p Machine to Machine (M2M) System Requirements Document
Purpose
Initial M2M System Requirements working document to enable capturing the requirements for
the prospective IEEE 802.16p Amendment.
Notice
Release
Patent
Policy
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.
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.
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
<http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and
<http://standards.ieee.org/board/pat>.
1
IEEE C802.16ppc-10/0050
Machine to Machine (M2M) System Requirements Document
1
Overview ..........................................................................................................................3
2
References ........................................................................................................................3
3
Definitions........................................................................................................................3
4
Abbreviations and Acronyms ..........................................................................................3
5
General Requirements ......................................................................................................3
5.1
Compatibility with other 802.16 equipment ........................................................3
5.2
Complexity...........................................................................................................4
5.3
M2M Services ......................................................................................................4
5.4
802.16p M2M Reference System Architecture ...................................................4
6
Functional Requirements .................................................................................................5
6.1
Low Power Consumption ....................................................................................5
6.2
Large Numbers of Devices ..................................................................................5
6.3
Small Burst Transmissions ..................................................................................6
6.4
Security Support...................................................................................................6
2
IEEE C802.16ppc-10/0050
1 Overview
The 802.16p amendment shall be developed in accordance with the Machine to Machine (M2M)
communication project authorization request (PAR) form and five criteria the approved version of IEEE
802.16ppc-10/0003r7 [1].
This document represents the initial high-level system requirements for the 802.16p amendment.
2 References
[1] IEEE 802.16ppc-10/0003r7: Machine to Machine (M2M) Communication PAR Form and Five Criteria
(Not approved yet).
[2] IEEE Std 802.16-2009: IEEE Standard for Local and metropolitan area networks – Part 16: Air Interface
for Fixed Broadband Wireless Access Systems, May 2009.
[3] IEEE P802.16m: IEEE Standard for Local and metropolitan area networks – Part 16: Air Interface for
Fixed and Mobile Broadband Wireless Access Systems
[4] IEEE 802.16ppc-10/0002r7: Machine to Machine (M2M) Communication Study Report.
[5]IEEE P802.16m System Requirements Document (SRD)
3 Definitions
Terms
Description
Embedded device with wireless WAN connectivity
M2M device
M2M gateway [Note. Need
to be clarified or deleted]
Machine-to-Machine (M2M) This is information exchange between devices (subscriber station)
through a base station, or between a device and a server in the core
network through a Base Station that may be carried out without any
human interaction.
4 Abbreviations and Acronyms
M2M
Machine to Machine
5 General Requirements
5.1 Compatibility with other 802.16 equipment
IEEE 802.16p BS provides continuing support for WirelessMAN-Advanced Air Interface and legacy
WirelessMAN-OFDMA R1 Reference System equipment. IEEE 802.16p system shall not degrade the
performance of the WirelessMAN-Advanced Air Interface and WirelessMAN-OFDMA R1 Reference System
equipment and additional complexity shall be minimized to the operation of WirelessMAN-Advanced Air
Interface and WirelessMAN-OFDMA R1 Reference System equipment.
3
IEEE C802.16ppc-10/0050
5.2 Complexity
IEEE 802.16p provides IEEE Std 802.16 medium access control (MAC) enhancements and minimal
OFDMA PHY modifications to provide functionalities for efficient Machine to Machine communication.
5.3 M2M Services
IEEE 802.16p shall efficiently maintain connectivity for a large number of M2M devices. IEEE 802.16p
shall support different quality of service (QoS) levels, which are more diversified than those of WirelessMANAdvanced Air Interface and WirelessMAN-OFDMA R1 Reference System equipment. It shall be possible to
subscribe to different M2M requirements or features independently according to the application or network
environment.
5.3.1 Smart Grid [Note. Move to Annex section]
5.3.2 Vehicular
5.3.3 Consumer devices
5.3.2 Health
5.4 802.16p M2M Reference System Architecture
MNO (Mobile Network Operator)
Access Service
Network
IEEE 802.16
Non M2M
device
IEEE 802.16
M2M device
Non IEEE
802.16
M2M device
IEEE 802.16
M2M device
Connectivity
Service Network
R1
M2M
Server
R1
IEEE 802.16
BS
R1
(a) 802.16p M2M service reference system architecture
4
M2M
Service
Consumer
IEEE C802.16ppc-10/0050
6 Functional Requirements
6.1 Low Power Consumption
The 802.16p system specification should shall support mechanisms for low power consumption in
M2M devices.
6.1.1 The 802.16p system should shall support power saving over long time intervals.
6.1.2 The protocol should support reduced mobility signaling for stationary M2M devices to conserve
power
6.1.3 The 802.16p system shall simplify or optimize the mobility-related operations for specific M2M
applications with no/low mobility,
6.1.4 The M2M devices that have batteries, which are infrequently recharged or replaced should be
supported
6.1.5 The amendment 802.16p system shall support signaling for time controlled, time-tolerant and
in-frequent traffic to conserve power
6.2 Large Numbers of Devices
The 802.16p amendment should shall support very large numbers of devices.
5
IEEE C802.16ppc-10/0050
6.2.1 The protocol should shall be able to address large number of devices individually or by group.
6.2.2 The protocol should shall support group management for large numbers of M2M devices
dispersed over a large area.
6.2.3 The group can consist of M2M devices belonging to the same M2M service consumer.
6.2.4 The 802.16p system should shall support network access from large numbers of M2M devices.
6.2.5 The 802.16p system should shall provide priority access for M2M devices across different
classes of M2M services.
6.2.6 The 802.16p amendment should shall support large numbers of M2M devices in connected
state as well as in idle state.
6.2.7 The 802.16p system should shall support QoS for diversified M2M services [Note: We would
like someone to clarify this sentence.].
6.2.8 The 802.16p system shall reduce the control overhead for state transition (i.e. from/to idle state
to/from active state) for large numbers of M2M devices.
6.3 Small Burst Transmissions
The standard should shall support very small burst transmissions.
6.3.1 The 802.16p amendment should shall support efficient transmission of small burst sizes.
6.4 Security Support
6.4.1 The 802.16p should shall support the M2M device authentication.
6.4.2 The 802.16p should shall support verification and validation of the exchanged data for M2M
services.
6.4.3 The protocol should shall support efficient security for small burst transmissions.
6.4.4 The 802.16p shall support location privacy for M2M devices.
Annex A
A.1 Usage scenario of M2M Services
6
IEEE C802.16ppc-10/0050
A.1.1 Smart Grid
A.1.1.1 Smart metering
Smart metering (e.g., Smart Grid) services meter gas, electricity, or water and bill the metered resource
without human intervention. Smart metering not only enables remote meter reading (saving the company, and in
turn, the customer money) but also improves the customer’s energy/utility efficiency (e.g. by regulating home
appliance usage according to gas/electricity’s time-varying unit price).
WAN M2M system should support following features for this service.
 Low/No Mobility
The required functionality for low/no mobility is a reduction in resource usage for low/no mobility
M2M Devices (e.g., paging, location management signaling, and mobility context in M2M server).
 Time-Controlled Operation
The network shall communicate in the pre-defined time interval to the M2M Device. To avoid
network overload, signaling and data traffic of the devices shall be distributed over the pre-defined
time period.
 Small burst transmission
 Large number of devices
A.1.2 Tracking & Tracing
“Tracking, Tracing” use cases is mainly related to services that rely on location-tracking information. For
example, in order to provide vehicular tracking services such as navigation, traffic information, road tolling,
automatic emergency call, pay as you drive, etc., the M2M application server needs to monitor the status and/or
position of an individual vehicle or group of vehicles. In this use case, vehicles are equipped with M2M devices
that send status information (e.g. location, velocity, local traffic, etc.) periodically or on-demand to the M2M
server via the cellular network. By analyzing the information gathered from vehicular M2M devices, the M2M
server generates data about traffic, navigation, etc. and provides that information to M2M service consumer via
the cellular network.
WAN M2M system should support following features for this service.
 Security
 Access priority
A.1.3 Health
WAN M2M healthcare applications improve patient monitoring/tracking and doctor responsiveness. M2M
services allow patients with advanced age, chronic disease, or complicated physical conditions to live
independently. They also improve patient care by virtue of more accurate and faster reporting of changes in
physical condition.
WAN M2M system should support following features for this service.
 High Reliability
High reliability implies that whenever and wherever M2M communication is required or triggered,
the connection and reliable transmission (i.e. extremely low packet error rate) between the M2M
device and the M2M server shall be guaranteed regardless of operating environment (e.g., mobility,
channel quality). To enable consistently good connectivity, the WAN M2M system shall provide the
methods of improving reliability.
 Security
WAN M2M system should support appropriate level of authentication for the M2M device to
provide secure access to the authorized M2M devices. The system should support verification and
7
IEEE C802.16ppc-10/0050
validation of the exchanged data.
 Enhanced Access Priority
Enhanced access priority implies that the M2M device is given priority over other network nodes
when contending for network access. Priority access is necessary in order to communicate alarms,
emergency situations or any other device states that require immediate attention.
8