6.2 Solutions for energy saving

28.3103GPPEnergy efficiency of 5GManagement and orchestrationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

6.2.1 Overview

For the scenarios where the capacity booster cell is fully or partially overlaid by the candidate cell(s), the key of energy saving solution is that 3GPP management system or NG-RAN node owning the capacity booster cell has the capability to autonomously decide to deactivate such capacity booster cell to lower energy consumption (in energySaving state) or activate the capacity booster cell in energySaving state back to notEnergySaving state due to the increasing traffic above the threshold. The cell activation/deactivation decision is typically based on the load information of the related cells and the energy saving policies (e.g. service related information as one kind of energy saving policies) set by operators.

The service related information may include service characteristic information and/or tenant information of service.

The service characteristic information may include service type information, service name information, and service priority information.

– The service type information indicates the type of service that is being provided via traffic carried by cells under observation, it can be decided by operator’s policy, for example, one kind of service type may be eMBB, URLLC, mIoT, or V2X etc, or another kind of service type may be voice, video, industrial control, web browsing, or autonomous driving;

– The service name may be human-readable name according to operator’s policy;

– The service priority information may be, for example, high priority, medium priority, or low priority.

The tenant information of service may include tenant type information, tenant name information, tenant priority information

– The tenant type may be, for example, Business to Consumer (B2C) tenant, Business to Business (B2B) tenant, Business to Household (B2H) tenant, Business to Business to Everything (B2B2X) tenant;

– The tenant name may be human-readable name according to operator’s policy;

– The tenant priority information may be, for example, high priority, medium priority, or low priority.

The service related information can be obtained from UEs, 5GC NFs (such as UPFs or SMFs) or operators’ information provisioned in 3GPP management system.

Based on the load information of the related cells and the service related information of the the area under consideration, 3GPP management system decides ES actions for the corresponding cells. 3GPP management system may use different weight values for the factors that can influence the ES actions – load information of the related cells and the service related information of the analysis area.

NOTE: How the weight values are assigned by the operator is not subject to standardization.

ES activation procedure and ES deactivation procedure may be initiated in different ways as below:

– Centralized ES solution

– Consumer of centralized MnS for ES requests the producer to configure ES procedure trigger points (e.g. cell traffic load crossing threshold, service characteristic information or tenant information of service), monitoring the traffic situation of capacity booster cells and candidate cells.

– Consumer of centralized MnS for ES requests the producer to instruct the capacity booster cells to move from notEnergySaving state into energySaving state (e.g. according to some traffic performance measurements which cross below some load thresholds and service characteristic information or tenant information of service)

– Consumer of centralized MnS for ES requests the producer to instruct the capacity booster cells to move from energySaving state into notEnergySaving state (e.g. according to some traffic performance measurements which cross above some load thresholds and service characteristic information or tenant information of service)

– Distributed ES solution

– NF provisioning MnS consumer requests the producer to set policies and conditions when these policies/conditions are met, the capacity booster cells will move from notEnergySaving state into energySaving state. Examples for policies/conditions are: A time period, during which energy saving is or not allowed; load thresholds to be considered for energy saving decisions; which of the RATs should be considered with priority in Inter-RAT scenario; service characteristic information or tenant information of service.

– Based on these policies/conditions and further information – e.g. the operational status of the candidate cell to take over the coverage- the NG-RAN node controls the energy saving procedures (ES activation procedure and ES deactivation procedure) in the network nodes. The network operator is informed about configuration changes which are triggered by the NG-RAN nodes. For example, the gNB owning the capacity booster cells moves itself to/from energySaving state autonomously and sends notifications of configuration changes to operator.

6.2.2 Centralized energy saving solution

6.2.2.1 Procedures

6.2.2.1.1 Energy saving activation

NOTE: The centralized energy saving solution in clause 6.2.2 is Domain-Centralized ES solution because the scope of the centralized ES solution is for NR only.

