IEEE C802.16n-11/0173r1
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Clarification on Section Number and Title related to Direct Communication
Date
Submitted
2011-09-14
Source(s)
E-mail:
Eunkyung Kim, Sungcheol Chang,
ekkim@etri.re.kr
Won-Ik Kim, Seokki Kim,
Sungkyung Kim, Miyoung Yun,
Hyun scchang@etri.re.kr
Lee, Chulsik Yoon, Kwangjae Lim
ETRI
Re:
“IEEE 802.16n-11/0013r1,” in response to Call for Comments on 802.16n (GRIDMAN) AWD
Abstract
Text clarification related to section number and section title on direct communication in 802.16n
Purpose
To discuss and adopt the proposed text in the AWD of 802.16n
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
1
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
Clarification on Section Number and Title related to Direct Communication
Eunkyung Kim, Sungcheol Chang, Won-Ik Kim, Seokki Kim, Sungkyung Kim, Miyoung Yun, Hyun
Lee, Chulsik Yoon, Kwangjae Lim
ETRI
Introductions
IEEE 802.16n AWD [4] describes some functional description based on the 802.16n SRD [1]. In order to
understand clearly the operation of direct communication including forwarding to network and path
management, section number and title need to clarify as follows:
-
17.2.2 Direct communication between HR-MSs
11
12
o this subsection describes direct communication to support HR-BS coordinated and talk-around,
which should be separated clearly with same level
13
o 17.2.2.1 General Description
14
o 17.2.2.2 HR-BS coordinated direct communication
15

includes moving 17.2.2.2 – 17.2.2.5 to new subsection 17.2.2.2.1 – 17.2.2.2.4
16

including power control (17.2.2.7) as new subsection 17.2.2.2.5
17
18
o 17.2.2.617.2.2.3 Talk-around Direct Communication
-
17.2.3 HR-MS Forwarding to Network
19
20
o this subsection describes forwarding to network to support HR-BS coordinated and talk-around,
which should be separated clearly with same level
21
22
o 17.2.3.2 HR-MS forwarding to network using BS-coordinate direct communication
 including moving 17.2.3.2 – 17.2.3.4 to new subsection 17.2.3.2.1 – 17.2.3.2.3
23
-
17.2.7 Path Discovery and Management
24
25
o this section describes path discover and management to support direct communication SPOF
recovery, which should be separated clearly with same level
26
27
o 17.2.7.1 Path discovery and management under BS-coordinate direct communication as well as
forwarding to network
28

including moving the section 17.2.7.1 to 17.2.7.1.1
29

including moving the section 17.2.7.3 to 17.2.7.1.2
30
31
32
33
34
35
o 17.2.7.2 Robustness against SPOF
-
17.3.2, 17.3.3 & 17.3.7 need to be modified similarly to the 17.2.x.
References
[1] IEEE 802.16n-10/0048r2, “802.16n System Requirements Document including SARM annex,” July 2011.
[2] IEEE Std. 802.16TM-2009, “IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface
for Broadband Wireless Access Systems,” May 2009.
2
IEEE C802.16n-11/0173r1
1
2
3
4
[3] IEEE 802.16mTM-2011, IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface for
Broadband Wireless Access Systems; Amendment 3: Advanced Air Interface,” May 2011.
[4] IEEE 802.16n-11/0015, “802.16n Amendment Working Draft,” August 2011.
5
Proposed Text for the 802.16n Amendment Working Document (AWD)
6

Note:
7

The text in BLACK color: the existing text in the 802.16n Amendment Draft Standard
8

The text in RED color: the removal of existing 802.16n Amendment Draft Standard Text
9

The text in BLUE color: the new text added to the 802.16n Amendment Draft Standard Text
10
11
[-------------------------------------------------Start of Text Proposal---------------------------------------------------]
12
13
[Remedy1: Adopt the following change in from line 24 , page 65 to line 32, page 66 in the
802.16n AWD.]
14
15
16
17
18
19
20
21
22
23
24
25
17.2.2 Direct communication between HR-MSs
17.2.2.1 General Description
In HR-MS direct communication, the two communicating HR-MSs are the source and the sink of data. The data
packets are passed from upper layers to MAC at the source HR-MS and back to upper layers at the sink HR-MS.
Data packets are exchanged between the two HR-MSs directly or by passing through another HR-MS.

HR-MS direct communication is applicable when 1) the two HR-MSs are in coverage of and are directly
associated to an HR infrastructure station; 2) one HR-MS is in coverage of and directly associated to an HR
infrastructure station, while the other HR-MS is out of coverage of any HR infrastructure stations; 3) the two
HR-MSs are out of coverage of any HR infrastructure stations.
26
27
28
29
Resource for HR-MS direct communication can be allocated by the HR infrastructure station for cases (1) and
(2).

30

31
32
33
34
-
The operation of HR-MSs shall not interfere with any existing infrastructure stations. When HR-MS cannot
receive any BS preamble from any infrastructure station and HR-MS direct communication without
infrastructure is permitted by device configuration, HR-MSs are allowed to communicate with each other in
the same band without getting permission from infrastructure stations.
35
36
37
38
-
A Coordinator is selected for the coordination of transmission among HR-MSs. Until a coordinator is
selected, an HR-MS is only allowed to transmit signals necessary to enable coordinator selection. To avoid
collisions among HR-MSs in coordinator selection, the HR-MS follow a collision avoidance procedure. The
procedure is defined in 17.2.2.5.
39
-
A coordinator shall function as a simplified HR-BS except it may not support handover. How to select a
For case-3, direct communications between HR-MSs shall satisfy:
3
IEEE C802.16n-11/0173r1
1
2
coordinator among HR-MSs shall follow the operation described in TBD.
-
A coordinator supports the following topologies:
3
4

