Generic Packet Convergence Sublayer for 802.16m
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE S802.16m-08/980r1
Date Submitted:
2008-09-12
Source:
Torsten Fahldieck
Voice: +49-711-821-32163
Email: torsten.fahldieck@alcatel-lucent.de
Alcatel-Lucent
Venue:
[802.16m] [16jm] Session #57, 16.-19. September, 2008
Base Contribution:
IEEE C802.16m-08/980r1
Purpose:
To propose a Generic Packet Convergence Sublayer for 802.16m
Notice:
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.
Release:
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.
Patent Policy:
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 >.
Convergence Sublayer for 802.16m
Content
•
•
•
•
•
•
•
Convergence Sublayers in 802.16rev2
Problem: 802.16rev2 GPCS and Classification Signaling
Proposed Solution for 802.16m
Generic Convergence Sublayer for 802.16m
Classification
Classification Signaling
Proposed text for SDD
2
CS Layers in 802.16
Currently defined convergence sublayer in 802.16rev2
• Service specific packet convergence sublayers
– Advantage
• Provide classification
– Disadvantage
• Specific to upper layer protocol stack and header suppression or
compression methods (6 different CS layers in 802.16rev2D6)
• Inflexible, not future proof
• Generic packet convergence sublayer
– Advantage
• Generic, adaptable to any protocol stack and header suppression or
compression methods, future proof
– Disadvantage
• No classification,
classification has to be performed in outside the 802.16 layers
• No signaling of classification parameter during connection setup or
change
3
Problem: 802.16rev2 GPCS and Classification Signaling
1.
2.
3.
4.
5.
6.
7.
8.
Network (BS) creates 2 MAC connections DL&UL between BS and
MS for IP-traffic
IP packet arrives from network side
Classification is done according to classification rules on the BS (in
MAC layer or upper layer)
MAC PDU is send to MS via its designated DL MAC connection
Packet is received by MS
MS MAC process MAC PDU and deliver IP packet to upper layers
Upper layer (application) generates reply packet
Reply packet is delivered to downwards (IP, MAC, ..)
How can classification be performed on MS side without
information about classification ?
4
CS Layer Function
•
Classification and connection mapping
Upper Layer Entity
(e.g., bridge, router, host)
Upper Layer Entity
(e.g., bridge, router, host)
SDU
SDU
SAP
SAP
Conn.ID* #1
Conn.ID* #2
Conn.ID* #..
Classifier
Reconstitution
(e.g., undo PHS
Conn.ID* #n
{SDU,
Conn.ID* , …}
{SDU,
Conn.ID* , …}
SAP
SAP
802.16m MAC CPS
802.16m MAC CPS
* Conn.ID = MSID/SID tuple
5
Proposed solution for 802.16m
• One generic packet convergence sublayer
(based on 802.16Rev2 GPCS)
• support any type of upper layer protocol stack
• Support header suppression and/or compression
• Includes Generic Classification
• Signals generic classification rules
• Combines advantages of generic and specific 802.16
CS layers
6
CS Interworking
CS layer interworking with other layers control and data plane
Data Plane
Data Plane
Upper Layers
Upper Layers
CS_DATA.
request
Flow
setup/
change
(rule set)
Control Plane
CS_DATA.
indication
CS_DATA.
request
CS_DATA.
indication
CS SAP
CS SAP
Convergence
Sublayer
Convergence
Sublayer
MAC SAP
MAC SAP
MAC CPS
PHY SAP
Phy Layer
MAC connection
setup/change
(rule set)
Flow
setup/
change
(rule set)
C_SAP
Control Plane
C_SAP
•
MAC CPS
PHY SAP
Phy Layer
7
CS – SAP Primitives
CS_DATA.request ( SFID, MS MAC Address, length, data )
SFID: Unique identifier to identify a unidirectional service flow
MS MAC Address: Unique identifier used by MS
Data: Payload delivered by the upper layer to the GPCS
length: Number of bytes in DATA
CS_DATA.indication ( SFID, MS MAC Address, length, data )
SFID: Unique identifier to identify a unidirectional service flow
MS MAC Address: Unique identifier used by MS
Data: payload delivered by the GPCS to the upper layer
length: Number of bytes in DATA
8
Packet Parsing
MAC PDU
MAC SDU
MAC Hdr
Pointer 1
Pointer 2
Data
Data
Length 1
Length 2
Pattern 1
Mask 1
Rule 1
Pattern 2
Payload
Mask 2
Rule 2
9
Classification Rule Set
Syntax
N
Size (bit)
Notes
8
Number of rules within the rule set, priority of the rule in ascending
order
Pointer
8
Position of the data inside the MAC SDU beginning from the start of
the MAC SDU in byte
Length
8
Length of the data and the match pattern in byte
For (i = 0; i < N; i++) {
Mask
Match type
Length*8
8
The mask which is logical AND with data and match pattern
1: direct
2: range low to high
If (Match type == 1){
Pattern
Length*8
Value of the match criteria
Pattern Low
Length*8
Value of the low match criteria
Pattern High
Length*8
Value of the high match criteria
Combination type
8
}
If (Match type == 2){
}
0: no combination (last rule in the rule set)
1: “or” combination with next rule
2: “and” combination with next rule
}
10
Classification Rule Set Signaling
•
•
•
Message flow between connection peers
Example: connection setup from network side
NCMS: Network Control and Management system
NCMS
BS side
802.16m
Entity BS
Primitive:
Flow setup/change
request (rule-set)
Primitive:
Flow setup/change
response (rule-set)
802.16m
Entity MS
MAC MSG:
Connection setup/change
request (rule-set)
MAC MSG:
Connection setup/change
response (rule-set)
NCMS
MS side
Primitive:
Flow setup/change
request (rule-set)
Primitive:
Flow setup/change
response (rule-set)
11
Text proposal
Insert the following text into SDD (IEEE 802.16m-08/003r4) section.9. –
9. Convergence Sub-Layer
The Convergence sublayer (CS) is an upper layer protocol-independent packet
convergence sublayer that supports multiple protocols over 802.16m air interface. This
convergence sublayer shall support any kind of upper layer protocol stack. This sublayer
uses the MAC SAP and exposes a SAP to CS applications. With CS, the upper layer
protocol that is immediately above the 802.16m CS is identified by a TLV parameter, CS
protocol type (tbd). The CS protocol type shall be included in service flow management
primitives and messages during connection establishment. The CS incorporates a
classification function, which may be used according to the requirements of a particular
connection. Classification is done on a connection basis by processing a classification
rules set. A set of classification rules may be associated to a connection. This rule set is
generated by an upper layer entity and is transferred during connection setup or change
by sending a rule set message via the C_SAP from the upper layer entity to the CS. The
rule set is send afterwards from the connection originator (BS or MS) to the connection
peer encapsulated in a MAC message via the 802.16m air interface. During MAC
connection setup or change the communication peer acknowledges the connection setup
or change according to its capability. On the transmit side, every MAC SDU coming from
the upper layer, is parsed according to the rule set and assigned to a MAC connection
specified by a Station/Flow Identifier tuple.
12