Sie sind auf Seite 1von 12

Self-Organizing Networks and Self-Governing Networks

Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

A paper on concepts and features of

Self-Organizing Network and Self-Governing Networks

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

Contents
1. 2. 3. Introduction Telecommunication Resources Features 3.1 Coverage and capacity optimization 3.2 Energy Saving 3.3 Interference Reduction 3.4 Automated Configuration of Physical Cell Identity 3.5 Mobility robustness optimisation 3.6 Mobility Load balancing optimisation 3.7 RACH Optimisation 3.8 3.9 3.10 Automatic Neighbour Relation Function Inter-cell Interference Coordination Self-Establishment of a new eNodeB

1.Introduction
As a consequence of flattening the access network architecture in E-UTRAN (due to removal of the RNC) it is likely that a network operator will require more Release 8 eNodeBs than Release 7 NodeBs in order to cover an equivalent geographical area.
2

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

Network operators have also articulated their requirement to have more flexibility over the choice of eNodeB vendor, irrespective of the MME or NMS vendor. In order to reduce the operating expenditure (OPEX) associated with the management of this larger number of nodes from more than one vendor the concept of the Self-Organizing Network (SON) is introduced. Automation of some network planning, configuration and optimisation processes via the use of SON functions can help the network operator to reduce OPEX by reducing manual involvement in such tasks. In 3GPP Release 8 many of the signalling interfaces between network elements are standardised (open) interfaces. Significant examples in the context of SON are the X2 interface between eNodeBs and the S1 interface between eNodeB and the EPC (e.g. MME, SGW). SON algorithms themselves will not be standardised in 3GPP.

2.Telecommunication Resources
The OAM system: The location of any SON function(s) within the OAM system will also be specific to each individual use case. SON Function: The SON algorithm and associated processes that automatically determines the optimum configuration, connectivity, or installation parameters for a network element. References-32.500

3.1
i)

Name of Feature-Coverage and capacity optimization


Providing optimal coverage This objective requires that in the area, where LTE system is offered, users can establish and maintain connections with acceptable or default service quality, according to operators requirements. It implies therefore that the coverage is continuous and users are unaware of cell borders. The coverage must be therefore provided in both, idle and active mode for both, UL and DL.

Description-

ii) Providing optimal capacity While coverage optimization has higher priority than capacity optimization in Rel-9, the coverage optimization algorithms must take the impact on capacity into account. Since coverage and capacity are linked, a trade-off between the two of them may also be a subject of optimisation. The following scenarios shall be considered in capacity and coverage optimization. 1. E-UTRAN Coverage holes with 2G/3G coverage 2. E-UTRAN Coverage holes without any other radio coverage 3. E-UTRAN Coverage holes with isolated island cell coverage 4. E-UTRAN cells with too large coverage
3

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

Network Elements and Interfaces Involved-

Operator shall be able to configure the objectives and targets for the coverage and capacity optimisation functions differently for different areas of the network. The IRPAgent shall provide a capability allowing the IRPManager to manage tradeoffs between coverage and capacity using policies.

References 32.521, 36.902

3.2

Name of Feature-Energy Saving

DescriptionEnergy savings based on enabling the possibility, for a cell providing additional capacity in a deployment where capacity boosters can be distinguished from cells providing basic coverage, to be switched off when its capacity is no longer needed and to be re-activated on a need basis. The solution builds upon the possibility for the eNB owning a capacity booster cell to autonomously decide to switch off such cell to lower energy consumption (dormant state). The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. All peer eNBs are informed by the eNB owning the concerned cell about the switch-off actions over the X2 interface, by means of the eNB Configuration Update procedure. All informed eNBs maintain the cell configuration data also when a certain cell is dormant. ENBs owning non-capacity boosting cells may request a re-activation over the X2 interface if capacity needs in such cells demand to do so. This is achieved via the Cell Activation procedure. The eNB owning the dormant cell should normally obey a request. The switch-on decision may also be taken by O&M. All peer eNBs are informed by the eNB owning the concerned cell about the re-activation by an indication on the X2 interface.

Network Elements and Interfaces InvolvedReferences- 36.300, 36.902

O&M, X2 Control Plane

3.3

