IP Library › Granted Patent US 12,634,218
Granted Patent B2
US 12,634,218 · App. 18/890,571 · Granted May 19, 2026

Cellular network component automated health checks

Inventors: Victor Elizondo Santos (Englewood, CO); Gaurang Deshmukh (Denver, CO); Dean DellaLoggia (Englewood, CO); Nidhi Gandhi (Englewood, CO); Jonathan Amdahl (Castle Rock, CO)
Assignee: Boost SubscriberCo L.L.C.
H04L43/10H04L41/12
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,634,218
App. No.
18/890,571
Granted
May 19, 2026
Kind
B2
Abstract

Systems and methods for performing automated health checks on cellular network components are disclosed. Cluster data regarding network components is obtained from a cluster management tool and used to aggregate configuration files into a master configuration file. A topology file for on-premises components is created based on the master file. Health status for each component is determined using a dataset developed from the topology file, involving extracting and joining alarm data and container orchestration platform data. A payload with health check results is generated, optionally converted to a standard format, and published to a streaming platform and cloud storage. The system enables comprehensive monitoring of cloud and on-premises components to facilitate proactive network management.

Claims (77)

1 . A method for performing health checks on network components in a cellular wireless network, the method comprising:

obtaining cluster data regarding the network components from a cluster management tool;

aggregating configuration files from multiple clusters into a master configuration file based on the cluster data;

creating a topology file for on-premises network components based on the master configuration file;

determining a health status for each of the network components based on a health status dataset developed using the topology file; and

generating a payload containing network component health check results based on the determined health status.

2 . The method of claim 1 , further comprising: converting the payload containing the network component health check results to a standardized format;

publishing the converted payload containing network component health check results to a distributed streaming platform; and

storing the converted payload containing network component health check results in a cloud storage service.

3 . The method of claim 1 wherein the determining the health status for said each of the network components based on the health status dataset developed using the topology file includes:

using the topology file, executing health check scripts to:

extract alarm data from an element management system to extract information about status of network elements;

access a container orchestration platform to extract information regarding nodes associated with containerized network components and status of the nodes;

join the alarm data and the information regarding the nodes associated with the containerized network components to generate the health status dataset including a joined health status dataset;

flatten the joined health status dataset;

add actual and expected Physical Random Access Channel (PRACH) fields to the joined health status dataset; and

detect disabled cells based on the joined health status dataset.

4 . The method of claim 3 wherein the determining the health status for said each of the network components based on the health status dataset developed using the topology file further includes:

examining parameters and metrics indicated by the health status dataset to classify a cell site status; and

examining parameters and metrics indicated by the health status dataset to classify the health status of various network components.

5 . The method of claim 3 , wherein the cluster management tool, the element management system, and the container orchestration platform are accessed via application programming interfaces (APIs).

6 . The method of claim 1 , further comprising making the network component health check results available to and displayed on a Network Operations Center (NOC) data visualization dashboard.

7 . The method of claim 1 , wherein the network components comprise one or more of a centralized unit (CU) and a distributed unit (DU).

8 . The method of claim 1 , wherein determining the health status includes:

filtering and classifying alarms;

classifying container statuses; and

evaluating criteria including cloud services router (CSR) reachability, master node status, and virtualization platform synchronization state.

9 . The method of claim 1 , wherein the method is performed within a containerized environment running on a cloud computing platform.

10 . The method of claim 1 , further comprising:

detecting, based on the network component health check results, differences between network components implemented in a cloud environment and network components implemented as on-premises devices; and

adjusting a network component health check process based on the detected differences.

11 . A system for performing health checks on network components in a cellular wireless network, the system comprising:

at least one processor; and

a memory storing instructions that, when executed by the at least one processor, cause the system to:

obtain cluster data regarding the network components from a cluster management tool;

aggregate configuration files from multiple clusters into a master configuration file based on the cluster data;

create a topology file for on-premises network components based on the master configuration file;

determine a health status for each of the network components based on a health status dataset developed using the topology file; and

generate a payload containing network component health check results based on the determined health status.

12 . The system of claim 11 , wherein the instructions further cause the system to:

convert the payload containing the network component health check results to a standardized format;

publish the converted payload containing the network component health check results to a distributed streaming platform; and

store the converted payload containing network component health check results in a cloud storage service.

13 . The system of claim 11 , wherein the determining the health status for said each of the network components based on the health status dataset developed using the topology file includes:

using the topology file to execute health check scripts to:

extracting alarm data from an element management system to extract information about status of network elements;

accessing a container orchestration platform to extract information regarding nodes associated with containerized network components and status of the nodes;

