SRv6 Gateway Node Policy Data Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In current slicing packet networks (SPN) end-to-end SRv6 scenarios, SRv6 gateway nodes receive and store SRv6 Policy configuration data intended for other nodes, leading to reduced processing performance due to irrelevant data storage.

Innovation Solution

An SRv6 gateway node determines whether received SRv6 Policy configuration data is relevant to its local configuration data before storing it, and performs traffic steering processing only on associated data, ignoring irrelevant data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If SRv6 gateway node stores all received SRv6 Policy configuration data, then complete policy data is available, but processing performance deteriorates due to storing irrelevant data

Engineering Contradiction:
Improvecompleteness of policy dataVSAvoidprocessing performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts and stores only the relevant portion of SRv6 Policy configuration data that is intended for the local gateway node, rather than storing all received configuration data. This is achieved by filtering configuration data based on destination node identification, thereby removing irrelevant data that would otherwise consume storage resources and degrade processing performance.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by making the storage behavior specific to each gateway node's local context. Each node stores only configuration data relevant to itself, rather than uniformly storing all received data. This localized approach optimizes each node's resource utilization while maintaining the reliability needed for its specific routing functions.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If SRv6 gateway node stores irrelevant configuration data, then all possible policies are available, but resource utilization deteriorates

Engineering Contradiction:
Improveavailability of policy optionsVSAvoidresource utilization
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary configuration data relevant to the local gateway node from the complete set of received policies. By identifying and retaining only the subset of data intended for this specific node, the system maintains adaptability for local routing decisions while eliminating waste of memory and processing resources on irrelevant configurations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent discards irrelevant configuration data that is not intended for the local gateway node. This selective discarding prevents resource exhaustion from storing unnecessary data, while the system recovers efficiency by processing only the relevant configuration set, thereby improving resource utilization without sacrificing necessary policy availability.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentEP4672701A1SRV6 policy configuration data processing method and apparatus, device and medium
Publication Date: 2025.12.31 ZTE CORP
  • EP4672701A1 patent drawingFigure 1~2
  • EP4672701A1 patent drawingFigure 3~4
  • EP4672701A1 patent drawing

AI summary

The present application provides an SRv6 Policy configuration data processing method and apparatus, an electronic device and a medium. In a solution, an SRv6 gateway node receives target SRv6 Policy configuration data; first determines whether the target SRv6 Policy configuration data is associated with locally stored existing SRv6 Policy configuration data; and if so, stores the target SRv6 Policy configuration data and performs diversion processing on a SRv6 service message according to the target SRv6 Policy configuration data, or if not, directly ignores the target SRv6 Policy configuration data.