# US 2025/0097285 A1 · Load balancing of performance management and fault management microservices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0097285 A1 - Document ID: US20250097285A1 - Status: Published application - Kind: A1 - Application number: 18/013,452 - Filed: 2022-11-29 - Published: 2025-03-20 - Earliest claimed: 2022-11-29 - Assignees: Rakuten Symphony, Inc. - Applicants: Rakuten Symphony, Inc. - Inventors: Virendra REDDY; Prasaanth GOWRAVALLI - Web page: https://patentgrep.com/patent/US20250097285A1 ## CPC - H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30) - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1004: Server selection for load balancing - H04L 67/566: Grouping or aggregating service requests, e.g. for unified processing - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - H04W 24/02: Arrangements for optimising operational condition - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method and system for load balancing of a Fault Management (FM) microservice (MS) and a Performance Management (PM) MS in a Network Function (NF) are provided. The method includes: determining whether there is a load issue in a first microservice (MS), the first MS being one of the FM and the PM MS; based on determining that there is the load issue, providing data, reported by at least one other MS for the first MS, to a second MS, the second MS being the other of the FM, and PM MS; and processing, by the second MS, the data and reporting, from the second MS to a northbound management system (NBMS), the processed data, wherein the FM MS is configured to receive the event data from the at least one MS, and the PM MS is configured to receive the performance data from the at least one MS. ## Claims ### Claim 1 A method of load balancing of a Fault Management (FM) microservice (MS) and a Performance Management (PM) MS in a Radio Access Network (RAN) Network Function (NF), performed by at least one processor, the method comprising: determining whether there is a load issue in a first microservice (MS), the first MS being one of the FM MS and the PM MS, and the load issue being an overload of processing requests with respect to raw data reported by at least one other MS of the NF; based on determining that there is the load issue in the first MS, providing data, reported by the at least one other MS of the NF for the first MS, to a second MS, the second MS being another one of the FM MS and the PM MS, and the data being performance data for the PM MS or event data for the FM MS; and based on determining that there is the load issue in the first MS, processing, by the second MS, the data and reporting, from the second MS to a northbound management system (NBMS), the processed data, wherein the FM MS is configured to receive the event data from the at least one MS, and the PM MS is configured to receive the performance data from the at least one MS. ### Claim 2 (depends on 1) The method of claim 1, further comprising: storing, by the second MS, the data in a persistent storage. ### Claim 3 (depends on 1) The method of claim 1, wherein the processing and the reporting comprises: encoding, by the second MS, the data; and reporting, by the second MS, the encoded data to the NBMS. ### Claim 4 (depends on 3) The method of claim 3, wherein, based on the first MS being the FM MS and the second MS being the PM MS, the processing further comprises enriching, by the second MS, the data, the data being the event data. ### Claim 5 (depends on 3) The method of claim 3, wherein, based on the first MS being the PM MS and the second MS being the FM MS, the processing further comprises aggregating, by the second MS, the data, the data being the performance data. ### Claim 6 (depends on 1) The method of claim 1, wherein the event data comprises information on at least one fault or error event. ### Claim 7 (depends on 1) The method of claim 1, wherein the performance data comprises at least one performance statistic or counter. ### Claim 8 A system for load balancing of a Fault Management (FM) microservice (MS) and a Performance Management (PM) MS in a Radio Access Network (RAN) Network Function (NF), the system comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions to: determine whether there is a load issue in a first microservice (MS), the first MS being one of the FM MS and the PM MS, and the load issue being an overload of processing requests with respect to raw data reported by at least one other MS of the NF; based on determining that there is the load issue in the first MS, provide data, reported by the at least one other MS of the NF for the first MS, to a second MS, the second MS being another one of the FM MS and the PM MS, and the data being performance data for the PM MS or event data for the FM MS; and based on determining that there is the load issue in the first MS, process, by the second MS, the data and report, from the second MS to a northbound management system (NBMS), the processed data, wherein the FM MS is configured to receive the event data from the at least one MS, and the PM MS is configured to receive the performance data from the at least one MS. ### Claim 9 (depends on 8) The system of claim 8, wherein the at least one processor is further configured to execute the instructions to: store, by the second MS, the data in a persistent storage. ### Claim 10 (depends on 8) The system of claim 8, wherein the at least one processor is further configured to execute the instructions to process and report by: encoding, the data; and reporting, the encoded data to the NBMS. ### Claim 11 (depends on 10) The system of claim 10, wherein, based on the first MS being the FM MS and the second MS being the PM MS, the at least one processor is further configured to execute the instructions to process the data by: enriching the data, the data being the event data. ### Claim 12 (depends on 10) The system of claim 10, wherein, based on the first MS being the PM MS and the second MS being the FM MS, the at least one processor is further configured to execute the instructions to process the data by: aggregating, by the second MS, the data being the performance data. ### Claim 13 (depends on 8) The system of claim 8, wherein the event data comprises information on at least one fault or error event. ### Claim 14 (depends on 8) The system of claim 8, wherein the performance data comprises at least one performance statistic or counter. ### Claim 15 A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor to perform a method of load balancing of a Fault Management (FM) microservice (MS) and a Performance Management (PM) MS in a Radio Access Network (RAN) Network Function (NF), performed by at least one processor, the method comprising: determining whether there is a load issue in a first microservice (MS), the first MS being one of the FM MS and the PM MS, and the load issue being an overload of processing requests with respect to raw data reported by at least one other MS of the NF; based on determining that there is the load issue in the first MS, providing data, reported by the at least one other MS of the NF for the first MS, to a second MS, the second MS being another one of the FM MS and the PM MS, and the data being performance data for the PM MS or event data for the FM MS; and based on determining that there is the load issue in the first MS, processing, by the second MS, the data and reporting, from the second MS to a northbound management system (NBMS), the processed data, wherein the FM MS is configured to receive the event data from the at least one MS, and the PM MS is configured to receive the performance data from the at least one MS. ### Claim 16 (depends on 15) The non-transitory computer-readable recording medium of claim 15 wherein the method further comprises: storing, by the second MS, the data in a persistent storage. ### Claim 17 (depends on 15) The non-transitory computer-readable recording medium of claim 15, wherein the processing and the reporting further comprises: encoding, by the second MS, the data; and reporting, by the second MS, the encoded data to the NBMS. ### Claim 18 (depends on 17) The non-transitory computer-readable recording medium of claim 17, wherein: based on the first MS being the FM MS and the second MS being the PM MS, the processing further comprises enriching, by the second MS, the data, the data being the event data. ### Claim 19 (depends on 17) The non-transitory computer-readable recording medium of claim 17, wherein: based on the first MS being the PM MS and the second MS being the FM MS, the processing further comprises aggregating, by the second MS, the data, the data being the performance data. ### Claim 20 (depends on 15) The non-transitory computer-readable recording medium of claim 15, wherein: the event data comprises information on at least one fault or error event; and the performance data comprises at least one performance statistic or counter.