Distributed Routing Table Architecture for Network Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional routing systems in large networks, such as the Internet, can become bottlenecks due to centralized router failures, leading to slowed or interrupted network communications, and lack flexibility in security and protocol implementation.
Innovation Solution
A distributed routing table (DRT) architecture where multiple computing devices host portions of a routing table, with modular security, transport, and bootstrap modules enabling flexible communication protocols and secure message verification using root certificates, and a routing table management module that optimizes entries based on network locality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized router is used to direct messages, then routing control is simplified, but the system becomes a bottleneck and loses reliability when the router fails
Solution Approach 1:
The patent divides the centralized routing table into multiple distributed routing table portions stored across different computing devices. Each portion contains routing information for a subset of destinations, eliminating the single point of failure while maintaining routing functionality through distribution.
Solution Approach 2:
The patent introduces a routing table management module that acts as an intermediary to coordinate between distributed routing table portions. This module handles routing table updates, synchronizations, and queries across the distributed system, resolving the complexity of managing distributed routing without requiring a centralized controller.
2Reliability
If a distributed routing table is implemented, then reliability is improved, but the device complexity increases
Solution Approach 1:
The routing table management module performs multiple functions including storing routing information, updating routing tables, synchronizing distributed portions, and handling queries. This multi-functional design consolidates complexity into a single manageable component rather than requiring separate mechanisms for each function.
Solution Approach 2:
The patent creates distributed copies of routing table portions across multiple computing devices. Each device maintains a local copy of relevant routing information, enabling local routing decisions without requiring constant communication with a central authority, thus reducing management complexity.
3Object-affected harmful factors
If security verification is performed on all messages, then malicious behavior is minimized, but processing time increases
Solution Approach 1:
The patent performs security verification and certificate validation in advance before messages are routed and processed. By verifying certificates and checking for malicious content upfront, the system prevents harmful messages from entering the routing system, reducing the need for repeated verification during message processing.
Solution Approach 2:
The system implements self-verification mechanisms where routing table entries and messages contain embedded security information that can be automatically validated by receiving devices without requiring manual intervention or complex verification processes, thus minimizing processing time while maintaining security.
Data Source
AI summary
A Distributed Routing Table (DRT) mesh can comprise two or more nodes, each of which maintains its own routing table that represents some or all of the overall routing knowledge of the DRT mesh. Each node can be comprised of modular components that can perform various defined functions such that the features and abilities of the node can be customized by an application based on which modular components are instantiated. A routing table management module can maintain individual routing tables at each node, and can ensure that only entries that are close to the node, in a network topology sense, are maintained in the routing table. In addition, a security module can verify received messages based on an agreed-upon root certificate.