IP Library Granted Patent US 12,463,860
Granted Patent B2
US 12,463,860 · App. 18/018,055 · Granted Nov 4, 2025

Optimal fault management reporting via NF level northbound fault reporting agent

Inventors: Virendra Reddy (Bangalore, IN); Prasaanth Gowravalli (Bangalore, IN)
Assignee: RAKUTEN SYMPHONY, INC.
H04L41/0631H04L41/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,463,860
App. No.
18/018,055
Granted
Nov 4, 2025
Kind
B2
Abstract

Provided are a method, computer readable medium, and system for reporting data to a Northbound Management System (NBMS) via a Network Function (NF) level Northbound Fault reporting Microservice (MS) in an NF of a Radio Access Network (RAN). The method includes: receiving, by a Fault Management (FM) MS from at least one other MS of the NF, events data; processing, by the FM MS, the events data; obtaining, by the Fault reporting MS, the processed data; and reporting, from the Fault reporting MS to the NBMS, the processed data.

Claims (56)

1 . A method of reporting data to a Northbound Management System (NBMS) via a Network Function (NF) level northbound Fault reporting Microservice (MS) in an NF of a Radio Access Network (RAN), performed by at least one processor implementing the NF, the method comprising:

receiving, by a Fault Management (FM) MS from at least one other MS of the NF, event data;

processing, by the FM MS, the event data;

obtaining, by the Fault reporting MS which is independent of the FM MS, the processed event data; and

reporting, from the Fault reporting MS to the NBMS, the processed event data,

wherein the FM MS and the Fault reporting MS are independent NF level microservices in a gNB of the RAN.

2 . The method of claim 1 , further comprising:

storing, by the FM MS, the received event data in a persistent storage.

3 . The method of claim 1 , further comprising:

storing, by the FM MS, the processed event data in a persistent storage,

wherein the obtaining the processed event data comprises obtaining, by the Fault reporting MS, the processed event data received from the FM MS or read from the persistent storage.

4 . The method of claim 1 , wherein the processing comprises:

enriching and/or encoding, by the FM MS, the received event data.

5 . The method of claim 1 , further comprising:

updating, by the Fault reporting MS, a northbound reporting status of the processed event data.

6 . The method of claim 1 , wherein the event data comprises information on at least one fault or error event.

7 . The method of claim 1 , further comprising:

updating, by the Fault reporting MS, a northbound reporting status of the processed event data after reporting the processed event data to the NBMS, and

updating, by the Fault reporting MS, the northbound reporting status of the processed event data, based on receipt of acknowledgement from the NBMS.

8 . A system for reporting data to a Northbound Management System (NBMS) via a Network Function (NF) level Northbound Fault reporting Microservice (MS) in an NF of a RAN, the system comprising:

at least one memory storing instructions; and

at least one processor configured to execute the instructions to:

receive, by a Fault Management (FM) MS from at least one other MS of the NF, event data;

process, by the FM MS, the event data,

obtain, by the Fault reporting MS which is independent of the FM MS, the processed event data; and

report, from the Fault reporting MS to the NBMS, the processed event data,

wherein the FM MS and the Fault reporting MS are independent NF level microservices in a gNB of the RAN.

9 . The system of claim 8 , wherein the at least one processor is further configured to execute the instructions to:

store, by the FM MS, the received event data in a persistent storage.

10 . The system of claim 8 , wherein the at least one processor is further configured to execute the instructions to:

store, by the FM MS, the processed event data in a persistent storage; and

obtain, by the Fault reporting MS, the processed event data received from the FM MS or read from the persistent storage.

11 . The system of claim 8 , wherein the at least one processor is further configured to execute the instructions to process the received event data by enriching and/or encoding the received event data.

12 . The system of claim 8 , wherein the at least one processor is further configured to execute the instructions to:

update, by the Fault reporting MS, a northbound reporting status of the processed event data.

13 . The system of claim 8 , wherein the event data comprises information on at least one fault or error event.

14 . The system of claim 8 , wherein the at least one processor is further configured to execute the instructions to:

update, by the Fault reporting MS, a northbound reporting status of the processed event data after reporting the processed event data to the NBMS, and

update, by the Fault reporting MS, the northbound reporting status of the processed event data, based on receipt of acknowledgement from the NBMS.

15 . A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor to perform a method for reporting data to a Northbound Management System (NBMS) via a Network Function (NF) level Fault reporting MS in an NF of a RAN, the method comprising:

receiving, by a Fault Management (FM) MS from at least one other MS of the NF, event data;

processing, by the FM MS, the event data;

