Content for TS 28.104 Word version: 19.1.0
6 MDA in management loop
6.1 MDA role in the management loop
6.2 MDA role in the management loop for service assurance
6.3 MDA role in cross-domain service assurance
...
...
6 MDA in management loop p. 20
6.1 MDA role in the management loop p. 20
Intelligence in Analytics, played by MDA, in the management loop which can be open loop (operator controlled) or closed loop (autonomous) see TS 28.535) as shown in Figure 6.1-1, generates value by processing and analysis of management and network data, where AI and ML techniques may be utilized (see TS 28.105).
The management loop constitutes of a number of elements including analytics, these elements are briefly described below:
Observation:
The observation of the managed networks and services. It involves monitoring and collection of events, status and performance information of the managed networks and services, and providing the data.
Analytics:
The data analytics capabilities for the managed networks and services. MDA plays the role of Analytics in the management loop. It prepares, processes, and analyses the collected data or time series of the collected data related to the managed networks and services. MDA reports may contain root cause analysis of ongoing issues, predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service demands.
Decision:
The decision making element for the management actions applied to the managed networks and services. The decisions and subsequent management actions are based on the analytics reports (provided by MDA) and other management data (e.g., historical decisions). The decision may be made by the consumer of MDAS (in the closed management control loop), or by a human operator (in the case of open management loop). The decision may include e.g. what actions to take, and when to take the actions.
Execution:
The execution element of management actions. During the execution step, the actions are applied to the managed networks and services, and the results of the executed actions are reported (e.g. notifications, logs).
6.2 MDA role in the management loop for service assurance p. 21
MDA represents Analytics roles in the management control loop for communications service assurance TS 28.535. The management and control of resources used by a communication service and the assurance of the communication service level agreements (e.g., per SLS) is provided by the management control loop involving different management services produced by the management system, which includes MDA service (MDAS, or MDA MnS). The MDAS (MDA MnS) may be produced based on a combination of information including e.g., the user quality of service experience, network performance and network resource utilization analysis and the SLS.
The MDAS complements other services in the management loop in order to perform SLS communication service assurance. Prior to the operation phase, the MDA role in the management control loop is to prepare, process and analyse the data related to the managed communication service, in order to provide the analytics output (analytics report) which may include prediction and feasibility checks of network resource requirements to meet the SLS.
During the operation phase, the MDA can identify ongoing issues impacting the performance of the communication service as per SLS requirements and identify potential risks caused by potential failure and/or performance degradation. The MDA can also predict the network and service demand to maintain delivery of communication service as per contracted SLS.
6.3 MDA role in cross-domain service assurance p. 21
Cross-domain MDA may base its analysis on the outputs from one or multiple single-domain MDA including analytics output and other input data (e.g., PM and alarm notifications.). To facilitate service assurance the cross-domain MDA may consume output from one or multiple single-domain MDA(s). Figure 6.3-1 shows the simplest case, where a cross-domain MDA consumes the results of single-domain MDA(s).
Figure 6.3-2 shows the case where a cross-domain MDA incorporates the results of single-domain MDA(s) which are embedded within single-domain control loopservice(s). Service assurance control loop servicesmay be performed at single-domain where analytics part is done by MDA.The cross-domain MDA may further leverage the output from one or more single-domain control loop services for the analytics ofthe e2e service.
Figure 6.3-2: Cross-domain MDA based on single-domain control loopservice
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 6.3-3 shows the case where a cross-domain MDA is part of a cross-domain control loop service. Also in this case, cross-domain MDA consumes the results of single-domain MDA(s). Service assurance control loop service may be performed at the cross-domain level in which the analytics is done by MDA. The cross-domain control loop may consume output from one or more multiple single-domain MDA(s) for the e2e service.
Figure 6.3-3: Cross-domain control loop service based on single-domain MDA(s)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 6.3-4 shows another case where a cross-domain MDA is part of a cross-domain control service. In this case, cross-domain MDA consumes the results of single-domain MDA(s) which are embedded within single-domain control service(s). Service assurance control loop service may be conducted at both levels where analytics is done by MDA, i.e. at the cross-domain and single-domain. The cross-domain MDA may consume output from one or more single-domain MDA(s) for the e2e service.
Figure 6.3-4: Cross-domain control loop service based on single-domain control loop service(s)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