Name of Feature- Interference Reduction

DescriptionCapacity could be improved through interference reduction by switching off those cells which are not needed for traffic at some point of time, in particular home eNodeBs when the user is not at home. Expected outcome: Increased capacity through interference reduction. Increased quality through interference reduction.

Network Elements and Interfaces InvolvedReferences 36.902


4

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

3.4 Name of Feature- Automated Configuration of Physical Cell Identity


DescriptionThe physical cell identity, or L1 identity (Phy_ID in this document), is an essential configuration parameter of a radio cell, it corresponds to a unique combination of one orthogonal sequence and one pseudo-random sequence, and 504 unique Phy_IDs are supported leading to unavoidable reuse of the Phy_ID in different cells (TS 36.211 [3]). When a new eNodeB is brought into the field, a Phy_ID needs to be selected for each of its supported cells, avoiding collision with respective neighbouring cells (the use of identical Phy_ID by two cells results in interference conditions hindering the identification and use of any of them where otherwise both would have coverage). Traditionally, the proper Phy_ID is derived from radio network planning and is part of the initial configuration of the node. The Phy_ID assignment shall fulfil following conditions,

collision-free: the Phy_ID is unique in the area that the cell covers confusion-free: a cell shall not have neighbouring cells with identical Phy_ID

Network Elements and Interfaces Involved- Self-configuration case be


applied during initial cell configuration.

References 36.902

3.5

Name of Feature- Mobility robustness optimisation

DescriptionRRM in one eNB can detect problems and adjust the mobility parameters. These functionalities can be added for the purpose. i) Detection of Too Late HO.

If the UE mobility is more aggressive than what the HO parameter settings allow for, handover can be triggered when the signal strength of the source cell is already too low leading to a RLF; or handover may not be
5

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

triggered at all if a RLF preempts it. Signature of Too Late HOs may be summarized by: ii) RLF in the source cell before the HO was initiated or during HO procedure, UE re-establishes the connection in a cell different than the source cell. Detection of Too Early HO.

Too early HO can be triggered when the UE enters unintended island of coverage of another cell contained inside the coverage area of the serving cell. This is a typical scenario for areas where fragmented cell coverage is inherent to the radio propagation environment, such as dense urban areas. Signature of Too Early HO may be summarized by: RLF occurred short time after the UE successfully connected to the target cell UE re-establishes the connection in the source cell

iii)

Detection of HO to a Wrong Cell.

If the Cell Individual Offset (CIO), parameters are set incorrectly, the handover, albeit timed correctly, will be directed towards a wrong cell. Signature of HO to a wrong cell may be summarized by: RLF occurred short time after the UE succesfully connected to the target cell UE re-establishes the connection in a cell other than the source cell or the target cell.

Four Parameters can be optimised (a) (b) (c) (d) Hysteresis Time to Trigger Cell Individual Offset Cell reselection parameters.

Network Elements and Interfaces Involved- O&M


It is proposed that certain information may be exchanged between neighboring eNBs, to facilitate optimization of mobility robustness parameters: Report of RLF failures: This report includes the following information elements. Failure Cell ID: PCI of the cell in which the RLF occurred. Reestablishment Cell ID: PCI and (optionally) ECGI of the cell where RL re-establishment attempt is made C-RNTI: C-RNTI of the UE in the cell where RLF occurred.

References 32.521, 36.902


6

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

3.6 Name of Feature- Mobility Load balancing optimisation


DescriptionOptimisation of cell reselection/handover parameters in order to cope with the unequal traffic load and to minimize the number of handovers and redirections needed to achieve the load balancing. These scenarios must be considered for load balancing. Each scenario shall include the load balancing on intra-frequency, inter-frequency, and inter-RAT. 1. Overlapping Coverage 2. Hierarchical Coverage 3. Neighbouring Coverage

Network Elements and Interfaces Involved- X2 and S1 Interface.


