IGP Flex Algorithm Network Slice QoS Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Interior Gateway Protocol (IGP) Flex Algorithm (FA) technology cannot support differentiated Quality of Service (QoS) policies among different network slices sharing the same link in 5G network slices, leading to inadequate traffic isolation and QoS management.

Innovation Solution

Allocate a segment identifier corresponding to each network slice's algorithm type, flood these identifiers through the IGP, and configure a QoS policy for each network slice based on its algorithm type, enabling packet forwarding based on segment identifiers and QoS policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple network slices share the same link using conventional IGP FA technology, then network resource utilization is improved, but differentiated QoS policy implementation deteriorates

Engineering Contradiction:

Improvenetwork resource utilizationVSAvoiddifferentiated QoS policy implementation

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the QoS policy configuration by introducing algorithm-type-specific QoS policies for each network slice. Instead of using a single conventional QoS policy for all slices, the system divides QoS management into separate policy sets corresponding to different algorithm types (e.g., SR-MPLS, SRv6), enabling differentiated service quality control while allowing multiple slices to share physical links.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by configuring algorithm-type-specific QoS policies at each network element (router/switch) along the path. Each network element locally applies the appropriate QoS policy based on the packet's algorithm type, ensuring that different network slices receive differentiated service quality treatment even when sharing the same physical infrastructure.

Inventive Principle:

Principle #3Local quality

2Device complexity

If traffic classification is performed based on link-level conventions, then implementation simplicity is maintained, but traffic isolation between network slices deteriorates

Engineering Contradiction:

Improveimplementation simplicityVSAvoidtraffic isolation between network slices

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent introduces algorithm type as an intermediary identifier that mediates between the physical link and the network slice. By tagging packets with their algorithm type and using this intermediary to select the appropriate QoS policy, the system achieves reliable traffic isolation without requiring complex link-level reconfiguration for each slice.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the classification parameter from link-level to packet-level by incorporating algorithm type information into the packet forwarding decision. This parameter change enables traffic isolation based on the packet's algorithm type rather than the physical link, maintaining implementation simplicity while improving isolation reliability.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12244474B2Routing method, routing device and computer-readable storage medium

Publication Date: 2025.03.04 ZTE CORP

AI summary

A routing method, a routing device and a computer-readable storage medium are disclosed. The routing method includes: allocating, to each of network slices corresponding to different algorithm types, a segment identifier corresponding to a respective algorithm type, and flooding the segment identifier through an IGP; configuring, for each network slice, a QoS policy corresponding to a respective algorithm type; and, forwarding a packet based on the segment identifier and the QoS policy.