Avoidance and arbitration in conflict mitigation functionality

Abstract

Disclosed herein is a method. The method includes receiving, at a Conflict Mitigation (ConMit) module, a configuration change command from one or more network applications. The method also includes detecting, by the ConMit module, whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix. Moreover, the method includes selectively accepting or rejecting, by the ConMit module, the received configuration change command based on a plurality of parameters and the detected conflict in response to detecting the conflict. The plurality of parameters comprises one or more operator policies.

Description

AVOIDANCE AND ARBITRATION IN CONFLICT MITIGATIONFUNCTIONALITYCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to India Provisional Application No. 202411064017, filed on August 24, 2024, and India Non-Pro visional Application No. 202411064017, filed on April 29, 2025. the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to avoidance and arbitration in conflict mitigation functionality.BACKGROUND

[0003] The information disclosed in this background section is only for an enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgment or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] In a network, multiple network applications (such as Radio Access Network (RAN) applications (rApps) and extensible applications (xApps)) may be deployed to optimize and manage various network functions. Such network applications interact with a RAN Intelligent Controller (RIC) using standardized interfaces, such as an E2 interface.

[0005] When such multiple network applications are deployed in the network, the likelihood that decisions made by one network application may conflict with other network applications isincreased. Such conflicts may adversely affect network performance and reliability. The decisions made by the network applications may be in terms of 01 configurations, Al policies, or E2 configurations. The conflicts between the decisions may arise due to differing objectives or overlapping control actions among the network applications.SUMMARY

[0006] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the present disclosure nor is it intended to determine the scope of the disclosure.

[0007] The present disclosure addresses a technical problem related to arbitration of potential conflicts that may arise from configuration change commands issued by multiple network applications.

[0008] According to one embodiment of the present disclosure, a method is disclosed. The method includes receiving a configuration change command from one or more network applications. The configuration change command is received at a Conflict Mitigation (ConMit) module. The method also includes detecting whether the received configuration change command conflicts with one or more configurations received within a coherence time. The ConMit module detects the conflict based on at least one of a dependency graph or a conflict mitigation matrix. Moreover, the method includes selectively accepting or rejecting the received configuration change command. The ConMit module selectively accepts or rejects the received configuration change command based on a plurality of parameters and the detected conflict. The ConMit module selectively accepts or rejects the received configuration changecommand in response to detecting the conflict. The plurality of parameters comprises one or more operator policies.

[0009] According to another embodiment of the present disclosure, an apparatus is disclosed. The apparatus is configured to receive a configuration change command from one or more network applications. The apparatus is also configured to detect whether the received configuration change command conflicts with one or more configurations received within a coherence time. The apparatus detects the conflict based on at least one of a dependency graph or a conflict mitigation matrix. Moreover, the apparatus is configured to selectively accept or reject the received configuration change command based on a plurality’ of parameters and the detected conflict. The apparatus selectively accepts or rejects the received configuration change command in response to detecting the conflict. The plurality of parameters comprises one or more operator policies.

[0010] According to another embodiment of the present disclosure, a non- transitory computer- readable medium is disclosed. The non-transitory computer-readable medium stores instructions. The instructions comprise one or more instructions that are executed by a conflict mitigation (ConMit) module. The ConMit module comprises one or more processors. The instructions cause the one or more processors to receive a configuration change command from one or more network applications. The one or more instructions also cause the one or more processors to detect whether the received configuration change command conflicts with one or more configurations received within a coherence time. The one or more processors detect the conflict based on at least one of a dependency graph or a conflict mitigation matrix. Moreover, the instructions also cause the one or more processors to selectively accept or reject the received configuration change command based on a plurality of parameters and the detected conflict.The one or more processors selectively accept or reject the received configuration change command in response to detecting the conflict. The plurality of parameters comprises one or more operator policies.BRIEF DESCRIPTION OF DRAWINGS

[0011] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:FIG. 1 illustrates a schematic block diagram of an example environment for implementation of a Conflict Mitigation (ConMit) module, in accordance with an embodiment of the present disclosure;FIG. 2 illustrates a flowchart depicting a method for arbitration and avoidance of potential conflicts, in accordance with an embodiment of the present disclosure;FIG. 3 illustrates a flowchart depicting a method for avoidance of the potential conflicts, in accordance with an embodiment of the present disclosure;FIG. 4 illustrates a flowchart depicting a method for transmitting a subscription-based notification to one or more network applications, in accordance with an embodiment of the present disclosure;FIG. 5 illustrates a flowchart depicting a method for transmitting a configuration guidance response to the one or more network applications, in accordance with an embodiment of the present disclosure; andFIG. 6 illustrates an embodiment of a device, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0012] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0013] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods should not limiting their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0014] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit thedisclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0015] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and "an” are intended to include one or more items, and may be used interchangeably with "one or more.” Also, as used herein, the terms "‘has,” “have,’7“having," “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthennore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B. or both A and B.

[0016] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0017] In the present disclosure, specific tasks may be performed using Artificial Intelligence / Machine Learning (AI / ML) models. An AI / ML model is a model generated using one or more Al technologies, one or more ML algorithms, or both, and generates output data based on input data. This output data is used to perform tasks. Tasks performed using AI / ML models include those generally referred to as intellectual tasks, such as classification, prediction, natural language processing, etc.

[0018] Although Al and ML are explained separately, ML is a technology included in Al. InML, instead of being explicitly programmed for a specific task, systems can improve their performance over time by identifying patterns and making inferences from training data. Typically, the generation of ML models includes data collection, model training, and model inference. Data collection involves gathering and preprocessing data to be used for training and inference. Model training involves developing and validating models using the collected data. Model inference involves applying the trained models to new data to generate new output data and perform tasks.

[0019] Machine learning includes various types of learning methods such as supervised learning, unsupervised learning, reinforcement learning, semi-supervised learning, selfsupervised learning, transudative learning, transfer learning, meta learning, and the like. These types of learning methods can be appropriately selected according to the embodiments. Unless otherwise specified, the application of types not mentioned in this description is not precluded. Additionally, the structure of ML models may vary depending on the embodiments and learning methods, and is not limited to the methods disclosed. Furthermore, ML includes deep learning, which uses models that include neural networks. Deep learning models may include, for example, deep neural networks (DNNs), convolutional neural networks (CNNs), etc.

[0020] It should be noted that the AI / ML models presented hereinafter are examples and are not limited to the illustrated AI / ML models. They can be modified or altered by using different Al or ML algorithms. The configuration of the neural network is not limited to the configuration disclosed in the present disclosure and can be modified.

[0021] Open-Radio Access Network (O-RAN) alliance has introduced a Conflict Mitigation (ConMit) functionality to handle and mitigate conflicts between decisions made by one or morenetwork applications (such as RAN applications (rApps) and extensible applications (xApps)) in a network. For instance, one rApp / xApp might attempt to optimize resource allocation for enhanced throughput, while another might focus on reducing latency, leading to conflicting configuration commands sent to elements of the network. The ConMit functionality has been introduced as part of a Non-Real Time RAN Intelligent Controller (Non-RT RIC) and a NearReal Time RIC (Near-RT RIC). The ConMit functionality primarily includes conflict detection (detecting any conflicts (e.g., a direct, an indirect, or an implicit conflict) with previously applied or accepted Operations, Administration, and Management - Configuration Management (OAM-CM) write configurations), conflict mitigation (using a mitigation policy to identify which configuration to accept or reject), and conflict avoidance (transmitting conflict related information to the rApps / xApps to avoid future conflicts).

[0022] Once a conflict has been detected, the ConMit functionality needs to be able to decide as to which xApp / rApp output may be further processed (for example, sent to RAN / E2 nodes). Furthermore, to avoid future conflicts, there is a need for a mechanism providing feedback to the rApps or xApps which may provide guidance about the conflicts caused. The mechanism may also assist the rApps or the xApps in potentially reducing the conflict instances.

