Distributed Router Protocol Address Conversion

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing IP/Ethernet networks face inefficiencies in packet routing due to complex logic and data structure requirements at each network node, leading to increased latency, energy consumption, and resource demands, as each node must perform routing lookups repeatedly.

Innovation Solution

A distributed router protocol that treats a collection of network nodes as a single entity, converting global destination addresses into local addresses only once, allowing subsequent routing to occur within this distributed router, thereby reducing computational demands and optimizing packet forwarding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IP lookup or Ethernet routing table lookup is performed at each network node, then packet routing can be achieved, but latency increases and energy consumption increases

Engineering Contradiction:

Improvepacket routing capabilityVSAvoidlatency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Multiple network nodes are merged into a single distributed router entity. The patent combines the routing functions of multiple independent nodes into one unified distributed system, where the collective behavior of nodes 102-106 forms a single logical router. This merging eliminates the need for repeated routing lookups at each node, as the distributed router performs routing collectively, thereby reducing latency while maintaining routing capability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The distributed router is segmented into multiple internal nodes that collectively perform routing. Each node handles specific portions of the routing task based on local relevance, with routing decisions distributed across the network nodes rather than centralized in a single node. This segmentation allows parallel processing of routing decisions, reducing overall latency.

Inventive Principle:

Principle #1Segmentation

2Reliability

If IP lookup or Ethernet routing table lookup is performed at each network node, then packet routing can be achieved, but energy consumption increases

Engineering Contradiction:

Improvepacket routing capabilityVSAvoidenergy consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Inventive Principle:

Principle #5Merging (Combining)

3Ease of operation

If complex logic and data structure are used at each network node for routing lookup, then routing decisions can be made, but resource requirements increase

Engineering Contradiction:

Improverouting decision capabilityVSAvoidlogic and memory requirements

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The complex routing logic is extracted from individual network nodes and consolidated into the distributed router system. The patent removes the burden of complex routing tables and lookup logic from each node, replacing it with simpler local relevance-based addressing. Nodes only need to handle locally relevant addressing information, while the distributed router collectively manages the complex routing decisions.

Inventive Principle:

Principle #2Taking out (Extraction)

4Reliability

If global destination address is used throughout the network, then end-to-end routing can be achieved, but routing lookup complexity increases at each hop

Engineering Contradiction:

Improveend-to-end routing capabilityVSAvoidrouting lookup complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The routing process is segmented into two distinct phases: global routing for end-to-end path determination and local routing for hop-by-hop forwarding. The patent divides the addressing scheme into global destination addresses (for end-to-end routing) and locally relevant addresses (for local forwarding decisions). This segmentation allows nodes to use simple local addressing for routing lookups while maintaining global end-to-end routing capability through the distributed router.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11190447B2Routing protocol and distributed router

Publication Date: 2021.11.30 SICILY MERGER SUB II INC

AI summary

A routing protocol, the routing protocol includes the steps of: receiving a packet at an ingress node of a distributed router, the ingress node having an ingress node address, and the packet having a packet header containing a global destination address; converting the global destination address into a local destination address, the local destination address identifying a location on the distributed router; and routing the packet to the local destination address. A distributed router includes a plurality of internal network nodes, the plurality of internal network nodes including an ingress node configured to receive a packet, the ingress node having an ingress node address, and the packet having a packet header containing a global destination address for that packet; means for converting the global destination address into a local destination address, the local destination address identifying a location on the distributed router; and a routing engine configured to route the packet to the local destination address.