IP Library Granted Patent US 12,483,470
Granted Patent B2
US 12,483,470 · App. 18/023,095 · Granted Nov 25, 2025

Optimal fault management reporting via host level northbound fault reporting agent

Inventors: Virendra Reddy (Bangalore, IN); Prasaanth Gowravalli (Bangalore, IN)
Assignee: RAKUTEN SYMPHONY, INC.
H04L41/069
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,483,470
App. No.
18/023,095
Granted
Nov 25, 2025
Kind
B2
Abstract

Provided are a method and system for handling northbound fault event reporting for the FM MS. The method, may be performed by at least one processor for reporting data to a northbound management system (NBMS), the method including: receiving, by a fault reporting microservice (FR MS) from an Fault Management microservice (FM MS) of a first Radio Access Network (RAN) Network Function (NF), first data comprising fault event data, the FR MS being a host level MS; and reporting, from the FR MS to the NBMS, the first data.

Claims (41)

1 . A method, performed by at least one processor, for reporting data to a northbound management system (NBMS), the method comprising:

receiving, by a fault reporting microservice (FR MS) from a Fault Management microservice (FM MS) of a first Radio Access Network (RAN) Network Function (NF), first data comprising fault event data, the FR MS being a host level MS; and

reporting, from the FR MS to the NBMS, the first data,

wherein the FR MS and the first RAN NF are both located within a same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS.

2 . The method as claimed in claim 1 , further comprising:

receiving, by the FR MS from another FM MS of a second RAN NF, second data comprising fault event data; and

reporting, from the FR MS to the NBMS, the second data,

wherein the FR MS, the first RAN NF, and the second RAN NF are all located within the same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS and the second RAN NF comprising the other FM MS.

3 . The method as claimed in claim 1 , wherein the fault event data comprises information on at least one fault or error event, and wherein the first RAN NF is one of an Open RAN (O-RAN) Centralized Unit (O-CU) or O-RAN Distributed Unit (O-DU).

4 . The method as claimed in claim 1 , wherein the first data is collected by the first FM MS upon detecting a fault event in the first RAN NF.

5 . The method as claimed in claim 1 , further comprising:

storing, by the FR MS, the received first data in a persistent storage for at least one of resiliency of FR MS and restart handling of FR MS.

6 . The method as claimed in claim 4 , wherein the first data is processed and/or encoded by the first FM MS after being collected.

7 . The method as claimed in claim 6 , wherein the first data is processed by enriching or aggregating by the first FM MS after being collected.

8 . An apparatus for reporting data to a northbound management system (NBMS), the apparatus comprising at least one processor configured to execute computer-executable instructions to:

receive, by a fault reporting microservice (FR MS) from an Fault Management microservice (FM MS) of a first Radio Access Network (RAN) Network Function (NF), first data comprising fault event data, the FR MS being a host level MS; and

report, from the FR MS to the NBMS, the first data,

wherein the FR MS and the first RAN NF are both located within a same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS.

9 . The apparatus as claimed in claim 8 , wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive, by the FR MS from another FM MS of a second RAN NF, second data comprising fault event data; and

report, from the FR MS to the NBMS, the second data,

wherein the FR MS, the first RAN NF, and the second RAN NF are all located within the same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS and the second RAN NF comprising the other FM MS.

10 . The apparatus as claimed in claim 8 , wherein the fault event data comprises information on at least one fault or error event.

11 . The apparatus as claimed in claim 8 , wherein the first data is collected by the first FM MS upon detecting a fault event in the first RAN NF.

12 . The apparatus as claimed in claim 8 , wherein the at least one processor is further configured to execute the computer-executable instructions to:

store, by the FR MS, the received first data in a persistent storage for at least one of resiliency of FR MS and restart handling of FR MS.

13 . The apparatus as claimed in claim 11 , wherein the first data is processed and/or encoded by the first FM MS after being collected.

14 . The apparatus as claimed in claim 13 , wherein the first data is processed by enriching or aggregating by the first FM MS after being collected.

15 . A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor to cause the at least one processor to perform a method comprising:

receiving, by a fault reporting microservice (FR MS) from an Fault Management microservice (FM MS) of a first Radio Access Network (RAN) Network Function (NF), first data comprising fault event data, the FR MS being a host level MS; and

reporting, from the FR MS to the NBMS, the first data,

wherein the FR MS and the first RAN NF are both located within a same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS.

16 . The non-transitory computer readable recording medium as claimed in claim 15 , the method further comprising:

