The goal of the use case is to enable communication service quality assurance and optimization for the set of services provided by the network to certain group (category) of UEs. For example, the set can include the communication services provided via certain NSI(s) or to IoT devices in certain area. The group of NG-RAN and 5GC nodes (deployed and active), which are essential for the set of E2E services, provide provisioning and PM management services. It is also assumed that the providers of the related NSI / NSSI provisioning and PM management services are deployed and active. The management system is consuming the afore mentioned management services either directly or through proxy nodes that re-expose the management services; the management system is aware of the performance requirements imposed on the set of communication services. The management system is collecting the service experience information and monitoring the key performance indicators, KPIs, related to the targeted services. Analytics hosted by the MDAF may be utilized for processing of the network data to derive and analyse the KPIs. If the service quality assurance and optimization function detects performance degradation the 3GPP management system may continuously modify the configuration parameters in the corresponding NG-RAN and 5GC nodes and NSI(s)/NSSI(s), to satisfy the SLA requirement. In case that changes of communication service SLS are needed, those changes may result as input to the 3GPP management system. If the network performance does not recover or improve, the management system may further adjust the network configuration, or roll back to the previous configuration. At all times the management system continues to collect the network data and to monitor the performance indicators.

The goal of this use case is to assure the SLSs (Service Level Specifications) for a particular communication service is crucial for the 5G network management. The negotiated SLS for a particular communication service should be assured in an autonomous way. 3GPP management system can be leveraged to enable autonomous SLS assurance for a deployed communication service. 3GPP management system can collect QoE data, related to network slice and applications, from NWDAF. Since the data collected will relate to network slice and a single NSI may be serving multiple communication services, the corresponding QoE data for the target communication service needs to be ascertained. Once the QoE data for a communication service is known, the SLS breach can also be ascertained. If the SLS is breached, the root cause analysis is performed to find the cause for SLS breach. Depending on the location of cause (at RAN or at, 5GC), remedial actions will be initiated to mitigate the SLS breach and network optimization is done so that the negotiated SLS can be assured. The QoE analytical data from NWDAF is per Application for an NSI. It is crucial to derive which communication service is associated to the QoE data from the data received from NWDAF in order to ascertain the SLS breach.

The goal of this use case is to describe 5G Core management to assure compliance to SLSs (Service Level Specifications) for a communication service in 3GPP management system. 3GPP management system receives the SLS requirements that required by CSP or NOP. 3GPP management system is capable to translate e2e SLS goal and set the 5GC goal(s) of SLS related to 5GC and activate a closed control loop for service assurance goal(s). To fulfill the SLS requirements, 3GPP management system is capable to configure the management resource and 5GC network functions (e.g. AMF, SMF, NWDAF) to monitor measurements and fault alarms that are relevant to the SLS. Since, for example, a network slice for eMBB can provide multiple communications services, one or multiple closed control loops for service assurance goals are set, and the network resource and performance measurements which are relevant to the SLS. During the process of service assurance of 5GC, the 5GC domain MDAS provider can be used to provide analysis of 5GC related network resource, virtual resources and performance assurance related to SLS in 5GC. The 5GC domain analysis report may be provided to 3GPP management system as part of the analysis result(s) of 5GC SLS. Together with the report from NWDAF, performance measurements and fault alarms related to 5GC NFs are also available for analysis of any potential service degradation.

