Cloud Packet Forwarding with Private VXLAN Extension Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing VXLAN protocol in cloud networks has insufficient reserved fields, limiting the amount of business information that can be carried in packets, which is a challenge in complex network scenarios.

Innovation Solution

Replace the Ethernet protocol header of packets with a preset private extension protocol header, setting each field in the private extension protocol header according to business requirements, and encapsulating the packet through a VXLAN protocol to generate a second packet that can carry more business information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If VXLAN protocol encapsulation is used for cloud network traffic, then packet forwarding capability is provided, but the reserved fields are insufficient to carry adequate business information

Engineering Contradiction:
Improveamount of business information carriedVSAvoidflexibility of protocol header fields
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The Ethernet protocol header is segmented and replaced with a private extension protocol header that is divided into multiple functional fields (source identifier field, destination identifier field, business information field, etc.). This segmentation allows each field to serve a specific purpose while collectively carrying comprehensive business information that exceeds the capacity of standard VXLAN reserved fields.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The solution introduces a new dimension by creating a private extension protocol header structure that operates alongside the standard VXLAN protocol. This additional dimensional layer provides extended field capabilities without disrupting the existing VXLAN encapsulation framework, enabling richer information carrying capacity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If a private extension protocol header is introduced to carry more business information, then information carrying capacity is improved, but protocol complexity increases

Engineering Contradiction:
Improvebusiness information carrying capacityVSAvoidprotocol processing complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The private extension protocol header is designed with multi-functionality, where a single header structure handles multiple tasks: identification of source and destination, classification of business information types, and carrying of specific business parameters. This universal design reduces the need for multiple specialized headers, thereby managing complexity while maintaining high information carrying capacity.

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

Solution Approach 2:

The solution employs parameter changes by making the private extension protocol header configurable based on different business requirements. Fields within the header can be dynamically adjusted or selected depending on the specific cloud network service being provided, allowing the protocol to adapt its complexity to match the actual information carrying needs rather than always operating at maximum complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260005964A1Packet forwarding method and device based on cloud network
Publication Date: 2026.01.01 BEIJING VOLCANO ENGINE TECH CO LTD
  • US20260005964A1 patent drawing
  • US20260005964A1 patent drawing
  • US20260005964A1 patent drawing

AI summary

Embodiments of the present disclosure provide a packet forwarding method and device based on a cloud network, the method including: receiving a first packet sent by a source virtual machine to a destination virtual machine, parsing the first packet, replacing an Ethernet protocol header of the first packet with a preset private extension protocol header, setting each field in the private extension protocol header according to a business requirement, and performing encapsulation through a VXLAN protocol to generate a second packet; and forwarding the target traffic based on the second packet.