Pseudo-Route Hardware Routing Table Stability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data packet routing systems face instability and inefficiency due to frequent additions and deletions in hardware routing tables, leading to overlapping routes and increased latency, especially when software components need to determine routes not present in hardware tables.

Innovation Solution

The method involves calculating a pseudo-route with a most specific non-overlapping route mask from overlapping software routing table routes and programmatically entering this pseudo-route into the hardware routing table, allowing for efficient data packet routing without table instability and overlapping routes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software components are used to determine routes for data packets, then routing flexibility and adaptability are improved, but routing latency increases due to additional processing time

Engineering Contradiction:

Improverouting flexibilityVSAvoidrouting latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-calculates and stores pseudo-routes in the hardware routing table based on software routing table entries before data packets arrive. This preliminary action allows the hardware to perform fast lookups without real-time software processing, reducing routing latency while maintaining flexibility through pre-computed pseudo-routes that represent software-determined routing decisions

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The pseudo-route acts as an intermediary between software routing table entries and hardware routing table lookups. It translates software-determined routes into a format suitable for hardware acceleration, enabling the hardware to perform fast routing decisions based on pre-processed software routing information without direct software involvement in real-time packet routing

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If hardware routing tables are frequently modified to add new routes, then routing adaptability is improved, but table stability deteriorates causing system instability

Engineering Contradiction:

Improverouting adaptabilityVSAvoidtable stability

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system extracts only the essential routing information from software routing table entries to create condensed pseudo-routes. By taking out only the necessary route characteristics and representing them in a simplified format, the system reduces the complexity of hardware routing table modifications while maintaining routing adaptability through the pseudo-route abstraction

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary processing of software routing table entries to generate pseudo-routes before they need to be used for actual packet routing. This advance preparation consolidates routing decisions and reduces the frequency and complexity of hardware routing table updates, improving table stability while maintaining adaptability through pre-computed pseudo-routes

Inventive Principle:

Principle #10Preliminary action

3Speed

If hardware routing tables are used for fast routing, then routing speed is improved, but routing precision deteriorates when routes are not present in hardware tables

Engineering Contradiction:

Improverouting speedVSAvoidrouting precision

Core Design Contradiction:

SpeedVSMeasurement precision

Solution Approach 1:

The pseudo-route serves as an intermediary that bridges hardware and software routing tables. It enables the hardware to perform fast lookups using pre-processed routing information that captures the precision of software routing decisions, allowing hardware-speed routing with software-level routing precision through the pseudo-route translation layer

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS7760742B2Systems and methods of using pseudo-routes for data transmissions

Publication Date: 2010.07.20 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In some embodiments of the present invention, method of routing data packets using a pseudo-route are presented including: receiving a data packet, the data packet having a destination; calculating the pseudo-route, if the destination corresponds with at least one of a plurality of software routing table routes, the pseudo-route having a most specific non-overlapping route mask derived from at least one of a plurality of overlapping software routing table routes; and routing the data packet using the pseudo-route. In some embodiments methods are presented further including: selecting a most specific route from the at least one of a plurality of software routing table routes corresponding with the destination. In some embodiments methods are presented further including: programmatically entering the pseudo-route into a hardware routing table.