ETSI TR 101 589 V1.1.1 (2013-07)

Technical Report
Broadband Radio Access Networks (BRAN);
Very high capacity density BWA networks;
Protocols
2 ETSI TR 101 589 V1.1.1 (2013-07)

Reference
DTR/BRAN-0040009
Keywords
architecture, broadband, BWA, protocol, radio
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2013.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TR 101 589 V1.1.1 (2013-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Introduction . 8
4.1 Architecture for the underlaying system . 8
4.2 Radio resource management. 9
4.2.1 RRM functional decomposition in system architecture . 10
5 Frequency channel assignment . 10
5.1 Dynamic centralized frequency assignment . 10
5.1.1 Overall objectives . 10
5.2 Description of the algorithms . 11
5.2.1 Recovery procedure . 15
5.2.2 Centralized interference mitigation . 15
5.2.3 Adaptive resource allocation. 15
5.2.4 Centralized RRM macro-application . 15
5.2.5 Control plane primitives . 16
5.2.5.1 Information request . 16
5.2.5.2 New station insertion indication . 17
5.2.5.3 Capacity overload indication . 18
5.2.5.4 Station re-configuration request . 19
5.3 Autonomous distributed cognitive radio dynamic frequency assignment . 20
5.3.1 Spectrum sensing based dynamic frequency assignment . 21
5.4 Learning based cognitive dynamic frequency assignment . 22
5.4.1 Overview and general objectives . 22
5.4.2 Functional decomposition and message flows . 25
5.4.3 Control plane primitives . 26
5.5 Cognitive and docitive RRM . 27
5.5.1 Feature overview . 28
5.5.2 Functional decomposition . 28
5.5.3 Message flows . 29
5.5.4 Protocol primitives description . 31
6 RAN self-organization and optimization support . 33
6.1 Automatic neighbours discovery . 34
6.1.1 Polling . 35
6.1.2 Proximity reports . 36
6.1.2.1 Proximity reports configuration . 37
6.1.2.2 Proximity reporting . 37
6.1.3 Neighbour BS "Hello" handshake. 38
6.1.3.1 Hello request . 38
6.1.3.2 Hello response . 39
6.2 Neighbours data synchronization . 39
6.2.1 Overview . 40
6.2.2 Functional decomposition . 41
6.2.3 Message flows . 41
6.2.3.1 Radio configuration update (Pull) . 41
6.2.3.2 Radio configuration unsolicited update (Push) . 42
6.2.4 Protocol primitive description. 42
ETSI
4 ETSI TR 101 589 V1.1.1 (2013-07)
6.2.4.1 Neighbour information request . 42
6.2.4.2 Neighbour information response . 42
6.2.4.3 UCD/DCD count update . 43
6.2.4.4 UCD/DCD configuration exchange . 43
6.2.4.5 NBR-ADV construction . 44
6.3 Automatic FFR regulation for reuse 1 . 45
6.3.1 General FFR approach . 45
6.3.2 Inter-cell FFR coordination . 46
6.3.2.1 Resource blocks categories . 46
6.3.2.2 Measurements . 47
6.3.2.3 RRM function . 48
6.3.2.4 Protocol . 48
6.4 Technology-independent network protocols for coexistence support in LE bands . 50
6.4.1 Interference detection . 51
6.4.2 Discovery of interference source . 51
6.4.3 Association of neighbour and interference . 51
6.4.4 Communication exchange between neighbours to avoid or mitigate interference . 52
Annex A: Bibliography . 53
History . 57

ETSI
5 ETSI TR 101 589 V1.1.1 (2013-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Broadband Radio Access Networks
(BRAN).
ETSI
6 ETSI TR 101 589 V1.1.1 (2013-07)
1 Scope
The present document describes the specific protocols for systems providing a throughput of 1 Gbit/s/km . Such
systems include features such as self-backhauling in both licensed and un-licensed bands, cognitive-radio based
self-organization, etc.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 101 534 (V1.1.1) (2012): "Broadband Radio Access Networks (BRAN); Very high
capacity density BWA networks; System architecture, economic model and derivation of technical
requirements".
[i.2] S. Haykin: "Cognitive Radio: Brain-Empowered Wireless Communications", IEEE Journal on
selected areas in communications, vol. 23, pp. 201-220, February 2005.
[i.3] R. S. Sutton and A. G. Barto: "Reinforcement learning: An Introduction", The MIT Press, 1998.
[i.4] Ana Galindo-Serrano, Lorenza Giupponi, Pol Blasco and Mischa Dohler: "Learning from Experts
in Cognitive Radio Networks: The Docitive Paradigm" in Proceedings of 5th International
Conference on Cognitive Radio Oriented Wireless Networks and Communications
(CrownCom 2010), 9-11 June 2010, Cannes (France).
[i.5] M. N. Ahmadabadi and M. Asadpour: "Expertness based cooperative Qlearning", IEEE
Transactions on Systems, Man, and Cybernetics, Part B, vol. 32, no. 1, pp. 66-76, February 2002.
[i.6] IEEE 802.16-2012: "IEEE Standard for Air Interface for Broadband Wireless Access Systems".
ETSI
7 ETSI TR 101 589 V1.1.1 (2013-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
DL-MAP: structured data sequence that defined the mapping of the downlink
self-backhauling: wireless links between HBS and ABS which may share a frequency channel with the access
operation (in-band) and use in addition license-exempt spectrum such as 5 GHz or 60 GHz bands (out-of-band)
UL-MAP: structured data sequence that defined the mapping of the uplink
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AAA Authentication, Authorization, and Accounting
ABS Access BS
ACK Acknowledge
ARA Adaptive Resource Allocation
ASN Access Service Network
BS Base Station
BS-BS Base Station to Base Station
BSID Base Station IDentifier
BWA user Fixed, Nomadic or Mobile user
BWA Broadband Wireless Access
CIM Centralized Interference Mitigation
CINR Carrier to Interference and Noise Ratio
CM Conditional-Mandatory
CNR Carrier-to-Noise Ratio
DCD Downlink Channel Description
DFP Dynamic Frequency Planning
DL Downlink
DNS Directory Name Server
FA Frequency Assignment
FAID Frequency Assignment ID
FFR Fractional Frequency Reuse
FQDN Fully Qualified Domain Name
GPS Global Positioning System
GW Gateway
HBS Hub Base Station
HO HandOver
HSPA High Speed Packed Access
HSS Subscriber Station connected to HBS
ICIC Inter Cell Interference Coordination
ICS Interference Control Server
ID IDentifier
IE Information Element
IP Internet Protocol
IQ Intelligence Quotient
LE License Exempt
LRT Last Reset Time
LTE Long Term Evolution
MAC Medium Access Control
MCS Modulation and Coding Scheme
MIMO Multi-Input-Multi-Output
MME Mobile Management Entity
MS Mobile Station
ETSI
8 ETSI TR 101 589 V1.1.1 (2013-07)
NBL NeighBour List
NBR NeighBour Relation
NBS Neighbour BS
NDS Neighbours Data Synchronization
NV Non-Volatile
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
PHY PHYsical
P-MP Point to MultiPoint
RAN Radio Access Network
RAT Radio Access Technology
RB Resource Block
REQ Request
RF Radio Frequency
RP Recovering Protocol
RRA Averaging/Reporting Period
RRC Radio Resource Control
RRM Radio Resource Management
RRM-E RRM-Entity
RSP Response
RSSI Received Signal Strength Indicator
RTD Round Trip Delay
SBS Serving BS
SON Self Organizing Network
SOTA State Of The Art
SSDFA Spectrum Sensing based Dynamic Frequency Assignment
TBS Target BS
TLV Type - Length - Value (data structure)
TS Time Stamp
UCD Uplink Channel Description
UL Uplink
4 Introduction
The present document presents new possible protocols specific to wireless BWA network, as described in [i.1],
including heterogeneous elements (a two tier approach), combined use of licensed and license-exempt spectrum, very
low delay communications between network elements, enabling the operation of the network MIMO technology and of
the self-organization approaches.
TM
The description of the networking features is in general done using the WiMAX terminology, however should be no
barrier in using the 3GPP network for implementing this network.
4.1 Architecture for the underlaying system
The architecture presented in [i.1] is summarized below, for easing the reader understanding. Its main features are:
• Multiple access links aggregation.
• Self-backhauling link aggregation.
• Network MIMO (for downlink and uplink).
• Radio Resource Management.
• Direct BS-BS or MS-MS communication.
The system architecture aims to offer a cost efficient capacity density of 1 Gbit/s/km . Here, a HBS serves several
below-rooftop ABSs, which in turn serve the associated MSs. The HBS possesses several beams which are used to
communicate with ABSs in its beam-space. ABSs can communicate with each other via the serving HBS.
ETSI
9 ETSI TR 101 589 V1.1.1 (2013-07)
The Femto-BS and their associated subscribers may also operate in the un-licensed spectrum.
To simplify the presentation, the HBS-ABS links, which are self-backhaul links inside this system, may be named in the
present document "backhaul links". This naming should not be understood as HBS backhauling, which is outside of the
scope of the present document.
The system presented in the present document has the following basic architecture:
ACCESS
SELF-
BACKHAUL
BACKHAUL
Figure 4.1: Basic architecture
The scheme in figure 4.1 provides an overview of most of the possible wireless links in the present document. At the
top level of the architecture, HBSs are directly connected to the wired backhaul. If in some cases a wired link could not
be done, this link should be replaced by LE high data rate connectivity.
An in-band backhaul link and a LE link between HBSs may not be systematically done but could offer additional
networking capacities and an alternative, in case of a router failure for example.
At the ABS location there are two elements, which are the HSS and the ABS. The HSS component is associated to an
HBS or to another HSS (for direct communication and collaborative MIMO). ABS provides connectivity for the BWA
users.
To increase the coverage or to provide a larger throughput in a given area exists the possibility to deploy additional
stations called pico-ABS. Those stations are basically similar to ABSs as they are providing connectivity to BWA users.
The lower level of the architecture shows mobile station connectivity possibilities. MS connects itself to ABS as in the
standard P-MP architecture, but can also directly connect one to each other, and associate with two ABSs for MIMO
support.
4.2 Radio resource management
This clause presents protocols and procedures related to RAN RRM and dynamic resource (frequency, power)
assignment. The description relates to the air interface and the network interfaces and presents reference design for
procedures and protocol primitives, required to support the aforementioned RRM mechanisms.
ETSI
10 ETSI TR 101 589 V1.1.1 (2013-07)
4.2.1 RRM functional decomposition in system architecture
TM
The functional decomposition is based on the state-of-the-art WiMAX and 3GPP standards, where Radio Resource
Management (RRM) functional entity is located in the Base Station/eNodeB, while ASN GW/MME may act as a
protocol relay function, but do not implement RRM-specific functions.
ASN GW/ MME ASN GW/ MME
R4/ S10
Relay Relay
R6/ S1
BS/ eNodeB BS/ eNodeB
R8/ X2
RRM RRM
functional functional
entity entity
TM
Figure 4.2: RRM functional entities in the SOTA WiMAX and 3GPP LTE architectures
The RRM entity may implement both RRM Client and RRM Server entities, thus being able to issue information
queries and to provide instructions. This is the de-centralized RRM approach, where there is no centralized entity
controlling and coordinating the radio resource allocation in the particular geographical area with multiple BSs
providing coverage and capacity. Coordination is done between RRM entities of different BSs over the R8/X2 reference
points or over R6/S1 reference points via ASN GW/MME assuming "relay" functionality.
The following RRM features are considered in the present document and may be taking the advantage of the addressed
system RRM split:
• Dynamic centralized and autonomous distributed frequency assignment.
• Cognitive and docitive power assignment.
• Support of advanced MIMO schemes.
• Self-Organization and Optimization features.
5 Frequency channel assignment
5.1 Dynamic centralized frequency assignment
5.1.1 Overall objectives
The centralized dynamic RRM protocol is based on an overall supervision of the radio network status, and tries to
optimize radio link resources depending on interference levels, throughput load and architecture deployment.
Certain extent of information is required for this purpose, which mainly consist of different requests or triggered alarms
informing the centralized RRM entity of the current status. The dynamic protocols act only by restraining or increasing
stations resources, and providing local RRM segments the choice to optimize links to a more specific level. Coexistence
is therefore easily ensured.
The centralized dynamic RRM entity (RRM-E) can be hosted either in HBS or in external equipment. It includes
different operating functions realized on a proactive basis with regular survey or in a reactive fashion while receiving
resource deficit alarms from the given sectors.
ETSI
11 ETSI TR 101 589 V1.1.1 (2013-07)
The knowledge of deployment topology allows Centralized RRM-E to perform initial distribution of frequency
resources to the overlapping stations, with further iterative dynamic adaptations. This function is called Dynamic
Frequency Planning (DFP).
In a second step, deployment topology awareness may allow it to realize adaptation of the network in case of a station
failure. This function is called Recovering Protocol (RP).
In the case of significant interference detection, which cannot be compensated on the local level, the centralized RRM
can impose a more robust link on specific network sections. This function is called Centralized Interference Mitigation
(CIM).
Finally, for the purpose of user data throughput maximization in the given segment (cluster), the centralized RRM may
dynamically redistribute radio resources, providing some selected stations with more resources while other stations are
provided with fewer resources, resulting in lower capacities. This function is called Adaptive Resource Allocation
(ARA).
5.2 Description of the algorithms
The procedures related to Dynamic Frequency Planning (DFP) should be performed automatically upon initial RAN
segment activation and after that periodically or event driven to take into consideration global evolutions of the radio
access network deployment characteristics. The main purpose of the cluster radio resource management is to minimize
interference impact in the system's deployment providing Centralized RRM-E with information available in other
distributed RRM entities, e.g. ABSs (for example, to report interferences at a cell edge).
The centralized RRM entity collects all useful information required to adapt the frequency planning and allow channels
allocations suiting the traffic load requirements
To avoid the performance degradation, these periodic updates should be scheduled while network load decreases (at
night or during off-load hours). However, an operator can force the centralized algorithm to operate and then to update
the overall channels allocation for the different stations. This process can be relevant especially while a station is being
removed, added or modified.
Figure 5.1 then explains the algorithm in its fundamental steps.

Figure 5.1: Dynamic frequency planning algorithm
ETSI
12 ETSI TR 101 589 V1.1.1 (2013-07)
As shown above, and apart from the initial state configuration, the process includes different sub-processes which will
be depicted later. A certain amount of information about the network segment is required. Having prior fresh
information will result in more effective channel allocation.
This information list includes the following parameters:
• List of ABS stations
• For each of those stations:
- Deployment parameters:
Location
Antenna type (among a known list, for gain, and aperture)
Antenna orientation
- Station capacities (time stamped):
Available bandwidth
Available channels (with interferences levels of them)
CNR/CINR threshold
- Required throughput (time stamped)
• The general propagation model for the Network surrounding environment
Two of those information elements are critical and have to be known:
• List of ABS stations the centralized RRM-E is responsible for
• The adapted propagation model
The aforementioned frequency assignment process results in configuration of the relevant stations with the channels
allowed for their usage.
The process starts with the identification of the network segment requirements in terms of throughput. Based on this
information, different priorities are assigned for the corresponding stations. The priority of the station is the determinant
factor for the channel assignment protocol, as the nodes with higher priority will be the firsts to get channel
assignments, and, correspondingly, will be less dependent on other stations assignments.
Once the station prioritization is accomplished, nodes are iteratively assigned with a frequency channel, one channel at
a time, meaning that after all stations were assigned a primary channel, the process restarts with the top priority station
assigning a secondary channel and so on. The process terminates when no available channels have been left.
Finally the Centralized RRM-E sends the requests to each station informing it about the assigned frequency channels.
Figure 5.2 presents the steps required for the stations information collection process.
ETSI
13 ETSI TR 101 589 V1.1.1 (2013-07)

Figure 5.2: Stations information collection process
This process uses another set of primitives designed for the collection of information from the known stations. The
details of those primitives are given in continuation.
In this process, the Centralized RRM-E is checking the timestamp of the data related to the corresponding node in order
to ensure its freshness.
In the case of periodic information collection process, the delivered data may be suppressed, sending only the
parameters that have been changed and thus reducing backhauling throughput requirements. Otherwise, if the process is
event-driven, all the parameters have to be included in the response message.
Once the network database is updated, the stations are assigned with the priorities based on different kinds of
parameters.
ETSI
14 ETSI TR 101 589 V1.1.1 (2013-07)

Figure 5.3: Stations prioritizing process
The first considered parameter is the level of interference with other stations of the list. Most interfering stations are
assigned with higher priorities, so that they will be assigned with frequency channels before other stations.
This initial prioritization should be tempered with other operational requirements related to the stations location,
coverage area, and their significance.
The priority value is increased for stations which have higher throughput needs (commercial areas, stadiums, etc.),
stations having larger coverage (more risks of being jammed by external systems), or stations having a specific
significance (serving the special events, providing coverage for the area with nearby station failure recovery, etc.).
Finally the stations are allocated with the frequency channels as depicted in figure 5.4.

Figure 5.4: Channel allocation process
As presented above, the allocation process initially identifies if the considered station has more dedicated channels than
others (channels with low interference, and not shared with neighbour stations). The dedicated channels are used before
others to comply with the station bandwidth requirements. In order to avoid allocations with reduced channel spacing
for a given node, channels should be allocated randomly inside the preferred frequency band.
After that, the actual allocation may be repeated depending on the station necessity for more bandwidth (e.g. two
adjacent channels may be provided to increase the station capacity and peak rate).
ETSI
15 ETSI TR 101 589 V1.1.1 (2013-07)
5.2.1 Recovery procedure
The recovery procedure is based on the centralized dynamic frequency planning, with the additional aspect of station
failure detection. In this procedure, stations status is periodically checked, just more frequently than the dynamic
frequency planning.
This way the station failure can be detected quite quickly and the system can adjust to the new constraints. In the case of
failure detection, the centralized RRM-E will firstly consider the neighbour stations power limitations, increase power if
possible, and re-run the frequency channel assignment process.

Figure 5.5: Station failure recovery procedure
5.2.2 Centralized interference mitigation
In the case that the station detects performance degradation below the threshold because of high interference level and
no useable channels can be found locally with acceptable noise/interference levels, the request may be sent to the
centralized RRM entity to readjust its dynamic frequency planning.
The request is sent including the node's current frequency channels. The subsequent frequency allocation procedure is
performed considering the channels previously allocated to the given station as the lower priority channels. Then other
resources will be selected and provided to the node for its local cognitive assignment decisions.
5.2.3 Adaptive resource allocation
In the case of some special events, such as New Year fests, throughput required in some hot-spots may drastically
increase. The centralized RRM can then be triggered to readjusts its channel assignment model and to provide wider
frequency bands to some ABSs. This process is basically the same as the dynamic frequency planning but with a direct
wide band assignment for those stations.
5.2.4 Centralized RRM macro-application
The hierarchy of centralization nodes for radio resource management may be introduced because previously presented
topology assumes centralized RRM entity for a number of Access Base Stations (e.g. collocating centralized RRM-E in
HBS serving the associated ABSs). However, similar RRM-E function may be introduced at the higher level, managing
multiple HBSs.
In the case of frequency bands sharing for backhaul and access tiers, the centralized RRM-E may be responsible for the
channels distribution between HBSs and ABS. In this situation, the algorithm should be adjusted to consider
backhauling tier propagation model (HBS multi-beam antenna, etc.). Also, the Backhaul Tier stations (HBSs) should be
provided with higher priority than access base stations.
ETSI
16 ETSI TR 101 589 V1.1.1 (2013-07)
5.2.5 Control plane primitives
The following clause presents control plan message flows and primitives designed to support the centralized RRM-E
concept.
5.2.5.1 Information request
The purpose of Information request procedure is to collect the radio-related measurements from the particular BS in
order to provide the centralized RRM Entity with a clear knowledge of the current status.
The message flow corresponding to this request is illustrated in figure 5.6.
RRM-E Local
ABS
RRM-E Authenticator database
1 ) RRME_Info_Req
2 ) RRME_Info_Req
3 ) RRME_Info_Req
4 ) RRME_Info_Rsp
5 ) RRME_Info_Rsp
6 ) RRME_Info_Rsp
Figure 5.6: Information request message flows
Step 1
The centralized RRM-E sends an RRM-E_Info_Req message to each of its ABSs. Messages are forwarded through HBS
and HSSs to reach ABSs.
Step 2
Each ABS forwards the request to its collocated RRM-E Authenticator, which checks the source RRM-E validity.
Steps 3 and 4
If authorized, the request is forwarded to the local RRM information database. The Response message is sent back with
the Status_Table including the different available channels, measured interference levels, and deployment specificities.
Steps 5 and 6
The ABS sends back the successful response message to the RRM-E.
Table 5.1: RRM-E_Info_Req
Message purpose
Query RRM-related information from a node
Trigger for the
Triggered by the centralized RRM-E
message generation
Source Centralized RRM-E
Destination
ABS
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
RRM-E_Id M The centralized RRM-E identifier to be recognized by
ABSs.
ABS Id M The identity of the station, which information is
requested.
Information Key M Bitmap indicating what information is requested.