HR-MS linked to the coordinator and the pair is the source and sink of data. This topology is
implemented through the local source and sink capability of the HR-MS.
5
6

Two HR-MS linked to the coordinator and the two HR-MS are the source and sink of data. This
topology is implemented through the local forwarding capability of the HR-BS.
7
8

A forwarding HR-MS forwards data of a forwarded HR-MS to the coordinator. This topology is
implemented through the HR-BS capability to support HR-MS forwarding operation.
9
10
11

Two HR-MS are linked (DC) and are the source and sink of data to each other under the control
of the coordinator. This topology is implemented through the HR-BS ability to support DC
between its subordinates.
12
13
14
-
The coordinator and any HR-MS that are communicating through the coordinator shall continue cell search
operation and shall cease DC operation as soon as the criteria for DC and prevention of interference above
are not met.
15
16
17
HR-MS direct communication using centralized resource allocated by HR-BS, that is called BS-coordinated direct
communication, is described in 17.2.2.2.
18
19
HR-MS direct communication using distributed resource allocation among nearby HR-MSs, that is called talkaround direct communication, is described in 17.2.2.6.17.2.2.3.
20
17.2.2.2 BS-coordinate direct communication
21
22
23
Resource for HR-MS direct communication can be allocated by the HR infrastructure station for cases (1) and
(2).
24
For case-3, direct communications between HR-MSs shall satisfy:
25
26
27
28
-
The operation of HR-MSs shall not interfere with any existing infrastructure stations. When HR-MS cannot
receive any BS preamble from any infrastructure station and HR-MS direct communication without
infrastructure is permitted by device configuration, HR-MSs are allowed to communicate with each other in
the same band without getting permission from infrastructure stations.
29
30
31
32
-
A Coordinator is selected for the coordination of transmission among HR-MSs. Until a coordinator is
selected, an HR-MS is only allowed to transmit signals necessary to enable coordinator selection. To avoid
collisions among HR-MSs in coordinator selection, the HR-MS follow a collision avoidance procedure. The
procedure is defined in 17.2.2.2.4.
33
34
-
A coordinator shall function as a simplified HR-BS except it may not support handover. How to select a
coordinator among HR-MSs shall follow the operation described in TBD.
35
-
A coordinator supports the following topologies:
36
37

HR-MS linked to the coordinator and the pair is the source and sink of data. This topology is
implemented through the local source and sink capability of the HR-MS.
38
39

Two HR-MS linked to the coordinator and the two HR-MS are the source and sink of data. This
topology is implemented through the local forwarding capability of the HR-BS.
4
IEEE C802.16n-11/0173r1
1
2

A forwarding HR-MS forwards data of a forwarded HR-MS to the coordinator. This topology is
implemented through the HR-BS capability to support HR-MS forwarding operation.
3
4
5

