# US 2026/0100902 A1 · Novel massively decentralized network automation framework, and corresponding method of operation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0100902 A1
- Document ID: US20260100902A1
- Status: Published application
- Kind: A1
- Application number: 19/347,446
- Filed: 2025-10-01
- Published: 2026-04-09
- Earliest claimed: 2024-10-08
- Assignees: Centre Tecnologic De Telecomunicacions De Catalunya
- Applicants: Centre Tecnologic De Telecomunicacions De Catalunya
- Inventors: Lluis GIFRE; Ricard VILALTA; Raul MUÑOZ
- Web page: https://patentgrep.com/patent/US20260100902A1

## CPC

- H04L 41/042: comprising distributed management centres cooperatively managing the network
- H04L 45/02: Topology update or discovery
- H04L 41/0668: by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 45/124: {using a combination of metrics}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/084: Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L 41/0893: Assignment of logical groups to network elements
- H04L 41/12: Discovery or management of network topologies
- H04L 41/34: Signalling channels for network management communication
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Different aspects of the invention provide a modular network component, which enables a highly scalable solution for optimum control and management of a network comprising multiple nodes. All network components together form a control and management plane which can intervene in determining what to do or how to resolve an incoming request, or up-scale or down-scale to efficiently handle the number of nodes being managed or maintaining communication with disconnected sub-groups of nodes, thereby minimizing the detrimental effects of network breakdowns, rendering a truly scalable as well as disaster tolerant network control and management network and corresponding method.

## Claims

### Claim 1

A network component, in a node of a network comprising a plurality of nodes, the network component configured for managing more than one network node for network control and management, synchronization and automation, the network component comprising:
a memory module configured for maintaining a copy of the data used by the network component to operate and which is exchanged with other network components;
a data bus configured for internal communications within the network component and external communications with other network components;
a servicing module configured for operating the various modules within the network component and configured for establishing and managing services provisioning;
a path computation module configured for determining the service provision path; and
a synchronization module configured for communicating and exchanging data with other network components comprising:
broadcasting reachability metrics to other network components in the network and receiving reachability metrics from other network components in the network;
computing a local domain table identifying all network components available per node based on the received reachability metrics;;
ordering, for each node, the available network components as a function of the reachability metrics;
establishing the network component with the optimum reachability metrics as the primary network component for each node; and
executing service provisioning, by the module of servicing, if established as the primary network component.

### Claim 2 (depends on 1)

The network component of claim 1, wherein the servicing module is further configured for:
managing connectivity services;
or requesting from the path computation module a corresponding path for a new service;
or managing connection requests to a south bound interface module configured for establishing a computed path through the corresponding nodes according to requested configurations;
or storing and retrieving from the memory module relevant information for the service provisioning.

### Claim 3 (depends on 1)

The network component of claim 1, wherein the synchronization module is further configured for:
monitoring the most efficient communication channels between network components of a same node;
or timely exchanging the partial replicas of information;
or detecting under-replicated data blocks and ensuring they are replicated on appropriate and relevant different nodes;
or negotiating network components operations across nodes, such as path computations, requesting partial computations and combining retrieved results;
or dealing with self-reconciliation and/or re-optimization activities between network components in the event of a disaster recovery, or a new link installation, or redirecting traffic through a recently installed, or recovered, traffic engineering link, or an entire new network location.

### Claim 4 (depends on 1)

The network component of claim 1, wherein the synchronization module is further configured for establishing the network components with the optimum reachability metrics as the primary network component for each node as a function of one or a combination of a plurality of whether the reachability metrics minimize latency, and/or maximise throughput, and/or minimize bandwidth usage, and/or minimize delay, and/or minimize costs, and/or otherwise optimize administrative metrics, and/or other metrics.

### Claim 5 (depends on 1)

The network component of claim 1, wherein the synchronization module is further configured for, in case of disaster-originated partition into a plurality of k disconnected partitions, determining that the primary network component for that node is non-operational and re-assigning the next network component in its local domain table as the new primary network component.

### Claim 6 (depends on 1)

A method, in a network component of claim 1 configured to manage more than one network node for control and management, synchronization and automation of a network comprising a plurality of nodes, the method comprising iteratively executing the steps of:
broadcasting reachability metrics to other network components in the network and receiving reachability metrics from other network components in the network;
computing a local domain table based on the received reachability metrics, the local domain table identifying all network components available per node;
ordering, for each node, the available network components as a function of the reachability metrics;
establishing the network component with the optimum reachability metrics as the primary network component for each node; and
executing service provisioning if established as the primary network component.

### Claim 7 (depends on 6)

The method of claim 6, comprising:
computing, or otherwise obtaining, reachability metrics per node in the network;
or broadcasting topological information to other network components in the network and receiving topological information from other network components in the network.

