Integrating radio access network applications with a conflict mitigation functionality

Abstract

The present disclosure relates to a method or an apparatus integrating radio access network applications with a conflict mitigation functionality. The method performed by a conflict mitigation (ConMit) module includes: receiving a configuration change command from one or more network applications; detecting whether the received configuration change command conflicts with one or more previously applied or accepted configurations; in response to detecting the conflict, transmitting a configuration change response message to the one or more network applications, wherein the configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

Description

INTEGRATING RADIO ACCESS NETWORK APPLICATIONS WITH ACONFLICT MITIGATION FUNCTIONALITYCROSS-REFERENCE TO RELATED APPLICATION (S)

[0001] This application claims priority to Indian Provisional Application No. 202411060431, filed on August 9, 2024, and Indian Non-Provisional Application No. 202411060431 filed December 27, 2024; the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to integrating Radio Access Network (RAN) applications (rApps) with a Conflict Mitigation (ConMit) functionality.BACKGROUND

[0003] The information disclosed in this background section is only for the 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)) are deployed to optimize and manage various network functions. However, the deployment of such network applications increases the likelihood that decisions made by one network application may conflict with other network applications, which 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 r / xApps. For instance, one r / 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. Tohandle and mitigate the conflicts, Open-RAN (O-RAN) alliance has introduced a Conflict Mitigation (ConMit) functionality as part of a Non-Real Time RAN Intelligent Controller (Non-RT RIC) and a Near-Real Time RIC (Near-RT RIC). The ConMit functionality primarily comprises of 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 or roll-back), and conflict avoidance (transmitting conflict related information to the rApps to avoid future conflicts).

[0005] Additionally, with the accelerated growth of rApp development by independent vendors, necessity of the ConMit functionality is increasing. This necessitates introduction of a standard Application Programming Interface (API) and data model at an R1 -interface level, so that the rApps and the ConMit functionality can communicate in a standardized way.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 disclosure nor is it intended to determine the scope of the disclosure.

[0007] 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 previously applied or accepted configurations. In response to detecting the conflict, the method includes transmitting, by the ConMit module, a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of arollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0008] Disclosed herein is an apparatus. 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 previously applied or accepted configurations. In response to detecting the conflict, the apparatus is configured to transmit a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0009] Disclosed herein is a non-transitory computer-readable medium storing instructions. The instructions comprising one or more instructions that are executed by a conflict mitigation (ConMit) module. The ConMit module comprises one or more processors. The one or more 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 previously applied or accepted configurations. In response to detecting the conflict, the one or more instructions cause the one or more processors to transmit a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0010] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawing. It is appreciated that these drawingsdepict only typical embodiments of the disclosure and are therefore not to be considered limiting its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying drawings.BRIEF DESCRIPTION OF THE 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 depicting a system for integrating radio access network (RAN) applications (rApps) with a conflict mitigation (ConMit) functionality, according to an embodiment of the present disclosure;FIG. 2 illustrates a schematic block diagram depicting a ConMit module, according to an embodiment of the present disclosure;FIG. 3 illustrates a sequence flow diagram depicting a “Reject configuration” outcome for ConMit-unaware rApps, according to an embodiment of the present disclosure;FIG. 4 illustrates a sequence flow diagram depicting a “Reject configuration” outcome for ConMit-aware rApps, according to an embodiment of the present disclosure;FIG. 5 illustrates a sequence flow diagram depicting an “Accept configuration and rollback previous configuration” outcome for the ConMit-aware rApps, according to an embodiment of the present disclosure;FIG. 6 illustrates a sequence flow diagram depicting a “Reject configuration and rollback previous configuration” outcome for the ConMit-aware rApps, according to an embodiment of the present disclosure;FIG. 7 illustrates a sequence flow diagram depicting a subscription-based notification about conflicts, according to an embodiment of the present disclosure;FIG. 8 illustrates a sequence flow diagram depicting Configuration Management (CM) configuration guidance procedure, according to an embodiment of the present disclosure;FIG. 9 illustrates a flowchart depicting a method for integrating the rApps with the ConMit functionality, in accordance with an embodiment of the present disclosure; andFIG. 10 illustrates a diagram of components 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 illustrations and descriptions, 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 the 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 limit 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 thatsoftware 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 the disclosure 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” (in other words, nouns not mentioned in the plural) 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,” “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. Furthermore, 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 terms “mobile device”, “user device”, “User Equipment”, and “UE” may be used interchangeably throughout the description.

