Presentation is loading. Please wait.

Presentation is loading. Please wait.

Common Header design in 802.16m IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: 2009-1-5 Source:

Similar presentations


Presentation on theme: "Common Header design in 802.16m IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: 2009-1-5 Source:"— Presentation transcript:

1 Common Header design in 802.16m IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: 2009-1-5 Source: Dongyao Wang, Gang Shen, Kaibin Zhang, Shan Jin Alcatel Shanghai BellE-mail:Dongyao.wang@alcatel-sbell.com.cn Venue: Re: Call for Comments on Project 802.16m System Description Document (SDD) Base Contribution: N/A Purpose: To be discussed and adopted by TGm for the 802.16m SDD 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: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2 Introduction A draft format of MAC PDU is defined in the current SDD –FlowID is included in Generic MAC Header to indicate which transport connection the MAC PDU belongs to –STID is not involved in MAC PDU Basic principle for MAC PDU transmission and receiving –Resource allocated to one station with the indication of STID –MAC PDU is constructed with the indication of FlowID and transmitted in the assigned resource block –On receive side, the MAC PDUs can be distinguished correctly with the information of STID in resource allocation and FlowID in MAC PDU However, the above scheme may not work in the following cases –Burst-level multiplexing –Relay-deployed scenario Common MAC header is proposed to indicate STID for MAC PDU –Multiple MAC PDUs belonging to the same MS can share the same common MAC header for overhead reduction Generic MAC Header in 16m

3 Problem Description Burst-level multiplexing required in downlink –If several MSs have the similar radio link condition, BS can assign one common radio resource block for these MSs –Thus multiple MAC PDUs belong to different MSs will be multiplexed into one transmission burst –Reduce the MAP overhead to some extend –Control the unused portion in a burst as small as possible –Thus improve the utilization efficiency of radio resource In this case, no STID or multiple STIDs will be indicated when allocating the radio resource The question is –When receiving the burst, MS can not get its data packets correctly Confusion of data packets on relay link −The same Flow ID may be assigned to different mobile stations −Difficult to determine the original owner of the transmitted MAC PDUs when STID of RS is used in resource allocation The possible solution is to add STID indication in MAC PDU

4 Text Proposal(1) [Change the Generic MAC header in the section 10.12.1.1 “Generic MAC Header” of SDD] 10.12.1.1 Generic MAC Header ………………………………….. L(Last): when multiplexing multiple MAC PDUs into a single MAC PDU by sharing the same common MAC header, this field is set to “0” indicating there is at least one MAC PDU left. Otherwise, the L field is set to “1”. …………………………………..

5 Text Proposal(2) [Insert the following text after the section 10.12.1.5 “Signaling MAC Header ” of SDD] 10.12.1.6 Common MAC header The common MAC header is optional. If presented, this header should always appear before the generic MAC header. Multiple MAC PDUs from different flows belonging to the same MS can be multiplexed into a single MAC PDU with sharing the same common MAC headers. Figure.xx Common Header Format [TBD]:Reserved bits, which may be used for other purposes, such as header check code [FFS]. STID: StationID field indicates identifier of MS (i.e. Station Identifier) which the corresponding MAC PDU belongs to. The size of STID field is 12 [FFS] bits.


Download ppt "Common Header design in 802.16m IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: 2009-1-5 Source:"

Similar presentations


Ads by Google