Hardware Circuit System for IPv4 to IPv6 Packet Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for converting network packets between IPv4 and IPv6 networks, such as MAP-T and MAP-E, are software-implemented and consume significant computing resources, making hardware acceleration difficult.

Innovation Solution

A method and system that utilize hardware-based conversion rules implemented in a circuit system, such as an ASIC, using content, control, and forwarding mapping rule tables to convert IPv4 packets to IPv6 packets and vice versa, optimizing packet conversion through hardware acceleration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software-based conversion methods (MAP-T or MAP-E) are used for packet conversion between IPv4 and IPv6 networks, then the conversion process can be implemented with flexibility, but computing resource consumption increases significantly

Engineering Contradiction:
Improveconversion method flexibilityVSAvoidcomputing resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent replaces the software-based packet conversion mechanism with a hardware-based conversion device that uses lookup tables and circuit logic to perform address and port mapping. This substitution of mechanical/software systems with hardware systems directly reduces computing resource consumption while maintaining conversion functionality.

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

Solution Approach 2:

The patent pre-configures conversion rules, mapping relationships, and lookup tables in the hardware device before actual packet conversion occurs. By preparing conversion data structures in advance, the hardware device can perform rapid lookups and conversions without requiring complex real-time computing resources.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If software-based conversion methods are used, then implementation flexibility is maintained, but conversion performance and processing speed are limited

Engineering Contradiction:
Improveimplementation flexibilityVSAvoidpacket conversion performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent replaces software-based packet conversion with a hardware-based conversion device that uses dedicated circuits and lookup tables. This hardware implementation provides parallel processing capability and deterministic timing, dramatically improving packet conversion performance and processing speed compared to software approaches.

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

Solution Approach 2:

The patent divides the packet conversion function into separate hardware modules including lookup table units, conversion rule engines, and packet processing units. This segmentation allows each module to operate independently and in parallel, enhancing overall conversion throughput and performance.

Inventive Principle:
Principle #1Segmentation

3Use of energy by moving object

If hardware-based conversion is implemented, then computing resource consumption is reduced, but device complexity increases

Engineering Contradiction:
Improvecomputing resource consumptionVSAvoidhardware conversion device complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent uses lookup tables that store pre-defined mapping relationships and conversion rules. Instead of implementing complex conversion algorithms in hardware, the system copies and stores conversion data in lookup tables, allowing simple hardware circuits to perform conversions by table lookup, thereby reducing hardware complexity while maintaining conversion functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The hardware conversion device is designed to support multiple conversion methods (MAP-T and MAP-E) and can handle both IPv4-to-IPv6 and IPv6-to-IPv4 conversions using the same hardware architecture. This multi-functionality reduces the need for separate dedicated hardware for each conversion scenario, managing device complexity.

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

4Ease of manufacture

If software-based conversion is used, then ease of implementation is maintained, but processing time and latency increase

Engineering Contradiction:
Improveconversion implementation easeVSAvoidpacket processing time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent replaces software-based packet conversion with hardware-based conversion using dedicated circuits and lookup tables. This hardware implementation performs conversions in parallel with packet forwarding, eliminating software processing delays and significantly reducing packet processing time and network latency.

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

Solution Approach 2:

The patent pre-configures all conversion rules, mapping tables, and forwarding information in the hardware device before operation. This preliminary setup allows the hardware to perform instant lookups and conversions during packet forwarding without requiring real-time software processing, thereby minimizing processing time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12149601B2Method for converting network packets and circuit system
Publication Date: 2024.11.19 REALTEK SEMICON CORP
  • US12149601B2 patent drawing
  • US12149601B2 patent drawing
  • US12149601B2 patent drawing

AI summary

A method for converting network packets and a circuit system are provided. The circuit system uses firmware therein to record tables for implementing packet conversion between two types of networks (IPv4 and IPv6). In the method, a process of mapping of address and port using encapsulation (MAP-E) or a process of mapping of address and port using translation (MAP-T) is determined according to IPv4 packets routing requirement to embody an uplink and a downlink packet conversion process. A content table stores an IPv6 packet header after the MAP-E or MAP-T process. A control table is referred to for controlling the fields to be updated when adding the IPv6 packet header. A forwarding mapping rule table is referred to for determining to convert a destination IP address of an uplink IPv6 packet, or both a source IP address and a destination IP address of a downlink IPv4 packet.