Protocol-Independent Data Forwarding for Encapsulated Header Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data forwarding systems are limited in processing encapsulated data units, leading to performance bottlenecks and increased resource consumption when devices communicate via networks, as they fail to modify or replace innermost headers, restricting direct communication between various devices.

Innovation Solution

A protocol independent data unit forwarding system that processes and forwards data units of various communication protocols using a common set of operations, logic, and templates, allowing flexible handling of headers and encapsulation, thereby reducing resource usage and enhancing compatibility across different network segments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If current data forwarding systems process encapsulated data units, then data transmission between devices is enabled, but performance bottlenecks and increased resource consumption occur due to inability to modify innermost headers

Engineering Contradiction:
Improvedata forwarding efficiencyVSAvoidresource consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system segments the data unit processing by separating the outer header processing (performed by the data forwarding system) from the inner header processing (performed by the encapsulated protocol system). This segmentation allows each component to operate independently and efficiently, with the outer system handling routing decisions and the inner system handling protocol-specific modifications, thereby improving overall forwarding efficiency while reducing resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The data forwarding system is designed with universal functionality to handle multiple protocol types through a single unified interface. The system can process different encapsulated protocols (Ethernet, IP, IPv6, UDP, etc.) without requiring protocol-specific processing logic in the outer system, enabling multi-protocol support while maintaining efficient resource utilization through standardized processing paths.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Device complexity

If current data forwarding systems forward encapsulated data units without modifying innermost headers, then system complexity is reduced, but device compatibility and communication flexibility are restricted

Engineering Contradiction:
Improveforwarding system complexityVSAvoiddevice communication compatibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system introduces an intermediary mechanism where the outer data forwarding system acts as a mediator that preserves the innermost header integrity while still enabling communication between diverse devices. The outer system provides the adaptability layer that handles protocol translation and routing, allowing inner systems to maintain their original complexity levels while achieving broader device compatibility through the mediating outer forwarding layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The architecture implements a nested structure where multiple protocol headers are encapsulated within each other (outer header containing inner header). This nesting allows the outer forwarding system to operate on the outermost layer without needing to modify inner headers, maintaining low complexity while the nested inner layers provide the necessary protocol-specific functionality for device compatibility.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Adaptability or versatility

If CPU intervention is used to re-cast data units, then protocol conversion capability is improved, but performance bottlenecks and resource consumption increase significantly

Engineering Contradiction:
Improveprotocol conversion capabilityVSAvoiddata forwarding throughput
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system implements self-service by enabling the encapsulated inner protocol system to automatically handle its own header modifications and protocol conversions without requiring external CPU intervention. The inner system processes its own data units through dedicated hardware or firmware paths, eliminating the need for software-based re-casting by the CPU and thereby maintaining high forwarding throughput while preserving protocol conversion capability.

Inventive Principle:
Principle #25Self-service

4Measurement precision

If protocol-specific processing is implemented for each encapsulated data unit type, then processing accuracy is improved, but system complexity and resource usage increase

Engineering Contradiction:
Improveheader processing accuracyVSAvoidprocessing system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system applies local quality by providing protocol-specific processing accuracy only where needed (in the inner encapsulated system) while maintaining simple, unified processing in the outer forwarding system. Each protocol layer processes headers with the precision appropriate to its specific requirements, rather than the entire system being optimized for all protocols, thereby achieving high processing accuracy for each protocol type without proportionally increasing overall system complexity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12388915B1Protocol independent data unit forwarding
Publication Date: 2025.08.12 ETHERNOVIA INC
  • US12388915B1 patent drawing
  • US12388915B1 patent drawing
  • US12388915B1 patent drawing

AI summary

Disclosed are systems, methods, and non-transitory computer-readable media for protocol independent data unit forwarding. A packet forwarding system receives a data unit comprising a header byte string via an input port. The packet forwarding system parses the data unit based on a header type determined based on the input port, yielding a parsing output describing the header byte string of the data unit. The packet forwarding system updates a metadata item associated with the data unit based on the parsing output and determines a packet forwarding instruction for forwarding the data unit to a destination based on the metadata item associated with the data unit. The packet forwarding system forwards the data unit to the destination based on the packet forwarding instruction and the metadata item associated with the data unit.