[0017] FIG. 1 illustrates a schematic block diagram depicting a system 100 for integrating radio access network (RAN) applications (rApps) with a conflict mitigation (ConMit) functionality, according to an embodiment of the present disclosure. In an embodiment, the system 100 may include a Service Management and Orchestration (SMO) framework 101 and one or more RAN nodes 112. In an embodiment, the RAN node(s) 112 may refer to one or more network elements such as base stations, radio units, distributed units, etc. The SMO framework 101 may include a non-real time RAN intelligent controller (Non-RT RIC) 106,and an 01 termination 110. The SMO framework 101 and the RAN node(s) 112 may communicate with each other via an 01 interface. The non-RT RIC 106 may include the one or more network applications and a ConMit module 108. In an embodiment, the one or more network applications may include one or more RAN applications (rApps) rApp-1 102a, ... rApp-N 102n (hereinafter referred to as “rApps 102”). In an embodiment, the one or more network applications may include one or more extensible applications (xApps), or one or more SMO applications. In an embodiment, the ConMit module 108 may provide the ConMit functionality. In case the one or more network applications correspond to the one or more rApps 102, the ConMit module 108 is implemented at the non-RT RIC 106. In case the one or more network applications correspond to the one or more xApps, the ConMit module 108 is implemented at a near-Real Time RIC (near-RT-RIC). The rApps 102 and the ConMit module 108 may communicate with each other via a standardized communication interface, R1 interface 104 to perform conflict detection, mitigation, and avoidance. The R1 interface 104 may receive input data from the rApps 102 to assist the ConMit module 108 to perform the conflict detection, mitigation, and avoidance. In an embodiment, the input data may include, but is not limited to, one or more proposed operations, administration, and maintenance - configuration management (OAM-CM) write configuration change commands (also referred to as “CM configuration change command(s)” or “configuration change command(s)” or “write configuration changes command(s)”). In an embodiment, the configuration change command(s) correspond to one of a change in one or more configurations, a change in one or more parameters, and a change in one or more policies, associated with the connected RAN node 112. The R1 interface 104 may also transmit feedback such as one or more CM write configuration change response messages (also referred to as “write configuration change response message(s)” or “configuration change response message(s)” or “write configuration changes response message(s)”) received from the ConMit module 108 to the rApps 102corresponding to the one or more proposed CM write configuration changes. In an embodiment, the R1 interface 104 may also transmit additional information such as a CM configuration guidance response (also referred to as “configuration guidance response”) from the ConMit module 108 to the rApps 102. In an embodiment, the rApps 102 may receive the CM configuration guidance response before the ConMit module 108 sends the proposed one or more CM write configuration changes towards the 01 Termination 110. The CM configuration guidance response has been explained in detail in conjunction with FIG. 8 in the forthcoming paragraphs.

[0018] FIG. 2 illustrates a schematic block diagram 200 depicting the ConMit module 108, according to an embodiment of the present disclosure. The ConMit module 108 may include a conflict detection sub-module 202, a conflict mitigation sub-module 204, and a conflict avoidance sub-module 206.

[0019] In an embodiment, the conflict detection sub-module 202 may be configured to detect a presence of a conflict with one or more CM write configurations previously applied at or accepted by the RAN node(s) 112. In an embodiment, the conflict may be one of a direct conflict, an indirect conflict, and an implicit conflict. After detecting the presence of the conflict, the conflict detection sub-module 202 may be configured to include HTTP status codes such as ‘409 Conflict’ as a part of the CM write configuration change response message transmitted to the rApps 102 via the R1 interface 104. The HTTP status code ‘409 Conflict’ may indicate to the rApps 102 that rejection of the proposed CM write configuration changes is due to the conflict detected by the ConMit module 108. In an embodiment, the ConMit module 108 may detect the conflicts based on one or more conflict detection rules received from a network operator.

[0020] In an embodiment, the conflict mitigation sub-module 204 may be configured to identify which of the one or more proposed CM write configuration changes to accept, reject,or roll-back using one or more mitigation policies. Particularly, the conflict mitigation may result in one or more outcomes for the rApps 102 based on the one or more mitigation policies. The one or more outcomes may include a “Reject configuration” outcome, an “Accept configuration and rollback previous configuration” outcome, and a “Reject configuration and rollback previous configuration” outcome. The conflict mitigation sub-module 204 may also be configured to introduce a “ConMit aware” flag as a part of an rApp registration procedure. The “ConMit aware” flag may indicate that the rApps 102 are aware that the Non-RT RIC 106 performs the conflict detection and mitigation and that the ConMit module 108 may reject the one or more CM write configuration change commands. The conflict mitigation sub-module 204 may also be configured to introduce a “rApp priority” flag as a part of the rApp registration procedure or an rApp onboarding procedure. The ConMit module 108 may use the “rApp priority” flag during the conflict mitigation to identify an rApp from among the rApps 102 whose configuration is to be prioritized when any conflict is detected. In an embodiment, the network operator may assign priority levels such as high, medium, and low to each of the rApps 102 during the rApp onboarding procedure. In an embodiment, the network operator may update the rApp priority levels during runtime. The “rApp priority” flag may inform the Non- RT RIC 106 about the priority level of the rApps 102 using an rApp registration or an rApp registration update procedure.

[0021] The conflict mitigation sub-module 204 may also be configured to introduce one or more new fields in the one or more CM write configuration change commands or the CM write configuration change responses for both ConMit-aware rApps and ConMit-unaware rApps. In an embodiment, the introduction of the one or more fields may be based on the one or more outcomes of the conflict mitigation. In an embodiment, the one or more new fields may include a Rollback-Notification Uniform Resource Identifier (URI) field that may be introduced in the one or more CM write configuration change commands, the HTTP status code field, andAccept / Reject response or Rollback-Notification with conflict details field. For ConMit- unaware rApps, the conflict mitigation sub-module 204 may introduce only the HTTP status code field in the CM write configuration change response(s). For the ConMit-aware rApps, the rApps may be capable of decoding additional information received from the ConMit module 108. For ConMit-aware rApps, the conflict mitigation sub-module 204 may introduce the Rollback-Notification URI field in the CM write configuration change command(s), conflict details field in the CM write configuration change response(s) if the configuration of the rApp is rejected, and notification to the rApps with conflict details field when the previously applied configuration is rolled-back.

