1
IEEE C802.16m-09/2926r1
Project
Title
IEEE 802.16 Broadband Wireless Access Working Group < http://ieee802.org/16 >
Proposed Text on the E-MBS Connection Establishment (16.9.2)
Date
Submitted
2010-01-13
Source(s)
Re:
Eunkyung Kim, Soojung Jung,
Jaesun Cha, Sungcheol Chang,
Kwangjae Lim, Hyun Lee, Chulsik Yoon
ETRI
Kaushik Josiam, Taeyoung Kim,
Hai Wang, Jaejeong Shim
Samsung Electronics
Yongjoo Tcha
KT
Kaiying Lv, Nan Li, Bo Sun
ZTE Corporation
Voice: +82-42-860-5415
E-mail: ekkim@etri.re.kr
brian.shim@samsung.com
yjtcha@kt.com lv.kaiying@zte.com.cn
*< http://standards.ieee.org/faqs/affiliationFAQ.html
>
“P802.16m/D3,” in response to the IEEE 802.16 Working Group Letter Ballot Recirc #30b:
Announcement, IEEE 802.16-09/0073
Abstract
Purpose
Notice
Release
Patent
Policy
E-MBS Connection Establishment on the IEEE 802.16m Amendment Draft Standard
To discuss and adopt the proposed text in the next revision of 802.16m draft
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

9
10
11
6
7
8
12
13
14
1
2
3
4
5
IEEE C802.16m-09/2926r1
Eunkyung Kim, Soojung Jung, Jaesun Cha, Sungcheol Chang, Kwangjae Lim, Hyun Lee, Chulsik
Yoon
ETRI
Kaushik Josiam, Taeyoung Kim, Hai Wang, Jaejeong Shim
Samsung Electronics
Yongjoo Tcha
KT
Kaiying Lv, Nan Li, Bo Sun
ZTE Corporation
15
16
17
18
This contribution provides clarification on the E-MBS Connection Establishment and some parameters thereof
in IEEE 802.16m Amendment Draft Standard [1].
19
20
21
22
23
24
25
26
Note:
The text in BLACK color: the existing text in the 802.16m Amendment Draft Standard
The text in RED color: the removal of existing 802.16m Amendment Draft Standard Text
The text in BLUE color: the new text added to the 802.16m Amendment Draft Standard Text
[ Modify the 16.9.2.1 of 802.16m/D3 as follows.
]
27
28
29
30
31
32
33
34
35
36
16.9.2.1 E-MBS Connection Establishment
To discover E-MBS service, AMS will inform ABS of support of E-MBS transmission by AAI_REG-REQ message and the ABS will indicate if it supports any of E-MBS modes for that AMS through AAI_REG-RSP message. The basic E-MBS capability exchange in AAI_REG-REQ/RSP message described in 16.2.3.7 and
16.2.3.8.
Following the discovery The AMS discovers the E-MBS services and registers with the ABS for receiving multicast and broadcast services through upper layer signaling which are outside the scope of this standard.
To prepare for subsequent E-MBS operation, the AMS obtains the E-MBS related configuration information
2

