Distributed SDN Control Plane for Real-Time Topology Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed Software Defined Networking (SDN) controllers face challenges in large-scale networks due to the lack of a standardized communication standard for the East/West interface, leading to performance bottlenecks and difficulties in maintaining a holistic view of the network topology.

Innovation Solution

A Distributed SDN Control Plane Framework (DSF) utilizing a data-centric Real-Time Publish/Subscribe (RTPS) model, which enables standardized communication among heterogeneous SDN controllers through a publish/subscribe protocol, allowing for real-time synchronization of network updates and topology management across multiple domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If distributed SDN controllers are deployed to overcome performance bottlenecks, then scalability and reliability are improved, but the lack of standardized East/West interface communication protocols leads to coordination complexity and synchronization difficulties

Engineering Contradiction:
Improvenetwork scalabilityVSAvoidcontroller coordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies homogeneity by standardizing the East/West interface communication protocol across all distributed SDN controllers. The controller information interaction protocol defines uniform message formats, interaction rules, and synchronization mechanisms that ensure all controllers follow the same communication standards, reducing coordination complexity while maintaining scalability.

Inventive Principle:
Principle #33Homogeneity

Solution Approach 2:

The patent implements universality through a protocol that handles multiple functions within a unified framework. The standardized East/West interface protocol simultaneously manages topology synchronization, state information exchange, configuration distribution, and event notification across heterogeneous controllers, eliminating the need for multiple specialized communication channels.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If distributed SDN controllers are used to maintain a holistic network view, then network visibility is improved, but synchronization of network topology information becomes more challenging without standardized protocols

Engineering Contradiction:
Improvenetwork topology visibilityVSAvoidtopology synchronization reliability
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent applies feedback mechanisms through the standardized East/West interface protocol, which includes explicit acknowledgment messages and confirmation protocols. When controllers exchange topology information and configuration data, the receiving controller sends confirmation messages back to verify successful reception and synchronization, ensuring reliable information propagation across the distributed system.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent implements preliminary action by establishing synchronization protocols and predefined interaction rules before topology changes occur. The standardized protocol includes pre-configured message templates, timing parameters, and coordination mechanisms that prepare controllers for upcoming topology updates, ensuring seamless synchronization when network changes happen.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If heterogeneous SDN controllers are deployed to increase system robustness, then fault tolerance is improved, but cross-platform coordination becomes difficult due to protocol incompatibility

Engineering Contradiction:
Improvesystem fault toleranceVSAvoidcross-platform compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements universality through a platform-agnostic East/West interface protocol that works across heterogeneous SDN controllers. The standardized message formats, interaction rules, and data structures are designed to be implementation-independent, allowing controllers from different vendors and platforms to coordinate effectively while maintaining their individual robustness characteristics.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The standardized protocol acts as an intermediary layer between heterogeneous controllers, translating and normalizing communication regardless of the underlying platform. This mediator protocol enables cross-platform coordination by providing a common language and set of rules that all controllers must follow, eliminating direct platform-specific dependencies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12107727B2Method for processing software defined network (SDN) updates
Publication Date: 2024.10.01 KING FAHD UNIVERSITY OF PETROLEUM AND MINERALS
  • US12107727B2 patent drawing
  • US12107727B2 patent drawing
  • US12107727B2 patent drawing

AI summary

A system includes a network of multiple network domains, each network domain includes a software defined network (SDN) controller. Each SDN controller includes a network interface circuitry, a processor and a memory. The network interface circuitry provides a communicative coupling with at least one domain of the multiple network domains. The memory includes instructions that when executed by the processor, performs a network update comprising adding links, subtracting links or reporting a status of links in at least one network domain upon receiving a network update request, and performs sending and receiving the network update request to a second SDN controller, where the network update request is part of real-time publish/subscribe protocol, the sending network update request includes a publish message having a specified topic and a set of QoS attributes, and the receiving a network update request includes subscribing to the specified topic and the set of QoS attributes.