Workflow Reconfiguration Across Device Ecosystem Domains

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As computing device ecosystems grow in complexity, determining optimal deployment locations for workflow components and efficiently managing data transfer between domains becomes increasingly challenging, especially when changes to workflow execution are necessary due to events such as capacity changes or service level objective (SLO) violations.

Innovation Solution

A method and system for optimizing workflow execution involving a federated controller that receives event notifications, performs workflow reconfiguration actions, and identifies data transfer optimization actions to efficiently deploy workflow portions across different domains within the ecosystem, utilizing service and platform controllers to map capabilities and capacity, and optimize data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If workflows are deployed across multiple domains in a complex device ecosystem, then workflow execution flexibility and adaptability are improved, but data transfer complexity and costs increase

Engineering Contradiction:
Improveworkflow deployment flexibilityVSAvoiddata transfer complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces data transfer optimization actions as intermediary mechanisms that mediate between different domains. These optimization actions include data compression, encryption, and format conversion that simplify cross-domain data transfer while maintaining workflow flexibility. The service controller acts as a mediator that coordinates data transfer between platform controllers in different domains, reducing the overall complexity of federated workflow execution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes data transfer parameters such as compression level, encryption method, and data format based on the specific requirements of each workflow portion and the capabilities of the target domain. This allows the system to adapt data transfer characteristics to optimize for speed, security, or bandwidth efficiency depending on the situation, thereby improving deployment flexibility without proportionally increasing complexity.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If data is transferred between domains to execute workflow portions, then workflow reconfiguration capability is improved, but data transfer time and costs increase

Engineering Contradiction:
Improveworkflow reconfiguration capabilityVSAvoiddata transfer time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary data transfer optimization actions before actual data transmission. This includes pre-compressing data, pre-encrypting sensitive information, and pre-converting data formats to match the target domain's requirements. By preparing data in advance, the system reduces the time required for actual data transfer when workflow reconfiguration is needed, as the optimization overhead is already completed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces traditional mechanical data transfer mechanisms with optimized digital processes. Instead of direct raw data transmission, the system uses automated data transformation pipelines that apply compression, encryption, and format conversion algorithms. This substitution of mechanical transfer with intelligent digital processing reduces transfer time and enables more efficient workflow reconfiguration across domains.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If workflow portions are redistributed across domains in response to events, then service level objective compliance is improved, but system control complexity increases

Engineering Contradiction:
Improveservice level objective complianceVSAvoidsystem control complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a feedback mechanism where the service controller monitors workflow execution across domains and receives event notifications about capacity changes, SLO violations, or other conditions. Based on this feedback, the service controller automatically triggers workflow reconfiguration actions, redistributing workflow portions to appropriate domains. This closed-loop control system maintains SLO compliance while managing complexity through automated decision-making rather than manual coordination.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service workflow reconfiguration where platform controllers in different domains autonomously execute optimization actions based on notifications from the service controller. Each platform controller independently manages its local resources and data transfer optimizations without requiring centralized control for every decision. This distributed self-service approach improves SLO compliance through rapid local responses while reducing overall system control complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11669525B2Optimizing workflow movement through device ecosystem boundaries
Publication Date: 2023.06.06 EMC IP HLDG CO LLC
  • US11669525B2 patent drawing
  • US11669525B2 patent drawing
  • US11669525B2 patent drawing

AI summary

Techniques described herein relate to a method for optimizing workflow execution. The method may include receiving an event notification at a service controller, wherein the event notification is associated with a workflow deployed in a device ecosystem; performing, based on receiving the event notification, a workflow reconfiguration action comprising: providing a first workflow portion to a first platform controller in a first domain in the device ecosystem; transmitting a workflow reconfiguration action notification to a second platform controller in a second domain of the device ecosystem; identifying, by the second platform controller and in response to receiving the workflow reconfiguration action notification, a data transfer optimization action associated with data to be transmitted from the second domain to the first domain and used during execution of the first workflow portion; and transmitting the data from the second domain to the first domain using the data transfer optimization action.