Two HR-MS are linked (DC) and are the source and sink of data to each other under the control
of the coordinator. This topology is implemented through the HR-BS ability to support DC
between its subordinates.
6
7
8
-
The coordinator and any HR-MS that are communicating through the coordinator shall continue cell search
operation and shall cease DC operation as soon as the criteria for DC and prevention of interference above
are not met.
9
10
[Remedy2: Adopt the following change in line 34, page 66 in the 802.16n AWD.]
11
17.2.2.217.2.2.2.1 Frame Structure and Resource Allocation
12
13
[Remedy3: Adopt the following change in line 14-19, page 67 in the 802.16n AWD.]
14
15
16
17
18
19
20
17.2.2.317.2.2.2.2 Synchronization between HR-MSs involving in HR-MS DC/FTN
21
22
[Remedy4: Adopt the following change the section number 17.2.2.3.1 to 17.2.2.3.3 in the
802.16n AWD as indicates:]
23
17.2.2.3.117.2.2.2.2.1 Use case 1: Both HR-MSs are within the coverage of HR-BS/RS
This section describes the process of maintaining synchronization between two HR-MSs that communicate directly
with each other under HR-MS DC and FTN. The process is employed after HR-MS DC/FTN has been setup, and
therefore should be differentiated from the discovery process described in 17.3.7.1.217.2.7.1.1.2. Synchronization
between HR-MSs is classified into two levels:
24
25
26
17.2.2.3.217.2.2.2.2.2 Use case 2: one HR-MS is inside and the other is outside the coverage of HR-BS/RS
27
17.2.2.3.317.2.2.2.2.3 Use case 3: MS-MS direct communications; there is no HR-BS/RS
28
29
30
[Remedy5: Adopt the following change the section number 17.2.2.4 & 17.2.2.4.1 including
subsection number in the 802.16n AWD.]
31
32
17.2.2.417.2.2.2.3 HR-MS Direct Communication with Infrastructure Stations
33
34
35
17.2.2.4.117.2.2.2.3.1 Direct Communication Link Management
17.2.2.4.1.117.2.2.2.3.1.1 Direct Communication Link Creation
36
37
17.2.2.4.1.217.2.2.2.3.1.2 Direct Communication Link Deletion
5
IEEE C802.16n-11/0173r1
1
2
17.2.2.4.1.317.2.2.2.3.1.3 Direct Communication Link Report
3
4
[Remedy6: Adopt the following change in line 4-12, page 73 in the 802.16n AWD.]
5
6
7
8
9
10
11
12
13
14
17.2.2.4.217.2.2.2.3.2 Direct communication service flow management
15
16
17
18
17.2.2.4.2.217.2.2.2.3.2.2 Modification and Deletion of Dynamic Service Flow over direct communication link
17.2.2.4.2.117.2.2.2.3.2.1 Service flow creation over direct communication link
After a direct communication link has been setup between the source and destination HR-MS, the source HR-MS can
setup flows over the direct communication link.
A direct communication setup protocol is illustrated in Figure 802 and described in detail in 17.2.2.4. 2.3.17.2.2.2.3.2.3
[Remedy7: Adopt the following change in line 23-27, page 73 in the 802.16n AWD.]
In addition to the methods presented in 17.2.2.4.2.317.2.2.2.3.2.3 for creating service flows, protocols are
defined for modifying and deleting service flows; see 17.2.2.4.2.417.2.2.2.3.2.4 and 17.2.2.4.2.517.2.2.2.3.2.5.
19
20
21
[Remedy8: Adopt the following change the section number 17.2.2.4.2.3 to 17.2.2.4.2.6
including subsection numbers in the 802.16n AWD as indicates:]
22
17.2.2.4. 2.317.2.2.2.3.2.3 Dynamic Service Addition
23
24
17.2.2.4.2.417.2.2.2.3.2.4 Dynamic Service Change
25
26
17.2.2.4.2.517.2.2.2.3.2.5 Dynamic Service Deletion
27
28
29
30
17.2.2.4.2.617.2.2.2.3.2.6 Management Messages
17.2.2.4.2.6.117.2.2.2.3.2.6.1 DSA_REQ
31
32
17.2.2.4.2.6.217.2.2.2.3.2.6.2 DSA_RSP
33
34
17.2.2.4.2.6.317.2.2.2.3.2.6.3 DSA_ACK
35
36
17.2.2.4.2.6.417.2.2.2.3.2.6.4 DSX_RVD
37
6
IEEE C802.16n-11/0173r1
1
2
[Remedy9: Adopt the following change of section number 17.2.2.5 including subsection
number in the 802.16n AWD as indicates:]
3
17.2.2.517.2.2.2.4 HR-MS Discovery for Direct Communication without Infrastructure
4
5
17.2.2.5.117.2.2.2.4.1 DC_DISCOV_Message
6
7
17.2.2.5.217.2.2.2.4.2 Encoding of DC_DISCOV_IEs
8
9
17.2.2.5.2.117.2.2.2.4.2.1 DC_DISCOV_NODE_NAME
10
11
17.2.2.5.2.217.2.2.2.4.2.2 DC_DISCOV_NBR_ADDR
12
13
17.2.2.5.2.317.2.2.2.4.2.3 DC_DISCOV_INVITE
14
15
17.2.2.5.2.1.417.2.2.1.4.2.1.4 DC_DISCOV_INVITE_ACCEPT
16
17
17.2.2.5.2.1.517.2.2.2.4.2.1.5 DC_DISCOV_INVITE_REJECT
18
19
17.2.2.5.2.1.617.2.2.2.4.2.1.6 DC_DISCOV_DATA
20
21
22
[Remedy10: Adopt the following change of section number 17.2.2.6 including subsection
number in the 802.16n AWD as indicates:]
23
17.2.2.617.2.2.3 Talk-around Direct Communication
24
25
17.2.2.6.117.2.2.3.1 Key management for talk-around direct communication
26
27
28
[Remedy11: Adopt the following change(move to the end of 17.2.2.2) of section number
17.2.2.7 including subsection number in the 802.16n AWD as indicates:]
29
30
31
32
33
34
35
17.2.2.717.2.2.2.5 Power control for mobile to mobile communication
17.2.2.7.117.2.2.2.5.1 Power control for two HR-MS associated with an HR-BS
36
[Remedy12: Adopt the following change in line 2-39, page 82 in the 802.16n AWD.]
17.2.2.7.217.2.2.2.5.2 Power control for one HR-MS associated with an HR-BS
17.2.2.7.317.2.2.2.5.3 Power control for no HR-MS associated with an HR-BS
7
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
17.2.3 HR-MS Forwarding to Network
27
17.2.3.217.2.3.2.1 Frame structure and resource allocation
28
See 17.2.2.2.1
29
17.2.3.317.2.3.2.2 Synchronization (this section is identical to 17.2.2.317.2.2.2.2)
30
31
32
33
34
35
36
37
38
39
40
41
42
43
See 17.2.2.317.2.2.2.2
17.2.3.1 General Description
In HR-MS Forwarding to Network, an HR-MS forwards user data and control signaling between an HR-MS and
an HR infrastructure station. The user data and control signaling do not go through higher layer at the
forwarding HR-MS. The origination and termination of the user data and control signaling are at the forwarded
HR-MS and the HR infrastructure station respectively and vice versa.
HR-MS Forwarding to Network is applicable when 1) the forwarded HR-MS and the forwarding HR-MS are in
coverage of and directly associated to an infrastructure station; 2) the forwarding HR-MS is in coverage of and
directly associated to an HR infrastructure station, while the forwarded HR-MS is out of coverage of any HR
infrastructure stations.
Under BS-coordinate direction communication described in 17.2.2.2, HR-MS forwarding to network is
described in 17.2.3.2.
Using talk-around direct communication described in 17.2.2.3, HR-MS forwarding to network is described in
17.2.3.3.
17.2.3.2 HR-MS forwarding to network using BS-coordinate direct communication
Resource for HR-MS Forwarding to Network can be allocated by the HR infrastructure station with which the
forwarding HR-MS is associated.
17.2.3.417.2.3.2.3 Bandwidth Requests sent from Forwarded HR-MS
For use case 2, an out-of-coverage forwarded HR-MS can request bandwidth by transmitting some known
sequences (Bandwidth Request (BR) preambles) toward the forwarding HR-MS.
The process can be described as follows.
- Serving HR-BS/RS schedules resources in an uplink subframe for forwarded HR-MSs to transmit BR
messages to their corresponding forwarding HR-MS.
- The resource allocation information is conveyed to the forwarded HR-MS.
- The forwarding HR-MS listens to bandwidth requests at times and resources indicated by the HR-BS. The
forwarded HR-MS may transmit bandwidth requests using these resources.
- The forwarding HR-MS, upon receiving BR messages from one of its forwarded HR-MS, forwards the
requests to serving HR-BS/RS.
8
IEEE C802.16n-11/0173r1
1
2
-
Any resource assignment from the HR-BS is forwarded to the forwarding HR-MS.
3
17.2.3.3 HR-MS forwarding to network using talk-around direct communication
4
5
[Remedy13: Adopt the following change in line 34-36, page 83 in the 802.16n AWD.]
6
17.2.7 Path Discovery and Management
7
8
9
Path discovery and management, supporting HR-MS direct communication described in 17.2.2.2 and HR-MS
forwarding to network described in 17.2.3.2, is described in 17.2.7.1.
10
Path discovery and management supporting robustness against SPOF is described in 17.2.7.2.
11
12
13
14
17.2.7.1 Path discovery and management under BS-coordinate direct communication as well as
forwarding to network
15
17.2.7.117.2.7.1.1 HR-MS Neighbor Discovery
16
17
18
[Remedy14: Adopt the following change of section number 17.2.7.1.1 to 17.2.7.1.2 in the
802.16n AWD as indicates:]
19
17.2.7.1.117.2.7.1.1.1 Neighbor Discovery among associated HR-MSs (Use Case 1)
20
21
17.2.7.1.217.2.7.1.1.2 HR-MS Discover Network Infrastructure
22
23
[Remedy15: Add the following text in line 6, page 85 in the 802.16n AWD.]
24
17.2.7.1.2 Alternative path to another HR-MS during HR-MS forwarding to network operation
25
26
27
28
29
30
31
32
33
34
35
36
37
HR-MSs capable of forwarding to the network may share the MAC context information with the HR-MS
performing forwarding to the network.
To support HR-MS forwarding to network using HR-MS forwarding to network performed by another HR-MS,
either HR-BS or HR-MS may prepare the alternative path.
To prepare the alternative path by an HR-BS, the HR-BS performs operation as follows:
a) neighbor discovery as described in 17.2.7.1.1.1
b) collecting HR-MS’ neighbor information as described in 17.2.7.1.1.1
c) determining the alternative path for HR-MS
d) informing HR-MS about its alternative path information
To prepare the alternative path by an HR-MS, the HR-MS and its serving HR-BS perform operation as follows:
a) An HR-MS transmit AP-NBR-REQ to the HR-BS to initiate the neighbor discovery process
9
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
b) After the HR-BS receives the AP-NBR-REQ, the HR-BS performs the neighbor discovery as described
in 17.2.7.1.1.1
c) The HR-BS collects the neighbor information of requesting HR-MS as described in 17.2.7.1.1.1
d) The HR-BS transmits AP-NBR-REP message to HR-MS, where the AP-NBR-REP includes the
neighbor information of requesting HR-MS.
e) The HR-MS determines alternative path by itself based on its received neighbor information in the APNBR-REP message, but how to determine is out of scope of this specification
[Remedy16: remove the following text in line 13-40, page 86 in the 802.16n AWD.]
17.2.7.3 Preparation for Alternative path to support fast network reentry to the neighbor HR-MS
HR-MSs capable of forwarding to the network and/or multimode operation shall share the MAC context
information with the HR-MS performing local forwarding to the network.
To support fast network reentry to the neighbor HR-MSs, either HR-BS or HR-MS may prepare the alternative
path.
To prepare the alternative path by an HR-BS, the HR-BS shall perform operation as follows:
a) neighbor discovery as described in 17.2.7.1.1
b) collecting HR-MS’ neighbor information as described in 17.2.7.1.1
c) determines the alternative path for HR-MS
d) informs HR-MS about its alternative path information
To prepare the alternative path by an HR-MS, following operation shall be performed by HR-MS and HR-BS:
a) An HR-MS transmit AP-NBR-REQ to the HR-BS to initiate the neighbor discovery process
b) HR-BS received AP-NBR-REQ, performs the neighbor discovery as described in 17.2.7.1.1
c) HR-BS collects the neighbor information of requesting HR-MS as described in 17.2.7.1.1
d) HR-BS transmits AP-NBR-REP message to HR-MS which includes the neighbor information of
requesting HR-MS.
e) HR-MS determines alternative path by itself based on its received neighbor information, but how to
determine is out of scope of this specification
32
33
34
[Remedy17: Adopt the following change in from line 15, page 120 to line 26, page 121 in the
802.16n AWD.]
35
17.3.2 Direct communication between HR-MSs
36
37
38
39
40
41
42
43
17.3.2.1 General Description
In HR-MS direct communication, the two communicating HR-MSs are the source and the sink of data. The data
packets are passed from upper layers to MAC at the source HR-MS and back to upper layers at the sink HR-MS.
Data packets are exchanged between the two HR-MSs directly or by passing through another HR-MS.
HR-MS direct communication is applicable when 1) the two HR-MSs are in coverage of and are directly
associated to an HR infrastructure station; 2) one HR-MS is in coverage of and directly associated to an HR
10
IEEE C802.16n-11/0173r1
1
2
infrastructure station, while the other HR-MS is out of coverage of any HR infrastructure stations; 3) the two
HR-MSs are out of coverage of any HR infrastructure stations.
3
4
5
6
Resource for HR-MS direct communication can be allocated by the HR infrastructure station for cases (1) and
(2).
7
For case-3, direct communications between HR-MSs shall satisfy:
8
9
10
11
-
The operation of HR-MSs shall not interfere with any existing infrastructure stations. When HR-MS cannot
receive any BS preamble from any infrastructure station and HR-MS direct communication without
infrastructure is permitted by device configuration, HR-MSs are allowed to communicate with each other in
the same band without getting permission from infrastructure stations.
12
13
14
15
-
A Coordinator is selected for the coordination of transmission among HR-MSs. Until a coordinator is
selected, an HR-MS is only allowed to transmit signals necessary to enable coordinator selection. To avoid
collisions among HR-MSs in coordinator selection, the HR-MS follow a collision avoidance procedure. The
procedure is defined in 17.3.2.5.
16
17
-
A coordinator shall function as a simplified HR-BS except it may not support handover. How to select a
coordinator among HR-MSs shall follow the operation described in TBD.
18
-
A coordinator supports the following topologies:
19
20