[0023] With respect to the Non-RT RIC, there is a specific need to avoid conflicts between the RAN OAM-CM changes and the Al policy. Currently, there are no standard defined mechanisms available to address the aforesaid requirements.

[0024] The present disclosure provides a solution to the above-mentioned problem(s), as discussed in detail in the forthcoming paragraphs. In one embodiment, the present disclosure proposes that the arbitration of the detected conflicts may be handled based on certain priorities and policies which reflect the operator’s intent. The priorities and policies may includexApps / rApps priority, KPI target, KPI priority. Service Level Assurance (SLA), sendee profiles and slice profiles, as explained in detail in the forthcoming paragraphs.

[0025] FIG. 1 illustrates a schematic block diagram of an example environment 100 for implementation of a Conflict Mitigation (ConMit) module 102, in accordance with an embodiment of the present disclosure. The example environment 100 may include the ConMit module 102, one or more network applications 110-1, ... , 110-n (may be interchangeably referred to as the “network application(s) 1 10” or “the network application 110?’), one or more RAN or E2 nodes 112. In an embodiment, the one or more RAN or E2 nodes 112 may refer to one or more network elements such as base stations, radio units, distributed units, etc. The example environment 100 may correspond to one of the Near-RT RIC, the Non-RT RIC, a Service Management and Orchestration (SMO), a Self-Organizing Networks (SON) server, an Element Management System (EMS), a RAN Commander, and any other centralized platforms capable of hosting a plurality of network applications.

[0026] In an embodiment, the network application(s) 110 may include one of one or more rApps and one or more xApps. The network application(s) 110 may receive one or more network application inputs based on which the network application(s) 110 propose configuration change(s). The one or more network application inputs may include one or more operator policies received from an operator 114 for one or more of the network applications 110. The one or more operator policies may indicate an intent or a target of the operator 114 for the one or more of the network applications 110, as discussed in detail in the forthcoming paragraphs. The one or more network application inputs may also include a configuration parameter to Key Performance Indicator (KPI) mapping table 118-1, as discussed in detail in the forthcoming paragraphs. Additionally, if a network application is a rApp, the rApp may receive Fault,Configuration, Accounting, Performance, and Security (FCAPS) details in the Non-RT RIC.Alternatively, if the network application 110 may correspond to an xApp, and the xApp may receive data from the one or more E2 nodes 1 12 via the Near-RT RIC. Based on the received network application input(s). the one or more network applications 110 may output a configuration change command to the ConMit module 102. The configuration change command may correspond to one of a change in one or more configurations, a change in one or more control parameters, and a change in one or more policies, associated with a connected RAN node 112. For example, the rApps may generate RAN OAM-CM changes, and the xApps may generate E2 policy or control outputs. Additionally, the rApps may output one or more Al policies, which may be fed into the Near-RT RIC. The one or more Al policies may refer to a set of rules or guidelines implemented via an Al interface in an O-RAN architecture to help manage and optimize network performance, resource allocation, and user experience in an O- RAN environment. The generated outputs may affect changes in the RAN node(s) 112, that may be tracked by one or more KPIs of interest. In an embodiment, the example environment 100 may include rApps / xApps. The one or more network application inputs may be provided to the rApps / xApps based on which the rApps / xApps propose the changes. The one or more network application inputs may include operator’s ConMit policy (also referred to as the “one or more operator policies”), and control parameter and KPI mapping. Further, the outputs from the rApps / xApps may be control parameters or Al policy.

[0027] The onboarded xApps / rApps may be characterized by the following fields from the point of view of the ConMit functionality:• Input: The rApps may get the FCAPS level details in the Non-RT RIC, and the xApps may get data from the E2 nodes in the Near-RT RIC.• Output: Based on the xApps / rApps objective function, the xApps / rApps may output either the RAN OAM CM changes (in case of the rApps) or the E2 policy or control (in case of the xApps). The control parameters may affect changes in the RAN nodes, typically tracked by the KPIs of interest. The rApps may also output the Al policy which is fed to the Near-RT RIC.The solution may apply to all outputs from the xApps / rApps, as discussed above.

[0028] In an embodiment, the ConMit module 102 may be configured to provide the ConMit functionality. To implement the ConMit functionality, the ConMit module 102 may include, but not limited to, a conflict detection sub-module 104. a conflict arbitration sub-module 106. and a conflict avoidance sub-module 108.

[0029] In an embodiment, the conflict detection sub-module 104 may be configured to receive the configuration change command from the one or more network applications 110. The conflict detection sub-module 104 may also receive a dependency graph or a conflict mitigation matrix from the operator 114. Further, the conflict detection sub-module 104 may be configured to detect whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of the dependency graph or the conflict mitigation matrix. The dependency graph may refer to a graph mapping a configuration or a policy parameter from the one or more network applications to an associated KPI or a system state impact. For example, the dependency graph may be used by the conflict detection sub-module 104 to detect one or more potential conflicts between the received configuration change command and one of previously applied or accepted configurations or one or more configurations received within the coherence time. For example, the conflict detection sub-module 104 may detect conflicting parameters, e.g. the parameter changes fromtwo xApps / rApps linked to a common KPI or the system state impact. The coherence time may refer to a time interval within which outputs (i.e.. configuration change commands) from a plurality of network applications (for example, the network application(s) 110) may be considered for performing conflict detection and mitigation. The coherence time may correspond to a time interval within which the configuration change commands from the plurality of network applications 110 may impact each other performance. The conflict mitigation matrix may refer to a framework used to determine interoperability issues, performance conflicts, or integration challenges that arise when the plurality of network applications 110 are deployed together in the network and perform the changes in the network. Further, the conflict detection sub-module 104 may be configured to send the one or more detected potential conflicts to the conflict arbitration sub-module 106.

[0030] In an embodiment, in response to detecting the conflict, the conflict arbitration submodule 106 may be configured to selectively accept or reject the received configuration change command based on a plurality of parameters and the one or more detected potential conflicts. The plurality of parameters may include the one or more operator policies. The plurality' of parameters may also include one or more inputs from a Performance Metrics (PM) database 116, a configuration parameter bookkeeping table 118-2 (may be interchangeably referred to as the table 118-2), and the configuration parameter to KPI mapping table 118-1 (may be interchangeably referred to as the table 118-1). Advantageously, the ConMit module 102 allows for arbitration of the detected conflicts in a RIC platform (for example, the Near-RT RIC platfonn or the Non-RT RIC platform) based on the operator’s intent.

[0031] In an embodiment, the one or more operator policies (also referred to as a “ConMit policy”) may be inputs provided by the operator 114 to the RIC platform to assist the ConMitmodule 102 in avoidance and arbitration of the detected potential conflict(s). For example, the one or more operator policies may assist the ConMit module 102 in effectively accepting or rejecting the received configuration change command and providing feedback to the one or more network applications 110. The one or more operator policies may include one or more of a relative priority order associated with each of the network application(s) 110. one or more KPI targets, a KPI priority order, one or more Service Level Agreements (SLAs), one or more service profiles, and one or more slice profiles. The relative priority order associated with each of the network application(s) 110 may refer to information about a relative priori ty or priority bins of the multiple onboarded network application(s). The information about the relative priority or the priority bins may be used by the conflict arbitration sub-module 106 for a direct comparison of priorities of the one or more network applications 110. For example, a network application with the higher priority may be considered for further processing over a network application with a lower priority. Further, the one or more KPI targets may refer to information about specific performance or KPI targets required to be achieved in accordance with the operator’s requirements. The conflict arbitration sub-module 106 may prioritize the network application 110 that recommends changes towards fulfilling the specific performance or KPI targets. For example, the operator 114 may specify that energy savings may be improved by 10%. Then, the conflict arbitration sub-module 106 may prioritize a network application that provides a configuration change command that may result in improved energy savings over a network application that provides a configuration change command that may lead to a higher energy consumption. The one or more KPI targets may be provided in the form of the one or more service profiles, the one or more slice profiles, or the one or more SLAs. The one or more service profiles may refer to a set of specifications associated with one or more services withinthe network. The one or more slice profiles may refer to a set of configuration parameters that specify requirements and behaviours of one or more network slices. Further, the one or more SLAs may refer to a set of agreements specifying measurable performance and service delivery expectations between two or more parties. Additionally, the KPI priority order may refer to information about particular KPIs that are more important for meeting the operator’s requirements. Therefore, the conflict arbitration sub-module 106 may prioritize the network application(s) 110 that improve the particular KPIs over other KPIs. For example, if the operator 114 specifies that improved mobility is a key requirement. Then, a network application that provides a configuration change command to enhance mobility may be prioritized by the conflict arbitration sub-module 106 over a network application that provides a configuration change command to improve coverage. The one or more operator policies may be configured in the Non-RT RIC by the SMO via a standardized service Application Programming Interface (API) interface. Further, the one or more operator policies may also be configured in the Near- RT RIC by the SMO via a standardized 01 interface.