ETSI
17 ETSI TR 101 589 V1.1.1 (2013-07)
Table 5.2: RRM-E_Info_Rsp
Message purpose
Delivers RRM related information (such as deployment and capacity information) to
the centralized RRM-E
Trigger for the Triggered by an Information request message (RRM-E_Info_Req)
message generation
Source ABS
Destination Centralized RRM-E
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
Status_Table M Contains ABSs deployment specificities (GPS location,
antenna type and aiming direction), and RF capacities
(available channels, output power, interferences levels if
known).
Failure Indication O Failure indication providing the code of the
corresponding error cause.
5.2.5.2 New station insertion indication
A new station insertion requires RRM adaptations. A new ABS acceding the access network and successfully
recognized by the AAA server sends an insertion request to the centralized RRM entity.
The corresponding message flow is illustrated in figure 5.7.
New
AAA RRME
ABS
1 ) RRM_Insertion_Req
2 ) Authentication_Req
3 ) Authentication _Rsp
4 ) RRM_Insertion_Ack
Figure 5.7: A new station insertion message flow
Step 1
The newly arrived ABS generates and sends RRM_Insertion_Req message to the Centralized RRM-E, including the
deployment topology related information (such as e.g. a location, etc.) and its authentication parameters.
Step 2
Based on the ABS geo-location, the Centralized RRM-E decides whether it takes responsibility of the new coming
station. If positive, the Centralized RRM-E authenticates the received request with AAA server by sending
Authentication_Req message to AAA. Otherwise, the centralized RRM-E responds back with RRM_Insertion_Ack
message with Failure Indication parameter indicating the error cause (e.g. "wrong domain").
Step 3
AAA authenticates the request message and if positive, sends Authentication_Rsp message, authorizing ABS operation
to the Centralized RRM-E and providing the corresponding authorization parameters. If authentication fails, AAA
returns "authentication failure" indication.
ETSI
18 ETSI TR 101 589 V1.1.1 (2013-07)
Step 4
The Centralized RRM-E responds to the ABS with RRM_Insertion_Ack message. If necessary, a new dynamic
frequency planning will be performed. In the case "authentication failure" indication has been provided by AAA server,
the Centralized RRM-E sends RRM_Insertion_Ack message with Failure Indication set to the value providing the error
cause (e.g. "request authentication failure").
Table 5.3: RRM_insertion_Req
Message purpose Request for a new station insertion in the access network
Trigger for the Triggered by the new node/station activation
message generation
Source ABS
Destination Centralized RRM-E
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
ABS Id M The identifier of the ABS node.
Deployment Topology M The information blob including parameters related to the
Info station deployment (such as e.g. station location,
antenna pattern direction and tilt, etc.).
ABS Authentication M Authentication extension providing the capabilities for
Extension message source authentication and possibly providing
other security means (such as message integrity
protection and non-repudiation).

