Proposal for Multi-Carrier Framework in 16m

advertisement
Proposal for Multi-Carrier Framework in 16m
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE C802.16m-08/026
Date Submitted:
2008-01-16
Source:
Junxian Mo, Hongliang Xu
Xiaolu Dong, Ying Du
Xin Su, Xiaofeng Zhong
Voice:
E-mail:
Voice:
E-mail:
Voice:
E-mail:
+86 755 28970188
{mojunxian; zhier81}@huawei.com
(dongxiaolu; duying) @mail.ritt.com.cn;
suxin@mail.tsinghua.edu.cn; zhongxf@tsinghua.edu.cn
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
Venue:
IEEE 802.16 Session #53, in Levi, Finland
Base Contribution:
None
Purpose:
Discussed the issues and approach about multi-carrier framework in 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 >.
Open issues of multi-carrier framework
• Resource allocation: whether resource of a carrier could be
allocated by control signals of its own carrier, or by control
signals of other carriers.
• Support single MAC or multiple MAC.
Suggest solution
• Support single MAC to provide load balancing and scheduling
enhancements.
• The common message of one DL carrier can allocate resource
of other DL carriers and UL carriers.
• Support MS Based Primary Carrier concept. It means that MS
only receives its control signal and resource assignment
message from its Primary Carrier.
Framework in TDD scenario
Frequency/
Sub-carriers
RF2
Broadcast
Messaging?
P
R
E
A
M
B
L
E
Common Message
(e.g. for MS2)
DL Allocations
UL Allocations
RF1
Broadcast
Messaging
P
R
E
A
M
B
L
E
Common
Message
(e.g. for MS1)
DL Allocations
UL Allocations
Time
Framework in FDD Scenario
RF1
RF2
RF3
RF4
P
R
E
A
M
B
L
E
P
R
E
A
M
B
L
E
Broadcast Message
Common Message
DL
Broadcast Message
Common Message
DL
UL
UL
Specific feature
• The Broadcast Channel of each carrier is independent.
• Even an MS that is capable of demodulating all carriers shall
access the system on only one carrier. When MS finishes the
process of network entry and BS knows its capability, it can
start scheduling the MS on multiple carries.
• When an MS enters idle mode, it will only listen on one
carrier.
Thanks!
Download