5.1 Requirements

28.6273GPPRelease 17RequirementsSelf-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP)Telecommunication managementTS

5.1.1 Self-Optimization Monitoring and Management

REQ-SO_MM-CON-1 IRPManager shall be able to control the self-optimization functions.

REQ-SO_MM-CON-2 The self-optimization complex corrective actions shall be executed in a consistent and coordinated way.

REQ-SO_MM-CON-3 Self-optimization functions shall reuse existing standardized solutions as much as possible.

REQ-SO_MM-CON-4 void

REQ-SO_MM-CON-5 The IRPAgent shall support a capability allowing the IRPManager to know the success or failure result of Self-Optimization.

REQ-SO_MM-CON-6 The trigger conditions of self-optimization functions should be able to be managed by the IRPManager. The trigger condition may be the scheduled time to start a self-optimization function or a period of time during which a self-optimization function is forbidden to be started or the event (i.e. do not meet objectives or targets) to start a self-optimization function. Each self-optimization function shall have its own set of trigger condition.

REQ-SO_MM-CON-7 For the self-optimization functions which need continuous monitoring, the IRPManager should be able to manage the execution of self-optimization actions (e.g. setting a period of time during which a self-optimization action is forbidden to be executed).

REQ-SO_MM-CON-8 Each self-optimization function shall have one or several related performance indicator, which may be used as objective to evaluate the performance before the self-optimization is initiated and after the self-optimization function is completed.

REQ-SO_MM-CON-9 For operator controlled (open loop) SON function, the IRPAgent shall support a capability allowing IRPManager to know the information about the self-optimization actions. The necessity of this capability will be decided case by case.

REQ-SO_MM-CON-10 The IRPAgent shall support a capability allowing IRPManager to know the information about the execution result of self-optimization actions.

5.1.2 Load Balancing

REQ-SO_LB-CON-1 The optimization of load balancing shall be performed with minimal human intervention.

REQ-SO_LB-CON-2 The following scenarios shall be considered in optimization of load balancing. Each scenario shall include the load balancing on intra-frequency, inter-frequency, and inter-RAT.

1. Overlapping Coverage

2. Hierarchical Coverage

3. Neighbouring Coverage

5.1.3 Handover (HO) Parameter optimization

REQ-SO_HO-CON-1 HO parameter optimization shall be performed with no human intervention as much as possible.

REQ-SO_HO-CON-2 HO parameter optimization function shall aim at reducing the number of HO failures as well as reducing inefficient use of network resources due to unnecessary handovers. In particular, the HO parameter optimization function shall aim at reducing the number of HO related failures that cause degradation in user experience, such as call drops, radio link failures before, during or shortly after HO, and reduced data rates.

5.1.4 Interference control

REQ-SO_IC-CON-1 Interference control shall be performed with as little human intervention as possible.

REQ-SO_IC-CON-2 The following scenarios shall be considered in interference control.

1. Uplink inter cell interference coordination

2. Downlink inter cell interference coordination

5.1.5 Coverage and Capacity optimization

REQ-SO_CC-CON-1 Coverage and capacity optimization shall be performed with minimal human intervention.

REQ-SO_CC-CON-2 Operator shall be able to configure the objectives and targets for the coverage and capacity optimization function.

REQ-SO_CC-CON-3 Operator shall be able to configure the objectives and targets for the coverage and capacity optimization functions differently for different areas of the network.

REQ-SO_CC-CON-4 The collection of data used as input into the coverage and capacity optimization function shall be automated to the maximum extent possible and shall require minimum possible amount of dedicated resources.

REQ-SO_CC-CON-5 The following scenarios shall be considered in coverage and capacity optimization.

1. E-UTRAN Coverage holes with 2G/3G coverage

2. E-UTRAN Coverage holes without any other radio coverage

3. E-UTRAN Coverage holes with isolated island cell coverage

4. E-UTRAN cells with too large coverage

REQ-SO_CC-CON-6 The operator shall be able to manage tradeoffs between coverage and capacity using policies.

5.1.6 RACH optimization

REQ-SO_RO-CON-1 RACH optimization shall be performed with minimal human intervention.

5.1.7 SON Coordination

REQ-SON_COORD-CON-1 SON coordination shall allow the prevention and resolution of conflicts between SON functions.

REQ-SON_COORD-CON-2 In case the SON coordination function is below Itf-N, the IRPAgent should support the capability for the IRPManager to define policies for the case that SON functions request conflicting parameter values. In case no policy is given, the IRPAgent shall apply default policies.

Note: A policy describes an expected behaviour from the IRPAgent. Examples for such policies:

i) Prioritizing SON functions in case of conflicts

ii) Assigning weights to SON targets

iii) Prohibiting further changes of a parameter for a certain amount of time

iv) Selecting preferred value ranges

v) Telling the IRPAgent to report conflicts

REQ-SON_COORD-CON-3 For the case that the IRPAgent does not resolve the case of SON functions requesting conflicting values for parameters, the IRPAgent should support the capability for the IRPManager to decide about the parameter values.

REQ-SON_COORD-CON-4 The IRPAgent shall support a capability allowing the IRPManager to configure the SON coordination policy. The coordination includes the following aspects:

1) Coordination between SON functions below Itf-N and CM operations over Itf-N.

2) Coordination between different SON functions.

5.1.8 Active Antenna System (AAS) management

REQ-SO_AAS-CON-1 AAS operations (including Cell Splitting, Cell Merging, Cell Shaping) shall be performed with no or minimal human intervention.

REQ-SO_AAS-CON-2 Operator shall be able to configure and manage the new split or merged cells (which is created from Cell Splitting or Cell Merging operations) in automated manner.

REQ-SO_AAS-CON-3 Operator shall be notified about the creation of split or merged cells as soon as possible after they are split or merged from the original cell(s).

REQ-SO_AAS-CON-4 Operator shall be able to configure the shaped cell (due to Cell Shaping operation) in automated manner with pre-defined alternative coverage configurations.

REQ-SO_AAS-CON-5 The AAS operations (including Cell Splitting, Cell Merging, Cell Shaping) shall be performed with coordination from OAM configuration on neighbour eNBs, to keep coverage, inter-cell interference and handover settings under control.