1 IEEE C802.

16n-10/0065
2
1

Project IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>

Title Proposed Protocol Structure for IEEE 802.16n

Date 2011-01-03
Submitted
E-mail:
Source(s) Eunkyung Kim, Sungcheol Chang,
ekkim@etri.re.kr
Sungkyung Kim, Hyun Lee, Chulsik
scchang@etri.re.kr
Yoon
ETRI

yb.chang@samsung.com
Jaehyuk Jang, Yeongmoon Son, ym1004.son@samsung.com
Youngbin Chang, Kyungkyu Kim, Jung
Je Son, Rakesh Taori
Samsung Electronics

Re: “IEEE 802.16gman-10/0042,” in response to the agreement by the Gridman TG at session #70
for the 3rd Teleconference

Abstract Protocol Structure on IEEE 802.16n SRD

Purpose To discuss and adopt the proposed text in the SRD of 802.16n
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It
Notice 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
Release 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:
Patent <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
Policy <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>.

3 1
4
 1 IEEE C802.16n-10/0065
2

1 Proposed Protocol Structure for IEEE 802.16n

2 Eunkyung Kim, Sungcheol Chang, Sungkyung Kim, Hyun Lee, Chulsik Yoon
3 ETRI
4
5 Jaehyuk Jang, Yeongmoon Son, Youngbin Chang, Kyungkyu Kim, Jung Je Son, Rakesh Taori
6 Samsung Electronics
7

8Introduction
9This document provides protocol structure as an annex of SRD(i.e., IEEE 802.16gman-10/0038r4[1]) in
10response to the agreement by the Gridman TG at session #70 for teleconference for SRAM.
11
12

13References
14[1] IEEE 802.16gman-10/0038r4, “(DRAFT) 802.16n System Requirements Documents,” November 2010.
15[2] IEEE Std. 802.16-2009, “IEEE Standard for Local and metropolitan area networks; Part 16: Air Interface
16 for Broadband Wireless Access Systems,” May 2009.
17[3] IEEE 802.16m-09/0034r3, “IEEE 802.16m System Description Document (SDD),” June 2010.
18g

19Proposed Protocol Architecture for the 802.16n System Requirement Document

20(SRD)
21 [-------------------------------------------------Start of Text Proposal---------------------------------------------------]
22
23[Remedy: Add the following text in the end of 802.16gman-10/0038r4]
24[Some highlighted change and enhancement to the IEEE 802.16m are shown in blue color.]

25
26Annex C: Protocol Structure
27Annex C.1 IEEE 802.16n Protocol Structure
28Figure XX shows the IEEE 802.16n Protocol Structure. As shown the figure, the IEEE 802.16n MAC is
29divided into two sublayers:
30 - Convergence Sublayer (CS)
31 - Common Part Sublayer (CPS)
32

3 2
4
 1 IEEE C802.16n-10/0065
2
Network
Network Layer
Layer

CS_SAP
CS_SAP

Convergence
Convergence sublayer
sublayer
Direct Enhanced System
System
Radio
Radio Resource
Resource Location
Location
communication multicast Relay
Relay Function
Function configuration
configuration
Management management
M_SAP

Management management
M_SAP

management management management

management Classification
Classification

Standalone Multi-Carrier
Multi-Carrier Mobility
Mobility Idle
Idle Mode
Mode
Priority Access MBS
MBS
management Support
Support management
management management
management
Header
Header suppression
suppression
C_SAP
C_SAP

Service
Service Flow
Flow and
and
Multi-mode Network
Network entry
entry Security
Security
Path management Self-Organization
Self-Organization Connection
Connection MAC_SAP
management managment
managment management
management MAC_SAP
Management
Management

Radio Resource Control and Management

(RRCM)
Fragmentation
Fragmentation and
and Packing
Packing

Medium Access Control (MAC)

QoS
QoS ARQ
ARQ

Multi-Radio
Multi-Radio Sleep
Sleep Mode
Mode
Coexistence
Coexistence Management
Management
Scheduling
Scheduling and
and
Resource
Resource Multiplexing
Multiplexing
MAC
MAC PDU
PDU formation
formation

PHY
PHY control
control
Encryption
Encryption
Data
Data Forwarding
Forwarding Interference
Interference Link
Link Adaptation
Adaptation (CQI,
(CQI, Control
Control signaling
signaling
Ranging
Ranging
Management
Management HARQ,
HARQ, power
power control)
control)

Control Plane Data Plane

Physical
Physical Layer
Layer
1

2 Figure XX: IEEE 802.16n Protocol Structure

3
4The MAC Common Part Sublayer is further classified into Radio Resource Control and Management (RRCM)
5functions and medium access control (MAC) functions. The RRCM functions fully reside on the control plane.
6The functions reside on the control and data planes. The RRCM functions include several functional blocks that
7are related to radio resource functions such as:
8 - Radio Resource Management: Indicates a block which adjusts radio network parameters based on the
9 traffic load, and also includes functions of load control (load balancing), admission, and interference
10 control.
11 - Mobility Management: Indicates a block which supports functions related to Intra-RAT/Inter-RAT
12 handover.
13 - Network-entry Management: Indicates a block which is in charge of initialization and access
14 procedures. The Network-entry Management block may generate management messages which are
15 needed during access procedures, i.e., ranging, basic capability negotiation, registration, and so on.
16 - Location Management: Indicates a block which is in charge of supporting location based service (LBS).
17 The Location Management block may generate messages including the LBS information.

3 3
4
 1 IEEE C802.16n-10/0065
2
1 - Idle Mode Management: Indicates a block which manages location update operation during idle mode.
2 The Idle Mode Management block controls idle mode operation, and generates the paging
3 advertisement message based on paging message from paging controller in the core network side.
4 - System Configuration Management: Indicates a block which manages system configuration parameters,
5 and transmits system configuration information to the HR-MS/HR-RS.
6 - MBS: Indicates a block which controls management messages and data associated with broadcasting
7 and/or multicasting service.
8 - Service Flow and Connection Management: Indicates a block which allocates connection identifier
9 during access/handover service flow creation procedures.
10 - Self Organization: Indicates a block which performs functions to support self-configuration and self-
11 optimization mechanisms.
12 - Multi-Carrier: Indicates a block which enables a common MAC entity to control a PHY spanning over
13 multiple frequency channels. The channels may be of different bandwidths (e.g. 5, 10 and 20 MHz) on
14 contiguous or non-contiguous frequency bands. The channels may be of the same or different duplexing
15 modes, e.g. FDD, TDD, or a mix of bidirectional and broadcast only carriers. For contiguous frequency
16 channels, the overlapped guard sub-carriers are aligned in frequency domain in order to be used for data
17 transmission.
18 - Security Management: Indicates a block which is in charge of authentication/authorization and key
19 management for secure communication. Traffic encryption/decryption and authentication are performed
20 using a managed encryption key. The Security Management block also supports security operation
21 meeting the requirements described in Section 6.1.4.
22 - Relay Function: Indicates a block which includes functions to support relay mechanisms as described in
23 section 6,1,1, 6.1.2, and 6.1.3.
24 - Direct Communication Management: Indicates a block which supports HR-MS to HR-MS direct
25 communication meeting the requirements described in Section 6.1.3.1.
26 - Standalone Management: Indicates a block which supports standalone operation of immunizing the loss
27 of HR-BS’ backbone connectivity meeting the requirements described in Section 6.1.2.1.
28 - Multi-Mode Management: Indicates a block which supports multi-mode operation meeting the
29 requirements described in Section 6.1.1.
30 - Enhanced Multicast: Indicates a block which controls management messages and data associated with
31 multicast communication meeting the requirements described in Section 6.2.1.
32 - Path Management: Indicates a block which controls and operates functionalities, including path
33 discovery and path management meeting the requirements described in Section 6.1.3.3 and 6.1.3.4,
34 respectively.
35 - Priority Access Management: Indicates a block which manages a priority access and connection
36 meeting the requirements described in Section 6.2.3.
37The control plane part of the Medium Access Control (MAC) functional group includes functional blocks
38which are related to the physical layer and link controls such as:
39 - PHY Control: Indicates a block which handles PHY signaling such as ranging, measurement/feedback
40 (CQI), and HARQ ACK/NACK. Based on CQI and HARQ ACK/NACK, the PHY Control block
41 estimates channel quality as seen by the HR-MS, and performs link adaptation via adjusting modulation

