Media Broadcast Content Distribution via Microservice API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing media broadcast systems face inefficiencies due to reliance on monolithic enterprise applications, batch processing, and integration, leading to duplicated data and errors from non-real-time data sourcing. Additionally, terrestrial broadcast stations lack effective disaster recovery mechanisms when communication with media automation systems is severed.

Innovation Solution

The implementation of a media broadcast content distribution system using multiple microservice applications accessed through a common application programming interface (API). This system operates independently, allowing for real-time data exchange and improved disaster recovery capabilities by employing edge devices that can switch between cloud-based and local media automation services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If monolithic enterprise applications and batch processing are used in media delivery systems, then system integration is simplified, but data duplication and errors occur due to non-real-time data sourcing

Engineering Contradiction:
Improvesystem integration complexityVSAvoiddata accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the monolithic enterprise application into multiple microservice applications, each handling specific media delivery functions independently. This segmentation eliminates data duplication by allowing each microservice to access real-time data from centralized sources, thereby improving data accuracy while maintaining manageable system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

2Extent of automation

If terrestrial broadcast stations use conventional media automation systems, then automated media delivery is achieved, but disaster recovery is limited when communication is severed

Engineering Contradiction:
Improveautomated media deliveryVSAvoiddisaster recovery capability
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring edge devices with local media automation services that can operate independently of cloud-based systems. When communication is severed, these pre-configured local services automatically take over, ensuring continuous automated media delivery and robust disaster recovery without requiring real-time cloud connectivity.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple microservice applications are implemented, then real-time data exchange and disaster recovery are improved, but system complexity increases

Engineering Contradiction:
Improvedisaster recovery capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an application programming interface (API) as an intermediary that standardizes communication between multiple microservice applications and edge devices. This API layer abstracts the complexity of inter-service communication, allowing microservices to exchange real-time data efficiently while maintaining manageable system architecture through standardized interaction protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12335567B1Change requests in media broadcast content distribution system
Publication Date: 2025.06.17 IHEARTMEDIA MANAGEMENT SERVICES INC
  • US12335567B1 patent drawing
  • US12335567B1 patent drawing
  • US12335567B1 patent drawing

AI summary

A method includes providing a media playout system (MPS) access to a plurality of media automation services via a master API. The MPS transmits media station content to end-users. The master API transmits, to the MPS, at least one media delivery schedule indicating scheduled media items to be transmitted by the media playout system to the end-users, and receives a change request from a first media playout system. The change request indicates a requested change in one or more media items scheduled for transmission by the media playout system to the end-users. The API transmits the change request to a first media automation service, selected by the master API based on the requested change, receives from the first media automation service updated media delivery information responsive to the change request, and transmits the updated media delivery information from the master API to the first media playout system.