[0032] Furthermore, for avoidance and arbitration services of ConMit functionality (also referred to as the “ConMit module 102’’), it may be expected that the operator provides some input to the RIC platform which may assist the ConMit functionality to make the right decisions and provide the right guidance as a feedback to the xApps / rApps. This input may be considered as the ConMit policy from the operator, and may include, but not be limited to, xApps / rApps priority , KPI target, and KPI priority. The xApps / rApps priority7may provide information about relative priority7or priority7bins of various onboarded xApps / rApps. The xApps / rApps priority7may be used by the conflict arbitration entity7for direct comparison of priorities, and the xApps / rApp with the higher priority7may be considered for further processing. The KPI targetmay provide information about what performance targets are required to be met in accordance with the operator’s requirements. Hence, the conflict arbitration entity may prioritize the xApps / rApps which recommend changes towards fulfilling those KPl / performance targets. The KPI targets may be provided in the form of the service profiles, the slice profiles or the SLAs. The KPI priority may provide information about which KPIs are more important for meeting the operator's requirements. Hence, the conflict arbitration entity may prioritize the xApps / rApps which improve certain KPIs over others. The ConMit Policy may be configured in the Non-RT RIC by the SMO via the standardized service API interface. Alternatively, the ConMit Policy may be configured in the Near-RT RIC by the SMO via the standardized 01 interface.

[0033] An example operator policy may be provided as follows:{"arbitrationpolicies": [{"scope" : {"cellldList": [{"plmnld": {"mcc": "248", "mnc": "35"}, "cld": {"nd": 71 }}, {"plmnld": {"mcc": "248", "mnc": "35"}, "cld": {"ncl": 72}}. {"plmnld": {"mcc": "248", "mnc": "35"}, "cld": {"nd": 73}} ] }, "arbitrationpriority Order": |"rAppPriorily". "KPITarget", "KPIPriority"], "kpiPriority Order": ["availability KPI", "retainability KPI", "mobilityKPI"], "kpiTargets":[{"KPIName": "Energy’ Saving","KPITargetCriteria": {"RelativeKPITarget": 10,"CompareWith": "PreviousValue"}},{"KPIName": "HOFailRate","KPITargetCriteria": {"RelativeKPITarget": -5,"CompareWith" : "PreviousWeekAverage"}}]},{"scope" : {"talList": [{"plmnld": {"mcc": "250", "mnc": "35"}. "tac": " 123456"}]},"arbitrationpriority Order": ["KPITarget". "rAppPriority"],"kpiTargets":[{"KPIName": "Availability","KPITargetCriteria": {"AbsoluteKPITarget": 90}}]}]}

[0034] Further, one or more example KPI targets in the form of a standardized sendee and the one or more slice profiles are provided in Table 1 and Table 2 below.Table 1Table 2

[0035] In an embodiment, the conflict arbitration sub-module 106 may receive the one or more inputs from the PM database 116 for tracking latest values of at least one of one or more PMs and one or more KPIs. For example, the one or more RAN nodes 1 12 may periodically output the PMs, the KPIs, and counters, which track performance of a Next Generation NodeB (gNB). The one or more RAN nodes 112 may output the PMs, the KPIs, and the counters via one or more standardized O-RAN interfaces (such as an 01 interface, an O-RAN FrontHaul (O-FH) Management (M)-plane, and an E2 interface). Furthermore, the one or more RAN nodes 112 may periodically output the PMs, the KPIs, and the counters after a predetermined time interval.For example, one or more RAN nodes 112 may periodically output the PMs, the KPIs, and the counters after 15 minutes or 5 minutes. The outputted PMs, KPIs, and counters may be available in the PM database 116. The outputted PMs, KPIs, and counters may also be available in various means of data store or memory capable of temporally storing data. For implementing the ConMit functionality, the conflict arbitration sub-module 106 may be configured to track one or more specific KPIs specified in the one or more operator policies. For example, if an energy saving target has been specified in the one or more operator policies, then the conflict arbitration sub-module 106 may track one or more KPIs associated with the energy consumption. Examples of such KPIs may include, but are not limited to, PEE.EnergySaving. The PEE.EnergySaving may refer to a KPI enabling or controlling energy-saving features within a Power Efficiency Enhancement (PEE) framework. This is based on the assumption that PM data may be available at the ConMit module 102 from the PM database 116.

[0036] For example, the RAN nodes may output the PMs, KPIs and counters via the standardized O-RAN interface(s) (such as 01, O-FH M-plane, E2) every 15 mins (or 5 mins) which track the performance of the gNB. The information may be available in the PM database 116 and / or any means of data storage or memory that may temporarily store the data. For the ConMit functionality , the conflict arbitration entity may track the specific KPIs which have been provided as input in the operator’s policy. For example, if the Energy' Saving target has been specified in the operator’s policy, then the ConMit functionality may track the energyconsumption KPIs like PEE.Energy Saving. It may be assumed that the PM data is available at the ConMit from the PM database.

[0037] In an embodiment, the conflict arbitration sub-module 106 may be configured to receive the table 118-1 to validate the output of a network application against the one or more operatorpolicies. The table 118-1 may refer to a table including mapping of one or more configuration parameters to corresponding impact on the one or more specific KPIs. For example, the table 118-1 may indicate that changing a configuration parameter from ‘t’ to ‘t+5t’ may cause a specific KPI value to change. The table 118-1 may also include a mapping of changes in the specific KPI(s) to corresponding changes in the one or more configuration parameters. The table 118-1 may enable the ConMit module 102 and / or the conflict arbitration sub-module 106 to estimate or predict an impact of the received configuration change command on the KPI(s). In an embodiment, the table 118-1 may include a mapping between the outputs of the network application(s) and the specific KPI(s). In an example embodiment, the table 118-1 may be provided by the operator 118. In another example embodiment, the table 118-1 may be generated by one or more AI / ML models or a Digital Twin (DT). In an embodiment, the table 118-1 may include a mapping of the configuration parameter to the KPIs at a cell -level. Additionally, the one or more operator policies may have a different scope, such as at a clusterlevel or a slice-level, accordingly, the table 118-1 may include corresponding mappings.

[0038] In one embodiment, the present disclosure proposes that a table be maintained where the changes in control parameters are mapped to the corresponding impact on the KPIs of interest. For example, a control parameter changing from t to t+5t may cause the KPI value to change, and the corollary may hold good too. This enables the ConMit functionality to estimate or predict the effect on the KPIs based on the changes proposed to the control parameters. It may be desirable (but not always possible) to map the output of various xApps / rApps to the KPIs of interest. The table may be generated based on lab or field data input by the operator. The table may also be generated with the help of AIML or use of DT. The table so far may be limited to the mapping of KPIs at a cell-level. However, the operator policy may have a differentscope, for example, cluster level, slice level, etc. Hence, the table may be expanded to include the cluster level and the slice level mappings.

