21 Telecom Management

21.9163GPPRelease 16Release descriptionTS

21.1 Network and Service Management

21.1.1 5G Management capabilities

860023

5G Management capabilities

5GMNC

S5

SP-191195

Jean-Michel Cornily, Orange

Summary based on the input provided by Orange in SP-200535.

In addition to generic management services, 5G management capabilities are needed to support the management and orchestration of 5G networks. This Rel-16 work item focuses on the heartbeat management capability.

This Work Item has produced TS 28.537: Management and orchestration; Management capabilities.

TS 28.537 [1] is a placeholder for the specification of 5G management capabilities. In Rel-16, only the heartbeat management capability is addressed.

The heartbeat management capability is needed to monitor the communication between Management Service (MnS) producers and MnS consumers, and to discover communication link breaks between them as early as possible.

TS 28.537 [1] captures use cases, requirements and procedures for the heartbeat management capability.

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=860023

[1] TS 28.537: Management and orchestration; Management capabilities

21.1.2 Energy Efficiency of 5G

810023

Energy Efficiency of 5G

EE_5G

S5

SP-191193

Jean-Michel Cornily, Orange

Summary based on the input provided by Orange in SP-200228.

The term ‘Energy Efficiency’ (EE) is to be understood as covering two areas:

1. Definition of EE KPI, required performance measurements and method(s) to collect them;

2. Definition of use cases, requirements and solutions to optimize Energy Efficiency – this is also sometimes referred to as Energy Saving.

Both aspects have been addressed in SA5 for pre-5G radio access technologies, focusing on how OA&M can provide support to them. This work item (EE_5G) addresses NG-RAN.

This Work Item has produced the Rel-16 TS 28.310 "Management and orchestration; Energy efficiency of 5G", as well as CRs 0055 and 0111 to TS 28.552 and CR 0032 to TS 28.554.

