Device-Independent Command Interface for SDN Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software-defined data centers face challenges in implementing specific operations due to the compromise between the ease of control provided by software-defined networking (SDN) abstraction and the greater control offered by traditional element management systems (EMS) via command line interfaces (CLI).

Innovation Solution

The implementation of device-independent commands across heterogeneous network devices, enabled by a graphical user interface on a virtual network controller, allows users to define and execute operations using job templates, tasks, and input/output schemas, facilitating device-agnostic operations across different device families.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If SDN abstraction is used to provide ease of control, then ease of operation is improved, but device complexity increases due to the need for abstraction layers

Engineering Contradiction:
Improveease of controlVSAvoidabstraction complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer that translates high-level intent-based commands into device-specific operations. This mediator handles the complexity of different device families internally while presenting a simplified interface to users, resolving the contradiction by hiding abstraction complexity behind an easy-to-use interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements universal device-independent commands that can operate across multiple device families through a common interface. This multi-functionality allows the same command structure to work across diverse devices, improving ease of operation without requiring users to understand device-specific complexities.

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

2Adaptability or versatility

If traditional EMS with CLI is used to provide greater control, then adaptability is improved, but ease of operation deteriorates due to complex command line interfaces

Engineering Contradiction:
Improvecontrol capabilityVSAvoidease of use
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the control interface into two distinct layers: a simplified user-facing layer for ease of operation and a backend layer that maintains full adaptability through device-specific command translations. This segmentation allows both high-level simplicity and low-level versatility to coexist.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adds a new dimension to the control interface by introducing device-independent commands that operate above the traditional CLI layer. This additional abstraction dimension provides both the simplicity of high-level commands and the adaptability of device-specific operations without requiring users to navigate complex CLI interfaces.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Manufacturing precision

If device-specific commands are used to perform operations on heterogeneous devices, then manufacturing precision is improved, but adaptability deteriorates due to vendor-specific command requirements

Engineering Contradiction:
Improveoperation accuracyVSAvoidvendor compatibility
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent creates copied versions of device-specific commands within the device-independent command structure. Each vendor-specific command is replicated and adapted to work across different device families through standardized parameter mappings, maintaining operational precision while achieving vendor compatibility.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system changes parameters from device-specific values to standardized device-independent parameters. By transforming vendor-specific command parameters into universal parameters that map to device-specific implementations, the system maintains precise control while achieving compatibility across heterogeneous devices.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If device-independent commands are implemented across heterogeneous devices, then adaptability is improved, but device complexity increases due to translation requirements

Engineering Contradiction:
Improvevendor-agnostic operationVSAvoidcommand translation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements self-service translation mechanisms where the device-independent command framework automatically handles the translation to device-specific commands without requiring external intervention. This automation reduces the perceived complexity for users while maintaining the necessary translation capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary translation setup by pre-defining mappings between device-independent commands and device-specific implementations. This advance preparation of translation rules reduces the complexity of real-time command translation and enables seamless operation across heterogeneous devices.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11329914B2User customization and automation of operations on a software-defined network
Publication Date: 2022.05.10 JUNIPER NETWORKS INC
  • US11329914B2 patent drawing
  • US11329914B2 patent drawing
  • US11329914B2 patent drawing

AI summary

In general, techniques are described for defining and executing device-independent commands on a network having a plurality of network devices. In some examples, a controller includes a graphical user interface. The controller displays, via the graphical user interface, network devices that support a device-independent command selected from one or more device-independent commands, wherein each device-independent command performs one or more operations on supported network devices. The controller receives, via the graphical user interface, user input selecting two or more of the displayed network devices and performs the one or more operations of the selected device-independent command on the selected network devices. In some examples, performing includes executing tasks associated with each network device, wherein the tasks, when executed, perform the one or more operations on each respective network device.