Figure 6.2.2.1.1-1 depicts a procedure that describes how MnS producer of Domain Centralized SON ES management makes the NR capacity booster cell enter the energySaving state.

Figure 6.2.2.1.1-1: Centralized energy saving activation

It is assumed that all relevant MOIs have been created.

Energy saving activation:

The MnS producer for Domain-centralized ES collects the traffic load performance measurements from the NR capacity booster cell and candidate cells.

The MnS producer for Domain-centralized ES analyzes the traffic load performance measurements and decides that the NR capacity booster cell should enter the energySaving state.

The MnS producer for Domain-centralized ES consumes the management service for NF provisioning with modifyMOIAttributes operation to request the NR capacity booster cell to enter the energySaving state.

The NR capacity booster cell may initiate handover actions to off-load the traffic to the neighbour cells (see clause 15.4.2 in TS 38.300 [13]), prior to entering into the energySaving state, and then change to the energySaving state, leading to a notifyMOIAttributeValueChanges being sent to the MnS producer for Domain-centralized ES that the NR capacity booster cell has entered the energySaving state.

6.2.2.1.2 Energy saving deactivation

Figure 6.2.2.1.2-1 depicts a procedure that describes how MnS producer of Domain-Centralized ES management makes the NR capacity booster cell leave the energySaving state.

Figure 6.2.2.1.2-1: Centralized energy saving deactivation

Energy saving deactivation:

The MnS producer for Domain-centralized ES collects the traffic load performance measurements from the candidate cells.

The MnS producer for Domain-centralized ES decides to re-activate the NR capacity booster cell if it detects that the capacity is needed (see clause 15.4.2 in TS 38.300 [13]).

The MnS producer for Domain-centralized ES consumes the management service for NF provisioning with modifyMOIAttributes operation to re-activate the NR capacity booster cell, and changes to the notEnergySaving state, leading to a notifyMOIAttributeValueChanges being sent to the consumer to indicate that the NR capacity booster cell has been re-activated.

6.2.2.2 Management services

6.2.2.2.1 MnS component type A

MnS Component Type A

Note

Operations defined in clause 11.1.1 of TS 28.532 [16]:

– createMOI

– getMOIAttributes

– modifyMOIAttributes

– deleteMOI

Supported by the Provisioning MnS for NF, as defined in TS 28.531 [6].

Notifications defined in clause 11.1.1 of TS 28.532 [16]:

– notifyMOICreation

– notifyMOIAttributeValueChanges

– notifyMOIDeletion

– notifyMOIChanges

Supported by the Provisioning MnS for NF, as defined in TS 28.531 [6].

6.2.2.2.2 MnS Component Type B

6.2.2.2.2.1 Objective and targets

The objective of ES is to automatically set parameters so as to maximize NG-RAN data energy efficiency – see Table 6.2.2.1.2.1-1.

Table 6.2.2.1.2.1-1. Energy Saving targets

Targets	Definition	Legal Values
NG-RAN data Energy Efficiency	Data Volume (DV) divided by Energy Consumption (EC) of the considered network elements.	In bit/J.

6.2.2.2.2.2 Control information

The parameters in CESManagementFunction IOC, which is defined in TS 28.541 [11], are used to control the Domain-SON ES functionality.

6.2.2.2.3 MnS Component Type C

6.2.2.2.3.1 Parameters to be optimized

This is out of the scope of the present document.

6.2.2.2.3.2 Performance measurements

Performance measurements related to Domain-centralized SON ES are captured in Table 6.2.2.2.3.2-1:

Table 6.2.2.2.3.2-1. Energy saving management related performance measurements

