SRv6 Packet Forwarding Across Network Slices With Shared SID Lists
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing segment routing over IPv6 (SRv6) technologies face challenges in efficiently managing packet forwarding across network slices, leading to limitations in resource consumption and usability when different services require different network slices.
Innovation Solution
Decouple slice information from segment routing policies by using a common forwarding path for packets from different network slices, allowing the same segment routing policy to be applied across multiple services, and implement packet forwarding through slice sub-interfaces based on stored mapping relationships between SIDs and interface identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If slice information is tightly coupled with segment routing policies for each service, then service-specific forwarding requirements can be met, but resource consumption increases and usability decreases
Solution Approach 1:
The patent applies universality by enabling a single segment routing policy to serve multiple services across different network slices. The head node identifies that packets from different slices matching the same policy can share a common forwarding path, allowing the policy to function universally for multiple services rather than requiring separate policies for each service-slice combination.
Solution Approach 2:
The patent merges the handling of packets from different network slices by combining them into a single forwarding process when they match the same segment routing policy. Instead of maintaining separate forwarding states for each slice, the system merges their processing into a unified path determination and forwarding mechanism.
2Adaptability or versatility
If separate segment routing policies are created for each network slice and service combination, then specific service requirements can be satisfied, but device complexity and resource consumption increase
Solution Approach 1:
The segment routing policy is designed to be universal and service-agnostic, capable of handling packets from any network slice that matches its forwarding requirements. The policy does not need to be customized for each service or slice combination, reducing the number of policies needed while maintaining adaptability to different service requirements through the slice information carried in packets.
Solution Approach 2:
The patent extracts slice information from the packet metadata and uses it independently for forwarding decisions without requiring separate policies for each slice. The slice information is taken out as a separate identifier that can be processed alongside the segment routing policy matching, rather than being embedded in policy definitions.
3Reliability
If network slices are strictly separated for different services, then service isolation is maintained, but forwarding path flexibility and resource utilization decrease
Solution Approach 1:
The patent merges forwarding paths for packets from different network slices when they match the same segment routing policy, allowing shared utilization of network resources while maintaining service isolation through packet-level processing. The merging occurs at the forwarding plane where packets are combined into common paths without compromising the logical separation of services.
Solution Approach 2:
The system dynamically determines whether packets from different slices can share forwarding paths based on real-time policy matching and service requirements. The forwarding behavior is dynamic and adaptive, allowing slices to be strictly separated when needed and combined for resource efficiency when service requirements permit.
Data Source
AI summary
A packet forwarding method implemented by a head node, includes receiving a first packet and a second packet, where the first packet is a packet forwarded by using a first network slice, and the second packet is a packet forwarded by using a second network slice; in response to the first packet matching a first segment routing policy, generating a third packet based on the first packet, where the third packet carries slice information of the first network slice and a first SID list; in response to the second packet matching the first segment routing policy, generating a fourth packet based on the second packet, where the fourth packet carries slice information of the second network slice and the first SID list; and forwarding the third packet and the fourth packet.