Single- and Multi-Node Datastore Architecture for Network Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network computing systems face challenges in efficiently storing and managing network routing information, particularly in large networks, where manual construction of routing tables is unfeasible, and dynamic routing can be computationally expensive and lacks safeguards against system failures.

Innovation Solution

Implementing a datastore architecture that offloads network routing information to a centralized database, which can be deployed as a single node or multiple nodes, allowing for flexible storage and processing of structured and unstructured data, and supports publish-subscribe messaging for efficient data distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If dynamic routing is used to automatically construct routing tables, then the network can act autonomously in avoiding failures and blockages, but the computational overhead and complexity increase significantly

Engineering Contradiction:
Improveautonomous routing constructionVSAvoidcomputational complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent extracts the routing table construction and storage functionality from the network devices themselves and places it in an external centralized database. This separation removes the computational burden of dynamic routing from individual devices while maintaining autonomous routing capabilities through the centralized system that collects and distributes routing information to the network.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If routing information is stored in a centralized database, then data management and distribution are simplified, but the system becomes vulnerable to single point of failure

Engineering Contradiction:
Improvedata managementVSAvoidsystem failure resistance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed database nodes that work together as a cluster. This segmentation maintains the ease of centralized data management while eliminating the single point of failure vulnerability by distributing the data storage and management across multiple independent nodes, ensuring system reliability even if individual nodes fail.

Inventive Principle:
Principle #1Segmentation

3Reliability

If multiple alternative paths are used for routing, then network reliability and load distribution improve, but the complexity of path selection and management increases

Engineering Contradiction:
Improvenetwork path redundancyVSAvoidpath management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary centralized database system that manages multiple routing paths. Instead of individual devices managing complex path selections, the intermediary database collects routing information from multiple sources, processes it, and distributes appropriate routing paths to devices. This simplifies path management at the device level while maintaining multiple alternative paths for improved reliability and load distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12445324B2Single node and multiple node datastore architecture in a network routing environment
Publication Date: 2025.10.14 ARRCUS INC
  • US12445324B2 patent drawing
  • US12445324B2 patent drawing
  • US12445324B2 patent drawing

AI summary

Systems, methods, and devices for offloading network data to a datastore. A system includes a plurality of instances of a datastore node in a single networking device, each of the plurality of instances of the datastore node comprising: a datastore; a publisher independent of the datastore for publishing data to the datastore; a subscriber independent of the datastore for receiving information from the datastore; a replicator agent configured to connect to the datastore as a publisher or a subscriber; and a persistent storage agent configured to connect to the datastore as a publisher or a subscriber.