Media Services Bus for Interoperable Workflow Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for integrating media asset management services across disparate business units are inflexible and costly, with point-to-point connections being time-consuming and fragile, and monolithic structures becoming prohibitively expensive as the number of services increases, limiting scalability in large organizations.
Innovation Solution
A service-oriented architecture with an interoperable media services bus that enables media services to exchange messages through a common protocol, using connectors and an orchestration service to coordinate complex transactions and workflows, allowing for the integration of diverse media services across an organization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If point-to-point connections are created between media services, then interoperability between services is achieved, but device complexity and implementation cost increase significantly as the number of services grows
Solution Approach 1:
The patent introduces a message bus as an intermediary component that mediates communication between media services. Instead of creating direct point-to-point connections between every pair of services, the message bus serves as a central intermediary that routes messages between services. This reduces connection complexity from O(n²) to O(n), where n is the number of services, while maintaining full interoperability.
Solution Approach 2:
The message bus provides universal communication capabilities that can be used by any media service to interact with any other service. A single bus infrastructure supports multiple communication patterns and service types, eliminating the need for separate connection mechanisms for each service pair.
2Adaptability or versatility
If custom interfaces are developed for each service connection, then specific integration requirements are met, but implementation time and development cost increase
Solution Approach 1:
The patent uses standardized message templates and protocols that can be copied and reused across different service integrations. Instead of developing unique interfaces for each connection, the same message bus protocol and template structures are replicated and adapted for different service pairs, significantly reducing development time while maintaining customization capabilities through message content flexibility.
3Adaptability or versatility
If a monolithic structure is used to support multiple media services, then system-wide integration is achieved, but implementation cost becomes prohibitively expensive as the number of services increases
Solution Approach 1:
The patent segments the integration architecture into independent, loosely-coupled components: individual media services that maintain their autonomy and a separate message bus infrastructure. This segmentation allows each service to be developed, deployed, and scaled independently, reducing overall system complexity and cost compared to a monolithic structure while achieving system-wide integration through the bus.
Data Source
AI summary
Systems and methods are provided to integrate disparate media services and applications across an organization. The media services are connected to an interoperable media services bus by creating a connector API for each service, thereby enabling the media services to exchange messages related to transactions to be performed involving media assets and/or metadata associated with media assets. To support complex transactions involving coordinated activity by multiple media services, an orchestration service advantageously performs a coordinated sequence of request/response transactions, referred to as a “workflow.” The workflow may include requests conditional on responses to previous requests, multiple parallel requests, a combination of synchronous and asynchronous requests, and so on. Multiple workflows may be managed concurrently.