1. Macro Diversity for E-MSB IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-08/981r1 Date Submitted: 2008-09-12 Source: Torsten Fahldieck Voice: +49-711-821-32163 Email: torsten.fahldieck@alcatel-lucent.de Alcatel-Lucent Venue: [802.16m] [16jm] Session #57, 16.-19. September, 2008 Base Contribution: IEEE C802.16m-08/981r1 Purpose: To propose Macro Diversity for E-MSB 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.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2. 2 Macro diversity for E-MBS Content Problem Description Solution Requirements Principle

3. 3 Problem Description Issue: –MS#1, MS#2, MS#3, … MS#n build one multicast group –All MS’s except MS#3 are located close to BS1 with good channel conditions –MS#3 is located at cell edge with poor channel conditions Consequence: –Multicast group has to use robust coding scheme with huge resource consumption

4. 4 Solution Macro diversity for E-MBS Terminal receives signal from 2 (or more) BS Better receive signal strength due to signal combining Less resource usage due to better coding scheme for the whole MBS group No need for regular handover for MBS connections (same connection parameters) Example: –MS#3 perform signal combining from BS1 and BS2 –Better SINR, more efficient coding scheme, less resource consumption, for the whole MBS group MS#1, MS#2, MS#3,.. MS#n Main issues for macro diversity How to provide synchronous MSB transmission? How to ensure that each BS autonomously schedules identical MBS bursts?

5. 5 Requirements for synchronized MBS DL frame incorporates MBS portion at same position (subchannel, symbol) MBS portions have identical size Structure and content of MBS portions have to be identical –Same amount of bursts Same modulation and coding Bursts located at same position (subchannel, symbol) Bursts have same size Bursts contains same MAC PDU’s –MAC PDU’s contains same data –For keeping the structure of the MBS portion simple, the bursts inside the MBS portion are placed in an ordered list

6. 6 Synchronized MBS Transmition1/2 BS#1–n form a E-MBS domain One E-MBS domain is controlled by one E-MBS server via network interface E-MBS server is a functional entity inside the Network Control and Management System E-MBS server broadcasts/multicasts MBS flows coming from the core network to all BS in the domain (data-plane) E-MBS server send control messages to all BS in the domain to enable synchronized MBS downlink transfer (control-plane)

7. 7 Synchronized MBS Transmission2/2 MBS servers send E-MBS control messages to all BS in its administrative domain E-MBS control messages force the individual running scheduler to generate identical MBS portions MBS portions is a reserved area in the downlink containing all E-MBS bursts E-MBS server sends control messages (not mandatory on every frame) –Initiation –Changes on MBS flow(s) Create, change, delete, bandwidth change

8. 8 MBS-Portion Synchronization

9. 9 Information in MBS Control Messages Position and size of MBS portion Frame number Time stamps Information about bursts (carried in the MBS Portion) –Ordered burst list –For each burst: Max size Associated parameters (Modulation, Coding…) Ordered list of connection identifiers –Connection identifiers (carried in a MBS Burst) For each Connection identifiers : –IP Classifier: MBS Packet ->MCID mapping rule –Security Association Fragmentation and packing parameters Max / min PDU/SDU size …

10. 10 Text proposal Insert the following text into SDD (IEEE 802.16m-08/003r4) section 15.x.x. – 15.x.x. Macro diversity for E-MBS An E-MBS zone is an administrative domain controlled by an E-MBS server. The E-MBS server is a functional entity inside the Network Control and Management System (NCMS). Within one E-MBS zone, basestations are able to transmit MSB data in a synchronized manner, which give the receiving terminals the opportunity to perform signal combining. The E-MBS server sends control messages to all basestations in its MBS zone. These control messages contain unambiguous information, which enable the individual running basestations to generate synchronized MSB portions. An MBS portion is an area in a downlink frames, which is exclusively reserved for MBS connections.