Link-Level Switch Packet Steering Without Header Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data communication systems face challenges in transparently routing data packets among multiple applications without modifying packet headers, which burdens hardware developers and application providers with additional configuration and integration requirements, and limits analysis capabilities.
Innovation Solution
A link-level data communications switch with a data communications processor and storage that steers packets among applications using rules associating ingress and egress ports, without relying on source, destination network addresses, or link-level identifiers, allowing for transparent, bump-in-the-wire processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If packet headers are modified for routing to bump-in-the-wire applications, then routing functionality is achieved, but packet analysis capabilities are limited and original addresses cannot be preserved
Solution Approach 1:
The patent segments the routing information into two parts: the original packet headers are preserved intact for analysis, while a separate data structure (connection table) stores the mapping between original addresses and application destinations. This allows routing functionality without modifying the actual packet headers.
Solution Approach 2:
The patent introduces an intermediary connection table that acts as a mediator between the original packet addresses and the bump-in-the-wire applications. The switch uses this table to translate routing information without altering the packets themselves, preserving original addresses while enabling application-specific routing.
2Ease of operation
If encapsulation headers are added to wrap packets for routing, then packet steering to applications is enabled, but device complexity increases and hardware developers must support additional header processing
Solution Approach 1:
The patent extracts the routing function from the packet header itself and places it in a separate connection table. Instead of embedding routing information in encapsulation headers that must be processed by every device in the path, the routing logic is taken out and stored externally, reducing device complexity.
Solution Approach 2:
The patent creates a copy of the routing information in the connection table rather than modifying the original packet or adding encapsulation headers. This copy contains the necessary steering information without requiring hardware to process additional header layers.
3Ease of operation
If application providers integrate new header processing, then packet routing to applications is achieved, but adaptability decreases as applications must be ported to specific hardware and OS platforms
Solution Approach 1:
The switch acts as an intermediary that handles all header processing and routing logic, allowing applications to remain platform-independent. The connection table serves as a mediator that translates generic packet flows to application-specific routing without requiring applications to understand or process hardware-specific headers.
4Ease of operation
If routers and switches are modified to track original addresses, then packet return functionality is achieved, but device complexity and integration requirements increase
Solution Approach 1:
The patent merges the address tracking functionality into the existing connection table used for forward routing. The same data structure that maps original addresses to application destinations also enables the return path, eliminating the need for separate tracking mechanisms in routers and switches.
Data Source
AI summary
Steering data communications packets for transparent, bump-in-the-wire processing among multiple data processing applications in a link-level data communications switch, the switch including data communications ports, a port connected to a first data communications network and another port connected to a second data communications network, other ports connected to the data processing applications, the switch also including rules governing the steering, including receiving in the switch from the first network data communications packets directed to the second network, each packet containing a source network address and a destination network address and steering by the switch each packet among the applications and through an egress port, such steering carried out only in accordance with the rules, using neither the source network address of the packet, the destination network address of the packet, nor any link-level identifier of any application.