Media Services Bus for Interoperable Asset Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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

An interoperable media services bus that connects disparate media services through a standardized connector API, enabling message exchange and centralized services for uniformity, security, and scalability, including a transport service for secure asset transfer and orchestration of complex transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If point-to-point connections are created between media services, then communication between specific services is enabled, but the system complexity and cost increase significantly as the number of services grows

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a message bus as an intermediary component that mediates communication between all 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 the number of direct connections needed from O(n²) to O(n), significantly reducing integration complexity while maintaining communication reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message bus provides universal communication capabilities that can be used by any media service in the system. A single bus infrastructure supports multiple services, multiple message types, and multiple communication patterns (publish-subscribe, request-response, etc.), eliminating the need for separate dedicated communication channels between each service pair.

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

2Adaptability or versatility

If custom interfaces are developed for each service connection, then specific communication needs are met, but the development time and cost increase

Engineering Contradiction:
Improvecommunication flexibilityVSAvoidinterface development time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The message bus provides a universal communication framework that handles standard message routing, formatting, and delivery for all services. This eliminates the need to develop custom communication interfaces for each service connection, reducing development time significantly while maintaining flexibility through standardized message protocols and subscription-based service discovery.

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

Solution Approach 2:

The system performs preliminary actions by pre-configuring service subscriptions and message routes in advance. Services declare their communication needs through subscriptions to specific message types or topics, and the message bus pre-establishes the communication paths. This eliminates the need for time-consuming custom interface development and testing for each service connection.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If modifications are made to media services, then service functionality is improved, but existing point-to-point connections become fragile and require updates

Engineering Contradiction:
Improveservice adaptabilityVSAvoidconnection stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The message bus acts as a buffer and adapter between services, absorbing the impact of service modifications. When a service is modified, the changes are isolated to that service's interaction with the bus, while other services continue to communicate through the unchanged bus interface. This maintains connection stability while allowing service adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message bus uses standardized message parameters and protocols that remain constant even when service implementations change. Services communicate through defined message types, topics, and schemas that are independent of specific service implementations, allowing services to be modified without affecting the stability of connections to other services.

Inventive Principle:
Principle #35Parameter changes

4Ease of operation

If a monolithic structure is used to support multiple services, then intercommunication is simplified, but the cost scales prohibitively with the number of services

Engineering Contradiction:
Improveoperation simplicityVSAvoidsystem cost
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the communication infrastructure into independent, modular components: a central message bus and individual service modules. Each service connects to the bus independently rather than requiring a custom-built monolithic system. This modular segmentation reduces system cost by allowing services to be added or removed without restructuring the entire system, while the bus provides simplified operation through unified communication protocols.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8086758B1Systems and methods for interconnecting media applications and services with centralized services
Publication Date: 2011.12.27 DISNEY ENTERPRISES INC
  • US8086758B1 patent drawing
  • US8086758B1 patent drawing
  • US8086758B1 patent drawing

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 in a standardized format related to transactions to be performed involving media assets and/or metadata associated with media assets. Also connected to the interoperable media services bus are one or more centralized services that can be used to improve uniformity of behavior across the media services. Examples of centralized services include searching of media asset metadata, management of access rights to media services and/or media assets, accounting functions related to use of the media services, transformations (such as encoding or digital-rights management wrapping) of media assets, and the like.