HR-MS linked to the coordinator and the pair is the source and sink of data. This topology is
implemented through the local source and sink capability of the HR-MS.
21
22

Two HR-MS linked to the coordinator and the two HR-MS are the source and sink of data. This
topology is implemented through the local forwarding capability of the HR-BS.
23
24

A forwarding HR-MS forwards data of a forwarded HR-MS to the coordinator. This topology is
implemented through the HR-BS capability to support HR-MS forwarding operation.
25
26
27

Two HR-MS are linked (DC) and are the source and sink of data to each other under the control
of the coordinator. This topology is implemented through the HR-BS ability to support DC
between its subordinates.
28
29
30
31
32
33
34
35
36
37
38
39
-
The coordinator and any HR-MS that are communicating through the coordinator shall continue cell search
operation and shall cease DC operation as soon as the criteria for DC and prevention of interference above
are not met.
HR-MS direct communication using centralized resource allocation allocated by HR-BS, that is called BS-coordinated
direct communication, is described in 17.3.2.2.
Resource for HR-MS direct communication may be allocated in a distributed manner among nearby HR-MSs
independent of infrastructure node deployment for cases (1), (2), and (3).
HR-MS direct communication using distributed resource allocation among nearby HR-MSs, that is called talkaround direct communication, is described in 17.3.2.6.17.3.2.3.
40
11
IEEE C802.16n-11/0173r1
1
17.3.2.2 BS-coordinate direct communication
2
3
4
5
Resource for HR-MS direct communication can be allocated by the HR infrastructure station for cases (1) and
(2).
6
For case-3, direct communications between HR-MSs shall satisfy:
7
8
9
10
-
The operation of HR-MSs shall not interfere with any existing infrastructure stations. When HR-MS cannot
receive any BS preamble from any infrastructure station and HR-MS direct communication without
infrastructure is permitted by device configuration, HR-MSs are allowed to communicate with each other in
the same band without getting permission from infrastructure stations.
11
12
13
14
-
A Coordinator is selected for the coordination of transmission among HR-MSs. Until a coordinator is
selected, an HR-MS is only allowed to transmit signals necessary to enable coordinator selection. To avoid
collisions among HR-MSs in coordinator selection, the HR-MS follow a collision avoidance procedure. The
procedure is defined in 17.3.2.2.4.
15
16
-
A coordinator shall function as a simplified HR-BS except it may not support handover. How to select a
coordinator among HR-MSs shall follow the operation described in TBD.
17
-
A coordinator supports the following topologies:
18
19

