The use cases for Data Volume measurement control, data file reporting and streaming in the following clauses 5.1.1.x are valid for all 5GS network functions.

Use cases specified in clause 5.1.1.1 of TS 28.550 ("NF measurement job control service") - apply for measurement job control of Data Volume. Depending on scenarios, NF measurement job control services may not exist. In such a case, the NF measurement control of DV may be achieved as specified in clause 5.1.18 of TS 28.531 ("Configuration of a 3GPP NF instance"). Traceability:

Use cases specified in clause 5.1.1.2 of TS 28.550 - apply for Data Volume measurement data file reporting, in compliance with [8], [9], [10]. Traceability:

Use cases specified in clause 5.1.1.3 of TS 28.550 - apply for Data Volume measurement data streaming. Traceability:

The requirements for PEE measurement control, data file reporting and streaming, fault supervision and configuration management in the following clauses 5.1.2.x are only valid for 5GS physical network functions.

Use cases specified in clause 5.1.1.1 of TS 28.550 ("NF measurement job control service") - apply for measurement job control of PEE parameters. Depending on scenarios, NF measurement job control services may not exist. In such a case, the NF measurement control of PEE parameters may be achieved as specified in clause 5.1.18 of TS 28.531 ("Configuration of a 3GPP NF instance"). Traceability:

Use cases specified in clause 5.1.1.2 of TS 28.550 - apply for PEE measurement data file reporting, in compliance with TS 32.432, TS 32.435, TS 32.436. Traceability:

Use cases specified in clause 5.1.1.3 of TS 28.550 - apply for PEE measurement data streaming. Traceability:

Use cases specified in clause 5.1.13 of TS 28.545 ("Report alarm notifications of NF instance") - apply for PEE fault supervision. Traceability:

Use cases specified in clause 5.1.18 of TS 28.531 - apply for PEE configuration management. Traceability:

The objective of energy saving is to lower OPEX for mobile operators, through the reduction of power consumption in the mobile networks that is becoming more urgent and challenging, as there are much more network elements in NR (e.g., small cells with massive MIMO in higher frequency bands) than those used in LTE (TR 37.816, TS 38.300). One typical scenario of energy saving is to switch off capacity boosters when the traffic demand is low, and re-activated them on a need basis (see clause 5.6 in TR 37.816). The energy saving consists of two scenarios where the capacity booster cell - gNB is fully or partially overlaid by the candidate cell(s).

An NG-RAN node, which connects with 5GC to provide boost capacity, may enter into energySaving state if there is radio coverage by other radio systems - be another NG-RAN node or an entity of another radio access technology - for the whole coverage area of the NG-RAN node in question, see Figure 5.1.3.3-1 for gNB capacity booster cell fully overlaid by candidate cell(s) case.

This use case applies both for Intra- and Inter-RAT Energy Saving. Two gNB cells (Cell A, Cell B) with separate frequency bands cover the same geographical area. Cell B has a smaller size than Cell A and is covered totally by Cell A. Generally, Cell A is deployed to provide continuous coverage of the area, while Cell B increases the capacity of the special sub-areas, such as hot spots. The ES activation procedure in the coverage of Cell B (ES area) may be triggered in case that light traffic in Cell B is detected. Cell B ES activation may also be triggered when the traffic of ES area (measured by candidate Cell A) resumes to a high level. A Cell B capable of ES probing can execute the ES probing procedure and based on Cell B measurements the centralized or distributed ES management can decide if the Cell B needs to be activated and take portion of the traffic from Cell A. Two IRAT cells (Cell A, Cell B) cover the same geographical area. gNB Cell B is totally covered by inter-RAT Cell A (such as legacy system UMTS or LTE). Cell A is deployed to provide continuous coverage of basic eMBB services in the area, while Cell B enhances the capability of the area to support eMBB services with high data rate or URLLC services. The ES activation in the coverage of Cell B (ES area) may be triggered in case that no eMBB services with high data rate or URLLC traffic in Cell B is detected or load threshold for going into energySaving state is reached. Cell B ES deactivation may be triggered when the eMBB services with high data rate or URLLC service request in ES area is restarted again or load threshold for going out of energySaving state (i.e. going into notEnergySaving state) is reached. A Cell B capable of ES probing can execute the ES probing procedure and based on Cell B measurements the centralized or distributed ES management can decide if the Cell B needs to be activated and take portion of the traffic from Cell A. Different scenarios of gNB capacity booster cell fully overlaid by candidate cell(s) are listed in below Table 5.1.3.3-1.

