IP Library Granted Patent US 12,335,567
Granted Patent B1
US 12,335,567 · App. 18/443,805 · Granted Jun 17, 2025

Change requests in media broadcast content distribution system

Inventors: Steve Mills (San Antonio, TX); Jeffrey Lee Littlejohn (Cincinnati, OH); David C. Jellison, Jr. (Austin, TX); Vijay Jayakumar (San Antonio, TX); Riad Edelbi (San Antonio, TX); Adam Zastawski (San Antonio, TX); José Antonio Carbajal Orozco (San Antonio, TX)
Assignee: iHeartMedia Management Services, Inc.
H04N21/4431H04N21/23424H04N21/2407H04N21/4622H04N21/812H04N21/23
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,335,567
App. No.
18/443,805
Granted
Jun 17, 2025
Kind
B1
Abstract

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.

Claims (67)

1. A method comprising:

providing a media playout system access to a plurality of media automation services via a master API, wherein the media playout system transmits media station content to end-users;

transmitting, from the master API to the media playout system, at least one media delivery schedule indicating scheduled media items to be transmitted by the media playout system to the end-users;

receiving, at the master API, a change request from a first media playout system, wherein 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;

transmitting the change request from the master API to a first media automation service selected by the master API based on the requested change;

receiving, at the master API from the first media automation service, updated media delivery information responsive to the change request; and

transmitting the updated media delivery information from the master API to the first media playout system.

2. The method of claim 1 , wherein:

the change request includes a request to modify scheduling of a programmatic advertisement; and

transmitting the change request from the master API to the first media automation service includes transmitting the request to modify scheduling of the programmatic advertisement to a programmatic advertisement system.

3. The method of claim 2 , further including:

transmitting the request to modify scheduling of the programmatic advertisement from the master API to a second media automation service, wherein the second media automation service includes a log manager.

4. The method of claim 1 , wherein:

the change request includes a request for an updated broadcast log; and

receiving the updated media delivery information responsive to the change request includes receiving the updated broadcast log.

5. The method of claim 4 , wherein:

receiving the updated broadcast log includes receiving, at an ingestion update module of the master API, a notification from a log manager indicating that an updated log is ready to be retrieved; and

retrieving, by the ingestion update module of the master API, the updated broadcast log from the log manager.

6. The method of claim 1 , further comprising:

storing, by the master API, the updated media delivery information in one or more databases accessible via the master API.

7. The method of claim 1 , further comprising:

in response to receiving the updated media delivery information indicating that broadcast of a media item is to be changed, transmitting a change notification to a second media automation service different than the first media automation service.

8. A processing device, comprising:

a processor;

memory coupled to the processor;

a program of instructions configured to be stored in the memory and executed by the processor to implement a master API, wherein the master API is configured to

provide a media playout system access to a plurality of media automation services via the master API, wherein the media playout system transmits media station content to end-users;

transmit, to the media playout system, at least one media delivery schedule indicating scheduled media items to be transmitted by the media playout system to the end-users;

receive, at the master API, a change request from a first media playout system, wherein 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;

transmit the change request from the master API to a first media automation service selected by the master API based on the requested change;

receive, at the master API from the first media automation service, updated media delivery information responsive to the change request; and

transmit the updated media delivery information from the master API to the first media playout system.

9. The processing device of claim 8 , wherein:

the change request includes a request to modify scheduling of a primary content media item; and

transmitting the change request from the master API to the first media automation service includes transmitting the request to modify scheduling of the primary content media item to a media manager.

10. The processing device of claim 9 , further including:

transmitting the request to modify scheduling of the primary content media item from the master API to a second media automation service, wherein the second media automation service includes a log manager.

11. The processing device of claim 8 , wherein:

the change request includes a request for an updated broadcast log; and

receiving the updated media delivery information responsive to the change request includes receiving the updated broadcast log.

12. The processing device of claim 11 , wherein:

receiving the updated broadcast log includes receiving, at an ingestion update module of the master API, a notification from a log manager indicating that an updated log is ready to be retrieved; and

retrieving, by the ingestion update module of the master API, the updated broadcast log from the log manager.

13. The processing device of claim 8 , further comprising:

