ETSI TS 102 178 V1.5.1 (2010-05)

Technical Specification
Broadband Radio Access Networks (BRAN);
HiperMAN;
Data Link Control (DLC) layer
2 ETSI TS 102 178 V1.5.1 (2010-05)

Reference
RTS/BRAN-0040002r5
Keywords
access, broadband, BWA, FWA, HiperMAN,
layer2, MAN, nomadic, radio
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 178 V1.5.1 (2010-05)
Contents
Intellectual Property Rights . 7
Foreword . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Symbols . 10
3.3 Abbreviations . 11
4 Packet Convergence Sublayer . 12
4.1 DLC SDU format . 12
4.2 Classification . 12
4.3 Payload Header Suppression (PHS) . 12
4.4 Ethernet specific part . 13
4.5 Virtual Local Area Network (VLAN) specific part . 13
4.6 IP specific part . 13
5 DLC common part sublayer . 13
5.1 Point to MultiPoint . 13
5.2 Mesh . 13
6 Data/Control plane . 13
7 PDU formats . 13
7.1 DLC header formats . 14
7.2 DLC header type encodings . 15
7.2.1 Type encodings . 15
7.2.2 Bandwidth request header . 15
7.2.3 Header Check Sequence (HCS) encoding . 16
7.3 DLC subheaders . 17
7.3.1 Mesh subheader . 17
7.3.2 ARQ feedback payload . 17
7.3.3 Fragmentation subheader . 17
7.3.4 Grant Management subheader . 17
7.3.5 Packing subheader . 18
7.3.6 FAST-FEEDBACK allocation subheader . 18
7.4 DLC management messages. 19
7.4.1 Supplemental DLC management messages . 20
7.4.2 Type 1/3: DL/UL Channel Descriptor (DCD/UCD) message . 21
7.4.3 Type 2: DL-MAP message . 24
7.4.3.1 DL-MAP PHY Synchronization Field . 25
7.4.3.2 DL-MAP IE format . 25
7.4.3.2.1 DIUC allocations . 26
7.4.3.2.2 DL-MAP extended IE format . 26
7.4.3.2.3 Channel measurement DL-MAP IE format . 26
7.4.3.2.4 DL-MAP AAS IE format . 27
7.4.3.2.5 DL-MAP STC IE format . 27
7.4.3.2.6 DL-MAP DUMMY IE format . 27
7.4.3.2.7 DL SUBCH_IE format . 28
7.4.4 Type 3: UL-MAP message . 28
7.4.4.1 UL-MAP IE format . 29
7.4.4.1.1 UIUC allocations . 30
7.4.4.1.2 UL-MAP focused contention IE format . 30
7.4.4.1.3 UL-MAP AAS IE format . 31
ETSI
4 ETSI TS 102 178 V1.5.1 (2010-05)
7.4.4.1.4 UL-MAP subchannelization IE format . 31
7.4.4.1.5 UL-MAP STC IE format . 31
7.4.4.1.6 UL-MAP DUMMY IE format . 31
7.4.4.1.7 Fast_Ranging_IE . 32
7.4.4.1.8 UL-MAP Fast Tracking IE . 32
7.4.4.2 Compressed private maps . 33
7.4.4.2.1 Compressed private DL-MAP . 33
7.4.4.2.2 Compressed private UL-MAP . 33
7.4.4.3 Reduced private maps . 33
7.4.4.3.1 Reduced private DL-MAP . 33
7.4.4.3.2 Reduced private UL-MAP . 33
7.4.5 Type 4/5: RaNGing REQuest/ReSPonse (RNG-REQ/RSP) message . 34
7.4.5.1 AAS Support . 34
7.4.5.2 Power management support . 35
7.4.6 Type 6: REGistration-REQuest (REG-REQ) message . 35
7.4.7 Type 7: REGistration-ReSPonse (REG-RSP) message . 36
7.4.8 Type 9/10: Privacy Key Management (PKM-REQ/RSP) messages . 36
7.4.9 Type 11: Dynamic Service Addition-Request (DSA-REQ) . 38
7.4.10 Type 12: Dynamic Service Addition-ReSPonse (DSA-RSP) . 38
7.4.11 Type 13: Dynamic Service Addition-ACKnowledgement (DSA-ACK) . 38
7.4.12 Type 14: Dynamic Service Change-REQuest (DSC-REQ) . 38
7.4.13 Type 15: Dynamic Service Change-ReSPonse (DSC-RSP) . 38
7.4.14 Type 16: Dynamic Service Change-ACKnowledge (DSC-ACK) . 38
7.4.15 Type 17: Dynamic Service Delete-REQuest (DSD-REQ) . 38
7.4.16 Type 18: Dynamic Service Delete-ReSPonse (DSD-RSP) . 39
7.4.17 Type 21: MultiCast polling Assignment REQuest (MCA-REQ) . 39
7.4.18 Type 22: MultiCast polling Assignment ReSPonse (MCA-RSP) . 39
7.4.19 Type 23: Downlink Burst Profile Change-REQuest (DBPC-REQ) . 39
7.4.20 Type 24: Downlink Bust Profile Change-ReSPonse (DBPC-RSP) . 39
7.4.21 Type 25: RESet CoMmanD (RES-CMD) . 39
7.4.22 Type 26/27: SS Basic Capability-REQuest/ReSPonse (SBC-REQ/RSP) . 39
7.4.22.1 OFDM demodulator . 39
7.4.22.2 OFDM modulator . 39
7.4.22.3 Subscriber transition gaps . 40
7.4.22.4 Bandwidth allocation support. 40
7.4.23 Type 33: ARQ Feedback message . 40
7.4.24 Type 34: ARQ_Discard message . 40
7.4.25 Type 35: ARQ_Reset message . 41
7.4.26 Type 36/37: Report-Request (REP-REQ/RSP) message . 41
7.4.27 Type 38: Fast Power Control (FPC) message . 42
7.4.28 Type 39: MeSH Network ConFiGuration (MSH-NCFG) message . 43
7.4.28.1 Nbr Physical Information Element . 45
7.4.28.2 Nbr Logical Information Element . 45
7.4.28.3 Embedded data . 46
7.4.28.3.1 Network Descriptor Embedded Data Information Element . 46
7.4.28.3.2 Network Entry Open Embedded Data Information Element . 48
7.4.28.3.3 Network Entry Reject Embedded Data Information Element . 48
7.4.28.3.4 Neighbour Link Establishment Embedded Data Information Element . 48
7.4.29 Type 40: MeSH-Network ENTry (MSH-NENT) message . 49
7.4.30 Type 41: MeSH-Distributed SCHeduling (MSH-DSCH) message . 49
7.4.30.1 MSH-DSCH Scheduling Information Element . 50
7.4.30.2 MSH-DSCH Scheduling Information Element . 51
7.4.30.3 MSH-DSCH Availability Information Element . 52
7.4.30.4 MSH-DSCH Grant Information Element . 52
7.4.31 Type 42: MeSH-Centralized SCHeduling (MSH-CSCH) message . 52
7.4.32 Type 43: MeSH-Centralized Scheduling ConFiguration (MSH-CSCF) message . 54
7.4.33 Type 44/45: AAS-FeedBaCK REQuest/ReSPonse (AAS-FBCK REQ/RSP) message . 55
7.4.34 Type 46 to 255: DUMMY message . 56
8 Automatic Repeat reQuest (ARQ) . 56
8.1 Packing for ARQ-enabled connections . 56
8.1.1 Interaction of packing with fragmentation . 56
ETSI
5 ETSI TS 102 178 V1.5.1 (2010-05)
8.1.2 Packing ARQ Feedback Information Elements . 57
8.2 ARQ parameters . 58
8.3 ARQ variables . 59
8.4 ARQ operation . 59
8.4.1 ARQ block usage . 59
8.4.2 Comparison of BSNs . 60
8.4.3 Transmitter state machine . 61
8.4.4 Receiver state machine . 62
8.4.5 Resetting the ARQ state machine . 63
8.5 ARQ service flow TLVs . 65
9 Mesh topology support . 67
9.1 Introduction . 67
9.2 Addressing and connections . 68
9.3 DLC service definition . 69
9.3.1 Primitives . 69
9.3.2 MAC_CREATE_CONNECTION.indication . 70
9.3.3 MAC_CHANGE_CONNECTION.indication . 70
9.3.4 MAC_TERMINATE_CONNECTION.request . 71
9.3.5 MAC_TERMINATE_CONNECTION.indication. 71
9.3.6 MAC_DATA.request . 72
9.3.7 MAC_DATA.indication . 72
9.3.8 MAC_FORWARDING_UPDATE.request . 73
9.3.9 MAC_FORWARDING_UPDATE.indication . 74
9.4 DLC management message applicability . 74
9.5 Network synchronization . 76
9.5.1 Physical neighbour list . 76
9.5.2 MSH-NCFG/MSH-NENT transmission channel and timing . 77
9.5.2.1 MSH-NCFG next transmission scheduling . 77
9.5.2.2 MSH-NENT next transmission scheduling . 78
9.6 Network entry and synchronization . 79
9.6.1 DLC management message tunnelling . 79
9.6.2 Scanning and coarse synchronization to network . 80
9.6.3 Obtaining network parameters . 81
9.6.4 Opening sponsor channel . 82
9.6.5 Negotiating basic capabilities . 85
9.6.6 Node Authorization. 85
9.6.7 Node Registration . 85
9.6.8 Establishing IP connectivity . 86
9.6.9 Establishing time of day . 87
9.6.10 Transfer of operational parameters . 87
9.7 Privacy sublayer . 87
9.7.1 TEK exchange overview . 87
9.7.2 Node Re-Authorization . 87
9.7.3 TEK usage . 88
9.7.4 Usage of operator shared key . 88
9.7.5 HMAC authentication keys and calculation of HMAC digests . 88
9.8 Data scheduling . 88
9.8.1 Distributed scheduling . 88
9.8.2 Centralized scheduling . 89
10 DLC support of PHY . 91
10.1 Uplink timing . 91
10.2 Uplink allocation . 92
11 Network Entry and Initialization . 92
11.1 Initial ranging and automatic adjustments . 92
11.1.1 Contention based Initial ranging and automatic adjustments . 92
12 Extended DLC Support . 95
13 Extended Privacy/Security . 95
14 DLC Support of OFDMA PHY . . 95
ETSI
6 ETSI TS 102 178 V1.5.1 (2010-05)
15 Parameters and constants. 95
16 TLV encoding . 95
History . 96