TS 28.310 [1] captures use cases, requirements and procedures for collecting performance measurements (namely data volume measurements and PEE (Power, Energy and Environment) parameters from 5G base stations. The EE KPI for 5G base stations is obtained thanks to these measurements. Those measurements are collected by the OSS thanks to the usage of generic management services defined in TS 28.532. Data Volume (DV) measurements, at PDCP layer, have been introduced in TS 28.552 [2], as well as PEE parameters definition (amongst which the Energy Consumption (EC) of the base station). A new KPI, named EE KPI, calculated by dividing Data Volume (DV) by Energy Consumption (EC) has been defined in TS 28.554 [5]. All this is fully aligned with baseline ETSI TC EE (Environmental Engineering) specifications ES 203 228 [7] and ES 202 336-12 [8].

Some intra- and inter-RAT energy saving use cases and requirements have been specified in TS 28.310 [1]. The 5G Network Resource Model (TS 28.541 [9]) has been augmented with an Energy Saving NRM fragment enabling the management of both centralized and distributed energy saving modes.

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=810023

[1] TS 28.310: Management and orchestration; Energy efficiency of 5G

[2] TS 28.552: Management and orchestration; 5G performance measurements

[3] SP-190755: Add Power, Energy and Environmental (PEE) measurements and related use case description

[4] SP-190119: Add PDCP data volume measurements for EE

[5] TS 28.554: Management and orchestration; 5G end to end Key Performance Indicators (KPI)

[6] SP-191165: Add 5G Energy Efficiency KPI

[7] ETSI ES 203 228: Environmental Engineering (EE); Assessment of mobile network energy efficiency

[8] ETSI ES 202 336-12: Environmental Engineering (EE); Monitoring and control interface for infrastructure equipment (power, cooling and building environment systems used in telecommunication networks); Part 12: ICT equipment power, energy and environmental parameters monitoring information model

[9] TS 28.541: Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3

21.1.3 OAM aspects of LTE and WLAN integration

810024

OAM aspects of LTE and WLAN integration

OAM_LTE_WLAN

S5

SP-180820

Yizhi Yao, Intel Corporation

Summary based on the input provided by Intel Corporation in SP-191252.

The OAM_LTE_WLAN work item defined the requirements and solutions for management aspects of LWA (LTE-WLAN aggregation) and LWIP (LTE WLAN integration with IPsec tunnel) features defined by 3GPP RAN WGs. The management aspects of LWA and LWIP addressed by this work item include:

-Configurations to eNB to support LWA and LWIP;

-Management model for WT for co-located and non-co-located LWA deployment scenarios; and

-Performance measurements to monitor the LWA (including co-located and non-co-located scenarios) and LWIP.

The work item resulted in a number of CRs on TS 32.425, 28.657, 28.658, and 28.659 based on the preceding TR 32.868.

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=810024

21.1.4 Methodology for 5G management specifications

810026

Methodology for 5G management specifications

METHOGY

S5

SP-180822

Jan Groenendijk, Ericsson

Summary based on the input provided by Ericsson in SP-200531.

This work item documents the methodology used to document the various specification artefacts, such as requirements and solutions, of the network management services. The target group for the methodology specification is the specification authors for the OAM specifications.

The methodologies include template(s) and network resource model repertoire.

This work item resulted in several CR’s to update network resource model repertoire TS 32.156 [1] and a new specification;

– TS 32.160: Management and orchestration: Management service template

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=810026

[1] TS 32.156: Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire

21.1.5 Closed loop SLS Assurance

850026

Closed loop SLS Assurance

COSLA

S5

SP-190781

Jan Groenendijk, Ericsson

Summary based on the input provided by Ericsson in SP-200532.

This work item specifies a closed loop assurance solution that helps an operator to continuously deliver the expected level of communication service quality. The closed loop assurance solution allows an operator to create a closed loop management service that automatically adjusts and optimizes the services provided by NG-RAN and 5GC based on the various performance management and QoE input data, and the state of the 5G network, using data analytics. To be able to deploy SLS assurance solutions number of areas need are addressed:

– key management control loops in SLS assurance, key entities in the loops (e.g. MDAS)

– describe important data and enable efficient data collection [for SLS assurance] from NG-RAN and 5GC (includes NWDAF information) to consumers in OAM, e.g. performance management and configuration data

– describe coordination and management of the management functions involved in SLS assurance loops.

– placement and role of management analytics functions in the OAM framework.

This work item resulted in several CR’s to update architecture framework TS 28.533 [1] and two new specifications:

– TS 28.535: Management and orchestration: Management Services for Communication Service Assurance; Requirements

– TS 28.536: Management and orchestration: Management Services for Communication Service Assurance; Stage 2 and stage 3

Reference:

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=850026

[1] TS 28.533: Management and orchestration: Architecture framework

21.1.6 Trace Management in the context of Services Based Management Architecture and Streaming Trace reporting

820036

Trace Management in the context of Services Based Management Architecture

TB_SBMA

S5

SP-181073

Anatoly Andrianov, Nokia

850027

Streaming Trace reporting

OAM_RTT

S5

SP-190782

Anatoly Andrianov, Nokia

Summary based on the input provided by Ericsson in SP-200532.

The combination of the 3GPP Rel-16 Trace features ("Trace management in the context of Services Based Management Architecture (SBMA)" and "Streaming Trace reporting") transformed the legacy, partially outdated trace functionality into a modern flexible and powerful toolset.

As SA5 no longer mandates the functional management architecture focused on interactions between IRPManager and IRPAgent over Itf-N, a new way of trace management was necessary. The concept of "configurable trace" has been introduced where the management trace activation is represented by the act of Managed Object Instance (MOI) creation. The new TraceJob Information Object Class (IOC) also known as "Trace control NRM fragment" has been specified for this purpose in the Generic NRM TSs 28.622 [1] and 28.623 [2]. The creation, deletion and modification of the MOIs based on the new IOC does not require a dedicated API and is performed by the means of Provisioning Management Service (Provisioning MnS) specified in TS 28.532 [3]. The corresponding content (concepts, requirements, definitions) has been added to the family of trace specifications (TSs 32.421 [4] and 32.422 [5]), while all the dependencies on the legacy Trace Management IRP and legacy functional architecture have been eliminated.

TR 28.806 [8] identified and documented use cases for collecting Cell and UE data for analytics, and for Collecting subscriber and equipment trace data for near-real-time diagnostics and troubleshooting. It established that enabling the capabilities for trace data to be delivered to the consumer(s) while it’s still relevant to the analytics, diagnostics and troubleshooting tasks performed by the consumer is important. The normative work on streaming trace data reporting leveraged the model-driven approach to the trace management and SBMA framework (TS 28.533 [7]). It added the new use cases and requirements for streaming trace to TS 32.421 [4], addressed all relevant trace control and configuration management aspects in TS 32.422 [5] and specified the serialization format for the streaming trace records in TS 32.423 [6]. The initial work on a dedicated Streaming Trace data reporting MnS has been further extended and generalized into support of additional streaming data types such as Streaming PM, Streaming Analytics and proprietary data. The new Streaming data reporting MnS has been fully specified in TS 28.532 [3] it includes a RESTful HTTP based solution set for streaming connection establishment and connection/stream meta-data exchange and an efficient protocol stack for high volume/high speed streaming data reporting based on WebSockets. The use of SBMA framework does not limit the consumers and producers of the new MnS to 3GPP Management Functions and supports the use cases where 3GPP Network Element (NE) reports management data (Trace, PM, Analytics and proprietary) to any authorized MnS consumer.

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=820036,850027

[1] TS 28.622 "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)"

[2] TS 28.623 "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions"

[3] TS 28.532 "Management and orchestration; Generic management services"

[4] TS 32.421 "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements"

[5] TS 32.422 "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management"

[6] TS 32.423 "Telecommunication management; Subscriber and equipment trace; Trace data definition and management"

[7] TS 28.533 "Management and orchestration; Architecture framework"

[8] TS 28.806 "Study on non-file-based trace reporting"

21.1.7 Management of QoE measurement collection

760058

Management of QoE measurement collection

QOED

S5

SP-181069

Petersen, Robert, Ericsson

Summary based on the input provided by Ericsson in SP-200872.

This work item specifies the function Management of QoE measurement collection for a specified area in UMTS and LTE.

An operator or an automated management function can request that DASH or MTSI measurements are collected (when those applications are used in UEs that has the capability of reporting them) and send them to a specified collection entity, which can use them for calculating KPIs or take part in automated functions etc.

Use cases and requirements are specified.

The e2e functionality is described according to the TS 26.247, TS 26.114, TS 27.007, TS 25.331, TS 25.413, TS 36.331, 36.413 and TS 28.308.

The output report is specified according to the TS 26.247, TS 26.114.

The management interfaces over Itf-N are specified in an Integration Reference Point (IRP).

This work item resulted in six specifications:

• TS 28.307: Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Requirements

• TS 28.308: Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Information Service (IS)

• TS 28.309: Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definition

• TS 28.404: Quality of Experience (QoE) measurement collection; Concepts, use cases and requirements

• TS 28.405: Quality of Experience (QoE) measurement collection; Control and configuration

• TS 28.406: Quality of Experience (QoE) measurement collection; Information definition and transport

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=760058

21.1.8 Network Resource Model (NRM) enhancement

820032

NRM enhancements

eNRM

S5

SP-190140

Jing Ping, Nokia

Summary based on the input provided by Nokia, Nokia Shanghai Bell in SP-201117.

This Work Item extends the 5G Network Resource Model to support the Service-Based Architecture (SBA) of 5G Core (5GC) and several new features of NG Radio Access Network (NG-RAN), together with enhancements of the stage 3 Solution Set (SS).

1. Support of 5GC Service-Based Architecture (SBA)

In the Rel-16 NRM, ManagedNFService InformationObjectClass (IOC) is introduced to represent a Network Function (NF) Service as defined in TS 23.501. This enhancement enables configuration management, performance management, fault management, state management, as well as lifecycle management on more granular NF Service level.

Figure 1 shows containment and inheritance relationship between the ManagedNFService IOC and other existing NRM IOCs (defined in TS 28.622 [1]).

Figure 1: Managed NF Service NRM fragment diagram

In addition, TS 28.541 [3] is enhanced to support NF Service configuration and registration.

2. Support of model driven approach

To align with the Service Based Management Architecture (SBMA) since Rel-15, configurable Performance Management (PM), Fault Management (FM), TM (Trace Management), etc., are introduced to fully support a model driven approach. Several NRM fragments were added in TS 28.622 [1] (stage 2 definition) and TS 28.623 [2] (stage 3 definition), including Performance measurement control NRM fragment, Measurement threshold monitoring control fragment, Heartbeat notification control fragment, Notification subscription control fragment and Trace control NRM fragment. Please see the overall diagram below.

Figure 2: Overall diagram of NRM fragment for FM, PM, TM control

Note: Managed Entity can be a subnetwork, managed network element or network function

3. Support of NG RAN and 5GC features

The 5G NRM is extended to support new or existing features or functionalities of NG RAN and 5GC, e.g. Remote Interference Management, Radio Resource Management policy for radio resources sharing between network slices and operators, New Radio (NR) Automatic Neighbour Relation (NAR), QoS monitoring, configurable 5QI, and transport related information model to support end to end network slice management. Refer to TS 28.541[3]

4. Enhancement of stage 3 codes to follow style guideline

Refact stage 3 YAML and YANG codes in TS 28.541[3] and 28.623[2] to align with new code style guideline defined in TS 32.158 [4] and TS 32.160 [5].

5. Publication and validation in 3GPP Forge

Stage 3 codes, including YAML and YANG solution sets, are uploaded to 3GPP Forge for validation and the OpenAPI code (including YAML code defined NRM) and YANG code is published. Please refer the below link for the SA5 Forge repository: https://forge.3gpp.org/rep/sa5/data-models

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=820032

[1] TS 28.622 "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)"

[2] TS 28.623 "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions"

[3] TS 28.541: “Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and Stage 3”.

[4] TS 32.158: "Management and orchestration; Design rules for REpresentational State Transfer (REST) Solution Sets (SS) ".

[5] TS 32.160: “Management and orchestration; Management service template”.

21.2 Charging Management

21.2.1 Charging Enhancement of 5GC interworking with EPC

820031

Charging Enhancement of 5GC interworking with EPC

5GIEPC_CH

S5

SP-181067

Chen Shan, Huawei

Summary based on the input provided by Huawei in SP-190855.

The WI 5GIEPC_CH is the enhancement of the WI 5GS_Ph1-SBI_CH and 5GS_Ph1-DCH (handover with N26 scenario) on charging aspect of 5GC interworking with EPC, to specify procedure, parameter and Open API impact for the handover cancel and handover without N26 scenarios.

Stage 2 work on WI 5GIEPC_CH for TS 32.255 [1] and TS 32.290 [2]:

– New message flow for EPS to 5GS handover for roaming in Home routed scenario, reflecting the "Visited created Charging Id, Home provided Charging ID" conveyed between VPLMN and HPLMN, and their use within each PLMN.

– Definition of charging information for interworking with EPC: use of 5G attributes and CDR fields extended with EPC specific ones in the new Interworking Annex.

– Handover triggers for handover cancel and handover without N26 scenarios.

– Stage 3 work on WI 5GIEPC_CH for 32.291 [3] and 32.298 [4]:

– TS 32.291 Nchf_ConvergedCharging API

– Extensions of Data model

– Update OpenAPI

– TS 32.298 ASN.1 CHF CDR with "charging Ids" and extended EPC parameters

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=820031

[1] TS 32.255: "5G data connectivity domain charging"

[2] TS 32.290: "5G system; Services, operations and procedures of charging using Service Based Interface (SBI)"

[3] TS 32.291: "5G system; Charging service, stage 3"

[4] TS 32.298: "Charging Data Record (CDR) parameter description"

21.3 Other charging and management items

The other charging and management items are reported under the Feature they relate to.

E.g. " Charging Aspect for 5WWC" is reported under "5WWC" rather than under "Charging".