3 4
4
 1 IEEE C802.16n-10/0065
2
1 and coding scheme (MCS), and/or power level. In the ranging procedure, PHY Control block does UL
2 synchronization with power adjustment, frequency offset and timing offset estimation.
3 - Control Signaling: Indicates a block which generates resource allocation messages.
4 - Sleep Mode Management: Indicates a block which handles sleep mode operation. The Sleep Mode
5 Management block may also generate MAC signaling relate to sleep operation, and may communicate
6 with Scheduling and Resource Multiplexing block in order to operate properly according to sleep
7 period.
8 - QoS: Indicates a block which handles QoS management based on QoS parameters input from Service
9 Flow and Connection Management block for each connection.
10 - Scheduling and Resource Multiplexing: Indicates a block which schedules and multiplexes packets
11 based on properties of connections. In order to reflect properties of connections, the Scheduling and
12 Resource Multiplexing block receives QoS information from QoS block for each connection.
13 - Multi-Radio Coexistence: Indicates a block which performs functions to support concurrent operations
14 of IEEE 802.16m and non-IEEE 802.16m radios collocated on the same mobile station.
15 - Data Forwarding: Indicates a block which performs forwarding functions when an HR-RS is present on
16 the path between an HR-BS and an HR-MS, or when an HR-MS is present on the path between an HR-
17 MS and an HR-BS meeting the requirements described in Section 6.1.3.2.
18 - Interference Management: Indicates a block which performs functions to manage the inter-cell/sector
19 interference. The operations may include:
20  MAC layer operation
21  Interference measurement/assessment report sent via MAC signaling
22  Interference mitigation by scheduling and flexible frequency reuse
23  PHY layer operation
24  Transmit power control
25  Interference randomization
26  Interference cancellation
27  Interference measurement
28  Tx beamforming/precoding
29 - Inter-BS Coordination: Indicates a block which performs functions to coordinate the actions of multiple
30 HR-BSs by exchanging information, e.g., interference management. The functions include procedures
31 to exchange information for e.g., interference management between the HR-BSs by backbone signaling
32 and by HR-MS MAC messaging. The information may include interference characteristics, e.g.
33 interference measurement results, etc.
34
35The data plane includes the following MAC functions:
36 - Fragmentation/Packing: Indicates a block which performs fragmenting or packing MSDUs based on
37 scheduling results from Scheduling and Resource Multiplexing block.
38 - ARQ: Indicates a block which handles MAC ARQ function. For ARQ-enabled connections, a logical
39 ARQ block is generated from fragmented or packed MSDUs of the same flow. The ARQ logical blocks
3 5
4
 1 IEEE C802.16n-10/0065
2
1 are sequentially numbered. The ARQ block may also generate ARQ management messages such as
2 feedback message (ACK/NACK information).
3 - MAC PDU formation: Indicates a block which constructs MAC control data unit (PDU) so that HR
4 stations can transmit user traffic or management messages into PHY channel. MAC PDU formation
5 block adds MAC header and may add sub-headers. Based on input from the security management
6 block, the encryption block can encrypt user traffic or management message by a managed encryption
7 key.
8

9
10
11 [-------------------------------------------------End of Text Proposal----------------------------------------------------]

3 6
4