[0039] In an embodiment, the table 118-2 may be for bookkeeping of configuration change commands proposed and committed by the network application(s) 110 to validate the outputs of network application(s) 110 against the one or more operator policies. For example, the table 118-2 may assist the ConMit module 102 and / or the conflict arbitration sub-module 106 to intelligibly utilize the outputs of the network application(s) 110 for deriving infomration on the corresponding impact on the specific KPI(s) mentioned in the one or more operator policies. The table 118-2 may include, for example, default values of the configuration parameter(s). proposed changes in the default values of configuration parameter(s) based on the outputs of the network application(s) 110, an identifier (ID) associated with the network application(s) proposing the changes, and associated timestamp(s). Based on the table 118-2, the conflict arbitration sub-module 106 may determine a trend in KPI changes based on the received configuration change commands. In an example embodiment, the table 118-2 may be maintained by the ConMit module 102. In one embodiment, for the ConMit functionality to intelligibly use the output of xApps / rApps for deriving information on their impact on the KPIs mentioned in the operator’s policy, the ConMit functionality may need to maintain a database of default values of the parameters, changes made to these values, xApp / rApp ID which proposed the change, and time stamp. Using the aforesaid information, the conflict arbitration and avoidance entity may have a handle of the trend in KPI changes caused by the trend in changes of the control or policy parameters. In an embodiment, the tables 118-1 and 118-2 may be included in the ConMit module 102. Alternatively, the tables 118-1 and 118-2 may be an input to the ConMit module 102.

[0040] In an embodiment, to selectively accept or reject the received configuration change command, the conflict arbitration sub-module 106 may be configured to compare the relative priorities of the network apphcation(s) 110 based on the corresponding relative priority order. Further, the conflict arbitration sub-module 106 may be configured to accept or reject the received configuration change command based on the comparison.

[0041] In an embodiment, to selectively accept or reject the received configuration change command, the conflict arbitration sub-module 106 may be configured to determine whether the received configuration change command aids in meeting the one or more KPI targets using the tables 118-1 and 118-2. Further, the conflict arbitration sub-module 106 may be configured to accept or reject the received configuration change command based on the detennination.

[0042] In an embodiment, to selectively accept or reject the received configuration change command, the conflict arbitration sub-module 106 may be configured to determine the priorities associated with the one or more KPIs impacted by the received configuration change command based on the KPI priority order. Further, the conflict arbitration sub-module 106 may be configured to accept or reject the received configuration change command based on the determination.

[0043] In an embodiment, in response to selectively accepting the received configuration change command (i. e. , after conflict arbitration), the conflict arbitration sub-module 106 may transmit an accepted configuration to the one or more RAN or E2 nodes 112 for implementation. Additionally, the conflict arbitration sub-module 106 may send information of the detected conflict to the conflict avoidance sub-module 108. The information of the detected conflict may include, for example, details of an applied arbitration policy based on which the detected conflict has been arbitrated and an applied timestamp.

[0044] In an embodiment, the conflict avoidance sub-module 108 may be configured to generate a feedback based on information of the detected conflict, in response to selective acceptance or rejection of the received configuration change command by the conflict arbitration sub-module 106. Further, the conflict avoidance sub-module 108 may be configured to transmit the generated feedback to the one or more network applications 110 for prevention of potential conflicts, for example, at a network application level. In an example embodiment, to transmit the generated feedback to the one or more network applications 110, the conflict avoidance sub-module 108 may be configured to transmit one or more of the configuration parameter bookkeeping table 118-2 and the configuration parameter to the KPI mapping table 118-1 to the one or more network applications 110. Advantageously, the ConMit module 102 may provide the network application(s) with an additional intelligence enabling the network application(s) to avoid future conflicts.

