NAT64 Translation Header Length Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing NAT64 translation mechanisms do not efficiently manage overheads such as memory read and write operations, leading to slower translation speeds and increased memory requirements for buffer translator functions.

Innovation Solution

The method involves discovering the NAT64-Prefix by an IPv6 host, generating IPv4 connectivity using a customer-side translator (CLAT) device, and configuring the IPv4 header with dummy options to increase its length, thereby reducing the need for memory operations and improving translation efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If standard NAT64 translation is used with default IPv4 header configuration, then translation functionality is provided, but memory read and write operations increase and translation speed decreases

Engineering Contradiction:
Improvetranslation speedVSAvoidmemory operation time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent changes the header length parameter of the IPv4 header from the standard 20 bytes to 40 bytes by adding dummy options. This parameter change allows the translated packet to match the IPv6 header size, eliminating the need for buffer reallocation and memory read/write operations during translation, thereby improving translation speed and reducing memory operation time

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent performs preliminary configuration by setting the IPv4 header length to 40 bytes before translation occurs. The CLAT device pre-configures the IPv4 header with dummy options to match IPv6 header size, so that when translation happens, no additional memory operations are needed. This preliminary action prevents the performance degradation that would occur during actual translation operations

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If standard NAT64 translation is used with default IPv4 header configuration, then translation functionality is provided, but memory requirements for buffer translator function increase

Engineering Contradiction:
Improvememory requirementVSAvoidtranslation efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

By changing the IPv4 header length parameter to 40 bytes (matching IPv6 header size), the patent eliminates the need for buffer allocation and memory operations during translation. This reduces memory requirements for the buffer translator function while simultaneously improving translation efficiency, as the translated packet can be directly sent without additional memory management overhead

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250080490A1Method of NAT64 Translation
Publication Date: 2025.03.06 MEDIATEK SINGAPORE PTE LTD
  • US20250080490A1 patent drawing
  • US20250080490A1 patent drawing
  • US20250080490A1 patent drawing

AI summary

A method of NAT64 translation includes discovering NAT64-Prefix by an IPv6 host, generating IPv4 connectivity by a customer-side translator (CLAT) device according to NAT64-Prefix, notifying the IPv4 connectivity to a private IPv4 (v4p) host, and notifying IPV4 header configuration to the v4p host by the CLAT device. The IPV4 header configuration includes a header length. The method further includes increasing a header length of the IPv4 header by the v4p host.