Network Backbone Fault Management

1 . A network backbone fault management system (NBFMS), for use with an Open Radio Access Network (ORAN) that includes a plurality of ORAN components, comprising:

a network operations center (NOC); and

wherein the NOC comprises:

a processor; and

a non-transitory NOC data store, coupled to the NOC processor, non-transitorily storing NOC computer instructions, which when executed by the processor, instantiate one or more computer engines, including:

a KAFKA® engine;

a representational state transfer (REST) engine;

a Query engine;

a Rule engine;

an Insights engine; and

an API engine; and

wherein the NOC data store stores data received from the one or more computer engines in a cache; and

a data lake, coupled to the NOC.

2 . The NBFMS of claim 1 ,

wherein the plurality of ORAN components includes:

a plurality of user devices;

a plurality of radio towers;

a plurality of radio units;

at least one distributed unit;

at least one centralized unit; and

at least one ORAN core.

3 . The NBFMS of claim 1 ,

wherein the NOC computer instructions include:

first computer instructions, which when executed by the NOC processor, instantiate the KAFKA® engine which performs KAFKA operations including:

monitoring a KAFKA data stream for event data, for a given event type, published by a given ORAN component of the plurality of ORAN components onto the storage coupling;

wherein the monitoring occurs in accordance with a request received from the Rules engine for monitoring of the given event type;

wherein the given ORAN component is configured as a KAFKA client;

wherein the event data includes:

 a key indicative of at least a type of event and the given ORAN component;

 a value indicative of an impact of the given event on at least one of the given ORAN component and the ORAN;

 a timestamp indicative when the given event occurred; and

 metadata pertinent to the given ORAN component and the given event; and

outputting, when the given event is detected on the KAFKA data stream, impact data to the cache;

wherein the impact data identifies, based on the event data, the given event and an impact of the given event on at least one of the given ORAN component and the ORAN.

4 . The NBFMS of claim 1 ,

wherein the NOC computer instructions include:

second computer instructions, which when executed by the NOC processor, instantiate the REST engine which performs REST operations including:

monitoring at least one web server for environment data;

determining, when environment data is detected, whether the environment data may be relevant to the given event and at least one of:

a degradation of at least one of the given ORAN component and the ORAN; and

an alleviation of the given degradation; and

outputting the environment data to the cache, when the environment data is detected by the REST engine.

5 . The NBFMS of claim 1 ,

wherein the NOC computer instructions include:

third computer instructions, which when executed by the NOC processor, instantiate the Query engine which performs Query operations including:

retrieving data lake data (DLD) from the data lake;

wherein the DLD includes:

network topology data, at a given time, for the ORAN;

retrieving at least one performance metric for at least one of the given ORAN component and the ORAN;

retrieving at least one faut metric for at least one of the given ORAN components and the ORAN; and

outputting the DLD to the cache.

6 . The NBFMS of claim 5 ,

wherein the NOC computer instructions include:

fourth computer instructions, which when executed by the NOC processor, instantiate the Rules engine which performs Rules operations including:

monitoring the cache for impact data, environment data, and DLD;

performing, in accordance with at least one business logic rule and based on one or more of the impact data, environment data and DLD, a health check on at least one of the given ORAN component and the ORAN;

wherein the business logic rule is generated based one at least one of:

 an artificial intelligence process;

 a schedule; and

 on-demand; and

wherein the business logic rule is implemented based on an importance rating of at least one of the given ORAN component and a service provided by the ORAN that is impacted by the given event;

performing root cause investigation and analysis for the given event; and

outputting results data, indicative of results obtained from the root cause investigation and analysis, to the API engine.

7 . The NBFMS of claim 1 ,

wherein the NOC computer instructions include:

fifth computer instructions, which when executed by the NOC processor, instantiate the API engine which performs API operations including:

receiving the results data from the Rules engine;

converting the results data into a humanly perceptible form results data; and

outputting the humanly perceptible form results data to a presentation device for presentation to a NOC operator.

