This section presents all the standalone management functionalities. Management aspects related to other features are reported in the relevant section. For instance, OAM for "Industrial IoT" is reported in the section on "Industrial IoT" and not here.

Summary based on the input provided by Ericsson in SP-220308. This Work Item added enhancements to the Closed loop SLS Assurance solution specified in TS 28.535 and TS 28.536. The enhancements add more advanced monitoring solutions that helps an operator to continuously deliver the expected level of communication service quality when deploying a NetworkSlice or a NetworkSliceSubnet. A closed control loop automatically adjusts and optimizes the services provided over an NG-RAN and 5GC network based on the various performance management, QoE input data, and the state of the 5G network, using data analytics. The solution has the following features:

• it can have existing KPI's and measurements as input and make predictions and depending on the parameter(s) to be assured the appropriate KPI's and measurements can be obtained.
• it can use existing provisioning capabilities to perform actions based on predicted goal status and depending on which network characteristics are predicted the appropriate actions can be provisioned
• it can configure assurance goal by extraction of the appropriate parameter values from the ServiceProfile or SliceProfile of the NetworkSlice or NetworkSliceSubnet which service is assured.
• it can collect the assurance goal status of a closed control loop based on domains and depending on which network characteristics are to be assured for a domain the appropriate actions can be provisioned.
• it can ascertain the assurance goal status of a closed control loop based on location and depending on which network characteristics are to be assured the appropriate actions can be provisioned.

The solution separates the goals that a closed control loop needs to fulfil from the results of the operation of a closed control loop. The results (fulfilment status of a goal) for a closed control loop are provided in a report including the observed fulfilment and predicted fulfilment. The goals for a closed control loop are derived from the service requirements that are specified in a ServiceProfile or SliceProfile. To be able to deploy SLS assurance solutions the following objectives are addressed:

• Add new service assurance management related use cases and requirements according to deployment, assurance aspects.
• Enhance the descriptions on closed loop and related interactions which are important for service assurance.
• Describe new information in NRM which support the service assurance.

This work item resulted in several CRs to update the communication services assurance solution specified in TS 28.535 and TS 28.536

Summary based on the input provided by Ericsson in SP-220308. This work item specifies Quality of Experience (QoE) measurement collection in UMTS, LTE and 5G networks. It extended eQoE to support NR. It also added Signalling Based Activation (SBA) for UTRAN and LTE functions. LTE is also aligned with RAN specifications. Functions that are added for NR includes: Management Based Activation (MBA), Deactivation of QoE measurement collection job, temporary stop and restart during RAN overload and new NR service Virtual Reality (VR). Signalling Based Activation and Handling QoE measurement collection during handover are also added. Management Based Activation allows for QoE measurement collection from UEs in a specified area. The operator has capability to deactivate the collection of QoE measurement job. Temporary stop and restart during RAN overload: provides capability to RAN that temporarily stops and restarts QoE measurement reporting at RAN overload. By supporting NR service Virtual Reality the QoE measurements for Virtual Reality can also be collected. Signalling Based Activation provides capability to request collection of end user service performance information for one specific UE. Signalling Based Activation is also added for UTRAN and LTE. Handling QoE measurement collection during handover provides capability to handle QoE measurement collection during handover. QMCjob added to the network resource information to enable QoE measurement collection between an Management Service (MnS) producer and Management Service consumer in deployment scenarios using the Service Based Management.

Summary based on the input provided by Ericsson in SP-210310. This work item specifies Plug and Connect support for NFs. It extended Plug and Connect (PnC) to support Service Based Architecture (SBMA). It added support of IPv6, DHCPv6 and Dual stack and extended PnC to be useful for all generations of NEs, e.g., NR and LTE. Support of virtualized nodes are not in the scope of this work item. PnC is the procedure by which a NE gets basic connectivity information after it is powered up and gets connected to its management system. After PnC, Self-Configuration procedures are used to complete Plug and Play (PnP). This work item only covers PnC. A new Rel-18 work item "Self-configurations of RAN NEs" was created to document the self-configuration management of RAN NEs of NR and future RAT technology if possible in the context of SBMA. Prior to this work item, 3GPP PnP specifications do not support NR. Those specifications restrict the PnP to eNB only. They also miss some updates from IETF RFCs regarding IPv6 and DHCPv6 support. There are three new specifications for PnC are created as result of this work item. They are the full set of specifications covering stage 1 (TS 28.314), stage 2 (TS 28.315), and stage 3 (TS 28.316) of PnC. The new specifications added support of IPv6, DHCPv6 and dual stack for PnC and extended the PnC to support SBMA. The restriction to PnC on eNB was removed, the scope of the PnC is extended to support network element (NE) including LTE and NR radio network nodes. Other types of nodes might also be compliant and use this PnC procedure. The same level of security support as for eNB is provided in the new specifications for NE. This work item also removed PnC clauses for 5G from TS 28.313 and referred them to the new specifications TS 28.314 and TS 28.315.

