Compressed Segment Identifiers for SRv6 Header Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The deployment of Segment Routing over IPv6 (SRv6) is limited due to the long segment routing header caused by the long SID list, which reduces payload efficiency and exceeds packet processing capabilities.

Innovation Solution

A routing method that generates and uses compressed segment identifiers to construct a shorter segment routing header, improving payload efficiency by reducing the number of bits in the segment identifier list, and includes a new function type for block swapping flavored segment identifiers to facilitate locator block updates across SRv6 domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a long SID list is used in SRv6 to achieve shortest path forwarding segment by segment, then routing flexibility and service chain capability are improved, but the segment routing header becomes long, reducing payload efficiency and exceeding packet processing capability

Engineering Contradiction:
Improverouting flexibilityVSAvoidsegment routing header length
Core Design Contradiction:
Adaptability or versatilityVSLength of moving object

Solution Approach 1:

The patent changes the parameter of segment identifier from full 128-bit IPv6 addresses to compressed 32-bit identifiers. This parameter transformation maintains the routing flexibility and service chain capability while significantly reducing the segment routing header length, thereby improving payload efficiency and enabling better packet processing performance.

Inventive Principle:
Principle #35Parameter changes

2Length of moving object

If compressed segment identifiers are used to reduce header length, then payload efficiency is improved, but the complexity of segment identifier compression and decompression increases

Engineering Contradiction:
Improvesegment routing header lengthVSAvoidsegment identifier processing complexity
Core Design Contradiction:
Length of moving objectVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing a compression mapping relationship between full IPv6 addresses and compressed 32-bit identifiers in the control plane. This pre-computed mapping is stored in routing tables, allowing intermediate nodes to simply perform table lookups during packet forwarding without performing complex real-time compression or decompression operations, thus reducing operational complexity.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If segment routing is deployed in practical networks, then network control flexibility is improved, but the long SID list causes packet processing capability to be exceeded

Engineering Contradiction:
Improvenetwork control flexibilityVSAvoidpacket processing capability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent changes the segment identifier parameter from 128-bit to 32-bit compressed form, which directly reduces the segment routing header length. This parameter change maintains network control flexibility while reducing the processing burden on intermediate nodes, thereby improving packet processing capability and enabling practical network deployment.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20230140531A1Routing method, routing apparatus and computer-readable storage medium
Publication Date: 2023.05.04 ZTE CORP
  • US20230140531A1 patent drawing
  • US20230140531A1 patent drawing
  • US20230140531A1 patent drawing

AI summary

A routing method, a routing apparatus and a non-transitory computer-readable storage medium are disclosed. The routing method may include, establishing a forwarding path to a destination node; generating, for each segment in the forwarding path, a compressed segment identifier according to a segment identifier corresponding to a respective one segment in the forwarding path, and establishing a compressed segment identifier list according to each compressed segment identifier; constructing an IPv6 message based on the compressed segment identifier list; and forwarding the IPv6 message.