### Claim 8 (depends on 6)

The method of claim 6, comprising establishing a connectivity configuration through service-oriented architecture mechanisms prior to executing the service provisioning, comprising computing the path between origin node and destination node and identifying, using the local domain table, the primary network components for managing each node in the path and the service provision between them.

### Claim 9 (depends on 6)

The method of claim 6, comprising the servicing module:
managing connectivity services;
or requesting from the path computation module a corresponding path for a new service;
or managing connection requests to the south bound interface module configured for establishing a computed path through the corresponding nodes according to requested configurations;
or storing and retrieving from the memory module relevant information for the service provisioning.

### Claim 10 (depends on 6)

The method of claim 6, comprising the synchronization module:
monitoring the most efficient communication channels between network components of a same node;
or timely exchanging partial replicas of information;
or detecting under-replicated data blocks and ensuring they are replicated on appropriate and relevant different nodes;
or negotiating network components operations across nodes, such as path computations, requesting partial computations and combining retrieved results;
or dealing with self-reconciliation and/or re-optimization activities between network components in the event of a disaster recovery, or a new link installation, or redirecting traffic through a recently installed, or recovered, traffic engineering link, or an entire new network location.

### Claim 11 (depends on 6)

The method of claim 6, wherein one of the network components is established as the primary network component for each node as a function of one or a combination of a plurality of whether the reachability metrics minimize latency, and/or maximise throughput, and/or minimize bandwidth usage, and/or minimize delay, and/or minimize costs, and/or otherwise optimize administrative metrics, and/or other metrics.

### Claim 12 (depends on 6)

The method of claim 6, further comprising, in case of disaster-originated partition into a plurality of k disconnected partitions, determining that the primary network component for that node is non-operational and re-assigning the next network component in its local domain table as the new primary NAF component by the synchronization module.

### Claim 13 (depends on 1)

A network comprising N nodes and M network components according to claim 1 for control and management, synchronization and automation, wherein each network component is configured in a node of the plurality of nodes, wherein one network component is configured to control, or manage, n nodes, n being smaller than N, the network further comprising a communications plane configured for direct communications between network components allowing executing service provisioning by the nodes comprising the network component established as the primary network component, each primary network component established as the network component with the optimum reachability metrics from a plurality of network components ordered in a local domain table, the reachability metrics received from other network components in the network.

### Claim 14 (depends on 13)

The network of claim 13, wherein the network components form a control management plane when in communication with each other.

### Claim 15 (depends on 14)

The network of claim 14, further configured for determining one or more network breakdowns and/or outages and performing reconfiguration operations to maintain service continuity within the nodes of at least one subset of nodes.

### Claim 16 (depends on 13)

The network of claim 13, wherein:
the total number M of network components assigned to control the N nodes,
or the partial number m of network components assigned to control the n nodes,
or, in case of disaster-originated partition into a plurality of k disconnected partitions, the number m of network components assigned to control the k nodes,
is dynamically determined as a function of at least one factor such as the particular implementation scenario, geographic, administrative, topologic, equipment vendor configuration, number of nodes, expected quality of service, resiliency, history of operation and faults, or any other factor that might be implemented.

### Claim 17 (depends on 13)

A method for network control and management, synchronization and automation of a network according to claim 13, the method comprising direct communications between network components each network component configured to manage more than one network node, and executing service provisioning by the nodes comprising the network component established as the primary network component, each primary network component established as the network component with the optimum reachability metrics from a plurality of network components ordered in a local domain table, the reachability metrics received from other network components in the network.

### Claim 18

A computer program comprising instructions, once executed on a processor, for performing a method to manage more than one network node for control and management, synchronization and automation of a network comprising a plurality of nodes, the method comprising iteratively executing the steps of:
broadcasting reachability metrics to other network components in the network and receiving reachability metrics from other network components in the network;
computing a local domain table based on the received reachability metrics, the local domain table identifying all network components available per node;
ordering, for each node, the available network components as a function of the reachability metrics;
establishing the network component with the optimum reachability metrics as the primary network component for each node; and
executing service provisioning if established as the primary network component.

### Claim 19

A non-transitory computer-readable storage medium comprising instructions, once executed on a processor, for performing a method to manage more than one network node for control and management, synchronization and automation of a network comprising a plurality of nodes, the method comprising iteratively executing the steps of:
broadcasting reachability metrics to other network components in the network and receiving reachability metrics from other network components in the network;
computing a local domain table based on the received reachability metrics, the local domain table identifying all network components available per node;
ordering, for each node, the available network components as a function of the reachability metrics;
establishing the network component with the optimum reachability metrics as the primary network component for each node; and
executing service provisioning if established as the primary network component.