Network Switch Protocol Translation via Canonical Packet Format

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network switch protocol translation methods, such as N-to-N protocol mapping, are complex and inefficient, leading to resource imbalances and increased complexity when adding new services or protocols, as they require implementing all possible uni-directional protocol translations, which is not linear with the number of supported protocols.

Innovation Solution

Implementing an N-to-1 protocol mapping mechanism during data ingress and a 1-to-N protocol mapping mechanism during data egress, using a Canonical Packet Format (CPF) to simplify protocol translations and distribute processing tasks between ingress and egress, reducing the number of required translations from N2 to 2N and allowing for easier addition of new services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If N-to-N protocol mapping with all N2 possible protocol translations is implemented, then complete protocol translation capability is achieved, but development complexity increases quadratically with N

Engineering Contradiction:
Improveprotocol translation capabilityVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Canonical Packet Format (CPF) as an intermediary representation between different protocol formats. Instead of implementing direct translations between all protocol pairs, each protocol is translated to and from the canonical format, reducing the number of translation paths from N2 to 2N. The CPF serves as a universal intermediate representation that simplifies the translation architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the protocol translation process into two distinct phases: ingress translation (from specific protocol to canonical format) and egress translation (from canonical format to specific protocol). This segmentation allows independent optimization of each translation direction and reduces the overall complexity by avoiding the need to implement all possible direct protocol-to-protocol translation paths.

Inventive Principle:
Principle #1Segmentation

2Reliability

If protocol translations are mainly performed during data ingress, then ingress processing is comprehensive, but resource stress increases during ingress and resource waste occurs during egress

Engineering Contradiction:
Improveprocessing completenessVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic protocol translation that adapts to the direction of data flow. During ingress, translations are performed from specific protocols to the canonical format. During egress, translations are performed from the canonical format to specific protocols. This dynamic approach ensures that translation resources are actively utilized in both directions, eliminating resource waste while maintaining processing completeness.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent ensures continuous useful action by performing protocol translations at both ingress and egress points. Rather than concentrating all translation work at one point in the data flow, the system maintains active translation capabilities throughout the data path, ensuring that resources are productively engaged regardless of the translation direction required.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If N-to-N protocol mapping is implemented, then all protocol combinations are supported, but adding a new service requires implementing an additional 2N protocol translations

Engineering Contradiction:
Improveservice support capabilityVSAvoidease of adding new services
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal Canonical Packet Format that can represent multiple protocol types. This universal format allows the system to support new services and protocols by simply adding translation paths to and from the canonical format, rather than requiring comprehensive reconfiguration of all existing translation paths. The CPF acts as a universal interface that simplifies service integration.

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

Data Source

PatentUS7970009B1Method for performing protocol translation in a network switch
Publication Date: 2011.06.28 KMIZRA LLC
  • US7970009B1 patent drawing
  • US7970009B1 patent drawing
  • US7970009B1 patent drawing

AI summary

A system and method are disclosed for processing a packet. Processing the packet comprises receiving the packet; translating the packet from a first protocol-specific format to a canonical packet format; translating the packet from the canonical packet format to a second protocol-specific format; and forwarding the packet.