[DEV] DL multicast transmission for M2M devices
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE S802.16p-rg-11/0021
Date Submitted:
2011-02-07
Source:
Jeongki Kim, Youngsoo Yuk, Jin Lee, Giwon Park, Email: {jeongki.kim, youngsoo.yuk} @lge.com
Kiseon Ryu, Jinsam Kwak
LG Electronics
Re: 80216p-10_0016: M2M Rapporteur Group Plan, Schedule, and Guidelines
Venue: M2M Rapporteur Group
Base Contribution:
IEEE C802.16p-rg-11/0021.doc
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 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.
Patent Policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
and .
Further information is located at and .
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 receive DL traffic addressed to MS in idle
mode, it has to perform network re-entry.
DL data
BS/
occurence
paging
controller
DL MAP + DL data
Connection setup
Network reentry
Paging
Idle AMS
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
Multicast transmission for M2M devices
Multicast operation in Idle mode
* MGPID: M2M Group Paging ID
* MTST: Multicast Transmission Start Time
* MTE indicator: Multicast Transmission End indicator
16p BS/
paging
controller
(Multicast notification,
MGPIDs, MTST)
Multicast data
MTE indicator
PAG-ADV
M2M device
MTST
Paging listening Unavailable Time interval for DL multicast
interval interval data trasnsmission
Multicast transmission for M2M devices
Reliable multicast transmission (1/2)
802.16p needs to provide the reliable multicast transmission for some
important multicast data (e.g., application/firmware update data)
According to Section 6.2.6 in 16p SRD (reliable data delivery)
If M2M device detects multicast data reception error (e.g., DL burst
decoding error ), the M2M device shall request the multicast data
retransmission to ABS
In response to the request of multicast data retransmission ABS shall
retransmit the requested multicast data
Multicast inter-arrival timer (MIA timer)
Start: When an M2M device successfully receives the first multicast data
burst
Reset: Whenever the multicast data are received successfully
Stop: When the M2M device receives the MTE indicator or the multicast
reception error happens
Multicast transmission for M2M devices
Reliable multicast transmission (2/2)
An example of the multicast reception error cases
M2M device 16p BS
A-MAP IE for multicast transmission
Multicast data burst
The burst
decoding error
Multicast ReTx Req message
ReTx of Multicast data
Proposed text
[Adopt the text proposal of contribution C802.16p-rg-11_xxxx]