IEEE C802.16m-09/1959
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Text for SON Message Formats (SON)
Date
Submitted
2009-08-28
Source(s)
Baowei Ji, Ying Li, Zhouyue Pi
bji@sta.samsung.com
Samsung Telecommunication America
+1-972-761-7167
Jungje Son, Hyunjeong Kang , Jaehyuk Jang,
Byungwook Jun, Jaehee Cho, Anshuman Nigam
Samsung Electronics
Re:
P802.16m/D1 SON
Abstract
To propose SON text
Purpose
To be discussed and adopted by TGm for 802.16m AWD
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>.
1
IEEE C802.16m-09/1959
Proposed Text for SON Message Formats (SON)
Baowei Ji, Ying Li, Zhouyue Pi, Jungje Son, Hyunjeong Kang, Jaehyuk Jang, Byungwook Jun,
Jaehee Cho, Anshuman Nigam
Samsung Electronics
1. SON Message Formats
The ABS and the AMS should follow the message flow shown in Figure 1 for neighbor discovery and self
optimization. The BS shall command all AMS using the AAI_SON-CMD() message to scan for neighbor
basestations. Having finished measurement, each AMS contends by sending at most one ranging code in a
ranging transmission opportunity (TXOP) following the contention rule stipulated in the previous
AAI_SON-CMD() message. The BS resolves the contention by sending the response message AAI_SON-RSP()
listing each indentified ranging code and the according UL burst allocation. The UL allocation and the format of
the report message AAI_SON-RSP() shall be derived from the previous AAI_SON-CMD() message. Having
received some reports, the BS might send a short version of the AAI_SON-CMD() listing all the BSs already
detected. AMS will contend only if they have information for other BSs that are not listed in this
AAI_SON-CMD() message.
BS
MS
MOB_SON_CMD()
Scan
Contention in SON Ranging Channels
MOB_SON_RSP()
MOB_SON_REP()
MOB_SON_CMD() with SON_Command = “111”
Contention in SON Ranging Channels
MOB_SON_RSP()
MOB_SON_REP()
Figure 1. SON Management Message Flowchart
2
IEEE C802.16m-09/1959
2. Coverage Hole Detection Functionality
ABS shall broadcast a CHD-indication field, which could be included in the superframe header (SFH. This
CHD-indication field has two possible values. The positive value enables coverage hole detection and report,
whereas the negative value disables coverage hole detection and report. During normal connection, an AMS
reads this CHD-indication field and is informed whether it should turn on the coverage hole detection and report
capability or not. If the AMS has just resumed connection and has CHD report ready for transmission, the AMS
shall evaluate the CHD-indication field in the current BS. It shall not send the report if the current BS has
disabled coverage hole detection and report functionality.
The network could enable the coverage hole detection and report functionality step by step. In the early stage of
network deployment, the network could set all the BSs to have the second value for the CHD-indication field
such that no reports should be sent because anyway the system is not fully covered yet. When the system has
covered a large enough area, the network could set the BSs inside the network to have the first value for the
CHD-indication field, meanwhile sets the BSs at the network border to have the second value for the
CHD-indication field. In this case, the cells with good coverage can further improves the coverage by collection
CHD report, whereas the cells at the network border does not have to suffer from numerous CHD reports
because the coverage hole detection and report functionality is disabled. Similarly, BS could set the second value
to the CHD-indication field if it is aware that the current cell and/or some neighbor cells have temporary
coverage problem, such that it does not suffer from a large number of unnecessary CHD reports.
3. CHD Message Format
The CHD report does not include ABS information if the detected coverage hole is in the same cell. The following
parameters shall be included in the AAI_CHD-REP message:
BS-Indicator
Indicates whether the current BS is the same as the previous serving BS when the MS lost connection. If they are same,
there is no need to report the information of the previous serving BS. Otherwise, the MS shall report the information of the
previous serving BS.
BS ID
BS Info
Those fields are included only if the previous serving BS is different from the current BS (see BS-Indicator). They are the
information of the previous serving BS.
MS Location
This is the 2-D or 3-D location of the MS when it lost connection with the previous serving BS.
Timestamp
This is the timestamp when the MS lost connection with the previous serving BS.
3