(i)Intra-LTE load balancing- An eNB monitors the load in the controlled cell and exchanges related information over X2 or S1 with neighbouring node(s). The signalling of composite available capacity impacts the X2AP protocol and the necessary support is introduced in the Resource Status Reporting procedures. The negotiation of HO trigger thresholds is also defined in the X2AP protocol by means of the Mobility Settings Change procedure. (ii) Inter-RAT load balancing- BSSGP specification has impacted where the cell load reporting has been specified as a new RIM application. In order to introduce routing of RIM messages between UTRAN and E-UTRAN, alignment CRs concerning the following interfaces have been done. - RANAP - S1AP - CN interfaces using GTPv2-C.

References - 36.404, 36.902, 32.521, 36.300

3.7

Name of Feature- RACH Optimisation

Description- The primary objectives of a RACH optimization function are:


a.) Minimize access delays for all UEs in the system b.) Minimize UL interference due to RACH Secondary objective is furthermore: c.) Minimize interference among RACH attempts. Consequently, the RACH optimization function will attempt to automatically set several parameters related to the performance of RACH, for example: PRACH configuration index (resource unit allocation and format) RACH preamble split (among dedicated, random-high, random-low) RACH backoff parameter value PRACH transmission power control parameters Expected results of SON is Reduction in access delay, which results into: short call setup delays short data resuming delays from UL unsynchronized state
7

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

short handover delays high call setup success rate high handover success rate

Network Elements and Interfaces InvolvedUE and eNB measurements are provided to the SON entity, which resides in the eNB. An eNB exchanges information over the X2 interface with its neighbors for the purpose of RACH optimisation. The PRACH Configuration is exchanged via the X2 Setup and eNB Configuration Update procedures. An eNB may also need to communicate with the O&M in order to perform RACH optimization.

Inputs Required The setting of RACH parameters depends on a multitude of factors, e.g.: - the uplink inter-cell interference from the Physical Uplink Shared Channel (PUSCH) - RACH load (call arrival rate, HO rate, tracking area update, traffic pattern and population under the cell coverage as it affects the UL synchronization states and hence the need to use random access) - PUSCH load - the cubic metric of the preambles allocated to a cell - whether the cell is in high-speed mode or not - uplink (UL) and downlink (DL) imbalances. Since these are affected by network configuration (e.g., antenna tilting, transmission power settings and handover thresholds), any change in these configurations would also affect the optimum RACH configuration. For example, if the antenna tilting of a cell is changed, the coverage of cells in the vicinity will be changed, consequently affecting the call arrival rate and handover rate at each cell. This will affect the amount of RACHs in each cell, including the usage per range of preambles. Then, the operator will have to check the RACH performance/usage in each cell and detect any problems on RACH associated with the applied changes. If required, it may further trigger some adjustments in RACH configuration. Measurements on the RACH performance/usage are needed to be collected at a SON entity. An automatic RACH optimization function monitors the prevailing conditions, e.g., a change on RACH load, uplink interference, and determines and updates the appropriate parameters. The desired performance of RACH may be expressed in terms of the access probability AP(m) and access delay probability ADP(), where random access attempt number m=1,2,3........ , Access delay probability is the probability that the access delay is less than . Various alternatives are possible, although it is noted that ADP is more appropriate since it explicitly takes into account the delay involved in the random access procedure as discussed in the objectives of RACH optimization

References- 36.300, 36.331, 36.902, 32.521

3.8 Name of Feature- Automatic Neighbour Relation Function


DescriptionANRF allows eNB to build and maintain neighbour relationships. The ANR function in the eNB relates to the Use Cases Establishment of new eNB in network and Optimisation of the
8

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

neighbourhood list. For Establishment of new eNB in network. If the operator so chooses, the OAM system adds and configures NRs before the eNB goes into operation. For Optimisation of the neighbourhood list, the ANR function deals with automatic NR additions and removals. It minimizes the need for planning and configuring NRs. If the operator so chooses, the OAM system adds and configures NRs or removes NRs after the eNB goes into operation.

A Neighbour cell Relation (NR) in the context of ANR is defined as follows: An existing Neighbour Relation from a source cell to a target cell means that eNB controlling the source cell: a) Knows the ECGI/CGI and PCI of the target cell. b) Has an entry in the Neighbour Relation Table for the source cell identifying the target cell. c) Has the attributes in this Neighbour Relation Table entry defined, either by O&M or set to default values. For each cell that the eNB has, the eNB keeps a NRT, see Figure 22.3.2a-1. For each NR, the NRT contains the Target Cell Identifier (TCI), which identifies the target cell. For E-UTRAN, the TCI corresponds to the E-UTAN Cell Global
9

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