HR-MS linked to the coordinator and the pair is the source and sink of data. This topology is
implemented through the local source and sink capability of the HR-MS.
20
21

Two HR-MS linked to the coordinator and the two HR-MS are the source and sink of data. This
topology is implemented through the local forwarding capability of the HR-BS.
22
23

A forwarding HR-MS forwards data of a forwarded HR-MS to the coordinator. This topology is
implemented through the HR-BS capability to support HR-MS forwarding operation.
24
25
26

Two HR-MS are linked (DC) and are the source and sink of data to each other under the control
of the coordinator. This topology is implemented through the HR-BS ability to support DC
between its subordinates.
27
28
29
-
The coordinator and any HR-MS that are communicating through the coordinator shall continue cell search
operation and shall cease DC operation as soon as the criteria for DC and prevention of interference above
are not met.
30
31
32
33
[Remedy18: Adopt the following replacement of section number 17.3.2.2 in the 802.16n
AWD as indicates:]
34
17.3.2.217.3.2.2.1 Frame Structure and Resource Allocation
35
36
[Remedy19: Adopt the following change in line 8-13, page 122 in the 802.16n AWD.]
37
38
17.3.2.317.3.2.2.2 Synchronization between HR-MSs involving in HR-MS DC/FTN
This section describes the process of maintaining synchronization between two HR-MSs that communicate
12
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
directly with each other under HR-MS DC and FTN. The process is employed after HR-MS DC/FTN has been
setup, and therefore should be differentiated from the discovery process described in 17.3.7.1.217.3.7.1.1.2.
Synchronization between HR-MSs is classified into two levels:
[Remedy20: Adopt the following replacement of section number 17.3.2.3.1 to 17.3.2.3.3 in
the 802.16n AWD as indicates:]
17.3.2.3.117.3.2.2.2.1 Use case 1: Both HR-MSs are within the coverage of HR-BS/RS
17.3.2.3.217.3.2.2.2.2 Use case 2: one HR-MS is inside and the other is outside the coverage of HR-BS/RS
17.3.2.3.317.3.2.2.2.3 Use case 3: MS-MS direct communications; there is no HR-BS/RS
[Remedy21: Adopt the following replacement of section number 17.3.2.4 – 17.3.2.5
including subsection numbers in the 802.16n AWD as indicates:]
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
17.3.2.417.3.2.2.3 HR-MS Direct Communication with Infrastructure Stations
33
17.3.2.5.117.3.2.2.4.1 DC_DISCOV_Message
17.3.2.4.117.3.2.2.3.1 Direct Communication Link Management
17.3.2.4.1.117.3.2.2.3.1.1 Direct Communication Link Creation
17.3.2.4.1.217.3.2.2.3.1.2 Direct Communication Link Deletion
17.3.2.4.1.317.3.2.2.3.1.3 Direct Communication Link Report
17.3.2.4.217.3.2.2.3.2 Direct communication service flow management
17.3.2.4.2.117.3.2.2.3.2.1 Direct communication service flow
17.3.2.4.2.217.3.2.2.3.2.2 Dynamic Service Flow Modification and Deletion
17.3.2.517.3.2.2.4 HR-MS Discovery for Direct Communication without Infrastructure
34
35
17.3.2.5.217.3.2.2.4.2 Encoding of DC_DISCOV_IEs
36
37
17.3.2.5.2.117.3.2.2.4.2.1 DC_DISCOV_NODE_NAME
38
39
17.3.2.5.2.217.3.2.2.4.2.2 DC_DISCOV_NBR_ADDR
40
41
17.3.2.5.2.317.3.2.2.4.2.3 DC_DISCOV_INVITE
42
13
IEEE C802.16n-11/0173r1
1
17.3.2.5.2.417.3.2.2.4.2.4 DC_DISCOV_INVITE_ACCEPT
2
3
17.3.2.5.2.417.3.2.2.4.2.5 DC_DISCOV_INVITE_REJECT
4
5
17.3.2.5.2.617.3.2.2.4.2.6 DC_DISCOV_DATA
6
7
8
[Remedy22: Adopt the following replacement of section number 17.3.2.3 – 17.3.2.6.11
including subsection numbers in the 802.16n AWD as indicates:]
9
10
17.3.2.617.3.2.3 Talk-around Direct Communication mode
11
12
13
17.3.2.6.117.3.2.3.1 Medium access control
17.3.2.6.1.117.3.2.3.1.1 Addressing
14
15
17.3.2.6.1.1.117.3.2.3.1.1.1 DC terminal identifier (DCTID)
16
17
17.3.2.6.1.1.217.3.2.3.1.1.2 DC group identifier (DCGID)
18
19
17.3.2.6.1.1.317.3.2.3.1.1.3 Flow identifier (FID)
20
21
17.3.2.6.1.217.3.2.3.1.2 MAC PDU formats
22
23
17.3.2.6.1.317.3.2.3.1.3 MAC control messages
24
25
17.3.2.6.1.3.117.3.2.3.1.3.1 DM-LEST-REQ
26
27
17.3.2.6.1.3.217.3.2.3.1.3.2 DM-LEST-RSP
28
29
17.3.2.6.1.3.317.3.2.3.1.3.3 DM-LREL-REQ
30
31
17.3.2.6.1.3.417.3.2.3.1.3.4 DM-LREL-RSP
32
33
17.3.2.6.1.3.517.3.2.3.1.3.5 DM-DSA-REQ
34
14
IEEE C802.16n-11/0173r1
1
17.3.2.6.1.3.617.3.2.3.1.3.6 DM-DSA-RSP
2
3
17.3.2.6.1.3.717.3.2.3.1.3.7 DM-DSA-ACK
4
5
17.3.2.6.1.3.817.3.2.3.1.3.8 DM-DSC-REQ
6
7
17.3.2.6.1.3.917.3.2.3.1.3.9 DM-DSC-RSP
8
9
17.3.2.6.1.3.1017.3.2.3.1.3.10 DM-DSC-ACK
10
11
17.3.2.6.1.3.1117.3.2.3.1.3.11 DM-DSD-REQ
12
13
17.3.2.6.1.3.1217.3.2.3.1.3.12 DM-DSD-RSP
14
15
17.3.2.6.1.3.1317.3.2.3.1.3.13 DM-DSD-ACK
16
17
17.3.2.6.1.3.1417.3.2.3.1.3.14 DM-MES-REQ
18
19
17.3.2.6.1.3.1517.3.2.3.1.3.15 DM-MES-RSP
20
21
17.3.2.6.1.3.1617.3.2.3.1.3.16 DM-MES-REP
22
23
17.3.2.6.1.3.1717.3.2.3.1.3.17 DM-RCHG-REQ
24
25
17.3.2.6.1.3.1817.3.2.3.1.3.18 DM-RCHG-RSP
26
27
17.3.2.6.1.3.1917.3.2.3.1.3.19 DM-TKN-REQ
28
29
17.3.2.6.1.3.2017.3.2.3.1.3.20 DM-TKN-RSP
30
31
17.3.2.6.1.3.2117.3.2.3.1.3.21 DM-TKN-HO
15
IEEE C802.16n-11/0173r1
1
2
17.3.2.6.1.3.2217.3.2.3.1.3.22 DM-LEST-CMD
3
4
17.3.2.6.1.3.2317.3.2.3.1.3.23 DM-LREL-CMD
5
6
17.3.2.6.1.3.2417.3.2.3.1.3.24 DM-DSA-CMD
7
8
17.3.2.6.1.3.2517.3.2.3.1.3.25 DM-DSC-CMD
9
10
17.3.2.6.1.3.2617.3.2.3.1.3.26 DM-DSD-CMD
11
12
17.3.2.6.1.3.2717.3.2.3.1.3.27 DM-MES-CMD
13
14
17.3.2.6.1.3.2817.3.2.3.1.3.28 DM-RCHG-CMD
15
16
17.3.2.6.1.3.2917.3.2.3.1.3.29 DM-TKN-ADV
17
18
17.3.2.6.1.417.3.2.3.1.4 Security
19
20
17.3.2.6.1.517.3.2.3.1.5 Connection management
21
22
17.3.2.6.1.5.117.3.2.3.1.5.1 Control connections
23
24
17.3.2.6.1.5.217.3.2.3.1.5.2 Transport connections
25
26
17.3.2.6.1.617.3.2.3.1.6 Link management
27
28
17.3.2.6.1.6.117.3.2.3.1.6.1 Synchronization
29
30
17.3.2.6.1.6.217.3.2.3.1.6.2 Link establishment
31
32
17.3.2.6.1.6.217.3.2.3.1.6.3 Link release
33
16
IEEE C802.16n-11/0173r1
1
17.3.2.6.1.717.3.2.3.1.7 QoS management
2
3
17.3.2.6.1.7.117.3.2.3.1.7.1 Service Flow Management
4
5
17.3.2.6.1.817.3.2.3.1.8 Token management
6
7
17.3.2.6.1.917.3.2.3.1.9 Resource management
8
9
17.3.2.6.1.1017.3.2.3.1.10 Measurement
10
11
17.3.2.6.1.1117.3.2.3.1.11 Support for two hop communication
12
13
14
15
[Remedy23: Adopt the following change in line 7-9, page 150 in the 802.16n AWD as
indicates:]
16
17
18
19
17.3.2.6.217.3.2.3.2 Physical layer
17.3.2.6.2.117.3.2.3.2.1 Frame structure
20
21
22
[Remedy24: Adopt the following change line 20-21, page 152 in the 802.16n AWD as
indicates:]
23
The detailed design of synchronization channel is described in 17.3.2.6.2.3.117.3.2.3.2.3.1
24
25
26
[Remedy25: Adopt the following change line 27-28, page 152 in the 802.16n AWD as
indicates:]
27
How to configure the resource of dedicated channel is discussed in described in 17.3.2.6.2.3.217.3.2.3.2.3.2.
28
29
30
[Remedy26: Adopt the following change line 21-22, page 153 in the 802.16n AWD as
indicates:]
31
The details of supplementary channel design are discussed in described in 17.3.2.6.2.3.317.3.2.3.2.3.3.
32
33
34
[Remedy27: Adopt the following replacement of section number 17.3.2.6.2.2 – 17.3.2.6.2.3
including subsection numbers in the 802.16n AWD as indicates:]
35
17
IEEE C802.16n-11/0173r1
1
2
3
17.3.2.6.2.217.3.2.3.2.2 Physical structure
17.3.2.6.2.2.3.217.3.2.3.2.2.3.2 Dedicated Channel
4
5
6
7
8
9
17.3.2.6.2.2.3.317.3.2.3.2.2.3.3 Supplementary Channel
17.3.2.6.2.317.3.2.3.2.3 Control structure
17.3.2.6.3.117.3.2.3.3.1 Synchronization channel
10
11
17.3.2.6.3.1.117.3.2.3.3.1.1 Synchronization channel structure
12
13
17.3.2.6.3.1.217.3.2.3.3.1.2 Preamble sequences for synchronization channel
14
15
17.3.2.6.3.1.317.3.2.3.3.1.3 Synchronization channel message
16
17
18
[Remedy28: Adopt the following replacement of section number 17.3.2.7 including
subsection numbers in the 802.16n AWD as indicates:]
19
17.3.2.717.3.2.2.5 Power control for mobile to mobile communication
20
17.3.2.7.117.3.2.2.5.1 Power control for two HR-MS associated with an HR-BS
21
22
17.3.2.7.217.3.2.2.5.2 Power control for one HR-MS associated with an HR-BS
23
24
17.3.2.7.317.3.2.2.5.3 Power control for no HR-MS associated with an HR-BS
25
26
27
[Remedy29: Adopt the following change line 5-32, page 161 in the 802.16n AWD as
indicates:]
28
29
30
31
32
33
34
35
36
37
17.3.3 HR-MS Forwarding to Network
17.3.3.1 General Description
In HR-MS Forwarding to Network, an HR-MS forwards user data and control signaling between an HR-MS and
an HR infrastructure station. The user data and control signaling do not go through higher layer at the
forwarding HR-MS. The origination and termination of the user data and control signaling are at the forwarded
HR-MS and the HR infrastructure station respectively and vice versa.
HR-MS Forwarding to Network is applicable when 1) the forwarded HR-MS and the forwarding HR-MS are in
coverage of and directly associated to an infrastructure station; 2) the forwarding HR-MS is in coverage of and
18
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
11
12
13
directly associated to an HR infrastructure station, while the forwarded HR-MS is out of coverage of any HR
infrastructure stations.
Under BS-coordinate direction communication described in 17.3.2.2, HR-MS forwarding to network is
described in 17.3.3.2.
Using talk-around direct communication described in 17.3.2.617.3.2.3, HR-MS forwarding to network is
described in 17.3.3.517.3.3.3.
17.3.3.2 HR-MS forwarding to network using BS-coordinate direct communication
Resource for HR-MS Forwarding to Network can be allocated by the HR infrastructure station with which the
forwarding HR-MS is associated.
14
15
17.3.3.217.3.3.2.1 Frame structure and Resource Allocation
16
See 17.3.3.217.3.3.2.1
17
17.3.3.317.3.3.2.2 Synchronization
18
19
20
21
See 17.3.2.317.3.3.2.2
22
23
[Remedy30: Adopt the following replacement of section number 17.3.3.5 including
subsection numbers in the 802.16n AWD as indicates:]
24
17.3.3.517.3.3.3 HR-MS forwarding to network using talk-around direct communication
17.3.3.417.3.3.2.3 Bandwidth Requests sent from Forwarded HR-MS
25
26
17.3.3.5.117.3.3.3.1 HR-MS discoveries
27
28
17.3.3.5.217.3.3.3.2 Forwarding connection management
29
30
17.3.3.5.2.117.3.3.3.2.1 Forwarding connection establishment
31
32
17.3.3.5.2.217.3.3.3.2.2 Forwarding connection release
33
34
17.3.3.5.317.3.3.3.3 QoS management
35
19
IEEE C802.16n-11/0173r1
1
2
3
[Remedy31: Adopt the following change line 6-8, page 165 in the 802.16n AWD as
indicates:]
4
17.3.7 Path Discovery and Management
5
6
7
Path discovery and management, supporting HR-MS direct communication described in 17.3.2.2 and HR-MS
forwarding to network described in 17.3.3.2, is described in 17.3.7.1.
8
Path discovery and management supporting robustness against SPOF is described in 17.3.7.2.
9
10
11
17.3.7.1 Path discovery and management under BS-coordinate direct communication as well as
forwarding to network
12
13
17.3.7.117.3.7.1.1 HR-MS Neighbor Discovery
14
15
[Remedy32: Adopt the following change line 20, page 165 in the 802.16n AWD as indicates:]
16
17.3.7.1.117.3.7.1.1.1 Neighbor Discovery among associated HR-MSs (Use Case 1)
17
18
[Remedy33: Adopt the following change line 7, page 166 in the 802.16n AWD as indicates:]
19
17.3.7.1.217.3.7.1.1.2 HR-MS Discover Network Infrastructure
20
21
22
[Remedy34: Adopt the following change line 20-26, page 166 in the 802.16n AWD as
indicates:]
23
24
25
26
27
28
29
The HR-BS may instruct HR-MS that are associated with it to transmit network configuration information
(NCI) at pre-defined resources relative to the preambles transmitted by the HR-MS. The NCI, when transmitted,
defines resources for access by the HR-MS that is not under HR-BS coverage. This corresponds to the coverage
extension procedure defined in 17.3.7.1.2.117.3.7.1.1.2.1. If NCI is omitted then access resources are defined by
the index and the sub-carrier set index of the SA-Preamble. This corresponds to the coverage extension
procedure defined in 17.3.7.1.2.217.3.7.1.1.2.2.
30
31
[Remedy35: Adopt the following replacement of section number 17.3.7.1.2.1 – 17.3.7.1.2.2 in
the 802.16n AWD as indicates:]
32
33
34
35
17.3.7.1.2.117.3.7.1.1.2.1 Coverage Extension with NCI Preceding Initial Ranging
36
[Remedy36: Add the following text in line 35, page 175 in the 802.16n AWD as indicates:]
37
17.3.7.1.2 Alternative path to another HR-MS during HR-MS forwarding to network operation
17.3.7.1.2.217.3.7.1.1.2.2 Coverage Extension with Initial Ranging Preceding NCI
20
IEEE C802.16n-11/0173r1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
HR-MSs capable of forwarding to the network may share the MAC context information with the HR-MS
performing forwarding to the network.
22
[Remedy37: remove the following text in line 1-28, page 177 in the 802.16n AWD.]
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
17.3.7.3 Preparation for Alternative path to support fast network reentry to the neighbor HR-MS
To support HR-MS forwarding to network using HR-MS forwarding to network performed by another HR-MS,
either HR-BS or HR-MS may prepare the alternative path.
To prepare the alternative path by an HR-BS, the HR-BS performs operation as follows:
a) neighbor discovery as described in 17.3.7.1.1.1
b) collecting HR-MS’ neighbor information as described in 17.3.7.1.1.1
c) determining the alternative path for HR-MS
d) informing HR-MS about its alternative path information
To prepare the alternative path by an HR-MS, the HR-MS and its serving HR-BS perform operation as follows:
a) An HR-MS transmit AP-NBR-REQ to the HR-BS to initiate the neighbor discovery process
b) After the HR-BS receives the AP-NBR-REQ, the HR-BS performs the neighbor discovery as described
in 17.2.7.1.1.1
c) The HR-BS collects the neighbor information of requesting HR-MS as described in 17.3.7.1.1.1
d) The HR-BS transmits AP-NBR-REP message to HR-MS, where the AP-NBR-REP includes the
neighbor information of requesting HR-MS.
e) The HR-MS determines alternative path by itself based on its received neighbor information in the APNBR-REP message, but how to determine is out of scope of this specification
HR-MSs capable of forwarding to the network and/or multimode operation shall share the MAC context
information with the HR-MS performing local forwarding to the network.
To support fast network reentry to the neighbor HR-MSs, either HR-BS or HR-MS may prepare the alternative
path.
To prepare the alternative path by an HR-BS, the HR-BS shall perform operation as follows:
a) neighbor discovery as described in 17.3.7.1.1
b) collecting HR-MS’ neighbor information as described in 17.3.7.1.1
c) determines the alternative path for HR-MS
d) informs HR-MS about its alternative path information
To prepare the alternative path by an HR-MS, following operation shall be performed by HR-MS and HR-BS:
a) An HR-MS transmit AP-NBR-REQ to the HR-BS to initiate the neighbor discovery process
b) HR-BS received AP-NBR-REQ, performs the neighbor discovery as described in 17.3.7.1.1
c) HR-BS collects the neighbor information of requesting HR-MS as described in 17.3.7.1.1
d) HR-BS transmits AP-NBR-REP message to HR-MS which includes the neighbor information of
requesting HR-MS
e) HR-MS determines alternative path by itself based on its received neighbor information, but how to
determine is out of scope of this specification
21
IEEE C802.16n-11/0173r1
1
2
[-------------------------------------------------End of Text Proposal----------------------------------------------------]
3
4
22