18
19
20
21
22
14
15
16
17
23
24
25
26
10
11
12
13
6
7
8
9
1
2
3
4
5
27
28
39
40
41
42
35
36
37
38
29
30
31
32
33
34
43
44
45
46
47
IEEE C802.16m-09/2926r1 receiving AAI_E-MBS-CFG MAC Control message on the corresponding E-MBS carrier described in Table
944.
The AMS learns the E-MBS_Zone_ID(s) to which the ABS belongs through AAI_E-MBS_CFG message.
If E-MBS is supported by the AMS/ABS, support of DSx messaging for E-MBS flow establishment is mandatory on AMS/ABS. In addition the E-MBS flows may also be established optionally through upper layer signaling that is outside the scope of this specification.
Following such registration at the ABS for receiving multicast and broadcast services, t T he ABS or AMS may/shall initiate the DSA procedure with respect to multicast and broadcast connections. When supported, the
E MBS service flows shall be activated, changed or deleted through ABS/network Initiated DSA, DSC and
DSD messaging respectively. The ABS initiated DSx messaging shall be supported and A MS initiated DSx may also be supported. When E MBS services involve multiple flows the compact form of DSx with group parameter should be used to reduce overhead and signaling delay associated with E MBS flow management.
The ABS sends the AAI _ DSA-RSP to the AMS containing the relevant E MBS/MBS parameters. The parameters sent will indicate to the AMS whether to listen to E MBS on a 16m zone or to listen to MBS on a legacy MBS zone. It also includes E-MBS multicast M STID ( s ) and FID ( s ) , E-MBS zone ID ( s ) , E-MBS carrier information (physical carrier index). Selective decoding of content is at the granularity of FID’s.
If multicarrier feature is supported by the AMS and the ABS, the ABS should use AAI_ DSA-REQ/RSP message to redirect the A MS to legacy MBS zones or 16m E MBS zone of other carriers, if such redirection is needed. The AMS, which has acquired the service flow information for the specific E-MBS service from
AAI_DSA message, shall proceed to decode AAI_E-MBS_CFG message sent on the target E-MBS carrier for
E-MBS configuration information.
A Start time parameter is included in AAI-DSA message for carrier switching mode to indicate the time the
AMS performs carrier switching to the E-MBS carrier for detecting and decoding the AAI_E
-
MBS_CFG message.
If E-MBS is supported by the AMS/ABS, support of DSx messaging for E-MBS flow establishment is mandatory on AMS/ABS. In addition the E-MBS flows may also be established optionally through upper layer signaling that is outside the scope of this specification.
The AMS learns the E-MBS_Zone_ID(s) to which the ABS belongs through E-MBS Zone configuration message.
The AMS may continue to receive E-MBS transmissions from any ABS that is part of the E-MBS
Zone, regardless of the AMS operating mode—Active Mode, Sleep Mode, Idle Mode—without need for update to any service flow management encoding for the E-MBS flow.
To allow seamless transition from one E-MBS Zone to another without any interruption of E-MBS data service and operation, the AMS should update E-MBS service flow management encodings including MSTID ( s ) and
FID ( s ) , Packet Classification Rule parameter(s), E-MBS Zone Identifier Assignment parameter. If the AMS has no MSTID ( s ) and FID ( s ) information regarding the new E-MBS Zone, then the AMS is required to acquire
MSTID ( s ) and FID ( s ) context through the other procedures, i.e., location-update if AMS is in the idle mode and handover if A MS is in connected mode.
3

1
2
3
4
IEEE C802.16m-09/2926r1
After successful configuration, the AMS shall reuse the same configuration when it moves to another ABS in the same E-MBS Zone without re-configuration.
[Modify the 16.2.3.41.1 in 802.16m/D3 as follows.
]
5 16.2.3.41.1 AAI_DSA-REQ
20
21
22
23
16
17
18
19
9
10
11
12
13
14
15
28
29
30
31
24
25
26
27
32
33
6
7
8
38
39
40
41
42
34
35
36
37
An AAI_DSA-REQ message is sent by an AMS or ABS to create a new service flow and may contain parameters for more than one service flow. An AMS or ABS shall generate AAI_DSA-REQ message, including the following parameters:
—Control Message Type : Type of AAI_DSA-REQ message.
—Service Flow Parameters : Specification of the service flow's traffic characteristics and scheduling requirements.
—Convergence Sublayer Parameter Encodings : Specification of the service flow's CS-specific parameters.
Following parameters may be included in the AAI_DSA-REQ mssage message .
— SCID: To switch sleep cycle setting
—Predefined BR index : To use in 3-step Bandwidth Request procedure, only included in ABS initiated DSA-REQ.
When an AMS commences E-MBS service flow, the following parameters shall be included in the AAI_DSA-
REQ message.
—E-MBS Service: Indicates whether the MBS service is being requested or provided for the connection that is being setup.
When an ABS commences E-MBS service flow, the following parameters shall be included in the AAI_DSA-
REQ message.
—E-MBS Service: Indicates whether the MBS service is being requested or provided for the connection that is being setup.
—E-MBS Zone ID: Indicates an E-MBS zone where the connection for associated service flow is valid.
—E-MBS Service Flow Parameter: Mapping of Multicast STID (MSTID) and FID are included.
—Physical Carrier Index: Target carrier which the AMS switches or is redirected by ABS to, only included in ABS initiated DSA-REQ.
The FID for the transport connection shall not be present in the AMS-initiated AAI_DSA message; at the ABS, the service flow within the AAI_DSA-REQ message shall be assigned a unique FID for the transport connection, which will be sent back in the AAI_DSA-RSP message. AMS-initiated AAI_DSA-REQ messages may use the service class name in place of some, or all, of the QoS parameters.
ABS-initiated AAI_DSA-REQ messages for named service classes shall include the QoS parameter set associated with that service class. ABS-initiated AAI_DSA-REQ messages shall also include the Target SAID for the service flow.
4

