1. Proposal for the Self-organization & Self-optimization in IEEE 802.16m System Document Number: C80216m-08_xxx Date Submitted: January 6, 2008 Source: Juejun Liu ( juejunliu@huawei.com), Libra Xiao (libra_xiao@huawei.com), Zhengzheng Li (lizhengzheng@huawei.com), Ke Zeng (zengk@huawei.com), Jianjun Yang (yougth@huawei.com), Wu Xuyong (wuxuyong@huawei.com), Lian Yang (yang.lian@huawei.com)lizhengzheng@huawei.comzengk@huawei.comyang.lian@huawei.com Huawei Technologies Co., Ltd. xiaoshanpeng@chinamobile.comxiaoshanpeng@chinamobile.com, liaowenqi@chinamobile.comliaowenqi@chinamobile.com China Mobile. dongxiaolu@mail.ritt.com.cn; duying@mail.ritt.com.cn;duying@mail.ritt.com.cn CATR. suxin@mail.tsinghua.edu.cn; zhongxf@tsinghua.edu.cnsuxin@mail.tsinghua.edu.cnzhongxf@tsinghua.edu.cn Tsinghua University. qu.hongyun@zte.com.cn; fang.huiying@zte.com.cnqu.hongyun@zte.com.cn ZTE Co. Ltd. Venue: IEEE 802.16 Session #53, in Levi, Finland Base Contribution: C80216-08_xxx Purpose: For discussion by IEEE 802.16 Working Group 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 Contents What’s the purpose of organization –scope What to be organized –entity and components When to organize –environments status & relationships How we can organize –coordinative or uncoordinative

3. 3 What’s the purpose of organization scope Self Installation and Configuration Automatic resource allocation and distribution optimization –To avoid or eliminate the impact of harmful/destructive interference Network throughput ensuring Interference prevention & resolution –That’s what we can also understand as interference impact mitigation Enhancement for Coverage Awareness (for operator) Adjacent Blind Area information report –That’s combine the impact from deserved signal and interference signal

4. 4 What to be organized entities and components System –A Base Station and its Subscribers Community –A Community is composed of those systems which coordinate to resolve their interference. These systems can be operated by the same or different operators. Interference Neighborhood –An Interference neighborhood relates to a specific system. A system will perceive as an interference neighbor of other systems which create/receive harmful interference to/from it. The Figure blow shows some examples of neighborhood.

5. 5 When to organize environments status A system’s environment status is a collective radio signal situation of its BS and SSs, which compose of deserved signal and interference: –Signal Quality on the Receiver: RSSI & SINR –Interference impact: SINR degradation from interference (or INR)* –Interference source of the receiver which encounter harmful interference (for collaborative mechanism only) BS is responsible to collect the system’s environment status SS is responsible to report its recent radio signal situation to its serving BS

6. 6 When to organize relationships Relationships is between systems: Neighbor Relationship: it is a relationship between two systems, when the BS in at least one of these two systems may create interference higher than the acceptable interference threshold to at least one SS in another system, or at least one of the SSs in at least one of these two systems may create interference higher than the acceptable interference threshold to the BS in another system. It is assumed that SS to SS interference and BS to BS interference are resolved in advance by frequency separation (in case of FDD systems) or transmission frame synchronization (in case of TDD). Neighbor: A system is called a neighbor of system A, when it has a neighbor relationship with system A.

7. 7 When to organized relationships-formed by bi-directional interference

8. 8 When to organize relationships-formed by unidirectional interference

9. 9 Geographical Neighbor: –The Geographical neighbor relationship means at least one station in one of the system will be interference victim of at least one station in another system if they allocate the frequency into co-channel or adjacent channel. Encounter Neighbor: –The Encounter neighbor relationship means at least one station in one of the system is an interference victim of at least one station in another system. When to organize relationships- Geographical & Encounter Neighbor

10. 10 Coordinative mechanism relies on the exchange of protocol-based signaling in radio within Geographical neighborhood. –Stations in system need to measure radio signal parameters –Stations in system need to identify the interference source –BS take the responsibility to coordinate the action of its whole system and be responsible to negotiate among neighborhood/ community Uncoordinative mechanism relies on the only the radio information within the system, and do not exchange protocol-base signaling in radio within Geographical neighborhood. –Stations in system need to measure radio signal parameters –Stations in system do not identify the interference source –BS take the responsibility to coordinate the action of its whole system but not negotiate with other system Both Coordinative and Uncoordinative solution should be considered according to different usage scenario How we can organize coordinative or uncoordinative

11. 11 Conclusion 16m should refine scope of SON mechanisms and define entities and components, e.g. –System –Community –Neighborhood etc. 16m should include both coordinative and uncoordinative approaches for SON.

12. 12 Thanks!