IP Library Granted Patent US 12,423,169
Granted Patent B2
US 12,423,169 · App. 18/021,826 · Granted Sep 23, 2025

Optimal FCAPS reporting via host level northbound reporting agent

Inventors: Virendra Reddy (Bangalore, IN); Prasaanth Gowravalli (Bangalore, IN)
Assignee: RAKUTEN SYMPHONY, INC.
G06F11/0766
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,423,169
App. No.
18/021,826
Granted
Sep 23, 2025
Kind
B2
Abstract

Provided are a method and system for handling FCAPS reporting for the FM MS and PM 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 FCAPS reporting microservice (FCAPSR 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 FCAPSR MS being a host level MS; receiving, by the FCAPSR MS from an Performance Management microservice (PM MS) of the first RAN NF, second data comprising performance data; and reporting, from the FCAPSR MS to the NBMS, at least one of the first data and the second data.

Claims (47)

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

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

receiving, by the FCAPSR MS from an Performance Management microservice (PM MS) of the first RAN NF, second data comprising performance data; and

reporting, from the FCAPSR MS to the NBMS, at least one of the first data and the second data,

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

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

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

receiving, by the FCAPSR MS from another PM MS of a second RAN NF, fourth data comprising performance data; and

reporting, from the FCAPSR MS to the NBMS, at least one of the third data and the fourth data,

wherein the FCAPSR MS, the first RAN NF, and the second RAN NF are all located within the same host, and the FCAPSR MS is external and distinct from the first RAN NF comprising the FM MS and the PM MS and the second RAN NF comprising the other FM MS and the other PM 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 performance data comprises at least one performance statistic or counter.

4. The method as claimed in claim 1 , wherein the first data is collected by the FM MS in the first RAN NF, and wherein the second data is collected by the PM MS in the first RAN NF.

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

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

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

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

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 FCAPS reporting microservice (FCAPSR 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 FCAPSR MS being a host level MS;

receive, by the FCAPSR MS from an Performance Management microservice (PM MS) of the first RAN NF, second data comprising performance data; and

report, from the FCAPSR MS to the NBMS, at least one of the first data and the second data,

wherein the FCAPSR MS and the first RAN NF are both located within a same host, and the FCAPSR MS is external and distinct from the first RAN NF comprising the FM MS and the PM 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 FCAPSR MS from another FM MS of a second RAN NF, third data comprising fault event data;

receive, by the FCAPSR MS from another PM MS of a second RAN NF, fourth data comprising performance data; and

report, from the FCAPSR MS to the NBMS, at least one of the third data and the fourth data,

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

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

11. The apparatus as claimed in claim 8 , wherein the first data is collected by the FM MS in the first RAN NF, and wherein the second data is collected by the PM MS in the first RAN NF.

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

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

14. 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 FCAPSR MS, at least one of the first data and the second data in a persistent storage for at least one of resiliency of FCAPSR MS and restart handling of FCAPSR MS.

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 FCAPS reporting microservice (FCAPSR 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 FCAPSR MS being a host level MS;

receiving, by the FCAPSR MS from an Performance Management microservice (PM MS) of the first RAN NF, second data comprising performance data; and

reporting, from the FCAPSR MS to the NBMS, at least one of the first data and the second data,

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

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

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

receiving, by the FCAPSR MS from another PM MS of a second RAN NF, fourth data comprising performance data; and

reporting, from the FCAPSR MS to the NBMS, at least one of the third data and the fourth data,

wherein the FCAPSR MS, the first RAN NF, and the second RAN NF are all located within the same host, and the FCAPSR MS is external and distinct from the first RAN NF comprising the FM MS and the PM MS and the second RAN NF comprising the other FM MS and the other PM 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, and wherein the performance data comprises at least one performance statistic or counter.

18. The non-transitory computer readable recording medium as claimed in claim 15 , wherein the first data is collected by the FM MS in the first RAN NF, and wherein the second data is collected by the PM MS in the first RAN NF.

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

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

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

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 17, 2023
From: REDDY, VIRENDRA; GOWRAVALLI, PRASAANTH
To: ALTIOSTAR NETWORKS INDIA PRIVATE LIMITED
Reel/Frame 062728/0181 →
Continuity (1)
Related Publication 20250077328A1 · Mar 6, 2025
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 examiner]
US 20140136906A1 · Power · 2014 [cited by examiner]
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 examiner]
US 20200092160A1 · Yoon · 2020 [cited by examiner]
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 et al. · 2021 [cited by applicant]
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 · 2023 [cited by examiner]
US 20230388203A1 · Bothe et al. · 2023 [cited by applicant]
US 20240095101A1 · Patro · 2024 [cited by examiner]
US 20240179079A1 · Mullally et al. · 2024 [cited by applicant]
US 20240259253A1 · Reddy · 2024 [cited by examiner]
WO 2022069033A1 · 2022 [cited by applicant]
WO 2022182396A1 · 2022 [cited by applicant]
WO 2023042142A1 · 2023 [cited by applicant]
WO 2024046588A1 · 2024 [cited by applicant]
Written Opinion dated May 16, 2023 in Application No. PCT/US23/11381. [cited by applicant]
International Search Report dated May 16, 2023 in Application No. PCT/US23/11381. [cited by applicant]
Cited By (1)
US 12,634,735