Table 5.4: RRM_insertion_Ack
Message purpose Respond for the new station insertion request, providing the result of operation and the
station operational parameters
Trigger for the
Triggered by RRM_insertinon_Req message reception and request authentication
message generation transaction completion
Source Centralized RRM-E
Destination
ABS
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
ABS Id M The identifier of the ABS node.
RRM-E_Id M The centralized RRM-E identifier to be recognized by
ABSs.
Result Indication M Provides the result of the "insertion" operation (success,
failure).
RRM Config O Radio configuration parameters to be used by the station.
It includes the list of the selected frequency channels
available for local assignment.
Failure Indication O Failure indication providing the code of the corresponding
error cause.
5.2.5.3 Capacity overload indication
Overload alarm is sent by the station to the Centralized RRM-E to indicate increase in the node throughput
requirements. If possible, the Centralized RRM-E will provide the node with a larger frequency band and/or better
quality channels in order to improve its performance.
ETSI
19 ETSI TR 101 589 V1.1.1 (2013-07)
ABS
RRME
1 ) RRM_Overload_Alarm
2 ) RRM_Overload_Ack
Figure 5.8: Overload alarm message flow
Step 1
While triggered by the threshold overstep, the ABS sends RRM_Overload_alarm message to the Centralized RRM-E.
This message includes indication of its throughput needs.
Step 2
The Centralized RRM-E receiving the alarm, sends back an acknowledgment to the ABS. If possible, it will send later
another message providing the ABS with the required resources.
Table 5.5: RRM_Overload_Alarm
Message purpose Provides signal indicating the station throughput overload to the Centralized RRM-E
Trigger for the
Triggered by the station throughput crossing the predefined threshold
message generation
Source ABS
Destination Centralized RRM-E
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
ABS Id M The identifier of the ABS node.
RRM-E_Id M The centralized RRM-E identifier.
Current throughput O Current throughput level (indication for RRM-E to
allocate sufficient bandwidth).
Required throughput O Indicates the station capacity demand.

