IEEE C802.16m-10/0979r1
1
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
E-MBS Service Establishment in IEEE P802.16m (16.9.2.1)
Date
Submitted
2010-08-18
Source(s)
Eunkyung Kim, Soojung Jung,
Jaesun Cha, Sungcheol Chang, Hyun Lee,
Chulsik Yoon
ETRI
138 Gajeongno, Yusong-gu, Daejeon,
305-700, KOREA
Re:
“P802.16m/D7,” in response to the IEEE 802.16 Working Group Sponsor Ballot Recirc #1
Abstract
E-MBS service establishment to start/change/end receiving E-MBS data on IEEE 802.16m
Amendment Draft Standard
Purpose
To discuss and adopt the proposed text in the next revision of 802.16m draft
Notice
Release
Patent
Policy
2
3
4
5
6
7
8
9
10
Voice: +82-42-860-5415
E-mail: ekkim@etri.re.kr
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>.
E-MBS Service Establishment in IEEE P802.16m (16.9.2.1)
Eunkyung Kim, Soojung Jung, Jaesun Cha, Sungcheol Chang, Hyun Lee, Chulsik Yoon
ETRI
Instructions
IEEE 802.16m Amendment Draft Standard [1] describes the Enhanced Multicast Broadcast Service (E-MBS).
According to the IEEE 802.16m Amendment Draft Standard [1], ABS sends AAI_DSA/DSC/DSD message
respectively to establish, change and delete E-MBS service flows. When E-MBS services involve multiple flows
the compact form of DSx with group parameter should be used to reduce overhead and signaling delay
1
IEEE C802.16m-10/0979r1
1
associated with E-MBS flow management.
2
3
However, due to variable scenario and charging system, E-MBS Service Establishment, which covers scenarios
as many as it can, should be defined.
4
5
6
7
8
9
10
11
Proposed Connection Establishment
Figure 1 shows the proposed connection establishment using action code and new message (i.e., AAI_EMBSREP). As shown Figure 1, the ABS may not know that which channel (E-MBS ID and FID) is served to AMS
but needs to know whether AMS receives E-MBS or not to apply charging after the successful procedure of
DSA. In the case of service charging and service scenario, the AMS may start receiving E-MBS with/without
notification to ABS. In order to use or not to use the AAI_EMBS-REP message, action code is proposed and if it
is set to 0, AAI_EMBS-REP should be transmitted from AMS to ABS to start receiving E-MBS. Otherwise, EMBS may start immediately after DSx procedure.
12
Capability Exchange using AAI_REGREQ/RSP described in 16.2.3.7 and 16.2.3.8
Connection Establishment using AAI_DSx
described in 16.2.3.46
Connection Established and AMS is ready to
receive E-MBS
Start receiving E-MBS
immediately?
No (action code = 0)
No
Yes
(action code = 1)
Receive AAI_EMBS-REP to start
receiving E-MBS from AMS?
Yes
AMS starts receiving E-MBS
13
14
Figure 1 – Procedure to start receiving E-MBS
15
2
IEEE C802.16m-10/0979r1
1
2
3
4
5
Connection Release
6
7
8
9
References
General E-MBS connection release is performed using AAI_DSD messages. However, to stop receiving E-MBS
without releasing the E-MBS connection, AAI_EMBS-REP message is used. In addition, to restart receiving EMBS, AAI_EMBS-REP message is also used.
[1] IEEE P802.16m/D7, “DRAFT Amendment to IEEE Standard for Local and metropolitan area networks;
Part 16: Air Interface for Broadband Wireless Access systems; Advanced Air Interface,” July 2010
10
11
Text Proposal for the 802.16m Amendment Draft Standard
12
The text in BLACK color: the existing text in the 802.16m Amendment Draft Standard
13
The text in RED color: the removal of existing 802.16m Amendment Draft Standard Text
14
The text in BLUE color: the new text added to the 802.16m Amendment Draft Standard Text
Note:
15
16
[-------------------------------------------------Start of Text Proposal---------------------------------------------------]
17
[Remedy1: Modify and add the following text in 16.9.2.1 of 802.16m/D7]
18
19
16.9.2.1 E-MBS Connection Establishment
20
The procedure of E-MBS Connection Establishment is showing in Figure xxx. The procedure includes
21
 Capability exchange using AAI_REG-REQ/RSP
22
 DSx procedure containing relevant E-MBS parameter to establish E-MBS connection
23
 Starting/Changing/Ending E-MBS service using AAI_E-MBS-REP
24
25
26
27
28
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 is described in 16.2.3.7 and
16.2.3.8.
29
30
31
When an AMS registers for receiving multicast and broadcast services, the serving ABS or the AMS may
initiate the DSA procedure for multicast and broadcast connections. The AMS’s discovery and registration of
the E-MBS services with the ABS through upper layer signaling are outside the scope of this standard.
32
To prepare for subsequent E-MBS operation, the AMS obtains the E-MBS related configuration information
3
IEEE C802.16m-10/0979r1
1
2
receiving AAI_SCD message and AAI_E-MBS-CFG message on the corresponding E-MBS carrier described in
Table 716 and Table 980.
3
4
The AMS learns the E-MBS_Zone_ID(s) to which the serving and neighboring ABS belongs through AAI_EMBS_CFG message.
5
6
7
8
9
The ABS sends AAI_DSA, AAI_DSC and AAI_DSD messaging respectively to establish, change and delete EMBS service flows. The AMS initiated DSx may also be supported. In addition the E-MBS service flows may
also be established optionally through upper layer signaling£¨which is outside the scope of this specification.
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.
10
11
12
The ABS sends the AAI_DSA-REQ/RSP to the AMS containing the relevant E-MBS parameters. It also
includes E-MBS IDs and FIDs, E-MBS zone IDs, E-MBS carrier information (physical carrier index). Selective
decoding of content is at the granularity of FID's.
13
14
15
16
17
If multicarrier feature is supported by the AMS and the ABS, the ABS should use AAI_DSA-REQ/RSP
message to redirect the AMS to AAI E-MBS zone of other carriers, if such redirection is needed.
In order to start receiving E-MBS or change/stop receiving E-MBS without releasing the E-MBS connection
allocated via AAI_DSA-REQ/RSP, the AAI_EMBS-REP message described in 16.2.3.x shall be transmitted
from AMS to ABS.
18
Capability Exchange using AAI_REGREQ/RSP described in 16.2.3.7 and 16.2.3.8
Connection Establishment using AAI_DSx
described in 16.2.3.46
Connection Established and AMS is ready to
receive E-MBS
No
Receive AAI_EMBS-REP to start
receiving E-MBS from AMS?
Yes
AMS starts receiving E-MBS
19
20
Figure xxx – Procedure of E-MBS connection Establishment to start receiving E-MBS
21
22
23
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.
4
IEEE C802.16m-10/0979r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
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 E-MBS IDs and
FIDs, Packet Classification Rule parameter(s), E-MBS Zone Identifier Assignment parameter. If the AMS has
no E-MBS IDs and FIDs information regarding the new E-MBS Zone, then the AMS is required to acquire EMBS IDs and FIDs context through the other procedures, i.e., location-update if AMS is in the idle mode and
handover if MS is in connected mode.
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.
[-------------------------------------------------End of Text Proposal----------------------------------------------------]
5