[0022] In an embodiment, the conflict avoidance sub-module 206 may be configured to transmit details of the conflicts to the rApps 102 to avoid future conflicts. The conflict avoidance sub-module 206 may also be configured to update the write configuration change response(s) with the details of the detected conflicts. The conflict avoidance sub-module 206 may also be configured to introduce a subscription-based notification towards the rApps 102 about the detected conflicts. In an embodiment, the subscription-based notification may include one or more ConMit action details. The introduction of the subscription-based notification is explained in detail in conjunction with FIG. 7 in the forthcoming paragraphs. The conflict avoidance sub-module 206 may also be configured to introduce a CM configuration guidance procedure from the ConMit module 108 towards the rApps 102. In an embodiment, the CM configuration guidance procedure may include one or more of guidance to resolve potential conflicts, and guidance to avoid future conflicts. The CM configuration guidance procedure is explained in detail in conjunction with FIG. 8 in the forthcoming paragraphs.

[0023] FIG. 3 illustrates a sequence flow diagram 300 depicting the “Reject configuration” outcome for the ConMit-unaware rApps, according to an embodiment of the present disclosure.The sequence flow diagram 300 may illustrate a sequence of operations between a ConMit-unaware rApp 302, the ConMit module 108, and the 01 Termination 110. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN 0A -related functions with ConMit).FIG. 3 shows only one ConMit-unaware rApp, however, it should be noted that any number of ConMit-unaware rApps may be used based on specific requirements.

[0024] At step 304, the ConMit module 108 receives a write configuration changes command from the ConMit-unaware rApp 302. In an embodiment, the ConMit module 108 receives the write configuration changes command from the ConMit-unaware rApp 302 via the R1 interface 104. In an embodiment, the write configuration changes command may include configuration data for the RAN node(s) 112. At step 306, the ConMit module 108 may check the presence of any possible conflict with the previously applied or accepted configuration(s). Particularly, the ConMit module 108 may detect whether the received write configuration changes command conflicts with the previously applied or accepted configuration(s). If the ConMit module 108 does not detect any conflict, the ConMit module 108 sends the received configuration data (also referred to as “configuration changes”) to the 01 Termination 110, at step 308. Thereafter, at step 310, the ConMit module 108 transmits a write configuration changes response message to the ConMit-unaware rApp 302 indicating an acceptance of the configuration changes. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with HTTP status code ‘200 OK’. In another example, if the ConMit module 108 detects the conflict, the ConMit module 108 transmits the write configuration changes response message to the ConMit-unaware rApp 302 indicating a rejection of the configuration changes, at step 312. Since the rApp is the ConMit-unaware rApp 302, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘409 Conflict’ upon detecting the conflict.

[0025] FIG. 4 illustrates a sequence flow diagram 400 depicting the “Reject configuration” outcome for the ConMit-aware rApps, according to an embodiment of the present disclosure. The sequence flow diagram 400 may illustrate a sequence of operations between the ConMit- aware rApps (rApp-1 402a and rApp-2402b), the ConMit module 108, and the 01 Termination 110. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN 0AM- related functions with ConMit). FIG. 4 shows only two ConMit-aware rApps, however, it should be noted that any number of ConMit-aware rApps may be used based on specific requirements.

[0026] At step 404, the ConMit module 108 receives a first write configuration changes command from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp 402a via the R1 interface 104. In an embodiment, the first write configuration changes command may include the configuration data, and the Rollback-Notification URL At step 406, the ConMit module 108 sends the configuration changes to the 01 Termination 110. Thereafter, at step 408, the ConMit module 108 transmits the write configuration changes response message to the first ConMit-aware rApp-1 402a indicating the acceptance of the configuration changes. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘200 OK’. At step 410, the ConMit module 108 receives a second write configuration changes command from the second ConMit- aware rApp-2402b. In an embodiment, the second write configuration changes command may include the configuration data, and the Rollback-Notification URL At step 412, the ConMit module 108 may check the presence of any possible conflicts with the previously applied or accepted configured on(s). Particularly, the ConMit module 108 may detect whether the received second write configuration changes command conflicts with the previously applied oraccepted configuration(s) (e.g., the configuration changes received from the first ConMit- aware rApp-1 402a). If the ConMit module 108 detects the conflict, the ConMit module 108 transmits the write configuration changes response message to the second ConMit-aware rApp- 2 402b indicating the rejection of the configuration changes received from the second ConMit- aware rApp-2 402b, at step 414. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘409 Conflict’, and the details of the detected conflicts. The details of the detected conflicts may include 01 parameters with path and values in {old, new} format, an applied timestamp, and an applied mitigation policy based on which the detected conflict has been mitigated. Table 1 below depicts an example data model for the “Reject configuration” outcome for the ConMit-aware rApps (rApp-1 402a and rApp-2 402b).Table 1: Example data model for the “Reject configuration” outcome for the ConMit-aware rApps

[0027] FIG. 5 illustrates a sequence flow diagram 500 depicting the “Accept configuration and rollback previous configuration” outcome for the ConMit-aware rApps, according to an embodiment of the present disclosure. The sequence flow diagram 500 may illustrate a sequence of operations between the ConMit-aware rApps (rApp-1 402a and rApp-2 402b), the ConMit module 108, and the 01 Termination 110. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN OAM-related functions with ConMit). FIG. 5 shows only two ConMit-aware rApps, however, it should be noted that any number of ConMit-aware rApps may be used based on specific requirements.

