Address-Based Routing in One-Dimensional Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing routing protocols for one-dimensional networks, such as distance-vector and link-state routing protocols, require extensive information exchange and maintenance of routing tables, leading to high complexity, memory requirements, and processing time, which is inefficient and not scalable with network size.

Innovation Solution

A method where nodes in a one-dimensional network are assigned unique addresses, allowing direct routing decisions based on address differences between the data unit's source and destination, eliminating the need for routing tables by using first and second hop connections determined by a threshold value, reducing memory and processing requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distance-vector or link-state routing protocols are used, then routing capability is provided, but memory requirements and processing time increase proportionally with network size

Engineering Contradiction:
Improverouting capabilityVSAvoidmemory requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and eliminates the routing table data structure from the system, replacing it with a simplified routing decision mechanism that uses only source and destination addresses to determine next-hop nodes. This removes the memory burden of storing routing tables while maintaining routing functionality through direct address-based lookup.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each node independently determines the next-hop node by comparing its own address with the destination address, without needing to query external routing tables or exchange routing information with other nodes. This self-service approach eliminates the need for centralized routing table maintenance and reduces per-node memory requirements.

Inventive Principle:
Principle #25Self-service

2Reliability

If distance-vector or link-state routing protocols are used, then routing capability is provided, but processing time to search routing tables increases with network size

Engineering Contradiction:
Improverouting capabilityVSAvoidrouting decision time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent removes the time-consuming routing table search operation by replacing it with a direct comparison between the node's address and the destination address. This extraction of the routing table eliminates the O(n) search time inherent in traditional protocols, achieving O(1) routing decision time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces the mechanical process of searching through routing table entries with a direct mathematical comparison operation. Instead of iterating through stored routing information, the system uses address arithmetic and comparison to instantly determine the next-hop node, significantly reducing processing time.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If routing tables are maintained in each node, then routing information is available, but overhead for construction and maintenance increases with network size

Engineering Contradiction:
Improverouting information availabilityVSAvoidrouting overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and eliminates the routing table maintenance mechanism entirely. Instead of constructing and updating routing tables through protocol exchanges, the system uses direct address comparison at each node, removing the overhead of table construction, updates, and synchronization while maintaining routing information availability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each node independently determines routing information by comparing its own address with the destination address, without needing to receive or process routing updates from other nodes. This eliminates the protocol overhead for routing table construction and maintenance while ensuring each node has the necessary routing information.

Inventive Principle:
Principle #25Self-service

4Reliability

If traditional routing protocols are used in one-dimensional networks, then routing is possible, but complexity is too high for the restricted topology

Engineering Contradiction:
Improverouting functionalityVSAvoidrouting complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies a routing mechanism specifically optimized for one-dimensional network topology, where nodes are arranged in a linear sequence. By exploiting the local structural property that neighbors are adjacent in the sequence, the system uses simple address comparison to determine next-hop nodes, achieving O(1) complexity instead of the O(n) complexity of general-purpose routing protocols.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the routing decision parameter from routing table lookups to direct address comparison. By using the node address and destination address as the primary parameters for routing decisions, the system adapts to the one-dimensional topology and achieves constant-time routing decisions independent of network size.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9338081B2Method and computer program products for routing a data unit
Publication Date: 2016.05.10 WSOU INVESTMENTS LLC
  • US9338081B2 patent drawing
  • US9338081B2 patent drawing

AI summary

For routing a data unit through a chain of nodes, the nodes are assigned addresses that are increasing in one direction of appearance of the nodes in the chain. For routing the data unit, the receiving node first verifies if the destination address of the data unit corresponds with the address of its first hop neighbor or its second hop neighbor, and the node routes the data unit directly to its first hop neighbor or its second hop neighbor if this is the case. Otherwise, the node determines the difference between the destination address of the data unit and its own address or the difference between the source and destination address of the data unit, selects a routing direction depending on the sign of this difference, and selects a first hop link when the difference is in magnitude below a threshold value or a second hop link when the difference is above the threshold value.