ETSI
7 ETSI TS 102 178 V1.5.1 (2010-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Broadband Radio Access
Networks (BRAN).
The present document describes the supplemental data transport and radio control functions of the Data Link Control
(DLC) of HIgh PErformance Radio Metropolitan Area Network (HiperMAN) systems. A separate ETSI document,
TS 102 177 [2], specifies the Physical (PHY). ®
With permission of IEEE (on file as BRAN43d016), portions of the present document are excerpted from
IEEE 802.16 [1] and IEEE 802.16e [3].
ETSI
8 ETSI TS 102 178 V1.5.1 (2010-05)
1 Scope
The present document defines the Data Link Control (DLC) of HiperMAN to support PMP and optionally Mesh
network topologies. The present document provides the DLC functions required for Fixed applications, in frequencies
below 11 GHz, and Nomadic and converged Fixed-Nomadic applications, in frequencies below 6 GHz.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] IEEE 802.16-2004: "IEEE Standard for Local and Metropolitan Area Networks - Part 16: Air
Interface for Fixed Broadband Wireless Access Systems".
[2] ETSI TS 102 177: "Broadband Radio Access Networks (BRAN); HiperMAN; Physical (PHY)
layer".
[3] IEEE 802.16e-2005: "IEEE Standard for Local and Metropolitan Area Networks - Part 16: Air
Interface for Fixed and Mobile Broadband Wireless Access Systems - Amendment 2 - Physical
and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed
Bands, And Corrigendum 1".
[4] IEEE 802.3-2005: "IEEE Standard for Information technology - Telecommunications and
information exchange between systems - Local and metropolitan area networks - specific
requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specification".
TM
[5] IEEE Std 802.16 -2009: "IEEE Standard for Local and metropolitan area networks Part 16: Air
Interface for Broadband Wireless Access Systems.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
Not available.
ETSI
9 ETSI TS 102 178 V1.5.1 (2010-05)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Adaptive Antenna System (AAS): system adaptively exploiting more than one antenna to improve the coverage and
the system capacity
NOTE: AAS-enabled in the context of a PMP BS denotes the implementation of AAS as defined. AAS-enabled
in the context of a PMP SS denotes the ability to communicate with an AAS-enabled BS using the AAS
specific mechanisms. Though a PMP SS may itself implement AAS as defined, this has no impact on the
air interface and hence no specific differentiation is made.
adaptive modulation: system's ability to communicate with another system using multiple burst profiles and a system's
ability to subsequently communicate with multiple systems using different burst profiles
ARQ Block: distinct unit of data that is carried on an ARQ-enabled connection
NOTE: Such a unit is assigned a sequence number, and is managed as a distinct entity by the ARQ state
machines.
bandwidth stealing: use, by a subscriber station operating on a grant per subscriber station basis, of a portion of the
bandwidth allocated in response to a bandwidth request for a connection to send a bandwidth request or data for any of
its connections
broadcast connection: management connection used by the Base Station (BS) to send Data Link Control (DLC)
management messages on a downlink to all Subscriber Station (SS)
NOTE: The broadcast connection is identified by a well-known Connection IDentifier (CID). A fragmentable
broadcast connection is a connection that allows fragmentation of broadcast DLC management messages.
connection: unidirectional mapping between Base Station (BS) and Subscriber Station (SS) Data Link Control (DLC)
peers
NOTE: Connections are identified by a Connection IDentifier (CID). The DLC defines two kinds of connections:
management connections and transport connections. See also: connection identifier.
Connection IDentifier (CID): 16-bit value that identifies a transport connection or an uplink (UL)/downlink (DL) pair
of associated management connections (i.e. belonging to the same subscriber station) to equivalent peers in the DLC of
the Base Station (BS) and Subscriber Station (SS)
NOTE: The Connection IDentifier (CID) address space is common (i.e. shared) between UL and DL and
IEEE 802.16 [1], table 345 as amended by IEEE 802.16e [3] specifies how it is partitioned among the
different types of connections. Security Associations (SAs) also exist between keying material and CIDs.
See also: connection.
DC carrier: in an OFDM or OFDMA signal, the carrier whose frequency would be equal to the RF centre frequency of
the station
Dynamic Frequency Selection (DFS): ability of a system to switch to different physical RF channels based on channel
measurement criteria to conform to particular regulatory requirements
initial ranging connection identifier: management connection used by the Subscriber Station (SS) and the Base
Station (BS) during the initial ranging process
NOTE: The initial ranging connection is identified by a well-known Connection IDentifier (CID) (see
IEEE 802.16 [1], table 345 as amended by IEEE 802.16e [3]). This CID is defined as constant value
within the protocol since an SS has no addressing information available until the initial ranging process is
complete.
ETSI
10 ETSI TS 102 178 V1.5.1 (2010-05)
management connection: connection used for the purpose of transporting Data Link Control (DLC) management
messages (see: basic connection, primary management connection, broadcast connection, initial ranging connection) or
standards-based messages (see: secondary management connection) required by the DLC layer
MeSH (MSH): network architecture, wherein systems are capable of forwarding traffic from and to multiple other
systems
Multiple Input Multiple Output (MIMO): system employing at least two transmit antennas and at least two receive
antennas to improve the system capacity, coverage or throughput
Payload Header Suppression Mask (PHSM): 8-bit value that references the Payload Header Suppression (PHS) rule
RF centre frequency: centre of the frequency band in which a BS or SS is intended to transmit
BS Rx/Tx Transition Gap (RTG): gap, used by TDD and H-FDD systems, between the last sample of the uplink burst
and the first sample of the subsequent downlink burst at the antenna port of the base station in a time division duplex
transceiver
NOTE: This gap allows time for the BS to switch from receive to transmit mode and SSs to switch from transmit
to receive mode. During this gap, the BS is not transmitting modulated data but simply allowing the BS
transmitter carrier to ramp up, the Tx/Rx antenna switch to actuate. Not applicable to frequency division
duplex systems.
SS Rx/Tx Gap (SSRTG): minimum receive to transmit turnaround gap
NOTE: SSRTG is measured from the time of the last sample of the received burst to the first sample of the
transmitted burst, at the antenna port of the SS.
SS Tx/Rx Gap (SSTTG): minimum transmit to receive turnaround gap
NOTE: SSTTG is measured from the time of the last sample of the transmitted burst to the first sample of the
transmitted burst, at the antenna port of the SS.
turbo decoding: iterative decoding, using soft inputs and soft outputs
BS Tx/Rx Transition Gap (TTG): gap, used by TDD and H-FDD systems, between the last sample of the downlink
burst and the first sample of the subsequent uplink burst at the antenna port of the base station in a time division duplex
transceiver
NOTE: This gap allows time for the BS to switch from transmit to receive mode. During this gap, the BS is not
transmitting modulated data but simply allowing the BS transmitter carrier to ramp down, the Tx/Rx
antenna switch to actuate, and the BS receiver section to activate. Not applicable to frequency division
duplex systems.
transport connection: connection used to transport user data
NOTE: It does not include any traffic over the basic, primary or secondary management connections. A
fragmentable transport connection is a connection that allows fragmentation of Service Data Units
(SDUs).
transport connection identifier: unique identifier taken from the Connection IDentifier (CID) address space that
uniquely identifies the transport connection
NOTE: All user data traffic is carried on transport connections, even for service flows that implement
connectionless protocols, such as Internet Protocol (IP). An active or admitted service flow (identified by
a Service Flow ID (SFID)) maps to a transport Connection IDentifier (transport CID) assigned by the BS.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
α Averaging parameter for CINR and RSSI computations
avg
RSS Initial Ranging Max. Received Signal Strength at BS
IR,max
ETSI
11 ETSI TS 102 178 V1.5.1 (2010-05)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AAS Adaptive Antenna System
ACK ACKnowledgement
AMC Adaptive Modulation Coding
ARQ Automatic Repeat reQuest
BR Bandwidth Request
BS Base Station
BSN Block Sequence Number
BTC Block Turbo Code
BW BandWidth
CID Connection IDentifier
CINR Carrier to noise and INterference Ratio
CRC Cyclic Redundancy Check
CS Convergence Sublayer
CSCF Centralized Scheduling ConFiguration
CSCH Centralized SCHedule
CTC Convolutional Turbo Code
dBm deciBels relative to one milliwatt
DCD DL Channel Descriptor
DFS Dynamic Frequency Selection
DIUC Downlink Interval Usage Code
DL DownLink
DLC Data Link Control
DSA-RSP Dynamic Service Addition - ReSPonse
DSCH Distributed SCHedule
DSC-REQ Dynamic Service Change - REQuest
DSC-RSP Dynamic Service Change - ReSPonse
EC Encryption Control
EKS Encryption Key Sequence
FDD Frequency Division Duplexing
FPC Fast Power Control
FSN Fragment Sequence Number
FWA Fixed Wireless Access
HCS Header Check Sequence
H-FDD Half-duplex FDD
HIPERMAN HIgh PErformance Radio Metropolitan Area Network
HT Header Type
ID IDentifier
IE Information Element
Im Imaginary
IP Internet Protocol
LSB Least Significant Beat
MAC Media Access Control
MIMO Multiple Input Multiple Output
MSB Most Significant Bit
MSH MeSH
NCFG Network ConFiGuration
NENT Network ENTry
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
PDU Protocol Data Unit
PHS Payload Header Suppression
PHSM Payload Header Suppression Mask
PHY PHYsical layer
PKM Privacy Key Management
PMP Point-to-MultiPoint
PUSC Partial Usage of SubChannels
QoS Quality of Service
ETSI
12 ETSI TS 102 178 V1.5.1 (2010-05)
Re Real
REQ REQuest
RNG RaNGing
RRPT Ranging Response Processing Time
RSP ReSPonse
RSSI Received Signal Strength Indicator
RTG Receive/transmit Transition Gap
SA Security Association
SDU Service Data Unit
SFID Service Flow IDentifier
SS Subscriber Station
STC Space Time Coding
TEK Traffic Encryption Key
TLV Type Length Value
Tx Transmit
TTG Transmit/receive Transition Gap
UCD UL Channel Descriptor
UDP User Datagram Protocol
UIUC Uplink Interval Usage Code
UL UpLink
VLAN Virtual Local Area Network
4 Packet Convergence Sublayer
The packet Convergence Sublayer (CS) resides on top of the DLC common part sublayer. The CS performs the
following functions, utilizing the services of the DLC:
a) Classification of the higher-layer protocol PDU into the appropriate transport connection. Suppression of
payload header information (optional).
b) Delivery of the resulting CS PDU to the DLC SAP associated with the service flow for transport to the peer
DLC SAP.
c) Receipt of the CS PDU from the peer DLC SAP.
d) Rebuilding of any suppressed payload header information (optional).
The sending CS is responsible for delivering the DLC SDU to the DLC SAP. The DLC is responsible for delivery of the
DLC SDU to peer DLC SAP in accordance with the QoS, fragmentation, concatenation and other transport functions
associated with a particular connection's service flow characteristics. The receiving CS is responsible for accepting the
DLC SDU from the peer DLC SAP and delivering it to a higher layer entity.
The packet CS is used for transport for all packet-based protocols as defined in IEEE 802.16 [1], clause 11.13.19.3 as
modified by IEEE 802.16e [3].
4.1 DLC SDU format
DLC SDU format is according to IEEE 802.16 [1], clause 5.2.1 as modified by IEEE 802.16e [3].
4.2 Classification
Packet classification is according to IEEE 802.16 [1], clause 5.2.2 as modified by IEEE 802.16e [3].
4.3 Payload Header Suppression (PHS)
Payload Header Suppression is according to IEEE 802.16 [1], clause 5.2.3 as modified by IEEE 802.16e [3].
ETSI
13 ETSI TS 102 178 V1.5.1 (2010-05)
4.4 Ethernet specific part
Ethernet specific part is according to IEEE 802.16 [1], clause 5.2.4 as modified by IEEE 802.16e [3].
4.5 Virtual Local Area Network (VLAN) specific part
Virtual local area network specific part is according to IEEE 802.16 [1], clause 5.2.5 as modified by IEEE 802.16e [3].
4.6 IP specific part
IP specific part is according to IEEE 802.16 [1], clause 5.2.6 as modified by IEEE 802.16e [3].
5 DLC common part sublayer
5.1 Point to MultiPoint
Point to MultiPoint is according to IEEE 802.16 [1], clause 6.1 as modified by IEEE 802.16e [3].
5.2 Mesh
Mesh is according to IEEE 802.16 [1], clause 6.2 as modified by IEEE 802.16e [3].
6 Data/Control plane
The data/control plane is according to IEEE 802.16 [1], clause 6.3 as modified by IEEE 802.16e [3].
7 PDU formats
DLC PDUs shall be of the form illustrated in figure 1. Each PDU shall begin with a fixed-length generic DLC header.
The header may be followed by the Payload of the DLC PDU. If present, the Payload shall consist of zero or more
subheaders and zero or more DLC SDUs and/or fra
...