[0028] At step 502, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp 402a via the R1 interface 104. In an embodiment, the first write configuration changes command may include the configuration data, and the Rollback-Notification URL At step 504, the ConMit module 108 sends the configuration changes received from the first ConMit-aware rApp-1 402a to the 01 Termination 110. Thereafter, at step 506, the ConMit module 108 transmits the write configuration changes response message to the first ConMit-aware rApp-1 402a indicating the acceptance of the configuration changes. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘200 OK’. At step 508, the ConMit module 108 receives the second write configuration changes command from the second ConMit-aware rApp-2 402b. In anembodiment, the second write configuration changes command may include the configuration data, and the Rollback-Notification URL At step 510, the ConMit module 108 may check the presence of any possible conflicts with the previously applied or accepted configuration(s). Particularly, the ConMit module 108 may detect whether the configuration changes received from the second ConMit-aware rApp-2 402b conflicts with the previously applied or accepted configuration(s) (e.g., the configuration changes received from the first ConMit-aware rApp-1 402a). If the ConMit module 108 detects the conflict, the ConMit module 108 sends the configuration changes received from the second ConMit-aware rApp-2 402b to the 01 Termination 110, at step 512a. The ConMit module 108 also rolls-back the previously applied configuration changes of the first ConMit-aware rApp-1 402a, at step 512b. Thereafter, at step 514, the ConMit module 108 transmits the write configuration changes response message to the second ConMit-aware rApp-2 402b indicating the acceptance of the configuration changes received from the second ConMit-aware rApp-2 402b. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘200 OK’, and details of the detected conflicts. The details of the detected conflicts may include a list of parameters rejected or rolled-back by the ConMit module 108 such as the 01 parameters with path and values in {old, new} format, a rejected / rolled-back timestamp, and the applied mitigation policy based on which the detected conflict has been mitigated. Further, at step 516, the ConMit module 108 transmits a notification about rollback to the first ConMit- aware rApp-1 402a indicating rolling-back of the previously applied configuration changes received from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 may transmit the notification with a cause of roll-back (e.g., conflict), rolled-back 01 parameters with path and values in {old, new} format, and the details of the detected conflict. The details of the detected conflict may include a list of parameters accepted by the ConMit module 108 such as the 01 parameters with path and values in {old, new} format, an acceptedtimestamp, and the applied mitigation policy based on which the detected conflict has been mitigated. Table 2 below depicts an example data model for the “Accept configuration and rollback previous configuration” outcome for the ConMit-aware rApps (rApp-1 402a and rApp-2 402b).Table 2: Example data model for the “Accept configuration and rollback previous configuration ” outcome for the ConMit-aware rApps

[0029] FIG. 6 illustrates a sequence flow diagram 600 depicting the “Reject configuration and rollback previous configuration” outcome for the ConMit-aware rApps, according to an embodiment of the present disclosure. The sequence flow diagram 600 may illustrate a sequence of operations between the ConMit-aware rApps (rApp-1 402a and rApp-2 402b), the ConMit module 108, and the 01 Termination 110. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN OAM-related functions with ConMit). FIG. 6 shows only two ConMit-aware rApps, however, it should be noted that any number of ConMit-aware rApps may be used based on specific requirements.

[0030] At step 602, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp 402a via the R1 interface 104. In an embodiment, the first write configuration changes command may include the configuration data, and the Rollback-Notification URL At step 604, the ConMit module 108 sends the configuration changes received from the first ConMit-aware rApp-1 402a to the 01 Termination 110. Thereafter, at step 606, the ConMit module 108 transmits the write configuration changes response message to the first ConMit-aware rApp-1 402a indicating the acceptance of the configuration changes. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘200 OK’. At step 608, the ConMit module 108 receives the second write configuration changes command from the second ConMit-aware rApp-2402b. At step 610, the ConMit module 108 may check the presence of any conflict with the previously applied or accepted configured on(s). Particularly, the ConMit module 108 may detect whether the configuration changes received from the second ConMit-aware rApp-2 402b conflicts with the previously applied or accepted configuration(s) (e.g., the configuration changes received fromthe first ConMit-aware rApp-1 402a). If the ConMit module 108 detects the conflict, the ConMit module 108 rolls-back the previously applied configuration(s), at step 612. Thereafter, at step 614, the ConMit module 108 transmits the write configuration changes response message to the second ConMit-aware rApp-2402b indicating the rejection of the configuration changes received from the second ConMit-aware rApp-2402b. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘409 Conflict, and details of the detected conflicts. The details of the detected conflicts may include a list of parameters rejected or rolled-back by the ConMit module 108 such as the 01 parameters with path and values in {old, new} format, a rejected timestamp, and the applied mitigation policy based on which the detected conflict has been mitigated. Further, at step 616, the ConMit module 108 transmits the notification about the rollback to the first ConMit-aware rApp-1 402a indicating the rolling -back of the previously applied configuration changes received from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 may transmit the notification with rollback details and the details of the detected conflict. The rollback details may include the cause of the roll-back (e.g., conflict), the rolled-back 01 parameters with path and values in {old, new} format. The details of the detected conflict may include the list of parameters rejected by the ConMit module 108 such as the 01 parameters with path and values in {old, new} format, the accepted timestamp and / or a rejected / rollback timestamp, and the applied mitigation policy based on which the detected conflict has been mitigated. Table 3 below depicts an example data model for the “Reject configuration and rollback previous configuration” outcome for the ConMit-aware rApps (rApp-1 402a and rApp-2 402b).Table 3: Example data model for the “Reject configuration and rollback previous configuration ” outcome for the ConMit-aware rApps

