IEEE C802.16m-09/1222r2

Download Report

Transcript IEEE C802.16m-09/1222r2

Assignment A-MAP for Multicarrier Operation
(AWD-MCDG)
Document Number: C80216m-09/1222r2
Date Submitted: 2009-7-14
Source:
Lei Huang;
Panasonic Singapore Laboratories Email: lei.huang@sg.panasonic.com
Isamu Yoshii
Panasonic Corporation
Email: yoshii.isamu@jp.panasonic.com
Yuqin Chen
Email: chen.yuqin@zte.com.cn
ZTE Corporation
Venue:
IEEE 802.16 Session #62, San Francisco, USA.
Re: Reply comment - Multi-Carrier DG Harmonized Text Proposal – PHY (C80216m-09/1282)
Base Contribution: N.A.
N/A
Purpose:
For TGm discussion and adoption of 802.16m AWD text.
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 >.
1
Assignment A-MAP in 16m AWD [1]
 Assignment A-MAP contains resource
assignment information which is
categorized into multiple types of
assignment A-MAP IE. Each assignment
A-MAP IE is coded separately and
carries information for one or a group of
users
 Assignment A-MAPs are grouped
together based on MCS level and A-MAP
IE sizes. Assignment A-MAPs in the
same group, e.g., Gi, are transmitted with
the same MCS level and contain the same
A-MAP IE size.
 The number of assignment A-MAPs in
each assignment A-MAP group is
signaled through non-user specific AMAP.
IE
IE
G1
IE
IE
IE
G2
IE
Assignment
A-MAP
IE
IE
GN
IE
2
Assignment A-MAP for Multicarrier Operation
• MAC segmentation is supported
for multicarrier operation, where
MAC data can be mapped to data
region in one of primary or
secondary carriers. The allocation
information shall be sent through
the carrier where the OFDMA data
region is located. The same
assignment A-MAP IE used for
single carrier allocation is used for
the allocation.
IE
IE
Gi
IE
IE
IE
Type B
Type A
IE
• In this case, IEs within an assignment A-MAP group, e.g., Gi, fall into two
categories:
– Type A: IEs intended for a specific MS or a specific group of MSs that treats
the carrier as a secondary carrier
– Type B: remaining IEs in the assignment A-MAP group
3
Problem
• Due to blind detection, a MS without MC capability needs to decode all the IEs of
an assignment A-MAP group.
• It would be better for a MS without MC capability to decode only IEs of Type B
in an assignment A-MAP group.
– This would greatly reduce blind decoding complexity for MS without MC
capability
4
Proposed Scheme
• IEs in an assignment A-MAP group, e.g.,
Gi, are grouped into 3 sub-groups
according to IE property and allocation
type
IE (unicast)
SG1i
IE (unicast)
IE (multicast)
– SG1i: unicast IEs of Type B in group
i
– SG2i: multicast IEs of Type B in
group i
Type B
SG2i
Gi
The endpoint of SG2i is
identified by IE property
(unicast or multicast) or
allocation type (Type A
or Type B)
IE (multicast)
IE
– SG3i: IEs of Type A in group i
• Multicast IEs of Type B (SG2i) is used as
a boundary between Type A IEs and Type
B IEs. So after identifying the endpoint
of SG2i, MS has no need of decoding
remaining IEs in SG3i
The start point of SG2i is
identified by IE property
(unicast or multicast)
SG3i
Type A
IE
• Benefit: If at least one multicast IE of Type B exists, blind decoding complexity for MS
without MC capability can be greatly reduced; Otherwise MS works as usual.
We can enjoy the benefit of proposed scheme without any cost
5
AWD Text Proposal
•The following text is inserted into Section 15.3.6.6 of Multi-Carrier DG Harmonized Text
Proposal – PHY [2].
*******************BEGIN Proposed Text ******************************
15.3.6.6. Downlink Control Structure for Multicarrier Support
For multicarrier operation, assignment A-MAP IEs within an assignment A-MAP group
shall be grouped into two subgroups. The first subgroup comprises of all the assignment AMAP IEs intended for AMSs that treat the carrier as a secondary carrier, and the second
subgroup comprises of the remaining assignment A-MAP IEs in the assignment A-MAP
group. The MLRUs occupied by the first subgroup shall be located behind the MLRUs
occupied by the second subgroup.
************** END Proposed Text *******************************
6
References
•
•
IEEE 802.16m-09/0010r2 (IEEE 802.16m Amendment Working Document)
IEEE C80216m-09/1282 (Multi-Carrier DG Harmonized Text Proposal – PHY)
7
Appendix: Important Facts
• According to AWD [1], some specific STIDs are
reserved for multicast. So MS has a prior knowledge
of multicast STIDs.
• MS can make use of this prior knowledge to
determine whether an IE is of multicast or not.
– MS can always successfully decode a multicast IE by
attempting different multicast STIDs for CRC check.
– After successfully decoding multicast IE, MS knows
whether this multicast IE is intended for SC allocation or
MC allocation according to certain IE fields, e.g., resource
allocation info field.
8