8 . The NBFMS of claim 1 ,

wherein the NOC computer instructions include:

sixth computer instructions, which when executed by the NOC processor, instantiate the Insights engine which performs Insight operations including:

determining past characteristics of two or more past degradations;

predicting, based on the past characteristics, whether current characteristics are indicative of a likely degradation occurring within a given period; and

identifying, based on the past characteristics, actions available to at least one of avoid and reduce impacts of the likely degradation; and

generating, for presentation to a NOC operator, a result of the predicting and the actions available.

9 . A computer readable medium non-transitorily storing Network Operations Center (NOC) computer instructions including:

first computer instructions which, when executed by a NOC processor coupled to the computer readable medium, instantiates a KAFKA® engine;

wherein the KAFKA engine configures the NOC to perform KAFKA operations comprising:

monitoring a KAFKA data stream for event data, for a given event type, published by a given Open Radio Access Network (ORAN) component of a plurality of ORAN components onto a storage coupling;

wherein the monitoring occurs in accordance with a request received from a Rules engine for monitoring of the given event type;

wherein the given ORAN component is configured as a KAFKA client;

wherein the event data includes:

a key indicative of at least a type of event and the given ORAN component;

a value indicative of an impact of the given event on at least one of the given ORAN component and the ORAN;

a timestamp indicative when the given event occurred; and

metadata pertinent to the given ORAN component and the given event; and

outputting, when the given event is detected on the KAFKA data stream, impact data to the cache;

wherein the impact data identifies, based on the event data, the given event and an impact of the given event on at least one of the given ORAN component and the ORAN.

10 . The computer readable medium of claim 9 ,

wherein the plurality of ORAN components include at least one of:

a user device;

a radio tower;

a radio unit;

a distributed unit;

a centralized unit; and

an ORAN core.

11 . The computer readable medium of claim 10 ,

wherein the NOC computer instructions include second computer instructions, which when executed by the NOC processor, instantiate a representational state transfer (REST) engine which configures the NOC to performs REST operations including:

monitoring at least one web server for environment data;

determining, when environment data is detected, whether the environment data may be relevant to a given event and at least one of:

a degradation of at least one of the given ORAN component and the ORAN; and

an alleviation of the given degradation; and

outputting the environment data to the cache, when the environment data is detected by the REST engine.

12 . The computer readable medium of claim 11 ,

wherein the NOC computer instructions include third computer instructions, which when executed by the NOC processor, instantiate the Query engine which configure the NOC to perform Query operations including:

retrieving data lake data (DLD) from a data lake coupled to the NOC processor;

wherein the DLD includes network topology data, at a given time, for the ORAN;

retrieving at least one performance metric for at least one of the given ORAN component and the ORAN;

retrieving at least one faut metric for at least one of the given ORAN components and the ORAN; and

outputting the DLD to the cache.

13 . The computer readable medium of claim 12 ,

wherein the NOC computer instructions include fourth computer instructions, which, when executed by the NOC processor, instantiate a Rules engine which configures the NOC to perform Rules operations including:

monitoring the cache for impact data, environment data, and DLD;

performing, in accordance with at least one business logic rule and based on one or more of the impact data, environment data and DLD, a health check on at least one of the given ORAN components and the ORAN;

wherein the business logic rule is generated based one at least one of:

an artificial intelligence process;

a schedule; and

on-demand; and

wherein the business logic rule is implemented based on an importance rating of at least one of the given ORAN component and a service provided by the ORAN that is impacted by the given event;

performing root cause investigation and analysis for the given event; and

outputting results data, indicative of results obtained from the root cause investigation and analysis, to the API engine.

14 . The computer readable medium of claim 13 ,

wherein the NOC computer instructions include fifth computer instructions which, when executed by the NOC processor, instantiate an API engine which configures the NOC to perform API operations including:

receiving the results data from the Rules engine;

converting the results data into a humanly perceptible form results data; and