joining the alarm data and the information regarding nodes associated with the containerized network components to generate the health status dataset including a joined health status dataset;

flattening the joined health status dataset;

adding actual and expected Physical Random Access Channel (PRACH) fields to the joined health status dataset; and

detecting disabled cells based on the joined health status dataset.

14 . The system of claim 13 , wherein the determining the health status for said each of the network components based on the health status dataset developed using the topology file further includes:

examining parameters and metrics indicated by the health status dataset to classify a cell site status; and

examining parameters and metrics indicated by the health status dataset to classify the health status of various network components.

15 . The system of claim 13 , wherein the cluster management tool, the element management system, and the container orchestration platform are accessed via application programming interfaces (APIs).

16 . A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations for performing health checks on network components in a cellular wireless network, the operations comprising:

obtaining cluster data regarding the network components from a cluster management tool;

aggregating configuration files from multiple clusters into a master configuration file based on the cluster data;

creating a topology file for on-premises network components based on the master configuration file;

determining a health status for each of the network components based on a health status dataset developed using the topology file; and

generating a payload containing network component health check results based on the determined health status.

17 . The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise:

converting the payload containing the network component health check results to a standardized format;

publishing the converted payload containing the network component health check results to a distributed streaming platform; and

storing the converted payload containing the network component health check results in a cloud storage service.

18 . The non-transitory computer-readable medium of claim 16 , wherein determining the health status for said each of the network components based on the health status dataset developed using the topology file includes:

using the topology file, executing health check scripts to:

extract alarm data from an element management system to extract information about status of network elements;

access a container orchestration platform to extract information regarding nodes associated with containerized network components and status of the nodes;

join the alarm data and information regarding nodes associated with containerized network components to generate the health status dataset including a joined health status dataset;

flatten the joined health status dataset;

add actual and expected Physical Random Access Channel (PRACH) fields to the joined health status dataset; and

detect disabled cells based on the joined health status dataset.

19 . The non-transitory computer-readable medium of claim 18 , wherein determining the health status for said each of the network components based on the health status dataset developed using the topology file further includes:

examining parameters and metrics indicated by the health status dataset to classify a cell site status; and

examining parameters and metrics indicated by the health status dataset to classify the health status of various network components.

20 . The non-transitory computer-readable medium of claim 18 , wherein the cluster management tool, the element management system, and the container orchestration platform are accessed via application programming interfaces (APIs).

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2025
From: DISH WIRELESS L.L.C.
To: BOOST SUBSCRIBERCO L.L.C.
Reel/Frame 073066/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2025
From: AMDAHL, JONATHAN
To: DISH WIRELESS L.L.C.
Reel/Frame 070632/0608 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 19, 2024
From: SANTOS, VICTOR ELIZONDO; DESHMUKH, GAURANG; DELLALOGGIA, DEAN; GANDHI, NIDHI
To: DISH WIRELESS L.L.C.
Reel/Frame 068640/0115 →
Continuity (1)
Related Publication 20260081860A1 · Mar 19, 2026
References Cited (21)
US 7313735B1 · Levergood · 2007 [cited by examiner]
US 9146798B2 · Gupta · 2015 [cited by examiner]
US 9336060B2 · Nori · 2016 [cited by examiner]
US 9397905B1 · Moniz · 2016 [cited by examiner]
US 9992086B1 · Mizik · 2018 [cited by examiner]
US 10148544B2 · Prakash · 2018 [cited by examiner]
US 11575559B1 · Khanna · 2023 [cited by examiner]
US 11856052B2 · Rao Krishnagi · 2023 [cited by examiner]
US 12314119B2 · Nagesh · 2025 [cited by examiner]
US 20090049152A1 · Rimhagen · 2009 [cited by examiner]
US 20130124713A1 · Feinberg · 2013 [cited by examiner]
US 20190089618A1 · Kludy · 2019 [cited by examiner]
US 20200076701A1 · Gershaft · 2020 [cited by examiner]
US 20220263890A1 · Rao Krishnagi · 2022 [cited by examiner]
US 20230093659A1 · O'Dell · 2023 [cited by examiner]
US 20230177378A1 · Hassan · 2023 [cited by examiner]
US 20230205681A1 · Gupta · 2023 [cited by examiner]
US 20230418731A1 · Gupta · 2023 [cited by examiner]
US 20240121636A1 · Wang · 2024 [cited by examiner]
US 20240241741A1 · Padevski · 2024 [cited by examiner]
US 20240248791A1 · Biswal · 2024 [cited by examiner]