storing, by the master API, the updated media delivery information in one or more databases accessible via the master API.

14. The processing device of claim 8 , further comprising:

receiving, at the master API, an additional change request from the first media playout system;

transmitting the additional change request from the master API to the first media automation service;

receiving, at the API, a denial of the additional change request; and

sending a denial notification to the first media playout system in place of the updated media delivery information in response to the denial.

15. A method comprising:

providing a media playout system access to a plurality of media automation services via a master API, wherein the media playout system transmits media station content to end-users;

transmitting, from the master API to the media playout system, at least one media delivery schedule indicating scheduled media items to be transmitted by the media playout system to the end-users;

receiving, at the master API, a change request from a first media playout system, wherein 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;

transmitting the change request from the master API to the plurality of media automation services selected by the master API based on the requested change;

receiving, at the master API from the plurality of media automation services, updated media delivery information responsive to the change request; and

transmitting the updated media delivery information from the master API to the first media playout system.

16. The method of claim 15 , wherein:

transmitting the change request from the master API to the plurality of media automation services includes transmitting the change request to a log manager.

17. The method of claim 16 , wherein:

transmitting the change request from the master API to the plurality of media automation services includes transmitting the change request to a programmatic advertisement system.

18. The method of claim 16 , wherein:

transmitting the change request from the master API to the plurality of media automation services includes transmitting the change request to a media automation service.

19. The method of claim 18 , wherein:

receiving the updated media delivery information at the master API includes receiving an updated primary content item from the media automation service.

20. The method of claim 16 , wherein:

receiving the updated media delivery information at the master API includes receiving an updated broadcast log from the log manager.

Assignments (6)
PATENT SECURITY AGREEMENT Recorded Dec 29, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 069795/0912 →
PATENT SECURITY AGREEMENT Recorded Dec 28, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069793/0758 →
PATENT SECURITY AGREEMENT Recorded Dec 28, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069794/0248 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069792/0335 →
PATENT SECURITY AGREEMENT Recorded Dec 23, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069762/0453 →
PATENT SECURITY AGREEMENT Recorded Dec 22, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069752/0941 →
Continuity (1)
Continuation 17678243 · Feb 23, 2022
References Cited (23)
US 10827214B1 · Thapaliya · 2020 [cited by applicant]
US 20010000194A1 · Sequeira · 2001 [cited by examiner]
US 20080167957A1 · Steelberg et al. · 2008 [cited by applicant]
US 20100299437A1 · Moore · 2010 [cited by applicant]
US 20160073176A1 · Phillips et al. · 2016 [cited by applicant]
US 20170262865A1 · Littlejohn et al. · 2017 [cited by applicant]
US 20170374116A1 · Phillips et al. · 2017 [cited by applicant]
US 20190246158A1 · Martell · 2019 [cited by applicant]
US 20210099759A1 · Armstrong et al. · 2021 [cited by applicant]
US 20210204009A1 · Levin et al. · 2021 [cited by applicant]
US 20210368215A1 · Richman et al. · 2021 [cited by applicant]
US 20210409110A1 · Chakraborty et al. · 2021 [cited by applicant]
US 20220014575A1 · Corl · 2022 [cited by applicant]
US 20220014579A1 · Bachmutsky et al. · 2022 [cited by applicant]
US 20220046302A1 · Shanson et al. · 2022 [cited by applicant]
US 20220245675A1 · Mochrie et al. · 2022 [cited by applicant]
US 20220321663A1 · Benson · 2022 [cited by applicant]
US 20220337910A1 · Delgado · 2022 [cited by applicant]
US 20230124840A1 · Giladi · 2023 [cited by examiner]
US 20230140859A1 · Fujiwara et al. · 2023 [cited by applicant]
US 20240201923A1 · Bertrand · 2024 [cited by examiner]
Cahill, Mark, “Building a Microservice API Gateway for iHeartRadio's Radio Station Network with GraphQL,” Oct. 22, 2018, 17 pages. [cited by applicant]
Nang, Kailuo, “Why we picked AKKA cluster as our microservice framework,” Feb. 3, 2016, 6 pages. [cited by applicant]