Granted Patent B2

US 12,250,111 · App. 17/918,599 · Granted Mar 11, 2025

Inventors: Amber Jain (Indore, IN); Nimit Agrawal (Indore, IN); Hemant Gupta (Indore, IN)

Assignee: RAKUTEN SYMPHONY, INC.

H04L41/0686H04L41/069H04L43/0817

Abstract

Claims (56)

1. A method for cloud-native centralized fault monitoring in a telecommunication network, the method executed by one or more processors in an operation support system of the telecommunication network, the method comprising:

receiving one or more raw fault messages associated with one or more respective network devices, wherein the one or more raw fault messages are received using one or more network protocols associated with the one or more respective network devices;

identifying fault information from the one or more raw fault messages;

enriching the fault information based on continuously processing the fault information and additional contextual information; and

storing the enriched fault information in a plurality of databases, wherein a first subset of the enriched fault information is stored in a first database and a second subset of the enriched fault information is stored in a second database,

wherein the first subset of the enriched fault information includes recent fault event information, wherein the second subset of the enriched fault information includes historical fault event information, wherein the first database is a relational database, and wherein the second database is a non-relational database.

2. The method of claim 1 , wherein the identifying the fault information comprises:

integrating the one or more respective network devices; and

storing the one or more raw fault messages in an event storing framework for continuous stream processing.

3. The method of claim 2 , wherein the integrating comprises:

determining a type of network device based on the identified fault information;

adding the type of network device to an inventory of network devices; and

registering an alarm library of the type of network device to an alarm inventory.

4. The method of claim 2 , wherein the identified fault information includes at least one of a network device IP address, a network device identification number, a network device vendor ID, or a type of network device.

5. The method of claim 1 , wherein the additional contextual information includes:

at least one of a device status, a network domain, a geographic location, a radio-frequency cluster, a vendor id, or an entity management system id based on a device identification number; and

planned event information indicating outages or maintenance events in the telecommunication network.

6. The method of claim 5 , wherein the enriching comprises at least one of:

mapping a respective raw fault message from the one or more raw fault messages to a specific network device from the one or more respective network devices; or

mapping the respective raw fault message from the one or more raw fault messages to the specific network device from the one or more respective network devices and a specific alarm from an alarm inventory.

7. The method of claim 1 , further comprising:

generating one or more user reports based on the first subset of the enriched fault information and the second subset of the enriched fault information, wherein the one or more user reports is one of a customizable dashboard, a trend report, or a map-based report.

8. The method of claim 2 , wherein a first raw fault message from the one or more raw fault messages is received using a first network protocol from the one or more network protocols and a second raw fault message from the one or more raw fault messages is received using a second network protocol from the one or more network protocols, and wherein the first network protocol is different than the second network protocol.

9. The method of claim 1 , wherein the one or more raw fault messages associated with the one or more respective network devices are received via one or more entity management systems.

10. The method of claim 9 , wherein the first database is organized based on vendor ID and entity management system ID.

11. The method of claim 1 , further comprising:

based on the first subset of the enriched fault information being stored in the first database longer than a history threshold, moving the first subset of the enriched fault information from the first database to the second database.

12. An apparatus for cloud-native centralized fault monitoring in a telecommunication network, the apparatus comprising:

a memory configured to store instructions; and

one or more processors configured to execute the instructions to:

receive one or more raw fault messages associated with one or more respective network devices, wherein the one or more raw fault messages are received using one or more network protocols associated with the one or more respective network devices;

identify fault information from the one or more raw fault messages;

enrich the fault information based on continuously processing the fault information and additional contextual information; and

store the enriched fault information in a plurality of databases, wherein a first subset of the enriched fault information is stored in a first database and a second subset of the enriched fault information is stored in a second database,

wherein the first subset of the enriched fault information includes recent fault event information, wherein the second subset of the enriched fault information includes historical fault event information, wherein the first database is a relational database, and wherein the second database is a non-relational database.

13. The apparatus of claim 12 , wherein the identifying the fault information comprises:

integrating the one or more respective network devices; and

storing the one or more raw fault messages in an event storing framework for continuous stream processing.

14. The apparatus of claim 13 , wherein the integrating comprises:

determining a type of network device based on the identified fault information;

adding the type of network device to an inventory of network devices; and

registering an alarm library of the type of network device to an alarm inventory.

15. The apparatus of claim 12 , wherein the one or more processors are further configured to execute the instructions to:

generate one or more user reports based on the first subset of the enriched fault information and the second subset of the enriched fault information, wherein the one or more user reports is one of a customizable dashboard, a trend report, or a map-based report.

16. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a cloud-native centralized fault monitoring in a telecommunication network, cause the one or more processors to:

receive one or more raw fault messages associated with one or more respective network devices, wherein the one or more raw fault messages are received using one or more network protocols associated with the one or more respective network devices;

identify fault information from the one or more raw fault messages;

enrich the fault information based on continuously processing the fault information and additional contextual information; and

store the enriched fault information in a plurality of databases, wherein a first subset of the enriched fault information is stored in a first database and a second subset of the enriched fault information is stored in a second database,

wherein the first subset of the enriched fault information includes recent fault event information, wherein the second subset of the enriched fault information includes historical fault event information, wherein the first database is a relational database, and wherein the second database is a non-relational database.

17. The non-transitory computer-readable medium of claim 16 , wherein the additional contextual information includes:

at least one of a device status, a network domain, a geographic location, a radio-frequency cluster, a vendor id, or an entity management system id based on a device identification number; and

planned event information indicating outages or maintenance events in the telecommunication network.

18. The non-transitory computer-readable medium of claim 17 , wherein the enriching comprises at least one of:

mapping a respective raw fault message from the one or more raw fault messages to a specific network device from the one or more respective network devices; or

mapping the respective raw fault message from the one or more raw fault messages to the specific network device from the one or more respective network devices and a specific alarm from an alarm inventory.

Assignments (2)

Continuity (1)

References Cited (9)