B.3 Coordination of COC, CCO and ES based on the cell state
28.6283GPPInformation Service (IS)Release 17Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP)Telecommunication managementTS
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;
– 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.
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 energySavingState 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 energySavingState = isNotEnergySaving) to((esSwitch = On and isChangeForEnergySavingAllowed = Yes and energySavingState = 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 energySavingState = isEnergySaving) to(esSwitch = On and isChangeForEnergySavingAllowed = Yes and energySavingState = 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 energySavingState = isNotEnergySaving): happens when:
IRP Manager sets the attribute isChangeForEnergySavingAllowed to “No”.
4) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and energySavingState = 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 energySavingState = isNotEnergySaving): happens when:
IRP Manager sets the attribute esSwitch to “Off”.
6) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = Yes and energySavingState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = Yes and energySavingState = isNotEnergySaving): happens when:
IRP Manager sets the attribute esSwitch to “On”.
7) Transition from (esSwitch = On and isChangeForEnergySavingAllowed = No and energySavingState = isNotEnergySaving) to (esSwitch = Off and isChangeForEnergySavingAllowed = No and energySavingState = isNotEnergySaving): happens when:
IRP Manager sets the attribute esSwitch to “Off”.
8) Transition from (esSwitch = Off and isChangeForEnergySavingAllowed = No and energySavingState = isNotEnergySaving) to (esSwitch = On and isChangeForEnergySavingAllowed = No and energySavingState = isNotEnergySaving): happens when:
IRP Manager sets the attribute esSwitch to “On”.
Annex D (informative):
Change history
|
Change history |
|||||||
|---|---|---|---|---|---|---|---|
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2013-03 |
SA#59 |
SP-130060 |
001 |
– |
Rel-11 CR 28.628 SON coordination synchronization with 32.522 |
11.0.0 |
11.1.0 |
|
2013-06 |
SA#60 |
SP-130304 |
002 |
1 |
SON coordination synchronization with 32.522 |
11.1.0 |
11.2.0 |
|
003 |
– |
Energy saving synchronization with 32.522 |
|||||
|
004 |
– |
Correction of attribute constraints |
|||||
|
2013-09 |
SA#61 |
SP-130441 |
005 |
– |
Add missing Object class id for SONPolicy IOCs |
11.2.0 |
11.3.0 |
|
2014-06 |
SA#64 |
SP-140358 |
007 |
– |
remove the feature support statements |
11.3.0 |
11.4.0 |
|
2014-09 |
Upgrade to Rel-12 |
11.4.0 |
12.0.0 |
||||
|
2014-12 |
SA#66 |
SP-140798 |
008 |
1 |
Change esState in the Annex C text with the correct name of the attribute |
12.0.0 |
12.1.0 |
|
2015-03 |
SA#67 |
SP-150063 |
009 |
1 |
Add NM centralized Coverage and Capacity Optimization (CCO) logical description |
12.1.0 |
13.0.0 |
|
2015-06 |
SA#68 |
SP-150320 |
010 |
3 |
Add measurements for NM centralized Coverage and Capacity Optimization (CCO) |
13.0.0 |
13.1.0 |
|
2015-09 |
SA#69 |
SP-150419 |
011 |
1 |
Add NM-Centralized CCO related measurements and delete redundant ones |
13.1.0 |
13.2.0 |
|
013 |
1 |
Correct coverage hole definition for NM centralized Coverage and Capacity Optimization (CCO) |
|||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
Promotion to Release 14 without technical change |
14.0.0 |
||||
|
2018-01 |
SA#78 |
SP-170968 |
0016 |
4 |
B |
Add SON for AAS deployment management description and attributes |
15.0.0 |
|
2019-03 |
SA#83 |
SP-190125 |
0017 |
– |
F |
Correction of AAS IP Throughput load rate definition |
15.1.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2020-09 |
SA#89e |
SP-200813 |
0018 |
– |
F |
Modify TOP as parent IOC |
16.1.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |