US 12,719,937 B2Granted

System and method for a scalable network architecture for diverse network element management

AssigneeVerizon Patent and Licensing Inc.

InventorsKonstantinos Kanonakis, Sanjay Nayak, Manoj Chokka, Ashoka Chikkanayakanahalli Kote, Yaojun Zeng, Songtao Qiu

Life of this patent

Estimating the term…

Loading patent…

Abstract

Disclosed are systems and methods for a network framework for managing network elements (NEs) of a wireless/cellular and wireline network. The framework enables the scaling of a quantity, diversity and availability of NEs on/within a network via secure, efficient handling of multiple connectivity protocols, management protocols and/or NE data models. The framework can operate to provide a newly configured microservice architecture for the performance of NE management that is based on the specifics of NE types and/or NE protocols. Such architecture can operate as a collection (e.g., cluster) of microservices (or components) that can be independently scaled and can enable services to communicate with one another at the service level. The disclosed framework provides customized service technologies for each component/service in a configured manner so as to cluster services to specific needs/requests of each NE.

Claims19

Dependent claims

A method comprising:

executing, by a network device, configuration operations for configuration of a network element (NE) respective to a set of instances of a network service, the configuration of the NE being based on a mapping of the NE to each instance in the set of instances;
causing, by the network device, execution of scaling operations based on detected NE management thresholds related to at least one of a number of NEs per network instance, average number of instances, disconnections, failures, or central processing unit (CPU) utilization;
maintaining, by the network device, availability of the NE mapping to the set of instances via execution of an availability operation, the availability operation comprising operations to:
detect an instance failure among the set of instances,
create, in response to the detected instance failure, a new network service and corresponding service instances,
map the NE to the service instances of the new network service, the service instances including all instances in the set of instances minus the failed instance, and
reestablish the configuration of the NE by reconfiguring the NE based on the mapping to the new network service;
and
causing, by the network device, execution of the new network service via user equipment (UE) in accordance with the maintained NE mapping.

6 more elements

A network device comprising:

a processor configured to:
execute configuration operations for configuration of a network element (NE) respective to a set of instances of a network service, the configuration of the NE being based on a mapping of the NE to each instance in the set of instances;
cause execution of scaling operations based on detected NE management thresholds related to at least one of a number of NEs per network instance, average number of instances, disconnections, failures, or central processing unit (CPU) utilization;
maintain availability of the NE mapping to the set of instances via execution of an availability operation, the availability operation comprising operations to:
detect an instance failure among the set of instances,
create, in response to the detected instance failure, a new network service and corresponding service instances,
map the NE to the service instances of the new network service, the service instances including all instances in the set of instances minus the failed instance, and
reestablish the configuration of the NE by reconfiguring the NE based on the mapping to the new network service;
and
cause execution of the new network service via user equipment (UE) in accordance with the maintained NE mapping.

7 more elements

A non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a network device, cause the network device to:

execute configuration operations for configuration of a network element (NE) respective to a set of instances of a network service, the configuration of the NE being based on a mapping of the NE to each instance in the set of instances;
cause execution of scaling operations based on detected NE management thresholds related to at least one of a number of NEs per network instance, average number of instances, disconnections, failures, or central processing unit (CPU) utilization;
maintain availability of the NE mapping to the set of instances via execution of an availability operation, the availability operation comprising operations to:
detect an instance failure among the set of instances,
create, in response to the detected instance failure, a new network service and corresponding service instances,
map the NE to the service instances of the new network service, the service instances including all instances in the set of instances minus the failed instance, and
reestablish the configuration of the NE by reconfiguring the NE based on the mapping to the new network service;
and
cause execution of the new network service via user equipment (UE) in accordance with the maintained NE mapping.

6 more elements

Dependencies are inferred from the claim text.

Facts

Application: 18/231,270Filed 8 Aug 2023
Published: US 2025/0055885 A113 Feb 2025
Granted: 25 Aug 2026
Term ends: Not estimatedThe source records don’t support an estimate.

Classification9 codes

H04L 65/1013
Architectures or entities: network architectures, gateways, control or user entities
H04L 41/06
Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks: management of faults,…
H04L 41/0806
Configuration setting: for initial configuration or provisioning, e.g. plug-and-play
H04L 41/0816
Characterised by the conditions triggering a change of settings: the condition being an adaptation, e.g. in response to network events