IP Library Granted Patent US 12,640,977
Granted Patent B2
US 12,640,977 · App. 18/174,070 · Granted May 26, 2026

Systems and methods for automated cross-domain root cause analysis

Inventors: Abhinav Dwivedi (Indore, IN); Abhishek Gadekar (Indore, IN); Bakir Malak (Indore, IN); Sumanthkumar Laxmirajam Eaga (Indore, IN)
Assignee: RAKUTEN SYMPHONY, INC.
H04L41/0631H04L41/0661H04L41/5009
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,640,977
App. No.
18/174,070
Granted
May 26, 2026
Kind
B2
Abstract

A method of performing cross-domain root cause analysis (RCA) includes determining whether a node of a parent domain violates a predefined parent domain condition, based on determining that the node of the parent domain violates the predefined parent domain condition, determining whether a node of at least one child domain violates a predefined child domain condition, the at least one child domain being interconnected with the parent domain that violates the predefined parent domain condition, based on determining that the node of the at least one child domain violates the predefined child domain condition, performing at least one corrective action on the at least one child domain, and based on determining that the node of the at least one child domain does not violate the predefined child domain condition, performing at least one corrective action on the parent domain that violates the predefined parent domain condition.

Claims (55)

1 . A method of performing cross-domain root cause analysis (RCA), the method comprising:

determining whether a node of a parent domain violates a predefined parent domain condition;

based on determining that the node of the parent domain violates the predefined parent domain condition, determining whether a node of at least one child domain violates a predefined child domain condition, the at least one child domain being interconnected with the parent domain that violates the predefined parent domain condition;

based on determining that the node of the at least one child domain violates the predefined child domain condition, performing at least one corrective action on the at least one child domain; and

based on determining that the node of the at least one child domain does not violate the predefined child domain condition, performing at least one corrective action on the parent domain that violates the predefined parent domain condition.

2 . The method of claim 1 , wherein the parent domain comprises one of a radio access network (RAN) domain, a transport domain and a core domain, and

wherein the at least one child domain comprises another of the RAN domain, the transport domain and the core domain.

3 . The method of claim 1 , wherein the predefined parent domain condition is generated based on at least one key performance indicator (KPI) obtained from a performance management as a service (PMaaS) database.

4 . The method of claim 3 , wherein the predefined parent domain condition is further generated based on at least one of:

fault alert information obtained from a fault management as a service (FMaaS) database; and

configuration parameter information obtained from a configuration management as a service (CMaaS) database.

5 . The method of claim 1 , wherein the predefined child domain condition is generated based on the predefined parent domain condition.

6 . The method of claim 1 , wherein performing the at least one corrective action on the at least one child domain comprises at least one of:

generating and transmitting, to a user capable of performing corrective actions, an alert indicating that the predefined child domain condition is violated;

executing a resolution method of procedure (RMOP) on the at least one child domain; and

changing configuration parameters corresponding to at least one of the predefined parent domain condition and the predefined child domain condition.

7 . The method of claim 1 , further comprising, based on determining that the node of the parent domain violates the predefined parent domain condition and prior to determining whether the node of the at least one child domain violates the predefined child domain condition:

determining whether at least one child domain is interconnected with the parent domain that violates the predefined parent domain condition; and

based on determining that no child domain is interconnected with the parent domain that violates the predefined parent domain condition, performing at least one corrective action on the parent domain that violates the predefined parent domain condition.

8 . The method of claim 1 , wherein the node of the parent domain comprises at least one of a router, an antenna, and a switch, and

wherein the node of the at least one child domain comprises at least one of a router, an antenna, and a switch.

9 . A system for performing cross-domain root cause analysis (RCA), the system comprising:

at least one memory configured to store instructions; and

at least one processor configured to execute the instructions to:

determine whether a node of a parent domain violates a predefined parent domain condition;

based on determining that the node of the parent domain violates the predefined parent domain condition, determine whether a node of at least one child domain violates a predefined child domain condition, the at least one child domain being interconnected with the parent domain that violates the predefined parent domain condition;

based on determining that the node of the at least one child domain violates the predefined child domain condition, perform at least one corrective action on the at least one child domain; and

based on determining that the node of the at least one child domain does not violate the predefined child domain condition, perform at least one corrective action on the parent domain that violates the predefined parent domain condition.

10 . The system of claim 9 , wherein the parent domain comprises one of a radio access network (RAN) domain, a transport domain and a core domain, and

wherein the at least one child domain comprises another of the RAN domain, the transport domain and the core domain.

11 . The system of claim 9 , wherein the predefined parent domain condition is generated based on at least one key performance indicator (KPI) obtained from a performance management as a service (PMaaS) database.

12 . The system of claim 11 , wherein the predefined parent domain condition is further generated based on at least one of:

fault alert information obtained from a fault management as a service (FMaaS) database; and

configuration parameter information obtained from a configuration management as a service (CMaaS) database.

13 . The system of claim 9 , wherein the predefined child domain condition is generated based on the predefined parent domain condition.

14 . The system of claim 9 , wherein the at least one processor is further configured to execute the instructions to perform the at least one corrective action on the at least one child domain by, at least one of:

generating and transmitting, to a user capable of performing corrective actions, an alert indicating that the predefined child domain condition is violated;

executing a resolution system of procedure (RMOP) on the at least one child domain; and

changing configuration parameters corresponding to at least one of the predefined parent domain condition and the predefined child domain condition.