Summary based on the input provided by Ericsson in SP-210311. This WI is an enhancement of the Rel-16 WI "5GMDT". During release 17, the MDT measurement configuration and reporting enhancement in NR has been defined to be aligned with RAN2/RAN3/CT4. The MDT (minimization of driving test) feature in NR has been defined in RAN2and RAN3. The e_5GMDT is part of the MDT feature from management point of view. This e-5GMDT work item has added the following features and addressed the following issues in release 17:

• MDT measurement configuration and reporting in a RAN split architecture in NR
• The MR-DC including EN-DC related configuration and measurement impacts from the management point of view.
• Measurement and configuration enhancement for logged and immediate MDT.
• Enhancement of reporting to be aligned with internode communication specified in RAN2 and RAN3

This WID mainly focuses on enhancement of management aspects 5G MOCN network sharing, including clarification of use cases, requirements and enhancement of NR NRM. It evaluates and specifies corresponding management features to support 5G network sharing scenarios in release 17. The SID is to make recommendations and potential enhancement for NR NRM to support MOCN network sharing scenarios This WID, management aspects of network sharing, is primarily to specify the concept, requirements and use cases for 5G MOCN network sharing scenarios on management aspects. This WID specifies which information or parameters in configuration management with different authorities need to be configured per operator, such as adding PLMN granularity for number of active UEs measurements and adding PLMN granularity for Radio resource utilization measurements. What's more, one of the important objectives is to enhance NR NRM to fulfil the requirements of 5G MOCN network sharing scenarios (including all NG-RAN deployment scenarios). Detailed scenarios have been captured in SID of FS_MANS including potential requirements and solutions. Evaluate existing trace/PM/FM solutions to ensure that the 5G MOCN network sharing is supported. Based on MANS, normative work is specified in TS 32.130, TS 28.552, TS 28.554 and TS 28.541.

Summary based on the input provided by Huawei in SP-220566. 5G network and network slicing management supports a service-based management architecture where deployed management service instances are exposed by management service producers. This WI adds the capability for management service consumers to discover the exposed management services in the 3GPP management system. The high-level requirement is described in TS 28.530. The management service producer profile is described in TS 28.533. Use cases and requirements are described in TS 28.537. The Network Resource Model in TS 28.622 is extended to add new data to support discovery of management services. OpenAPI and YANG solution sets in TS 28.623 are extended to comply with the extended Network Resource Model.

Summary based on the input provided by Huawei in SP-220567. Management of the enhanced tenant concept provides conceptual description on tenant as MnS consumer in 3GPP management system. The management system is required to provide management capability for reporting performance monitoring and alarm notifications for the tenant based on management and orchestration for network slicing. The management and orchestration for network slicing supports performance measurement per S-NSSAI (see TS 28.552) and alarm notification with slice identifier(s). The clarification is provided in this work item, to provide the conceptual description in 28.533 [] and TS 28.532 on how those management information are provided by 3GPP management system to vertical MnS consumers. So the clarifications to use MnS for performance monitoring and alarm notifications are provided in TS 28.533, TS 28.532 and TS 28.552. Management of the enhanced tenant concept provides some discussion and not pursued change requests in network slice NRM on tenant information IOC and use in slice NRM in TS 28.541. Those changes are related to the provisioning service exposed to tenant MnS consumers, which are also in the scope of ongoing R18 study item on management capability exposure in SA5.

Summary based on the input provided by Huawei in SP-220568. An intent driven system will be able to learn the behaviour of networks and services and allows a customer to provide the desired state as intent (an intent specifies the expectations including requirements, goals and constraints for a specific service or network management workflow), without detailed knowledge of how to get to the desired state. Thus, the intent driven management is introduced to reduce the complexity of management without getting into the intricate detail of the underlying network resources. This WI specifies the concept, use cases, requirements and solutions for the intent driven management for service or network management. Following content is specified in TS 28.312.