obtaining, by the Fault reporting MS which is independent of the FM MS, the processed event data; and

reporting, from the Fault reporting MS to the NBMS, the processed event data,

wherein the FM MS and the Fault reporting MS are independent NF level microservices in a gNB of the RAN.

16 . The non-transitory computer-readable recording medium of claim 15 , wherein the method further comprises:

storing, by the FM MS, the received event data in a persistent storage; and

storing, by the FM MS, the processed event data in the persistent storage.

17 . The non-transitory computer-readable recording medium of claim 15 , wherein the processing comprises:

enriching and/or encoding, by the FM MS, the received event data.

18 . The non-transitory computer-readable recording medium of claim 15 , wherein the method further comprises:

updating, by the Fault reporting MS, a northbound reporting status of the processed event data.

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

20 . The non-transitory computer-readable recording medium of claim 15 , wherein the method further comprises:

updating, by the Fault reporting MS, a northbound reporting status of the processed event data after reporting the processed event data to the NBMS, and

updating, by the Fault reporting MS, the northbound reporting status of the processed event data based on receipt of acknowledgement from the NBMS.

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 Jan 26, 2023
From: REDDY, VIRENDRA; GOWRAVALLI, PRASAANTH
To: ALTIOSTAR NETWORKS INDIA PRIVATE LIMITED
Reel/Frame 062492/0317 →
Continuity (1)
Related Publication 20240250864A1 · Jul 25, 2024
References Cited (40)
US 11483218B2 · Al-Dulaimi et al. · 2022 [cited by applicant]
US 11582327B1 · Cifuentes de la Paz et al. · 2023 [cited by applicant]
US 11751056B2 · Russell · 2023 [cited by applicant]
US 11818570B2 · Rajput et al. · 2023 [cited by applicant]
US 11880419B2 · Libby et al. · 2024 [cited by applicant]
US 20060244585A1 · Bishop et al. · 2006 [cited by applicant]
US 20110191373A1 · Botros et al. · 2011 [cited by applicant]
US 20120124195A1 · Bird · 2012 [cited by applicant]
US 20140136906A1 · Power et al. · 2014 [cited by applicant]
US 20140298350A1 · Kimata · 2014 [cited by applicant]
US 20150378845A1 · Shang et al. · 2015 [cited by applicant]
US 20180367373A1 · Chou · 2018 [cited by applicant]
US 20190102717A1 · Wu et al. · 2019 [cited by applicant]
US 20200028761A1 · Holness · 2020 [cited by applicant]
US 20200092160A1 · Yoon · 2020 [cited by applicant]
US 20200322235A1 · Bothe et al. · 2020 [cited by applicant]
US 20210014113A1 · Guim Bernat et al. · 2021 [cited by applicant]
US 20210021494A1 · Yao et al. · 2021 [cited by applicant]
US 20210022024A1 · Yao · 2021 [cited by examiner]
US 20210111942A1 · Tahhan et al. · 2021 [cited by applicant]
US 20220012608A1 · Lehmann · 2022 [cited by applicant]
US 20220038902A1 · Mueck · 2022 [cited by applicant]
US 20220109741A1 · Chen et al. · 2022 [cited by applicant]
US 20220167236A1 · Melodia et al. · 2022 [cited by applicant]
US 20220231929A1 · Li et al. · 2022 [cited by applicant]
US 20220358730A1 · Otsuki et al. · 2022 [cited by applicant]
US 20220407820A1 · Kempanna et al. · 2022 [cited by applicant]
US 20230043784A1 · Chandrasekaran et al. · 2023 [cited by applicant]
US 20230336239A1 · Schmidt et al. · 2023 [cited by applicant]
US 20230337019A1 · Mehta et al. · 2023 [cited by applicant]
US 20230388203A1 · Bothe et al. · 2023 [cited by applicant]
US 20240095101A1 · Patro · 2024 [cited by examiner]
US 20240179079A1 · Mullally · 2024 [cited by examiner]
US 20240259253A1 · Reddy et al. · 2024 [cited by applicant]
WO 2022069033A1 · 2022 [cited by applicant]
WO 2022182396A1 · 2022 [cited by applicant]
WO 2023042142A1 · 2023 [cited by applicant]
WO 2024046588A1 · 2024 [cited by applicant]
International Search Report (PCT/ISA/210) dated Apr. 7, 2023 issued by the International Searching Authority in application No. PCT/US 22/53942. [cited by applicant]
Written Opinion (PCT/ISA/237) dated Apr. 7, 2023 issued by the International Searching Authority in application No. PCT/US 22/53942. [cited by applicant]
Cited By (1)
US 12,634,735