Cloud Microservices Orchestrate Media Workflows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital media archive solutions are costly, require significant maintenance, and are inflexible, relying on on-premises infrastructure that is hard to scale and maintain, necessitating manual coding for workflow establishment and requiring specialized engineering staff, which limits innovation and increases technical debt.

Innovation Solution

A microservice application architecture using REST web services that allows non-engineers to create and orchestrate media pipelines dynamically through programmatically generated webforms, leveraging cloud-native serverless workflows and microservices to decouple functionality and empower administrators to manage workflows without extensive software development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If on-premises linear tape-open storage and enterprise workflow solution are used, then asset protection and archiving are achieved, but capital investment and maintenance costs increase significantly

Engineering Contradiction:
Improveasset protectionVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements digital media archiving by creating digital copies of media assets and storing them in cloud-based digital media archives, replacing physical tape storage. This allows asset protection through multiple digital replicas while eliminating the need for complex on-premises tape libraries and associated hardware infrastructure.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces mechanical tape storage systems with cloud-based digital storage infrastructure. The physical mechanical systems (tape drives, library robots, cooling systems) are substituted with virtualized cloud storage services, eliminating the need for specialized hardware while maintaining asset protection capabilities.

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

2Productivity

If on-premises enterprise workflow solution is used, then media workflow management is achieved, but continuous maintenance and support requirements increase

Engineering Contradiction:
Improveworkflow managementVSAvoidmaintenance time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements serverless cloud-based workflows that automatically manage media processing tasks without requiring continuous human intervention or specialized maintenance. The cloud infrastructure self-manages scaling, updates, and operational complexity, freeing engineering staff from routine maintenance while maintaining productive workflow management.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If on-premises software infrastructure is used, then media pipeline functionality is achieved, but scalability and ease of maintenance deteriorate

Engineering Contradiction:
Improvemedia pipeline functionalityVSAvoidease of maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements a universal cloud-based media pipeline platform that handles multiple media processing functions (transcoding, rendering, delivery) through a single unified infrastructure. This multi-functional cloud platform serves diverse media workflow needs while maintaining consistent ease of operation and maintenance across all functions, unlike specialized on-premises tools.

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

Solution Approach 2:

The patent implements dynamically scalable cloud-based media pipelines that can automatically adjust computing resources based on workflow demands. The infrastructure transitions from static on-premises hardware to dynamic cloud resources that scale up during peak processing needs and scale down during low-utilization periods, maintaining functionality while improving operational ease.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If manual workflow coding is required, then customized media workflows are achieved, but engineering staff time and expertise requirements increase

Engineering Contradiction:
Improveworkflow customizationVSAvoidworkflow establishment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements self-service workflow templates that allow media professionals to create customized workflows through configuration interfaces without requiring programming expertise. The system provides pre-built workflow templates that can be customized through parameter settings rather than code writing, enabling rapid workflow establishment while maintaining adaptability.

Inventive Principle:
Principle #25Self-service

5Productivity

If siloed software tools are used, then specific media tasks are achieved, but development consistency and team collaboration deteriorate

Engineering Contradiction:
Improvetask executionVSAvoiddevelopment consistency
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The patent merges previously siloed media processing tools into a unified cloud-based media pipeline platform. All media tasks (transcoding, rendering, delivery) are combined into a single integrated system with consistent development practices, eliminating the fragmentation that caused inconsistency across development, quality assurance, and production environments.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11363087B2Leveraging microservices to orchestrate media workflows in the cloud
Publication Date: 2022.06.14 ADEIA MEDIA HOLDINGS INC
  • US11363087B2 patent drawing
  • US11363087B2 patent drawing
  • US11363087B2 patent drawing

AI summary

A method and system provide the ability to orchestrate a media workflow using a computer system. A payload for an application programming interface (API) to be utilized to process media content is determined. The payload is parsed to display one or more variables of the payload in a graphical user interface. The variables are mapped to webform user interface elements. A job of the media workflow is executed. During execution, a webform of the user interface elements is programmatically generated and presented to an operator, data for the payload is received via the webform, and the received data is provided to the API to process the media content.