SlideShare a Scribd company logo

3 gpp ts 32.522 self-organizing networks (son) policy network resource model (nrm)

Download as DOCX, PDF
T
Telecom Consultant

This document defines specifications for self-organizing network (SON) policy and optimization functions. It describes several SON functions including load balancing optimization, handover parameter optimization, interference control, capacity and coverage optimization, and random access channel optimization. For each function, it defines objectives, parameters to optimize, optimization methods, architecture, and performance monitoring considerations. It also covers coordination between different SON functions and between SON functions and non-SON network management operations.

EducationTechnologyBusiness
1 of 57
Downloaded 14 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
3GPP TS 32.522 V11.6.1(2013-06) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) (Release 11) The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPPOrganizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPPonly. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 11 2 3GPP TS 32.522 V11.6.1(2013-06) Keywords SON, Self-Optimization, management 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org 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. © 2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association 3GPP
Release 11 3 3GPP TS 32.522 V11.6.1(2013-06) Contents Foreword............................................................................................................................................................. 6 Introduction ........................................................................................................................................................ 6 1 Scope ........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7 3 Definitions and abbreviations................................................................................................................... 8 3.1 3.2 4 Definitions ......................................................................................................................................................... 8 Abbreviations ..................................................................................................................................................... 8 SON Policy and Optimization Function Definitions ................................................................................ 9 4.1 Monitoring and Management Operations for Self-Optimization ....................................................................... 9 4.1.1 Monitoring and Management Function ........................................................................................................ 9 4.1.1.1 Usage of Itf-N ......................................................................................................................................... 9 4.2 Load Balancing Optimization Function ............................................................................................................. 9 4.2.1 Objective and Targets................................................................................................................................... 9 4.2.2 Parameters To Be Optimized ..................................................................................................................... 10 4.2.3 Optimization Method ................................................................................................................................. 10 4.2.3.1 Problem Detection ................................................................................................................................ 10 4.2.3.2 Problem Solution .................................................................................................................................. 11 4.2.4 Architecture ................................................................................................................................................ 11 4.2.4.1 Definition of Logical Functions............................................................................................................ 11 4.2.4.2 Location of Logical Functions .............................................................................................................. 11 4.2.5 PM .............................................................................................................................................................. 11 4.3 Handover (HO) Parameter Optimization Function .......................................................................................... 12 4.3.1 Objective and Targets................................................................................................................................. 12 4.3.2 Parameters To Be Optimized ..................................................................................................................... 12 4.3.3 Optimization Method ................................................................................................................................. 13 4.3.3.1 Problem Detection ................................................................................................................................ 13 4.3.3.2 Problem Solution .................................................................................................................................. 13 4.3.4 Architecture ................................................................................................................................................ 13 4.3.4.1 Definition of Logical Functions............................................................................................................ 13 4.3.4.2 Location of Logical Functions .............................................................................................................. 14 4.3.5 PM .............................................................................................................................................................. 14 4.4 Interference Control Function .......................................................................................................................... 15 4.5 Capacity and Coverage Optimization Function ............................................................................................... 15 4.5.1 Objective and Targets................................................................................................................................. 15 4.5.2 Parameters to be optimized ........................................................................................................................ 15 4.5.3 Optimization Method ................................................................................................................................. 15 4.5.3.1 ProblemDetection ................................................................................................................................. 15 4.5.3.2 Problem Solution .................................................................................................................................. 16 4.5.4 Architecture ................................................................................................................................................ 16 4.5.4.1 Definition of Logical Functions............................................................................................................ 16 4.5.4.2 Location of Logical Functions .............................................................................................................. 16 4.6 RACH Optimization Function ......................................................................................................................... 17 4.6.1 Objective and Targets................................................................................................................................. 17 4.6.2 Parameters to be optimized ........................................................................................................................ 18 4.6.3 Optimization Method ................................................................................................................................. 18 4.6.3.1 ProblemDetection ................................................................................................................................. 18 4.6.3.2 Problem Solution .................................................................................................................................. 18 4.6.4 PM .............................................................................................................................................................. 18 4.7 SON coordination ............................................................................................................................................ 18 4.7.1 Introduction ................................................................................................................................................ 18 4.7.2 Coordination between SON functions below Itf-N and non-SON CM operations over itf-N .................... 19 4.7.2.1 Description ............................................................................................................................................................ 19 4.7.2.2 Prevention ............................................................................................................................................................. 20 4.7.2.3 Resolution ............................................................................................................................................................. 20 4.7.3 Coordination between different SON functions ......................................................................................... 20 3GPP
Release 11 4.7.3.1 4.7.3.1.1 4.7.3.1.2 4.7.3.1.3 4.7.3.2 4.7.3.2.1 4.7.3.2.2 4.7.3.2.3 4.7.3.3 4.7.3.3.1 4.7.3.3.2 4.7.3.3.3 4.7.3.4 4.7.3.4.1 4.7.3.4.2 4.7.3.4.3 4.7.4 4.7.4.1 4.7.4.2 4.7.4.3 5 5.1 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 5.3.3.4 5.3.4 5.3.4.1 5.3.4.2 5.3.4.3 5.3.4.4 5.3.5 5.3.6 5.3.6.1 5.3.6.2 5.3.6.3 5.3.6.4 5.3.7 5.3.7.1 5.3.7.2 5.3.7.3 5.3.7.4 5.3.8 5.3.8.1 5.3.8.2 4 3GPP TS 32.522 V11.6.1(2013-06) Coordination between Cell Outage Compensation and Energy Saving Management .......................... 20 Description ...................................................................................................................................... 20 Prevention ....................................................................................................................................... 20 Resolution ....................................................................................................................................... 20 Coordinationamong Cell Outage Compensation,Capacity and Coverage Optimization, and Energy Saving Management ................................................................................................................. 21 Description ...................................................................................................................................... 21 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 22 Coordination between Cell Outage Compensation and Automatic NeighbourRelation ....................... 22 Description ...................................................................................................................................... 22 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 22 Coordination between HandOver parameter Optimization and Load Balancing Optimization............ 22 Description ...................................................................................................................................... 22 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 23 General SON coordination solutions .......................................................................................................... 23 Overview .............................................................................................................................................. 23 Conflict prevention ............................................................................................................................... 24 Conflict resolution ................................................................................................................................ 25 Information Object Classes (IOCs) ........................................................................................................ 26 Information entities imported and local labels ................................................................................................. 26 Class diagram................................................................................................................................................... 26 Attributes and relationships ........................................................................................................................ 26 Inheritance .................................................................................................................................................. 34 Information Object Class (IOC) definitions ..................................................................................................... 36 SONTargets ................................................................................................................................................ 36 Definition.............................................................................................................................................. 36 Attributes .............................................................................................................................................. 36 Attribute constraints ............................................................................................................................. 37 Notifications ......................................................................................................................................... 37 SONControl................................................................................................................................................ 37 Definition.............................................................................................................................................. 37 Attributes .............................................................................................................................................. 37 Attribute constraints ............................................................................................................................. 37 Notifications ......................................................................................................................................... 37 ESPolicies .................................................................................................................................................. 37 Definition.............................................................................................................................................. 37 Attributes .............................................................................................................................................. 37 Attribute constraints ............................................................................................................................. 38 Notifications ......................................................................................................................................... 38 EUtranCellSON.......................................................................................................................................... 38 Definition.............................................................................................................................................. 38 Attributes .............................................................................................................................................. 38 Attribute constraints ............................................................................................................................. 38 Notifications ....................................................................................................................................... 38 Void ............................................................................................................................................................ 38 EnergySavingProperties ............................................................................................................................. 38 Definition.............................................................................................................................................. 38 Attributes ............................................................................................................................................ 39 Attribute constraints ............................................................................................................................. 39 Notifications ......................................................................................................................................... 39 interRatEsPolicies ...................................................................................................................................... 39 Definition.............................................................................................................................................. 39 Attributes .............................................................................................................................................. 39 Attribute constraints ............................................................................................................................. 39 Notifications ....................................................................................................................................... 39 IOC SONFuncInfo ..................................................................................................................................... 39 Definition.............................................................................................................................................. 39 Attributes .............................................................................................................................................. 40 3GPP
Release 11 5.3.8.3 5.3.8.4 5.3.9 5.3.9.1 5.3.9.2 5.3.9.3 5.3.9.4 5.4 5.5 5.5.1 5.5.2 5.6 5.6.1 5 3GPP TS 32.522 V11.6.1(2013-06) Attribute constraints ............................................................................................................................. 40 Notifications ......................................................................................................................................... 40 IOC SONCoordinationPolicies .................................................................................................................. 40 Definition.............................................................................................................................................. 40 Attributes .............................................................................................................................................. 41 Attribute constraints ............................................................................................................................. 41 Notifications ......................................................................................................................................... 41 Information relationship definitions................................................................................................................. 41 Information attribute definitions ...................................................................................................................... 42 Definition and legal values ......................................................................................................................... 42 Constraints ................................................................................................................................................. 50 Common Notifications ..................................................................................................................................... 50 Configuration notifications ........................................................................................................................ 50 Annex A (informative): Target Achievement Evaluation ................................................................... 51 Annex B (informative): Examples of how to use general SON coordination solutions .................... 52 B.1 Coordination of COC and CCO using priority of SON functions.......................................................... 52 B.2 Coordination of COC, CCO and ES using priority of SON functions ................................................... 52 B.3 Coordination of COC, CCO and ES based on the cell state................................................................... 53 Annex C (informative): State diagram for Distributed and EM-centralized Energy Saving Management ................................................................................................... 53 Annex D(informative): Change history ............................................................................................... 57 3GPP
Release 11 6 3GPP TS 32.522 V11.6.1(2013-06) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below: 32.521: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements 32.522: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) 32.526: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP):Solution Set (SS) definitions 3GPP
Release 11 1 7 3GPP TS 32.522 V11.6.1(2013-06) Scope The present document is part of an Integration Reference Point (IRP) named Self Organizing Networks (SON) Policy Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning SON policies. The SON policy NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s). The present document specifies the protocol neutral SON policy NRM IRP: Information Service (IS). In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [11]). However, which Interface IRP is applicable is outside the scope of the present document. The present document also contains stage 2 descriptions for those functionalities for the Self-Optimization OAM, SON coordination and Energy Saving Management. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements". [2] 3GPP TS 32.102: "Telecommunication management; Architecture". [3] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions". [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [5] 3GPP TS 32.521: "Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements". [6] 3GPP TS 36.331: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification". [7] 3GPP TS 36.423: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access Network (E-UTRAN);X2 Application Protocol (X2AP)". [8] 3GPP TS 32.425: "Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Performance measurements; Evolved Universal Terrestrial Radio Access Network (E-UTRAN)" [9] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)" [10] 3GPP TS 32.762: "Telecommunication management; Configuration Management (CM); Evolved Universal Terrestrial Radio Access Network (E-UTRAN) network resources Integration Reference Point (IRP): Network Resource Model (NRM)" [11] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Information Service (IS)". [12] 3GPP TS 36.413: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". 3GPP
Release 11 8 3GPP TS 32.522 V11.6.1(2013-06) [13] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 Measurements". [14] 3GPP TS 36.300:"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description;Stage 2". [15] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);Overall description; Stage 2". [16] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". [17] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". [18] 3GPP TS 48.008: "Mobile Switching Centre-Base Station System (MSC-BSS) interface; Layer 3 specification". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 32.101 [1], TS 32.102 [2], TS 32.150 [3] and TR 21.905 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 32.521 [5], TS 32.101 [1], TS 32.102 [2] and TR 21.905 [4], in that order. Target: See 3GPPTS32.521 [5]. Trigger condition:See 3GPPTS32.521 [5]. Hand-Over parameter Optimisation: See clause 4.3 of this document and Mobility Robustness Optimisation (MRO) are synonyms (see TS 36.300 [14]). 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [4], TS 32.521 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [4] and TS 32.521 [5]. CAC CCO CDF COC EM eNodeB, eNB ESM E-UTRAN HO HOO ICIC IOC LB LBO MRO NM NRM OAM RO SON UE Composite Available Capacity Capacity and Coverage Optimization Cumulative Distribution Function Cell Outage Compensation Element Manager evolved NodeB Energy Saving Management Evolved Universal Terrestrial Radio Access Network Handover HandOver parameter Optimization Inter Cell Interference Coordination Information Object Class Load Balancing Load Balancing Optimization Mobility Robustness Optimisation Network Manager Network Resource Model Operation Administration Maintenance RACH Optimization Self Organizing Networks User Equipment 3GPP
Release 11 9 3GPP TS 32.522 V11.6.1(2013-06) 4 SON Policy and Optimization Function Definitions 4.1 Monitoring and Management Operations for SelfOptimization 4.1.1 Monitoring and Management Function 4.1.1.1 Usage of Itf-N For specifically defined Itf-N NRM Interface see clause 5. 4.2 Load Balancing Optimization Function 4.2.1 Objective and Targets The objective of LB Optimization is to cope with undesired traffic load distribution and to minimize the number of handovers and redirections needed to achieve the load balancing. One of the following targets or the combination of the following targets shall be used. The specific target value or values shall be configured by operators. Operators should assign weights for targets being used. Targets drawn from the following table can be configured for LBO: Target Name RRC connection establishmentsfailure rate related to load Definition The number of Failed RRC connection establishments related to load/ The total number of Attempted RRC connection establishments. E-RAB setup failure raterelated to load The target is met if the actual rate is smaller than the target value. The number ofE-RABsetup failure related to load/ The total number of attempted E-RABsetup Legal Values Integer [0..100] in unit percentage Integer [0..100] in unit percentage For E-RAB setup failure related to load, the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 [12] could be used. RRCConnectionAbn ormalReleaseRateR elatedtoLoad ERABAbnormalReleas eRateRelatedtoLoad The target is met if the actual rate is smaller than the target value. The number of abnormal RRC connection release related to load/ The total number of RRC connection release. The target is met if the actual rate is smaller than the target value. The number ofE-RABabnormal release related to load/ The total number of E-RABrelease Integer [0..100] in unit percentage Integer [0..100] in unit percentage For E-RAB setup failure related to load, the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 [12] could be used. Rate of failures related to handover The target is met if the actual rate is smaller than the target value. (the number of failure events related to handover) / (the total number of handover events) Integer [0..100] in unit percentage The target is met if the actual rate is smaller than the target value. For the following targets out of the above table, the target values depend on the composite available capacity range in the cell and are defined separately for uplink and downlink. For these tuples can be configured, indicating the capacity ranges together with the target value valid in that range. 3GPP
Release 11 10 3GPP TS 32.522 V11.6.1(2013-06) RRC connection establishments failure rate related to load, E-RAB setup failure rate related to load, RRC Connection Abnormal Release Rate Related to Load, E-RAB Abnormal Release Rate Related to Load For the following targets shall be identical with the corresponding targets defined in Handover Optimization. Rate of failures related to handover 4.2.2 Parameters To Be Optimized To reach load optimization target, LBO may optimize some mobility settings (HO and/or idle mobility configuration) defined in TS 36.331 [6]. 4.2.3 Optimization Method 4.2.3.1 Problem Detection The problem detection is out of scope of this specification. 4.2.3.2 Problem Solution The problem solution is out of scope of this specification. 4.2.4 4.2.4.1 Architecture Definition of Logical Functions LB Monitor Function: This function is used for monitoring the load balance optimization (e.g. Monitoring related performance counters or alarms). LB Policy control function: This function is used for configuring the load balance optimization policies. 3GPP
Release 11 11 4.2.4.2 3GPP TS 32.522 V11.6.1(2013-06) Location of Logical Functions NM(IRPManager) LB Policy Control Function LB Monitor Function Itf-N DM LB Policy Control Function LB Monitor Function EM eNB LB decision algorithm X2 eNB X2 LB decision algorithm eNB EM LB decision algorithm For Load Balancing, the SON LB decision algorithm is located in eNB. The detailed SON functionalities in eNB are out of scope of this specification. 4.2.5 PM IRPManager may collect Load balancing related performance measurements. Performance Measurements related with Load balancing are captured in the table below: 3GPP
Release 11 12 Performance measurement name The number of Failed RRC connection establishments related to load The total number of Attempted RRC connection establishments 3GPP TS 32.522 V11.6.1(2013-06) Description Relatedtargets Refer to 3GPP TS 32.425 [8] Failed RRC connection establishments Refer to 3GPP TS 32.425 [8] Attempted RRC connection establishments RRCconnection establishments failure rate related to load RRCconnection establishments failure rate related to load The number of E-RAB setup failure related to load Refer to 3GPP TS 32.425 [8] Number of initial SAE Bearers failed to setup E-RAB setup related to load failure rate The total number of attempted ERAB setup Refer to 3GPP TS 32.425 [8] Number of initial SAE Bearers attempted to setup Number of UE CONTEXT Release Request initiated by eNodeB E-RAB setup related to load failure rate Number of Successful Context Release RRC Connection Abnormal Release Rate Related to Load E-RAB Abnormal Release Rate Related to Load The number of abnormal RRC connection release related to load The total number connection release of RRC The number of E-RAB abnormal release related to load The total number of E-RAB release the number of failure events related to handover the total number of handover events NOTE: UE Refer to 3GPP TS 32.425 [8] Number of SAE Bearers requested to release initiated by eNodeB per cause Refer to 3GPP TS 32.425 [8] Number of SAE Bearers successfully released Refer to 4.3.5 Refer to 4.3.5 RRC Connection Abnormal Release Rate Related to Load E-RAB Abnormal Release Rate Related to Load Rate of failures related to handover Rate of failures related to handover The monitoring of performance measurements will make use of existing PM IRP. 4.3 Handover (HO) Parameter Optimization Function 4.3.1 Objective and Targets For intra-LTE, one of the following targets or the combination of the following targets shall be used. The specific target value shall be configured by operators. Operators should assign weights for targets being used. Target Name Rate of failures related to handover Definition (the number of failure events related to handover) / (the total number of handover events) Legal Values Integer [0..100] in unit percentage The target is met if the actual rate is smaller than the target value. The objective of minimizing the number of unnecessary handovers shall always be pursued in case the other target/s configured by the operator is/are achieved. This objective may not need configuration of a target value. 4.3.2 Parameters To Be Optimized The tables below summarise the handover parameters in TS 36.331 [6]. 3GPP
Release 11 13 Table4.3.2-1. Event A3 A4 A5 Handover parameters that may be optimized for intra-frequency and inter-frequency handovers Summary Neighbour becomes offset better than serving Neighbour becomes better than threshold Serving becomes worse than threshold1 and neighbour becomes better than threshold2 Table4.3.2-2. Event B1 B2 3GPP TS 32.522 V11.6.1(2013-06) Tunable parameters Ofn, Ofs, Ocn, Ocs, Hys, Off, timeToTrigger Ofn, Ocn, Hys, Thresh, Off, timeToTrigger Ofn, Ocn, Hys, Thresh1, Thresh2, timeToTrigger Off, Handover parameters that may be optimised for inter RAT handover Summary Inter RAT Neighbour becomes better than threshold Serving becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2 4.3.3 Ofn, Hys, Thresh1, Thresh2, timeToTrigger Optimization Method 4.3.3.1 Tunable parameters Ofn, Hys, Thresh, timeToTrigger Problem Detection HO Parameter Optimization Function shall focus on detecting the problem scenarios described in TS 32.521 [5]; namely: too early handovers, too late handovers and inefficient use of NW resources due to HOs. For more information about these scenarios see TS 32.521 [5] section 6.1.3. The following inputs may be used for the identification of the problem scenarios: - Event capture and analysis - UE measurements - Performance measurements In event capture and analysis, the eNodeB exploits event information associated with a UE context, such as evidence of previous handovers (UE History, see TS 36.423 [7]) and HO failure details (such as in which cell the handover failed and where the UE re-established the connection). UE measurements are sent within UE measurement reports and they may indicate whether HOs are too early or too late. HO-related performance measurements (PMs) collected at the source and / or target eNB can be useful in detecting HOrelated issues on the cell level. Since the impact of incorrect HO parameter setting will also be on the cell-level, PMs can provide useful information that can be used to detect and resolve HO-related issues due to incorrect parameter settings. 4.3.3.2 Problem Solution HO Parameter Optimization Function will aim at optimizing the HO parameters listed in Section 4.3.2 in such way to mitigate the problem scenarios discussed in Section 4.3.3.1. The optimization algorithms will not be specified. The exact set of HO parameters that may be adjusted by the algorithms is dictated by the choice of triggered HO measurements made by the RRM entity in an eNodeB. 4.3.4 4.3.4.1 Architecture Definition of Logical Functions HO Parameter Optimization Monitor Function: This function is used for monitoring the handover parameter optimization (e.g. monitoring related performance counters or alarms). HO Parameter Optimization Policy Control Function: This function is used for configuring the handoverparameter optimization policies. 3GPP
Release 11 4.3.4.2 14 3GPP TS 32.522 V11.6.1(2013-06) Location of Logical Functions For HandOver (HO) parameter optimization there are several options for the location of the SON algorithm: 1. The SON algorithm is located in the eNB(s). 2. The SON algorithm is located in the EM, the parameter changes are executed in the eNBs. An example for the first option is shown in figure 4.3.4.2: NM HO Parameter Optimization Policy Control Function HO Parameter Optimization Monitor Function Itf-N DM HO Parameter Optimization Policy Control Function HO Parameter Optimization Monitor Function EM eNB eNB X2 HO Parameter Optimization algorithm HO Parameter Optimization algorithm eNB X2 EM HO Parameter Optimization algorithm Figure 4.3.4.2: Example when the SON algorithm is located in the eNB(s) The detailed SON functionalities in eNB are out of scope of this specification. 4.3.5 PM IRPManager shall collect HO-related performance measurements from the source and / or target eNB which can be useful in detecting HO-related issues on the cell level.The following input can be used for the identification of the problem scenarios specified: The number of RLF event happened within an interval after handover success. The number of unnecessary handovers to another RAT without RLF. Performance Measurements related to handover failure are captured in the table below. The Performance Measurements are for outgoing handovers. Further, they should be available on a cell relation basis. 3GPP
Release 11 15 Performance measurement name Number of handover events Description Number of HO failures Includes successful handovers plus all identified failures All failure cases Number of too early HO failures Too early HO failure cases Number of too late HO failures Too late HO failure cases Number of HO failures to wrong cell Number of unnecessary HOs to another RAT HO failuresto wrong cell NOTE: 3GPP TS 32.522 V11.6.1(2013-06) Related targets Rate of failures handover Rate of failures handover Rate of failures handover Rate of failures handover Rate of failures handover related to related to related to related to related to Unnecessary HOs to each of different RATs The monitoring of performance measurements will make use of existing PM IRP. 4.4 Interference Control Function 4.5 Capacity and Coverage Optimization Function 4.5.1 Objective and Targets The objective of capacity and coverage optimization is to provide optimal coverage and capacity for the radio network. A tradeoff between capacity and coverage needs to be considered. The detailed target(s) FFS. 4.5.2 Parameters to be optimized To reach capacity and coverage optimization targets, the following parameters may be optimized: Downlink transmit power Antenna tilt Antenna azimuth 4.5.3 Optimization Method 4.5.3.1 ProblemDetection The main symptoms ofcapacity and coverage optimizationproblems (see TS 37.320 [15]) are: Coverage hole: A coverage hole is an area where the pilot signal strength is below a threshold which is required by a UE to access the network, or the SINRs of both serving and neighbor cells is below a level needed to maintain the basic service.Coverage holes are usually caused by physical obstructions such as new buildings, hills, or by unsuitable antenna parameters, or just inadequate RF planning. UE in coverage hole will suffer from call drop and radio link failure. Typical phenomenon of coverage hole is either HO failure happens frequently and cannot be optimized by HO parameter optimization or call drop happens frequently and cannot be rescued by RRC re-establishment. Weak coverage: Weak coverage occurs when the pilot signal strength or the SNR (or SINR) of serving cell is below the level needed to maintain a planned performance requirement (e.g. cell edge bit-rate). Pilot pollution: In areas where coverage of different cells overlap a lot, interference levels are high, power levels are high, energy consumption is high and cell performance may be low. Typically in this situation UEs may experience high SNR to more than one cell and high interference levels. Overshoot coverage: Overshoot occurs when coverage of a cell reaches far beyond what is planned. It can occur as an “island” of coverage in the interior of another cell, which may not be a direct neighbor. Reasons for overshoot may be reflections in buildings or across open water, lakes etc. UEs in this area may suffer call drops or high interference. 3GPP
Release 11 16 3GPP TS 32.522 V11.6.1(2013-06) DL and UL channel coverage mismatch:DL channel coverage is larger than UL channel coverage is one typical scenario of DL and UL channel coverage mismatch. The UE will suffer UL problems when it moves into the mismatch area. In a realistic network, these symptoms may be tolerated to a certain level. These symptoms may indicate a real problem when combined with other factors such as frequency of symptoms, duration of symptoms, or affected population. The following inputs may be used for the identification of the problem scenarios: UE measurements Performance measurements Alarms, other monitoring information e.g. trace data UE measurements are sent within UE measurement reports and they may indicate the capacity and coverage problem. Capacity and coverage related performance measurements collected at the source and / or target eNB can be useful in detecting capacity and coverage related issues on the cell level. Minimizing Driver Test (MDT) or HO-related performance measurements may be usedalso in detecting capacity and coverage related issues on the cell level. Alarms, othermonitoring information e.g. trace data can be correlated to get an unambiguous indication of capacity and coverage problem. 4.5.3.2 Problem Solution Capacity and coverageoptimization function will aim at optimizing the parameters listed in Section 4.5.2 in such way to mitigate the problem scenarios discussed in Section 4.5.3.1. 4.5.4 Architecture 4.5.4.1 Definition of Logical Functions CCO Monitor Function: This function is used for monitoring the capacity and coverage optimization (e.g. monitoring related performance counters, UE measurements or alarms). CCO Policy Control Function: This function is used for configuring the capacity and coverageoptimization policies. 4.5.4.2 Location of Logical Functions For capacity and coverage optimization (CCO), there are several options for the location of the centralized CCO SON algorithm: 1. The CCO SON algorithm is located in the DM. The capacity and coverage optimization decision is made by the DM centralized CCO algorithm. 2. The CCO SON algorithm is located in the NM.The capacity and coverage optimization decision is made by the NM centralized CCO algorithm. An example for the first option is shown in figure 4.5.4.2: 3GPP
Release 11 17 3GPP TS 32.522 V11.6.1(2013-06) NM CCO Policy Control Function CCO Monitor Function Itf-N DM CCO Policy Control Function CCO Monitor Function CCO Algorithm EM eNB X2 X2 eNB eNB EM Figure 4.5.4.2: Example when the CCO SON algorithm is located in DM The detailed CCO SON algorithm in OAM (NM centralized or EM centralized) is out of scope of this specification. 4.5.5 PM The IRPAgent shall support a capability allowing the IRPManagerto collect CCO related performance measurements to know the situation of coverage or interference which may then trigger corresponding optimization procedures. Performance measurements related with CCO are captured in the table below: Performance measurement name Maximum carrier transmit power Mean carrier transmit power Description Comment Refer to 3GPP TS 32.425 [8] Maximum value of the total carrier power transmitted in a cell. Refer to 3GPP TS 32.425 [8] Mean value of the total carrier power transmitted in a cell. 4.6 RACH Optimization Function 4.6.1 Objective and Targets The objective of RACH Optimization is to automatically set several parameters related to the performance of RACH. One of the following targets shall be used. The specific target value shall be configured by operators. 3GPP
Release 11 18 3GPP TS 32.522 V11.6.1(2013-06) Target Name Access Probability, AP Definition The probability that the UE has access after a certain random access attempt number. Legal Values CDF of access attempts. See section 5.5.1 Access Delay Probability,ADP The target is met if the actual access probability is higher than the target probability value. The probability distribution of Access Delay expected to be experienced by UEs accessing the RACH Channel. CDF of delays. See section 5.5.1 The target is met if the actual access probability is higher than the target probability value. 4.6.2 Parameters to be optimized To achieve RACH optimization target, RACH optimization function may optimize several parameters defined in TS 36.300 [14] section 22.4.3. 4.6.3 Optimization Method 4.6.3.1 ProblemDetection The problem detection is out of scope of this specification since theRACH optimization entity resides in the eNB. 4.6.3.2 Problem Solution The problem solution is out of scope of this specification since the RACH optimization entity resides in the eNB. 4.6.4 PM The IRPAgent shall support a capability allowing the IRPManagerto collect RACH optimization related performance measurements. Performance measurements related with RACH optimization are captured in the table below: Performance measurement name Distribution of RACH preambles sent Distribution of RACH access delay 4.7 Refer to 3GPP TS 32.425 [8] Cumulative Distribution of RACH preambles sent by UE Refer to 3GPP TS 32.425 [8] Cumulative Distribution of RACH Access Delay Related targets Access Probability, AP Access Delay Probability, ADP SON coordination 4.7.1 Description Introduction There may be conflicts or dependencies between SON functions; SON coordination means preventing or resolving conflicts or negative influences between SON functions to make SON functions comply with operator’s policy. As the example shown in figure 4.7.1.1, there is mesh relationship between SON functions and network parameters (or network elements) in which conflicts or negative influences may happen if no SON coordination. 3GPP
Release 11 19 SON functions Network parameters and/or elements CCO Antenna Para (Tilt, Azimuth) COC 3GPP TS 32.522 V11.6.1(2013-06) ES Cell switch on/off HOO Downlink TX Power LBO Handover Parameters Legend: RF related RRM related Figure 4.7.1.1: Mesh relationshipbetween SON functions and network parameters (or network elements) 4.7.2 Coordination between SON functions below Itf-N and non-SON CM operations over itf-N 4.7.2.1 Description Conflict may arise between non-SON CM operation via Itf-N and the SON functions (in particularly self-optimization function) below Itf-N in the following scenario. The network parameters can be changed by the non-SON CM operations via Itf-N,meanwhile, the SON functions below Itf-N may also require changing the parameters. If these parametersare some (same or associated) parameters of some (same or associated) nodes which will be changed by the non-SON CM operations and the SON functions below Itf-N, conflict arises. (Conflict see clause 4 of 32.521[5]) For example, the non-SONCM operation via Itf-N may try to reduce the CIO (cell individual offset) parameter, it makes the HO trigger between cells (e.g., HO from cell A to cell B) become more difficult. But in the meanwhile, the SON function MRO may try to increase the CIO parameter, it makes the HO easier. In this case, if the conflict is not coordinated, the parameter may be modified twice. Then the failed rate related with handover may rise or ping-pong handover may arise between the two cells. In case the SON function below Itf-N and non-SON CM operation via Itf-N has conflict, the SON function below Itf-N shall take into account and re-evaluate, if applicable, any non-SON CM operation changes via Itf-N. As showing in the following example, At Time T3, after Non-SON operation has finished the modification, SON function below Itf-N shall take the non-SON CM operation changes into account for further SON analysis. 3GPP
Release 11 20 3GPP TS 32.522 V11.6.1(2013-06) NonSON operati on over Itf-N T2 Modify (same or associated) parameters of (same or T1 Modify associated) nodes SON functions below ItfN T3 Reanalysis Time SON functions below ItfN 4.7.2.2 Prevention In a real network, it is possible that non-SON CM operations via Itf-N and several SON functions below Itf-N are running at the same time, and they may try to change the same or associated parameters during a short time period. So coordination is needed to prevent this kind of conflicts. 4.7.2.3 Resolution Refer to common coordination solutions part. 4.7.3 Coordination between different SON functions Note: The coordination between different SON functions should be decided case by case. 4.7.3.1 4.7.3.1.1 Coordination between Cell Outage Compensation and Energy Saving Management Description A conflict could arise between energy saving and cell outage compensation in the following scenario. One or more candidate cells are configured to possibly take coverage of the original cell. The original cell is in energySaving state or is about to enter energySaving state. One or more candidate cells go into outage with the consequence that coverage of the original cell cannot be provided any more. 4.7.3.1.2 Prevention Prevention is hardly possible, except making the cells as outage proof as possible. But cell outages can happen even to the most stable cell in a network. 4.7.3.1.3 Resolution If the original cell is in energySaving state, it shall leave energySaving state. If the original cell is about to enter energySaving state, it shall not go into energySaving state until candidate cell outage is recovered and candidate cell is able to provide the coverage. The original cellmaygo into the energySaving state after the candidate cell outage is recovered and coverage of the original cell can be taken over by candidate cell again. 3GPP
Release 11 4.7.3.2 4.7.3.2.1 21 3GPP TS 32.522 V11.6.1(2013-06) Coordinationamong Cell Outage Compensation,Capacity and Coverage Optimization, and Energy Saving Management Description Capacity and Coverage Optimization (CCO), Cell Outage Compensation (COC) and Energy Saving Management (ESM) may require changes to the coverage and/or capacity ofone or more cells during the same time period, which couldlead to the following issue: Cell3 Cell1 Cell2 Cell4 Figure 4.7.3.2 Coordination among COC, CCO, and ESM Figure 4.7.3.2 is a typical scenario for the coordination among COC, CCO and ESM. Cell 1 is detected in outage, COC will try to compensate the outage Cell 1 by reconfiguring the RF configuration of some compensation candidate cells, e.g., TX power, antenna tilt and antenna azimuth of Cell 2 and Cell 3. Before the outage Cell 1 is compensated, CCO may detect the degrading of coverage related KPI (e.g., success rate of RRC connection establishments, cell throughput) of Cell 1 and its neighbour cells (Cell 2 and other blue cells) and make a conclusion that there is a coverage problem in this KPI degraded area. Meanwhile, ESM is operating on Cell 2 to compensate the coverage of its neighboring cell (Cell 4) which is going into energySaving state. From the time point at which the outage Cell 1 is detected until Cell 1 has been compensated by Cell 2 and Cell 3, during this period, if there is no coordination among COC, CCO and ESM, there will be possibly different settings for adjusting TX power, antenna tilt and antenna azimuth of Cell 2 for COC, CCO or ESM purposes respectively.It’s most likely that the adjustment from COC, ESM and optimization from CCO may conflict in the common affected outage compensation candidate cell(s) (Cell 2 in the above example). It is also possible that ESM is operating on Cell 2 to compensate the coverage of Cell 4 that is in energySaving state, while COC detects that Cell 1 has outage, and requests Cell 2 to compensate the coverage of Cell 1. COC and ESM need to be coordinated to determine if this request can be accepted. After the outage cell comes back to normal, the COC exits the coordination scenario, while CCO and ESM continute to work and need to be well coordinated. For example, CCO may adjust the antenna tilt of Cell 2 in a downward direction to improve the coverage signal quality, but ESM may adjust the antenna tilt of Cell 2 in an opposite direction to enlarge its coverage area for purpose of ES compensation. Therefore, coordination should be continued between CCO and ESM to resolve the possible configuration conflict on Cell 2. Other conflict scenarios could be: Cell A is compensating to provide coverage for Cell B that is in energySaving state. COC detects that Cell A has outage. Since Cell A is not able to provide the coverage for Cell B any more, Cell B needs to be covered by another cell, or to deactivate energy saving. Cell A is in energySaving state. COC detects Cell B has outage, and requests Cell A to compensate the coverage of Cell B. Cell A may need to terminate energy saving in order to compensate the coverage of Cell B. 3GPP
Release 11 22 3GPP TS 32.522 V11.6.1(2013-06) Cell A which is compensating Cell B in outage shall not go into energySaving state as long as its compensation for Cell B is needed. 4.7.3.2.2 Prevention Prevention is hardly possible. 4.7.3.2.3 Resolution Refer to clause 4.7.4 General SON coordination solutions. 4.7.3.3 4.7.3.3.1 Coordination between Cell Outage Compensation and Automatic NeighbourRelation Description In case one cell is detected in outage, COC will try to compensate the outage cell by reconfiguring the RF configuration of some compensation candidate cells. As a result of this, there will be new NRs (neighbour relations) which reflect the new topology relations. For a stable network, ANR could be deactivated for the purpose of system resource saving. If ANR is deactivated, the new NRs cannot be captured in NRT by ANR. Network performance, for example, handover will be impacted negatively by the NRT which lacks of the new NRs. 4.7.3.3.2 Prevention Prevention is hardly possible, except making the cells as outage proof as possible. But cell outages can happen even to the most stable cell in a network. 4.7.3.3.3 Resolution The ANR function should monitor if a cell outage or cell outage compensation takes place within its area. If this happens, then the ANR function should check the NRs of the affected cells (for example the outage cell and its neighbours and neighbours’ neighbours). In case the ANR function in the the affected areais deactivated, the possible NRs change of the affected cellsshould be taken as a factor toreactivate the ANR function. 4.7.3.4 4.7.3.4.1 Coordination between HandOver parameter Optimization and Load Balancing Optimization Description HOO function and LBO function both optimize network performance by adjusting handover parameters such as CIO, Hysteresis, TTT, etc. Conflicts may happen when HOO function and LBOfunction are changing the same or associated handover parameters in opposite direction or towards the same direction but on different scales. For example, HOO function may adjust handover parameters (e.g. decrease CIO of source cell A to target cell B) to minimize the number of too early handovers from cell A to cell B whilst LBO function may adjust handover parameters (e.g. increase the CIO of source cell A to target cell B) to make the handover from cell A to cell B more easier in case the load of cell B is much less than cell A. 4.7.3.4.2 Prevention Prevention is hardly possible unless switch off HOO function or LBO function. However, disabling the complete HOO function or LBO function cannot fulfil the requirement that both handover performance and load performance need to be improved at the same time. 4.7.3.4.3 Resolution For the coordination between HOO and LBO, IRPManager should assign priorities for HOO function and LBO function or weights for targets of HOO function and LBO function according to operator’s policy. The policy should cover different scenarios well: 3GPP
Release 11 23 3GPP TS 32.522 V11.6.1(2013-06) Policy may assign higher priority for HOO function than LBO function or higher weight for target of HOO function than targets of LBO function when resolving MRO issues (HO too early/too late/to wrong cell) is the main objective of network optimization, e.g. in handover optimization scenario for better coverage. Policy may assign lower priority for HOO function than LBO function or lower weight for target of HOO function than targets of LBO function when enhancing load performance is the main objective of network optimization, e.g. in load optimization scenario for better capacity. Concrete way of using priority or weights of targets, refers to clause 4.7.4 General SON coordination solutions. 4.7.4 4.7.4.1 General SON coordination solutions Overview As described in TS 32.521 [5], multiple SON functions may have conflicting demands on network resources. This situation is considered as “SON functions in conflict” and requires conflict prevention or resolution. A SON Coordination Function will be responsible for preventing or resolving conflicts. Conflict needs to be detected when there is “SON functions in conflict”. Policies can be preset by operator to SON Coordination Function to avoid conflict on certain associated resources (network elements and/or parameters) among SON functions. Conflict prevention is to take some advanced methods to prevent the occurrence of conflict. However, no matter what implementation is chosen, it is impossible to guarantee that 100% of conflicts will be prevented, so conflict detection and resolution are needed. Conflict detection should be taken firstly as the pre-condition of conflict resolution. The SON Coordination Function is a logical function, which means it can be implemented as a separate function entity or as part of SON function. When the SON Coordination Function is implemented as a separate function entity, all the SON functions send the necessary information to the SON Coordination Function, the SON Coordination Function coordinate these SON functions as a centralized control point. This centralized coordination approach fulfills the requirements of SON coordination in a large area scope, for example, the coordination between NM centralized SON functions and distributed SON functions. In some other situations, coordination is only needed in a smaller area, for example, the coordination between distributed SON functions inside one domain. Then the SON Coordination Function can be implemented as part of each SON function. The necessary coordination information can be inter-exchanged between each SON functions to achieve coordination as well. The SON Coordination Function may reside above or below Itf-N. Figure 4.7.4.1 shows an example of a SON Coodination Function, which is a separate function entity, above Itf-N. 3GPP
Release 11 24 NM SON Coordination Function 3GPP TS 32.522 V11.6.1(2013-06) SON_X Itf-N EM SON_Y eNB SON_A eNB SON_B EM eNB SON_C Figure 4.7.4.1: Example of SON Coordination entity located in NM The SON Coordination Function may be responsible for conflict prevention, conflict resolution, or both in parallel. 4.7.4.2 Conflict prevention To prevent conflicts between the SON functions, the SON functions may ask the SON Coordination function for permission before changing some specific configuration parameters. The SON Coordination Function should check the SON coordination interdependancy policy between this requesting SON function and other SON function(s) upon receiving the permission request from the SON function. SON coordination interdependancy policy which is preconfigured can help the SON Coordination Function to find which SON function(s)possibly conflict with this requesting SON function. As a basis for decisions, the SON Coordination Function will typically use one or some of the following inputs received from the SON function(s) Which SON functions are modifying configuration parameters (including information about vendor, release etc.) Configuration parameters intended to be changed and/or their existing and proposed new values The time duration how long the configuration parameter should not be interfered with (“impact time”) The state of SON functions The SON targets which are the justification for the configuration change. Possible impact of a parameter change on other objects (“impact area”) The state of certain managed objects Possible impact of the parameter change on Key Performance Indicators Priority of SON functions, which can be used to determine the execution order of requests from different SON functions in case of conflicts SON coordination policies 3GPP
Release 11 25 3GPP TS 32.522 V11.6.1(2013-06) The SON Coordination Function sends the decision back to the requesting SON function; the decision may be confirmation or suspension or rejection of the SON executing request, or other actions like configuration of specific parameters with specific value. After SON function executes action, the SON Coordination Function is then informed about the result (successful/unsuccessful, parameters changes) of the executed SON action. The SON Coordination Function may prevent parameter changes by one or more SON functions for a specified time period after the same parameter has been changed by another SON function. The SON Coordination Function may inform a SON Function of a managed object state change which may impact calculation of KPIs. Detailed description of how to use general SON coordination solutions are in Annex B. 4.7.4.3 Conflict resolution The SON Coordination Function should detect conflicts and attempt to resolve the conflicts. To detect conflicts, the SON Coordination Function will typically analyse one or some of the following types of data Key Performance Indicatorswhich indicate if SON functions are meeting their targets or improving network performance Measurements which indicate if SON functions are meeting their targets or improving network performance Unacceptable oscillations in configuration parameters To resolve conflicts, the SON Coordination Function will typically use one or some of following methods Enabling/disabling/suspending certain SON functions Stopping/suspending/modifying certain SON actions Modifying certain configuration parameters 3GPP
Release 11 26 3GPP TS 32.522 V11.6.1(2013-06) 5 Information Object Classes (IOCs) 5.1 Information entities imported and local labels Label reference 3GPP TS 32.622 [9], IOC, Top Top Local label 3GPP TS 32.622 [9], IOC, SubNetwork SubNetwork 3GPP TS 32.762 [10], IOC, ENBFunction ENBFunction 3GPP TS 32.762 [10], IOC, EUtranRelation EUtranRelation 3GPP TS 32.762 [10], IOC, EUtranGenericCell EUtranGenericCell 5.2 Class diagram 5.2.1 Attributes and relationships <<names>> <<InformationObjectClass>> SubNetwork 1 <<names>> <<names>> (from TS 32.622) 1 1 <<InformationObjectClass>> SONTargets 0..1 1 <<names>> 0..1 0..* <<InformationObjectClass>> SONControl XOR <<InformationObjectClass>> ManagedElement (from TS 32.622) 1 0..1 <<names>> <<names>> 0..* 1 <<InformationObjectClass>> ENBFunction <<names>> (from TS 32.762) 1 <<InformationObjectClass>> SONTargets 0..1 1 <<names>> 0..* <<InformationObjectClass>> EUtranGenericCell <<names>> (from TS 32.762) 1 <<InformationObjectClass>> SONTargets 0..1 NOTE 1: IOC SONControl shall be instantiated whenever one or more IOC SONTargets are instantiated. Figure 5.2.1-1: Cell view of SON Policy NRM 3GPP
Release 11 27 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> ...>> Subnetwork 1 <<InformationObjectClass>> ...>> ESPolicies <<names>> (f rom TS 32.622) 0..1 1 1 <<names>> 0..* <<InformationObjectClass>> ...>> ManagedElement (f rom TS 32.622) 1 <<names>> 0..* <<InformationObjectClass>> ...>> ENBFunction (f rom TS 32.762) <<InformationObjectClass>> ESPolicies <<names>> 1 0..1 1 <<names>> 0..* <<InformationObjectClass>> ...>> EUtranGenericCell (f rom TS 32.762) <<InformationObjectClass>> ESPolicies <<names>> 1 0..1 Figure 5.2.1-2:ES Policies NRM IOCs (ContainmentRelationship) NOTE 2: Also IOC SONControl is used for intra-LTE ES purposes – see clause 5.3.2.2 – but is not shown in Figure 5.2.1-2 to avoid the impression that there would an additional instance of this IOC be needed for intraLTE ES. <<InformationObjectClass>> EUtranGenericCell (f rom TS 32.762) 1 0..1 <<InformationObjectClass>> EUtranCellSON Figure 5.2.1-3: IOCs to control SON on cell level (Containment Relationship) 3GPP
Release 11 28 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ManagedElement (f rom TS 32.622) 1 <<names>> 0..n <<InformationObjectClass>> ENBFunction <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.762) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> EUtranGenericCell <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.762) 1 0..1 Figure 5.2.1-4: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 1) NOTE 3: Also IOC SONControl is used for inter-RAT ES purposes – see clause 5.3.2.2 – but is not shown in Figure 5.2.1-4 to avoid the impression that there would an additional instance of this IOC be needed for inter-RAT ES. 3GPP
Release 11 29 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork 1 (from TS 32.622) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ExternalENBFunction (from TS 32.762) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ExternalEUtranGenericCell (from TS 32.762) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 Figure 5.2.1-5: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 2) 3GPP
Release 11 30 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ManagedElement (from TS 32.622) 1 <<names>> 0..n <<InformationObjectClass>> RncFunction <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.642) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> UtranGenericCell <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.642) 1 0..1 Figure 5.2.1-6: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 3) NOTE 4: Also IOC SONControl is used for inter-RAT ES purposes – see clause 5.3.2.2 – but is not shown in Figure5.2.1-6 to avoid the impression that there would an additional instance of this IOC be needed for inter-RAT ES. SONControl is contained by Subnetwork or RncFunction when esSwitch attribute is applied in SONControl. 3GPP
Release 11 31 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass> > Subnetwork <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalRncFunction <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.642) 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalUtranGenericCell <<InformationObjectClass> InterRatEsPolicies > <<names>> (from TS 32.642) 1 0..1 Figure 5.2.1-7: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 4) 3GPP
Release 11 32 <<InformationObjectClass>> ManagedElement 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.622) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> BssFunction (from TS 32.652) 1 <<names>> 0..n <<InformationObjectClass>> BtsSiteMgr <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.652) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> GsmCell <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.652) 1 0..1 Figure 5.2.1-8: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 5) 3GPP
Release 11 33 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass> > Subnetwork <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalBssFunction (from TS 32.652) 1 <<names>> 0..n <<InformationObjectClass> ExternalGsmCell > <<InformationObjectClass> InterRatEsPolicies > <<names>> (from TS 32.652) 1 0..1 Figure 5.2.1-9: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 6) 3GPP
Release 11 34 3GPP TS 32.522 V11.6.1(2013-06) Figure 5.2.1-10: IOCs for SON coordination (Containment Relationship) 5.2.2 Inheritance <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> <<InformationObjectClass>> SONTargets SONControl Figure 5.2.2-1: SON Policy NRM Inheritance Hierarchy 3GPP
Release 11 35 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> Top (f rom TS 32.622) <<InformationObjectClass>> ESPolicies <<InformationObjectClass>> InterRatEsPolicies Figure 5.2.2-2:ES PolicesNRM IOCs (Inheritance Relationship) <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> EUtranCellSON Figure 5.2.2-3: Inheritance for IOC to control SON on cell level <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass> > EnergySavingProperties Figure 5.2.2-4: Energy saving propertiesNRM IOCs (Inheritance Relationship) 3GPP
Release 11 36 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> SONFuncInfo <<InformationObjectClass>> SONCoordinationPolicies Figure 5.2.2-5: IOCs for SON coordination (Inheritance Relationship) 5.3 Information Object Class (IOC) definitions 5.3.1 SONTargets 5.3.1.1 Definition This IOC represents targets for SON functions and their relative weights. Target hierarchy rule: An NRM IOC instance X may name-contain an IOC SONTargets instance T. The rule states that: - If X name-contains a SONTargets instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONTargets instance, then no SONTargets instance is applicable to X. - If X does not name-contain any SONTargets instance, but one or more of X’s superior instances name-contain a SONTargets instance, then the SONTargets instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.1.2 Attributes Attribute name hoFailureRate rrcConnectionEstablishmentFailureRateCharacteristic rrcConnectionAbnormalReleaseRateCharacteristic eRabSetupFailureRateCharacteristic eRabAbnormalReleaseRateCharacteristic rachOptAccessProbability rachOptAccessDelayProbability *) Note 1: At least one of the attributes shall be supported. **) Note 2: Only one of these attributes shall be present. 3GPP Support Qualifier O *) O *) O *) O *) O *) CM **) CM **) Read Qualifier M M M M M M M Write Qualifier M M M M M M M
Release 11 5.3.1.3 37 Attribute constraints Name rachOptAccessProbability CM Support Qualifier rachOptAccessDelayProbability CM Support Qualifier 5.3.1.4 3GPP TS 32.522 V11.6.1(2013-06) Definition RACH Optimization is supported and Access Probability is supported as target. RACH Optimization is supported and Access Delay Probability is supported as target. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.2 SONControl 5.3.2.1 Definition This IOC represents the possibility to switch on or off SON functions. This is provided for Handover parameter optimization, Load Balancing optimization, Energy Saving, RACH optimization and Cell Outage Compensation. 5.3.2.2 Attributes Attribute name hooSwitch lboSwitch esSwitch roSwitch cocSwitch 5.3.2.3 Support Qualifier CM CM CM CM CM Write Qualifier M M M M M Attribute constraints Name hooSwitchCM Support Qualifier lboSwitchCM Support Qualifier esSwitch Support Qualifier roSwitch CM Support Qualifier cocSwitch Support Qualifier 5.3.2.4 Read Qualifier M M M M M Definition Handover (HO) parameter Optimization function is supported. Load Balancing Optimization function is supported. The condition is “Distributed or EM-Centralized ESM architecture is supported”. RACH Optimization is supported. The condition is “CoC is supported”. Only allowed to be present, if SONControl is contained in subnetwork IOC instance. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.3 5.3.3.1 ESPolicies Definition This IOC represents the energy saving policies information. This object class is valid in a distributed ES architecture or in an EM-centralized ES architecture. 5.3.3.2 Attributes Attribute name esActivationOriginalCellLoadParameters esActivationCandidateCellsLoadParameters esDeactivationCandidateCellsLoadParameters esNotAllowedTimePeriod 5.3.3.3 Support Qualifier CM CM CM O Attribute constraints 3GPP Read Qualifier M M M M Write Qualifier M M M M
Release 11 38 Name esActivationOriginalCellLoadParameters esActivationCandidateCellsLoadParameters esDeactivationCandidateCellsLoadParameters 5.3.3.4 3GPP TS 32.522 V11.6.1(2013-06) Definition The condition is "Intra-RAT ESM is supported AND the cell acts as an original cell". The condition is "Intra-RAT ESM is supported AND the cell acts as a candidate cell". The condition is "Intra-RAT ESM is supported AND the cell acts as a candidate cell". Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.4 5.3.4.1 EUtranCellSON Definition This IOC represents the parameters for control of SON functions on E-UTRAN cell level. 5.3.4.2 Attributes Attribute name maximumDeviationHoTrigger minimumTimeBetweenHoTriggerChange 5.3.4.3 Read Qualifier M M Write Qualifier M M Attribute constraints Name maximumDeviationHoTrigger Support Qualifier minimumTimeBetweenHoTriggerChange Support Qualifier 5.3.4.4 Support Qualifier CM CM Definition The condition is "HOO function is supported". The condition is "HOO function is supported". Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.5 Void 5.3.6 EnergySavingProperties 5.3.6.1 Definition This IOC represents the energy saving properties of a network element supporting Energy Saving Management functionality. 3GPP
Release 11 5.3.6.2 39 Attributes Attribute name energySavingState energySavingControl isProbingCapable 5.3.6.3 3GPP TS 32.522 V11.6.1(2013-06) Support Qualifier M CM O Read Qualifier M M M Write Qualifier M - Attribute constraints Name energySavingControl CM Support Qualifier Definition The condition is "ESM functionality supports and uses NMCentralized architecture". 5.3.6.4 Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC. Notification notifyAttributeValueChange shall be supported for attribute energySavingState. 5.3.7 5.3.7.1 interRatEsPolicies Definition This IOC represents the inter-RAT energy saving policies information. This object class is valid in a distributed ES architecture or in an EM-centralized ES architecture. 5.3.7.2 Attributes Attribute name interRatEsActivationOriginalCellParameters interRatEsActivationCandidateCellParameters interRatEsDeactivationCandidateCellParameters 5.3.7.3 Read Qualifier M M M Write Qualifier M M M Attribute constraints Name interRatEsActivationOriginalCellParame ters CM Support Qualifier interRatEsActivationCandidateCellParam eters CM Support Qualifier interRatEsDeactivationCandidateCellPar ameters CM Support Qualifier 5.3.7.4 Support Qualifier CM CM CM Definition The condition is "The cell acts as an original cell" AND inter-RAT ESM is supported. The condition is "The cell acts as a candidate cell" AND inter-RAT ESM is supported. The condition is "The cell acts as a candidate cell" AND inter-RAT ESM is supported. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.8 IOC SONFuncInfo 5.3.8.1 Definition This IOC represents information of SON functions, to support SON coordination.In case of SON coordination function is located below Itf-N, this IOC is used together with SONCoordinationPolices IOC for SON coordination purpose. SONFuncInfo hierarchy rule: An NRM IOC instance X may name-contain an IOC SONFuncInfo instance T. The rule states that: - If X name-contains a SONFuncInfo instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONFuncInfo instance, then no SONFuncInfo instance is applicable to X. 3GPP
Release 11 - 40 3GPP TS 32.522 V11.6.1(2013-06) If X does not name-contain any SONFuncInfo instance, but one or more of X’s superior instances name-contain a SONFuncInfo instance, then the SONFuncInfo instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.8.2 Attributes Attribute Name sonFuncCapabilityBelowItfN 5.3.8.3 Support Qualifier M Read Qualifier M Write Qualifier - Attribute constraints None. 5.3.8.4 Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.9 IOC SONCoordinationPolicies 5.3.9.1 Definition This IOC represents the SON coordination policies that are selected by IRPManagers from the IRPAgent supported policies in the case of a separate SON coordination function is located below Itf-N (i.e., EM centralized SON coordination) or SON coordination function is implemented as part of each SON function (i.e., distributed SON coordination). For EM centralized SON coordination case, the case that the SON function is located above Itf-N and the corresponding SON coordination function is below Itf-N is not in the scope of this release. This IOC is not intended to be used by IRPManager to create SON coordination policies that are not supported by IRPAgent. The selected SON coordination policies are used by SON coordination function to coordinate the SON functions with potential conflicts, in case no SON coordination policies are selected by IRPManager, the default SON coordination policies are applied to the SON coordination function below Itf-N; the default SON coordination policies are per agreement between IRPManager and IRPAgent, the value of the default SON coordination policies is out of the scope of this specification. SONCoordinationPolicies hierarchy rule: An NRM IOC instance X may name-contain an IOC SONCoordinationPolicies instance T. The rule states that: - If X name-contains a SONCoordinationPolicies instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONCoordinationPolicies instance, then no SONCoordinationPolicies instance is applicable to X. - If X does not name-contain any SONCoordinationPolicies instance, but one or more of X’s superior instances name-contain a SONCoordinationPolicies instance, then the SONCoordinationPolicies instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.9.2 Attributes Attribute Name selectedSonCoordPolicy sonFuncPriorityOrder 5.3.9.3 Support Qualifier CM CM Read Qualifier M M Write Qualifier M M Attribute constraints Name Definition selectedSonCoordPolicy CM Support Qualifier SON coordination function below Itf-N supports more than one coordination policy. sonFuncPriorityOrder CM Support Qualifier The selectedSonCoordPolicy “BaseOnPriority”. 3GPP equals to
Release 11 5.3.9.4 41 3GPP TS 32.522 V11.6.1(2013-06) Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.4 Information relationship definitions None. 3GPP
Release 11 42 5.5 Information attribute definitions 5.5.1 3GPP TS 32.522 V11.6.1(2013-06) Definition and legal values Table5.5.1.1 defines the attributes that are present in the Information Object Classes (IOCs) of the present document. Table 5.5.1.1: Attributes definitions and legal values Attribute Name cocSwitch energySavingCo ntrol energySavingSt ate Definition This attribute allows the operator to enable/disable the COC functionality. This attribute allows the IRPManager to initiate energy saving activation or deactivation. Its value can not be changed by the IRPAgent. Specifies the status regarding the energy saving in the cell. If the value of energySavingControl is toBeEnergySaving, then it shall be tried to achieve the value isEnergySaving for the energySavingState. If the value of energySavingControl is toBeNotEnergySaving, then it shall be tried to achieve the value isNotEnergySaving for the energySavingState. 3GPP Legal Values Enumerated {on, off} Enumerated {toBeEnergySaving, toBeNotEnergySaving}. Enumerated {isNotEnergySaving, isEnergySaving}.
Release 11 eRabAbnormalRe leaseRateChara cteristic 43 3GPP TS 32.522 V11.6.1(2013-06) The target is on the number of E-RAB abnormal release related to load divided by the total number of attempted E-RABsetups. lowerEndOfCacRange and upperEndOfCacRange: Integer 0..10000 This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:eRabAbnormalReleaseRateCharacteris ticDownlink and eRabAbnormalReleaseRateCharacteristicU plink. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: eRabAbnormalReleaseRateCharacteristicD ownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, eRabAbnormalReleaseRateTarget eRabAbnormalReleaseRateCharacteristicU plink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, eRabAbnormalReleaseRateTarget Remark: Formula for composite available capacity: Available Capacity = Cell Capacity Class Value * Capacity Value For definition of Cell Capacity Class Value and Capacity Value see TS 36.331 [6]. These definitions lead to a value range of a composite available capacity from 0..10000. 36.423 [7] has cell capacity class value as optional parameter in case of intra-LTE load balancing. If cell capacity class value is not present, than 36.423 assumes that bandwidth should be used instead to assess the capacity. eRabAbnormalReleaseRateTarget: Integer 0..100 (representing a percentage) This target is suitable for LBO. 3GPP targetWeight: Integer 1..N. The higher the number the higher the weight.
Release 11 eRabSetupFailu reRateCharacte ristic esActivationOr iginalCellLoad Parameters esActivationCa ndidateCellsLo adParameters 44 The target is on the number of E-RABsetup failures related to load divided by the total number of attempted E-RABsetups. For E-RAB setup failure related to load the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 are used. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:eRabSetupFailureRateCharacteristic Downlink and eRabSetupFailureRateCharacteristicUpli nk. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: eRabSetupFailureRateCharacteristicDown link: List of one or more entries, each consisting of: LowerEndOfCacRange, UpperEndOfCacRange, eRabSetUpFailureRateTarget eRabSetupFailureRateCharacteristicUpli nk: List of one or more entries, each consisting of: LowerEndOfCacRange, UpperEndOfCacRange, eRabSetUpFailureRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic This target is suitable for LBO. This attributes is relevant, if the cell acts as an original cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed ES algorithms to allow a cell to enter the energySaving state. The time duration indicates how long the load needs to have been below the threshold. This attributes is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed ES algorithms level to allow a n „original‟ cell to enter the energySaving state. Threshold and duration are applied tothe candidate cell(s)which will provides coverage backup of an original cell when it is in the energySaving state. The threshold applies in the same way for a candidate cell, no matter for which original cell it will provide backup coverage. The time duration indicates how long the traffic in the candidate cell needs to have been below the threshold before any original cells which will be provided backup coverage by the candidate cell enters energy saving state. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) lowerEndOfCacRange and upperEndOfCacRange and targetWeight: See eRabAbnormalReleaseRateCharacterist ic eRabSetUpFailureRateTarget: Integer 0..100 (representing a percentage) Threshold: Integer 0..100 (Percentage of PRB usage, see 3GPP TS 36.314 [13]) TimeDuration: Integer (in unit of seconds) Threshold: Integer 0..100 (Percentage of PRB usage (see 3GPP TS 36.314 [13]) ) TimeDuration: Integer (in unit of seconds)
Release 11 esDeactivation CandidateCells LoadParameters 45 3GPP TS 32.522 V11.6.1(2013-06) Threshold: Integer 0..100 (Percentage of PRB usage (see 3GPP TS 36.314 [13]) ) TimeDuration: Integer (in unit of seconds) Time period is valid on the specified day and time of every week. esNotAllowedTi mePeriod This attributes is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration which is used by distributed ES algorithms to allow a cell to leave the energySaving state. Threshold and time duration are applied to the candidate cell when itwhich provides coverage backup for the cell in energySaving state. The threshold applies in the same way for a candidate cell, no matter for which original cell it provides backup coverage. The time duration indicates how long the traffic in the candidate cell needs to have been above the threshold to wake up one or more original cells which have been provided backup coverage by the candidate cell. This attribute can be used to prevent a cell entering energySaving state. This attribute indicates a list of time periods during which inter-RAT energy saving is not allowed. periodOfDay: structure of startTime and endTime. The legal values are as follows: startTime and endTime: All values that indicate valid UTC time. endTime should be later than startTime. daysOfWeekList: list of weekday. weekday: Monday, Tuesday, … Sunday. esSwitch hoFailureRate hooSwitch This attribute determines whether the energy saving function is enabled or disabled. This indicates the assigned HOO target of the number of failure events related to handover divided by the total number of handover events, together with its targetWeight. This target is suitable for HOO or LBO. This attribute determines whether the Handover parameter Optimization Function is activated or deactivated. 3GPP List of time periods: {{daysOfWeek daysOfWeekList, periodOfDay dailyPeriod}} On, off A set of two numbers: the first indicates a percentage, the second a targetWeight (see eRabAbnormalReleaseRateCharacterist ic). On, off
Release 11 interRatEsActi vationOriginal CellParameters 46 This attribute is relevant, if the cell acts as an original cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed inter-RAT ES algorithms to allow an original cell to enter the energySaving state. The time duration indicates how long the traffic load (both for UL and DL) needs to have been below the threshold. 3GPP TS 32.522 V11.6.1(2013-06) InterRatESActivationOriginalCellParam eters: Structure: { LoadThreshold: Integer 0..10000 TimeDuration: Integer 0..900 (in unit of seconds) } In case the original cell is an EUTRAN cell, the load information refers to Composite Available Capacity Group IE (see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load = (100 - „Capacity Value‟ ) * „Cell Capacity Class Value‟, where„Capacity Value‟ and „Cell Capacity Class Value‟ are defined in 3GPP TS 36.423 [16]. In case the original cell is a UTRAN cell, the load information refers to Cell Load Information Group IE (see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load= „Load Value‟ * „Cell Capacity Class Value‟, where„Load Value‟ and „Cell Capacity Class Value‟ are defined in 3GPP TS 25.413 [17]. interRatEsActi vationCandidat eCellParameter s If the „Cell Capacity Class Value‟is not known, then „Cell Capacity Class Value‟ should be set to 1 when calculating the load, and the load threshold should be set in range of 0..100. This attribute is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed inter-RAT ES algorithms to allow an original cell to enter the energySaving state. Threshold and time duration are applied tothe candidate cell(s)which will provides coverage backup of an original cell when it is in the energySaving state. The time duration indicates how long the traffic load (both for UL and DL) in the candidate cell needs to have been below the threshold before any original cells which will be provided backup coverage by the candidate cell enters energySaving state. In case the candidate cell is a UTRAN or GERAN cell, the load information refers to Cell Load Information Group IE(see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load= „Load Value‟ * „Cell Capacity Class Value‟, where „Load Value‟ and „Cell Capacity Class Value‟ are definedin 3GPP TS 25.413 [17] (for UTRAN) / TS 48.008[18] (for GERAN). If the „Cell Capacity Class Value‟is not known, then „Cell Capacity Class Value‟ should be set to 1 when calculating the load, and the load threshold should be set in range of 0..100. 3GPP InterRatEsActivationCandidateCellPara meters: Structure { LoadThreshold: Integer 0..10000 TimeDuration: Integer 0..900 (in unit of seconds) }
Release 11 interRatEsDeac tivationCandid ateCellParamet ers lboSwitch maximumDeviati onHoTrigger isProbingCapab le minimumTimeBet weenHoTriggerC hange 47 This attribute is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration which is used by distributed interRAT ES algorithms to allow an original cell to leave the energySaving state. Threshold and time duration are applied to the candidate cell which provides coverage backup for the cell in energySaving state. The time duration indicates how long the traffic load (either for UL or DL) in the candidate cell needs to have been above the threshold to wake up one or more original cells which have been provided backup coverage by the candidate cell. For the load see the definition of interRatEsActivationCandidateCellParameters. This attribute determines whether the Load Balancing Optimization Function is activated or deactivated. This parameter allows the IRPManager to define the maximum allowed absolute deviation of the cell pair specific part of Handover Trigger (as defined in [14] (§22.4.1.4), from the default point of operation This attribute indicates whether this cell is capable of performing the ES probing procedure. During this procedure the eNB owning the cell indicates its presence to UEs for measurement purposes, but prevents idle mode UEs from camping on the cell and prevents incoming handovers to the same cell. If this parameter is absent, then probing is not done. This parameter defines the minimum allowed time interval between two changes of the Handover Trigger performed by MRO. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) InterRatEsDeactivationCandidateCellPa rameters: See InterRatEsActivationCandidateCellPara meters On, off Integer (+1..+96) Unit: 0.5 dB Boolean Integer (0..1440) Unit: Minutes
Release 11 rachOptAccessD elayProbabilit y 48 This is a list of target Access Delay probability (ADP) for the RACH optimization function. Each instance ADP of the list is the target time before the UE gets access on the random access channel, for the P percent of the successful RACH Access attempts with lowest access delay, over an unspecified sampling period. Each element of the list, ADPn, is a pair (a, b) where a is the targetProbability (in %) and b is the access delay (in milliseconds). The legal values for a are 25, 50, 75, 90. The legal values for b are 10 to 560. If ADPx‟s a is larger than that of ADPy, then ADPx‟sb must be larger than that of ADPy. This target is suitable for RO. rachOptAccessP robability 3GPP TS 32.522 V11.6.1(2013-06) This is a list of target Access Probability (APn) for the RACH optimization function. Each instance APn of the list is the probability that the UE gets access on the random access channel within n number of attempts, over an unspecified sampling period. The number of elements specified is 4. The number of elements supported is vendor specific. The choice of supported values for a and b is vendorspecific. Each element of the list, APn, is a pair (a, n) where a is the targetProbability (in %) and n is the access attempt number. The legal values for a are 25, 50, 75, 90. The legal values for n are 1 to 200. If APx‟s a is larger than that of APy, then APx‟s n must be larger than that of APy. This target is suitable for RO. The number of elements specified is 4. The number of elements supported is vendor specific. The choice of supported values for a and n is vendorspecific. roSwitch This attribute determines whether the RACH Optimization function is activated or deactivated. 3GPP On, off
Release 11 rrcConnectionA bnormalRelease RateCharacteri stic 49 The target is on the number of abnormal RRC connection releases related to load divided by the total number of RRC connection releases. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:rrcConnectionAbnormalReleaseRateCh aracteristicDownlink and rrcConnectionAbnormalReleaseRateCharac teristicUplink. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: rrcConnectionAbnormalReleaseRateCharac teristicDownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionAbnormalReleaseRateTarget rrcConnectionAbnormalReleaseCharacteri sticUplink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionAbnormalReleaseRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic rrcConnectionE stablishmentFa ilureRateChara cteristic This target is suitable for LBO. The target is on the number of RRC connection establishment failures related to load divided by the total number of attempted RRC connection establishments. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:rrcConnectionEstablishmentFailureR ateCharacteristicDownlink and rrcConnectionEstablishmentFailureRateC haracteristicUplink. At least one of these charateristics must be present. Together with the characteristic its targetWeigth as a SON target is defined as part of this attribute. The characteristics have the following structure: rrcConnectionEstablishmentFailureRateC haracteristicDownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionEstablishmentFailureRateTarget rrcConnectionEstablishmentFailureRateC haracteristicUplink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionEstablishmentFailureRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic This target is suitable for LBO. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) lowerEndOfCacRange and upperEndOfCacRange and targetWeight: See eRabAbnormalReleaseRateCharacterist ic rrcConnectionAbnormalReleaseRateTar get: Integer 0..100 (representing a percentage) lowerEndOfCacRange and upperEndOfCacRange and targetWeigth: See eRabAbnormalReleaseRateCharacterist ic rrcConnectionEstablishmentFailureRate Target: Integer 0..100 (representing a percentage)
Release 11 50 selectedSonCoo rdPolicy sonFuncCapabil ityBelowItfN sonFuncPriorit yOrder 5.5.2 3GPP TS 32.522 V11.6.1(2013-06) This attribute indicates the SON coordination policy that is selected by IRPManager in case the SON coordination function is located below Itf-N. The selected SON coordination policy is one of the enumed value from BaseOnPriority and BaseOnState, wherein - BaseOnPriority, representing that the coordination is based on the priority order of the SON functionslistedin “sonFuncPriorityOrder” attribute; - BaseOnState, representing the coordination is based on the cell state. The examples of SON coordination for some certain conflicting casesbased on priority and state are depicted in Annex B. This attributes represents the SON functions supported below Itf-N. It is a list of SON function name. The SON function name is one of the enumed value from anr, hoo, lbo, es, coc and cco, wherein - anr repesenting automated neighbor relation; - hoo representing handover parameter optimization; - lbo representing load balancing optimization; - es representing energy saving; - coc representing cell outage compensation; - cco representing coverage and capacity optimization. This attribute indicates the priority order of SON functions below Itf-N for SON coordination purpose, in case the selectedSonCoordPolicy equals to “BaseOnPriority”. It is a list of SON function name, see the detailed description in “sonFuncCapabilityBelowItfN” attribute. The priority order is indicated by the sequence of the SON function name in the list, i.e., the first element in the list takes the highest priority, and the last element in the list takes the lowest priority. In case of selectedSonCoordPolicy does not equal to “BaseOnPriority”, this sequence of the SON function name in the list is not used as priority order for SON coordination. Enumerated {BaseOnPriority, BaseOnState} List of SON function name. SON function name: Enumerated{anr, hoo, lbo, es, coc, cco} List of SON function name: for SON function name, see “sonFuncCapabilityBelowItfN” attribute. Constraints None. 5.6 Common Notifications 5.6.1 Configuration notifications Name notifyAttributeValueChange notifyObjectCreation notifyObjectDeletion 3GPP Qualifier O O O Notes
Release 11 51 3GPP TS 32.522 V11.6.1(2013-06) Annex A (informative): Target Achievement Evaluation To evaluate the result of the optimization the target achievement needs to be evaluated. This can be done by calculating the Total Target Achievement as follows. The Total Target Achievement is the sum of the products of the individual target achievement (difference between target and performance) and the individual targetWeights: Total Target Achievement = Sum i=1..n [ ( minTarget i – performance i ) x weighti ] + Sum j=1..n [ performance j – maxTarget j ) x weight j ] where minTarget is a target to be minimized and maxTarget is a target to be maximized. For targets with a substructure (like *Characteristic, see §5.5.1) the above formula is applied to each individual substructure target. The higher the Total Target Achievement, the better is the result of the optimization. 3GPP
Release 11 52 3GPP TS 32.522 V11.6.1(2013-06) Annex B (informative): Examples of how to use general SON coordination solutions Examples of how to use general SON coordination solutions are as below: B.1 Coordination of COC and CCO using priority of SON functions To prevent conflicting setting as illustrated in clause 4.7.3.2.1, the cell(s) whichmay need to be coordinated between COC and CCO, i.e., the impact area information, should be known by the SON Coordination Function. By comparing the priorities of COC and CCO, SON Coordination Function will decide to do the high-priority action and suspend the low-priority action on the coordinated cell(s). The priorities of COC and CCO can be preset by operator to SON Coordination Function, or SON Coordination Function inquires the default priority of COC and CCO to each of them. The cell which needs to be coordinated between COC and CCO is: - The cell in which there is coverage or capacity problem and CCO action is needed, meanwhile the cell is outage or compensating or going to compensate for outage; or - The cell which is located in the CCO optimization analysis area for other cell which has coverage or capacity problem, meanwhile the cell is outage orcompensatingor going to compensating for outage; After the high-priority SON function executes action, the SON Coordination Function is informed about the result (successful/unsuccessful, parameters changes) of the executed high-priority SON action. Then,SON Coordination Function will analyse the latest network situation to decide how to deal with the suspended low-priority SON action, for example, resuming or rejecting. B.2 Coordination of COC, CCO and ES using priority of SON functions To prevent conflicting adjustment from COC, ES and optimization from CCO in the common affected cell(s) (e.g., Cell 2 in the Figure 4.7.3.2), the cell(s) whichmay need to be coordinated among COC, CCO and ES, i.e., the impact area information, should be known by the SON Coordination Function. By comparing the priorities of COC, CCO and ES, SON Coordination Function will decide to do the highest-priority action and suspend the low-priority actions on the coordinated cell(s). The priorities of COC, CCO and ES can be preset by operator to SON Coordination Function, or SON Coordination Function inquires the default priority of COC, CCO and ES to each of them. The cell which needs to be coordinated among COC, CCO and ES is: - The cell in which there is coverage or capacity problem and CCO action is needed, meanwhile the cell is outage or compensating or going to compensate for outage or ES; or - The cell which is located in the CCO optimization analysis area for other cell which has coverage or capacity problem, meanwhile the cell is outage or compensating or going to compensate for outage or ES; After the highest-priority SON function executes action, the SON Coordination Function is informed about the result (successful/unsuccessful, parameters changes) of the executed highest-priority SON action. Then,SON Coordination Function will analyse the latest network situation to decide how to deal with the suspended lowpriority SON actions, for example, resuming or rejecting. 3GPP
Release 11 B.3 53 3GPP TS 32.522 V11.6.1(2013-06) Coordination of COC, CCO and ES based on the cell state The following lists the examples of how SON Coordination Function (SCF) can resolve the conflicts between COC, CCO, and ES functions based on cell state. Although not shown, priority may be used to along with the cell state to resolve the conflicts. Possible conflict #1: COC requests a cell that is compensating an energy saving cell to compensate an outage cell Resolution: When COC requests SCF that cell A is going to compensate an outaged cell, SCF should check whether cell A is compensating an energy saving cell. If so, SCF should check whether cell A can compensate both the outage cell and the energy saving cell concurrently. If not, the SCF may disallow cell A to compensate an energy saving cell. Possible conflict #2: COC requests a cell that is being changed or going to be changed by CCO to compensate an outage cell Resolution: When COC requests SCF that cell A is going to compensate an outaged cell, SCF should check whether CCO is updating parameters to optimize the capacity and coverage of cell A. If so, SCF may not allow cell A to compensate an outaged cell; otherwise SCF should allow cell A to compensate an outage cell. Possible conflict #3: ES requests a candidate cell that is compensating an outage cell to compensate an energy saving cell Resolution: When ES request SCF that cell A is to compensate a cell going to enter energy saving, SCF should check the cOCStatus.state of cell A. If cOCStatus.state = cOCCompensating, SCF should check whether cell A can compensate both the outage cell and the energy saving cell concurrently. If not, the SCF may disallow cell A to compensate an energy saving cell. Possible conflict #4: ES requests a cell that is being changed or going to be changed by CCO to compensate an energy saving cell Resolution: When ES requests SCF that cell A is going to compensate a cell going to enter energy saving, SCF should check whether CCO is updating parameters to optimize the capacity and coverage of cell A. If so, SCF may not allow cell A to compensate an energy saving cell; otherwise SCF should allow cell A to compensate an outage cell. Possible conflict #5: CCO is going to change the configuration parameter of a cell that is compensating an outage cell Resolution: When CCO requests SCF that cell A is going to change the configuration parameter, SCF should check the cOCStatus.state of cell A. If cOCStatus.state = cOCCompensating, SCF should disallow cell A to change the configuration parameter. Annex C (informative): State diagram for Distributed and EM-centralized Energy Saving Management Energy Saving Management “state” attributes are available at various levels: - SubNetwork IOC level, via the attribute esSwitch defined in the IOC SonControl; 3GPP
Release 11 54 3GPP TS 32.522 V11.6.1(2013-06) - ENBFunction IOC level, via the attribute esSwitch defined in the IOC SonControl; - EUtranGenericCell IOC level, via the locally defined attribute isChangeForEnergySavingAllowed, and via the attribute energySavingState defined in the IOC EnergySavingProperties. The following figure provides an overview of Energy Saving Management related IOCs, state attribute names and possible values, for Distributed and EM-centralized Energy Saving Management: Figure C-1: IOCs and state attributes for Distributed and EM-centralized ESM Dependencies exist between distributed ESM state attributes. The diagram below shows which allowed combinations of attribute state values, and which state transitions, are valid and which are not. 3GPP
Release 11 55 3GPP TS 32.522 V11.6.1(2013-06) Figure C-2: State diagram for Distributed and EM-centralized ESM Description: a) The ESM-related state attribute esSwitch is used by IRPManager to switch on / off the ESM functionality, in the distributed and EM-centralized architectures. This attribute has two possible values: On, Off. It can be set at the sub-network level and at the eNodeB level; b) The ESM-related state attribute isChangeForEnergySavingAllowed is used by IRPManager to prohibit or allow configuration changes of cells individually, within a eNodeB / sub-network, for ESM purposes by the IRPAgent. This attribute has two possible values: Yes, No. c) The ESM-related state attribute esState is used to reflect the actual status of a cell regarding the energy saving. This attribute has two possible values: isEnergySaving, isNotEnergySaving. Figure C-2 describes the following state transitions: 1) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving) to((esSwitch = On and isChangeForEnergySavingAllowed = Yesand esState = isEnergySaving): happens when: ES Policies attached to the subject cell and to candidate for compensation cells, e.g. threshold and duration, are satisfied and allow entering Energy Saving state. 2) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isEnergySaving) to(esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: ES Policies attached to the subject cell and to candidate for compensation cells, e.g. threshold and duration, are satisfied and allow leaving Energy Saving state. 3) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes) to (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute isChangeForEnergySavingAllowed to “No”. 3GPP
Release 11 56 3GPP TS 32.522 V11.6.1(2013-06) 4) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to isChangeForEnergySavingAllowed = Yes: happens when: IRP Manager sets the attribute isChangeForEnergySavingAllowed to “Yes”. 5) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes) to( esSwitch = Off and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “Off”. 6) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “On”. 7) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to (esSwitch = Off and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “Off”. 8) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “On”. 3GPP
Release 11 57 3GPP TS 32.522 V11.6.1(2013-06) Annex D(informative): Change history Change history Date 2010-03 2010-03 2010-09 2010-12 2010-12 2010-12 TSG # SA#47 -SA#49 SA#50 SA#50 SA#50 TSG Doc. SP-100053 -SP-100491 SP-100858 SP-100749 SP-100833 CR --001 003 005 002 Rev ---1 3 2010-12 SA#50 SP-100866 004 3 2011-01 -- -- -- - 2011-03 2011-03 2011-03 2011-03 2011-03 SA#51 SA#51 SA#51 SA#51 SA#51 SP-110098 SP-110098 SP-110100 SP-110100 010 011 013 014 2 3 - 2011-06 2011-06 2011-09 2011-12 2011-12 2012-06 2012-06 2012-06 SA#52 SA#52 SA#53 SA#54 SA#54 SA#56 SA#56 SA#56 SP-110097 SP-110284 SP-110284 SP-110634 SP-110718 SP-110721 SP-120364 SP-120358 SP-120364 016 018 066 066a 068 071 078 087 088 1 2 1 1 1 1 -1 2012-06 2012-06 2012-09 2012-09 2012-09 2012-09 2012-09 2012-09 SA#56 SA#56 SA#57 SA#57 SA#57 SA#57 SA#57 SA#57 SP-120364 SP-120371 SP-120645 SP-120645 SP-120573 SP-120567 SP-120567 SP-120567 091 092 096 098 103 105 107 108 2 1 2 2 -1 3 2012-09 2012-09 SA#57 SA#57 SP-120567 SP-120567 SP-120791 SP-120783 SP-120791 SP-120791 109 110 111 114 115 117 2 2 2 2 2 SP-120791 SP-120800 SP-120791 SP-120791 SP-120791 SP-120783 SP-120800 119 120 125 126 127 128 131 2 5 1 1 1 3 - SP-130056 SP-130048 SP-130056 104 132 133 7 2 2 SP-130266 SP-130266 SP-130304 SP-130304 134 135 136 139 1 1 1 - 2012-12 SA#58 2013-03 SA#59 2013-03 2013-06 2013-06 SA#60 Subject/Comment Presentation to SA for Information and Approval Publication of SA approved version Remove targets based on not supported by measurements Correcting the support qualifiers of SONControl attributes Disambiguate and correct the description of SON Targets hierarchy Allow EM centralized architecture for Hand-over parameter optimization - Align with 32.500 Adding NRM for Energy Saving Management policies and ESM switch Correction of misimplementation of CR in clause 5.3.2.3 and CR history correction. Introducing RACH optimization management Rapporteur clean-up for editorial errors Use ESPolicies also for EM centralized architecture Correct cardinality of ESPolicies Add a new attribute into SONControl object class to switch on/off Cell Outage Compensation - Align with 32.541 Finalization of Rel-10 SON functionalities Add parameters to control Mobility Robustness Optimization Add PM for Inter-RAT MRO Adding definition of SON coordination Correction MRO management of HO Trigger Adding coordination use case among CCO, COC and ESM Remove the EUTRANRelationSON in the UML Add SON Coordination use case between SON functions below ItfN and CM operations over Itf-N Common SON coordination solution Add time period configuration to allow inter-RAT energy saving Remove Inter-RAT ES restriction for esNotAllowedTimePeriod Correct candidateCellLoadParameters Add support for Inter-RAT Energy Saving Management MoveSON coordination concept description to TS 32.521 Coordinationbetween ES and cell compensation Change description of Coordination between SON functions below Itf-N and CM operations over itf-N Enhancement of general SON coordination solutions Add examples of how to use general SON coordination solutions Correcting function name Clean-up changes Further enhancement of general SON coordination solutions Add description for Coordination between SON functions below ItfN and non-SON operations over Itf-N Add conflict detection for general SON coordination solutions Add load threshold parameters to Inter-RAT energy saving policy Coordination between COC and ANR Coordination between HOO and LBO Add relationship diagram for SON coordination Addition of probing state and its control for Energy Saving Enhance esNotAllowedTimePeriod text description to fulfil energy saving allowed or prohibited for an EUTRAN cell SON Coordination NRMs Add informative annex on Distributed ES State Management Add coordination example based on cell state Editorial correction of the spec title Correction of attribute constraints Remove EUtranRelationSON in UML diagram Correcting error in attribute constraint Correct the attribute constraint of energySavingControl Fixes typo in history table 3GPP Old -1.0.0 9.0.0 9.1.0 9.1.0 9.2.0 New 1.0.0 9.0.0 9.1.0 9.2.0 9.2.0 10.0.0 9.2.0 10.0.0 10.0.0 10.0.1 10.0.1 10.0.1 10.0.1 10.0.1 10.0.1 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 11.0.0 11.0.0 11.1.0 11.1.0 11.1.0 10.2.0 10.2.0 11.0.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.3.0 11.3.0 11.3.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.4.0 11.4.0 11.5.0 11.5.0 11.5.1 11.5.1 11.6.0 11.6.0 11.6.1

