IPv6 Header Encoding for Explicit Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network routing technologies face challenges in efficiently encoding service and path information without increasing packet size, which can lead to security concerns and require hardware upgrades, especially in IPv6 and SRv6 environments.
Innovation Solution
The method encodes service and path information in unused bits of an unaltered IPv6 header using IP-in-IP encapsulation, allowing only service-aware nodes to maintain this information, and uses a distributed or centralized control plane to manage state, thereby avoiding hardware changes and maintaining packet integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If segment routing or service function chaining is implemented using extension headers or encapsulation headers, then routing control and service function capability are improved, but packet size increases which may exceed packet size limits
Solution Approach 1:
The patent embeds routing control information and service function identifiers within the existing IPv6 header structure by utilizing the Flow Label field and extending the Destination Address field. This nesting approach allows segment routing and service function chaining capabilities to be integrated without adding external headers, thereby avoiding packet size expansion while maintaining enhanced routing control and service function deployment capabilities.
2Adaptability or versatility
If extension headers or encapsulation headers are added to enable segment routing or service function chaining, then routing flexibility is improved, but security concerns arise regarding packet integrity and privacy
Solution Approach 1:
The patent designs the IPv6 header extension to serve multiple functions: the Flow Label field provides both flow identification and routing control, while the extended Destination Address field simultaneously specifies both the target node and service function identifiers. This multi-functional design eliminates the need for separate extension headers that could be manipulated, thereby maintaining packet integrity and privacy while achieving routing flexibility through a unified, standardized header structure.
3Adaptability or versatility
If new extension headers or encapsulation headers are introduced for segment routing or service function chaining, then network functionality is improved, but hardware upgrades are required which increases deployment complexity
Solution Approach 1:
The patent achieves enhanced network functionality by changing the parameter usage of existing IPv6 header fields rather than adding new hardware-supported fields. Specifically, the Flow Label field is repurposed to carry routing control information, and the Destination Address field is extended to include service function identifiers. This parameter-based approach allows segment routing and service function chaining to be implemented through software updates alone, eliminating the need for expensive hardware upgrades and reducing deployment complexity.
4Measurement precision
If all network nodes maintain path information and service functions for proper packet processing, then routing accuracy is improved, but device complexity and memory requirements increase
Solution Approach 1:
The patent implements local quality by enabling only service-aware nodes to maintain and process the extended routing information, while other nodes operate with standard IPv6 forwarding. The Flow Label and extended Destination Address fields are processed locally at service-aware nodes to determine service function execution, without requiring global knowledge of the entire service function chain at all nodes. This selective processing approach maintains routing accuracy for packets requiring service functions while significantly reducing the complexity and memory requirements at individual nodes.
Data Source
AI summary
A method of routing a data packet through a network comprises updating at least one router local forwarding table to include path IDs of network segments defining paths between network nodes and network function bit encoding/decoding information. In response to a data packet arriving at an ingress network node, an encapsulation header including a path ID identifying at least one network segment of an explicit routing path and a bit encoding specifying network functions to be performed on the data packet are encapsulated in unused portions of the source address and/or the destination address in the encapsulation header. A network node in the explicit routing path performs a network function encoded in the source address and/or the destination address of the encapsulation header of the data packet and forwards the data packet based on network function bit encoding/decoding and path ID information in the network node's local updated local forwarding table.