Abstract Segment ID Mapping for Stable SRv6 Traffic Steering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional End-to-End communication systems using Segment Routing IPv6 require frequent updates to edge routers due to changes in service function instance identifiers, such as address changes or additions, leading to instability in traffic steering.
Innovation Solution
A communication system that employs abstracted Segment IDs (SIDs) to maintain consistent path settings in edge routers, allowing changes in service function instance identifiers without requiring updates, by using a hub to convert abstracted SIDs into actual instance identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If service function instance identifiers are changed due to failures, upgrades, or demand changes, then the service can adapt to new conditions, but the edge router path settings must be updated frequently causing instability
Solution Approach 1:
The patent introduces an intermediary mapping mechanism between abstract SIDs and concrete service function instance identifiers. The edge router uses abstract SIDs that do not change, while a mapping table (maintained by controller or router) translates these stable abstract identifiers to the actual dynamic instance identifiers. This intermediary layer decouples the stability requirement of routing from the volatility of instance identifiers.
Solution Approach 2:
The patent segments the identifier system into two parts: stable abstract SIDs used for routing decisions in the edge router, and dynamic concrete instance identifiers used for actual service function identification. This segmentation allows each part to serve its specific purpose independently - abstract SIDs provide stability for routing while concrete identifiers can change freely to adapt to service dynamics.
2Manufacturing precision
If the carrier provider updates path settings in the edge router every time SF instance information changes, then the routing remains accurate, but the complexity and frequency of updates increase
Solution Approach 1:
The patent creates a copy or abstraction of the service function identifiers in the form of abstract SIDs. These abstract SIDs are copies that represent the service functions but are decoupled from the actual dynamic identifiers. The edge router uses these abstract copies for routing, eliminating the need to track and update every change in the original identifiers.
Solution Approach 2:
The patent performs preliminary action by pre-establishing the mapping relationship between abstract SIDs and concrete instance identifiers before routing decisions are made. The mapping table is prepared in advance, allowing the edge router to use stable abstract identifiers without needing to react to every change in service function instances.
3Reliability
If abstracted SIDs are used in edge routers to maintain stable path settings, then traffic steering stability improves, but a conversion mechanism is needed to map abstract SIDs to actual instance identifiers
Solution Approach 1:
The patent introduces an intermediary mapping mechanism between abstract SIDs and concrete service function instance identifiers. The edge router uses abstract SIDs that do not change, while a mapping table (maintained by controller or router) translates these stable abstract identifiers to the actual dynamic instance identifiers. This intermediary layer decouples the stability requirement of routing from the volatility of instance identifiers.
Data Source
AI summary
A communication system realizes End-to-End communication between communication devices via at least one service function by using Segment Routing IPv6. The communication system executes: transferring a packet received from one of the communication devices at a communication origin of the End-to-End communication, by using an abstracted ID obtained by abstracting a segment ID in a prescribed range determined in advance; and converting, upon receipt of the packet including the abstracted ID, the abstracted ID into an address or a segment ID of a service function instance providing the service function.


