The CSP needs to meet the CSC expectations on automation as well as internal goals on CAPEX and OPEX efficiency. The CSP has access to capabilities, procedures and tools that can address both CAPEX and OPEX in the provisioning and management of communication services to their customers (CSC). The CSC expects the CSP to offer a variety of communication services including business critical communication services that allow the CSC (e.g. Enterprise) to run their applications in a predictable manner [2]. Hence automation of the onboarding of the CSC application, which will use communication services provided by the CSP, on a 5GS, is a requirement to meet the following needs:

• reduce the complexity for a CSC application to be on-boarded on a 5GS,
• improve the network performance over time, based on predicting communication service behaviour,
• assure the target goals for a CSC, and
• reduce the cost ownership through automation.

During the operation of the communication service the CSP provides assurance of service quality requirements and CSP meets the CSC expectations on automation as well as internal goals on CAPEX and OPEX efficiency. REQ-CSA_NSA-FUN-01 REQ-CSA_NSA-FUN-02 REQ-CSA_NSA-FUN-03 REQ-CSA_NSA-FUN-04

In this scenario, it is assumed that the SLA's for the two communication services will allow for them to share resources, for example RAN resources. The management systems CS-Assurance service receives the request from Order Care and using a MDAS CS preparation assistance service, explores and evaluates communication service realisation and impact on other communication services, if any. Once the Order Care has committed to an SLA with a CSC, the management system activates the communication service. As the communication service operates, a management service for communication service assurance, CSA, continuously monitors the SLA fulfilment using MDAS, PM assurance services [3] including and core network NWDAF QoE analytics service, if available. Based on goals for SLA fulfilment, or other KPIs, the CSA service may initiate an action when SLA goals are not met, be that over- or under fulfilment. The CSA service may use an MDAS to assist in selecting proper action and how to best execute the action. The CSA service triggers the action by using provisioning service [4] towards RAN, transport and core network and monitors the effect of the change. REQ-CSIA_CON-01: REQ-CSIA_CON-02:

Once a request for a communication service is received, the 3GPP management system needs to identify the network resources to be used by this service in order to do service assurance. For example, during the feasibility study, in order to assure the performance, the 3GPP management system should be able to determine the network availability for that service. This could be done by informing the MDAS provider about the network requirements and check if the requirements can be met with the available network resources. MDAS provider may already have network requirement for a given service requirement, which is obtained by the historical analysis using offline or online monitoring of network resource usage of similar services. The 3GPP management system may check the feasibility of provisioning the communication services by using the existing network, and if feasible, provision the communication services using that network to go to the operational phase If the network requirement cannot be determined (e.g. not sufficient prior data), the 3GPP management system may assign certain amount of the initial network resources and limit the number of users admitted by configuring the appropriate CN functions. The resource usage information and the services using those resources in a given time period with their performance (e.g. delay) is monitored by the 3GPP management system for different number of UEs to learn the network resource requirement for different service requirements. This data could be used to determine network requirements for future service requests during the provisioning phase or to adjust network resources to reflect the changing service demands for the already admitted communication services. It may be a continuous learning process in the run-time phase since service degradation could happen due to various reasons and network resources may need to be adjusted to address such situations. REQ-CSA_RR-CON-01 REQ-CSA_RR-CON-02

The goal is to enable the 3GPP management system to take early action to prevent service degradation. The 3GPP management system configures the control plane functions (e.g. NWDAF) so as to report potential service degradation according to the SLS. Service load can be determined by considering both NF(s) load in 5GC and network utilization in access network. If the service degradation occurs or is predicted when the network capacity is decreased, network capacity could be increased to solve the issue. Therefore, it is necessary for the 3GPP management system to configure the 5GC functions such that in the event of a potential service degradation or prediction of overloading, a notification is sent to the 3GPP management system. This can be done by configuring the overloading conditions (e.g. triggering parameters) in the 5GC functions for a selected service. The 3GPP management system could configure the 5GC functions to trigger when the service load is increased or predicted to be increased beyond a certain threshold level. The 3GPP management system could then increase the network capacity or use an MDAS to find a proper solution. Similarly, when the network resources are underutilized the 3GPP management system could decrease the network capacity. REQ-CSA_RR-CON-01 REQ-CSA_RR-CON-02 REQ-CSA_RR-CON-03