receiving, by the FR MS from another FM MS of a second RAN NF, second data comprising fault event data; and

reporting, from the FR MS to the NBMS, the second data,

wherein the FR MS, the first RAN NF, and the second RAN NF are all located within the same host, and the FR MS is external to and distinct from the first RAN NF comprising the FM MS and the second RAN NF comprising the other FM MS.

17 . The non-transitory computer readable recording medium as claimed in claim 15 , wherein the fault event data comprises information on at least one fault or error event.

18 . The non-transitory computer readable recording medium as claimed in claim 15 , wherein the first data is collected by the first FM MS upon detecting a fault event in the first RAN NF.

19 . The non-transitory computer readable recording medium as claimed in claim 15 , the method further comprising:

storing, by the FR MS, the received first data in a persistent storage for at least one of resiliency of FR MS and restart handling of FR MS.

20 . The non-transitory computer readable recording medium as claimed in claim 18 , wherein the first data is processed and/or encoded by the first FM MS after being collected.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2024
From: ALTIOSTAR NETWORKS INDIA PRIVATE LIMITED
To: RAKUTEN SYMPHONY, INC.
Reel/Frame 068023/0473 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: REDDY, VIRENDRA; GOWRAVALLI, PRASAANTH
To: ALTIOSTAR NETWORKS INDIA PRIVATE LIMITED
Reel/Frame 062794/0465 →
Continuity (1)
Related Publication 20250080409A1 · Mar 6, 2025
References Cited (44)
US 8796883B2 · Stump · 2014 [cited by examiner]
US 10476763B2 · Holness · 2019 [cited by examiner]
US 10491453B2 · Stern · 2019 [cited by examiner]
US 10819679B2 · Peng · 2020 [cited by examiner]
US 11283693B2 · Hollis · 2022 [cited by examiner]
US 11824715B2 · Zhang · 2023 [cited by examiner]
US 11870638B1 · Rahman · 2024 [cited by examiner]
US 11876673B2 · Miriyala · 2024 [cited by examiner]
US 11968537B2 · Sharma · 2024 [cited by examiner]
US 12022306B2 · Yao · 2024 [cited by examiner]
US 12041528B2 · Park · 2024 [cited by examiner]
US 12068941B2 · Mary · 2024 [cited by examiner]
US 12075254B1 · Gupta · 2024 [cited by examiner]
US 12088453B2 · Safavi · 2024 [cited by examiner]
US 12095628B2 · Lukens · 2024 [cited by examiner]
US 12154079B2 · Ash · 2024 [cited by examiner]
US 12166637B2 · Zhu · 2024 [cited by examiner]
US 12206557B2 · Bush · 2025 [cited by examiner]
US 12245054B2 · Al-Dulaimi · 2025 [cited by examiner]
US 12245118B2 · Avetoom · 2025 [cited by examiner]
US 20170220663A1 · Zhao · 2017 [cited by examiner]
US 20190245740A1 · Kachhla · 2019 [cited by applicant]
US 20220109741A1 · Chen et al. · 2022 [cited by applicant]
US 20230037802A1 · Karampatsis · 2023 [cited by examiner]
US 20230169145A1 · Saldanha · 2023 [cited by examiner]
US 20230345264A1 · Guduru · 2023 [cited by examiner]
US 20240171545A1 · Majjiga · 2024 [cited by examiner]
US 20240172001A1 · Farooq · 2024 [cited by examiner]
US 20240187317A1 · Cui · 2024 [cited by examiner]
US 20240231843A1 · Gupta · 2024 [cited by examiner]
US 20240235959A1 · Browne · 2024 [cited by examiner]
US 20240236733A1 · Ping · 2024 [cited by examiner]
US 20240259768A1 · Zhang · 2024 [cited by examiner]
US 20240259879A1 · Ranganath · 2024 [cited by examiner]
US 20250007787A1 · Burgarella · 2025 [cited by examiner]
US 20250024284A1 · Pateromichelakis · 2025 [cited by examiner]
US 20250047345A1 · Li · 2025 [cited by examiner]
EP 4040728A1 · 2022 [cited by examiner]
EP 4475589A1 · 2024 [cited by examiner]
WO WO2015100611A1 · 2015 [cited by examiner]
WO WO2017069792A1 · 2017 [cited by examiner]
WO WO2019145049A1 · 2019 [cited by examiner]
WO WO2020208506A1 · 2020 [cited by examiner]
WO 2023283102A1 · 2023 [cited by applicant]