Content for  TS 28.104  Word version:  18.3.0

The MDA request and control allow any authorized MDA MnS consumer to request management data analytics.

The MDA MnS consumer can request the MDA MnS producer to provide MDA output for a list of specified MDA type of analytics, i.e. MDA type, which corresponds to an MDA capability, which is to support analytics for a set of data or analytics for a certain PM, KPI, trace or QoE data. The MDA MnS consumer may introduce control attributes related to the MDA output with respect to the geographical location (i.e. area scope) and/or the target objects, e.g. managed elements, time schedule for obtaining an MDA output, time conditions related to the preparation of MDA output (i.e. time schedule for start, end and duration of analytics, etc.), and potential filter conditions to be met before an MDA output is made available, e.g. load or delay threshold crossing related to a target object. The geographical location indicates an area of interest for obtaining MDA output and/or target objects include affected objects or objects of interest for obtaining MDA output. The MDA MnS consumer may control the MDA output attributes related to, e.g. time schedule, geographical location, target objects, etc., and has the capability to modify them at any point in time. The MDA MnS consumer can request the MDA MnS producer to generate an MDA output that contains numeric output results, e.g. average, normal distribution, etc., recommendation options, e.g. potential handover target cells, or root cause analysis, e.g. alarm prediction. The MDA MnS consumer can be informed with an acknowledgment if the request was successful. If the request was not successful, the consumer is informed about potential errors indicating the reasons. The attributes related to time can provide the flexibility to configure the MDA reporting control to provide analytics indefinitely. The MDA MnS consumer should delete the MDA request MOI after the requested analytics has been performed. The MDA MnS consumer can also deactivate the MDA reporting control request once it is no longer needed.

Following a successful MDA request any authorized MDA MnS consumer can obtain management data analytics from the corresponding MDA MnS producer. The MDA MnS consumer can control the MDA output by modifying the attributes related to the MDA request at any point in time.

The MDA MnS producer allow consumers to obtain MDA output when the conditions indicated in the MDA request are met. The level of details and granularity of MDA output results would depend on the MDA request and nature of MDA capability. Therefore an MDA output can vary in complexity and may contain one or more MDA results, which may be: i) numeric, e.g. average, etc.; ii) recommendation options, e.g. potential handover target cells; or iii) root cause analysis, e.g. alarm prediction. These results may be related to one or more MDA types, which correspond to MDA capabilities, and can also contain information regarding the time schedule or the validity time of the provided MDA output. MDA MnS producer may allow consumers to request and obtain different MDA output results. The MDA MnS producer may also allow consumers to obtain information regarding the geographical location and/or the target objects, e.g. managed elements, related to the provided MDA result - from the corresponding element. The MDA MnS producer may allow consumers options to obtain MDA output results either by pulling or pushing mechanisms. Any MDA output may be obtained once it is prepared or when the specified MDA request and control conditions are met.

The MDA MnS consumer may configure the MDA request in the MDA MnS producer to avoid providing recommendation on certain entities.

When MDA provides prescriptive recommendations, the recommendations may include actions targeted towards entities for which the MDA MnS consumer cannot execute actions. In some cases, this may cause erroneous behaviour. As an example, ACCL (Assurance Closed Control Loop) may receive recommendations from MDA which are in conflict with the ACCL "CLDisallowedList" indicating the objects for which the ACCL should not take any actions. If ACCL is only able to act on a subset of the recommendations received from MDA, ACCL will not be able to implement the full change as recommended by MDA. This could result in an incomplete solution to an issue. At worst, this could cause imbalance or oscillation within the network. As another example, the recommendations provided by EnergySavingAnalysis may recommend multiple changes across the network which are intended to balance the network load as efficiently as possible to reduce energy usage. However, the MDA MnS consumer may not be authorized to change/configure all of the recommended RAN and/or CN nodes. This is unlikely to attain the expected reduction in energy usage and may cause imbalanced traffic in the network. These problems may be avoided if the MDA MnS consumer could specify a set of objects for which no actions can be taken and thus no recommendations should be provided. The MDA MnS consumer could also indicate the objects, for which it does not want to receive recommendations, based on a geographical area. Recommendations should not be provided for the object(s) in that geographical area.