SRv6 Packet Routing via IPv6 Address Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing SRv6 packet routing technology experiences bandwidth pressure due to the inefficient use of 80 bits of information, which is not utilized effectively in the segment routing network, leading to unnecessary network congestion.

Innovation Solution

A method and routing node that extract and update the destination IP address's node identifier, function identifier, and argument based on a segment list in the SRH, allowing for efficient routing within the segment routing network by optimizing the bit width usage and eliminating the need to carry unnecessary network addresses in the segment list.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If 128-bit IPv6 addresses are used to encode segment identifiers with full node identifier capacity, then the network can support a large number of nodes and virtual nodes, but 80 bits of information are transmitted unnecessarily, causing bandwidth pressure

Engineering Contradiction:
Improvenode identifier capacityVSAvoidbandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the 128-bit IPv6 address into functional components (network identifier, node identifier, function identifier, argument) and only transmits the necessary segments. The segment list in SRH carries compressed segment identifiers that include only essential routing information rather than full 128-bit addresses, reducing bandwidth consumption while maintaining the ability to identify multiple nodes and virtual nodes through the functional components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and transmits only the necessary portions of the IPv6 address (network identifier, node identifier, function identifier, and argument) rather than the complete 128-bit address. By taking out only the essential routing information needed for segment routing operations, the system eliminates 80 bits of redundant data transmission while preserving full node identifier capacity through the functional components.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If full 128-bit IPv6 addresses are carried in segment lists, then complete node identification is maintained, but network congestion increases due to unnecessary data transmission

Engineering Contradiction:
Improvenode identification accuracyVSAvoidnetwork throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the IPv6 address into functional components and transmits only the necessary segments in the segment list. This segmentation maintains node identification accuracy through the network identifier, node identifier, function identifier, and argument components while reducing the amount of data transmitted, thereby improving network throughput and reducing congestion.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter representation from full 128-bit addresses to compressed segment identifiers that include only essential routing information. This parameter change maintains the reliability of node identification through the functional components (network identifier, node identifier, function identifier, argument) while improving network productivity by reducing bandwidth consumption and congestion.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If 16 bits are allocated to Locator for node identification, then 64K node identifiers are supported, but 48 bits are sufficient for full SRv6 application, leaving 80 bits unused and wasting bandwidth

Engineering Contradiction:
Improvenumber of supported nodesVSAvoidbandwidth waste
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary 48 bits of information (network identifier, node identifier, function identifier, and argument) from the full 128-bit IPv6 address for transmission in the segment list. This extraction maintains support for 64K node identifiers through the functional components while eliminating 80 bits of unused data, preventing bandwidth waste while preserving full adaptability for SRv6 applications.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the transmission parameter from full 128-bit addresses to compressed 48-bit segment identifiers that include only essential routing information. This parameter change maintains the ability to support 64K node identifiers through the network identifier, node identifier, function identifier, and argument components while reducing bandwidth waste by eliminating 80 bits of unnecessary data transmission.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11206215B2Method and apparatus for routing packet in segment routing network based on IPv6
Publication Date: 2021.12.21 UTSTARCOM TELECOM CO LTD
  • US11206215B2 patent drawing
  • US11206215B2 patent drawing
  • US11206215B2 patent drawing

AI summary

A method for routing a packet in a segment routing network includes extracting a destination Internet Protocol (IP) address from an IP header of the packet received by a routing node wherein the destination IP address includes a network identifier, a node identifier, a function identifier, and an argument; determining whether the network identifier and the node identifier match a routing node identifier; when the network identifier and the node identifier match the routing node identifier, determining a function to be executed based on the function identifier and the argument; when the function to be executed is determined, updating the node identifier, the function identifier, and the argument according to a segment list included in a segment routing header of the packet; and routing the packet according to the updated node identifier, the updated function identifier, and the updated argument in the destination IP address.