1 [Modify the 16.2.3.41.2 in 802.16m/D3 as follows.
]
2 16.2.3.41.2 AAI_DSA-RSP
IEEE C802.16m-09/2926r1
13
14
15
16
17
18
19
10
11
12
6
7
8
9
3
4
5
30
31
32
33
34
26
27
28
29
20
21
22
23
24
25
35
36
37
38
39
40
An AAI_DSA-RSP message shall be generated in response to a received AAI_DSA-REQ message. An AMS or
ABS shall generate AAI_DSA-RSP message, including the following parameters:
—Control Message Type : Type of AAI_DSA-RSP message.
—Confirmation Code : The appropriate confirmation code (CC) for the entire corresponding
AAI_DSA-REQ.
—Service Flow Parameters : Specification of the service flow's traffic characteristics and scheduling requirements if the transaction is successful. The complete specification of the service flow shall be included in the AAI_DSA-RSP if it includes an expanded service class name.
—Convergence Sublayer Parameter Encodings : Specification of the service flow's CS-specific parameters if the transaction is successful.
In response to AAI_DSA-REQ message which contains SCID, the SCID may be included in AAI_DSA-RSP message as approval to ABS or AMS’s request. If AAI_DSA-RSP message doesn’t include SCID, the AMS shall regard its request as being failed.
In response to AAI_DSA-REQ message which contains 'Predefined BR index', the 'Predefined BR index' may be included in AAI_DSA-RSP message as approval to ABS or AMS’s request. If AAI_DSA-RSP message doesn’t include 'Predefined BR index', the AMS shall regard its request to use the 'Predefined BR index' as being failed.
The ABS's AAI_DSA-RSP message for service flows that are successfully added shall contain a FID for the transport connection. The ABS's AAI_DSA-RSP message shall also include the Target SAID for the service flow. If the corresponding AAI_DSA-REQ message uses the service class name to request service addition, an
AAI_DSA-RSP message shall contain the QoS parameter set associated with the named service class. If the service class name is used in conjunction with other QoS parameters in the AAI_DSA-REQ message, the ABS shall accept or reject the AAI_DSA-REQ message using the explicit QoS parameters in the AAI_DSA-REQ message. If these service flow encodings conflict with the service class attributes, the ABS shall use the
AAI_DSA-REQ message values as overrides for those of the service class.
If an AMS's AAI_DSA-RSP with status success is sent and Service Flow Parameters are included, the only
Service Flow Parameters that may be included shall be ARQ parameters for ARQ enabled connections).
When an AMS commences E-MBS service flow, the ABS shall include the following parameters in the
AAI_DSA-RSP message.
—E-MBS Service: Indicates whether the MBS service is being requested or provided for the connection that is being setup.
—E-MBS Zone ID: Indicates an E-MBS zone where the connection for associated service flow is valid.
—E-MBS Service Flow Parameter: Mapping of Multicast STID (MSTID) and FID are included.
—Physical Carrier Index: Target carrier which the AMS switches or is redirected by ABS to, only included in ABS initiated DSA-REQ.
5

