IEEE C802.16p-11/0136r3
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
STID-Sharing Scheme for Addressing M2M Devices
Date
Submitted
2011-07-19
Source(s)
Ming-Hung Tao, Ying-Chuan Hsiao
E-mail: mhtao@itri.org.tw
ITRI
Lei Zhou, Anil Agiwal, Hyunjeong Kang
Samsung Electronics
Yi-Ting Lin, Chun-Yen Hsu, Chiu-Wen Chen,
Youn-Tai Lee
III
Jeongki Kim
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
LG Electronics
Shantidev Mohanty
Intel Corporation
Re:
[STDS-802-16] 802.16p (M2M) AWD Call for Comments
Abstract
This contribution proposes a new STID addressing scheme for M2M devices.
Purpose
To be discussed and agreed in IEEE 802.16p AWD.
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.16p-11/0136r3
STID-Sharing Scheme for Addressing M2M Devices
Ming-Hung Tao, Ying-Chuan Hsiao
ITRI
Lei Zhou, Anil Agiwal, Hyunjeong Kang
Samsung Electronics
Yi-Ting Lin, Chun-Yen Hsu, Chiu-Wen Chen, Youn-Tai Lee
III
Jeongki Kim
LG Electronics
Shantidev Mohanty
Intel Corporation
1 Introduction
As mentioned in current AWD, the STID is used to identify the M2M devices in the domain of the ABS.
However, the current addressing scheme associated with the 12-bit STID could make it very difficult to satisfy
the requirement of “Large Number of Devices” in IEEE 802.16p. Therefore, a new addressing scheme without
changing the length of STID is desired for IEEE 802.16p.
2 Time-Sharing STID Addressing Scheme
The base station can recognize a device as an M2M device through the capability negotiation process, and
assign the STID to the M2M device through the registration process. During the registration process, the base
station shall send the AAI-REG-RSP message including at least ‘STID’, ‘STID_Valid_Periodicity’, and
‘STID_Valid_Offset’ parameters to the M2M device message as the response to the AAI-REG-REQ message, as
shown in Figure 1. In case that the base station decides to assign a STID which is already assigned to or is going
to be assigned to other M2M devices, it shall assign a value which is larger than ‘1’ to STID_Valid_Periodicity;
otherwise, the base station shall assign the value ‘1’ to the STID_Valid_Periodicity. The base station shall
always assign a value which is smaller than STID_Valid_Periodicity to the STID_Valid_Offset. It should be
noticed that for the M2M devices sharing the same STID, their STID_Valid_Periodicity values shall be identical,
and their STID_Valid_Offset values shall be different from each other.
2
IEEE C802.16p-11/0136r3
M2M Device
Base Station
Capability
Negotiation
Key
Exchange
AAI-REG-REQ
AAI-REG-RSP
(STID, STID_Valid_Periodicity,
STID_Valid_Offset)
Figure 1. Message exchanges between the M2M device and the BS during the network entry procedure.
If a STID is shared by multiple M2M devices, each M2M device can only apply this STID as its device
identifier in certain time periods (frames), depending on its assigned STID_Valid_Periodicity and
STID_Valid_Offset values. To be more specific, the M2M device can apply the STID as its device identifier
whenever the following condition is met.
Framenum mod STID_Valid_Periodicity = STID_Valid_Offset,
(1)
where Framenum denotes the current frame sequence number of the system. The M2M device shall not use the
STID if condition (1) is not met.
To receive unicast downlink traffic, an M2M device will monitor the assigned STID at the frame where
the STID is valid for the M2M device according to condition (1). On the other hand, whenever the BS has
unicast downlink traffic pending for an M2M device, it shall allocate the traffic to the M2M device at the frame
where the STID is valid to the M2M device. If the BS is going to allocate an uplink transmission opportunity to
an M2M device, it shall also allocate the opportunity to the M2M device via STID at the frame where the STID
is valid for the M2M device.
If an M2M device needs more bandwidth for uplink transmission, according to the IEEE 802.16m
standard, it shall firstly signal a ranging code to request an uplink transmission opportunity for submitting its
bandwidth request message. After successfully decoding the ranging code, the BS will grant an uplink
transmission opportunity to the device signaling the ranging code; then the device can utilize the opportunity to
submit its bandwidth request message including the STID of the device and the size of the required bandwidth.
The bandwidth request message also includes a STID_Valid_Offset parameter so that the BS can know which
M2M device is requesting the bandwidth while the STID is shared by multiple M2M devices. After recognizing
which M2M device is requesting the bandwidth and how much bandwidth the device needs, the BS then grants
the corresponding uplink transmission opportunity to the M2M device at the frame where the STID is valid to
the M2M device. Figure 2 illustrates the example for the bandwidth request procedure.
3
IEEE C802.16p-11/0136r3
M2M Device
Base Station
(STID_Valid_Periodicity = 5,
STID_Valid_Offset = 1)
Ranging code
frame #10
Opportunity for BR
frame #11
BR message
(STID, BR size, STID_Valid_Offset)
.
.
.
Opportunity for uplink traffic
frame #16
Uplink traffic
(16 mod 5 =1)
Figure 2. Bandwidth request procedure for M2M device.
Whenever a BS receives a packet from an M2M device, it shall determine the STID_Valid_Periodicity
and STID_Valid_Offset of the device based on the STID and the current frame sequence number. Then if the BS
has any response to the received packet, it shall wait a time period equal to n * STID_Valid_Periodicity frames
and then transmits the response to the M2M device, where n > 0.
BS receives a packet from an M2M
device at frame #i, and determines the
STID_Valid_Periodicity and
STID_Valid_Offset of the M2M device.
If the BS has a response/ack to the received
packet, it shall wait
n*STID_Valid_Periodicity frames then send
the response to the M2M device (n>0).
generate response
BS
M2M
device
RSP
RSP
STID_Valid_Periodicity * n
Frame i + n *
STID_Valid_Periodicity
frame i frame i+1
Figure 3. BS transmits the response to the M2M device for the received packet.
The BS may be able to know the application type of an M2M device during or before the registration
process. Some M2M applications can tolerate long traffic delay while some M2M applications can allow only
very limited traffic delay. Therefore, the BS should assign the value of STID_Valid_Periodicity to an M2M
device according to device’s application type. The BS should assign a small STID_Valid_Periodicity to the
M2M device with delay-sensitive application and assign a large STID_Valid_Periodicity to the M2M device
with delay-tolerable application. Once the BS associates a STID with a STID_Valid_Periodicity value, the other
4
IEEE C802.16p-11/0136r3
M2M devices sharing the same STID will be assigned the same STID_Valid_Periodicity value. Since the
STID_Valid_Offset for each M2M device sharing the same STID shall be unique, we can say that the value of
STID_Valid_Periodicity represents the maximum number of M2M devices that can share the STID.
3 Text Proposal
Adopt the following text modifications (insert the blue text) to IEEE P802.16p AWD:
--------------------------
Begin Text Proposal
-------------------------------
[Remedy #1: Insert the following text to page 9, line 19]
16.2.1.2 Logical Identifiers
16.2.1.2.1 Station Identifier (STID)
The STID is used to identify the M2M devices in the domain of the ABS. The ABS may assign the same STID
to multiple M2M devices.
If the assigned STID to an M2M device is shared with other M2M device (s), the ABS shall assign the frame (s)
in which the STID is valid for an M2M device. The assigned STID to an M2M device is valid only in the frame
(i.e. Framenum) which satisfies the following condition.
Framenum mod STID_Valid_Periodicity = STID_Valid_Offset,
where Framenum denotes the frame sequence number. The parameters STID_Valid_Periodicity and
STID_Valid_Offset are transmitted by ABS in AAI-REG-RSP message. For the M2M devices sharing the same
STID, their STID_Valid_Periodicity values shall be identical, and their STID_Valid_Offset values shall be
unique.
[Remedy #2: Insert the following text to page 9, line 44]
16.2.2.1.3 MAC Signaling Header
Table 656—Type field encodings for MAC signaling header type
Type field (5-bits)
MAC Signaling Header Type
00000
BR with STID
00001
BR without STID
00010
Service Specific Scheduling Control
Header
00011
Sleep Control
00100
AMS Battery Level Report
00101
Uplink Power Status Report
00110
Correlation Matrix Feedback
00111
MIMO Feedback
01000
M2M Bandwidth Request (BR) with STID
Header
0100001001-11111
Reserved
5
IEEE C802.16p-11/0136r3
16.2.2.1.3.9 M2M Bandwidth Request (BR) with STID Header
When an M2M device requests bandwidth through an UL resource allocated by the CDMA Allocation A-MAP
IE, it shall transmit M2M BR with STID signaling header on the allocated UL resource. M2M BR format with
STID header is defined in Table xxx.
Table xxx—M2M BR with STID header format
Syntax
Size (bit)
Notes
BR with STID () {
FID
4
Flow Identifier. Set to 0010
Type
5
MAC signaling header type = 0b01000
Length
3
Indicates the length of the signaling header in
bytes.
BR Size
17
Aggregated bandwidth request size in bytes
BR FID
4
The FID for which UL bandwidth is requested.
STID
12
STID of the M2M device which requests UL
bandwidth.
STID_Valid_Offset
3
STID_Valid_Offset of the M2M device which
requests UL bandwidth
}
[Remedy #3: Insert the following text to page 11, line 51]
16.2.3.9 AAI-REG-RSP
Field
STID_Valid_Periodicity
STID_Valid_Offset
Table 686—AAI-REG-RSP message Field Description
Size (bits) Value/Description
Condition
3
The STID_Valid_Periodicity
Shall be included when an M2M
together with STID_Valid_Offset device is performing initial
indicates at which frames the
network entry or an M2M device
assigned STID is valid for the
has no STID pre-assigned when
M2M device
it is performing network reentry
procedure
3
The STID_Valid_Offset together
Shall be included when an M2M
with STID_Valid_Periodicity
device is performing initial
indicates at which frames the
network entry or an M2M device
assigned STID is valid for the
has no STID pre-assigned when
M2M device
it is performing network reentry
procedure
[Remedy #4: Insert the following text to page 18, line 55]
16.2.3.47.1 AAI-DSA-REQ
—— Predefined BR index parameters: Predefined BR index parameters define the mapping from predefined
BR index(es) to BR action and BR size, which is used in 3-step Bandwidth Request procedure, and are only
6
IEEE C802.16p-11/0136r3
included in ABS initiated DSA-REQ. They are determined based on the QoS parameters of the service flow in
the AAI-DSx messages. If BR Action is 0b00 or 0b01, the same BR Index shall not be assigned to different
service flows. If BR action is 0b10 (BR), ABS shall assign different BR index to service flows whose UL Grant
Scheduling Type is different and shall assign different BR index to different service flows whose UL
Scheduling Type is same but BR size is different. If the STID assigned to an M2M device is shared with other
M2M device (s), then BS shall assign different BR indexes to the M2M devices sharing STID. The BS shall use
the STID and assigned BR index received in the quick access message to identify the M2M device if the
received STID is assigned to multiple M2M devices.
[Remedy #5: Insert the following text to page 21, line 29]
16.2.14 HARQ functions
16.2.14.2.1.2 Uplink
When an ABS allocates new UL resource to an M2M device sharing a STID, if there is UL burst retransmitted
by another device sharing the same STID at the same UL subframe, the ABS shall allocate the new UL resource
by using different ACID from the ACID of retransmitted UL burst.
----------------------------- End Text Proposal
----------------------------------
4 Reference
[1] IEEE 802.16p-10/0004r2: IEEE 802.16p Machine to Machine (M2M) System Requirements Document
(SRD).
[2] IEEE 802.16p-10/0018r2: IEEE P802.16p Amendment Working Document (AWD).
[3] IEEE 802.16p-10/0005r1: Machine to Machine (M2M) Communications Technical Report.
[4] IEEE P802.16m/D12, Draft Amendment to IEEE Standard for Local and Metropolitan area Networks.
7