Traceability:

To meet service demands, e.g. in terms of latency, the Network Operator (NOP) decided to deploy some UPFs at the edge of its core network, i.e. closer to low latency demanding service users than if they were deployed in its central core network. During off-peak periods and depending on service users' profile, observed behaviour and habits, the NOP may decide that some of these edge UPFs are no longer justifed. For example, at night, in some locations where no user paying for low latency services is connected, the remaining traffic (not demanding low latency) can be redirected from the edge UPFs to central core UPFs. The NOP may then decide to:

• redirect the remaining traffic to and from these edge UPFs to existing central core UPFs, and
• decommission these edge UPFs, or scale them in/down, or any other action enabling to achieve energy saving, depending on e.g. whether these UPFs are virtualized or not.

The decommissioning of edge UPFs can be done e.g. by administratively putting them out of service so that they can't carry any more traffic, either with immediate effect or only when no more users are using these UPFs. The NOP may decide at any time to come back to the initial situation. Traceability:

The MnS producer for Domain-centralized ES or the distributed ES function, that makes a decision for the NR capacity booster cell to enter or exit energySaving state, should be able to initiate energy saving compensation activation and/or deactivation on one or multiple cells.

For the energy saving use cases (defined in clause 5.1.3), when a NR capacity booster cell enters energySaving state, then the candidate cell(s) may transition to:

• compensatingForEnergySaving.
  Correspondingly, the use cases support the following procedures:
• Energy saving compensation activation: the procedure to increase the coverage area for the candidate cell(s).
• Energy saving compensation deactivation: the procedure to decrease a previously increased coverage area.

The requirements for Data Volume measurement control, data file reporting and streaming in the following clauses 5.2.1.x are valid for all 5GS network functions.

REQ-DVMCS-FUN-001: REQ-DVMCS-FUN-002: REQ-DVMCS-FUN-003: REQ-DVMCS-FUN-004: REQ-DVMCS-FUN-005:

REQ-DVFRS-FUN-010: REQ-DVFRS-FUN-011:

REQ-DVDS-FUN-020:

The requirements for PEE measurement control, data file reporting and streaming, fault supervision and configuration management in the following clauses 5.2.2.x are only valid for 5GS physical network functions.

REQ-PEEMCS-FUN-001: REQ-PEEMCS-FUN-002: REQ-PEEMCS-FUN-003: REQ-PEEMCS-FUN-004: REQ-PEEMCS-FUN-005: REQ-PEEMCS-FUN-006:

REQ-PEEFRS-FUN-010: REQ-PEEFRS-FUN-011:

REQ-PEEDS-FUN-020:

REQ-PEEFSS-FUN-020:

REQ-PEECMS-FUN-030: REQ-PEECMS-FUN-031:

REQ-ESCOL-FUN-1: REQ-ESCOL-FUN-2: REQ-ESCOL-FUN-3: REQ-ESCOL-FUN-4: REQ-ESCOL-FUN-5: REQ-ESCOL-FUN-6: REQ-ESCOL-FUN-7:

REQ-SOUPF-FUN-1: REQ-SOUPF-FUN-2:

REQ-ESCOL-FUN-y1: REQ-ESCOL-FUN-y2: REQ-ESCOL-FUN-y3: REQ-ESCOL-FUN-y4: