IEEE C802.16m-10/0400r1
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Changes Related to Carrier Management Procedures in Multicarrier
Systems (16.2.8.2.11)
Date
Submitted
2010-07-09
Source(s)
Lei Wang
Voice : +1 858 205-7286
InterDigital Communications, LLC
E-mail: leiw@billeigean.com
Re:
IEEE Standards Sponsor Ballot for P802.16m/D6.
Abstract
The contribution proposes the changes regarding carrier management procedures in
multicarrier systems (16.2.8.2.11).
Purpose
To be discussed and adopted by TGm for the 802.16m DRAFT 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.16m-10/0400r1
Proposed Changes Related to Carrier Management
Procedures in Multicarrier Systems (16.2.8.2.11)
Lei Wang
InterDigital Communications, LLC
1 Introduction
In the carrier management procedure, the AAI_CM-CMD message is used for the ABS to
instruct the AMS to perform certain actions, and the carrier management procedure is always
initiated by the ABS. Then, the question is why the AMS is not allowed to initiate a carrier
management procedure.
Note that in some cases it is useful and important that the AMS can also initiate carrier
management processes. For example, based on the AMS’s measurements and monitoring of its
assigned multiple carriers, it may detects one of the fully configured secondary carrier is more
suitable to be used as its primary carrier, in this case the AMS may want to initiate a carrier
management process to make the primary carrier change. This is very similar to the use case of
AMS-initiated HO, as the primary carrier is actually the anchor for the AMS to connect to the
ABS in the multicarrier operation.
This contribution proposes a new MAC control message, called AAI_CM-REQ, which is sent by
the AMS to initiate carrier management procedures.
2 Suggested changes in the 802.16m/D6
Based on the above discussion, we propose the following changes in the 802.16m/D6. Note that
the new text is marked with blue and underline; the deleted text are marked with red and
strikethrough.
Suggested change #1: page 318 line 4
Insert the following paragraph before line 4 on page 318:
The secondary carrier management procedure for activation or deactivation of secondary carrier(s) can
also be initiated by the AMS through sending the AAI_CM-REQ message to the ABS. Upon receiving a
secondary carrier activation or deactivation request from an AMS in an AAI_CM-REQ, the ABS responds
with an AAI_CM-CMD message based on the ABS’ decision regarding accepting or rejecting the AMS’
2
IEEE C802.16m-10/0400r1
request.
Suggested change #2: on page 319, line 63
Insert the following paragraph before line 63 on page 319:
The primary carrier change procedure can also be initiated by the AMS through sending the AAI_CM-REQ
message to the ABS. Upon receiving a primary carrier change request from an AMS in an AAI_CM-REQ,
the ABS responds with an AAI_CM-CMD message based on the ABS’ decision regarding accepting or
rejecting the AMS’ request.
Suggested change #3: on page 225, line 13
Insert the following text before line 13 on page 225:
16.2.3.59 Carrier Management Request (AAI_CM-REQ) MAC Control message
The carrier management request MAC control message, AAI_CM-REQ, is sent by the AMS to the ABS to initiate a
carrier management action, e.g., secondary carrier activation or deactivation, and primary carrier change. Its format
is defined in Table nnn.
Table nnn—AAI_CM-REQ MAC Control Message Format
Field
Size
(bit)
Description
AAI_CM-REQ MAC control message format
() {
Control message type
8
AAI_CM-REQ
Action Code
1
0b0: secondary carrier management
0b1: primary carrier change
If (action code ==0b0) {
Indication Type
2
Indicate the corresponding secondary carrier is activated
or deactivated
00: no action
01: deactivation only
10: activation only
11: both activation and deactivation
If (Indication Type != 0b00) {
Num of carriers
3
Indicate the number of secondary carrier(s) to be
activated or deactivated
1..8
3
IEEE C802.16m-10/0400r1
For (i=0; i<Num of target carrier; i++) {
carrier index
3
Indicate the secondary carrier index to be activated or
deactivated
1..8
Activation/Deactivation indicator
1
Indicate activation/deactivation
0b0: activation
0b1: deactivation
If (Activation/Deactivation indicator
0b0) {
==
Activation deadline
6
LSB bits of Superframe number after the
AAI_CM-CMD is sent for the AMS to confirm the
activation of secondary carrier by sending the
AAI_CM-IND message
Activation DL/UL
1
Indicate the activation of DL or UL in the corresponding
secondary carrier
0b0: Both DL/UL of the secondary carrier are activated
0b1: DL of the secondary carrier is activated but UL of
the secondary carrier is not activated
Ranging indicator
1
Indicate the periodic ranging is required for the carrier
0b0: no initial or periodic ranging is required for the
carrier
0b1: periodic ranging is required for the carrier
}
else {
Deactivation DL/UL
Indicate the deactivation of DL or UL in the
corresponding secondary carrier
0b0: Both DL/UL of the secondary carrier are
deactivated
0b1: UL of the secondary carrier is deactivated but DL
of the secondary carrier is kept active
}
}
}
}
If (action code ==0b1) {
4
IEEE C802.16m-10/0400r1
Physical carrier index of target carrier
6
Indicate the physical carrier index of a target carrier for primary carrier change. If the AMS supports multicarrier
operation, the carrier shall be one of the assigned carriers
0..63
Ranging indicator
1
Indicate the periodic ranging is required for the carrier
0b0: no initial or periodic ranging is required for the
carrier
0b1: periodic ranging is required for the carrier
Action Time
3
LSB bits of Superframe number at the time to switch to
the target carrier The value shall be set to the value more
than the Message ACK timer for AAI_CM-CMD
message
0..7: LSB of superframe
Next state of serving primary carrier
1
Indicate the deactivation of serving primary carrier after
primary carrier change.
0b0: serving primary carrier will be deactivated after
primary carrier change. If the AMS does not support
carrier aggregation, this field shall be always set to 0b0.
0b1: serving primary carrier is kept active after primary
carrier change
}
}
Suggested change #4: on page 74 line 47
Append the following two rows at the end of Table 678 in line 47 on page 74:
No.
68
Functional area
multicarrier
Message Name
AAI_CM-REQ
Message description
Carrier Management
Request
3 References
[1] IEEE Std 802.16-2009
5
Security
connection
<TBD>
Basic
IEEE C802.16m-10/0400r1
[2] IEEE P802.16m/D6, “DRAFT Amendment to IEEE Standard for Local and metropolitan area
networks”
6