Proposed AWD Text for Idle mode support in Multicarrier
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE S802.16m-09/0852
Date Submitted:
2009-05-04
Source:
Chie Ming Chou, Chun-Yen Wang, Frank Ren, Yung-Han Chen
chieming@itri.org.tw
ITRI
Venue:
Re : Call for Contributions on Project 802.16m Amendment Working Document (AWD) Content
Base Contribution:
IEEE C802.16m-09/0852r1
Purpose:
To be discussed and adopted in TGm
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 >.
1
Background
• In Section 17.4.9.2 of SDD (IEEE 802.16m-08/003r8), idle
mode in Multicarrier is addressed:
– When an AMS supports Multicarrier operations, it will monitor paging
notification on a fully configured carrier.
– The selection of the paging carrier in the Multicarrier deployment is
the same for single carrier and multicarrier capable AMSs
– One set of unified idle mode parameters (i.e., paging listening interval
and paging unavailable interval configuration) is configured for an AMS
regardless of single carrier or multi-carrier operation.
• How to configure a fully configured carrier to support idle
mode is discussed in this contribution
2
Option 1:
(Every fully configured carrier in an ABS provides
identical paging notifications)
• For AMS, it can be able to arbitrarily camp on one of fully
configured carrier to perform idle mode operation
– Check the PGID information
• If ABS supports same PGID, then listen the paging message in negotiated
interval
• If ABS support different PGID, then perform location update process
• For ABS, configuring every fully configured carrier to
broadcast the identical paging message is an obvious
overhead
3
Option 1 (example)
Both ABS1 and ABS2 support
PGID {a,b,c}; AMS1,2,3,4 are in
idle mode & belonged to
PGID {a}
Fully configured carrier #1
ABS2 has three fully
configured carriers
When paging controller
wants to page PGID {a}’s
members, and needs M
resources Mx3 in ABS2
Paging message for PGID a
Support PGID {a,b,c}
SFH
Fully configured carrier #2
Support PGID {a,b,c}
SFH
Fully configured carrier #3
Support PGID {a,b,c}
SFH
ABS2
ABS1
AMS3
AMS4
AMS1
AMS2
4
Option 2:
(Fully configured carrier in an ABS provides
partial paging message)
• Each carrier will be configured to support one or multiple
PGID
– Each carrier will provide PGID information which advertise
• The PGIDs supported by this ABS
• The PGIDs supported by this carrier
– A carrier only provides paging message for its support PGID
• AMS needs to find supported carrier (support its PGID) when
selecting a carrier
– Check the PGID information
• If both ABS and camped carrier support this PGID OK
• If ABS support this PGID, but this carrier doesn’t find another carrier
– No any update of a paging controller
• If ABS does not support this PGIDlocation update
• Saving resource overhead, but AMS may need to select
suitable carrier
5
Option 2 (example)
Both ABS1 and ABS2 support
PGID {a,b,c}; AMS1,2,3,4 are in
idle mode & belonged to
PGID {a}
Fully configured carrier #1
ABS2 has three fully
configured carriers, but
only carrier #1 support
PGID {a}
Paging message for PGID a
Support PGID {a}
SFH
Fully configured carrier #2
Support PGID {b}
SFH
Fully configured carrier #3
Support PGID {b,c}
SFH
When paging controller
wants to page PGID {a}’s
member, and needs M
resources Mx1 in ABS2
ABS2
ABS1
AMS3
AMS4
AMS1
AMS2
6
Option 2:
(Modification on PGID information)
7
Conclusion
• Configuring different fully configured carriers to
support different PGIDs (option 2) have benefits
– Saving paging message overhead
– No additional location update process
– Do not need different idle mode parameters for an AMS
• TGm should consider this and adopt the proposed
text in C80216m-09_0852r1
8