The goal of this use case is to enable the MnS consumer to control the communication service SLS assurance closed control loop(s) (e.g. specify the SLS to be assured, enable/disable the SLS assurance, specify the assurance time for certain SLS) and obtain the SLS fulfilment information provided by MnS producer. It is assumed that the MnS producer maintains SLS assurance closed control loops for multiple SLSs. The detailed SLSs for network slice assurance are captured in ServiceProfile (e.g. latency, Throughput) associated to network slice and the detailed SLS for network slice subnet assurance are captured in SliceProfile (e.g. latency, Throughput) associated to network slice subnet. When an MnS producer receives an SLS assurance closed control loops(s) creation request with SLS assurance requirements for certain managed Entity (i.e. network slice, network slice subnet) from an MnS consumer, the SLS assurance requirements may include information of which SLS should be assured (e.g. latency should be assured), the SLS assurance granularity (e.g. per UE, per Network Slice, per S-NSSAI), SLS assurance condition (e.g. SLS assurance duration time, SLS assurance fulfilment requirements (e.g. the ratio of the SLS assurance time during the whole service usage time) ), the MnS producer create SLS closed control loop managed object instance contained by the specified managed Entity (i.e. NetworkSlice, NetworkSliceSubnet) and configures the received SLS assurance requirements in the created SLS closed control loop managed object instances. The MnS producer performs the network and/or service management to satisfy the SLS assurance requirements by adjusting the network (e.g. adjust the network topology, configure RRM policy) to satisfy the required SLS assurance requirements. During the SLS assurance closed control loop operation phase, the MnS consumer may request MnS producer to enable/disable the corresponding SLS assurance or update the SLS assurance requirements if needed, then MnS producer update corresponding the SLS assurance closed control loop managed object instance to ensure the MnS producer perform the SLS assurance closed control loop based on the new request. During the SLS assurance closed control loop operation phase, the MnS producer may report the SLS assurance closed control loop progress information and fulfilment information (e.g. SLS assurance requirements is satisfied or not) to the MnS consumer.

The goal of this use case is to identify the management of network prediction assisted SLS communication service assurance. The SLS related to a particular communication service can be assured by considering the predicted network resource usage and performance (e.g. latency, throughtput) for the managed entity (e.g. network slice, network slice subnet) associated with the SLS closed control loop managed object instance within a certain time frame. The 3GPP management system will have the most comprehensive network operating data, such as network resource utilization, network performance parameters in different periods, which would include different collection granularities (e.g. per UE, per S-NSSAI) and have corresponding performance parameters respectively in NG-RAN or 5GC. By introducing MDAS and NWDAF into both the management system and core network, it is possible that the network operating data can be the input of the closeloop to fulfil SLS requirements from CSP or NOP. The MDAS could predict the network resource usage and performance for the whole network as well as different domain, for example, the MDAS could predict the resource utilization and throughtput for the NSSI in the NG-RAN within a certain time period. In a certain period of time, the current network condition is good enough to satisfy the SLS requirements. By introducing the prediction results from the analysis of MDAF and NWDAF, the historical data shows that the network will experience a traffic burst in certain area and certain time which can cause network resource shortage and performance degradation. This predictional results can directly trigger the MDAF to analyse the root cause for performance degradation and analyse the solution which is used for making the network desicion such as reconfiguration and resource reallocation before the predicted traffic burst time. And the resource reallocation could be conducted between the multiple NSIs or NSSIs, for example, there are different network slices in the network for SLS communication service assurance, the resources between network slices could be adjusted dynamically based on the MDAF analysis results. Similarly, in office area, the network will not active during holiday but will have network surges on working day, the network prediction can also trigger resource release and network function reconfiguration. This can not only save network operating costs on holiday but also achieve the goal of network service assurance on working day.

The goal of this use case is to provide the consumer of an assurance closed loop the ability to limit actions the assurance closed loop can execute. This renders the assurance closed loop taking action (configuration of MoI attributes) that are within the limits of the scope as defined by the consumer. Assurance closed loops have a defined assurance goal related to a communication service SLS may execute various actions in the deployed operator network. There may be cases in which two or more assurance closed loops can execute the same or related set of actions on a managed entity. For example, assurance closed loops ACL1 and ACL2 for coverage optimization running in neighbouring RAN domains may take independent decision on the radio signal strength and azimuth to optimize the coverage. These assurance closed loops therefore may have the capability to cause a conflict with both simultaneously changing the azimuth to address a coverage-hole thereby causing an unnecessary coverage-overlap instead. An authorized coordinating entity (authorized common consumer of the two ACL), should be able to configure the closed loops in a way that such occurrences are minimized. To coordinate the execution of multiple such assurance closed loops in the system the common authorized consumer of the assurance closed loop limits the set of actions of the assurance closed loops to avoid possible conflicts between the two or more assurance closed loops. In the example above: The authorized consumer of an assurance closed loops may limit the coverage optimization configurations signal strength and azimuth configurations to be done only by ACL1. The 3GPP management system shall therefore provide the ability to limit action capabilities (possible configurations of an MoI attributes) that an assurance closed loop can take, this can be for example via operational policy configurations. The MnS consumer obtains the allowed action capabilities (configurations that assurance closed loops could execute on an managed entitiy) from the MnS producer. The MnS consumer may then internally compare the action capabilities allowed that can be taken by a set of assurance closed loops to determine if possible conflicts exist. If conflicts are found, and the MnS consumer determines a possible resolution by limiting the action capabilities of a set of assurance closed loops, then it requests the MnS producer to limit the set of action capabilities, for example: by configuring new operational policies.