Performance measurements	Description	Related targets
DRB.PdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered to PDCP layer – see clause 5.1.2.1.1.1 of TS 28.552 [15], per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DRB.PdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered from PDCP layer to higher layers – see clause 5.1.2.1.2.1 of TS 28.552 [15], per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DL Cell PDCP SDU Data Volume on X2 Interface	Data Volume (amount of PDCP SDU bits) in the downlink delivered on X2 interface in DC-scenarios – see clause 5.1.2.1.1.2 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3). In case of non-split gNBs.	NG-RAN data Energy Efficiency
DL Cell PDCP SDU Data Volume on Xn Interface	Data Volume (amount of PDCP SDU bits) in the downlink delivered on Xn interface in DC-scenarios scenarios – see clause 5.1.2.1.1.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
UL Cell PDCP SDU Data Volume on X2 Interface	Data Volume (amount of PDCP SDU bits) in the uplink delivered on X2 interface in NSA scenarios – see clause 5.1.2.1.2.2 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3). In case of non-split gNBs.	NG-RAN data Energy Efficiency
UL Cell PDCP SDU Data Volume on Xn Interface	Data Volume (amount of PDCP SDU bits) in the uplink delivered on Xn interface in SA scenarios – see clause 5.1.2.1.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DRB.F1uPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to GNB-DU (F1-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.XnuPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to external gNB-CU-UP (Xn-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.X2uPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to external eNB (X2-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI). In case of split gNBs.	NG-RAN data Energy Efficiency
DRB.F1uPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from GNB-DU (F1-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.XnuPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from external gNB-CU-UP (Xn-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.X2uPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from external eNB (X2-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI). In case of split gNBs.	NG-RAN data Energy Efficiency
PNF Energy consumption	Energy consumed – see clause 5.1.1.19.3 of TS 28.552 [15]	NG-RAN data Energy Efficiency

6.2.3 Distributed energy saving solution

6.2.3.0 Management service components used for Distributed SON ES solution

The MnS components used for Distributed SON ES solution are listed in the following clauses 6.2.3.1.1, 6.2.3.1.2 and 6.2.3.1.3.

6.2.3.1 Management services

6.2.3.1.1 MnS component type A

MnS Component Type A

Note

Operations defined in clause 11.1.1 of TS 28.532 [16]:

– createMOI

– getMOIAttributes

– modifyMOIAttributes

– deleteMOI

Supported by the Provisioning MnS for NF, as defined in TS 28.531 [6].

Notifications defined in clause 11.1.1 of TS 28.532 [16]:

– notifyMOICreation

– notifyMOIAttributeValueChanges

– notifyMOIDeletion

– notifyMOIChanges

Supported by the Provisioning MnS for NF, as defined in TS 28.531 [6].

6.2.3.1.2 MnS Component Type B

6.2.3.1.2.1 Objective and targets

The objective of ES is to automatically set parameters so as to maximize NG-RAN data energy efficiency – see Table 6.2.3.1.2.1-1.

Table 6.2.3.1.2.1-1. Energy Saving targets

Targets	Definition	Legal Values
NG-RAN data Energy Efficiency	Data Volume (DV) divided by Energy Consumption (EC) of the considered network elements.	In bit/J.

6.2.3.1.2.2 Control information

The parameters in DESManagementFunction IOC, which is defined in TS 28.541 [11], are used to control the Distributed SON ES functionality.

6.2.3.1.3 MnS Component Type C

6.2.3.1.3.1 Parameters to be optimized

This is out of the scope of the present document.

6.2.3.1.3.2 Performance measurements

Performance measurements related to Distributed SON ES are captured in Table 6.2.3.1.3.2-1:

Table 6.2.3.1.3.2-1. Energy saving management related performance measurements

Performance measurements	Description	Related targets
DRB.PdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered to PDCP layer – see clause 5.1.2.1.1.1 of TS 28.552 [15], per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DRB.PdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered from PDCP layer to higher layers – see clause 5.1.2.1.2.1 of TS 28.552 [15], per configured PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DL Cell PDCP SDU Data Volume on X2 Interface	Data Volume (amount of PDCP SDU bits) in the downlink delivered on X2 interface in DC-scenarios – see clause 5.1.2.1.1.2 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3). In case of non-split gNBs.	NG-RAN data Energy Efficiency
DL Cell PDCP SDU Data Volume on Xn Interface	Data Volume (amount of PDCP SDU bits) in the downlink delivered on Xn interface in DC-scenarios scenarios – see clause 5.1.2.1.1.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
UL Cell PDCP SDU Data Volume on X2 Interface	Data Volume (amount of PDCP SDU bits) in the uplink delivered on X2 interface in NSA scenarios – see clause 5.1.2.1.2.2 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI or QCI in NR option 3). In case of non-split gNBs.	NG-RAN data Energy Efficiency
UL Cell PDCP SDU Data Volume on Xn Interface	Data Volume (amount of PDCP SDU bits) in the uplink delivered on Xn interface in SA scenarios – see clause 5.1.2.1.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of non-split gNBs.	NG-RAN data Energy Efficiency
DRB.F1uPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to GNB-DU (F1-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.XnuPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to external gNB-CU-UP (Xn-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.X2uPdcpSduVolumeDL_Filter	Data Volume (amount of PDCP SDU bits) in the downlink delivered from GNB-CU-UP to external eNB (X2-U interface) – see clause 5.1.3.6.2.3 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI). In case of split gNBs.	NG-RAN data Energy Efficiency
DRB.F1uPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from GNB-DU (F1-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.XnuPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from external gNB-CU-UP (Xn-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI. In case of split gNBs	NG-RAN data Energy Efficiency
DRB.X2uPdcpSduVolumeUL_Filter	Data Volume (amount of PDCP SDU bits) in the uplink delivered to GNB-CU-UP from external eNB (X2-U interface) – see clause 5.1.3.6.2.4 of TS 28.552 [15], per PLMN ID and per QoS level (mapped 5QI). In case of split gNBs.	NG-RAN data Energy Efficiency
PNF Energy consumption	Energy consumed – see clause 5.1.1.19.3 of TS 28.552 [15]	NG-RAN data Energy Efficiency

6.2.3.2 Procedures

6.2.3.2.1 Energy saving activation

Figure 6.2.3.2.1-1 depicts a procedure that describes how MnS producer of Distributed ES management makes the NR capacity booster cell enter the energySaving state.

Figure 6.2.3.2.1-1: Distributed energy saving activation

It is assumed that all relevant MOIs have been created.

Energy saving activation:

The MnS producer for distributed ES management consumes the management service for NF provisioning with modifyMOIAttributes operation to:

– Configure the cell overlaid relations for NR capacity booster cells, and macro cells as candidate cells

– Configure the ES policy that includes the thresholds for the energy saving activation and deactivation for NR capacity booster cells and candidate cells

– Enable the distribute energy saving function for intra-RAT or inter-RAT.

NOTE: Void

The distributed ES function makes decision for the NR capacity booster cell to enter the energySaving state based on the cell traffic load information (see clause 15.4.2 in TS 38.300 [13]).

The distributed ES function changes to the energySaving state, leading to a notifyMOIAttributeValueChanges (see clause 5.1.9 in TS 28.532 [16]) being sent to the MnS producer for distributed ES management to indicate the NR capacity booster has entered the energySaving state.

6.2.3.2.2 Energy saving deactivation

Figure 6.2.3.2.2-1 depicts a procedure that describes how Distributed ES function makes the NR capacity booster cell leave the energySaving state.

Figure 6.2.3.2.2-1: Distributed energy saving deactivation

Energy saving deactivation:

The distributed ES function monitors the traffic load of candidate cell, and decides to re-activate the NR capacity booster cell when it detects that additional capacity is needed (see clause 15.4.2 in TS 38.300 [13]).

The distributed ES function changes to the notEnergySaving state, leading to a notifyMOIAttributeValueChanges being sent to the MnS producer for distributed ES management to indicate the NR capacity booster has been re-activated.