More Related Content

PDF
3gpp wifi lte_rel_10
Sankarshan Deb
 
DOC
R3 030340(tr25.891 v030 improvement of rrm across rns and rns bss)-clean
adelekejare
 
DOC
25934 400 aal2 qo s optimization
adelekejare
 
DOC
25933 540 ip transport in the utran
adelekejare
 
DOC
25922 601 radio resource management strategies
adelekejare
 
PDF
Ir33 40 gprs
Suren Aslanyan
 
DOC
25892 600 feasibility study for orthogonal frequency division multiplexing (o...
adelekejare
 
DOC
R3 031545 tr25852-v012 iu enhancements for ims support in utran
adelekejare
 
3gpp wifi lte_rel_10
Sankarshan Deb
 
R3 030340(tr25.891 v030 improvement of rrm across rns and rns bss)-clean
adelekejare
 
25934 400 aal2 qo s optimization
adelekejare
 
25933 540 ip transport in the utran
adelekejare
 
25922 601 radio resource management strategies
adelekejare
 
Ir33 40 gprs
Suren Aslanyan
 
25892 600 feasibility study for orthogonal frequency division multiplexing (o...
adelekejare
 
R3 031545 tr25852-v012 iu enhancements for ims support in utran
adelekejare
 

Viewers also liked (20)

DOCX
Retail marketing
Krishna Kumar K
 
PDF
Vessel 2l
Mark Posey
 
PDF
Vice body
Mark Posey
 
PDF
7 Facts Every Author Ought To Know
TreDigital
 
PDF
directiva
Sally chavez
 
PDF
Nanh trang
cohtran
 
PDF
LIFE OF PI
cohtran
 
PDF
Public Safety LTE Broadband - Service Assurance
Steve Bowker
 
PPT
Obn211111 i manager n2000 bms introduction r011 issue 1.0
Vìctor Isaac Herrera Pérez
 
PPTX
LTE crash course
Samuel Erdtman
 
PPT
ptcl noc Introductry concepts -_lecture___1
Zohaib Hafeez
 
PDF
Tycvth
cohtran
 
PDF
3g-lte-oss-performance-management
vishal123
 
PPTX
Croatian Telekom NGOSS projects – Shape of things to came …
Damir Medved
 
PDF
Oss transformation
Riswan
 
PDF
Summit 16: Open-O Mini-Summit - Vision and Update
OPNFV
 
PDF
Ngen oss bss - architecture evolution
Grazio Panico
 
PDF
Next generation OSS/BSS architecture
Ericsson
 
PPTX
network monitoring system ppt
ashutosh rai
 
PDF
Telecom OSS/BSS Overview
magidg
 
Retail marketing
Krishna Kumar K
 
Vessel 2l
Mark Posey
 
Vice body
Mark Posey
 
7 Facts Every Author Ought To Know
TreDigital
 
directiva
Sally chavez
 
Nanh trang
cohtran
 
LIFE OF PI
cohtran
 
Public Safety LTE Broadband - Service Assurance
Steve Bowker
 
Obn211111 i manager n2000 bms introduction r011 issue 1.0
Vìctor Isaac Herrera Pérez
 
LTE crash course
Samuel Erdtman
 
ptcl noc Introductry concepts -_lecture___1
Zohaib Hafeez
 
Tycvth
cohtran
 
3g-lte-oss-performance-management
vishal123
 
Croatian Telekom NGOSS projects – Shape of things to came …
Damir Medved
 
Oss transformation
Riswan
 
Summit 16: Open-O Mini-Summit - Vision and Update
OPNFV
 
Ngen oss bss - architecture evolution
Grazio Panico
 
Next generation OSS/BSS architecture
Ericsson
 
network monitoring system ppt
ashutosh rai
 
Telecom OSS/BSS Overview
magidg
 
Ad

Similar to 3 gpp ts 32.522 self-organizing networks (son) policy network resource model (nrm) (20)

DOC
3GPP VoLTE IMS
PaulTayebwa
 
DOC
3GPP IMS VOLTE
PaulTayebwa
 
PDF
23060 8d0
Eran Gross
 
DOC
Document nsn
Lm Tài
 
PDF
25331 b50
Rajender Reddy
 
PDF
3GPP TR 22.885 study on LTE support for V2X services
Yi-Hsueh Tsai
 
PDF
Inter rnc procedures
radio56
 
DOC
3 gpp key performance indicators (kpi) for umts and gsm release 9
Telecom Consultant
 
DOC
25951 620 base station (bs) classification (fdd)
adelekejare
 
PDF
3GPP A25133 450
Georgios Giannakopoulos
 
DOC
25931 510 utran functions, examples on signalling procedures
adelekejare
 
PDF
0801 801
uttuttimail
 
PDF
3 gpp ts 36.423 36423-800
Anderson Brandão
 
DOC
R3 030340(tr25.891 v030 improvement of rrm across rns and rns bss)-rev
adelekejare
 
PDF
3 gpp ts 36.211
Hosnan Fath
 
DOC
25952 520 base station classification (tdd)
adelekejare
 
DOC
25996 610 spacial channel model for multiple input multiple output (mimo) sim...
adelekejare
 
PDF
3 gpp tr 23.907v1.2.0
Alicia Delafinca
 
PDF
25414 3d0
kosotiro
 
PDF
Lte x2 ap_3gpp_36423-pdf
saint_40s
 
3GPP VoLTE IMS
PaulTayebwa
 
3GPP IMS VOLTE
PaulTayebwa
 
23060 8d0
Eran Gross
 
Document nsn
Lm Tài
 
25331 b50
Rajender Reddy
 
3GPP TR 22.885 study on LTE support for V2X services
Yi-Hsueh Tsai
 
Inter rnc procedures
radio56
 
3 gpp key performance indicators (kpi) for umts and gsm release 9
Telecom Consultant
 
25951 620 base station (bs) classification (fdd)
adelekejare
 
3GPP A25133 450
Georgios Giannakopoulos
 
25931 510 utran functions, examples on signalling procedures
adelekejare
 
0801 801
uttuttimail
 
3 gpp ts 36.423 36423-800
Anderson Brandão
 
R3 030340(tr25.891 v030 improvement of rrm across rns and rns bss)-rev
adelekejare
 
3 gpp ts 36.211
Hosnan Fath
 
25952 520 base station classification (tdd)
adelekejare
 
25996 610 spacial channel model for multiple input multiple output (mimo) sim...
adelekejare
 
3 gpp tr 23.907v1.2.0
Alicia Delafinca
 
25414 3d0
kosotiro
 
Lte x2 ap_3gpp_36423-pdf
saint_40s
 
Ad

Recently uploaded (20)

PDF
Hazard Identification & Risk Assessment .pdf
estagiarioprotegesms
 
PPTX
A powerpoint presentation on the Revised K-10 Science Shaping Paper
JericEstaco2
 
PPTX
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
PDF
Practical Manual AGRO-233 Principles and Practices of Natural Farming
MilindKhedekar2
 
PPTX
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
EricaRamos80
 
PPTX
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
DOC
Soft-furnishing-By-Architect-A.F.M.Mohiuddin-Akhand.doc
ArchitectAFMMohiuddi
 
PDF
Empowerment Technology for Senior High School Guide
solthereseamericandr
 
PDF
ChatGPT for Dummies - Pam Baker Ccesa007.pdf
Demetrio Ccesa Rayme
 
PPTX
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
kawisojames10
 
PDF
LNK 2025 (2).pdf MWEHEHEHEHEHEHEHEHEHEHE
NielDestora
 
PDF
Indian roads congress 037 - 2012 Flexible pavement
offersjackpot
 
PDF
OBE - B.A.(HON'S) IN INTERIOR ARCHITECTURE -Ar.MOHIUDDIN.pdf
ArchitectAFMMohiuddi
 
PPTX
UNIT III MENTAL HEALTH NURSING ASSESSMENT
Sonali Gupta
 
PPTX
Onco Emergencies - Spinal cord compression Superior vena cava syndrome Febr...
Medpopz
 
PPTX
Orientation - ARALprogram of Deped to the Parents.pptx
JeromeTamayoSantiago1
 
PDF
advance database management system book.pdf
hinamannan364
 
PDF
Weekly quiz Compilation Jan -July 25.pdf
Nitin Suresh
 
PDF
Complications of Minimal Access Surgery at WLH
mohitsuren827
 
PDF
Classroom Observation Tools for Teachers
Nicaramirez
 
Hazard Identification & Risk Assessment .pdf
estagiarioprotegesms
 
A powerpoint presentation on the Revised K-10 Science Shaping Paper
JericEstaco2
 
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
Practical Manual AGRO-233 Principles and Practices of Natural Farming
MilindKhedekar2
 
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
EricaRamos80
 
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
Soft-furnishing-By-Architect-A.F.M.Mohiuddin-Akhand.doc
ArchitectAFMMohiuddi
 
Empowerment Technology for Senior High School Guide
solthereseamericandr
 
ChatGPT for Dummies - Pam Baker Ccesa007.pdf
Demetrio Ccesa Rayme
 
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
kawisojames10
 
LNK 2025 (2).pdf MWEHEHEHEHEHEHEHEHEHEHE
NielDestora
 
Indian roads congress 037 - 2012 Flexible pavement
offersjackpot
 
OBE - B.A.(HON'S) IN INTERIOR ARCHITECTURE -Ar.MOHIUDDIN.pdf
ArchitectAFMMohiuddi
 
UNIT III MENTAL HEALTH NURSING ASSESSMENT
Sonali Gupta
 
Onco Emergencies - Spinal cord compression Superior vena cava syndrome Febr...
Medpopz
 
Orientation - ARALprogram of Deped to the Parents.pptx
JeromeTamayoSantiago1
 
advance database management system book.pdf
hinamannan364
 
Weekly quiz Compilation Jan -July 25.pdf
Nitin Suresh
 
Complications of Minimal Access Surgery at WLH
mohitsuren827
 
Classroom Observation Tools for Teachers
Nicaramirez
 

3 gpp ts 32.522 self-organizing networks (son) policy network resource model (nrm)

  • 1. 3GPP TS 32.522 V11.6.1(2013-06) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) (Release 11) The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPPOrganizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPPonly. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
  • 2. Release 11 2 3GPP TS 32.522 V11.6.1(2013-06) Keywords SON, Self-Optimization, management 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org 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. © 2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association 3GPP
  • 3. Release 11 3 3GPP TS 32.522 V11.6.1(2013-06) Contents Foreword............................................................................................................................................................. 6 Introduction ........................................................................................................................................................ 6 1 Scope ........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7 3 Definitions and abbreviations................................................................................................................... 8 3.1 3.2 4 Definitions ......................................................................................................................................................... 8 Abbreviations ..................................................................................................................................................... 8 SON Policy and Optimization Function Definitions ................................................................................ 9 4.1 Monitoring and Management Operations for Self-Optimization ....................................................................... 9 4.1.1 Monitoring and Management Function ........................................................................................................ 9 4.1.1.1 Usage of Itf-N ......................................................................................................................................... 9 4.2 Load Balancing Optimization Function ............................................................................................................. 9 4.2.1 Objective and Targets................................................................................................................................... 9 4.2.2 Parameters To Be Optimized ..................................................................................................................... 10 4.2.3 Optimization Method ................................................................................................................................. 10 4.2.3.1 Problem Detection ................................................................................................................................ 10 4.2.3.2 Problem Solution .................................................................................................................................. 11 4.2.4 Architecture ................................................................................................................................................ 11 4.2.4.1 Definition of Logical Functions............................................................................................................ 11 4.2.4.2 Location of Logical Functions .............................................................................................................. 11 4.2.5 PM .............................................................................................................................................................. 11 4.3 Handover (HO) Parameter Optimization Function .......................................................................................... 12 4.3.1 Objective and Targets................................................................................................................................. 12 4.3.2 Parameters To Be Optimized ..................................................................................................................... 12 4.3.3 Optimization Method ................................................................................................................................. 13 4.3.3.1 Problem Detection ................................................................................................................................ 13 4.3.3.2 Problem Solution .................................................................................................................................. 13 4.3.4 Architecture ................................................................................................................................................ 13 4.3.4.1 Definition of Logical Functions............................................................................................................ 13 4.3.4.2 Location of Logical Functions .............................................................................................................. 14 4.3.5 PM .............................................................................................................................................................. 14 4.4 Interference Control Function .......................................................................................................................... 15 4.5 Capacity and Coverage Optimization Function ............................................................................................... 15 4.5.1 Objective and Targets................................................................................................................................. 15 4.5.2 Parameters to be optimized ........................................................................................................................ 15 4.5.3 Optimization Method ................................................................................................................................. 15 4.5.3.1 ProblemDetection ................................................................................................................................. 15 4.5.3.2 Problem Solution .................................................................................................................................. 16 4.5.4 Architecture ................................................................................................................................................ 16 4.5.4.1 Definition of Logical Functions............................................................................................................ 16 4.5.4.2 Location of Logical Functions .............................................................................................................. 16 4.6 RACH Optimization Function ......................................................................................................................... 17 4.6.1 Objective and Targets................................................................................................................................. 17 4.6.2 Parameters to be optimized ........................................................................................................................ 18 4.6.3 Optimization Method ................................................................................................................................. 18 4.6.3.1 ProblemDetection ................................................................................................................................. 18 4.6.3.2 Problem Solution .................................................................................................................................. 18 4.6.4 PM .............................................................................................................................................................. 18 4.7 SON coordination ............................................................................................................................................ 18 4.7.1 Introduction ................................................................................................................................................ 18 4.7.2 Coordination between SON functions below Itf-N and non-SON CM operations over itf-N .................... 19 4.7.2.1 Description ............................................................................................................................................................ 19 4.7.2.2 Prevention ............................................................................................................................................................. 20 4.7.2.3 Resolution ............................................................................................................................................................. 20 4.7.3 Coordination between different SON functions ......................................................................................... 20 3GPP
  • 4. Release 11 4.7.3.1 4.7.3.1.1 4.7.3.1.2 4.7.3.1.3 4.7.3.2 4.7.3.2.1 4.7.3.2.2 4.7.3.2.3 4.7.3.3 4.7.3.3.1 4.7.3.3.2 4.7.3.3.3 4.7.3.4 4.7.3.4.1 4.7.3.4.2 4.7.3.4.3 4.7.4 4.7.4.1 4.7.4.2 4.7.4.3 5 5.1 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 5.3.3.4 5.3.4 5.3.4.1 5.3.4.2 5.3.4.3 5.3.4.4 5.3.5 5.3.6 5.3.6.1 5.3.6.2 5.3.6.3 5.3.6.4 5.3.7 5.3.7.1 5.3.7.2 5.3.7.3 5.3.7.4 5.3.8 5.3.8.1 5.3.8.2 4 3GPP TS 32.522 V11.6.1(2013-06) Coordination between Cell Outage Compensation and Energy Saving Management .......................... 20 Description ...................................................................................................................................... 20 Prevention ....................................................................................................................................... 20 Resolution ....................................................................................................................................... 20 Coordinationamong Cell Outage Compensation,Capacity and Coverage Optimization, and Energy Saving Management ................................................................................................................. 21 Description ...................................................................................................................................... 21 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 22 Coordination between Cell Outage Compensation and Automatic NeighbourRelation ....................... 22 Description ...................................................................................................................................... 22 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 22 Coordination between HandOver parameter Optimization and Load Balancing Optimization............ 22 Description ...................................................................................................................................... 22 Prevention ....................................................................................................................................... 22 Resolution ....................................................................................................................................... 23 General SON coordination solutions .......................................................................................................... 23 Overview .............................................................................................................................................. 23 Conflict prevention ............................................................................................................................... 24 Conflict resolution ................................................................................................................................ 25 Information Object Classes (IOCs) ........................................................................................................ 26 Information entities imported and local labels ................................................................................................. 26 Class diagram................................................................................................................................................... 26 Attributes and relationships ........................................................................................................................ 26 Inheritance .................................................................................................................................................. 34 Information Object Class (IOC) definitions ..................................................................................................... 36 SONTargets ................................................................................................................................................ 36 Definition.............................................................................................................................................. 36 Attributes .............................................................................................................................................. 36 Attribute constraints ............................................................................................................................. 37 Notifications ......................................................................................................................................... 37 SONControl................................................................................................................................................ 37 Definition.............................................................................................................................................. 37 Attributes .............................................................................................................................................. 37 Attribute constraints ............................................................................................................................. 37 Notifications ......................................................................................................................................... 37 ESPolicies .................................................................................................................................................. 37 Definition.............................................................................................................................................. 37 Attributes .............................................................................................................................................. 37 Attribute constraints ............................................................................................................................. 38 Notifications ......................................................................................................................................... 38 EUtranCellSON.......................................................................................................................................... 38 Definition.............................................................................................................................................. 38 Attributes .............................................................................................................................................. 38 Attribute constraints ............................................................................................................................. 38 Notifications ....................................................................................................................................... 38 Void ............................................................................................................................................................ 38 EnergySavingProperties ............................................................................................................................. 38 Definition.............................................................................................................................................. 38 Attributes ............................................................................................................................................ 39 Attribute constraints ............................................................................................................................. 39 Notifications ......................................................................................................................................... 39 interRatEsPolicies ...................................................................................................................................... 39 Definition.............................................................................................................................................. 39 Attributes .............................................................................................................................................. 39 Attribute constraints ............................................................................................................................. 39 Notifications ....................................................................................................................................... 39 IOC SONFuncInfo ..................................................................................................................................... 39 Definition.............................................................................................................................................. 39 Attributes .............................................................................................................................................. 40 3GPP
  • 5. Release 11 5.3.8.3 5.3.8.4 5.3.9 5.3.9.1 5.3.9.2 5.3.9.3 5.3.9.4 5.4 5.5 5.5.1 5.5.2 5.6 5.6.1 5 3GPP TS 32.522 V11.6.1(2013-06) Attribute constraints ............................................................................................................................. 40 Notifications ......................................................................................................................................... 40 IOC SONCoordinationPolicies .................................................................................................................. 40 Definition.............................................................................................................................................. 40 Attributes .............................................................................................................................................. 41 Attribute constraints ............................................................................................................................. 41 Notifications ......................................................................................................................................... 41 Information relationship definitions................................................................................................................. 41 Information attribute definitions ...................................................................................................................... 42 Definition and legal values ......................................................................................................................... 42 Constraints ................................................................................................................................................. 50 Common Notifications ..................................................................................................................................... 50 Configuration notifications ........................................................................................................................ 50 Annex A (informative): Target Achievement Evaluation ................................................................... 51 Annex B (informative): Examples of how to use general SON coordination solutions .................... 52 B.1 Coordination of COC and CCO using priority of SON functions.......................................................... 52 B.2 Coordination of COC, CCO and ES using priority of SON functions ................................................... 52 B.3 Coordination of COC, CCO and ES based on the cell state................................................................... 53 Annex C (informative): State diagram for Distributed and EM-centralized Energy Saving Management ................................................................................................... 53 Annex D(informative): Change history ............................................................................................... 57 3GPP
  • 6. Release 11 6 3GPP TS 32.522 V11.6.1(2013-06) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below: 32.521: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements 32.522: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) 32.526: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP):Solution Set (SS) definitions 3GPP
  • 7. Release 11 1 7 3GPP TS 32.522 V11.6.1(2013-06) Scope The present document is part of an Integration Reference Point (IRP) named Self Organizing Networks (SON) Policy Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning SON policies. The SON policy NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s). The present document specifies the protocol neutral SON policy NRM IRP: Information Service (IS). In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [11]). However, which Interface IRP is applicable is outside the scope of the present document. The present document also contains stage 2 descriptions for those functionalities for the Self-Optimization OAM, SON coordination and Energy Saving Management. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements". [2] 3GPP TS 32.102: "Telecommunication management; Architecture". [3] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions". [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [5] 3GPP TS 32.521: "Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements". [6] 3GPP TS 36.331: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specification". [7] 3GPP TS 36.423: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access Network (E-UTRAN);X2 Application Protocol (X2AP)". [8] 3GPP TS 32.425: "Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Performance measurements; Evolved Universal Terrestrial Radio Access Network (E-UTRAN)" [9] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)" [10] 3GPP TS 32.762: "Telecommunication management; Configuration Management (CM); Evolved Universal Terrestrial Radio Access Network (E-UTRAN) network resources Integration Reference Point (IRP): Network Resource Model (NRM)" [11] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Information Service (IS)". [12] 3GPP TS 36.413: "Technical Specification Group Radio Access Network;Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". 3GPP
  • 8. Release 11 8 3GPP TS 32.522 V11.6.1(2013-06) [13] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 Measurements". [14] 3GPP TS 36.300:"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description;Stage 2". [15] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);Overall description; Stage 2". [16] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". [17] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". [18] 3GPP TS 48.008: "Mobile Switching Centre-Base Station System (MSC-BSS) interface; Layer 3 specification". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 32.101 [1], TS 32.102 [2], TS 32.150 [3] and TR 21.905 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 32.521 [5], TS 32.101 [1], TS 32.102 [2] and TR 21.905 [4], in that order. Target: See 3GPPTS32.521 [5]. Trigger condition:See 3GPPTS32.521 [5]. Hand-Over parameter Optimisation: See clause 4.3 of this document and Mobility Robustness Optimisation (MRO) are synonyms (see TS 36.300 [14]). 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [4], TS 32.521 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [4] and TS 32.521 [5]. CAC CCO CDF COC EM eNodeB, eNB ESM E-UTRAN HO HOO ICIC IOC LB LBO MRO NM NRM OAM RO SON UE Composite Available Capacity Capacity and Coverage Optimization Cumulative Distribution Function Cell Outage Compensation Element Manager evolved NodeB Energy Saving Management Evolved Universal Terrestrial Radio Access Network Handover HandOver parameter Optimization Inter Cell Interference Coordination Information Object Class Load Balancing Load Balancing Optimization Mobility Robustness Optimisation Network Manager Network Resource Model Operation Administration Maintenance RACH Optimization Self Organizing Networks User Equipment 3GPP
  • 9. Release 11 9 3GPP TS 32.522 V11.6.1(2013-06) 4 SON Policy and Optimization Function Definitions 4.1 Monitoring and Management Operations for SelfOptimization 4.1.1 Monitoring and Management Function 4.1.1.1 Usage of Itf-N For specifically defined Itf-N NRM Interface see clause 5. 4.2 Load Balancing Optimization Function 4.2.1 Objective and Targets The objective of LB Optimization is to cope with undesired traffic load distribution and to minimize the number of handovers and redirections needed to achieve the load balancing. One of the following targets or the combination of the following targets shall be used. The specific target value or values shall be configured by operators. Operators should assign weights for targets being used. Targets drawn from the following table can be configured for LBO: Target Name RRC connection establishmentsfailure rate related to load Definition The number of Failed RRC connection establishments related to load/ The total number of Attempted RRC connection establishments. E-RAB setup failure raterelated to load The target is met if the actual rate is smaller than the target value. The number ofE-RABsetup failure related to load/ The total number of attempted E-RABsetup Legal Values Integer [0..100] in unit percentage Integer [0..100] in unit percentage For E-RAB setup failure related to load, the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 [12] could be used. RRCConnectionAbn ormalReleaseRateR elatedtoLoad ERABAbnormalReleas eRateRelatedtoLoad The target is met if the actual rate is smaller than the target value. The number of abnormal RRC connection release related to load/ The total number of RRC connection release. The target is met if the actual rate is smaller than the target value. The number ofE-RABabnormal release related to load/ The total number of E-RABrelease Integer [0..100] in unit percentage Integer [0..100] in unit percentage For E-RAB setup failure related to load, the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 [12] could be used. Rate of failures related to handover The target is met if the actual rate is smaller than the target value. (the number of failure events related to handover) / (the total number of handover events) Integer [0..100] in unit percentage The target is met if the actual rate is smaller than the target value. For the following targets out of the above table, the target values depend on the composite available capacity range in the cell and are defined separately for uplink and downlink. For these tuples can be configured, indicating the capacity ranges together with the target value valid in that range. 3GPP
  • 10. Release 11 10 3GPP TS 32.522 V11.6.1(2013-06) RRC connection establishments failure rate related to load, E-RAB setup failure rate related to load, RRC Connection Abnormal Release Rate Related to Load, E-RAB Abnormal Release Rate Related to Load For the following targets shall be identical with the corresponding targets defined in Handover Optimization. Rate of failures related to handover 4.2.2 Parameters To Be Optimized To reach load optimization target, LBO may optimize some mobility settings (HO and/or idle mobility configuration) defined in TS 36.331 [6]. 4.2.3 Optimization Method 4.2.3.1 Problem Detection The problem detection is out of scope of this specification. 4.2.3.2 Problem Solution The problem solution is out of scope of this specification. 4.2.4 4.2.4.1 Architecture Definition of Logical Functions LB Monitor Function: This function is used for monitoring the load balance optimization (e.g. Monitoring related performance counters or alarms). LB Policy control function: This function is used for configuring the load balance optimization policies. 3GPP
  • 11. Release 11 11 4.2.4.2 3GPP TS 32.522 V11.6.1(2013-06) Location of Logical Functions NM(IRPManager) LB Policy Control Function LB Monitor Function Itf-N DM LB Policy Control Function LB Monitor Function EM eNB LB decision algorithm X2 eNB X2 LB decision algorithm eNB EM LB decision algorithm For Load Balancing, the SON LB decision algorithm is located in eNB. The detailed SON functionalities in eNB are out of scope of this specification. 4.2.5 PM IRPManager may collect Load balancing related performance measurements. Performance Measurements related with Load balancing are captured in the table below: 3GPP
  • 12. Release 11 12 Performance measurement name The number of Failed RRC connection establishments related to load The total number of Attempted RRC connection establishments 3GPP TS 32.522 V11.6.1(2013-06) Description Relatedtargets Refer to 3GPP TS 32.425 [8] Failed RRC connection establishments Refer to 3GPP TS 32.425 [8] Attempted RRC connection establishments RRCconnection establishments failure rate related to load RRCconnection establishments failure rate related to load The number of E-RAB setup failure related to load Refer to 3GPP TS 32.425 [8] Number of initial SAE Bearers failed to setup E-RAB setup related to load failure rate The total number of attempted ERAB setup Refer to 3GPP TS 32.425 [8] Number of initial SAE Bearers attempted to setup Number of UE CONTEXT Release Request initiated by eNodeB E-RAB setup related to load failure rate Number of Successful Context Release RRC Connection Abnormal Release Rate Related to Load E-RAB Abnormal Release Rate Related to Load The number of abnormal RRC connection release related to load The total number connection release of RRC The number of E-RAB abnormal release related to load The total number of E-RAB release the number of failure events related to handover the total number of handover events NOTE: UE Refer to 3GPP TS 32.425 [8] Number of SAE Bearers requested to release initiated by eNodeB per cause Refer to 3GPP TS 32.425 [8] Number of SAE Bearers successfully released Refer to 4.3.5 Refer to 4.3.5 RRC Connection Abnormal Release Rate Related to Load E-RAB Abnormal Release Rate Related to Load Rate of failures related to handover Rate of failures related to handover The monitoring of performance measurements will make use of existing PM IRP. 4.3 Handover (HO) Parameter Optimization Function 4.3.1 Objective and Targets For intra-LTE, one of the following targets or the combination of the following targets shall be used. The specific target value shall be configured by operators. Operators should assign weights for targets being used. Target Name Rate of failures related to handover Definition (the number of failure events related to handover) / (the total number of handover events) Legal Values Integer [0..100] in unit percentage The target is met if the actual rate is smaller than the target value. The objective of minimizing the number of unnecessary handovers shall always be pursued in case the other target/s configured by the operator is/are achieved. This objective may not need configuration of a target value. 4.3.2 Parameters To Be Optimized The tables below summarise the handover parameters in TS 36.331 [6]. 3GPP
  • 13. Release 11 13 Table4.3.2-1. Event A3 A4 A5 Handover parameters that may be optimized for intra-frequency and inter-frequency handovers Summary Neighbour becomes offset better than serving Neighbour becomes better than threshold Serving becomes worse than threshold1 and neighbour becomes better than threshold2 Table4.3.2-2. Event B1 B2 3GPP TS 32.522 V11.6.1(2013-06) Tunable parameters Ofn, Ofs, Ocn, Ocs, Hys, Off, timeToTrigger Ofn, Ocn, Hys, Thresh, Off, timeToTrigger Ofn, Ocn, Hys, Thresh1, Thresh2, timeToTrigger Off, Handover parameters that may be optimised for inter RAT handover Summary Inter RAT Neighbour becomes better than threshold Serving becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2 4.3.3 Ofn, Hys, Thresh1, Thresh2, timeToTrigger Optimization Method 4.3.3.1 Tunable parameters Ofn, Hys, Thresh, timeToTrigger Problem Detection HO Parameter Optimization Function shall focus on detecting the problem scenarios described in TS 32.521 [5]; namely: too early handovers, too late handovers and inefficient use of NW resources due to HOs. For more information about these scenarios see TS 32.521 [5] section 6.1.3. The following inputs may be used for the identification of the problem scenarios: - Event capture and analysis - UE measurements - Performance measurements In event capture and analysis, the eNodeB exploits event information associated with a UE context, such as evidence of previous handovers (UE History, see TS 36.423 [7]) and HO failure details (such as in which cell the handover failed and where the UE re-established the connection). UE measurements are sent within UE measurement reports and they may indicate whether HOs are too early or too late. HO-related performance measurements (PMs) collected at the source and / or target eNB can be useful in detecting HOrelated issues on the cell level. Since the impact of incorrect HO parameter setting will also be on the cell-level, PMs can provide useful information that can be used to detect and resolve HO-related issues due to incorrect parameter settings. 4.3.3.2 Problem Solution HO Parameter Optimization Function will aim at optimizing the HO parameters listed in Section 4.3.2 in such way to mitigate the problem scenarios discussed in Section 4.3.3.1. The optimization algorithms will not be specified. The exact set of HO parameters that may be adjusted by the algorithms is dictated by the choice of triggered HO measurements made by the RRM entity in an eNodeB. 4.3.4 4.3.4.1 Architecture Definition of Logical Functions HO Parameter Optimization Monitor Function: This function is used for monitoring the handover parameter optimization (e.g. monitoring related performance counters or alarms). HO Parameter Optimization Policy Control Function: This function is used for configuring the handoverparameter optimization policies. 3GPP
  • 14. Release 11 4.3.4.2 14 3GPP TS 32.522 V11.6.1(2013-06) Location of Logical Functions For HandOver (HO) parameter optimization there are several options for the location of the SON algorithm: 1. The SON algorithm is located in the eNB(s). 2. The SON algorithm is located in the EM, the parameter changes are executed in the eNBs. An example for the first option is shown in figure 4.3.4.2: NM HO Parameter Optimization Policy Control Function HO Parameter Optimization Monitor Function Itf-N DM HO Parameter Optimization Policy Control Function HO Parameter Optimization Monitor Function EM eNB eNB X2 HO Parameter Optimization algorithm HO Parameter Optimization algorithm eNB X2 EM HO Parameter Optimization algorithm Figure 4.3.4.2: Example when the SON algorithm is located in the eNB(s) The detailed SON functionalities in eNB are out of scope of this specification. 4.3.5 PM IRPManager shall collect HO-related performance measurements from the source and / or target eNB which can be useful in detecting HO-related issues on the cell level.The following input can be used for the identification of the problem scenarios specified: The number of RLF event happened within an interval after handover success. The number of unnecessary handovers to another RAT without RLF. Performance Measurements related to handover failure are captured in the table below. The Performance Measurements are for outgoing handovers. Further, they should be available on a cell relation basis. 3GPP
  • 15. Release 11 15 Performance measurement name Number of handover events Description Number of HO failures Includes successful handovers plus all identified failures All failure cases Number of too early HO failures Too early HO failure cases Number of too late HO failures Too late HO failure cases Number of HO failures to wrong cell Number of unnecessary HOs to another RAT HO failuresto wrong cell NOTE: 3GPP TS 32.522 V11.6.1(2013-06) Related targets Rate of failures handover Rate of failures handover Rate of failures handover Rate of failures handover Rate of failures handover related to related to related to related to related to Unnecessary HOs to each of different RATs The monitoring of performance measurements will make use of existing PM IRP. 4.4 Interference Control Function 4.5 Capacity and Coverage Optimization Function 4.5.1 Objective and Targets The objective of capacity and coverage optimization is to provide optimal coverage and capacity for the radio network. A tradeoff between capacity and coverage needs to be considered. The detailed target(s) FFS. 4.5.2 Parameters to be optimized To reach capacity and coverage optimization targets, the following parameters may be optimized: Downlink transmit power Antenna tilt Antenna azimuth 4.5.3 Optimization Method 4.5.3.1 ProblemDetection The main symptoms ofcapacity and coverage optimizationproblems (see TS 37.320 [15]) are: Coverage hole: A coverage hole is an area where the pilot signal strength is below a threshold which is required by a UE to access the network, or the SINRs of both serving and neighbor cells is below a level needed to maintain the basic service.Coverage holes are usually caused by physical obstructions such as new buildings, hills, or by unsuitable antenna parameters, or just inadequate RF planning. UE in coverage hole will suffer from call drop and radio link failure. Typical phenomenon of coverage hole is either HO failure happens frequently and cannot be optimized by HO parameter optimization or call drop happens frequently and cannot be rescued by RRC re-establishment. Weak coverage: Weak coverage occurs when the pilot signal strength or the SNR (or SINR) of serving cell is below the level needed to maintain a planned performance requirement (e.g. cell edge bit-rate). Pilot pollution: In areas where coverage of different cells overlap a lot, interference levels are high, power levels are high, energy consumption is high and cell performance may be low. Typically in this situation UEs may experience high SNR to more than one cell and high interference levels. Overshoot coverage: Overshoot occurs when coverage of a cell reaches far beyond what is planned. It can occur as an “island” of coverage in the interior of another cell, which may not be a direct neighbor. Reasons for overshoot may be reflections in buildings or across open water, lakes etc. UEs in this area may suffer call drops or high interference. 3GPP
  • 16. Release 11 16 3GPP TS 32.522 V11.6.1(2013-06) DL and UL channel coverage mismatch:DL channel coverage is larger than UL channel coverage is one typical scenario of DL and UL channel coverage mismatch. The UE will suffer UL problems when it moves into the mismatch area. In a realistic network, these symptoms may be tolerated to a certain level. These symptoms may indicate a real problem when combined with other factors such as frequency of symptoms, duration of symptoms, or affected population. The following inputs may be used for the identification of the problem scenarios: UE measurements Performance measurements Alarms, other monitoring information e.g. trace data UE measurements are sent within UE measurement reports and they may indicate the capacity and coverage problem. Capacity and coverage related performance measurements collected at the source and / or target eNB can be useful in detecting capacity and coverage related issues on the cell level. Minimizing Driver Test (MDT) or HO-related performance measurements may be usedalso in detecting capacity and coverage related issues on the cell level. Alarms, othermonitoring information e.g. trace data can be correlated to get an unambiguous indication of capacity and coverage problem. 4.5.3.2 Problem Solution Capacity and coverageoptimization function will aim at optimizing the parameters listed in Section 4.5.2 in such way to mitigate the problem scenarios discussed in Section 4.5.3.1. 4.5.4 Architecture 4.5.4.1 Definition of Logical Functions CCO Monitor Function: This function is used for monitoring the capacity and coverage optimization (e.g. monitoring related performance counters, UE measurements or alarms). CCO Policy Control Function: This function is used for configuring the capacity and coverageoptimization policies. 4.5.4.2 Location of Logical Functions For capacity and coverage optimization (CCO), there are several options for the location of the centralized CCO SON algorithm: 1. The CCO SON algorithm is located in the DM. The capacity and coverage optimization decision is made by the DM centralized CCO algorithm. 2. The CCO SON algorithm is located in the NM.The capacity and coverage optimization decision is made by the NM centralized CCO algorithm. An example for the first option is shown in figure 4.5.4.2: 3GPP
  • 17. Release 11 17 3GPP TS 32.522 V11.6.1(2013-06) NM CCO Policy Control Function CCO Monitor Function Itf-N DM CCO Policy Control Function CCO Monitor Function CCO Algorithm EM eNB X2 X2 eNB eNB EM Figure 4.5.4.2: Example when the CCO SON algorithm is located in DM The detailed CCO SON algorithm in OAM (NM centralized or EM centralized) is out of scope of this specification. 4.5.5 PM The IRPAgent shall support a capability allowing the IRPManagerto collect CCO related performance measurements to know the situation of coverage or interference which may then trigger corresponding optimization procedures. Performance measurements related with CCO are captured in the table below: Performance measurement name Maximum carrier transmit power Mean carrier transmit power Description Comment Refer to 3GPP TS 32.425 [8] Maximum value of the total carrier power transmitted in a cell. Refer to 3GPP TS 32.425 [8] Mean value of the total carrier power transmitted in a cell. 4.6 RACH Optimization Function 4.6.1 Objective and Targets The objective of RACH Optimization is to automatically set several parameters related to the performance of RACH. One of the following targets shall be used. The specific target value shall be configured by operators. 3GPP
  • 18. Release 11 18 3GPP TS 32.522 V11.6.1(2013-06) Target Name Access Probability, AP Definition The probability that the UE has access after a certain random access attempt number. Legal Values CDF of access attempts. See section 5.5.1 Access Delay Probability,ADP The target is met if the actual access probability is higher than the target probability value. The probability distribution of Access Delay expected to be experienced by UEs accessing the RACH Channel. CDF of delays. See section 5.5.1 The target is met if the actual access probability is higher than the target probability value. 4.6.2 Parameters to be optimized To achieve RACH optimization target, RACH optimization function may optimize several parameters defined in TS 36.300 [14] section 22.4.3. 4.6.3 Optimization Method 4.6.3.1 ProblemDetection The problem detection is out of scope of this specification since theRACH optimization entity resides in the eNB. 4.6.3.2 Problem Solution The problem solution is out of scope of this specification since the RACH optimization entity resides in the eNB. 4.6.4 PM The IRPAgent shall support a capability allowing the IRPManagerto collect RACH optimization related performance measurements. Performance measurements related with RACH optimization are captured in the table below: Performance measurement name Distribution of RACH preambles sent Distribution of RACH access delay 4.7 Refer to 3GPP TS 32.425 [8] Cumulative Distribution of RACH preambles sent by UE Refer to 3GPP TS 32.425 [8] Cumulative Distribution of RACH Access Delay Related targets Access Probability, AP Access Delay Probability, ADP SON coordination 4.7.1 Description Introduction There may be conflicts or dependencies between SON functions; SON coordination means preventing or resolving conflicts or negative influences between SON functions to make SON functions comply with operator’s policy. As the example shown in figure 4.7.1.1, there is mesh relationship between SON functions and network parameters (or network elements) in which conflicts or negative influences may happen if no SON coordination. 3GPP
  • 19. Release 11 19 SON functions Network parameters and/or elements CCO Antenna Para (Tilt, Azimuth) COC 3GPP TS 32.522 V11.6.1(2013-06) ES Cell switch on/off HOO Downlink TX Power LBO Handover Parameters Legend: RF related RRM related Figure 4.7.1.1: Mesh relationshipbetween SON functions and network parameters (or network elements) 4.7.2 Coordination between SON functions below Itf-N and non-SON CM operations over itf-N 4.7.2.1 Description Conflict may arise between non-SON CM operation via Itf-N and the SON functions (in particularly self-optimization function) below Itf-N in the following scenario. The network parameters can be changed by the non-SON CM operations via Itf-N,meanwhile, the SON functions below Itf-N may also require changing the parameters. If these parametersare some (same or associated) parameters of some (same or associated) nodes which will be changed by the non-SON CM operations and the SON functions below Itf-N, conflict arises. (Conflict see clause 4 of 32.521[5]) For example, the non-SONCM operation via Itf-N may try to reduce the CIO (cell individual offset) parameter, it makes the HO trigger between cells (e.g., HO from cell A to cell B) become more difficult. But in the meanwhile, the SON function MRO may try to increase the CIO parameter, it makes the HO easier. In this case, if the conflict is not coordinated, the parameter may be modified twice. Then the failed rate related with handover may rise or ping-pong handover may arise between the two cells. In case the SON function below Itf-N and non-SON CM operation via Itf-N has conflict, the SON function below Itf-N shall take into account and re-evaluate, if applicable, any non-SON CM operation changes via Itf-N. As showing in the following example, At Time T3, after Non-SON operation has finished the modification, SON function below Itf-N shall take the non-SON CM operation changes into account for further SON analysis. 3GPP
  • 20. Release 11 20 3GPP TS 32.522 V11.6.1(2013-06) NonSON operati on over Itf-N T2 Modify (same or associated) parameters of (same or T1 Modify associated) nodes SON functions below ItfN T3 Reanalysis Time SON functions below ItfN 4.7.2.2 Prevention In a real network, it is possible that non-SON CM operations via Itf-N and several SON functions below Itf-N are running at the same time, and they may try to change the same or associated parameters during a short time period. So coordination is needed to prevent this kind of conflicts. 4.7.2.3 Resolution Refer to common coordination solutions part. 4.7.3 Coordination between different SON functions Note: The coordination between different SON functions should be decided case by case. 4.7.3.1 4.7.3.1.1 Coordination between Cell Outage Compensation and Energy Saving Management Description A conflict could arise between energy saving and cell outage compensation in the following scenario. One or more candidate cells are configured to possibly take coverage of the original cell. The original cell is in energySaving state or is about to enter energySaving state. One or more candidate cells go into outage with the consequence that coverage of the original cell cannot be provided any more. 4.7.3.1.2 Prevention Prevention is hardly possible, except making the cells as outage proof as possible. But cell outages can happen even to the most stable cell in a network. 4.7.3.1.3 Resolution If the original cell is in energySaving state, it shall leave energySaving state. If the original cell is about to enter energySaving state, it shall not go into energySaving state until candidate cell outage is recovered and candidate cell is able to provide the coverage. The original cellmaygo into the energySaving state after the candidate cell outage is recovered and coverage of the original cell can be taken over by candidate cell again. 3GPP
  • 21. Release 11 4.7.3.2 4.7.3.2.1 21 3GPP TS 32.522 V11.6.1(2013-06) Coordinationamong Cell Outage Compensation,Capacity and Coverage Optimization, and Energy Saving Management Description Capacity and Coverage Optimization (CCO), Cell Outage Compensation (COC) and Energy Saving Management (ESM) may require changes to the coverage and/or capacity ofone or more cells during the same time period, which couldlead to the following issue: Cell3 Cell1 Cell2 Cell4 Figure 4.7.3.2 Coordination among COC, CCO, and ESM Figure 4.7.3.2 is a typical scenario for the coordination among COC, CCO and ESM. Cell 1 is detected in outage, COC will try to compensate the outage Cell 1 by reconfiguring the RF configuration of some compensation candidate cells, e.g., TX power, antenna tilt and antenna azimuth of Cell 2 and Cell 3. Before the outage Cell 1 is compensated, CCO may detect the degrading of coverage related KPI (e.g., success rate of RRC connection establishments, cell throughput) of Cell 1 and its neighbour cells (Cell 2 and other blue cells) and make a conclusion that there is a coverage problem in this KPI degraded area. Meanwhile, ESM is operating on Cell 2 to compensate the coverage of its neighboring cell (Cell 4) which is going into energySaving state. From the time point at which the outage Cell 1 is detected until Cell 1 has been compensated by Cell 2 and Cell 3, during this period, if there is no coordination among COC, CCO and ESM, there will be possibly different settings for adjusting TX power, antenna tilt and antenna azimuth of Cell 2 for COC, CCO or ESM purposes respectively.It’s most likely that the adjustment from COC, ESM and optimization from CCO may conflict in the common affected outage compensation candidate cell(s) (Cell 2 in the above example). It is also possible that ESM is operating on Cell 2 to compensate the coverage of Cell 4 that is in energySaving state, while COC detects that Cell 1 has outage, and requests Cell 2 to compensate the coverage of Cell 1. COC and ESM need to be coordinated to determine if this request can be accepted. After the outage cell comes back to normal, the COC exits the coordination scenario, while CCO and ESM continute to work and need to be well coordinated. For example, CCO may adjust the antenna tilt of Cell 2 in a downward direction to improve the coverage signal quality, but ESM may adjust the antenna tilt of Cell 2 in an opposite direction to enlarge its coverage area for purpose of ES compensation. Therefore, coordination should be continued between CCO and ESM to resolve the possible configuration conflict on Cell 2. Other conflict scenarios could be: Cell A is compensating to provide coverage for Cell B that is in energySaving state. COC detects that Cell A has outage. Since Cell A is not able to provide the coverage for Cell B any more, Cell B needs to be covered by another cell, or to deactivate energy saving. Cell A is in energySaving state. COC detects Cell B has outage, and requests Cell A to compensate the coverage of Cell B. Cell A may need to terminate energy saving in order to compensate the coverage of Cell B. 3GPP
  • 22. Release 11 22 3GPP TS 32.522 V11.6.1(2013-06) Cell A which is compensating Cell B in outage shall not go into energySaving state as long as its compensation for Cell B is needed. 4.7.3.2.2 Prevention Prevention is hardly possible. 4.7.3.2.3 Resolution Refer to clause 4.7.4 General SON coordination solutions. 4.7.3.3 4.7.3.3.1 Coordination between Cell Outage Compensation and Automatic NeighbourRelation Description In case one cell is detected in outage, COC will try to compensate the outage cell by reconfiguring the RF configuration of some compensation candidate cells. As a result of this, there will be new NRs (neighbour relations) which reflect the new topology relations. For a stable network, ANR could be deactivated for the purpose of system resource saving. If ANR is deactivated, the new NRs cannot be captured in NRT by ANR. Network performance, for example, handover will be impacted negatively by the NRT which lacks of the new NRs. 4.7.3.3.2 Prevention Prevention is hardly possible, except making the cells as outage proof as possible. But cell outages can happen even to the most stable cell in a network. 4.7.3.3.3 Resolution The ANR function should monitor if a cell outage or cell outage compensation takes place within its area. If this happens, then the ANR function should check the NRs of the affected cells (for example the outage cell and its neighbours and neighbours’ neighbours). In case the ANR function in the the affected areais deactivated, the possible NRs change of the affected cellsshould be taken as a factor toreactivate the ANR function. 4.7.3.4 4.7.3.4.1 Coordination between HandOver parameter Optimization and Load Balancing Optimization Description HOO function and LBO function both optimize network performance by adjusting handover parameters such as CIO, Hysteresis, TTT, etc. Conflicts may happen when HOO function and LBOfunction are changing the same or associated handover parameters in opposite direction or towards the same direction but on different scales. For example, HOO function may adjust handover parameters (e.g. decrease CIO of source cell A to target cell B) to minimize the number of too early handovers from cell A to cell B whilst LBO function may adjust handover parameters (e.g. increase the CIO of source cell A to target cell B) to make the handover from cell A to cell B more easier in case the load of cell B is much less than cell A. 4.7.3.4.2 Prevention Prevention is hardly possible unless switch off HOO function or LBO function. However, disabling the complete HOO function or LBO function cannot fulfil the requirement that both handover performance and load performance need to be improved at the same time. 4.7.3.4.3 Resolution For the coordination between HOO and LBO, IRPManager should assign priorities for HOO function and LBO function or weights for targets of HOO function and LBO function according to operator’s policy. The policy should cover different scenarios well: 3GPP
  • 23. Release 11 23 3GPP TS 32.522 V11.6.1(2013-06) Policy may assign higher priority for HOO function than LBO function or higher weight for target of HOO function than targets of LBO function when resolving MRO issues (HO too early/too late/to wrong cell) is the main objective of network optimization, e.g. in handover optimization scenario for better coverage. Policy may assign lower priority for HOO function than LBO function or lower weight for target of HOO function than targets of LBO function when enhancing load performance is the main objective of network optimization, e.g. in load optimization scenario for better capacity. Concrete way of using priority or weights of targets, refers to clause 4.7.4 General SON coordination solutions. 4.7.4 4.7.4.1 General SON coordination solutions Overview As described in TS 32.521 [5], multiple SON functions may have conflicting demands on network resources. This situation is considered as “SON functions in conflict” and requires conflict prevention or resolution. A SON Coordination Function will be responsible for preventing or resolving conflicts. Conflict needs to be detected when there is “SON functions in conflict”. Policies can be preset by operator to SON Coordination Function to avoid conflict on certain associated resources (network elements and/or parameters) among SON functions. Conflict prevention is to take some advanced methods to prevent the occurrence of conflict. However, no matter what implementation is chosen, it is impossible to guarantee that 100% of conflicts will be prevented, so conflict detection and resolution are needed. Conflict detection should be taken firstly as the pre-condition of conflict resolution. The SON Coordination Function is a logical function, which means it can be implemented as a separate function entity or as part of SON function. When the SON Coordination Function is implemented as a separate function entity, all the SON functions send the necessary information to the SON Coordination Function, the SON Coordination Function coordinate these SON functions as a centralized control point. This centralized coordination approach fulfills the requirements of SON coordination in a large area scope, for example, the coordination between NM centralized SON functions and distributed SON functions. In some other situations, coordination is only needed in a smaller area, for example, the coordination between distributed SON functions inside one domain. Then the SON Coordination Function can be implemented as part of each SON function. The necessary coordination information can be inter-exchanged between each SON functions to achieve coordination as well. The SON Coordination Function may reside above or below Itf-N. Figure 4.7.4.1 shows an example of a SON Coodination Function, which is a separate function entity, above Itf-N. 3GPP
  • 24. Release 11 24 NM SON Coordination Function 3GPP TS 32.522 V11.6.1(2013-06) SON_X Itf-N EM SON_Y eNB SON_A eNB SON_B EM eNB SON_C Figure 4.7.4.1: Example of SON Coordination entity located in NM The SON Coordination Function may be responsible for conflict prevention, conflict resolution, or both in parallel. 4.7.4.2 Conflict prevention To prevent conflicts between the SON functions, the SON functions may ask the SON Coordination function for permission before changing some specific configuration parameters. The SON Coordination Function should check the SON coordination interdependancy policy between this requesting SON function and other SON function(s) upon receiving the permission request from the SON function. SON coordination interdependancy policy which is preconfigured can help the SON Coordination Function to find which SON function(s)possibly conflict with this requesting SON function. As a basis for decisions, the SON Coordination Function will typically use one or some of the following inputs received from the SON function(s) Which SON functions are modifying configuration parameters (including information about vendor, release etc.) Configuration parameters intended to be changed and/or their existing and proposed new values The time duration how long the configuration parameter should not be interfered with (“impact time”) The state of SON functions The SON targets which are the justification for the configuration change. Possible impact of a parameter change on other objects (“impact area”) The state of certain managed objects Possible impact of the parameter change on Key Performance Indicators Priority of SON functions, which can be used to determine the execution order of requests from different SON functions in case of conflicts SON coordination policies 3GPP
  • 25. Release 11 25 3GPP TS 32.522 V11.6.1(2013-06) The SON Coordination Function sends the decision back to the requesting SON function; the decision may be confirmation or suspension or rejection of the SON executing request, or other actions like configuration of specific parameters with specific value. After SON function executes action, the SON Coordination Function is then informed about the result (successful/unsuccessful, parameters changes) of the executed SON action. The SON Coordination Function may prevent parameter changes by one or more SON functions for a specified time period after the same parameter has been changed by another SON function. The SON Coordination Function may inform a SON Function of a managed object state change which may impact calculation of KPIs. Detailed description of how to use general SON coordination solutions are in Annex B. 4.7.4.3 Conflict resolution The SON Coordination Function should detect conflicts and attempt to resolve the conflicts. To detect conflicts, the SON Coordination Function will typically analyse one or some of the following types of data Key Performance Indicatorswhich indicate if SON functions are meeting their targets or improving network performance Measurements which indicate if SON functions are meeting their targets or improving network performance Unacceptable oscillations in configuration parameters To resolve conflicts, the SON Coordination Function will typically use one or some of following methods Enabling/disabling/suspending certain SON functions Stopping/suspending/modifying certain SON actions Modifying certain configuration parameters 3GPP
  • 26. Release 11 26 3GPP TS 32.522 V11.6.1(2013-06) 5 Information Object Classes (IOCs) 5.1 Information entities imported and local labels Label reference 3GPP TS 32.622 [9], IOC, Top Top Local label 3GPP TS 32.622 [9], IOC, SubNetwork SubNetwork 3GPP TS 32.762 [10], IOC, ENBFunction ENBFunction 3GPP TS 32.762 [10], IOC, EUtranRelation EUtranRelation 3GPP TS 32.762 [10], IOC, EUtranGenericCell EUtranGenericCell 5.2 Class diagram 5.2.1 Attributes and relationships <<names>> <<InformationObjectClass>> SubNetwork 1 <<names>> <<names>> (from TS 32.622) 1 1 <<InformationObjectClass>> SONTargets 0..1 1 <<names>> 0..1 0..* <<InformationObjectClass>> SONControl XOR <<InformationObjectClass>> ManagedElement (from TS 32.622) 1 0..1 <<names>> <<names>> 0..* 1 <<InformationObjectClass>> ENBFunction <<names>> (from TS 32.762) 1 <<InformationObjectClass>> SONTargets 0..1 1 <<names>> 0..* <<InformationObjectClass>> EUtranGenericCell <<names>> (from TS 32.762) 1 <<InformationObjectClass>> SONTargets 0..1 NOTE 1: IOC SONControl shall be instantiated whenever one or more IOC SONTargets are instantiated. Figure 5.2.1-1: Cell view of SON Policy NRM 3GPP
  • 27. Release 11 27 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> ...>> Subnetwork 1 <<InformationObjectClass>> ...>> ESPolicies <<names>> (f rom TS 32.622) 0..1 1 1 <<names>> 0..* <<InformationObjectClass>> ...>> ManagedElement (f rom TS 32.622) 1 <<names>> 0..* <<InformationObjectClass>> ...>> ENBFunction (f rom TS 32.762) <<InformationObjectClass>> ESPolicies <<names>> 1 0..1 1 <<names>> 0..* <<InformationObjectClass>> ...>> EUtranGenericCell (f rom TS 32.762) <<InformationObjectClass>> ESPolicies <<names>> 1 0..1 Figure 5.2.1-2:ES Policies NRM IOCs (ContainmentRelationship) NOTE 2: Also IOC SONControl is used for intra-LTE ES purposes – see clause 5.3.2.2 – but is not shown in Figure 5.2.1-2 to avoid the impression that there would an additional instance of this IOC be needed for intraLTE ES. <<InformationObjectClass>> EUtranGenericCell (f rom TS 32.762) 1 0..1 <<InformationObjectClass>> EUtranCellSON Figure 5.2.1-3: IOCs to control SON on cell level (Containment Relationship) 3GPP
  • 28. Release 11 28 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ManagedElement (f rom TS 32.622) 1 <<names>> 0..n <<InformationObjectClass>> ENBFunction <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.762) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> EUtranGenericCell <<InformationObjectClass>> InterRatEsPolicies <<names>> (f rom TS 32.762) 1 0..1 Figure 5.2.1-4: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 1) NOTE 3: Also IOC SONControl is used for inter-RAT ES purposes – see clause 5.3.2.2 – but is not shown in Figure 5.2.1-4 to avoid the impression that there would an additional instance of this IOC be needed for inter-RAT ES. 3GPP
  • 29. Release 11 29 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork 1 (from TS 32.622) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ExternalENBFunction (from TS 32.762) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ExternalEUtranGenericCell (from TS 32.762) <<InformationObjectClass>> InterRatEsPolicies <<names>> 1 0..1 Figure 5.2.1-5: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 2) 3GPP
  • 30. Release 11 30 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass>> Subnetwork <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> ManagedElement (from TS 32.622) 1 <<names>> 0..n <<InformationObjectClass>> RncFunction <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.642) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> UtranGenericCell <<InformationObjectClass>> InterRatEs Policies <<names>> (from TS 32.642) 1 0..1 Figure 5.2.1-6: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 3) NOTE 4: Also IOC SONControl is used for inter-RAT ES purposes – see clause 5.3.2.2 – but is not shown in Figure5.2.1-6 to avoid the impression that there would an additional instance of this IOC be needed for inter-RAT ES. SONControl is contained by Subnetwork or RncFunction when esSwitch attribute is applied in SONControl. 3GPP
  • 31. Release 11 31 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass> > Subnetwork <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalRncFunction <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.642) 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalUtranGenericCell <<InformationObjectClass> InterRatEsPolicies > <<names>> (from TS 32.642) 1 0..1 Figure 5.2.1-7: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 4) 3GPP
  • 32. Release 11 32 <<InformationObjectClass>> ManagedElement 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.622) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> BssFunction (from TS 32.652) 1 <<names>> 0..n <<InformationObjectClass>> BtsSiteMgr <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.652) 1 0..1 1 <<names>> 0..n <<InformationObjectClass>> GsmCell <<InformationObjectClass>> InterRatEsPolicies <<names>> (from TS 32.652) 1 0..1 Figure 5.2.1-8: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 5) 3GPP
  • 33. Release 11 33 3GPP TS 32.522 V11.6.1(2013-06) <<names>> <<InformationObjectClass> > Subnetwork <<InformationObjectClass> > InterRatEsPolicies <<names>> (from TS 32.622) 1 1 0..1 1 <<names>> 0..n <<InformationObjectClass> > ExternalBssFunction (from TS 32.652) 1 <<names>> 0..n <<InformationObjectClass> ExternalGsmCell > <<InformationObjectClass> InterRatEsPolicies > <<names>> (from TS 32.652) 1 0..1 Figure 5.2.1-9: Inter-RAT ES Policies NRM IOCs (ContainmentRelationship, part 6) 3GPP
  • 34. Release 11 34 3GPP TS 32.522 V11.6.1(2013-06) Figure 5.2.1-10: IOCs for SON coordination (Containment Relationship) 5.2.2 Inheritance <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> <<InformationObjectClass>> SONTargets SONControl Figure 5.2.2-1: SON Policy NRM Inheritance Hierarchy 3GPP
  • 35. Release 11 35 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> Top (f rom TS 32.622) <<InformationObjectClass>> ESPolicies <<InformationObjectClass>> InterRatEsPolicies Figure 5.2.2-2:ES PolicesNRM IOCs (Inheritance Relationship) <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> EUtranCellSON Figure 5.2.2-3: Inheritance for IOC to control SON on cell level <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass> > EnergySavingProperties Figure 5.2.2-4: Energy saving propertiesNRM IOCs (Inheritance Relationship) 3GPP
  • 36. Release 11 36 3GPP TS 32.522 V11.6.1(2013-06) <<InformationObjectClass>> Top (from TS 32.622) <<InformationObjectClass>> SONFuncInfo <<InformationObjectClass>> SONCoordinationPolicies Figure 5.2.2-5: IOCs for SON coordination (Inheritance Relationship) 5.3 Information Object Class (IOC) definitions 5.3.1 SONTargets 5.3.1.1 Definition This IOC represents targets for SON functions and their relative weights. Target hierarchy rule: An NRM IOC instance X may name-contain an IOC SONTargets instance T. The rule states that: - If X name-contains a SONTargets instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONTargets instance, then no SONTargets instance is applicable to X. - If X does not name-contain any SONTargets instance, but one or more of X’s superior instances name-contain a SONTargets instance, then the SONTargets instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.1.2 Attributes Attribute name hoFailureRate rrcConnectionEstablishmentFailureRateCharacteristic rrcConnectionAbnormalReleaseRateCharacteristic eRabSetupFailureRateCharacteristic eRabAbnormalReleaseRateCharacteristic rachOptAccessProbability rachOptAccessDelayProbability *) Note 1: At least one of the attributes shall be supported. **) Note 2: Only one of these attributes shall be present. 3GPP Support Qualifier O *) O *) O *) O *) O *) CM **) CM **) Read Qualifier M M M M M M M Write Qualifier M M M M M M M
  • 37. Release 11 5.3.1.3 37 Attribute constraints Name rachOptAccessProbability CM Support Qualifier rachOptAccessDelayProbability CM Support Qualifier 5.3.1.4 3GPP TS 32.522 V11.6.1(2013-06) Definition RACH Optimization is supported and Access Probability is supported as target. RACH Optimization is supported and Access Delay Probability is supported as target. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.2 SONControl 5.3.2.1 Definition This IOC represents the possibility to switch on or off SON functions. This is provided for Handover parameter optimization, Load Balancing optimization, Energy Saving, RACH optimization and Cell Outage Compensation. 5.3.2.2 Attributes Attribute name hooSwitch lboSwitch esSwitch roSwitch cocSwitch 5.3.2.3 Support Qualifier CM CM CM CM CM Write Qualifier M M M M M Attribute constraints Name hooSwitchCM Support Qualifier lboSwitchCM Support Qualifier esSwitch Support Qualifier roSwitch CM Support Qualifier cocSwitch Support Qualifier 5.3.2.4 Read Qualifier M M M M M Definition Handover (HO) parameter Optimization function is supported. Load Balancing Optimization function is supported. The condition is “Distributed or EM-Centralized ESM architecture is supported”. RACH Optimization is supported. The condition is “CoC is supported”. Only allowed to be present, if SONControl is contained in subnetwork IOC instance. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.3 5.3.3.1 ESPolicies Definition This IOC represents the energy saving policies information. This object class is valid in a distributed ES architecture or in an EM-centralized ES architecture. 5.3.3.2 Attributes Attribute name esActivationOriginalCellLoadParameters esActivationCandidateCellsLoadParameters esDeactivationCandidateCellsLoadParameters esNotAllowedTimePeriod 5.3.3.3 Support Qualifier CM CM CM O Attribute constraints 3GPP Read Qualifier M M M M Write Qualifier M M M M
  • 38. Release 11 38 Name esActivationOriginalCellLoadParameters esActivationCandidateCellsLoadParameters esDeactivationCandidateCellsLoadParameters 5.3.3.4 3GPP TS 32.522 V11.6.1(2013-06) Definition The condition is "Intra-RAT ESM is supported AND the cell acts as an original cell". The condition is "Intra-RAT ESM is supported AND the cell acts as a candidate cell". The condition is "Intra-RAT ESM is supported AND the cell acts as a candidate cell". Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.4 5.3.4.1 EUtranCellSON Definition This IOC represents the parameters for control of SON functions on E-UTRAN cell level. 5.3.4.2 Attributes Attribute name maximumDeviationHoTrigger minimumTimeBetweenHoTriggerChange 5.3.4.3 Read Qualifier M M Write Qualifier M M Attribute constraints Name maximumDeviationHoTrigger Support Qualifier minimumTimeBetweenHoTriggerChange Support Qualifier 5.3.4.4 Support Qualifier CM CM Definition The condition is "HOO function is supported". The condition is "HOO function is supported". Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.5 Void 5.3.6 EnergySavingProperties 5.3.6.1 Definition This IOC represents the energy saving properties of a network element supporting Energy Saving Management functionality. 3GPP
  • 39. Release 11 5.3.6.2 39 Attributes Attribute name energySavingState energySavingControl isProbingCapable 5.3.6.3 3GPP TS 32.522 V11.6.1(2013-06) Support Qualifier M CM O Read Qualifier M M M Write Qualifier M - Attribute constraints Name energySavingControl CM Support Qualifier Definition The condition is "ESM functionality supports and uses NMCentralized architecture". 5.3.6.4 Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC. Notification notifyAttributeValueChange shall be supported for attribute energySavingState. 5.3.7 5.3.7.1 interRatEsPolicies Definition This IOC represents the inter-RAT energy saving policies information. This object class is valid in a distributed ES architecture or in an EM-centralized ES architecture. 5.3.7.2 Attributes Attribute name interRatEsActivationOriginalCellParameters interRatEsActivationCandidateCellParameters interRatEsDeactivationCandidateCellParameters 5.3.7.3 Read Qualifier M M M Write Qualifier M M M Attribute constraints Name interRatEsActivationOriginalCellParame ters CM Support Qualifier interRatEsActivationCandidateCellParam eters CM Support Qualifier interRatEsDeactivationCandidateCellPar ameters CM Support Qualifier 5.3.7.4 Support Qualifier CM CM CM Definition The condition is "The cell acts as an original cell" AND inter-RAT ESM is supported. The condition is "The cell acts as a candidate cell" AND inter-RAT ESM is supported. The condition is "The cell acts as a candidate cell" AND inter-RAT ESM is supported. Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.8 IOC SONFuncInfo 5.3.8.1 Definition This IOC represents information of SON functions, to support SON coordination.In case of SON coordination function is located below Itf-N, this IOC is used together with SONCoordinationPolices IOC for SON coordination purpose. SONFuncInfo hierarchy rule: An NRM IOC instance X may name-contain an IOC SONFuncInfo instance T. The rule states that: - If X name-contains a SONFuncInfo instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONFuncInfo instance, then no SONFuncInfo instance is applicable to X. 3GPP
  • 40. Release 11 - 40 3GPP TS 32.522 V11.6.1(2013-06) If X does not name-contain any SONFuncInfo instance, but one or more of X’s superior instances name-contain a SONFuncInfo instance, then the SONFuncInfo instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.8.2 Attributes Attribute Name sonFuncCapabilityBelowItfN 5.3.8.3 Support Qualifier M Read Qualifier M Write Qualifier - Attribute constraints None. 5.3.8.4 Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.3.9 IOC SONCoordinationPolicies 5.3.9.1 Definition This IOC represents the SON coordination policies that are selected by IRPManagers from the IRPAgent supported policies in the case of a separate SON coordination function is located below Itf-N (i.e., EM centralized SON coordination) or SON coordination function is implemented as part of each SON function (i.e., distributed SON coordination). For EM centralized SON coordination case, the case that the SON function is located above Itf-N and the corresponding SON coordination function is below Itf-N is not in the scope of this release. This IOC is not intended to be used by IRPManager to create SON coordination policies that are not supported by IRPAgent. The selected SON coordination policies are used by SON coordination function to coordinate the SON functions with potential conflicts, in case no SON coordination policies are selected by IRPManager, the default SON coordination policies are applied to the SON coordination function below Itf-N; the default SON coordination policies are per agreement between IRPManager and IRPAgent, the value of the default SON coordination policies is out of the scope of this specification. SONCoordinationPolicies hierarchy rule: An NRM IOC instance X may name-contain an IOC SONCoordinationPolicies instance T. The rule states that: - If X name-contains a SONCoordinationPolicies instance T, then T is applicable to X. - If X and all its superior instances do not name-contain any SONCoordinationPolicies instance, then no SONCoordinationPolicies instance is applicable to X. - If X does not name-contain any SONCoordinationPolicies instance, but one or more of X’s superior instances name-contain a SONCoordinationPolicies instance, then the SONCoordinationPolicies instance of the superior instance closest to X, in X’s naming tree, is applicable to X. 5.3.9.2 Attributes Attribute Name selectedSonCoordPolicy sonFuncPriorityOrder 5.3.9.3 Support Qualifier CM CM Read Qualifier M M Write Qualifier M M Attribute constraints Name Definition selectedSonCoordPolicy CM Support Qualifier SON coordination function below Itf-N supports more than one coordination policy. sonFuncPriorityOrder CM Support Qualifier The selectedSonCoordPolicy “BaseOnPriority”. 3GPP equals to
  • 41. Release 11 5.3.9.4 41 3GPP TS 32.522 V11.6.1(2013-06) Notifications The common notifications defined in subclause 5.6.1 are valid for this IOC, without exceptions or additions. 5.4 Information relationship definitions None. 3GPP
  • 42. Release 11 42 5.5 Information attribute definitions 5.5.1 3GPP TS 32.522 V11.6.1(2013-06) Definition and legal values Table5.5.1.1 defines the attributes that are present in the Information Object Classes (IOCs) of the present document. Table 5.5.1.1: Attributes definitions and legal values Attribute Name cocSwitch energySavingCo ntrol energySavingSt ate Definition This attribute allows the operator to enable/disable the COC functionality. This attribute allows the IRPManager to initiate energy saving activation or deactivation. Its value can not be changed by the IRPAgent. Specifies the status regarding the energy saving in the cell. If the value of energySavingControl is toBeEnergySaving, then it shall be tried to achieve the value isEnergySaving for the energySavingState. If the value of energySavingControl is toBeNotEnergySaving, then it shall be tried to achieve the value isNotEnergySaving for the energySavingState. 3GPP Legal Values Enumerated {on, off} Enumerated {toBeEnergySaving, toBeNotEnergySaving}. Enumerated {isNotEnergySaving, isEnergySaving}.
  • 43. Release 11 eRabAbnormalRe leaseRateChara cteristic 43 3GPP TS 32.522 V11.6.1(2013-06) The target is on the number of E-RAB abnormal release related to load divided by the total number of attempted E-RABsetups. lowerEndOfCacRange and upperEndOfCacRange: Integer 0..10000 This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:eRabAbnormalReleaseRateCharacteris ticDownlink and eRabAbnormalReleaseRateCharacteristicU plink. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: eRabAbnormalReleaseRateCharacteristicD ownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, eRabAbnormalReleaseRateTarget eRabAbnormalReleaseRateCharacteristicU plink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, eRabAbnormalReleaseRateTarget Remark: Formula for composite available capacity: Available Capacity = Cell Capacity Class Value * Capacity Value For definition of Cell Capacity Class Value and Capacity Value see TS 36.331 [6]. These definitions lead to a value range of a composite available capacity from 0..10000. 36.423 [7] has cell capacity class value as optional parameter in case of intra-LTE load balancing. If cell capacity class value is not present, than 36.423 assumes that bandwidth should be used instead to assess the capacity. eRabAbnormalReleaseRateTarget: Integer 0..100 (representing a percentage) This target is suitable for LBO. 3GPP targetWeight: Integer 1..N. The higher the number the higher the weight.
  • 44. Release 11 eRabSetupFailu reRateCharacte ristic esActivationOr iginalCellLoad Parameters esActivationCa ndidateCellsLo adParameters 44 The target is on the number of E-RABsetup failures related to load divided by the total number of attempted E-RABsetups. For E-RAB setup failure related to load the causes “Reduce load in serving cell” and “Radio resources not available” defined in TS 36.413 are used. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:eRabSetupFailureRateCharacteristic Downlink and eRabSetupFailureRateCharacteristicUpli nk. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: eRabSetupFailureRateCharacteristicDown link: List of one or more entries, each consisting of: LowerEndOfCacRange, UpperEndOfCacRange, eRabSetUpFailureRateTarget eRabSetupFailureRateCharacteristicUpli nk: List of one or more entries, each consisting of: LowerEndOfCacRange, UpperEndOfCacRange, eRabSetUpFailureRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic This target is suitable for LBO. This attributes is relevant, if the cell acts as an original cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed ES algorithms to allow a cell to enter the energySaving state. The time duration indicates how long the load needs to have been below the threshold. This attributes is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed ES algorithms level to allow a n „original‟ cell to enter the energySaving state. Threshold and duration are applied tothe candidate cell(s)which will provides coverage backup of an original cell when it is in the energySaving state. The threshold applies in the same way for a candidate cell, no matter for which original cell it will provide backup coverage. The time duration indicates how long the traffic in the candidate cell needs to have been below the threshold before any original cells which will be provided backup coverage by the candidate cell enters energy saving state. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) lowerEndOfCacRange and upperEndOfCacRange and targetWeight: See eRabAbnormalReleaseRateCharacterist ic eRabSetUpFailureRateTarget: Integer 0..100 (representing a percentage) Threshold: Integer 0..100 (Percentage of PRB usage, see 3GPP TS 36.314 [13]) TimeDuration: Integer (in unit of seconds) Threshold: Integer 0..100 (Percentage of PRB usage (see 3GPP TS 36.314 [13]) ) TimeDuration: Integer (in unit of seconds)
  • 45. Release 11 esDeactivation CandidateCells LoadParameters 45 3GPP TS 32.522 V11.6.1(2013-06) Threshold: Integer 0..100 (Percentage of PRB usage (see 3GPP TS 36.314 [13]) ) TimeDuration: Integer (in unit of seconds) Time period is valid on the specified day and time of every week. esNotAllowedTi mePeriod This attributes is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration which is used by distributed ES algorithms to allow a cell to leave the energySaving state. Threshold and time duration are applied to the candidate cell when itwhich provides coverage backup for the cell in energySaving state. The threshold applies in the same way for a candidate cell, no matter for which original cell it provides backup coverage. The time duration indicates how long the traffic in the candidate cell needs to have been above the threshold to wake up one or more original cells which have been provided backup coverage by the candidate cell. This attribute can be used to prevent a cell entering energySaving state. This attribute indicates a list of time periods during which inter-RAT energy saving is not allowed. periodOfDay: structure of startTime and endTime. The legal values are as follows: startTime and endTime: All values that indicate valid UTC time. endTime should be later than startTime. daysOfWeekList: list of weekday. weekday: Monday, Tuesday, … Sunday. esSwitch hoFailureRate hooSwitch This attribute determines whether the energy saving function is enabled or disabled. This indicates the assigned HOO target of the number of failure events related to handover divided by the total number of handover events, together with its targetWeight. This target is suitable for HOO or LBO. This attribute determines whether the Handover parameter Optimization Function is activated or deactivated. 3GPP List of time periods: {{daysOfWeek daysOfWeekList, periodOfDay dailyPeriod}} On, off A set of two numbers: the first indicates a percentage, the second a targetWeight (see eRabAbnormalReleaseRateCharacterist ic). On, off
  • 46. Release 11 interRatEsActi vationOriginal CellParameters 46 This attribute is relevant, if the cell acts as an original cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed inter-RAT ES algorithms to allow an original cell to enter the energySaving state. The time duration indicates how long the traffic load (both for UL and DL) needs to have been below the threshold. 3GPP TS 32.522 V11.6.1(2013-06) InterRatESActivationOriginalCellParam eters: Structure: { LoadThreshold: Integer 0..10000 TimeDuration: Integer 0..900 (in unit of seconds) } In case the original cell is an EUTRAN cell, the load information refers to Composite Available Capacity Group IE (see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load = (100 - „Capacity Value‟ ) * „Cell Capacity Class Value‟, where„Capacity Value‟ and „Cell Capacity Class Value‟ are defined in 3GPP TS 36.423 [16]. In case the original cell is a UTRAN cell, the load information refers to Cell Load Information Group IE (see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load= „Load Value‟ * „Cell Capacity Class Value‟, where„Load Value‟ and „Cell Capacity Class Value‟ are defined in 3GPP TS 25.413 [17]. interRatEsActi vationCandidat eCellParameter s If the „Cell Capacity Class Value‟is not known, then „Cell Capacity Class Value‟ should be set to 1 when calculating the load, and the load threshold should be set in range of 0..100. This attribute is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration, which are used by distributed inter-RAT ES algorithms to allow an original cell to enter the energySaving state. Threshold and time duration are applied tothe candidate cell(s)which will provides coverage backup of an original cell when it is in the energySaving state. The time duration indicates how long the traffic load (both for UL and DL) in the candidate cell needs to have been below the threshold before any original cells which will be provided backup coverage by the candidate cell enters energySaving state. In case the candidate cell is a UTRAN or GERAN cell, the load information refers to Cell Load Information Group IE(see 3GPP TS 36.413 [12] Annex B.1.5) and the following applies: Load= „Load Value‟ * „Cell Capacity Class Value‟, where „Load Value‟ and „Cell Capacity Class Value‟ are definedin 3GPP TS 25.413 [17] (for UTRAN) / TS 48.008[18] (for GERAN). If the „Cell Capacity Class Value‟is not known, then „Cell Capacity Class Value‟ should be set to 1 when calculating the load, and the load threshold should be set in range of 0..100. 3GPP InterRatEsActivationCandidateCellPara meters: Structure { LoadThreshold: Integer 0..10000 TimeDuration: Integer 0..900 (in unit of seconds) }
  • 47. Release 11 interRatEsDeac tivationCandid ateCellParamet ers lboSwitch maximumDeviati onHoTrigger isProbingCapab le minimumTimeBet weenHoTriggerC hange 47 This attribute is relevant, if the cell acts as a candidate cell. This attribute indicates the traffic load threshold and the time duration which is used by distributed interRAT ES algorithms to allow an original cell to leave the energySaving state. Threshold and time duration are applied to the candidate cell which provides coverage backup for the cell in energySaving state. The time duration indicates how long the traffic load (either for UL or DL) in the candidate cell needs to have been above the threshold to wake up one or more original cells which have been provided backup coverage by the candidate cell. For the load see the definition of interRatEsActivationCandidateCellParameters. This attribute determines whether the Load Balancing Optimization Function is activated or deactivated. This parameter allows the IRPManager to define the maximum allowed absolute deviation of the cell pair specific part of Handover Trigger (as defined in [14] (§22.4.1.4), from the default point of operation This attribute indicates whether this cell is capable of performing the ES probing procedure. During this procedure the eNB owning the cell indicates its presence to UEs for measurement purposes, but prevents idle mode UEs from camping on the cell and prevents incoming handovers to the same cell. If this parameter is absent, then probing is not done. This parameter defines the minimum allowed time interval between two changes of the Handover Trigger performed by MRO. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) InterRatEsDeactivationCandidateCellPa rameters: See InterRatEsActivationCandidateCellPara meters On, off Integer (+1..+96) Unit: 0.5 dB Boolean Integer (0..1440) Unit: Minutes
  • 48. Release 11 rachOptAccessD elayProbabilit y 48 This is a list of target Access Delay probability (ADP) for the RACH optimization function. Each instance ADP of the list is the target time before the UE gets access on the random access channel, for the P percent of the successful RACH Access attempts with lowest access delay, over an unspecified sampling period. Each element of the list, ADPn, is a pair (a, b) where a is the targetProbability (in %) and b is the access delay (in milliseconds). The legal values for a are 25, 50, 75, 90. The legal values for b are 10 to 560. If ADPx‟s a is larger than that of ADPy, then ADPx‟sb must be larger than that of ADPy. This target is suitable for RO. rachOptAccessP robability 3GPP TS 32.522 V11.6.1(2013-06) This is a list of target Access Probability (APn) for the RACH optimization function. Each instance APn of the list is the probability that the UE gets access on the random access channel within n number of attempts, over an unspecified sampling period. The number of elements specified is 4. The number of elements supported is vendor specific. The choice of supported values for a and b is vendorspecific. Each element of the list, APn, is a pair (a, n) where a is the targetProbability (in %) and n is the access attempt number. The legal values for a are 25, 50, 75, 90. The legal values for n are 1 to 200. If APx‟s a is larger than that of APy, then APx‟s n must be larger than that of APy. This target is suitable for RO. The number of elements specified is 4. The number of elements supported is vendor specific. The choice of supported values for a and n is vendorspecific. roSwitch This attribute determines whether the RACH Optimization function is activated or deactivated. 3GPP On, off
  • 49. Release 11 rrcConnectionA bnormalRelease RateCharacteri stic 49 The target is on the number of abnormal RRC connection releases related to load divided by the total number of RRC connection releases. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:rrcConnectionAbnormalReleaseRateCh aracteristicDownlink and rrcConnectionAbnormalReleaseRateCharac teristicUplink. At least one of these charateristics must be present. Together with the characteristic its targetWeight as a SON target is defined as part of this attribute. The characteristics have the following structure: rrcConnectionAbnormalReleaseRateCharac teristicDownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionAbnormalReleaseRateTarget rrcConnectionAbnormalReleaseCharacteri sticUplink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionAbnormalReleaseRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic rrcConnectionE stablishmentFa ilureRateChara cteristic This target is suitable for LBO. The target is on the number of RRC connection establishment failures related to load divided by the total number of attempted RRC connection establishments. This attribute allows to define for a value the composite available capacity (CAC) range in which the target is valid. For this, it contains onecharacteristic dependent on Uplink CAC, one for Downlink CAC:rrcConnectionEstablishmentFailureR ateCharacteristicDownlink and rrcConnectionEstablishmentFailureRateC haracteristicUplink. At least one of these charateristics must be present. Together with the characteristic its targetWeigth as a SON target is defined as part of this attribute. The characteristics have the following structure: rrcConnectionEstablishmentFailureRateC haracteristicDownlink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionEstablishmentFailureRateTarget rrcConnectionEstablishmentFailureRateC haracteristicUplink: List of one or more entries, each consisting of: lowerEndOfCacRange, upperEndOfCacRange, rrcConnectionEstablishmentFailureRateTarget For CAC see eRabAbnormalReleaseRateCharacteristic This target is suitable for LBO. 3GPP 3GPP TS 32.522 V11.6.1(2013-06) lowerEndOfCacRange and upperEndOfCacRange and targetWeight: See eRabAbnormalReleaseRateCharacterist ic rrcConnectionAbnormalReleaseRateTar get: Integer 0..100 (representing a percentage) lowerEndOfCacRange and upperEndOfCacRange and targetWeigth: See eRabAbnormalReleaseRateCharacterist ic rrcConnectionEstablishmentFailureRate Target: Integer 0..100 (representing a percentage)
  • 50. Release 11 50 selectedSonCoo rdPolicy sonFuncCapabil ityBelowItfN sonFuncPriorit yOrder 5.5.2 3GPP TS 32.522 V11.6.1(2013-06) This attribute indicates the SON coordination policy that is selected by IRPManager in case the SON coordination function is located below Itf-N. The selected SON coordination policy is one of the enumed value from BaseOnPriority and BaseOnState, wherein - BaseOnPriority, representing that the coordination is based on the priority order of the SON functionslistedin “sonFuncPriorityOrder” attribute; - BaseOnState, representing the coordination is based on the cell state. The examples of SON coordination for some certain conflicting casesbased on priority and state are depicted in Annex B. This attributes represents the SON functions supported below Itf-N. It is a list of SON function name. The SON function name is one of the enumed value from anr, hoo, lbo, es, coc and cco, wherein - anr repesenting automated neighbor relation; - hoo representing handover parameter optimization; - lbo representing load balancing optimization; - es representing energy saving; - coc representing cell outage compensation; - cco representing coverage and capacity optimization. This attribute indicates the priority order of SON functions below Itf-N for SON coordination purpose, in case the selectedSonCoordPolicy equals to “BaseOnPriority”. It is a list of SON function name, see the detailed description in “sonFuncCapabilityBelowItfN” attribute. The priority order is indicated by the sequence of the SON function name in the list, i.e., the first element in the list takes the highest priority, and the last element in the list takes the lowest priority. In case of selectedSonCoordPolicy does not equal to “BaseOnPriority”, this sequence of the SON function name in the list is not used as priority order for SON coordination. Enumerated {BaseOnPriority, BaseOnState} List of SON function name. SON function name: Enumerated{anr, hoo, lbo, es, coc, cco} List of SON function name: for SON function name, see “sonFuncCapabilityBelowItfN” attribute. Constraints None. 5.6 Common Notifications 5.6.1 Configuration notifications Name notifyAttributeValueChange notifyObjectCreation notifyObjectDeletion 3GPP Qualifier O O O Notes
  • 51. Release 11 51 3GPP TS 32.522 V11.6.1(2013-06) Annex A (informative): Target Achievement Evaluation To evaluate the result of the optimization the target achievement needs to be evaluated. This can be done by calculating the Total Target Achievement as follows. The Total Target Achievement is the sum of the products of the individual target achievement (difference between target and performance) and the individual targetWeights: Total Target Achievement = Sum i=1..n [ ( minTarget i – performance i ) x weighti ] + Sum j=1..n [ performance j – maxTarget j ) x weight j ] where minTarget is a target to be minimized and maxTarget is a target to be maximized. For targets with a substructure (like *Characteristic, see §5.5.1) the above formula is applied to each individual substructure target. The higher the Total Target Achievement, the better is the result of the optimization. 3GPP
  • 52. Release 11 52 3GPP TS 32.522 V11.6.1(2013-06) Annex B (informative): Examples of how to use general SON coordination solutions Examples of how to use general SON coordination solutions are as below: B.1 Coordination of COC and CCO using priority of SON functions To prevent conflicting setting as illustrated in clause 4.7.3.2.1, the cell(s) whichmay need to be coordinated between COC and CCO, i.e., the impact area information, should be known by the SON Coordination Function. By comparing the priorities of COC and CCO, SON Coordination Function will decide to do the high-priority action and suspend the low-priority action on the coordinated cell(s). The priorities of COC and CCO can be preset by operator to SON Coordination Function, or SON Coordination Function inquires the default priority of COC and CCO to each of them. The cell which needs to be coordinated between COC and CCO is: - The cell in which there is coverage or capacity problem and CCO action is needed, meanwhile the cell is outage or compensating or going to compensate for outage; or - The cell which is located in the CCO optimization analysis area for other cell which has coverage or capacity problem, meanwhile the cell is outage orcompensatingor going to compensating for outage; After the high-priority SON function executes action, the SON Coordination Function is informed about the result (successful/unsuccessful, parameters changes) of the executed high-priority SON action. Then,SON Coordination Function will analyse the latest network situation to decide how to deal with the suspended low-priority SON action, for example, resuming or rejecting. B.2 Coordination of COC, CCO and ES using priority of SON functions To prevent conflicting adjustment from COC, ES and optimization from CCO in the common affected cell(s) (e.g., Cell 2 in the Figure 4.7.3.2), the cell(s) whichmay need to be coordinated among COC, CCO and ES, i.e., the impact area information, should be known by the SON Coordination Function. By comparing the priorities of COC, CCO and ES, SON Coordination Function will decide to do the highest-priority action and suspend the low-priority actions on the coordinated cell(s). The priorities of COC, CCO and ES can be preset by operator to SON Coordination Function, or SON Coordination Function inquires the default priority of COC, CCO and ES to each of them. The cell which needs to be coordinated among COC, CCO and ES is: - The cell in which there is coverage or capacity problem and CCO action is needed, meanwhile the cell is outage or compensating or going to compensate for outage or ES; or - The cell which is located in the CCO optimization analysis area for other cell which has coverage or capacity problem, meanwhile the cell is outage or compensating or going to compensate for outage or ES; After the highest-priority SON function executes action, the SON Coordination Function is informed about the result (successful/unsuccessful, parameters changes) of the executed highest-priority SON action. Then,SON Coordination Function will analyse the latest network situation to decide how to deal with the suspended lowpriority SON actions, for example, resuming or rejecting. 3GPP
  • 53. Release 11 B.3 53 3GPP TS 32.522 V11.6.1(2013-06) Coordination of COC, CCO and ES based on the cell state The following lists the examples of how SON Coordination Function (SCF) can resolve the conflicts between COC, CCO, and ES functions based on cell state. Although not shown, priority may be used to along with the cell state to resolve the conflicts. Possible conflict #1: COC requests a cell that is compensating an energy saving cell to compensate an outage cell Resolution: When COC requests SCF that cell A is going to compensate an outaged cell, SCF should check whether cell A is compensating an energy saving cell. If so, SCF should check whether cell A can compensate both the outage cell and the energy saving cell concurrently. If not, the SCF may disallow cell A to compensate an energy saving cell. Possible conflict #2: COC requests a cell that is being changed or going to be changed by CCO to compensate an outage cell Resolution: When COC requests SCF that cell A is going to compensate an outaged cell, SCF should check whether CCO is updating parameters to optimize the capacity and coverage of cell A. If so, SCF may not allow cell A to compensate an outaged cell; otherwise SCF should allow cell A to compensate an outage cell. Possible conflict #3: ES requests a candidate cell that is compensating an outage cell to compensate an energy saving cell Resolution: When ES request SCF that cell A is to compensate a cell going to enter energy saving, SCF should check the cOCStatus.state of cell A. If cOCStatus.state = cOCCompensating, SCF should check whether cell A can compensate both the outage cell and the energy saving cell concurrently. If not, the SCF may disallow cell A to compensate an energy saving cell. Possible conflict #4: ES requests a cell that is being changed or going to be changed by CCO to compensate an energy saving cell Resolution: When ES requests SCF that cell A is going to compensate a cell going to enter energy saving, SCF should check whether CCO is updating parameters to optimize the capacity and coverage of cell A. If so, SCF may not allow cell A to compensate an energy saving cell; otherwise SCF should allow cell A to compensate an outage cell. Possible conflict #5: CCO is going to change the configuration parameter of a cell that is compensating an outage cell Resolution: When CCO requests SCF that cell A is going to change the configuration parameter, SCF should check the cOCStatus.state of cell A. If cOCStatus.state = cOCCompensating, SCF should disallow cell A to change the configuration parameter. Annex C (informative): State diagram for Distributed and EM-centralized Energy Saving Management Energy Saving Management “state” attributes are available at various levels: - SubNetwork IOC level, via the attribute esSwitch defined in the IOC SonControl; 3GPP
  • 54. Release 11 54 3GPP TS 32.522 V11.6.1(2013-06) - ENBFunction IOC level, via the attribute esSwitch defined in the IOC SonControl; - EUtranGenericCell IOC level, via the locally defined attribute isChangeForEnergySavingAllowed, and via the attribute energySavingState defined in the IOC EnergySavingProperties. The following figure provides an overview of Energy Saving Management related IOCs, state attribute names and possible values, for Distributed and EM-centralized Energy Saving Management: Figure C-1: IOCs and state attributes for Distributed and EM-centralized ESM Dependencies exist between distributed ESM state attributes. The diagram below shows which allowed combinations of attribute state values, and which state transitions, are valid and which are not. 3GPP
  • 55. Release 11 55 3GPP TS 32.522 V11.6.1(2013-06) Figure C-2: State diagram for Distributed and EM-centralized ESM Description: a) The ESM-related state attribute esSwitch is used by IRPManager to switch on / off the ESM functionality, in the distributed and EM-centralized architectures. This attribute has two possible values: On, Off. It can be set at the sub-network level and at the eNodeB level; b) The ESM-related state attribute isChangeForEnergySavingAllowed is used by IRPManager to prohibit or allow configuration changes of cells individually, within a eNodeB / sub-network, for ESM purposes by the IRPAgent. This attribute has two possible values: Yes, No. c) The ESM-related state attribute esState is used to reflect the actual status of a cell regarding the energy saving. This attribute has two possible values: isEnergySaving, isNotEnergySaving. Figure C-2 describes the following state transitions: 1) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving) to((esSwitch = On and isChangeForEnergySavingAllowed = Yesand esState = isEnergySaving): happens when: ES Policies attached to the subject cell and to candidate for compensation cells, e.g. threshold and duration, are satisfied and allow entering Energy Saving state. 2) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isEnergySaving) to(esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: ES Policies attached to the subject cell and to candidate for compensation cells, e.g. threshold and duration, are satisfied and allow leaving Energy Saving state. 3) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes) to (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute isChangeForEnergySavingAllowed to “No”. 3GPP
  • 56. Release 11 56 3GPP TS 32.522 V11.6.1(2013-06) 4) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to isChangeForEnergySavingAllowed = Yes: happens when: IRP Manager sets the attribute isChangeForEnergySavingAllowed to “Yes”. 5) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = Yes) to( esSwitch = Off and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “Off”. 6) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = Yes and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “On”. 7) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to (esSwitch = Off and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “Off”. 8) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = No and esState = isNotEnergySaving): happens when: IRP Manager sets the attribute esSwitch to “On”. 3GPP
  • 57. Release 11 57 3GPP TS 32.522 V11.6.1(2013-06) Annex D(informative): Change history Change history Date 2010-03 2010-03 2010-09 2010-12 2010-12 2010-12 TSG # SA#47 -SA#49 SA#50 SA#50 SA#50 TSG Doc. SP-100053 -SP-100491 SP-100858 SP-100749 SP-100833 CR --001 003 005 002 Rev ---1 3 2010-12 SA#50 SP-100866 004 3 2011-01 -- -- -- - 2011-03 2011-03 2011-03 2011-03 2011-03 SA#51 SA#51 SA#51 SA#51 SA#51 SP-110098 SP-110098 SP-110100 SP-110100 010 011 013 014 2 3 - 2011-06 2011-06 2011-09 2011-12 2011-12 2012-06 2012-06 2012-06 SA#52 SA#52 SA#53 SA#54 SA#54 SA#56 SA#56 SA#56 SP-110097 SP-110284 SP-110284 SP-110634 SP-110718 SP-110721 SP-120364 SP-120358 SP-120364 016 018 066 066a 068 071 078 087 088 1 2 1 1 1 1 -1 2012-06 2012-06 2012-09 2012-09 2012-09 2012-09 2012-09 2012-09 SA#56 SA#56 SA#57 SA#57 SA#57 SA#57 SA#57 SA#57 SP-120364 SP-120371 SP-120645 SP-120645 SP-120573 SP-120567 SP-120567 SP-120567 091 092 096 098 103 105 107 108 2 1 2 2 -1 3 2012-09 2012-09 SA#57 SA#57 SP-120567 SP-120567 SP-120791 SP-120783 SP-120791 SP-120791 109 110 111 114 115 117 2 2 2 2 2 SP-120791 SP-120800 SP-120791 SP-120791 SP-120791 SP-120783 SP-120800 119 120 125 126 127 128 131 2 5 1 1 1 3 - SP-130056 SP-130048 SP-130056 104 132 133 7 2 2 SP-130266 SP-130266 SP-130304 SP-130304 134 135 136 139 1 1 1 - 2012-12 SA#58 2013-03 SA#59 2013-03 2013-06 2013-06 SA#60 Subject/Comment Presentation to SA for Information and Approval Publication of SA approved version Remove targets based on not supported by measurements Correcting the support qualifiers of SONControl attributes Disambiguate and correct the description of SON Targets hierarchy Allow EM centralized architecture for Hand-over parameter optimization - Align with 32.500 Adding NRM for Energy Saving Management policies and ESM switch Correction of misimplementation of CR in clause 5.3.2.3 and CR history correction. Introducing RACH optimization management Rapporteur clean-up for editorial errors Use ESPolicies also for EM centralized architecture Correct cardinality of ESPolicies Add a new attribute into SONControl object class to switch on/off Cell Outage Compensation - Align with 32.541 Finalization of Rel-10 SON functionalities Add parameters to control Mobility Robustness Optimization Add PM for Inter-RAT MRO Adding definition of SON coordination Correction MRO management of HO Trigger Adding coordination use case among CCO, COC and ESM Remove the EUTRANRelationSON in the UML Add SON Coordination use case between SON functions below ItfN and CM operations over Itf-N Common SON coordination solution Add time period configuration to allow inter-RAT energy saving Remove Inter-RAT ES restriction for esNotAllowedTimePeriod Correct candidateCellLoadParameters Add support for Inter-RAT Energy Saving Management MoveSON coordination concept description to TS 32.521 Coordinationbetween ES and cell compensation Change description of Coordination between SON functions below Itf-N and CM operations over itf-N Enhancement of general SON coordination solutions Add examples of how to use general SON coordination solutions Correcting function name Clean-up changes Further enhancement of general SON coordination solutions Add description for Coordination between SON functions below ItfN and non-SON operations over Itf-N Add conflict detection for general SON coordination solutions Add load threshold parameters to Inter-RAT energy saving policy Coordination between COC and ANR Coordination between HOO and LBO Add relationship diagram for SON coordination Addition of probing state and its control for Energy Saving Enhance esNotAllowedTimePeriod text description to fulfil energy saving allowed or prohibited for an EUTRAN cell SON Coordination NRMs Add informative annex on Distributed ES State Management Add coordination example based on cell state Editorial correction of the spec title Correction of attribute constraints Remove EUtranRelationSON in UML diagram Correcting error in attribute constraint Correct the attribute constraint of energySavingControl Fixes typo in history table 3GPP Old -1.0.0 9.0.0 9.1.0 9.1.0 9.2.0 New 1.0.0 9.0.0 9.1.0 9.2.0 9.2.0 10.0.0 9.2.0 10.0.0 10.0.0 10.0.1 10.0.1 10.0.1 10.0.1 10.0.1 10.0.1 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 11.0.0 11.0.0 11.1.0 11.1.0 11.1.0 10.2.0 10.2.0 11.0.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.3.0 11.3.0 11.3.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.4.0 11.4.0 11.5.0 11.5.0 11.5.1 11.5.1 11.6.0 11.6.0 11.6.1