A transmission scheme of DL Control information

Slides:



Advertisements
Similar presentations
[Idle Mode Paging in Multicarrier] IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0411r2 Date Submitted:
Advertisements

Clarification for Staggered Super-frame Transmissions in the SDD Document Number: IEEE C802.16m-08/854 Date Submitted: Source: Richard Li, Chun-Yen.
Relative Timing of Super-Frames in the Legacy-Support Mode IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/244.
Common Header design in m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0178 Date Submitted: Source:
Network Entry Procedure with Multi-Carrier Support Document Number: IEEE C802.16m-09/0966 Date Submitted: 2009/04/27 Source: I-Kang Fu, Yih-Shen Chen,
1 Proposal for Multicarrier Uplink Control Structure IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/303r3 Date.
Notice: This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the.
Multiplexing of MBS and unicast services in 16m Document Number: IEEE S80216m-08/959r1 Date Submitted: Source: Kaiying Lv, Changyin Sun, Wei.
Group Sleep Mode in IEEE m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-08/591r3 Date Submitted:
DL Preamble Design for m Document Number: IEEE S802.16m-08/385 Date Submitted: Source: Sun Changyin, Liu Min, Wang Wenhuan,Yao
IEEE m Identifying Femtocell BS and its Accessibility Document Number: IEEE C80216m-09_0068 Date Submitted: Source: Ying Li, Zhouyue Pi,
Multi-Level Codes Sequence for Simultaneous MCS Feedback IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE S80216m-08/1152 Date.
Preamble for 16m IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C80216m-08/480 Date Submitted: Source:Zexian Li,
Clarification on Temporary Identifier of Idle AMS IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/0839r2 Date Submitted:
IEEE Presentation Submission Template (Rev. 9) Document Number:
[A Reliable Multicast Service in m]
FDD Frame Structure Supporting TDD-based Legacy Systems for P802.16m
Report of the Handover Rapporteur Group, Session #55 Macau
Uplink Pilot Structure for IEEE802.16m
Discussion of Explicit vs. Implicit PC-A-MAP IE Assignment (15.2.3)
Emergency Service – NS/EP Vs E-911 for IEEE m
IEEE m DL Interference Mitigation
Downlink Control Channel Design Considerations for IEEE m
Group Resource Allocation for DL Data
Proposal for Downlink HARQ Scheme
A MAC Addressing in IEEE m
Frame structure supporting multiple CP sizes
IEEE Presentation Submission Template (Rev. 9) Document Number:
IEEE Presentation Submission Template (Rev. 9) Document Number:
Collaborative uplink MIMO techniques for IEEE m
Opening report of Connection Management and QoS DG
IEEE Presentation Submission Template (Rev. 9) Document Number:
Proposal on Update of S-SFH
HO DG Meeting Minutes Document Number: IEEE S802.16m-09/0752
Sounding Antenna Switching for IEEE m Amendment Working Document
Comment on Relay Frame Structure
Modulation and Coding set design for IEEE m system
Project Planning Committee Opening Report
IEEE m SDD ToC for Inter RAT Handover
Expedited Hard Handover
HARQ Soft Buffer Management for m
SPID transmission order in IEEE m UL HARQ
Investigation on One- and Two-Stream BCH MIMO Schemes
Dynamic Interference Mitigation for Femtocell Access Points in IEEE802
Clarification on ACK of Bandwidth Request
Investigation on one and two stream BCH MIMO Schemes
IEEE m UL Fractional Power Control
IEEE Presentation Submission Template (Rev. 9) Document Number:
IEEE m MIMO RG recommendations for SDD text
Document Number: IEEE C80216m-08/828 Date Submitted: Source:
MAP NACK Channel for Persistent Allocation
Session # Maintenance Task Group Opening and Agenda
Resource Shifting in Persistent Scheduling
Report of the Handover Rapporteur Group
Session # Maintenance Task Group Opening and Agenda
PMI Feedback Mechanism
Compressed MAC PDU Overhead
IETF 16ng Working Group Update
SON in IEEE m system IEEE Presentation Submission Template (Rev. 9)
Comments on SFH IE to Support Network Entry for Multi-Carrier MS
Further Considerations to MS-MS Power Control
Network Coding Retransmission Design with Common Feedback Channel
Bandwidth Request Indicator
Zhu dengkui,Jerry Chow UL HARQ Feedback Channel Performance Comparisons of tile Format Options Document Number: C80216m-09_0158.
Network Synchronization Considerations for n
HARQ Feedback Joint Coding
HARQ and ARQ Interactions
Text Proposals of PHY Control Structure for 16n Direct Communication
Treasurer’s Report Document Number: IEEE /0059
ARQ protocol in m IEEE Presentation Submission Template (Rev. 9)
Presentation transcript:

A transmission scheme of DL Control information for Multi-carrier support in IEEE IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/955 Date Submitted: 2008-09-05 Source: Nan Li, Min Liu, Changyin Sun, Wenhuan Wang, Ruixia Zhang, Huiying Fang, Yuqin Chen Voice: [Telephone Number (optional)] E-mail: li.nan25@zte.com.cn ZTE Corporation *<http://standards.ieee.org/faqs/affiliationFAQ.html> Venue: Re:Multi-Carrier Operation; in response to the TGm Call for Contributions and Comments 802.16m-08/033 for Session 57 Base Contribution: IEEE C802.16m-08/955r1 Purpose: To be discussed and adopted by TGm for use in the IEEE 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: <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 >.

