Reusable Workflow Designer for SDN Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software-defined networks (SDNs), managing software changes across virtualized network components is inefficient due to the need for manual task execution and lack of reusable workflows, leading to lengthy development times and inefficiencies in operations.

Innovation Solution

The introduction of an API Stitching Workflow Designer and Task Management dashboard enables the creation of reusable workflows, allowing for automated orchestration of open loop tasks without additional programming, focusing on metadata-driven design and execution to streamline SDN operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual task execution is used for managing software changes in SDN, then flexibility in task execution is maintained, but development time increases and operational efficiency decreases

Engineering Contradiction:
Improveoperational efficiencyVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining reusable workflow templates that encapsulate common SDN operational tasks. These templates are created in advance and stored in a repository, allowing operators to quickly deploy standardized procedures without manual programming each time. The workflow templates include pre-configured task sequences, parameters, and logic, enabling rapid instantiation when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements copying by allowing workflow templates to be reused across multiple instances. Once a workflow is designed and validated, it can be copied and instantiated multiple times with different parameters. This eliminates the need to recreate the same operational procedures repeatedly, significantly reducing development time while maintaining consistency across operations.

Inventive Principle:
Principle #26Copying

2Productivity

If reusable workflows are implemented, then development time is reduced and operational efficiency increases, but system complexity increases due to workflow management infrastructure

Engineering Contradiction:
Improveoperational efficiencyVSAvoidworkflow management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer in the form of a workflow management system that sits between the operational requirements and the underlying system components. This intermediary handles the complexity of workflow definition, storage, validation, and execution, shielding users from the intricate details while providing powerful reusable workflow capabilities. The workflow engine acts as a mediator that translates high-level operational intents into executable task sequences.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If workflows are created without additional programming, then ease of operation improves, but the level of automation decreases

Engineering Contradiction:
Improveworkflow creation easeVSAvoidworkflow automation level
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The patent applies self-service by enabling operations personnel to create and configure workflows using a visual designer interface without requiring programming expertise. The system provides self-service capabilities through drag-and-drop workflow assembly, automatic parameter binding, and built-in validation, allowing users to build automated workflows independently. This maintains high automation levels while improving ease of operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10536348B2Operational micro-services design, development, deployment
Publication Date: 2020.01.14 AT&T INTELLECTUAL PROPERTY I L P
  • US10536348B2 patent drawing
  • US10536348B2 patent drawing
  • US10536348B2 patent drawing

AI summary

Components may provide functionality which separate operation functions in a separate entity, isolate the functions as reusable, and connect them in a control loop in an SDN environment.