[0045] The example environment 100 may also include a ConMit functionality module (also referred to as the “ConMit module 102’'). The one or more inputs to the ConMit functionality may include the dependency graph which maps each configuration or policy parameter from xApps / rApps to the associated KPI or system state impact. The dependency graph may be used by a conflict detection entity (for example, the conflict detection sub-module 104) to detect potential conflicting parameters, e g., the parameter changes from two xApps / rApps linked to a common KPI or system state impact. The one or more inputs may also include an input from the operator in terms of policy (i.e., the one or more operator policies), and the input from the PM database 116 for tracking latest values of the performance metrics and KPIs, as discussed in detail in the preceding paragraphs. The one or more inputs may further include control, configuration or policy changes from the xApps / rApps. Furthermore, the one or more inputsmay include xApp / rApp control configuration or policy parameters and KPI mapping to validate the rApp output against the operator’s policy, and bookkeeping of the changes proposed and committed by xApps / rApps for the aforesaid validation. The outputs from the ConMit functionality may include control, configuration or policy changes from the xApps / rApps after conflict mitigation, and the feedback to xApps / rApps for conflict mitigation or avoidance at the xApp / rApp level.

[0046] The ConMit functionality may include the conflict detection entity (for example, the conflict detection sub-module 104), a conflict arbitration entity (for example, the conflict arbitration sub-module 106), and a conflict avoidance entity (for example, the conflict avoidance sub-module 108). An input to the conflict detection entity includes the control, configuration or policy changes from the xApps / rApps, and the dependency graph. An output of the conflict detection entity may include the detected potential conflicts. An input of the conflict arbitration entity may include the detected potential conflicts by the conflict detection entity, input of parameters and KPI mapping to validate the rApp output against the operator’s policy, the bookkeeping of the changes proposed and committed by xApps / rApps for the aforesaid validation. The input of the conflict arbitration entity may further include one or more inputs from the operator in terms of policy, and one or more inputs from the PM database for tracking the latest values of the performance metrics and KPIs. The output of the conflict arbitration entity may include control, configuration or policy changes from xApps / rApps after the conflict mitigation, and conflict details. An input of the conflict avoidance entity may include the conflict details. An output of the conflict avoidance entity may include the feedback to xApps / rApps to mitigate or avoid the conflicts at the application layer.

[0047] An operation of the ConMit module 102 for arbitration and avoidance of the conflicts is explained in detail in the forthcoming paragraphs.

[0048] In an example embodiment, the ConMit module 102 and / or the conflict detection submodule 104 may receive a first configuration change command from a first network application and a second configuration command from a second network application within the coherence time. Although the configuration change commands from two network applications have been discussed in this example embodiment, it may be noted that the ConMit module 102 may receive the configuration change commands from any number of network applications. The conflict detection sub-module 104 may detect the potential conflict(s) between the first and second configuration change commands based on one of the dependency graph and the conflict mitigation matrix. Based on the plurality’ of parameters (e.g., the one or more operator policy, the one or more inputs from the PM database 116. and the tables 118-1 and 118-2, the conflict arbitration sub-module 106 may decide which of the first and second configuration change commands to accept (i.e., commit to the RAN node(s) 112) and which one to reject. For example, the conflict arbitration sub-module 106 may decide based on steps explained in the forthcoming paragraphs.

[0049] In an example embodiment, the conflict arbitration sub-module 106 may first check the relative priorities of the first and second network applications. If the first network application has a higher priority than the second netw ork application, the conflict arbitration sub-module 106 may accept the first configuration change command (for further processing) and reject the second configuration change command. However, if the first and second network applications have the same priority, the conflict arbitration sub-module 106 may decide based on the one or more KPI targets (including the one or more sendee profiles, the one or more slice profiles, andthe one or more SLAs) specified in the one or more operator policies. For this, the conflict arbitration sub-module 106 may check the table 118-2 to first determine a trend in change of the configuration parameters. Based on the determination, the conflict arbitration sub-module 106 may predict the impact of the first and second configuration change commands on the specified KPI(s). In an example embodiment, the conflict arbitration sub-module 106 may predict the impact based on the table 118-1. In another example embodiment, the conflict arbitration sub-module 106 may predict the impact using the AI / ML models or the DT. The conflict arbitration sub-module 106 may determine whether any of the first and second configuration change commands ensure a step closer to the KPI target(s) based on the prediction. In response to determining that both the first and second configuration change commands aid the KPI target requirement, the conflict arbitration sub-module 106 may consider both the first and second configuration change commands to be constructive outputs, and accept both the first and second configuration change commands. Alternatively, in response to determining that only the first configuration change command aids the KPI target requirement, the conflict arbitration sub-module 106 may accept the first configuration change command. In such a situation, the conflict arbitration sub-module 106 may allow the second configuration change command to be a destructive output, and accordingly, reject the second configuration change command.

[0050] Further, if the KPI target(s) are met and are no longer a consideration based on the one or more inputs from the PM database 116, the conflict arbitration sub-module 106 may check the KPI priority order to make the decision. For example, upon determining that the first configuration change command impacts the KPI(s) with a higher priority' than the KPI(s) impacted by the second configuration change command, the conflict arbitration sub-module106 may accept the first configuration change command and reject the second configuration change command.

[0051] The above example embodiment explains that the conflict arbitration sub-module 106 first checks the relative priorities of the network application(s). followed by the KPI target(s). and then the KPI priority order. However, it may be noted that the above-mentioned order is not fixed. In an embodiment, the operator may define the order through the one or more operator policies.

[0052] In an embodiment, the SLA(s) or the service profile(s) may assist the conflict arbitration sub-module 106 in making the decision during the conflict. The SLA(s) or the service profile(s) may be a first criteria to identify a preferred configuration change command. If both the first and second configuration change commands degrade a defined SLA, the conflict arbitration sub-module 106 may reject both. Alternatively, if any of or both the first and second configuration change commands improve or do not impact the defined SLA, the conflict arbitration sub-module 106 may consider a next check.

[0053] In an embodiment, for avoidance or mitigation of potential future conflicts at the network application level, the conflict avoidance sub-module 108 may send feedback (or guidance information from the ConMit module 102) to one or more of the network applications involved in the conflict, as discussed in detail in the forthcoming paragraphs. The feedback may include information about a kind of conflict detected, and a cause of rejection.

[0054] In an embodiment, the conflict avoidance sub-module 108 may transmit a response (or, the feedback) towards the network application(s) in respect of the received configuration change command. The response may include conflict arbitration results (for example, accepted configurations or policy parameters, rejected configurations or policy parameters, etc.), a reasonof the conflict, conflict arbitration criteria (for example, KPI target values or priority being missed, etc.), and a backoff timer indicating a suitable time for the network application to reevaluate the decision.

[0055] In an embodiment, the conflict avoidance sub-module 108 may receive a subscription request from the network application(s) 110. In one embodiment, a network application may subscribe to receive notifications about the detected conflicts from the ConMit module 102 even if the configuration changes of that network application are accepted. In response to receiving the subscription request, the conflict avoidance sub-module 108 may transmit a subscription-based notification to the network application(s) 110. The subscription-based notification may include the conflict arbitration results (for example, the accepted configurations or policy parameters, the rejected configurations or policy parameters, etc.), the reason of the conflict, the conflict arbitration criteria (for example, KPI target values or priority being missed, etc.), and the backoff timer.

[0056] In an embodiment, the conflict avoidance sub-module 108 may receive a configuration guidance request for one or more intended configuration changes (e.g., a CM Write configuration request, an Al policy create or update request, or an E2 control request) from the network application(s) 110. The conflict avoidance sub-module 108 may determine whether the one or more intended configuration changes conflict with configuration(s) received from other network application(s) 110. Further, the conflict avoidance sub-module 108 may transmit the configuration guidance response to the network application(s) 110 based on the detected conflict. The configuration guidance response may include an indication on whether the one or more intended configuration changes may result in a conflict with the configuration(s) receivedfrom the other network application(s) 110, and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

[0057] In an embodiment, the conflict avoidance sub-module 108 may communicate the tables 118-1 and 118-2 to the network application(s) 110. The tables 118-1 and 118-2 may assist the network application(s) 110 in determining whether the corresponding proposed configuration change command may aid the one or more KPI targets. In an example embodiment, the conflict avoidance sub-module 108 may communicate the tables 118-1 and 118-2 to the network application(s) 110 as a part of the feedback or the configuration guidance response. In another example embodiment, the tables 118-1 and 118-2 may be communicated to the network application(s) 110 by the SMO or other R1 services. Based on the tables 118-1 and 118-2. the network application(s) 110 may suggest modifications to the one or more RAN or E2 nodes 112 for reducing the likelihood of the future conflicts and enhance acceptance chances of corresponding proposed configuration change commands.

[0058] In an example scenario, the following may be the steps involved in providing conflict avoidance and conflict arbitration services to the ConMit functionality. Two or more xApps / rApps may send control or policy parameter changes (RAN 0AM CM / E2 changes) to the ConMit functionality within the coherence time. The coherence time may be defined as the time period within which outputs from multiple xApps / rApps are considered for conflict detection and mitigation. Using the dependency graph or the conflict mitigation matrix, the ConMit functionality may detect a potential conflict between the xApps / rApps. The conflict arbitration entity' may follow7the mentioned steps in the specified order to decide which xApp / rApp’s output may be accepted for further processing, i.e., accepted (e.g. commit to RANnodes), and which x / rApp(s) output is rejected. The decision may be based on the operator policy and other inputs to the ConMit functionality, as discussed above.

[0059] Relative priorities of the xApps / rApps may be checked. If one rApp has a higher priority than the other x / rApp(s), then this x / rApp’s output is ACCEPTED (considered for further processing) and the other x / rApp(s) output is REJECTED. If the multiple xApps / rApps involved in the conflict are of the same priority, then the arbitration entity uses the KPI target including service SLA or the service or slice profiles in the operator's policy to make decision. The conflict arbitration entity may check the control parameter bookkeeping table to first determine the trend in the change of the control parameter. Using the infomiation, the conflict arbitration entity may evaluate or predict from the control / policy parameter to KPI mapping table the impact of the proposed change on the target KPIs. Alternatively, the evaluation or prediction may be done with AI / ML based algorithms or digital twin without using the predefined control / policy parameter to KPI mapping. The abovementioned steps enable the conflict arbitration entity to decide whether an output from the xApps / rApps may ensure a step closer to the KPI target or not. If both the xApps / rApps evaluate to a situation aiding the KPI target requirement, then this may be considered to be constructive output, and both the x / rApps may be ACCEPTED. However, if only one xApps / rApps evaluate to aiding the KPI target, then that control parameter change is ACCEPTED, and the other xApps / rApp’s control parameter change is considered to be a destructive output, and this is REJECTED.

[0060] Further, if the KPI target is met, and no longer a consideration based on the data from the PM Database, then the relative KPI priorities may be used to break the deadlock. For example, if xAppl / rAppl impacts KPIs which have higher priority7than the KPIs impacted by xApp2 / rApp2, then the proposed control parameter change of xAppl / rAppl is ACCEPTEDand the proposed control parameter change of xApp2 / rApp2 is REJECTED. In one embodiment, all the xApps / rApps involved in the conflict may get a feedback (e.g.. guidance information from the ConMit functionality) which may be used for future conflict avoidance. The feedback may include information about the kind of conflict detected, and the cause of rejection. The above-mentioned sequence of steps is an example of the ConMit functionality checking the priority of different rules i.e., rApp Priority or KPI Target or KPI Priority. However, the order may not be fixed, and the operator may provide the order as part of the policy. Further, the SLA or service profiles may be used to assist the arbitration on preferring a specific xApp / rApp output during the conflict. The SLA or service profiles may be the first criteria to identify which configuration is to be preferred. If any or both proposed change degrade the defined SLA, both may be rejected. If any or both proposed change improve the SLA or do not impact the SLA, the next check for arbitration may be considered.

[0061] Furthermore, avoidance of future conflicts or mitigating the conflicts at the xApp / rApp level may require some feedback to be sent to the xApps / rApps to avoid or pre-empt the future conflicts. To avoid the future conflicts, the present disclosure proposes one or more changes which may include, but are not limited to, changes in response towards xApp / rApp for any of write configuration changes request or control or policy parameter change or update or create request. The one or more changes may also include introducing subscription-based notification towards the xApp / rApp about the detected conflicts. The one or more changes may further include introducing the guidance procedure, and communicating the table details back to the xApp / rApp. Changes in response towards the xApps / rApps or the subscription-based notification may include conflict arbitration results e.g., accepted configuration or policy parameters, rejected configuration or policy parameters, etc. Further, the changes may includereason of the conflicts, conflict arbitration criteria e.g., KPI target values or priority being missed, etc. The changes may also include the backoff timer indicating when the xApp / rApp may try to re-evaluate the decision. The guidance procedure may add extra intelligence to the xApps / rApps inputs, so that it may be considered while recommending changes to the control parameters. The intelligence may include, but is not limited to. a request towards the ConMit functionality to check for possible conflicts with proposed changes in terms of CM Write configuration request or Al policy create / update request or E2 control request. Guidance response may include an indication on whether the xApp / rApp’s proposed change request may result in a conflict with change requests from other xApps / rApps. The guidance response may also include recommendations on modifying the proposed control parameter change request to avoid conflict. The tables may be communicated to the xApps / rApps which have the intelligence to figure out whether the proposed output is aiding the target KPIs or not. The communication may be from the SMO or via a response back to the xApp / rApp or guidance procedures or any other R1 services. Using the above, the xApps / rApps may propose changes for the RAN / E2 nodes to minimize future potential conflicts, and maximize the chance of acceptance of corresponding recommendations of control parameters.

[0062] FIG. 2 illustrates a flowchart depicting a method 200 for arbitration and avoidance of the potential conflicts, in accordance with an embodiment of the present disclosure. The method 200 may be performed by the ConMit module 102.

[0063] At step 202, the method 200 may include receiving the configuration change command from the one or more network applications 110. The one or more network applications 110 may include one of the one or more rApps and the one or more xApps. Further, the configuration change command may correspond to one of the change in the one or more configurations, thechange in the one or more control parameters, and the change in the one or more policies. associated with the connected RAN node 112.

[0064] At step 204, the method 200 may include detecting whether the received configuration change command conflicts with the one or more configurations received within the coherence time based on at least one of the dependency graph or the conflict mitigation matrix.

[0065] At step 206, the method 200 may include selectively accepting or rejecting the received configuration change command based on the plurality’ of parameters and the detected conflict in response to detecting the conflict. The plurality of parameters may include the one or more operator policies. The plurality of parameters may further include the one or more inputs from the PM database 116, the configuration parameter bookkeeping table 118-2, and the configuration parameter to KPI mapping table 118-1. Further, the one or more operator policies may include one or more of the relative priority order associated with each of the one or more network applications 110, the one or more KPI targets, the KPI priority order, the one or more SLAs, the one or more service profiles, and the one or more slice profiles.

[0066] In an embodiment, for selectively accepting or rejecting the received configuration change command, the method 200 may include comparing the relative priorities of the one or more network applications 110 based on the corresponding relative priority' order. Thereafter, the method 200 may include accepting the configuration change command received from a network application having a higher priority'. Alternatively, the method 200 may include rejecting the configuration change command received from remaining one or more network applications having lower priorities.

[0067] In an embodiment, for selectively accepting or rejecting the received configuration change command, the method 200 may include determining whether the received configurationchange command aids in meeting the one or more KPI targets using the configuration parameter bookkeeping table 118-2 and the configuration parameter to KPI mapping table 118-1. Thereafter, the method 200 may include accepting the received configuration change command in response to determining that the received configuration change command aids in meeting the one or more KPI targets. Alternatively, the method 200 may include rejecting the received configuration change command in response to determining that the received configuration change command fails to aid in meeting the one or more KPI targets.

[0068] In an embodiment, for selectively accepting or rejecting the received configuration change command, the method 200 may include determining the priorities associated with the one or more KPIs impacted by the received configuration change command based on the KPI priority order. Thereafter, the method 200 may include accepting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with higher priority. Alternatively, the method 200 may include rejecting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with lower priority.

[0069] In an embodiment, for selectively accepting or rejecting the received configuration change command, the method 200 may include determining whether the received configuration change command degrades the one or more SLAs. Thereafter, the method 200 may include rejecting the received configuration change command in response to determining that the received configuration change command degrades the one or more SLAs.

[0070] FIG. 3 illustrates a flowchart depicting a method 300 for avoidance of the potential conflicts, in accordance with an embodiment of the present disclosure. The method 300 may be a part of the method 200, and may be performed by the ConMit module 102.

[0071] At step 302, the method 300 may include generating the feedback based on the information of the detected conflict, in response to selectively accepting or rejecting the received configuration change command.

[0072] At step 304. the method 300 may include transmitting the generated feedback to the one or more network applications 110 for prevention of the potential conflicts. In an embodiment, for transmitting the generated feedback to the one or more network applications 110. the method 300 may include transmitting the one or more of the configuration parameter bookkeeping table 118-2 and the configuration parameter to the KPI mapping table 118-1 to the one or more network applications 110.

[0073] FIG. 4 illustrates a flowchart depicting a method 400 for transmitting the subscriptionbased notification to the network application(s) 110, in accordance with an embodiment of the present disclosure. The method 400 may be a part of the method 300, and may be performed by the ConMit module 102. The method 400 may be performed prior to step 302.

[0074] At step 402, the method 400 may include receiving the subscription request from the one or more network applications 110.

[0075] At step 404, the method 400 may include transmitting the subscription-based notification to the one or more network applications 110. The subscription-based notification may include information of an accepted configuration change command, infonnation of a rej ected configuration change command, the information of the detected conflict, one or more criteria associated with acceptance or rejection of the received configuration change command, and the back-off timer.

[0076] FIG. 5 illustrates a flow chart depicting a method 500 for transmitting the configuration guidance response to the netw ork application(s) 110, in accordance with an embodiment of thepresent disclosure. The method 500 may be a part of the method 200, and may be performed by the ConMit module 102. The method 400 may be performed prior to step 202.

[0077] At step 502, the method 500 may include receiving the configuration guidance request for the one or more intended configuration changes from the one or more network applications 110.

[0078] At step 504. the method 500 may include detecting a possible conflict while implementing the one or more intended configuration changes based on the one or more previous configurations received within the coherence time.

[0079] At step 506, the method 500 may include transmitting the configuration guidance response to the one or more network applications 110 based on the detected possible conflict. The configuration guidance response may include an indication of the detected possible conflict related to the configuration change and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

[0080] FIG. 6 illustrates an embodiment of a device 600, in accordance with an embodiment of the present disclosure. As shown in FIG. 6, the device 600 includes a processor 610, a memory 620, a storage component 630, an input component 640, an output component 650, a communication interface 660, and a bus 670. The device 600 may correspond to the ConMit module 102. The one or more components of the device 600 may be configured to implement one or more operations / functionalities of the present disclosure as discussed above.

[0081] The processor 610, as used herein, means any ty pe of computational circuit that may comprise hardware elements and software elements. The processor 610 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or thelike. The processor 610 may be a Central Processing Unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0082] The memory 620 includes a non-transitory computer readable medium. The memory 620 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g.. a flash memory, a magnetic memory, and / or an optical memory’) that stores information and / or instructions for use by the processor 610. The memory 620 comprises machine-readable instructions which are executable by the processor 610. These machine-readable instructions when executed by the processor 610 cause the processor 610 to perform one or more method steps of an embodiment described above.

