Boundary Packet Header Switching for Cross-Domain Network Slices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current packet forwarding methods in network slicing technologies cannot implement cross-domain interworking between network slices, leading to complex configurations and reduced forwarding efficiency due to service reidentification when packets cross domains.
Innovation Solution
A packet forwarding method that switches slice identifiers between different network domains by using specific packet headers (e.g., ETH, VXLAN, GENEVE, IPv6 extension, HBH, DOH) to enable cross-domain interworking, avoiding complex configurations and improving forwarding efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a slice identifier is carried in a packet to direct the packet to a network slice for forwarding, then packet forwarding can be directed to the correct network slice, but cross-domain interworking between network slices cannot be implemented
Solution Approach 1:
The patent segments the network into multiple domains (first network domain and second network domain) with different packet header formats. Each domain uses its own slice identifier format (first slice identifier in first packet header, second slice identifier in second packet header), allowing cross-domain interworking while maintaining domain-specific forwarding accuracy through localized segmentation rules
Solution Approach 2:
The boundary network node acts as an intermediary between different network domains. It performs packet header conversion, translating slice identifiers from the first packet header format to the second packet header format, enabling cross-domain communication while preserving forwarding accuracy through the mediation of standardized conversion rules
2Adaptability or versatility
If service reidentification is performed when a packet crosses domains, then packet routing can be adjusted for different domains, but complex configuration and forwarding efficiency deterioration occur
Solution Approach 1:
The boundary network node performs preliminary packet header conversion before packets enter different network domains. By pre-converting packet headers to the appropriate domain format and embedding domain-specific routing information in advance, the system enables domain-specific handling without requiring complex reidentification operations during packet forwarding, thus maintaining high forwarding efficiency
Solution Approach 2:
The patent changes packet header parameters (slice identifier format, header structure) based on the target domain. The boundary node dynamically adjusts packet header parameters according to the destination domain requirements, enabling adaptive domain-specific handling while avoiding complex reidentification through systematic parameter transformation rules
Data Source
AI summary
A packet forwarding method and apparatus. A first network node located at a boundary between a first network domain and a second network domain receives a first packet from the first network domain, where the first packet includes a first packet header that matches the first network domain, and the first packet header includes a first slice identifier that indicates a first network slice. The first network node obtains a second packet based on the second network domain and the first packet, where the second packet includes a second packet header that matches the second network domain, the second packet header includes a second slice identifier that indicates a second network slice, and the second packet header is different from the first packet header. The first network node sends the second packet in the second network domain based on the second slice identifier.