SRv6 Flowspec Routing for Extension Header Traffic Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Flowspec technology is limited in identifying and controlling traffic other than Native IP traffic, particularly SRv6 packets, due to its inability to recognize the routing extension header of SRv6 traffic, restricting its application scenarios.

Innovation Solution

A transmission control method and apparatus for SRv6 packets that include a first traffic matching condition and corresponding traffic control actions, enabling the identification and control of SRv6 packets by configuring Flowspec routing to recognize SRv6 traffic through specific matching conditions and actions, such as routing extension header fields and control actions like header popping and redirection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Flowspec technology is used for traffic control, then traffic control capability is improved, but it cannot identify SRv6 packets due to inability to recognize routing extension header

Engineering Contradiction:
Improvetraffic control capabilityVSAvoidtraffic identification capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the traffic identification process by introducing separate matching conditions for different packet types. It divides the Flowspec routing into IPv6 traffic matching conditions and SRv6 traffic matching conditions, where SRv6 conditions specifically examine the routing extension header fields (such as segment list, remaining segments, flags) while IPv6 conditions examine standard IPv6 headers. This segmentation allows the system to reliably identify and control both traditional IPv6 traffic and SRv6 traffic independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to traffic identification by introducing SRv6-specific matching conditions that examine fields in the routing extension header (segment list, remaining segments, flags, next header). This dimensional extension transforms the identification capability from examining only standard IPv6 headers to also examining SRv6-specific header fields, thereby enabling Flowspec to identify and control SRv6 packets without losing compatibility with traditional IPv6 traffic control.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of manufacture

If Flowspec routing only supports Native IP traffic matching conditions, then implementation simplicity is maintained, but application scenarios are greatly limited

Engineering Contradiction:
Improveimplementation simplicityVSAvoidapplication scenarios
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent makes the Flowspec routing structure universal by enabling it to handle multiple traffic types through a unified routing entry. Each Flowspec routing can now contain both IPv6 traffic matching conditions and SRv6 traffic matching conditions, allowing a single routing entry to serve multiple functions: controlling traditional IPv6 traffic and controlling SRv6 traffic with segment routing capabilities. This multi-functionality greatly expands application scenarios while maintaining the familiar Flowspec structure.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies preliminary action by pre-configuring SRv6-specific matching conditions and control actions in the Flowspec routing before actual packet processing. The routing extension header fields (segment list, remaining segments, flags) are examined in advance to determine whether a packet is an SRv6 packet, and appropriate control actions (such as modifying segment list, popping routing extension header, redirecting packets) are predetermined based on these pre-configured conditions. This preliminary configuration enables the system to handle diverse SRv6 application scenarios without complex runtime decision-making.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4723580A1Srv6 message transmission control method, apparatus, device and storage medium
Publication Date: 2026.04.08 ZTE CORP
  • EP4723580A1 patent drawingFigure 1~2
  • EP4723580A1 patent drawingFigure 3~4
  • EP4723580A1 patent drawingFigure 5~6

AI summary

The present application discloses a transmission control method, apparatus and device for a SRv6 packet and a storage medium, belonging to the technical field of communication. The present application obtains a Flowspec routing, the Flowspec routing includes a first traffic matching condition configured for the SRv6 traffic, and a traffic control action corresponding to the first traffic matching condition; matches a currently received packet based on the first traffic matching condition, and obtains a target SRv6 packet; and determines a transmission mode of the target SRv6 packet based on the traffic control action.