SDN Load-Sharing Path Reroute Protection via Pre-Configured Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional SDN networks based on the OpenFlow protocol do not support fast rerouting when any one of the multiple load-sharing paths fails, leading to packet loss and inefficiencies in network processing.

Innovation Solution

A routing method that determines at least three paths for a data flow, generates a first group entry and a flow entry to instruct the forwarding device to set the first and second paths as load-sharing paths and the third path as a reroute protection path, and updates these entries based on path failure notifications to ensure seamless rerouting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple load-sharing paths are configured in conventional SDN networks, then network bandwidth utilization is improved, but the system cannot perform fast rerouting when a path fails, leading to packet loss

Engineering Contradiction:
Improvenetwork bandwidth utilizationVSAvoidrerouting capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent pre-configures a backup path alongside the primary load-sharing paths before any failure occurs. The control device generates a flow entry that includes a backup path identifier and establishes the backup path in advance, so that when a failure is detected, the forwarding device can immediately switch to the pre-prepared backup path without calculation or reconfiguration delays, thus resolving the contradiction between utilizing multiple paths for bandwidth and maintaining rerouting capability for reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a control device as an intermediary that manages the backup path configuration and provides backup path information to forwarding devices. This intermediary maintains the backup path state and coordinates the failure response, enabling the forwarding device to quickly switch paths without complex local decision-making, thereby achieving both efficient bandwidth utilization and reliable fast rerouting

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If conventional SDN networks use multiple load-sharing paths, then network capacity is increased, but processing efficiency deteriorates when path failure occurs due to lack of fast rerouting support

Engineering Contradiction:
Improvenetwork capacityVSAvoidprocessing efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The control device pre-establishes backup paths and configures flow entries with backup path identifiers before failures occur. This preliminary action ensures that when a path fails, the forwarding device can immediately activate the pre-configured backup path without undergoing path calculation or reconfiguration processes, thereby maintaining high processing efficiency while supporting multiple load-sharing paths for increased network capacity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The forwarding device is equipped with the capability to autonomously detect path failures and switch to the pre-configured backup path using the backup path identifier provided in the flow entry. This self-service mechanism eliminates the need for centralized control intervention during failure events, enabling fast rerouting that maintains processing efficiency while utilizing multiple paths for enhanced network capacity

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11509584B2Routing method, related device, and system
Publication Date: 2022.11.22 HUAWEI TECH CO LTD
  • US11509584B2 patent drawing
  • US11509584B2 patent drawing
  • US11509584B2 patent drawing

AI summary

The present disclosure related to routing methods. One example method includes configuring a first path and a second path in charge of load sharing for a data flow, and configuring a third path in charge of reroute protection. A first group entry is generated for instructing the forwarding device to use the first path and the second path as load-sharing paths and use the third path to perform reroute protection on the first path and the second path. A flow entry for instructing to perform an operation of going to the first group entry is generated.