15 . The system of claim 9 , wherein, based on determining that the node of the parent domain violates the predefined parent domain condition and prior to determining whether the node of the at least one child domain violates the predefined child domain condition, the at least one processor is further configured to execute the instructions to:

determine whether at least one child domain is interconnected with the parent domain that violates the predefined parent domain condition; and

based on determining that no child domain is interconnected with the parent domain that violates the predefined parent domain condition, perform at least one corrective action on the parent domain that violates the predefined parent domain condition.

16 . The system of claim 9 , wherein the node of the parent domain comprises at least one of a router, an antenna, and a switch, and

wherein the node of the at least one child domain comprises at least one of a router, an antenna, and a switch.

17 . A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to:

determine whether a node of a parent domain violates a predefined parent domain condition;

based on determining that the node of the parent domain violates the predefined parent domain condition, determine whether a node of at least one child domain violates a predefined child domain condition, the at least one child domain being interconnected with the parent domain that violates the predefined parent domain condition;

based on determining that the node of the at least one child domain violates the predefined child domain condition, perform at least one corrective action on the at least one child domain; and

based on determining that the node of the at least one child domain does not violate the predefined child domain condition, perform at least one corrective action on the parent domain that violates the predefined parent domain condition.

18 . The storage medium of claim 17 , wherein the parent domain comprises one of a radio access network (RAN) domain, a transport domain and a core domain, and

wherein the at least one child domain comprises another of the RAN domain, the transport domain and the core domain.

19 . The storage medium of claim 17 , wherein the predefined parent domain condition is generated based on at least one key performance indicator (KPI) obtained from a performance management as a service (PMaaS) database.

20 . The storage medium of claim 19 , wherein the predefined parent domain condition is further generated based on at least one of:

fault alert information obtained from a fault management as a service (FMaaS) database; and

configuration parameter information obtained from a configuration management as a service (CMaaS) database.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2024
From: RAKUTEN SYMPHONY INDIA PRIVATE LIMITED
To: RAKUTEN SYMPHONY, INC.
Reel/Frame 068425/0761 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2023
From: DWIVEDI, ABHINAV; GADEKAR, ABHISHEK; MALAK, BAKIR; EAGA, SUMANTHKUMAR LAXMIRAJAM
To: RAKUTEN SYMPHONY INDIA PRIVATE LIMITED
Reel/Frame 062935/0601 →
Continuity (1)
Related Publication 20240291707A1 · Aug 29, 2024
References Cited (45)
US 9697103B2 · Wang · 2017 [cited by examiner]
US 10171335B2 · Maheshwari · 2019 [cited by examiner]
US 10812318B2 · Tammana · 2020 [cited by examiner]
US 10812336B2 · Harneja · 2020 [cited by examiner]
US 10862738B2 · Tocker · 2020 [cited by examiner]
US 11017298B2 · Cormier · 2021 [cited by examiner]
US 11087263B2 · Boe · 2021 [cited by examiner]
US 11199837B2 · Cella · 2021 [cited by examiner]
US 11271795B2 · Bhalla · 2022 [cited by examiner]
US 11275775B2 · Fletcher · 2022 [cited by examiner]
US 11343150B2 · Harneja · 2022 [cited by examiner]
US 11431550B2 · Zafer · 2022 [cited by examiner]
US 11496353B2 · Chandrasekhar · 2022 [cited by examiner]
US 11501238B2 · Fletcher · 2022 [cited by examiner]
US 11539590B2 · Anwer · 2022 [cited by examiner]
US 11593029B1 · Dhuse · 2023 [cited by examiner]
US 11599407B2 · Haines · 2023 [cited by examiner]
US 11604502B2 · Menzel · 2023 [cited by examiner]
US 11620203B2 · Larkin · 2023 [cited by examiner]
US 11627033B2 · Umakanth · 2023 [cited by examiner]
US 11645131B2 · Monk · 2023 [cited by examiner]
US 11668764B2 · Menzel · 2023 [cited by examiner]
US 11716372B2 · Toth · 2023 [cited by examiner]
US 11853777B2 · Cheriton · 2023 [cited by examiner]
US 11886155B2 · Nixon · 2024 [cited by examiner]
US 11894969B2 · Barber · 2024 [cited by examiner]
US 11929899B2 · Abidi · 2024 [cited by examiner]
US 12072784B2 · Dupont · 2024 [cited by examiner]
US 12309182B1 · McAleer · 2025 [cited by examiner]
US 12333579B2 · Null · 2025 [cited by examiner]
US 20160072688A1 · Desai · 2016 [cited by examiner]
US 20180270114A1 · Indiresan · 2018 [cited by examiner]
US 20180316594A1 · Wu · 2018 [cited by examiner]
US 20220078071A1 · Agapitos · 2022 [cited by examiner]
US 20220108262A1 · Cella · 2022 [cited by examiner]
US 20220294816A1 · Martin · 2022 [cited by examiner]
US 20230010111A1 · Rahman · 2023 [cited by examiner]
US 20230189382A1 · Haustein · 2023 [cited by examiner]
US 20240056346A1 · Leask · 2024 [cited by examiner]
US 20240259879A1 · Ranganath · 2024 [cited by examiner]
CN 114024837A · 2022 [cited by examiner]
CN 116866149A · 2023 [cited by examiner]
JP 2014119982A · 2014 [cited by examiner]
WO WO2023073859A1 · 2023 [cited by examiner]
WO WO2025013004A1 · 2025 [cited by examiner]