Location update procedure for 802.16p system
IEEE 802.16 Presentation Submission Template (Rev. 9.2)
Document Number:
IEEE C80216p-10_0017
Date Submitted:
2010-12-29
Source:
Giwon Park, Jin Lee, Jeongki Kim, Youngsoo Yuk, Kiseon Ryu and JinSam Kwak Email: {giwon.park}@lge.com
LG Electronics
Re:
80216p-10_0009: call for contributions on project 802.16p amendment working document content
Venue:
IEEE Session #71
Base Contribution:
IEEE 802.16ppc-10/0004r1
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:
<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 >.
Introduction
 Location update of 16m system
 Timer based update, location (i.e., paging group) based update, power down
update, MBS location update
 In the SRD[IEEE 802.16p-10/0004r1],
 Low power consumption in M2M devices
 The 802.16p system shall provide optimized operation for M2M devices with
no/low mobility to conserve power.
 The 802.16p system shall support optimized operation for time controlled,
time tolerant and in-frequent traffic to conserve power.
 The location update for 16p system shall consider the following features of M2M
device to optimize the location update operation.
 Mobility capability (No, Low, Medium, High)
 Traffic pattern (Time controlled, Non time controlled)
Negotiation of M2M device’s capabilities
 Mobility capability and traffic pattern may be considered for location update of
M2M device.
 Following capabilities of M2M device can be negotiated in the network (re)entry
phase (e.g., SBC-REQ/RSP or REG-REQ/RSP).
 Mobility capability (no, low, medium, fast),
 Traffic pattern (Time controlled, Non time controlled)
 Network decides the location update type (e.g., No location update) and/or
location update parameter (e.g., the type of location based update, location
update timer) based on mobility capability and traffic pattern of M2M
M2M
device.
device
BS
Capability negotiation
Network Entry
Mobility capability and traffic pattern (e.g.,
Fixed mobility, Time controlled traffic)
Capability negotiation
Location update type (i.e., No location update)
Figure 1. Mobility capability & traffic pattern based location update type decision
Location update for time controlled M2M device
 Time controlled M2M device
 The device of this type may not perform the timer based location update
because it periodically reports uplink traffic to the BS at pre-defined time
duration.
 If the time controlled M2M devices (e.g., metering devices) get the
location update timer (e.g., timer duration > UL report cycle) via
explicit signaling (e.g., SBC-REQ/RSP or REG-REQ/RSP) based on its
traffic pattern (e.g., Time controlled or Non time controlled), it may not
perform timer based update.
UL report cycle for time controlled traffic featured
M2M device
On
duration
Off
duration
On
duration
Off
duration
Duration of Idle mode timer (location update timer)
Figure 2. Location update timer for time controlled M2M device
Location update for no/low mobility M2M device
 No/Low mobility M2M device
 The device of this type may not perform the location based update.
 No mobility M2M device does not perform the location based update
because its location is always fixed.
 Low mobility M2M device may not perform the paging group based update
because the mobility bound is limited.
 Cell based location update is more proper than paging group based
update to no/low mobility M2M device.
M2M
device
BS
Capability negotiation
Mobility capability and traffic pattern (e.g., low
mobility, Time un-controlled traffic)
Network Entry
Capability negotiation
·
·
·
LU type (e.g., performs the location update)
Location update timer
Type of location based update (e.g., Cell
based update)
Figure 3. Negotiation of the location based update
Conclusion
 Mobility capability and traffic pattern of M2M device shall be considered
for M2M specific location update.
Text proposal in AWD
[Insert the following texts in 16p amendment document] :
16.2.29 MAC Support of M2M
16.2.29.x Idle mode
16.2.29.x.1 Location update
An M2M device in idle mode shall perform the location update based on its mobility capability
and traffic pattern which were negotiated in capability negotiation phase of the network entry.
Based on the mobility capability and traffic pattern of M2M device, the ABS shall assign the
location update behavior of M2M device.
16.2.29.x.1.1 Location update for time controlled M2M device
Time controlled M2M device may not perform the timer based update because the time
controlled M2M device periodically transmits the uplink traffic to the base station at the prescheduled time.
16.2.29.x.1.2 Cell based update
An M2M device with no or low mobility shall perform the Cell based update when an M2M
device detects that the selected preferred cell does not support any of its currently attached
cell.