Background Carriers of a multi-carrier system may be configured as fully configured carrier and partially configured carrier in SDD: Fully configured carrier: A carrier for which all control channels including synchronization, broadcast, multicast and unicast control signaling are configured. Further, information and parameters regarding multi-carrier operation and the other carriers can also be included in the control channels. Partially configured carrier: A carrier with only essential control channel configuration to support traffic exchanges during multi-carrier operation. PBCH and SBCH are used to transmit essential system parameters and system configuration information. DL control information also includes extended system parameters and system configuration information, control and signaling for DL notifications and control and signaling for traffic.

Problems How PBCH, SBCH and other DL control information are configured on fully configured carriers and partially configured carriers ? Needs a clarification about the configuration of DL control information on these two kinds of carriers for the benefit of system overhead reduction and improvement of transmission efficiency. In the case partially configured carrier has SCH, the MS could not acquire complete control and system information after finishing synchronization and has to scan other DL frequency again. There will be long access delay if MS has to decode the whole BCH information to find the configuration of the carrier. This contribution proposes a Superframe control header(SFCH)to solve this problem.

BCH Considerations in multi-carrier system PBCH solution All the MSs in a cell complete network entry through fully configured carriers. Each fully configured carrier needs to be configured with PBCH. MS gets deployment-wide common information during Initialization State. After network entry, if the serving BS assigns partially configured carriers to MS as secondary carriers or do carrier switch for the purpose of system load balancing or QoS requirement according to the MS’s multi-carrier capability, MS may use the PBCH information acquired during network access. PBCH information could only be sent on fully configured carriers with fixed length.

BCH Considerations in multi-carrier system SBCH solution SBCH information may change along with the sector’s configuration and the carrier’s operation. Single-radio MS If uses a partially configured carrier as its secondary carrier, MS should return to its primary carrier periodically or event-triggered for maintaining control by the BS, therefore, the SBCH information may be sent on partially configured carrier for the convenience of MS’s work. Information about initial ranging may not be sent on partially configured carrier since it would not be used for the purpose of access. Multi-radio MS May simultaneously working on one or more fully configured carriers and /or partially configured carriers, thus the SBCH information may be configured only on fully configured carriers. Two methods to send SBCH information could be applied.

BCH Considerations in multi-carrier system SBCH solution Option 1 Configured on both fully configured carrier and partially configured carrier. Option 2 Configured only on fully configured carriers. SBCH information about partially configured carriers will be sent by one or more fully configured carriers MS is working with in the following three ways: Unicast A partially configured carrier is assigned to MS, or traffic switches from one partially configured carrier to another. Information may be a complete one or just information different from the current carrier. Multicast A group of MSs which work on the same fully configured carrier and have been assigned the same target partially configured carrier. Broadcast

DL control information configuration on fully/partially carrier Channel Carrier configuration Essential system parameters and system configuration information Deployment-wide common information PBCH Fully Downlink sector-specific information SBCH Partially Uplink sector-specific information Extended system parameters and system configuration information FFS Control and signaling for DL notifications Control and signaling for traffic USCCH

Superframe control header (SFCH) 16m Superframe control header (SFCH) Transmitted in every Superframe Predefined transmission format , length and MCS Fixed location : may be TDM with SCH and followed by BCH. MS can decode SFCH without any other information.

Superframe control header (SFCH) SFCH format Only fully configured carriers need to be configured with PBCH. PI : specify the existence of PBCH. PI=1 means PBCH is present. PBCH is transmitted using predetermined scheme with fixed length and right after the SFCH, if PI=1. SI and SBCH length: indicate the presence and the size of SBCH, which should be known by MS before decoding SBCH. Syntax Size Notes PBCH indicator (PI) 1 0: PBCH is not present 1: PBCH is present SBCH indicator(SI) 0: SBCH is not present 1: SBCH is present SBCH length Reserved MS only needs to decode SFCH after synchronization to determine whether the current carrier is fully configured and continue to decode the whole BCH.

Proposed SDD text 19.x DL broadcast information for Multi-carrier support Each fully configured carrier needs to be configured with PBCH. After network entry, the serving BS may assign another carrier to MS as secondary carrier or do carrier switch for the purpose of system load balancing or QoS requirement according to the MS’s multi-carrier capability. PBCH information could only be sent on fully configured carriers with fixed length.

Proposed SDD text SBCH information may be transmitted through either of the following two options: Option 1: SBCH can be configured on both fully configured carrier and partially configured carrier. Option 2: SBCH can be configured only on fully configured carriers. SBCH information about partially configured carriers will be sent by one or more fully configured carriers MS is working with.

Proposed SDD text 19.x.1 Superframe control header (SFCH) A Superframe control header (SFCH) is used to indicate the configuration of a carrier in the case that partially configured carrier has SCH. A PBCH indicator (PI) Bit in SFCH specifies the existence of PBCH. PI=1 means PBCH is present. PBCH is transmitted using predetermined scheme with fixed length and right after the SFCH, if PI=1. SFCH indicator(SI)Bit and SBCH length are used to indicate the presence and the size of SBCH. SFCH should be transmitted with predefined transmission format, length, MCS and location . SFCH may be TDM with SCH and followed by BCH.

Proposed SDD text The structure of SFCH is shown in Table 1. Table 1 SFCH format Syntax Size Notes PBCH indicator (PI) 1 0: PBCH is not present 1: PBCH is present SBCH indicator(SI) 0: SBCH is not present 1: SBCH is present SBCH length Reserved