Hybrid Segment List Packet Forwarding Across IPv6, MPLS, and IPv4
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid networks where Segment Routing (SR) needs to traverse different types of networks, such as those supporting IPv6, MPLS, or IPv4, the existing methods fail to obtain a global optimal path and require complex configuration at splicing nodes due to the inability to program the entire forwarding path with a single segment list.
Innovation Solution
A packet forwarding method that uses a hybrid segment list containing multiple types of identifiers, including SRv6 and non-SRv6 identifiers, to program the path across different network types, allowing for encapsulation of these identifiers in the packet to facilitate global optimal path planning and simplify network configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If segment-based path computation and segment-by-segment splicing is used to forward packets through hybrid networks, then packets can traverse different network types (SRv6, MPLS, IPv4), but a global optimal path cannot be obtained and configuration at splicing nodes becomes complex
Solution Approach 1:
The patent segments the hybrid network path into multiple network types (SRv6 network, MPLS network, IPv4 network), with each segment identified by specific identifier types. The segment list is divided into first-type identifiers for SRv6 networks and second-type identifiers for non-SRv6 networks, allowing independent optimization of each segment while maintaining global path programmability.
Solution Approach 2:
The patent creates a universal segment list structure that can accommodate multiple identifier types (first-type and second-type identifiers) within a single data structure. This unified approach allows the same segment list mechanism to program paths across diverse network types, eliminating the need for separate path computation methods for each network type and simplifying splicing node configuration.
2Adaptability or versatility
If segment-based path computation is used for hybrid networks, then packets can be forwarded through network devices that do not support SRv6, but the path planning cannot be globally optimized
Solution Approach 1:
The patent performs preliminary path planning by pre-computing the complete hybrid path and encoding it in advance in the segment list with proper identifier types. The ingress device prepares the entire path program before packet injection, including all first-type and second-type identifiers in the correct sequence, enabling global optimal path selection before packet transmission begins.
Solution Approach 2:
The patent introduces the segment list as an intermediary data structure that bridges SRv6 and non-SRv6 networks. By encoding both first-type identifiers (for SRv6 devices) and second-type identifiers (for MPLS/IPv4 devices) within the same segment list, the system enables coordinated path computation across heterogeneous networks, allowing global optimization while maintaining compatibility with non-SRv6 devices.
Data Source
AI summary
A segment routing device receives a first packet from a first network. A first packet header of the first packet includes a segment list. The segment list includes a plurality of sequentially arranged identifiers. The identifiers include a first-type identifier and a plurality of second-type identifiers. Network devices or links identified by the first-type identifier and the second-type identifier are respectively on the first network and a second network. A type of the first network is different from a type of the second network. The segment routing device encapsulates a second packet header for the first packet to form a second packet. The second packet header includes the plurality of second-type identifiers. The segment routing device sends the second packet to the second network.