outputting the humanly perceptible form results data to a presentation device for presentation to a NOC operator.

15 . The computer readable medium of claim 14 ,

wherein the NOC computer instructions include sixth computer instructions which, when executed by the NOC processor, instantiate the Insights engine which configures the NOC to perform Insight operations including:

determining past characteristics of two or more past degradations;

predicting, based on the past characteristics, whether current characteristics are indicative of a likely degradation occurring within a given period;

identifying, based on the past characteristics, actions available to at least one of avoid and reduce impacts of the likely degradation; and

generating, for presentation to a NOC operator, a result of the predicting and the actions available.

16 . A method for managing faults on an Open Radio Access Network (ORAN) comprising:

instantiating a KAFKA® engine on a Network Operations Center (NOC) processor for the ORAN;

instantiating a representational state transfer (REST) engine on the NOC processor;

instantiating a query engine on the NOC processor;

instantiating a rules engine on the NOC processor;

instantiating an Applications Program Interface (API) engine on the NOC processor; and

instantiating an Insights engine on the NOC processor.

17 . The method of claim 16 ,

wherein the KAFKA engine configures the NOC to perform KAFKA operations comprising:

monitoring a KAFKA data stream for event data, for a given event type, published by a given ORAN component of a plurality of ORAN components onto a storage coupling;

wherein the monitoring occurs in accordance with a request received from a Rules engine for monitoring of the given event type; and

outputting, when the given event is detected on the KAFKA data stream, impact data to the cache;

wherein the impact data identifies, based on the event data, the given event and an impact of the given event on at least one of the given ORAN component and the ORAN.

18 . The method of claim 17 ,

wherein the given ORAN component is configured as a KAFKA client;

wherein the event data includes:

a key indicative of at least a type of event and the given ORAN component;

a value indicative of an impact of the given event on at least one of the given ORAN component and the ORAN;

a timestamp indicative when the given event occurred; and

metadata pertinent to the given ORAN component and the given event.

19 . The method of claim 16 ,

wherein the REST engine configures the NOC to performs REST operations including:

monitoring at least one web server, coupled to the NOC processor, for environment data;

determining, when environment data is detected, whether the environment data may be relevant to a given event and at least one of:

a degradation of at least one of a given ORAN component and the ORAN; and

an alleviation of the given degradation; and

outputting the environment data to the cache, when the environment data is detected by the REST engine.

20 . The method of claim 16 ,

wherein the Query engine configures the NOC to perform Query operations including:

retrieving data lake data (DLD) from a data lake coupled to the NOC processor;

wherein the DLD includes network topology data, at a given time, for the ORAN;

retrieving at least one performance metric for at least one of a given ORAN component and the ORAN;

retrieving at least one faut metric for at least one of the given ORAN components and the ORAN; and

outputting the DLD to the cache;

wherein the Rules engine configures the NOC to perform Rules operations including:

monitoring the cache for impact data, environment data, and DLD;

performing, in accordance with at least one business logic rule and based on one or more of the impact data, environment data and DLD, a health check on at least one of the given ORAN components and the ORAN;

wherein the business logic rule is implemented based on an importance rating of at least one of the given ORAN component and a service provided by the ORAN that is impacted by the given event;

performing root cause investigation and analysis for the given event; and

outputting results data, indicative of results obtained from the root cause investigation and analysis, to an API engine;

wherein the API engine configures the NOC to perform API operations including:

receiving the results data from the Rules engine;

converting the results data into a humanly perceptible form results data; and

outputting the humanly perceptible form results data to a presentation device for presentation to a NOC operator; and

wherein the Insights engine configures the NOC to perform Insight operations including:

determining past characteristics of two or more past degradations;

predicting, based on the past characteristics, whether current characteristics are indicative of a likely degradation occurring within a given period;

identifying, based on the past characteristics, actions available to at least one of avoid and reduce impacts of the likely degradation; and

generating, for presentation to a NOC operator, a result of the predicting and the actions available.