L3 Network Node Hitless Maintenance via Traffic Rerouting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large computer networks, especially enterprise computing systems, maintenance operations such as upgrading or replacing hardware/software can disrupt user services if not managed transparently, impacting network performance and user experience.

Innovation Solution

A method for exiting and reintroducing a node from an Internet Protocol, Layer 3 network involves preparing the network by rerouting traffic, notifying peer nodes, and using maintenance managers to ensure seamless transitions during maintenance, allowing for transparent maintenance without service disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If maintenance operations are performed on network nodes, then hardware/software can be upgraded or replaced, but network services are disrupted and user experience deteriorates

Engineering Contradiction:
Improvemaintenance capabilityVSAvoidservice availability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent applies preliminary action by establishing a backup node before maintenance operations begin. The backup node is pre-configured with necessary hardware and software, and traffic routing is pre-arranged to bypass the node undergoing maintenance. This allows maintenance to be performed without service disruption, as the backup node is already in place to immediately assume traffic flow when the primary node is taken offline.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traffic is rerouted around a node for maintenance, then service continuity is maintained, but network complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidnetwork configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the network into distinct segments: primary nodes, backup nodes, and maintenance nodes. Each node type has a specific function and configuration. Backup nodes are segmented as separate entities with dedicated standby capacity, allowing traffic rerouting to be managed through clear segment boundaries rather than complex reconfiguration of the entire network. This modular segmentation simplifies the overall network management during maintenance operations.

Inventive Principle:
Principle #1Segmentation

3Reliability

If backup nodes are maintained in standby configuration, then failover capability is improved, but resource utilization decreases

Engineering Contradiction:
Improvefailover capabilityVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies dynamics by implementing dynamic resource allocation where backup nodes can transition between standby and active states based on network conditions. When no maintenance is required, backup nodes remain in low-power standby mode with minimal resource consumption. When maintenance is needed on primary nodes, the system dynamically activates the backup node and redistributes traffic load. This dynamic state transition allows the network to maintain failover capability while optimizing resource utilization during normal operation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10931568B2Hitless maintenance of a L3 network
Publication Date: 2021.02.23 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10931568B2 patent drawing
  • US10931568B2 patent drawing
  • US10931568B2 patent drawing

AI summary

A method for use in exiting a portion of a node from an Internet Protocol, Layer 3 network includes: preparing the network for the portion to exit prior to the exit, including: notifying a set of peer nodes of the portion's exit; and rerouting traffic in the network away from the portion to the set of peer nodes; exiting the portion from the network once the traffic is rerouted; and reintroducing the exited portion to the network, including: notifying the peer nodes of the portion's reintroduction; and rerouting at least some of the traffic through the re-introduced portion.