The goal of this use case is to provide the consumer of an assurance closed loop the ability to set conditions (example threshold crossings) in the 3GPP management system that when met, trigger changes in ACCL state (enable or diable an ACCL). This implies that an ACCL may be activated or deactivated if the set condition in the 3GPP network is met (example: the threshold is crossed). Assurance closed loops may be required to run at different times and network conditions in the 3GPP network. For example, an ACCL related to handover optimization may only execute when the handover failure crosses a certain threshold. Similarly, an ACCL managing energy efficiency may be disabled when the network is overloaded beyond a certain threshold. These conditions (network overload, handover failure threshold crossing) can therefore be associated with a change in state (enable/disable) of an ACCL to further support autonomy of the 3GPP management domain. An authorized entity (authorized consumer of the ACCL), for example, another closed loop or operator, should be able to configure the condition and its association with an ACCL state transition (enable/disable) in the 3GPP management domain. The 3GPP management system shall therefore provide the ability to configure conditions and associate them with the state transition of an ACCL. The 3GPP management system then configure appropriate listeners to monitor the configured threshold crossing and once triggered execute a state transition (enable/disable) of the associated ACCL. The MnS consumer obtains the possible conditions as well as the possible ACCL state transitions they can be associated with. The MnS consumer may then configure condition in the 3GPP network. When the threshold crossing notification is received the MnS producer it executes the associated state transition (enable/disable) of the ACCL.

Assurance closed loops have a defined goal related to a communication service SLS may execute various actions in the deployed operator network. To fully understand and trust the execution of such an assurance closed loop in the system, The MnS consumer of the assurance closed loop may want to supervise the execution of the assurance closed loop at "pause point" during the Execute step of the closed loop. At this pause point the consumer is enabled to review the available information. MnS consumer can set the pause point before the closed loop is running or when the closed loop is de-activated. The 3GPP management system provides the ability to enable or disable such "pause point" during the Execute step of the assurance closed loop. At a pause point, when notification is sent to the MnS consumer, the consumer of the control loop can enable pausing the execution of the control. The assurance closed loop pause point can be defined by the assurance closed loop and set for "Execute" step only. The MnS consumer obtain the pause point capabilities for assurance closed loop(s) from the MnS producer. For example, for NR coverage optimization closed loop, the pause point can be coverage adjustment action execution. Based on the pause capabilities, MnS consumer requests the MnS producer to enable pause point for an assurance closed loop. When a pause point is reached, the flow of the assurance closed loop is paused and the authorized MnS consumer is informed with the pause information. When the notified MnS consumer sends a resume request, the assurance closed loop flow will continue to execute to the next step of the assurance closed loop. For example, when a pause point at coverage adjustment execute step is enabled, the MnS producer will not execute coverage adjustment action and instead inform the authorized MnS consumer that coverage adjustment action is determined and wait for approval.

• If the coverage adjustment action is approved by the MnS consumer, the MnS consumer will request the MnS producer to resume. Then MnS producer can continue to execute the coverage adjustment action.
• If the coverage adjustment action is not approved by the MnS consumer, the MnS consumer requests MnS producer to reject execution of the coverage adjustment action.

The goal of this use case is to provide the consumer of an assurance closed loop the ability to set targets (example location, UEs) per assurance goal(s) of an ACCL. This implies that an ACCL will be assuring goal(s) pertaining to the configured targets only. The SLS requirement may come for a particular location. It would be beneficial if the ACL can target a particular location while assuring the SLS. Strict SLS assurance for a service can be provided using ACL for a high-valued vertical customer present in a particular location. This will require configuring the ACL accordingly and would need ACL to collect the performance measurements, while monitoring the network, for the same target location. The example of this may include SP assuring assurance goal of guaranteed throughput for an eMBB service inside a customer premises.