IEEE C802.16m-09/0054 Project IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16> Title Proposed MSCCH Allocation Scheme for Multi-Carrier Date Submitted 2009-01-05 Source(s) Nan Li, Li Wang Voice: E-mail: li.nan25@zte.com.cn ZTE Corporation Re: Call for Contributions and Comments on Project 802.16m System Description Document (SDD) issued on 2008-12-12 (IEEE 802.16m-08/052), on the SDD Section 19.4 Abstract This contribution suggests a MSCCH allocation scheme for multi-carrier. Purpose For review and discussion by IEEE 802.16m TG Notice Release Patent Policy 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. 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. 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>. Proposed MSCCH Allocation Scheme for Multi-Carrier Nan Li, Yuqin Chen ZTE 1. Introduction IEEE 802.16m shall provide support for an enhanced multicast broadcast service (E-MBS), providing enhanced multicast and broadcast spectral efficiency [1].It has been agreed that E-MBS may be transmitted via a dedicated carrier or a unicast/E-MBS mixed carrier. In detail, there could be three kinds of carrier application scenarios in IEEE 802.16m system: both mixed carrier and dedicated carrier, mixed carrier only and dedicated carrier only. Based on the consensus on frame and control channel structure, this contribution proposes a multicast service control channel (MSCCH) allocation scheme under these three scenarios for multi-carrier in IEEE 802.16m system. 1 IEEE C802.16m-09/0054 2. MSCCH allocation scheme for multi-carrier In the current SDD text [2], SBCH is used to provide a pointer for the AMS to find the location of MSCCHs and MSCCH is used to indicate physical layer parameters of MBS data channels for each service using joint coding. SBCH and MSCCH may also include other E-MBS control information, such as MBS zone ID list, MBS resource allocation information, etc. The E-MBS control information should be classified based on the carrier application scenario. 2.1 Scenario 1: mixed carriers coexisting with dedicated carrier E-MBS control information is classified into two levels: Information carried in SBCH: – MBS zone ID list indicating which zones the serving BS belongs to; – Each MBS zone resource allocation information, may include the pointers to MSCCHs for each MBS zone on each carrier, MBS scheduling interval, and MBS resource allocation pattern, etc.; – etc. Information carried in MSCCH: – MBS service and carrier mapping list (could be only included in the MSCCH carried in fully configured carrier); – Service data scheduling information and physical layer parameters, such as MCS. – MBS control information update indicator; – Service start indication,service stop indication; – etc. When a multi-carrier AMS completes access with one of the fully configured carriers and takes this carrier as its primary carrier, by the classification described above, it acquires MBS zone ID list, the location of MSCCHs and MBS zone resource allocation information from SBCH on its primary carrier. If the AMS is interested in EMBS service, it shall continue to read MSCCH on its primary carrier for the MBS service and carrier mapping list. A carrier switch may be executed if the service which the AMS cares is not on the current carrier. After switching, the AMS could continuously receive the E-MBS data which is indicated by the MSCCH on this carrier. MSCCH may also carry control information update indicator to indicate content change of SBCH or MSCCH, or both. The MSCCH may be transmitted periodically for reliability. The period is FFS. SBCH carrying E-MBS control information can be configured on all fully configured carriers. MSCCH should be configured on all carriers which carry E-MBS traffic. The allocation of MSCCHs of different MBS zone on each carrier is shown as Fig.1. Primary carrier (fully configured) ... Secondary carrier 1 (fully configured) ... Secondary carrier 2 (partially configured, dedicated carrier) ... SBCH MSCCH for MBS zone A MSCCH for MBS zone B MBS zone A Traffic 2 MBS zone B Traffic IEEE C802.16m-09/0054 Fig.1 MSCCH Allocation under Scenario 1 E-MBS control information may also be classified further into three levels: Information carried in SBCH: – MBS zone ID list indicating which zones the serving BS belongs to; – Each MBS zone resource allocation information, may include the pointer to Primary MSCCH (P-MSCCH), MBS scheduling interval ,and MBS resource allocation pattern, etc.; – etc. Information carried in P-MSCCH: – MBS service and carrier mapping list; – Location of Secondary MSCCH(S-MSCCH); – Service start indication,service stop indication; – etc. Information carried in S-MSCCH: – Service data scheduling information and physical layer parameters, such as MCS. – MBS control information update indicator; – etc. By this classification, a multi-carrier AMS which is interested in E-MBS shall decode and analyze P-MSCCH for the MBS service and carrier mapping list and the location of S-MSCCH. Then it may switch to the relevant carrier to receive the E-MBS data base on the content of S-MSCCH. The control information update indicator in S-MSCCH is used to indicate content change of SBCH, P-MSCCH, or S-MSCCH or all of them. The PMSCCH and S-MSCCH may be transmitted periodically for reliability and the period is FFS. SBCH carrying E-MBS control information can be configured on all fully configured carriers. P-MSCCH can be allocated on all fully configured carriers. S-MSCCH should be configured on all carriers which carry E-MBS traffic. The allocation of MSCCHs of different MBS zone on each carrier is shown as Fig.2. ... Primary carrier (fully configured) ... Secondary carrier 1 (fully configured) Secondary carrier 2 (partially configured, dedicated carrier) SBCH ... P-MSCCH MBS zone A S-MSCCH MBS zone B S-MSCCH MBS zone A Traffic MBS zone B Traffic Fig.2 P-MSCCH and S-MSCCH Allocation under Scenario 1 2.2 Scenario 2: mixed carrier only Under scenario 2, there are only mixed carriers in the system for E-MBS.E-MBS control information classification is the same as scenario 1, allocation of MSCCHs of different MBS zone on each carrier is shown 3 IEEE C802.16m-09/0054 in Fig.3 and Fig 4. Primary carrier Fully configured ... Secondary carrier Fully configured ... Secondary carrier Partially configured ... MSCCH for MBS zone A SBCH MSCCH for MBS zone B MBS zone B Traffic MBS zone A Traffic Fig. 3 MSCCH Allocation under Scenario 2 Primary carrier Fully configured ... Secondary carrier Fully configured ... Secondary carrier Partially configured ... SBCH P-MSCCH MBS zone A S-MSCCH MBS zone B S-MSCCH MBS zone A Traffic MBS zone B Traffic Fig. 4 P-MSCCH and S-MSCCH Allocation under Scenario 2 2.2 Scenario 3: dedicated carrier only E-MBS data could be transmitted only on dedicated carrier. In this case there is no need to allocate E-MBS subframes like scenario 1and scenario 2 in mixed carrier scenarios, which mean the parameters such as MBS scheduling interval, and MBS resource allocation pattern need not to be sent by the ABS. Classify E-MBS control information into two levels: Information carried in SBCH: – MBS zone ID list indicating which zones the serving BS belongs to; – The location of MSCCHs on each dedicated carrier; – MBS service and carrier mapping list; – etc. Information carried in MSCCH: – Service data scheduling information and physical layer parameters, such as MCS; – The location of the next MSCCH; – Service start indication,service stop indication; 4 IEEE C802.16m-09/0054 – MBS control information update indicator; – etc. SBCH carrying E-MBS control information can be configured on all fully configured carriers. MSCCH should be configured on all carriers which carry E-MBS traffic. Allocation of MSCCHs on each carrier in scenario 3 is shown in Fig.5. Primary carrier Fully configured ... EMBS dedicated carrier 1 ... EMBS dedicated carrier 2 ... SBCH MSCCH for MBS zone A MSCCH for MBS zone B MBS zone A Traffic MBS zone B Traffic Fig. 5 MSCCH Allocation under Scenario 3 Classify E-MBS control information into three levels: Information carried in SBCH: – MBS zone ID list indicating which zones the serving BS belongs to; – The location of P-MSCCH; – etc. Information carried in Primary MSCCH (P-MSCCH): – MBS service and carrier mapping list; – The location of S-MSCCH on each dedicated carrier; – Service start indication,service stop indication; – The location of the next P-MSCCH; – etc. Information carried in S-MSCCH: – Service data scheduling information and physical layer parameters, such as MCS. – MBS control information update indicator; – The location of the next S-MSCCH; – etc. SBCH carrying E-MBS control information can be configured on all fully configured carriers. P-MSCCH can be allocated on all fully configured carriers. S-MSCCH should be configured on all carriers which carry E-MBS traffic. Allocation of MSCCHs on dedicated carriers in scenario 3 is shown in Fig.6. 5 IEEE C802.16m-09/0054 Primary carrier Fully configured ... EMBS dedicated carrier 1 ... EMBS dedicated carrier 2 ... SBCH P-MSCCH MBS zone A S-MSCCH MBS zone B S-MSCCH MBS zone A Traffic MBS zone B Traffic Fig. 6 P-MSCCH and S-MSCCH Allocation under Scenario 3 4. Conclusion In this contribution, we discuss three carrier application scenarios in IEEE 802.16m E-MBS transmission. Under each scenario, the E-MBS control information may be classified into two levels (SBCH and MSCCH) or three levels (SBCH, P-MSCCH, S-MSCCH). Moreover, dividing MSCCH into P-MSCCH and S-MSCCH can make the function classification more clear and reduce the overhead. The content of SBCH, MSCCH or P-MSCCH and S-MSCCH varies with the classification. SBCH carrying E-MBS control information can be allocated on all fully configured carriers. It may contain MBS zone ID, MBS zone resource allocation information and MSCCH location information, etc. .These information are useful for the unicast AMS for the reason that it can transfer into power saving mode when EMBS data is multiplexed with unicast traffic using TDM. Also, in FDM,the unicast AMS should know the control block allocation when E-MBS multiplexed with unicast traffic. MSCCH should be configured on all carriers which carry E-MBS traffic. It may contain scheduling information and transmission mode for AMSs to decode E-MBS data. Also,MSCCH could be divided into P-MSCCH and S –MSCCH based on their different content ,function and transmission time scales. In this case, P-MSCCH can be allocated on all fully configured carriers. It may contain MBS service and carrier mapping list, the location of S-SMCCH, etc. S-MSCCH should be configured on all carriers which support E-MBS traffic. It may contain scheduling information and physical layer parameters for AMSs to decode E-MBS data. Locate MSCCH/S-MSCCH of each E-MBS zone on E-MBS traffic carrier benefits the minimum bandwidth capacity terminals and carrier switch AMS. The AMS which can only connect to one carrier at one time may continuously receive E-MBS data on secondary carrier without getting back to primary carrier frequently if there is no update in SBCH or P-MSCCH. 5. References [1] IEEE 802.16m-07/002r7, “802.16m System Requirements” [2] IEEE 802.16m-08/003r6, “IEEE 802.16m System Description Document” 6 IEEE C802.16m-09/0054 Text Proposal for SDD The following text is proposed to be adopted in the IEEE 802.16m system description document. ---------------------------------------------------- Start of the Text Proposal ---------------------------------------------[Insert the following text into this section] 19.4.10.X E-MBS control channel structure SBCH carrying E-MBS control information can be configured on all fully configured carriers. It may contain MBS zone ID list, MBS zone resource allocation information and MSCCH location information, etc. MSCCH should be configured on all carriers which carry E-MBS traffic. It may contain scheduling information and transmission mode for AMSs to decode E-MBS data. Also,MSCCH could be divided into P-MSCCH and S –MSCCH based on their different content ,function and transmission time scales. In this case, P-MSCCH can be allocated on all fully configured carriers. It may contain MBS service and carrier mapping list and the location of S-SMCCH and other E-MBS configuration parameters. S-MSCCH should be configured on all carriers which carry E-MBS traffic. It may contain scheduling information and transmission mode for AMSs to decode E-MBS data. -----------------------------------------------------End of the Text Proposal ---------------------------------------------- 7