[0031] In an optional embodiment, an rApp can subscribe to receive notifications about future detected conflicts even if the configuration changes of that rApp is accepted by the ConMit module 108. FIG. 7 illustrates a sequence flow diagram 700 depicting the subscription-based notification about the conflicts, according to an embodiment of the present disclosure. The sequence flow diagram 700 may illustrate a sequence of operations between the ConMit-awarerApps (rApp-1 402a and rApp-2 402b), the ConMit module 108, and the 01 Termination 110. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN OAM-related functions with ConMit). FIG. 7 shows only two ConMit-aware rApps, however, it should be noted that any number of ConMit-aware rApps may be used based on specific requirements.

[0032] At step 702, the ConMit module 108 receives a request to subscribe to conflict notification (also referred to as a “subscription request”) from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 receives the subscription request from the first ConMit-aware rApp 402a via the R1 interface 104. At step 704, the ConMit module 108 transmits a subscription response to the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 transmits the subscription response via the R1 interface 104. The subscription response may include a subscription ID. At step 706, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp-1 402a. In an embodiment, the ConMit module 108 receives the first write configuration changes command from the first ConMit-aware rApp 402a via the R1 interface 104. The first write configuration changes command may include the configuration data, and the Rollback- Notification URI. At step 708, the ConMit module 108 sends the configuration changes received from the first ConMit-aware rApp-1 402a to the 01 Termination 110. Thereafter, at step 710, the ConMit module 108 transmits the write configuration changes response message to the first ConMit-aware rApp-1 402a indicating the acceptance of the configuration changes. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘200 OK’. At step 712, the ConMit module 108 receives the second write configuration changes command from the second ConMit-aware rApp-2402b. The second write configuration changes command may include the configuration data, and the Rollback-Notification URI. At step 714, the ConMit module 108 may check thepresence of any possible conflicts with the previously applied or accepted configuration(s). Particularly, the ConMit module 108 may detect whether the configuration changes received from the second ConMit-aware rApp-2 402b conflicts with the previously applied or accepted configuration(s) (e.g., the configuration changes received from the first ConMit-aware rApp-1 402a). If the ConMit module 108 detects the conflict, the ConMit module 108 transmits the write configuration changes response message to the second ConMit-aware rApp-2 402b indicating the rejection of the configuration changes, at step 716. In an embodiment, the ConMit module 108 may transmit the write configuration changes response message with the HTTP status code ‘409 Conflict’, and details of the detected conflicts. The details of the detected conflicts may include the list of parameters rejected by the ConMit module 108 such as the 01 parameters with path and values in {old, new} format, the rejected timestamp, and the applied mitigation policy based on which the detected conflict has been mitigated. Further, at step 718, the ConMit module 108 notifies (via a notification) the first ConMit-aware rApp- 1 402a about the detected conflicts along with the details of the detected conflicts. Table 4 below depicts an example data model for the subscription-based notification about the conflicts.Table 4: Example data model for the subscription-based notification about the conflicts

[0033] In an embodiment, the ConMit-aware rApps may use the CM configuration guidance response received from the ConMit module 108 for resolving potential conflicts or avoiding future conflicts prior to sending the CM configuration change requests. FIG. 8 illustrates a sequence flow diagram 800 depicting the CM configuration guidance procedure, according to an embodiment of the present disclosure. The sequence flow diagram 800 may illustrate a sequence of operations between a ConMit-aware rApp 802 and the ConMit module 108. In an embodiment, the ConMit module 108 may perform one or more non-anchored functions in the SMO framework 101 or the non-RT RIC 106 (such as one or more RAN OAM-related functions with ConMit). FIG. 8 shows only one ConMit-aware rApp, however, it should be noted that any number of ConMit-aware rApps may be used based on specific requirements.

[0034] At step 804, the ConMit module 108 receives the CM configuration guidance request from the ConMit-aware rApp 802. In an embodiment, the ConMit module 108 receives the CM configuration guidance request via the R1 interface 104. The CM configuration guidance request may include the configuration changes proposed by the ConMit-aware rApp 802. At step 806, the ConMit module 108 checks for any possible conflicts. Particularly, the ConMit module 108 may detect whether the configuration changes received from the ConMit-awarerApp 802 conflicts with the previously applied or accepted configuration(s). Then, at step 808, the ConMit module 108 transmits the CM configuration change guidance response to the ConMit-aware rApp 802. In an embodiment, the ConMit module 108 transmits the CM configuration guidance response via the R1 interface 104. The CM configuration guidance response may include an indication on whether the proposed CM configuration change request may result in a conflict with one or more CM configuration change requests received from other rApps. The CM configuration guidance response may include recommendations on how the proposed CM configuration change request should be modified to avoid the possible conflict(s). Thereafter, at step 810, the ConMit-aware rApp 802 reevaluates the configuration changes based on the received CM configuration guidance response.

[0035] FIG. 9 illustrates a flowchart depicting a method 900 for integrating the rApps 102 with the ConMit functionality, in accordance with an embodiment of the present disclosure. The method 900 may be performed by the ConMit module 108.

