IEEE C802.16m-09/1744
Project
|
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
|
Title
|
Simplified MEH Format for 802.16m
|
Date Submitted
|
2009-08-29
|
Source(s)
|
Anil Agiwal, Youngbin Chang, Rakesh Taori, Jungje Son
Samsung Electronics
|
anilag@samsung.com
yb.chang@samsung.com
|
Re:
|
IEEE 802.16-09/0044, IEEE 802.16 Working Group Letter Ballot #30
|
Abstract
|
The contribution proposes a simplified MEH format
|
Purpose
|
To be discussed and adopted by TGm
|
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 .
Further information is located at and .
|
Simplified MEH format for 16m
Anil Agiwal, Youngbin Chang, Rakesh Taori, Jungje Son
Samsung Electronics
-
Introduction
The MEH format adopted in IEEE P802.16m/D1 document [1] has following issues:
-
The MEH consists of MEHBs and there are many formats of MEHBs
-
First MEHB
-
MEHB (other than first MEHB)
-
First RMEHB
-
RMEHBs (other than first RMEHB)
The adopted format is complex and adds to processing and implementation complexity
-
The MEH can not be used for multiplexing when management & transport connection having same SA are sent in same PHY burst
-
The definition of Length field in GMH is different for multiplexed and non multiplexed MAC PDU
This contribution proposes a simplified MEH format, which is a simple extension of single connection MAC PDU format with GMH and FPEH.
-
Multiplexed MPDU – Simplified MEH
-
GMH provides the information about 1st Payload’s FlowID & Length.
-
Multiplexing Extended Header (MEH) provides the information about the other Payloads’ FlowIDs and Lengths as shown in figure 1
-
MEH is the first extended header present in the MAC PDU
-
MEH consists of one or more Flow Information Blocks (FIBs)
-
Number of FIBs = number of connections’ payloads multiplexed in the MAC PDU – 1
-
Each FIB contains Flow Identifier and Payload Length
Figure 1 Multiplexing Extended Header
-
Multiplexed MPDU – Simplified MEH Format
Syntax
|
Size (in bits)
|
Notes
|
MEH () {
|
|
|
Last
|
1
|
0 = another extended header follows MEH
1 = another extended header does not follow MEH
|
Type
|
4
|
MEH type
|
Num Flows
|
4
|
Number of Flow information present in the MEH
|
for (i = 1; i <= Num Flows ; i++) {
|
|
|
Flow ID
|
4
|
Flow Identifier
|
Length
|
11
|
Length of Payload
|
}
|
|
|
Reserved
|
variable
|
|
}
|
|
|
-
Multiplexed MPDU – Simplified MEH Illustration
Figure 2 Multiplexed MAC PDU using simplified MEH
Figure 3 Multiplexed and non multiplexed MAC PDU
-
Multiplexed MPDU – Simplified MEH Overhead Comparison
Overhead in new simplified scheme is same as old scheme.
# Flow Payloads in MPDU
|
#SDUs per Flow Payload
|
Old Scheme Overhead (MEH) in bytes
|
New Simplified Scheme Overhead (MEH + FPEH) in bytes
|
2
|
1
|
7
|
7
|
2
|
2
|
10
|
10
|
2
|
3
|
13
|
13
|
3
|
1
|
11
|
11
|
3
|
2
|
15
|
15
|
3
|
3
|
20
|
20
|
4
|
1
|
15
|
15
|
4
|
2
|
21
|
21
|
4
|
3
|
27
|
27
|
5
|
1
|
19
|
19
|
5
|
2
|
26
|
26
|
5
|
3
|
34
|
34
|
-
References
[1] IEEE P802.16m/D1, “DRAFT Amendment to IEEE Standard for Local and metropolitan area networks Part 16: Air Interface for Broadband Wireless Access Systems”
-
Proposed Text
Replace the entire section 15.2.2.2.4 in P802.16m/D1, page 15-20 by the proposed text as shown below.
-------------------Beginning of Proposed Text---------------------------
15.2.2.2.4 Multiplexing Extended Header (MEH)
The format of MEH is defined in Table 665. It is used when SDUs/SDUs fragments from multiple connections are multiplexed in the same MAC PDU. GMH provides the information about the FlowID and length of the first connection’s payload in MAC PDU. MEH provides the information about the FlowIDs and lengths of the remaining connections’ Payloads in MAC PDU.
Table 665 MEH Format
Syntax
|
Size
(bit)
|
Notes
|
MEH () {
|
|
|
Last
|
1
|
0 = another extended header follows MEH
1 = another extended header does not follow MEH
|
Type
|
4
|
MEH type
|
Num Flows
|
4
|
Number of Flow information present in the MEH
|
for (i = 1; i <= num flows; i++) {
|
|
|
Flow ID
|
4
|
Flow Identifier
|
Length
|
11
|
Length of Payload
|
}
|
|
|
Reserved
|
variable
|
|
}
|
|
|
-------------------End of Proposed Text---------------------------
|
Yüklə 473.5 Kb.