7
8
9
10
11
12
5
6
2
3
4
1 [Adopt the following change in the table 748 in 802.16m/D3.
]
E-MBS_Zone_ID MBS zone identifier assignment
IEEE C802.16m-09/2926r1
8 E-MBS Zone identifier, which indicates an E-MBS zone where the connection for associated service flow is valid.
To support E-MBS, tt shall be included in AAI_DSA-
REQ/RSP message.
Refer to 11.13.29
variable Refer to 11.13.37
MBS contents ID
[Add the following row into the table 748 in 802.16m/D3.
]
E-MBS Service Flow 16
E-MBS service 2
Mapping of E-MBS STID+FID
To support E-MBS, it shall be included in AAI_DSA-REQ/RSP message.
0: No available E-MBS
1: E-MBS in Serving ABS Only
2: E-MBS in a multi-ABS Zone supporting macro-diversity
3: E-MBS in a multi-ABS Zone not supporting macro-diversity
[ Modify the Table 679 in Section 16.2.3.7 of 802.16m/D3 as follows.
]
Table 679 – Parameters for AAI_REG-REQ
AMS capability negotiation parameters
ARQ parameters
Name
ARQ_SN_MODULUS
ARQ_WINDOW_SIZE
ARQ_SUB_BLOCK_SIZE
ARQ_BLOCK_LIFETIME
ARQ_RX_PURGE_TIMEOUT
Value the number of unique SN values; default =2^10 the maximum number of ARQ blocks with consecutive SN in the sliding window of ARQ blocks
ARQ sub-block length when ARQ block is fragmented into ARQ subblocks prior to retransmission with rearrangement the maximum time interval an ARQ block shall be managed by the transmitter ARQ state machine, once initial transmission of the block has occurred the time interval the receiver shall wait after successful reception of a block that does not result in advancement of
ARQ_RX_WINDOW_START, before
6

IEEE C802.16m-09/2926r1 advancing
ARQ_RX_WINDOW_START
Convergence sublayer capabilities
MAXIMUM_
ARQ_BUFFER_SIZE
The maximum ARQ buffer size
Multicarrier capabilities
Capabilities for interference mitigation support
DL PMI coordination capability
DL
DL collaborative
MIMO capability closed-loop multi-BS multi-BS macro diversity capability
UL PMI combination capability
E-MBS capabilities
0b00: No MC modes
0b01: Multicarrier aggregation
0b10: Multicarrier switching
0b11: Both multicarrier aggregation and switching
0: AMS is DL PMI coordination capable
1: AMS is not DL PMI coordination capable
0: AMS is DL collaborative multi-BS
MIMO capable
1: AMS is not DL collaborative multi-
BS MIMO capable
0: AMS is DL closed-loop multi-BS macro diversity capable
1: AMS is not DL closed-loop multi-
BS macro diversity capable
0: AMS is UL PMI combination capable
1: AMS is not UL PMI combination capable
If Bit#0 is set to 1, it indicates E-MBS in Serving ABS only is supported.
If Bit#1 is set to 1, it indicates macro diversity multi ABS E-MBS is supported.
If Bit#2 is set to 1, it indicates nonmacro-diversity multi ABS E-MBS is supported.
If all Bit#0~Bit#2 are set to 0, it indicates no E-MBS is supported.
Classification/PHS options and SDU encapsulation support
Maximum number of classification rules
ROHC support
PHS support
Indicates which classification/PHS options and SDU encapsulation the
AMS supports
Maximum number of admitted classification rules that the AMS supports.
Indicates the level of ROHC support.
Indicates the level of PHS support.
Supported-IP-Versions IE
Indicates whether the AMS supports
IPv4, IPv6 or both.
7