[0036] At step 902, the ConMit module 108 may receive the configuration change command from the one or more network applications. In an embodiment, the one or more network applications comprise one of one or more rApps 102 and one or more xApps or one or more SMO applications. In an embodiment, in case the one or more network applications correspond to the one or more rApps 102, the ConMit module 108 may be implemented at the non-RT RIC 106, and the one or more rApps 102 communicate with the non-RT RIC 106 over the R1 interface 104. In an embodiment, in case the one or more network applications correspond to the one or more xApps, the ConMit module 108 may be implemented at the near-RT-RIC. In an embodiment, the configuration change command corresponds to one of the change in the one or more configurations, the change in the one or more parameters, and the change in the one or more policies, associated with the connected RAN node 112.

[0037] At step 904, the ConMit module 108 may detect whether the received configuration change command conflicts with the one or more previously applied or accepted configurations.

[0038] At step 906, in response to detecting the conflict, the ConMit module 108 may transmit the configuration change response message to the one or more network applications. In an embodiment, the configuration change response message comprises information including one or more of the rollback notification, the status code indicating the rejection of the configuration change command, and information of the detected conflict.

[0039] In one embodiment, for transmitting the configuration change response message, the ConMit module 108 may receive a registration request from each of the one or more network applications, and performing one of in response to determining that the corresponding network application is non-compatible with the ConMit module 108, transmitting the status code as the configuration change response message, and in response to determining that the corresponding network application is compatible with the ConMit module 108, transmitting the rollback notification, the status code indicating a rejection of the configuration change command, and the information of the detected conflict as the configuration change response message. In an embodiment, the registration request comprises the conflict aware flag indicating computability of the corresponding network application with the ConMit module 108.

[0040] In one embodiment, prior to transmitting the configuration change response message, the ConMit module 108 may receive the registration request from each of the one or more network applications, wherein the registration request comprises a priority of the application, and in case of detecting of the conflict, the ConMit module 108 may determine whether to accept or reject the configuration change command based on the received priorities of the plurality of applications.

[0041] In one embodiment, in response to detecting no conflict with the one or more previously applied or accepted configuration, the ConMit module 108 may transmit the configuration change response message indicating the acceptance of the configuration change command.

[0042] In one embodiment, prior to receiving the configuration change command, the ConMit module 108 may receive the configuration guidance request for one or more intended configuration changes from the one or more network applications, detect the possible conflict while implementing the one or more intended configuration changes based on the previously applied or accepted configurations, and transmit the configuration guidance response to the one or more network applications based on the detected possible conflict. In an embodiment, the configuration guidance response comprises the indication of the detected possible conflict related to the configuration change and the one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

[0043] In one embodiment, the ConMit module 108 may receive a subscription request from at least one of the one or more network applications (for example, the rApps 102a-102n). In an embodiment, the subscription request comprises a request to receive a notification associated with one or more potential conflicts. In response to the received subscription request and detecting the one or more potential conflicts, the ConMit module 108 may transmit the notification to the at least one of the one or more network applications. In an embodiment, the notification is associated with the one or more detected potential conflicts. In an embodiment, the notification is transmitted along with the information of the one or more detected potential conflicts.

[0044] While the above-discussed steps in FIG. 9 are shown and described in a particular sequence, the steps may occur in variations to the sequence in accordance with various embodiments. Further, a detailed description related to the various steps of FIG. 9 is already covered in the description related to FIG. 3-FIG.8 and is omitted herein for the sake of brevity.

[0045] FIG. 10 is a diagram of example components of a device 1000 (also referred to as the device / apparatus 1000), in accordance with an embodiment of the present disclosure. In one or more embodiments, the device 1000 may correspond to the ConMit module 108. As shown in FIG. 10, the device 1000 includes a processor 1010, a memory 1020, a storage component 1030, an input component 1040, an output component 1050, a communication interface 1060, and a bus 1070.

[0046] The processor 1010, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 1010 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 the like. The processor 1010 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.

[0047] The memory 1020 includes a non-transitory computer-readable medium. The memory 1020 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 1010. The memory 1020 comprises machine-readable instructions which are executable by the processor 1010. These machine-readable instructions when executed by the processor 1010 cause the processor 1010 to perform one or more method steps of an embodiment described above. In an embodiment, the ConMit module 108 as shown in FIG. 1, and the corresponding sub-modules, i.e., the conflict detection sub-module 202, the conflict reduction sub-module204, and the conflict avoidance sub-module 206 as shown in FIG. 2 may be implemented in the memory 1020.

[0048] The storage component 1030 stores information and / or software related to the operation and use of the device 1000. For example, the storage component 1030 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 type of non-transitory computer-readable medium, along with a corresponding drive.

[0049] The input component 1040 is configured to receive information, such as user input. For example, the input component 1040 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 1040 may include a sensor for sensing information (e.g., a Global Positioning System (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0050] The output component 1050 is configured to provide output information from the device 600. For example, the output component 1050 maybe, but is not limited to, a display, a speaker, an instruction device to an external device, and / or one or more Light-Emitting Diodes (LEDs).

[0051] The communication interface 1060 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 1060 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 1000 and other devices. In other words, the standard of the communication interface 1060 is not limited.

[0052] The bus 1070 acts as an interconnect between the processor 1010, the memory 1020, the storage component 1030, the input component 1040, the output component 1050, and the communication interface 1060 of the device 1000. The bus 1070 may include a wired interconnection or a wireless interconnection.

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

[0054] It is understood that terms including “unit” or “module” at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

[0055] The present disclosure proposes a standard mechanism to inform the rApps via the R1 interface about the detected conflicts by the ConMit functionality during the CM write configuration. The present disclosure enables the rApps to utilize the information about the detected conflicts to minimize or preempt future conflicts. Further, the present disclosure standardizes communication between the rApps and the ConMit functionality, thereby facilitating co-existence of multi-vendor rApps and an RIC platform. The present disclosure also significantly reduces potential future conflicts.

[0056] In one embodiment, a method is described. The method includes receiving, at the 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 previously applied or accepted configurations. In response to detecting the conflict, the method includes transmitting, by the ConMit module, a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of arollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0057] The method as described in

