IEEE C802.16m-10/0065
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Text Clean Up for Network Entry (16.2.15)
Date
Submitted
2010-03-05
Source(s)
Yang Liu, Nan Li
ZTE Corporation
Voice: [Telephone Number (optional)]]
E-mail:
liu.yang8@zte.com.cn
Youngkyo Baek
Samsung
youngkyo.baek@samsung.com
Hee Jeong Cho, Inuk Jung, Minseok Oh
LG
heejeong.cho@lge.com
kelvin.chou@mediatek.com
Kelvin Chou
MeidiaTek
chenyunghan@itri.org.tw
Yunghan Chen
ITRI
xiangying.yang@intel.com
Xiangying Yang, Sassan Ahmadi
Intel
Re:
Call for LB #31 on “ P802.16m/D4”:
Target topic: “16.2.15”
Abstract
Purpose
Notice
Release
This proposal provides editorial change on network entry (16.2.15) and related message formats.
To be discussed and adopted
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.
1
IEEE C802.16m-10/0065
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>.
Text Clean Up for Network Entry (16.2.15)
Yang Liu, Nan Li
ZTE Corporation
Youngkyo Baek
Samsung
Hee Jeong Cho, Inuk Jung
LG
Introduction
This proposal provides editorial change on network entry (16.2.15) and related message formats.
Text Proposal
----------------------------------------------------------- Start of the Text 1------------------------------------------[On the IEEE P802.16m/D4, page 290, line 1, make the following changes to subclause 16.2.15]
16.2.15 Network Entry and Initialization
The procedure for initialization of an AMS is shown in Figure 440. This figure shows the overall flow between
the stages of initialization in an AMS. This figure does not include error paths and is shown simply to provide
an overview of the process. [Comment on the figure 440: Please change “Pereferred Cell Type” in the center
diamond to “Preferred Cell Type”]
2
IEEE C802.16m-10/0065
Figure 440—AMS Initilaalization Overview
Systems shall support the applicable procedures for entering and registering a new AMS to the network. The
procedure for initialization of an AMS shall be divided into the following steps:
a)Scan for DL channel and establish DL PHY synchronization with the ABS
b)Obtain DL/UL parameters (from P-SFH/S-SFH IEs etc.) and establish DL MAC synchronization
c)Perform ranging and automatic adjustment
d)Negotiate basic capability
e)Perform AMS authorization and key exchange
f)Perform registration, and setup default service flows (i.e. pre-provisioned service flows).
Figure 441 and Figure 442 describe the state machine of the AMS and ABS for the initial NW entry process
respectively.
3
IEEE C802.16m-10/0065
Establish DL sync
/Got DL&UL parameters,
and network not selected
(T3 expired or T31 expired or
received AAI_RNG-ACK(not
detected) and retries exhausted)
or (received AAI_RNG-ACK
RSP(abort))
Acquire
System
Information
Establish DL sync
/ Got DL&UL parameters,
and network selected
Wait for
ranging
opportunity
Got ranging
opportunity/ Send
Initial ranging code
Wait for
AAI_RNGACK or
CDMA
allocation AMAP IE
T3 expired and
have more retries
Received
AAI_RNG-ACK
(continue or not
detected)
or T3 expired or T31
expired and have more
retries)
Got CDMA Allocation IE/
Send AAI_RNG-REQ
Wait for
AAI_RNGRSP with
temporary
STID
(T3 expired and retries
exhausted) or (received
AAI_RNG-RSP(abort))
Got AAI_RNG-RSP(success) with
temporary STID /
Send AAI_SBC-REQ
T18 expired and have more
retries/ Send AAI-SBC-REQ
(T18 expired and
retries exhausted) or
(received AAI_RNGRSP(abort) from ABS)
Wait for
AAI_SBCRSP
got AAI_SBCRSP and if
Auth. supported
got AAI_SBCRSP and if
Auth. not
supported, send
AAI_REG-REQ
AMS
authorization
and key
exchange
(T17 expires and
retries exhausted) or
(received AAI_RNGRSP(abort) from ABS)
Authenticated/ Send
AAI_REG-REQ
T6 expired and have more
retries/ Send AAI_REG-REQ
Wait for
AAI_REGRSP with
STID
(T6 expires and retries
exhausted) or ( AAI_RNGRSP(abort) or AAI_RESCMD from ABS
Got AAI_REG-RSP/
Handle AAI_REG-RSP
(AAI_RNG-RSP(Abort) or
AAI_DREG-CMD or
AAI_RES-CMD from ABS
Default
service flow
setup &
NW entry
completed
Figure 441—State machine of the AMS for the initial NW entry process
4
IEEE C802.16m-10/0065
Got initial ranging code /
Send AAI_RNG-ACK(continue)
Wait for
initial
ranging code
Got initial ranging code /
Send AAI_RNG-ACK(success) and Send CDMA
Allocation A-MAP IE
Wait for
AAI_RNGREQ
AMS Ranging Response
Processing Time expired
Wait for
AAI_SBCREQ
Send AAI_RNG-RSP(abort)
AMS
authorization
and key
exchange
Send AAI_RNG-RSP(abort)
Got initial ranging code/
Send AAI_RNG-ACK
(abort)
Got AAI_RNG-REQ/
Send AAI_RNG-RSP(success)with
temporary STID
Got AAI_RNG-REQ/Handle AAI_RNG-REQ
retx (Send AAI_RNG-RSP(success) with
temporary STID
Auth. Supported,
Got AAI_SBC-REQ/
Send AAI_SBC-RSP
Auth. Not supported,
Got AAI_SBC-REQ/
Send AAI_SBC-RSP
Got AAI_SBC-REQ/
Handle AAI_SBC-REQ
retx(i.e.,Send AAI_SBC-RSP)
END
Authenticated
Send AAI_RNG-RSP(abort)
or AAI_RES-CMD
Auth. Not supported,
Got AAI_SBC-REQ/Handle AAI_SBCREQ re-tx (i.e.,Send AAI_SBC-RSP)
Wait for
AAI_REGREQ
Got AAI_REG-REQ/ Send
AAI_REG-RSP with STID*
Got AAI_REG-REQ/
Handle AAI_REG-REQ retx(i.e.,Send
AAI_REG-RSP with STID)
Send AAI_RNG-RSP(abort)
or AAI_RES-CMD
Wait for
ACK for
AAI_REGRSP
Got Implicit or explicit
ACK for AAI_REG-RSP
Send AAI_RNG-RSP(abort),
AAI_RES-CMD or
AAI_DREG-CMD
Establish
connection/
NW entry
completed
Figure 442—State machine of the ABS for the initial NW entry process
5
IEEE C802.16m-10/0065
During network entry, an ABS may allocate an UL bandwidth for transmission or retransmission of MAC
messages, the size of which is predefined, without a bandwidth request from the AMS by setting an unsolicited
bandwidth indicator in an AAI_RNG-RSP message to the AMS. If the unsolicited bandwidth indicator is
enabled, the ABS should allocate UL bandwidth within the predefined time duration in order to transmit or
retransmit subsequent MAC messages during network entry.
An AMS should monitor the A-MAP IE during the predefined time duration for possible bandwidth allocation
without performing any bandwidth request. If the AMS fails to identify allocated bandwidth within the
predefined time duration, the AMS may perform contention based bandwidth request. When the allocated
resource is not sufficient for transmission of MAC messages, the AMS shall send a piggyback bandwidth
request. To reduce latency, a piggyback bandwidth request is used for this purpose.
When an AMS sends an MAC message in a different size from the predefined, the AMS should notify the ABS
of its size in the previous message defined for the network entry procedure, so that the ABS can allocate precise
bandwidth to the AMS.
Each AMS contains the following information when shipped from the manufacturer:
•A 48-bit universal MAC address (per IEEE Std 802-2001) assigned during the manufacturing process. This is
used to identify the AMS SS to the various provisioning servers during initialization.
•Security information as defined in Clause 7 (e.g., X.509 certificate) used to authenticate the AMS to the
security server and authenticate the responses from the security and provisioning servers.
16.2.15.1 AMS DL PHY synchronization.
On initialization or after signal loss, the AMS shall acquire the DL PHY synchronization by A-Preamble. The
detailed procedure for DL PHY synchronization is described in section 16.3.6.1.
The AMS shall have nonvolatile storage in which the last operational parameters are stored and, when the AMS
needs to acquire DL PHY synchronization, it may at first try synchronizatioin using the stored DL channel
information. But if the trial fails, the AMS shall begin to scan the possible channels of the DL frequency band of
operation until it finds a valid DL signal.
16.2.15.2 AMS obtaining DL/UL parameters
For initial network entry, once the AMS has achieved DL PHY synchronization with an ABS, the AMS shall
decode the P-SFH and S-SFH in order to obtain the necessary system information containing the DL and UL
parameters for the initial network entry. Based on the network information such as NSP list which may be
6
IEEE C802.16m-10/0065
obtained from AAI_SII-ADV message, the AMS shall decide whether to continue the network entry process
with this ABS or to scan for other ABSs. If the AMS reads cell_bar=1 in SFH, this which means this cell does
not allow access of new AMS, and the AMS shall select a different cell to restart network entry procedure.
If the AMS succeeds to decode the essential system information, the AMS is DL MAC synchronized with the
ABS.
16.2.15.3 Initial ranging and automatic adjustments
After DL synchronization, the AMS shall attempt to perform initial ranging with the ABS. If the ranging
procedure is successfully completed, the AMS is UL synchronized with the ABS and obtains TSTID from the
ABS. The TSTID is used until the ABS assigns the AMS an STID through registration procedure.
Ranging is the process of acquiring the correct timing offset, frequency offset and power adjustments so that the
AMS's transmissions are aligned with the ABS, and they are received within the appropriate reception
thresholds.
An AMS that wishes to perform initial ranging shall take the following steps:

The AMS, after acquiring downlink synchronization and uplink transmission parameters, shall select one
ranging opportunity based on the random backoff. The random backoff shall use a binary truncated exponent algorithm. After selecting the ranging opportunity, the AMS shall choose a ranging preamble code
(from the Initial Ranging domain) using a uniform random process. The AMS shall send the selected
ranging preamble code to the ABS in the selected ranging opportunity.
 The ABS should respond with an AAI_RNG-ACK message in a predefined, subsequent DL AAI
subframe as defined in 16.2.3.3. The AAI_RNG-ACK message provides responses to all the successfully
received and decoded ranging preamble codes in all the ranging opportunities in a previous UL AAI
subframe. If all the decoded ranging preamble codes prove 'success' status and the ABS provides UL BW
allocation for each ranging preamble codes before the predefined DL AAI subframe that AAI_RNGACK is to be transmitted, the AAI_RNG-ACK may be omitted. If the AMS finds in the RNG-ACK
bitmap that no ranging preamble code has been successfully decoded in the ranging opportunity selected
by the AMS, or it does not find either a response in the AAI_RNG-ACK message or UL BW allocation
to its ranging preamble code, the AMS considers its initial ranging request is failed and restarts the initial
ranging procedure.
 There are three possible ranging status responses from ABS to AMS provided in the AAI_RNG-ACK
message:
- continue: the ABS provides the needed adjustments (e.g., time, power, and possibly frequency
7
IEEE C802.16m-10/0065
corrections) and a status notification of "continue".
- success: the ABS provides a status notification of "success", but may have adjustment suggestions to
the AMS if necessary. With IR status successs, the ABS shall provide the AMS an UL BW allocation for
the AMS to send AAI_RNG-REQ message.
- abort: the ABS requests the AMS to abort the ranging process.
 Based on the received response of ranging status, the AMS performs the followings.
- Upon receiving a Continue status notification and parameter adjustments in the AAI_RNG-ACK
message, the AMS shall adjust its parameters accordingly and continue the ranging process as done on
the first entry (using random selection rather than random backoff) with ranging preamble code
randomly chosen from the initial ranging domain sent on the initial ranging region opportunity.
- Upon receiving a Success status notification, the AMS shall wait for the ABS to provide UL BW
allocation. If the AMS has not received the CDMA Allocation A-MAP IE for UL BW allocation by T3
after sending a ranging preamble code, it restarts the initial ranging procedure or, if 'ranging retries' is
exhausted, it retries DL PHY synchronization. When receiving an UL BW allocation, the AMS shall
send the AAI_RNG-REQ message. If the granted BW allocation cannot accommodate the entire
AAI_RNG-REQ message, the AMS may fragment the AAI_RNG-REQ message to fit the provided BW
allocation, and requests additional UL bandwidth through either BR without STID header (refer to
16.2.2.1.3.2) or PBREH as defined in 16.2.2.2.8 for the remaining fragments. In response to the BR
without STID header or PBREH, the ABS shall provide UL BW allocation through CDMA Allocation
A-MAP IE, which is identified by the same RA-ID used for the previous BW allocation. The RA-ID is
used until AAI_RNG-RSP transmission is completed, but if AMS does not receive any UL bandwidth
allocation in T3 or the AAI_RNG-REQ/RSP transaction is not completed in 128 frames, it sends ranging
code to perform ranging procedure again.
-----------------------------------------------------------End of the Text 1-----------------------------------------------------[Change the text as follows from P.297, line 3.]
-----------------------------------------------------------Start of the Text 2-----------------------------------------------------
16.2.15.5 AMS authorization and key exchange
If authorization support is enabled in basic capability negotiation, the ABS and the AMS shall perform
authorization and key exchange through EAP-based authentication (IETF RFC 3748) and key agreement
procedure (see 16.2.5.2.1.4). If this procedure completes successfully, all parameters for TEK generation are
shared, and TEKs are derived at each side of the AMS and the ABS. If authorization support is disabled, the
step of AMS authorization and key exchange shall be skipped.
16.2.15.6 Registration
8
IEEE C802.16m-10/0065
Registration is the process by which the AMS is allowed to enter into the network.
After authorization and key exchange are finished, the AMS informs the ABS of its capabilities and requests the
registration for entry into the network by AAI_REG-REQ. If an ABS receives an AAI_REG-REQ, the ABS
shall respond with an AAI_REG-RSP.
In the AAI_REG-REQ, the AMS informs the ABS of its capability parameters to be negotiated except those
capabilities already negotiated with the ABS through AAI_SBC-REQ/RSP messages. In AAI_REG-RSP, the
ABS responds with the accepted capability parameters. If the AMS omits some capability parameters in the
AAI_REG-REQ, the ABS considers the AMS follows the default values for those parameters and, if acceptable,
the ABS may omit those parameters applying default value in its AAI_REG-RSP.
The ABS shall allocate and transfer a STID to the AMS through an encrypted AAI_REG-RSP message. The
temporary STID, which was allocated during initial ranging procedure, is discarded when the ABS recognizes
that the AMS received the AAI_REG-RSP messages successfully. The AAI_REG-RSP message contains the
CRID, where the network retains the AMS contexts including the CRID and the AMS MAC address.
Upon successful registration, a DL FID and a UL FID are assigned to the AMS without using the DSA
procedure in order to activate one preprovisioned service flow for each UL FID and DL FID which can be used
for upper layer signaling (e.g. DHCP).
During the registration procedure, the AMS and the ABS shall negotiate IP versions and may negotiate host
configuration parameters. The AMS shall inform the supported IP version(s) (for example, IPv4, IPv6 or both)
to the network through the ABS by including the Supported-IP-Versions IE in the AAI_REG-REQ message.
After the network selects one of the supported IP version(s), the ABS shall inform the AMS of the selected IP
service type (for example, IPv4 only, IPv6 only or IPv4/IPv6 dual mode) by including the IP-Service-Type IE in
the AAI_REG-RSP message.
The AMS may indicate its capability of configuring host parameters (for example, host address or home
network prefix) and request the additional parameters (for example, DNS Server Address) to the network
through the ABS by including the Host-Configuration-Capability-Indicator IE in the AAI-REG-REQ message.
If the AMS indicates its capability of configuring host parameters, the ABS shall include either the IPv4-HostAddress IE or the IPv6-Home-Network-Prefix IE or both and the requested host configuration parameter(s) in
the AAI-REG-RSP message.
If the AMS does not indicate its capability of configuring host parameters, the ABS shall not include any of
those host configuration parameters in the AAI_REG-RSP message assuming that the AMS will be configured
by using upper layer protocol. If the AMS wants to configure additional host configuration parameters, the AMS
may indicate those parameters by including Requested-Host-Configurations IE in the AAI_REG-REQ message.
9
IEEE C802.16m-10/0065
If the AMS indicates additional host configuration parameters or the network decides to configure additional
host configuration parameters, the ABS may include Additional-Host-Configurations IE in the AAI_REG-RSP
message.
The format of the value field of Requested-Host-Configurations IE and Additional-Host-Configurations IE is
defined in RFC2132[1] for IPv4, RFC3315[2] for IPv6. Note that list of parameters can be found in [3], [4].
-----------------------------------------------------------End of the Text 2------------------------------------------------------
[Change the text as follows from P.64, line 5, table 676 as indicated.]
-----------------------------------------------------------Start of the Text 3----------------------------------------------------Table 676—Parameters for AAI_RNG-REQ
Name
Value
…
…
Ranging
Purpose
Indication
The presence of this item in the message indicates the following AMS
action:
Usage
…
If Bit#0 is set to 1, it indicates that the AMS is currently attempting HO
reentry, or, in combination with a Paging Controller ID, indicates that the
MS is attempting network reentry from idle mode to the BS. In this case,
Bit#1 shall be 0.
If Bit#1 is set to 1, it indicates that the AMS is initiating the idle mode
location update process, or, in combination with CRID, it indicates that
the AMS is initiating DCR mode extension. In this case, Bit#0 shall be 0.
If Bit#2 is set to 1, ranging request for emergency call setup. When this bit
is set to 1, it indicates AMS action of Emergency Call process.
If Bit#43 is set to 1, it indicates that the AMS is attempting to perform
location update due to a need to update service flow management
encodings for E-MBS flows.
If Bit #54 is set to 1, it indicates that the AMS is initiating location update
for transmission to DCR mode from idle mode.
If Bit #65 is set to 1 in combination with ID of the network entity that
1
0
It shall be included
when the AMS is
attempting
to
perform
reentry,
HO,
location
update or DCR
mode extension.
IEEE C802.16m-10/0065
assigns/retains the context, it indicates that the AMS is currently
attempting reentry from DCR mode.
If Bit#76 is set to 1, it indicates that the AMS is currently attempting
network reentry after experiencing a coverage loss.
If Bit#87 is set to 1, it indicates that the AMS is currently attempting
network reentry from a IEEE802.16e only Legacy BS
Bit#8: Reserved
…
…
…
-----------------------------------------------------------End of the Text 3-----------------------------------------------------[Change the text as follows from P.67, line 10, table 677 as indicated.]
-----------------------------------------------------------Start of the Text 4----------------------------------------------------Table 677—Parameters for AAI_RNG-RSP
Name
Ranging Status
Value
Usage
Used to indicate whether UL messages are It shall be included
received within acceptable limits by ABS.
AAI_RNGRSP message
in
the
1 = continue, 2 = abort, 3 = success
0b00=success, 0b01= abort, 0b11= continue
…
…
…
-----------------------------------------------------------End of the Text 4-----------------------------------------------------[Change the text as follows from P.69, line 60, table 678 as indicated.]
-----------------------------------------------------------Start of the Text 5----------------------------------------------------Table 678—Parameters for AAI_RNG-ACK
Name
Value
Usage
1
1
IEEE C802.16m-10/0065
…
Ranging Status
…
…
When the AAI_RNG-ACK is sent
Used to indicated whether UL messages are with a broadcast STID, the
parameter shall be included for
received within acceptable limits by the ABS
each received ranging code if
Number of received codes > 0.
0b01: continue
When the AAI_RNG-ACK is sent
with an unicast STID, the
0b11: abort
parameter is included for the
specific user.
0b00: success
0b00=success, 0b01= abort, 0b11= continue
…
…
…
-----------------------------------------------------------End of the Text 5------------------------------------------------------
1
2