SDN Communication Device Persistent Configuration Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software-defined networks (SDNs) in electric power transmission and distribution systems face challenges in quickly recovering from disruptions, such as loss of power or communication link failures, due to the reliance on a central controller for network management, leading to substantial downtime in restoring communication functionality.

Innovation Solution

Communication devices in the network are configured to retain persistent configuration information and unique identifiers, allowing them to revert to a default state and reestablish communication flows with neighboring devices, reducing the time needed to recover from disruptions without relying on the SDN controller, and incorporating authentication processes to ensure network security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the network relies on a central SDN controller for management and recovery, then network security and centralized control are improved, but recovery time from disruptions increases substantially

Engineering Contradiction:
Improvenetwork securityVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring communication devices with persistent configuration information, including authentication credentials and network topology data, before disruptions occur. This allows devices to immediately reestablish communication with neighboring devices without waiting for controller authorization, thereby reducing recovery time while maintaining security through pre-validated credentials.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service by enabling communication devices to autonomously recover from disruptions using their own persistent configuration information. Devices can independently authenticate with neighboring devices and restore communication flows without requiring controller intervention, thus eliminating the single point of failure and reducing dependency on centralized control during recovery scenarios.

Inventive Principle:
Principle #25Self-service

2Productivity

If communication devices retain persistent configuration information locally, then recovery speed is improved, but device complexity and security risks increase

Engineering Contradiction:
Improverecovery speedVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies copying by creating simplified replicas of the controller's configuration data in each communication device's persistent memory. Instead of storing complete controller functionality, devices hold essential configuration information (authentication credentials, initial network topology) that enables immediate recovery. This reduces device complexity compared to full controller implementation while maintaining fast recovery capability.

Inventive Principle:
Principle #26Copying

3Loss of time

If devices can autonomously reestablish communication without controller verification, then recovery time is reduced, but network security may be compromised

Engineering Contradiction:
Improverecovery timeVSAvoidnetwork security
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-configuring authentication credentials and security parameters in persistent memory before disruptions occur. This allows devices to perform secure authentication with neighboring devices immediately upon recovery, eliminating the need for time-consuming controller verification while maintaining security through pre-validated credentials.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by establishing mutual authentication mechanisms where devices verify each other's identities and configuration integrity during the reestablishment process. This feedback loop ensures that only authorized devices with valid persistent configuration information can restore communication, preventing unauthorized access while enabling fast recovery.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9900206B2Communication device with persistent configuration and verification
Publication Date: 2018.02.20 SCHWEITZER ENGINEERING LABORATORIES INC
  • US9900206B2 patent drawing
  • US9900206B2 patent drawing
  • US9900206B2 patent drawing

AI summary

The present disclosure pertains to systems and methods for establishing communication with a remote communication device in a software defined network (SDN) during time when an SDN controller is unavailable. In one embodiment, a local communication device may be configured to receive a plurality of data flows from an SDN controller and to store the plurality of data flows in a persistent data memory. The device may generate a unique identifier for the local communication device that is transmitted to a remote communication device. Following a disruption the results in the SDN controller being unavailable, the local communication device may recover into a default configured state based on the plurality of data flows in the persistent data memory. The local communication device may then transmit the unique identifier to the remote communication device after the disruption to begin a process of reestablishing communication with the remote communication device.