[0083] The storage component 630 stores information and / or software related to the operation and use of the device 600. For example, the storage component 630 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another ty pe of non-transitory computer-readable medium, along with a corresponding drive.

[0084] The input component 640 is configured to receive information, such as user input. For example, the input component 640 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 640 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0085] The output component 650 is configured to provide output information from the device 600. For example, the output component 650 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0086] The communication interface 660 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 660 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 600 and other devices. In other words, the standard of the communication interface 660 is not limited.

[0087] The bus 670 acts as an interconnect between the processor 610, the memory 620. the storage component 630, the input component 640, the output component 650. and the communication interface 660 of the device 600. The bus 670 may include a wired interconnection or a wireless interconnection.

[0088] The number and arrangement of components shown in FIG. 6 are provided as an example. In practice, the device 600 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 6. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 800 may perform one or more functions described as being performed by another set of components of the device 600. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 600 in communication with one another.

[0089] Examples of the techniques and apparatus described herein include, but are not limited to, the following enumerated embodiments:[1] A method comprising: receiving, at a Conflict Mitigation (ConMit) module, a configuration change command from one or more network applications;detecting, by the ConMit module, whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accepting or rejecting, by the ConMit module, the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality of parameters comprises one or more operator policies.[2] The method as described in [1], further comprising: in response to selectively accepting or rejecting the received configuration change command, generating, by the ConMit module, a feedback based on information of the detected conflict; and transmitting, by the ConMit module, the generated feedback to the one or more network applications for prevention of potential conflicts.[3] The method as described in any one of [1] to [2], wherein the plurality of parameters further comprises one or more inputs from a performance metrics (PM) database, a configuration parameter bookkeeping table, and a configuration parameter to Key Performance Indicator (KPI) mapping table; and wherein the one or more operator policies comprise one or more of a relative priority order associated with each of the one or more network applications, one or more KPI targets, a KPI priority order, one or more Service Level Agreements (SLAs), one or more service profiles, and one or more slice profiles, and selectively accepting or rejecting the received configuration change command comprises: comparing relative priorities of the one or more network applications based on the corresponding relative priority order; andbased on the comparison, performing one of: accepting the configuration change command received from a network application having a higher priority; or rejecting the configuration change command received from remaining one or more network applications having lower priorities.[4] The method as described in any one of [1] to [3], wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command aids in meeting one or more KPI targets using the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table; and performing one of: accepting the received configuration change command in response to determining that the received configuration change command aids in meeting the one or more KPI targets; or rejecting the received configuration change command in response to determining that the received configuration change command fails to aid in meeting the one or more KPI targets.[5] The method as described in any one of [1] to [4], wherein selectively accepting or rejecting the received configuration change command comprises: determining priorities associated with one or more KPIs impacted by the received configuration change command based on a KPI priority7order; and performing one of:accepting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with higher priority; or rejecting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with lower priority.[6] The method as described in any one of [1] to [5], wherein prior to transmitting the generated feedback to the one or more network applications, the method comprises: receiving, by the ConMit module, a subscription request from the one or more network applications; and transmitting, by the ConMit module, a subscription-based notification to the one or more network applications, wherein the subscription-based notification comprises information of an accepted configuration change command, information of a rejected configuration change command, the information of the detected conflict, one or more criteria associated with acceptance or rejection of the received configuration change command, and a back-off timer.[7] The method as described in any one of [1] to [6], wherein prior to receiving the configuration change command from the one or more network applications, the method comprises: receiving, by the ConMit module, a configuration guidance request for one or more intended configuration changes from the one or more network applications; detecting, by the ConMit module, a possible conflict while implementing the one or more intended configuration changes based on the one or more previously configurations received within the coherence time; andtransmitting, by the ConMit module, a configuration guidance response to the one or more network applications based on the detected possible conflict, wherein the configuration guidance response comprises an indication of the detected possible conflict related to the configuration change and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.[8] The method as described in any one of [1] to [7], wherein transmitting the generated feedback to the one or more network applications comprises: transmitting one or more of the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table to the one or more network applications.[9] The method as described in any one of [1] to [8], wherein the one or more network applications comprise one of one or more radio access network Applications (rApps) and one or more extensible Applications (xApps); wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more control parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node; and wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command degrades the one or more SLAs; and rejecting the received configuration change command in response to determining that the received configuration change command degrades the one or moreSLAs.