Identifier (ECGI) and Physical Cell Identifier (PCI) of the target cell. Furthermore, each NR has three attributes, the NoRemove, the NoHO and the NoX2 attribute. These attributes have the following definitions: - No Remove: If checked, the eNB shall not remove the Neighbour cell Relation from the NRT. - No HO: If checked, the Neighbour cell Relation shall not be used by the eNB for handover reasons. - No X2: If checked, the Neighbour Relation shall not use an X2 interface in order to initiate procedures towards the eNB parenting the target cell. Neighbour cell Relations are cell-to-cell relations, while an X2 link is set up between two eNBs. Neighbour cell Relations are unidirectional, while an X2 link is bidirectional. The ANR function also allows O&M to manage the NRT. O&M can add and delete NRs. It can also change the attributes of the NRT. The O&M system is informed about changes in the NRT.

Automatic Neighbour Relation Function


The ANR (Automatic Neighbour Relation) function relies on measurement reports send by UE. 1. The UE sends a measurement report regarding cell B. 2. The eNB decides to add this neighbour relation. If needed, setup a new X2 interface towards this eNB. Network Elements and Interfaces Involved- OAM, X2 addition and deletion functionality in IRP Manager. UE Support Required.

References- 36.300, 32.511, 36.902

3.9

Name of Feature- Inter-cell Interference Coordination

DescriptionIn reuse one cellular networks mutual interference between cells occurs. Within the OFDM and SC-FDMA based LTE system interference has to be coordinated on the basis of the physical resource blocks (PRBs). Such interference can be reduced or avoided in uplink and downlink by a coordinated usage of the available resources (PRBs) in the related cells which leads to improved SIR and corresponding throughput. This coordination is realized by restriction and preference for the resource usage in the different cells. This can be achieved by means of ICIC related RRM mechanisms employing signalling of e.g. HII, OI and DL TX Power indicator. ICIC RRM might be configured by ICIC related configuration parameters like reporting thresholds/periods and preferred/prioritized resources. Then these have to be set by the operator for each cell. Setting and updating these parameters automatically is the task of a SON mechanism. The following scenarios shall be considered in interference control. 1. Uplink inter cell interference coordination 2. Downlink inter cell interference coordination

Network Elements and Interfaces Involved O&M References- 36.902

3.10

Name of Feature- Self-Establishment of a new


10

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

eNodeB
DescriptionFunctions include Address Allocation Function, OAM Connectivity Establishment Function, Software Management Function, Inventory Update Function, Self-Test Function, SelfConfiguration Monitoring and Management Function, Self-Configuration Monitoring and Management Function, Self-Configuration Monitoring and Management Function, Call Processing Link (CPL) Set Up Function, Radio Network Configuration Data Function, Transport Network Configuration Data Function, NRM IRP Update Function, Radio Network and Transport Network Configuration Data Preparation Function Automatic Radio Configuration Data handling Function(ARCF) handles ARCF Data, ARCF Data Preparation, ARCF Handling, ARCF Data Transfer and ARCF data validation. ARCF data is required for successful activation of cell and eNB, which requires coordination between several cells and cannot be generated below Itf-N. Some of the ARCF data may be used directly as eNodeB configuration data and some of the ARCF data may be used to generate more other eNodeB configuration data. eNodeB will use the ARCF data together with other configuration data as initial eNodeB radio configuration data. The eNodeB initial radio configuration data will be used for self-configuration.

Network Elements and Interfaces Involved.

X2- and S1-interfaces shall be set up as part of the self-configuration process. The eNodeB connects to the OAM (sub) system(s) providing support for normal OAM functions after completion of the selfconfiguration process, eNodeB need to configure Radio configuration and Transport configuration data.

References- 32.501

11

Self-Organizing Networks and Self-Governing Networks


Ajay(RF Consultant) ajaykkaushik@gmail.com

2011

Thank You
Please send queries to ajaykkaushik@gmail.com

12

Das könnte Ihnen auch gefallen