NOTE: RRM_Overload_Ack message serves the purpose of the message transaction completion and does not
include any parameters.
5.2.5.4 Station re-configuration request
The purpose of this message is to send the actual configuration parameters to the station.
RRME ABS
1 ) RRME_Reconf_Req
2 ) RRME_Reconf_Ack
Figure 5.9: Re-configuration request message flow
ETSI
20 ETSI TR 101 589 V1.1.1 (2013-07)
Step 1
The RRM-E sends for each node under its responsibility a personalized message including the required configuration.
Step 2
The ABS checks that the originated RRM-E is the right one. If legitimate, the node will answer an acknowledgement to
the re-configuration request and adapt its functional parameters.
Table 5.6: RRM-E_Reconf_Req
Message purpose Delivers RRM configuration parameters to the ABS
Trigger for the Triggered by successful DFP procedure completion
message generation
Source Centralized RRM-E
Destination ABS
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
RRM-E_Id M The centralized RRM-E identifier.
ABS Id M The identifier of the ABS node.
Reconfig Reason M Indicates the reason of the station reconfiguration.
RRM Config M Radio configuration parameters to be used by the
station. It includes the list of selected frequency
channels available for local assignment.

Table 5.7: RRM-E_Reconf_Ack
Message purpose Response for RRM-E_Reconf_Req message
Trigger for the RRM-E_Reconf_Req message reception
message generation
Source ABS
Destination Centralized RRM-E
List of Information Elements
IE Name MANDATORY/OPTIONAL Description
Result Indication M Provides the result of the
...