[0010] An apparatus configured to: receive a configuration change command from one or more network applications; detect whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accept or reject the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality of parameters comprises one or more operator policies.

[0011] The apparatus as described in

[0010] , wherein the apparatus is further configured to: in response to selectively accepting or rejecting the received configuration change command, generate a feedback based on information of the detected conflict; and transmit the generated feedback to the one or more network applications for prevention of potential conflicts.

[0012] The apparatus as described in any one of

[0010] to

[0011] , wherein the plurality of parameters further comprises one or more inputs from a performance metrics (PM) database, a configuration parameter bookkeeping table, and a configuration parameter to Key Performance Indicator (KPI) mapping table; and the one or more operator policies comprise one or more of a relative priority order associated with each of the one or more network applications, one or more KPI targets, a KPI priority order, one or more Service Level Agreements (SLAs), one or more service profiles, and one or more slice profiles, and to selectively accept or reject the received configuration change command, the apparatus is configured to:compare relative priorities of the one or more network applications based on the corresponding relative prionty order; and based on the comparison, perform one of: accept the configuration change command received from a network application having a higher priority; or reject the configuration change command received from remaining one or more network applications having lower priorities.

[0013] The apparatus as described in any one of

[0010] to

[0012] , wherein to selectively accept or reject the received configuration change command, the apparatus is configured to: determine whether the received configuration change command aids in meeting one or more KPI targets using the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table; and perfonn one of: accept the received configuration change command in response to determining that the received configuration change command aids in meeting the one or more KPI targets; or reject the received configuration change command in response to determining that the received configuration change command fails to aid in meeting the one or more KPI targets.

[0014] The apparatus as described in any one of

[0010] to

[0013] , wherein to selectively accept or reject the received configuration change command, the apparatus is configured to: determine priorities associated with one or more KPIs impacted by the received configuration change command based on a KPI priority order; andperform one of: accept the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with higher priority; or reject the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with lower priority.

[0015] The apparatus as described in any one of

[0010] to

[0014] , wherein prior to transmitting the generated feedback to the one or more network applications, the apparatus is configured to: receive a subscription request from the one or more network applications; and transmit a subscription-based notification to the one or more network applications, wherein the subscription-based notification comprises information of an accepted configuration change command, information of a rej ected configuration change command, the information of the detected conflict, one or more criteria associated with acceptance or rejection of the received configuration change command, and a back-off timer.

[0016] The apparatus as described in any one of

[0010] to

[0015] , wherein prior to receiving the configuration change command from the one or more network applications, the apparatus is configured to: receive a configuration guidance request for one or more intended configuration changes from the one or more network applications; detect a possible conflict while implementing the one or more intended configuration changes based on the one or more previously configurations received within the coherence time; andtransmit a configuration guidance response to the one or more network applications based on the detected possible conflict wherein the configuration guidance response comprises an indication of the detected possible conflict related to the configuration change and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

[0017] The apparatus as described in any one of

[0010] to

[0016] . wherein to transmit the generated feedback to the one or more network applications, the apparatus is configured to: transmit one or more of the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table to the one or more network applications.

[0018] The apparatus as described in any one of

[0010] to

[0017] . wherein the one or more network applications comprise one of one or more radio access network Applications (rApps) and one or more extensible Applications (xApps).

[0019] The apparatus as described in any one of

[0010] to

[0018] , wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more control parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node; wherein the apparatus corresponds to a conflict mitigation (ConMit) module; and wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command degrades the one or more SLAs; andrejecting the received configuration change command in response to determining that the received configuration change command degrades the one or more SLAs.

[0020] A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by a conflict mitigation (ConMit) module, the conflict mitigation (ConMit) module comprising one or more processors, cause the one or more processors to: receive a configuration change command from one or more network applications; detect whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accept or reject the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality of parameters comprises one or more operator policies.