4
5
6
1
2
3
IEEE C802.16m-09/2926r1
Host-Configuration-Capability-Indicator IE
0b00: reserved
0b01: IPv4 support
0b10: IPv6 support
0b11: both IPv4 and IPv6 support
Indicates whether the AMS supports the capability of configuring host using the received parameters through the
AAI_REG-RSP message. (One bit indicator) This shall be omitted if
Requested-Host-Configurations IE is included in the message.
Host configuration capabilities parameters and
Requested-Host-Configurations IE
Includes requested host configuration options in DHCP Options format. If included, this IE indicates that the
AMS supports host configuration using
AAI_REG-RSP message, and Host-
Configuration-Capability-Indicator IE shall be omitted.
Notes
If the Supported-IP-Versions IE indicates both IPv4 and IPv6 capable, it means the AMS supports dual stack of IPv4/IPv6.
[ Modify the Table 690 in Section 16.2.3.8 of 802.16m/D3 as follows.
]
A MS capability negotiation parameters
ARQ parameters
Table 690 – Parameters for AAI_REG-RSP message
Name
ARQ_SN_MODULUS
ARQ_WINDOW_SIZE
Value the number of unique SN values; default =2^10 the maximum number of ARQ blocks with consecutive SN in the sliding window of ARQ blocks
ARQ_SUB_BLOCK_SIZE
ARQ_BLOCK_LIFETIME
ARQ sub-block length when ARQ block is fragmented into ARQ subblocks prior to retransmission with rearrangement the maximum time interval an ARQ block shall be managed by the transmitter ARQ state machine, once initial transmission of the block has occurred
8

IEEE C802.16m-09/2926r1
Capabilities for interference mitigation support
LBS capabilities
ARQ_RX_PURGE_TIMEOUT the time interval the receiver shall wait after successful reception of a block that does not result in advancement of
ARQ_RX_WINDOW_START, before advancing
ARQ_RX_WINDOW_START
MAXIMUM_
ARQ_BUFFER_SIZE
The maximum ARQ buffer size
DL PMI coordination capability
DL collaborative multi-BS
MIMO capability
0: AMS is DL PMI coordination capable
1: AMS is not DL PMI coordination capable
0: AMS is DL collaborative multi-BS
MIMO capable
1: AMS is not DL collaborative multi-
BS MIMO capable
DL closed-loop multi-BS macro diversity capability
0: AMS is DL closed-loop multi-BS macro diversity capable
1: AMS is not DL closed-loop multi-
BS macro diversity capable
UL PMI combination capability
Capability for support A-GPS method
TBD
Muticarrier capabilities
E-MBS capabilities
0: AMS is UL PMI combination capable
1: AMS is not UL PMI combination capable
0b0: no support
0b1: support
TBD
0b00: No MC modes
0b01: Multicarrier Aggregation
0b10: Multicarrier Switching
0b11: Both Multicarrier aggregation and switching
If Bit#0 is set to 1, it indicates E-MBS in Serving ABS only is supported.
If Bit#1 is set to 1, it indicates macro diversity multi ABS E-MBS is supported.
If Bit#2 is set to 1, it indicates nonmacro-diversity multi ABS E-MBS is supported.
If all Bit#0~Bit#2 are set to 0, it indicates no E-MBS is supported.
9

Convergence sublayer capabilities
Classification/PHS options and SDU encapsulation support
Maximum number of classification rules
ROHC support
IEEE C802.16m-09/2926r1 indicates which classification/PHS options and SDU encapsulation the
AMS supports
Maximum number of admitted classification rules that the AMS supports.
Indicates the level of ROHC support.
PHS support Indicates the level of PHS support.
1
2
3
4
Host configuration capabilities and its parameters
Resource_Retain_Time
IP-Service-Type IE
IPv4-Host-Address IE
IPv6-Home-Network-Prefix IE
Additional-Host-Configurations IE
Number of frames that the serving
ABS shall retain the AMS resource.
Indicates which IP service will be used, the value is one of following:
IPv4-Service
IPv6-Service
IPv4/IPv6-Dual-Mode-Service
The allocated IPv4 Host Address for the AMS.
Size: 4 octet
The allocated IPv6 Home Network
Prefix for the AMS.
Size: 8 octet
Includes additional host configuration options in DHCP Options format as detailed in [3], [4]
5
6
7
8
9
[1] IEEE P802.16m/D3, “DRAFT Amendment to IEEE Standard for Local and metropolitan area networks;
Part 16: Air Interface for Broadband Wireless Access systems; Advanced Air Interface,” December 2009
1
0