[0056] , wherein transmitting the configuration change response message comprises: receiving, at the ConMit module, a registration request from each of the one or more network applications, wherein the registration request comprises a conflict aware flag indicating computability of the corresponding network application with the ConMit module; performing one of in response to determining that the corresponding network application is non-compatible with the ConMit module, transmitting the status code as the configuration change response message; and in response to determining that the corresponding network application is compatible with the ConMit module, transmitting the rollback notification, the status code indicating a rejection of the configuration change command, and the information of the detected conflict as the configuration change response message.

[0058] The method as described in any one of

[0056] -

[0057] , wherein prior to transmitting the configuration change response message, the method comprises: receiving, at the ConMit module, a registration request from each of the one or more network applications, wherein the registration request comprises a priority of the application; and in case of detecting of the conflict, determining, by the ConMit module, whether to accept or reject the configuration change command based on the receive priorities of the plurality of applications.

[0059] The method as described in any one of

[0056] -

[0058] , wherein in response to detecting no conflict with the one or more previously applied or accepted configuration, the method comprises: transmitting, by the ConMit module, the configuration change response message indicating an acceptance of the configuration change command.

[0060] The method as described in any one of

[0056] -

[0059] , wherein prior to receiving the configuration change command, 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 previously applied or accepted configurations; 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.

[0061] The method as described in any one of

[0056] -

[0060] , 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) or any service management and orchestration (SMO) application.

[0062] The method as described in any one of

[0056] -

[0061] , wherein in case the one or more network applications correspond to the one or more rApps, the ConMit module is implemented at a non -Real Time-Radio Access Network (RAN) Intelligent Controller (non-RT-RIC), and the one or more rApps communicate with the non-RT RIC over an R1 interface.

[0063] The method as described in any one of

[0056] -

[0062] , wherein in case the one or more network applications correspond to the one or more xApps, the ConMit module is implemented at a near-Real Time-Radio Access Network (RAN) Intelligent Controller (near-RT-RIC).

[0064] The method as described in any one of

[0056] -

[0063] , wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node.

[0065] The method as described in any one of

[0056] -

[0064] , further comprising: receiving, at the ConMit module, a subscription request from at least one of the one or more network applications, wherein the subscription request comprises a request to receive a notification associated with one or more potential conflicts; in response to the received subscription request and detecting the one or more potential conflicts, transmitting, by the ConMit module, the notification to the at least one of the one or more network applications, wherein the notification is associated with the one or more detected potential conflicts, and wherein the notification is transmitted along with the information of the one or more detected potential conflicts.

[0066] In one embodiment, an apparatus is described. 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 previously applied or accepted configurations. In response to detecting the conflict, the apparatus is configured to transmit a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0067] The apparatus as described in

[0066] , wherein to transmit the configuration change response message, the apparatus is configured to: receive a registration request from each of the one or more network applications, wherein the registration request comprises a conflict aware flag indicating computability of the corresponding network application with the apparatus; perform one of in response to determining that the corresponding network application is noncompatible with the apparatus, transmit the status code as the configuration change response message; and in response to determining that the corresponding network application is compatible with the apparatus, transmit the rollback notification, the status code indicating a rejection of the configuration change command, and the information of the detected conflict as the configuration change response message.

[0068] The apparatus as described in any one of

[0066] -

[0067] , wherein prior to transmitting the configuration change response message, the apparatus is configured to: receive a registration request from each of the one or more network applications, wherein the registration request comprises a priority of the application; and in case of detecting of the conflict, determine whether to accept or reject the configuration change command based on the receive priorities of the plurality of applications.

[0069] The apparatus as described in any one of

[0066] -

[0068] , wherein in response to detection of no conflict with the one or more previously applied or accepted configuration, the apparatus is further configured to: transmit the configuration change response message indicating an acceptance of the configuration change command.

[0070] The apparatus as described in any one of

[0066] -

[0069] , wherein prior to receipt of the configuration change command, 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 previously applied or accepted configurations; 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 or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

[0071] The apparatus as described in any one of

[0066] -

[0070] , 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).

[0072] The apparatus as described in any one of

[0066] -

[0071] , wherein the apparatus corresponds to the ConMit module.

[0073] The apparatus as described in any one of

[0066] -

[0072] , further configured to: receive a subscription request from at least one of the one or more network applications, wherein the subscription request comprises a request to receive a notification associated with one or more potential conflicts; in response to the received subscription request and detecting the one or more potential conflicts, transmit the notification to the at least one of the one or more network applications, wherein the notification is associated with the one or more detected potential conflicts, and wherein the notification is transmitted along with the information of the one or more detected potential conflicts

[0074] A non-transitory computer-readable medium storing instructions is described. The instructions comprise one or more instructions that are executed by the ConMit module. The ConMit module comprises one or more processors. The one or more 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 previously applied or accepted configurations. In response to detecting the conflict, the one or more instructions cause the one or more processors to transmit a configuration change response message to the one or more network applications. The configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

[0075] 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.

[0076] 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.

[0077] 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 performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly givenin 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.

[0078] 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.

[0079] 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, readily modify and 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 previously applied or accepted configurations; and in response to detecting the conflict, transmitting, by the ConMit module, a configuration change response message to the one or more network applications, wherein the configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

2. The method as claimed in claim 1, wherein transmitting the configuration change response message comprises: receiving, at the ConMit module, a registration request from each of the one or more network applications, wherein the registration request comprises a conflict aware flag indicating computability of the corresponding network application with the ConMit module; performing one of: in response to determining that the corresponding network application is non-compatible with the ConMit module, transmitting the status code as the configuration change response message; and in response to determining that the corresponding network application is compatible with the ConMit module, transmitting the rollback notification, the status code indicating a rejection of the configuration change command, and the information of the detected conflict as the configuration change response message.

3. The method as claimed in claim 1, wherein prior to transmitting the configuration change response message, the method comprises: receiving, at the ConMit module, the registration request from each of the one or more network applications, wherein the registration request comprises a priority of the application; and in case of detecting of the conflict, determining, by the ConMit module, whether to accept or reject the configuration change command based on the received priorities of the plurality of applications.

4. The method as claimed in claim 1, wherein in response to detecting no conflict with the one or more previously applied or accepted configuration, the method comprises: transmitting, by the ConMit module, the configuration change response message indicating an acceptance of the configuration change command.

5. The method as claimed in claim 1, wherein prior to receiving the configuration change command, 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 previously applied or accepted configurations; 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 tothe configuration change and one or more recommendations on modifications of the configuration change request to prevent the detected possible conflict.

6. The method as claimed in claim 1, wherein the one or more network applications comprise one of one or more radio access network Applications (rApps), one or more extensible Applications (xApps), and one or more service management and orchestration (SMO) applications.

7. The method as claimed in claim 6, wherein in case the one or more network applications correspond to the one or more rApps, the ConMit module is implemented at a non-Real Time- Radio Access Network (RAN) Intelligent Controller (non-RT-RIC), and the one or more rApps communicate with the non-RT RIC over an R1 interface.

8. The method as claimed in claim 6, wherein in case the one or more network applications correspond to the one or more xApps, the ConMit module is implemented at a near-Real Time- Radio Access Network (RAN) Intelligent Controller (near-RT-RIC).

9. The method as claimed in claim 1, wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node.

10. The method as claimed in claim 1, further comprising: receiving, at the ConMit module, a subscription request from at least one of the one or more network applications, wherein the subscription request comprises a request to receive a notification associated with one or more potential conflicts;in response to received subscription request and detecting the one or more potential conflicts, transmitting, by the ConMit module, the notification to the at least one of the one or more network applications, wherein the notification is associated with the one or more detected potential conflicts, and wherein the notification is transmitted along with the information of the one or more detected potential conflicts.

11. 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 previously applied or accepted configurations; and in response to detecting the conflict, transmit a configuration change response message to the one or more network applications, wherein the configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

12. The apparatus as claimed in claim 11, wherein to transmit the configuration change response message, the apparatus is configured to: receive a registration request from each of the one or more network applications, wherein the registration request comprises a conflict aware flag indicating computability of the corresponding network application with the apparatus; perform one of: in response to determining that the corresponding network application is noncompatible with the apparatus, transmit the status code as the configuration change response message; andin response to determining that the corresponding network application is compatible with the apparatus, transmit the rollback notification, the status code indicating a rejection of the configuration change command, and the information of the detected conflict as the configuration change response message.

13. The apparatus as claimed in claim 11, wherein prior to transmitting the configuration change response message, the apparatus is configured to: receive the registration request from each of the one or more network applications, wherein the registration request comprises a priority of the application; and in case of detecting of the conflict, determine whether to accept or reject the configuration change command based on the received priorities of the plurality of applications.

14. The apparatus as claimed in claim 11, wherein in response to detection of no conflict with the one or more previously applied or accepted configuration, the apparatus is further configured to: transmit the configuration change response message indicating an acceptance of the configuration change command.

15. The apparatus as claimed in claim 11, wherein prior to receipt of the configuration change command, 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 previously applied or accepted configurations; 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.

16. The apparatus as claimed in claim 11, wherein the one or more network applications comprise one of one or more radio access network Applications (rApps), one or more extensible Applications (xApps), and one or more service management and orchestration (SMO) applications.

17. The apparatus as claimed in claim 11, the apparatus corresponds to a conflict mitigation (ConMit) module.

18. The apparatus as claimed in claim 11, wherein the configuration change command corresponds to one of a change in one or more configurations, a change in one or more parameters, and a change in one or more policies, associated with a connected Radio Access Network (RAN) node.

19. The apparatus as claimed in claim 11, further configured to: receive a subscription request from at least one of the one or more network applications, wherein the subscription request comprises a request to receive a notification associated with one or more potential conflicts; in response to the received subscription request and detecting the one or more potential conflicts, transmit the notification to the at least one of the one or more network applications,wherein the notification is associated with the one or more detected potential conflicts, and wherein the notification is transmitted along with the information of the one or more detected potential conflicts.

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 previously applied or accepted configurations; and in response to detecting the conflict, transmit a configuration change response message to the one or more network applications, wherein the configuration change response message comprises information including one or more of a rollback notification, a status code indicating a rejection of the configuration change command, and information of the detected conflict.

Images