[0090] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device or a combination of hardware devices and software modules. The ConMit module may include respective processors, communication units, and storage units (e.g., memory). The communication units may perform functions for transmitting and receiving signals. The storage units may include executable instructions that, when executed by the corresponding processors, cause the corresponding ConMit module to perform the functions as described above with reference to FIGS. 2-5.

[0091] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0092] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

[0093] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be perfonned. Also, those acts that are not dependent on other acts may be perfonned in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

[0094] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0095] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readilymodify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

We Claim:

1. A method comprising: receiving, at a Conflict Mitigation (ConMit) module, a configuration change command from one or more network applications; detecting, by the ConMit module, whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accepting or rejecting, by the ConMit module, the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality of parameters comprises one or more operator policies.

2. The method as claimed in claim 1, further comprising: in response to selectively accepting or rejecting the received configuration change command, generating, by the ConMit module, a feedback based on information of the detected conflict; and transmitting, by the ConMit module, the feedback to the one or more network applications for prevention of potential conflicts.

3. The method as claimed in claim 1 , wherein the plurality' of parameters further comprises one or more inputs from a performance metrics (PM) database, a configuration parameter bookkeeping table, and a configuration parameter to Key Performance Indicator (KPI) mapping table; andwherein the one or more operator policies comprise one or more of a relative priority order associated with each of the one or more network applications, one or more KPI targets, a KPI priority order, one or more Service Level Agreements (SLAs), one or more service profiles, and one or more slice profiles, and selectively accepting or rejecting the received configuration change command comprises: comparing relative priorities of the one or more network applications based on the corresponding relative priority order; and based on the comparison, performing one of: accepting the configuration change command received from a network application having a higher priority’; or rejecting the configuration change command received from remaining one or more network applications having lower priorities.

4. The method as claimed in claim 1, wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command aids in meeting one or more KPI targets using the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table; and performing one of: accepting the received configuration change command in response to determining that the received configuration change command aids in meeting the one or more KPI targets; orrejecting the received configuration change command in response to determining that the received configuration change command fails to aid in meeting the one or more KPI targets.

5. The method as claimed in claim 1, wherein selectively accepting or rejecting the received configuration change command comprises: determining priorities associated with one or more KPIs impacted by the received configuration change command based on a KPI priority order; and performing one of: accepting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with higher priority; or rejecting the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with lower priority.

6. The method as claimed in claim 2, wherein prior to transmitting the generated feedback to the one or more network applications, the method comprises: receiving, by the ConMit module, a subscription request from the one or more network applications; and transmitting, by the ConMit module, a subscription-based notification to the one or more network applications, wherein the subscription-based notification comprises information of an accepted configuration change command, information of a rejected configuration changecommand, the information of the detected conflict, one or more criteria associated with acceptance or rejection of the received configuration change command, and a back-off timer.

7. The method as claimed in claim 1. wherein prior to receiving the configuration change command from the one or more network applications, the method comprises: receiving, by the ConMit module, a configuration guidance request for one or more intended configuration changes from the one or more network applications: detecting, by the ConMit module, a possible conflict while implementing the one or more intended configuration changes based on the one or more configurations received within the coherence time; and transmitting, by the ConMit module, a configuration guidance response to the one or more network applications based on the detected possible conflict, wherein the configuration guidance response comprises an indication of the detected possible conflict related to the configuration change and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

8. The method as claimed in claim 2, wherein transmitting the generated feedback to the one or more network applications comprises: transmitting one or more of the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table to the one or more network applications.

9. The method as claimed in claim 1, wherein the one or more network applications compnse one of one or more radio access network Applications (rApps) and one or more extensible Applications (xApps); wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more control parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node; and wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command degrades the one or more SLAs; and rejecting the received configuration change command in response to determining that the received configuration change command degrades the one or more SLAs.

10. An apparatus configured to: receive a configuration change command from one or more network applications; detect whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accept or reject the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality' of parameters comprises one or more operator policies.

11. The apparatus as claimed in claim 10, wherein the apparatus is further configured to: in response to selectively accepting or rejecting the received configuration change command, generate a feedback based on information of the detected conflict; and transmit the generated feedback to the one or more network applications for prevention of potential conflicts.

12. The apparatus as claimed in claim 10. wherein the plurality of parameters further comprises one or more inputs from a performance metrics (PM) database, a configuration parameter bookkeeping table, and a configuration parameter to Key Performance Indicator (KPI) mapping table; and the one or more operator policies comprise one or more of a relative priority order associated with each of the one or more network applications, one or more KPI targets, a KPI priority order, one or more Service Level Agreements (SLAs), one or more service profiles, and one or more slice profiles, and to selectively accept or reject the received configuration change command, the apparatus is configured to: compare relative priorities of the one or more network applications based on the corresponding relative priority order; and based on the comparison, perform one of: accept the configuration change command received from a network application having a higher priority; or rej ect the configuration change command received from remaining one or more network applications having lower priorities.

13. The apparatus as claimed in claim 10, wherein to selectively accept or reject the received configuration change command, the apparatus is configured to: determine whether the received configuration change command aids in meeting one or more KPI targets using the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table; and perform one of: accept the received configuration change command in response to determining that the received configuration change command aids in meeting the one or more KPI targets; or reject the received configuration change command in response to determining that the received configuration change command fails to aid in meeting the one or more KPI targets.

14. The apparatus as claimed in claim 10, wherein to selectively accept or reject the received configuration change command, the apparatus is configured to: determine priorities associated with one or more KPIs impacted by the received configuration change command based on a KPI priority order; and perform one of: accept the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with higher priority: orreject the received configuration change command in response to determining that the received configuration change command impacts the one or more KPIs with lower pnority.

15. The apparatus as claimed in claim 11. wherein prior to transmitting the generated feedback to the one or more network applications, the apparatus is configured to: receive a subscription request from the one or more network applications; and transmit a subscription-based notification to the one or more network applications, wherein the subscription-based notification comprises information of an accepted configuration change command, information of a rejected configuration change command, the information of the detected conflict, one or more criteria associated with acceptance or rejection of the received configuration change command, and a back-off timer.

16. The apparatus as claimed in claim 10, wherein prior to receiving the configuration change command from the one or more network applications, the apparatus is configured to: receive a configuration guidance request for one or more intended configuration changes from the one or more network applications; detect a possible conflict while implementing the one or more intended configuration changes based on the one or more configurations received within the coherence time; and transmit a configuration guidance response to the one or more network applications based on the detected possible conflict, wherein the configuration guidance response comprises an indication of the detected possible conflict related to the configuration change and one ormore recommendations on modifications of the configuration change request to prevent the detected possible conflict.

17. The apparatus as claimed in claim 11, wherein to transmit the generated feedback to the one or more network applications, the apparatus is configured to: transmit one or more of the configuration parameter bookkeeping table and the configuration parameter to KPI mapping table to the one or more network applications.

18. The apparatus as claimed in claim 10. wherein the one or more network applications comprise one of one or more radio access network Applications (rApps) and one or more extensible Applications (xApps).

19. The apparatus as claimed in claim 10, wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more control parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node; wherein the apparatus corresponds to a conflict mitigation (ConMit) module; and wherein selectively accepting or rejecting the received configuration change command comprises: determining whether the received configuration change command degrades the one or more SLAs; andrejecting the received configuration change command in response to determining that the received configuration change command degrades the one or more SLAs.

20. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by a conflict mitigation (ConMit) module, the conflict mitigation (ConMit) module comprising one or more processors, cause the one or more processors to: receive a configuration change command from one or more network applications; detect whether the received configuration change command conflicts with one or more configurations received within a coherence time based on at least one of a dependency graph or a conflict mitigation matrix; and in response to detecting the conflict, selectively accept or reject the received configuration change command based on a plurality of parameters and the detected conflict, wherein the plurality of parameters comprises one or more operator policies.

Images