Download presentation
Presentation is loading. Please wait.
Published byLaura Owen Modified over 9 years ago
1
Uplink Control Information Content for Bandwidth Request Channel IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0401 Date Submitted: 2009-02-27 Source: Kanchei (Ken) Loa, Yi-Ting Lin, Yi-Hsueh Tsai, E-mail: loa@iii.org.tw Chun-Yen Hsu, Youn-Tai Lee, Tsung-Yu Tsai, Chiu-Wen Chen, Institute for Information Industry * http://standards.ieee.org/faqs/affiliationFAQ.html Venue: IEEE 802.16m-09/0012: Call for Contributions on Project 802.16m Amendment Working Document (AWD) Content Base Contribution: N/A Purpose: Propose Uplink Control Information Content for Bandwidth Request Channel 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 In SDD, contention based or non-contention based random access is used to transmit bandwidth request information on the BW REQ channel. However, the region in which an AMS transmits BW REQ for the two mode is not defined. We propose the quick access message that is carried on different access region for contention based and non-contention based BW REQ. In contention based BR, multiple AMSs request BW in a pre- allocated region to contend for the resource. So a STID is used to uniquely identify an AMS. A FID in the quick access message is used to identify the connection within the AMS and the BR content is used to identify the number of bytes requested by the AMS. In non-contention based BR, each AMS requests BW in the region that is indicated in the A-MAP by ABS (e.g. piggyback BR). So the quick access message shall contain a FID and the BR content. QoS ID is used for both mode to identify the class of QoS.
3
Quick access message Length (bit)DescriptionNote Type1Identifies the BW REQ mode 0: contention based BW REQ 1: non-contention based BW REQ STID12Uniquely identifies an AMS Only for contention based BW REQ FID4Uniquely identifies the connection within an AMS BR contentTBDIdentifies the number of bytes requested by an AMS QoS IDTBDIdentifies the class of QoS
4
Proposed text 15.3.9.3.3 Bandwidth Request Channel –The quick access message for contention based and non- contention based BW REQ is shown in TABLE xxx. –In contention based BR, multiple AMSs request BW in a pre- allocated region to contend for the resource. A STID is used to uniquely identify an AMS. A FID is used to identify the connection within the AMS and the BR content is used to identify the number of bytes requested by the AMS. –In non-contention based BR, each AMS requests BW in the region indicated by the ABS (including piggyback BR). The quick access message shall contain a FID and the BR content. –QoS ID is used for both mode to identify the class of QoS.
5
Length (bit)DescriptionNote Type1Identifies the BW REQ mode 0: contention based BW REQ 1: non-contention based BW REQ STID12Uniquely identifies an AMS Only for contention based BW REQ FID4Uniquely identifies the connection within an AMS BR contentTBDIdentifies the number of bytes requested by an AMS QoS IDTBDIdentifies the class of QoS TABLE xxx quick message for contention based and non- contention based bandwidth request
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.