SRv6 Slice Locator Aggregation for Scalable Network Slicing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing SRv6-based network slicing solutions, the need to publish a large quantity of locators for each slice becomes complex when dealing with a large number of slices, complicating operations.
Innovation Solution
A network device generates a slice locator with a target argument indicating association with multiple slices, allowing it to publish only one slice locator, which other devices can use to generate the necessary locators based on the target argument, simplifying the operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a network device publishes a locator for each slice in SRv6 network slicing, then slice traffic forwarding can be ensured and slice resources can be isolated, but the operation becomes complex when the quantity of slices is large
Solution Approach 1:
The patent combines multiple slice locators into a single unified locator structure that includes a target argument field. This target argument field can indicate multiple slices, allowing one locator to represent multiple slices instead of requiring separate locators for each slice. This merging approach maintains the ability to forward traffic for multiple slices while significantly reducing the number of locators that need to be published and managed.
Solution Approach 2:
The patent creates a universal locator structure that can serve multiple functions. The locator includes a target argument field that can indicate different slices, allowing the same locator to be used for traffic forwarding in multiple slices. This multi-functional design eliminates the need for separate dedicated locators for each slice, thereby simplifying the operation while maintaining slice isolation and forwarding reliability.
2Reliability
If a network device publishes multiple slice locators to support network slicing, then slice isolation and traffic forwarding are achieved, but the scalability becomes poor when supporting a large quantity of slices
Solution Approach 1:
The patent merges multiple slice locators into a single locator structure with a target argument field that can indicate multiple slices. This reduces the number of locators that need to be published and managed, thereby improving scalability. The unified structure maintains slice isolation by using the target argument to distinguish between different slices, allowing the system to support a large quantity of slices without proportionally increasing the number of locators.
Solution Approach 2:
The patent changes the structure of the locator by adding a target argument field that can indicate multiple slices. This parameter change allows the locator to evolve from a single-slice identifier to a multi-slice indicator. By changing the locator structure to include this flexible target argument, the system can scale to support many slices without requiring a proportional increase in locator publications, thereby improving scalability while maintaining slice isolation.
Data Source
Figure 1~3
Figure 4~5
Figure 6
AI summary
Embodiments of this application disclose an SRv6-based data processing method. A network device may publish only one slice locator including slice information of the network device, and does not need to publish a corresponding slice locator for each slice supported by the network device. This simplifies an operation. The method according to an embodiment of this application includes: A first network device generates a slice locator, where the slice locator includes an target argument, the slice locator is used to identify an addressable destination address prefix in a slice supported by the first network device, and the target argument is used to indicate that the slice locator is associated with at least two slices supported by the first network device; and the first network device sends the slice locator to a second network device, so that the second network device generates, based on the slice locator, at least two target slice locators corresponding to the at least two slices.