# US 2024/0205809 A1 · Multi-component configurations in a ran system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2024/0205809 A1 - Document ID: US20240205809A1 - Status: Published application - Kind: A1 - Application number: 18/101,557 - Filed: 2023-01-25 - Published: 2024-06-20 - Earliest claimed: 2022-12-19 - Assignees: VMware, Inc. - Applicants: VMware LLC - Inventors: Gauresh Dilip Vanjare - Web page: https://patentgrep.com/patent/US20240205809A1 ## CPC - H04L 41/0803: Configuration setting - G06F 9/4451: {User profiles; Roaming} - G06F 16/211: {Schema design and management} - G06F 16/288: {Entity relationship models} - H04L 41/024: {using relational databases for representation of network management data, e.g. managing via structured query language [SQL]} - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/082: the condition being updates or upgrades of network functionality - H04L 41/0866: Checking the configuration - H04L 41/0886: {Fully automatic configuration} - H04L 41/28: Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration - H04L 63/101: {Access control lists [ACL]} - H04L 69/08: Protocols for interworking; Protocol conversion - H04W 16/10: Dynamic resource partitioning - H04W 24/02: Arrangements for optimising operational condition - H04W 28/16: Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service] - H04W 48/16: Discovering, processing access restriction or access information - H04W 48/18: Selecting a network or a communication service - H04W 60/04: using triggered events - H04W 76/27: Transitions between radio resource control [RRC] states - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 41/14: Network analysis or design - H04L 41/16: using machine learning or artificial intelligence - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04W 84/04: Large scale networks; Deep hierarchical networks - H04W 88/18: Service support devices; Network management devices - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Some embodiments of the invention provide a method for providing automated admission control services for a RAN system. The method receives a trigger alert that includes an application identifier for an application, a dRIC identifier associated with a dRIC to which the application is to be deployed, and a set of configurations for the application that are in a first format. The method converts the set of configurations from the first format to a second format and sends the set configurations in the second format to an FCAPS management pod deployed to the dRIC. Upon receiving positive acknowledgment indicating successful implementation of the set of configurations from the FCAPS management pod, the method updates a configuration table stored in a database of the RAN with a set of admissions control information for the application. The method sends a notification to an API server for the RAN indicating the set of configurations have been successfully implemented for the application. ## Claims ### Claim 1 A method for configuring RAN (Radio Access Network) applications deployed in a RAN system comprising a RAN intelligent controller (RIC) and at least one RIC management system (RMS) for managing the RIC, the method comprising: at a configuration service of the RIC: receiving, from the RMS, a request to modify a configuration of each RAN application in a plurality of RAN applications; forwarding a configuration update to each RAN application in the plurality of RAN applications; receiving (i) at least one acknowledgment from a first RAN application of the plurality of RAN applications that the configuration update is accepted for processing and (ii) at least one acknowledgement from a second RAN application of the plurality of RAN applications that the configuration update is rejected; based on the at least one acknowledgement that the configuration update is rejected, instructing each RAN application in the plurality of RAN applications to ignore the configuration update; and in response to receiving an acknowledgement from each RAN application that the configuration update has been ignored, sending a notification to the RMS to notify the RMS that the set of RAN applications have rejected the configuration update. ### Claim 2 (depends on 1) The method of claim 1, wherein the request to modify includes intent that defines a modification to the configuration, wherein receiving the request to modify the configuration further comprises (i) storing the intent in to a cache of a running datastore of the configuration service, (ii) generating an event in response to the stored intent, and (iii) for each RAN application in the plurality of RAN applications, adding the requested modification for the RAN application to a watch list that is processed on a per-RAN application basis. ### Claim 3 (depends on 2) The method of claim 2, wherein forwarding the configuration update to each RAN application in the plurality of RAN applications comprises forwarding the configuration update from the watch list to each RAN application after the RAN application has polled the configuration service for updates during a regular polling interval of the RAN application. ### Claim 4 (depends on 3) The method of claim 3, wherein the configuration service comprises a set of processes comprising: a server process for (i) receiving the request to modify and (ii) storing the intent in the running datastore, wherein the running datastore generates the event in response to the storing of the intent; a first watcher process for receiving the generated event from the running datastore and adding the requested modification for each RAN application to the watch list that is processed by a conflict second watcher process on a per-RAN application basis; the conflict second watcher process that waits for each RAN application to poll the configuration service for updates and provides the requested modification to a worker process for distribution; and a worker process that distributes the requested modification to each RAN application in response to polling by the RAN application. ### Claim 5 (depends on 4) The method of claim 4, wherein the worker process comprises a gRPC worker process that distributes the request modification to each RAN application via gRPC. ### Claim 6 (depends on 4) The method of claim 4, wherein the worker process receives each acknowledgement from each RAN application in the plurality of RAN applications. ### Claim 7 (depends on 6) The method of claim 6, wherein each acknowledgement corresponds to a current state of the configuration update, wherein the conflict watcher process checks the state each time the worker process receives an acknowledgement from a RAN application in the plurality of RAN applications. ### Claim 8 (depends on 1) The method of claim 1, wherein the configuration update comprises an update to at least one of a log level configured for the plurality of RAN applications, an absolute radio frequency channel number assigned to the plurality of RAN applications, a request timeout period configured for the plurality of RAN applications, and whether replay for messages is enabled for the plurality of RAN applications. ### Claim 9 (depends on 1) The method of claim 1, wherein the request to modify a configuration of each RAN application in the plurality of RAN applications comprises (i) the configuration update for the plurality of RAN applications and (ii) identifiers of each RAN application in the plurality of RAN applications for which the configuration update is intended. ### Claim 10 (depends on 1) The method of claim 1, wherein the configuration service waits to receive an acknowledgement that the configuration update is accepted for processing or that the configuration update is rejected from each RAN application in the plurality of RAN applications before instructing each RAN application in the plurality of RAN applications to ignore the configuration update. ### Claim 11 A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for a configuration service of a RAN (Radio Access Network) intelligent controller (RIC) that configures RAN applications deployed in a RAN system comprising the RIC and a RIC management system (RMS) for managing the RIC, the program comprising sets of instructions for: receiving, from the RMS, a request to modify a configuration of each RAN application in a plurality of RAN applications; forwarding a configuration update to each RAN application in the plurality of RAN applications; receiving (i) at least one acknowledgment from a first RAN application of the plurality of RAN applications that the configuration update is accepted for processing and (ii) at least one acknowledgement from a second RAN application of the plurality of RAN applications that the configuration update is rejected; based on the at least one acknowledgement that the configuration update is rejected, instructing each RAN application in the plurality of RAN applications to ignore the configuration update; and in response to receiving an acknowledgement from each RAN application that the configuration update has been ignored, sending a notification to the RMS to notify the RMS that the set of RAN applications have rejected the configuration update. ### Claim 12 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the request to modify includes intent that defines a modification to the configuration, wherein the set of instructions for receiving the request to modify the configuration further comprises sets of instructions for: storing the intent in a cache of a running datastore of the configuration service; generating an event in response to the stored intent; and for each RAN application in the plurality of RAN applications, adding the requested modification for the RAN application to a watch list that is processed on a per-RAN application basis. ### Claim 13 (depends on 12) The non-transitory machine readable medium of claim 12, wherein the set of instructions for forwarding the configuration update to each RAN application in the plurality of RAN applications comprises a set of instructions for forwarding the configuration update from the watch list to each RAN application after the RAN application has polled the configuration service for updates during a regular polling interval of the RAN application. ### Claim 14 (depends on 13) The non-transitory machine readable medium of claim 13, wherein the configuration service comprises a set of processes comprising: a server process for (i) receiving the request to modify and (ii) storing the intent in the running datastore, wherein the running datastore generates the event in response to the storing of the intent; a first watcher process for receiving the generated event from the running datastore and adding the requested modification for each RAN application to the watch list that is processed by a conflict second watcher process on a per-RAN application basis; the conflict second watcher process that waits for each RAN application to poll the configuration service for updates and provides the requested modification to a worker process for distribution; and a worker process that distributes the requested modification to each RAN application in response to polling by the RAN application. ### Claim 15 (depends on 14) The non-transitory machine readable medium of claim 14, wherein the worker process comprises a gRPC worker process that distributes the request modification to each RAN application via gRPC. ### Claim 16 (depends on 14) The non-transitory machine readable medium of claim 14, wherein the worker process receives each acknowledgement from each RAN application in the plurality of RAN applications. ### Claim 17 (depends on 16) The non-transitory machine readable medium of claim 16, wherein each acknowledgement corresponds to a current state of the configuration update, wherein the conflict watcher process checks the state each time the worker process receives an acknowledgement from a RAN application in the plurality of RAN applications. ### Claim 18 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the configuration update comprises an update to at least one of a log level configured for the plurality of RAN applications, an absolute radio frequency channel number assigned to the plurality of RAN applications, a request timeout period configured for the plurality of RAN applications, and whether replay for messages is enabled for the plurality of RAN applications. ### Claim 19 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the request to modify a configuration of each RAN application in the plurality of RAN applications comprises (i) the configuration update for the plurality of RAN applications and (ii) identifiers of each RAN application in the plurality of RAN applications for which the configuration update is intended. ### Claim 20 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the configuration service waits to receive an acknowledgement that the configuration update is accepted for processing or that the configuration update is rejected from each RAN application in the plurality of RAN applications before instructing each RAN application in the plurality of RAN applications to ignore the configuration update.