Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Similar presentations


Presentation on theme: "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."— Presentation transcript:

1 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. Further information is located at and. IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/1033r2 Date Submitted: 2008-09-16 Source:Chung-Hsien Hsustanley.hsu@mediatek.com Yih-Shen Chenyihshen.chen@mediatek.com I-Kang FuIK.Fu@mediatek.com Paul Chengpaul.cheng@mediatek.com MediaTek Inc. No.1, Dusing Rd. 1, Hsinchu Science-Based Industrial Park, Hsinchu, Taiwan 300, R.O.C. Venue:MAC: Multi-Carrier Operation; in response to the TGm Call for Contributions and Comments 802.16m-08/033 for Session 57 Base Contribution: This is the base contribution Purpose: To be discussed and adopted by TGm for the 802.16m SDD Sleep Mode Operations with Multi-carrier Support for IEEE 802.16m

2 2 Design Principles (1/2)  Multi-carrier operation principles (specified in SDD)  Each MS shall consider only one RF carrier to be its primary carrier in a cell  A primary carrier shall be fully configured for an MS  A secondary carrier shall be partially configured for an MS  The resource allocation can span across multiple RF carriers  A multi-carrier system may assign secondary carriers to an MS in the downlink and/or uplink asymmetrically based on system load, peak data rate, or QoS demand  Summary from the multi-carrier operation principles  Traffic indication can be implemented on different RF carriers  Traffic exchange can be implemented on different RF carriers  Traffic indication and exchange can be implemented on different RF carriers

3 3 Design Principles (2/2)  Design principles of Sleep mode in multi-carrier system  Reuse the fundamental design concept of sleep mode in single-carrier system  Enhance the power saving in RF level  Reduce the total times of the RFs sleep/awake switch in an MS  Reduce the number of MS’s active RFs as many as possible  Basic sleep mode operation for an MS with multi-carrier  All the RFs are turned off or connected with other BSs in the sleep intervals  One or more RFs can be awaked to exchange traffic in the extended listening windows  Only one of the RFs is awaked to detect/receive traffic indication in the listening window per sleep cycle  Option #1: Traffic indication is always executed on MS’s primary carrier  Option #2: Traffic indication is executed on one of the MS’s carriers

4 4 Basic Sleep Mode Operation for an MS with Multi-carrier (1/2 )  Option #1: Traffic indication is always executed on MS’s primary carrier  BS transmits traffic indication message on MS’s primary carrier  BS indicates MS to receive traffic on which carrier according to some purposes (e.g., enhanced power saving, bandwidth constraint, and QoS consideration)  MS receives traffic indication message on its primary carrier and awakes the corresponding RF to receive traffic  Disadvantages:  Performance is constrained by the schedule of MS’s primary carrier  Ex: MS’s primary carrier is scheduled for scanning, pre-association, and network re-entry  Power consumption is increased due to traffic indication and traffic exchange is executed on different RF carriers  Ex: BS doesn’t have any bandwidth to transmit traffic to an MS on its primary carrier

5 5 Basic Sleep Mode Operation for an MS with Multi-carrier (2/2)  Option #2: Traffic indication is executed on MS’s primary or secondary carriers  BS transmits traffic indication message on MS’s primary or secondary carriers  BS indicates MS to receive traffic on which carrier according to some purposes (e.g., enhanced power saving, bandwidth constraint, and QoS consideration)  MS receives traffic indication message on a pre-designed carrier and awakes the corresponding RF to receive traffic  Advantage: Reduce the unnecessary RF sleep/awake switch for an MS  Traffic indication and traffic exchange is executed on the same RF carrier for an MS  Disadvantage: Some power consumption is caused while executing traffic indication and traffic exchange on different RF carriers  Ex: BS doesn’t have enough bandwidth to transmit all the traffic to an MS on a carrier

6 6 Proposed Text for SDD Add the following text into SDD (IEEE 802.16m-08/003r4) -------------------------- text begin ----------------------------------------------------------------------------- 10.x.y Sleep Mode Operation with Multi-carrier Support BS transmits traffic indication message to an MS on one of MS’s RF carriers. MS receives traffic indication message on a pre-designed carrier. MS awakes the corresponding RF to receive traffic in accordance with BS’s resource allocation. -------------------------- text end -------------------------------------------------------------------------------


Download ppt "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."

Similar presentations


Ads by Google