# US 2025/0166012 A1 · Live ad processing engine service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0166012 A1
- Document ID: US20250166012A1
- Status: Published application
- Kind: A1
- Application number: 19/026,974
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2013-04-23
- Assignees: Adeia Media Holdings LLC
- Applicants: Adeia Media Holdings LLC
- Inventors: Albert John McGowan; Nicholas Maultsby; Niko T.J. Huffman; Christian D. Moosman
- Web page: https://patentgrep.com/patent/US20250166012A1

## CPC

- G06Q 30/0264: {based upon schedule}
- H04N 21/23424: {involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement}
- H04N 21/44016: {involving splicing one content stream with another content stream, e.g. for substituting a video clip}
- H04N 21/812: {involving advertisement data (advertising per se G06Q30/02)}
- H04N 21/2393: {involving handling client requests (scheduling or organising the servicing of application requests H04L67/60)}
- H04N 21/262: Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists {(scheduling strategies for dispatcher in multiprogramming arrangements G06F9/4881; arrangements for scheduling broadcast services or broadcast-related services H04H60/06; flow control in packet networks H04L47/10; establishing a time schedule or organising the servicing of application requests H04L67/62)}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

Techniques described herein provide for a live advertising processing engine service to act as an intermediary between client applications and advertising networks. The live advertising processing engine service can provide an interface with which the client can interact, via an application programming interface (API) or directly through the use of a standardized language, thereby allowing client applications to receive advertisement data without the need to be customized to communicate with specific advertising networks. The live advertising processing engine service can further track where, in playback the live content, a client currently is, to indicate to the client—or other application—when advertisement breaks are and/or provide supplemental advertisement information to enable the client to provide a rich user experience.

## Claims

### Claim 1

(canceled)

### Claim 2

A method performed by a client device in communication with a system comprising at least one service provider server and at least one advertisement engine server, the method comprising:
requesting a first manifest for live media content;
receiving the first manifest for the live media content from the at least one service provider server, wherein the first manifest comprises:
a plurality of URIs corresponding to a plurality of chunks of the live media content; and
an indication of a first time in the live media content designated for advertising content;
generating for display a chunk of the plurality of chunks of the live media content based at least in part on data received by accessing a URI corresponding to the chunk of the plurality of chunks of the live media content;
transmitting, while the chunk of the plurality of chunks of the live media content is being displayed and before reaching the first time, an application programming interface (API) call;
receiving, based at least in part on transmitting the API call to the at least one advertisement engine server, a second manifest comprising a plurality of URIs corresponding to a plurality of chunks of first advertising content for display at the first time; and
generating for display, at the first time, a chunk of the plurality of chunks of the first advertising content based at least in part on data received by accessing the URI corresponding to the chunk of the plurality of chunks of the first advertising content.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
receiving an identification of a second time in the live media content designated for advertising content;
transmitting, while displaying another chunk of the plurality of chunks of the live media content and before reaching the second time, a second API call to the at least one advertisement engine server; and
receiving, based at least in part on transmitting the second API call to the at least one advertisement engine server, a third manifest comprising a plurality of URIs corresponding to a plurality of chunks of a content for display at the second time, wherein the third manifest is dynamically generated based at least in part on information associated with the client device.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
generating a play session token for consumption of the live media content; and
wherein a generation of the second manifest comprising the plurality of URIs corresponding to the plurality of chunks of the first advertising content and the generation of the third manifest comprising the plurality of URIs corresponding to the plurality of chunks of the second advertising content are coordinated based on the play session token.

### Claim 5 (depends on 2)

The method of claim 2, further comprising:
configuring a tracking beacon for monitoring playback parameters of the live media content; and
transmitting data gathered by the tracking beacon to at least one server.

### Claim 6 (depends on 2)

The method of claim 2, wherein the second manifest is dynamically generated based at least in part on information associated with the client device.

### Claim 7 (depends on 2)

The method of claim 2, wherein the second manifest comprises one or more instructions for predetermined behaviors to be implemented on the client device during the display of the plurality of chunks of the first advertising content, the predetermined behaviors comprising at least one of:
displaying an interstitial banner, displaying an overlay advertisement, blocking fast-forward controls, enabling interactive content, or providing a tracking beacon.

### Claim 8 (depends on 2)

The method of claim 2, wherein the second manifest is generated based on stored rules and identifying information associated with the client device.

### Claim 9 (depends on 8)

The method of claim 8, wherein the identifying information comprises geographical data associated with the client device.

### Claim 10 (depends on 2)

The method of claim 2, wherein the second manifest is generated based on at least one of: a title of the live media content, a duration of the live media content, or a genre of the live media content.

### Claim 11 (depends on 2)

The method of claim 2, wherein the second manifest comprises one or more tracking URLs for monitoring at least one of:
playing performance of the advertising content, advertisement impressions, or user interactions with the advertising content.

### Claim 12

A method performed by a client device in communication with a system comprising at least one service provider and at least one advertisement engine server, the method comprising:
receiving a first manifest for a live media content from the at least one service provider, wherein the first manifest comprises:
a first plurality of addresses corresponding to a first subset of segments of the live media content; and
generating for display a segment of the first subset of segments of the live media content received by transmitting a request comprising an address of the first plurality of addresses corresponding to the segment of the first subset of segments;
while the segment of the first subset of segments is being displayed, receiving data for updating the first manifest, wherein the updated first manifest comprises:
a second plurality of addresses corresponding to a second subset of segments of the live media content; and
an indication of a first time in the live media content designated for advertising content;
generating for display a segment of the second subset of segments based at least in part on data received by accessing addresses of the second plurality of addresses corresponding to the segment of the second subset of segments;
transmitting, while the segment of the of the second subset of segments is being displayed and before reaching the first time, a request to the at least one advertisement engine server;
receiving, based at least in part on transmitting the request to the at least one advertisement engine server, a second manifest comprising a plurality of addresses corresponding to a plurality of segments of first advertising content for display at the first time; and
generating for display, at the first time, a segment of the plurality of segments of the first advertising content based at least in part on data received by accessing the address corresponding to the segment of the plurality of segments of the first advertising content.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
receiving an identification of a second time in the live media content designated for advertising content;
transmitting, while displaying another chunk of the plurality of segments of the live media content and before reaching the second time, a second API call to the at least one advertisement engine server; and
receiving, based at least in part on transmitting the second API call to the at least one advertisement engine server, a third manifest comprising a plurality of addresses corresponding to a plurality of segments of a second advertising content for display at the second time, wherein the third manifest is dynamically generated based at least in part on information associated with the client device.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
generating a play session token for consumption of the live media content; and
wherein a generation of the second manifest comprising the plurality of addresses corresponding to the plurality of segments of the first advertising content and the generation of the third manifest comprising the plurality of addresses corresponding to the plurality of segments of the second advertising content are coordinated based on the play session token.

### Claim 15

A system comprising:
at least one service provider;
at least one advertisement engine server communicatively coupled with the at least one service provider;
a client device communicatively coupled with the at least one service provider and the at least one advertisement engine server comprising control circuitry and input/output circuitry, wherein the input/output circuitry is configured to:
request a first manifest for live media content from the at least one service provider;
receive the first manifest for the live media content from the at least one service provider, wherein the first manifest comprises:
a plurality of URIs corresponding to a plurality of chunks of the live media content; and
an indication of a first time in the live media content designated for advertising content; and
wherein the control circuitry is configured to:
generate for display a chunk of the plurality of chunks of the live media content based at least in part on data received by accessing a URI corresponding to the chunk of the plurality of chunks of the live media content; and
wherein the input/output circuitry is further configured to:
transmit, while the chunk of the plurality of chunks of the live media content is being displayed and before reaching the first time, an application programming interface (API) call to the at least one advertisement engine server;
receive, based at least in part on transmitting the API call to the at least one advertisement engine server, a second manifest comprising a plurality of URIs corresponding to a plurality of chunks of first advertising content for display at the first time; and
wherein the control circuitry is further configured to:
generating for display, at the first time, a chunk of the plurality of chunks of the first advertising content based at least in part on data received by accessing the URI corresponding to the chunk of the plurality of chunks of the first advertising content.

### Claim 16 (depends on 15)

The system of claim 15, wherein the input/output circuitry is further configured to:
receive an identification of a second time in the live media content designated for advertising content;
transmit, while displaying another chunk of the plurality of chunks of the live media content and before reaching the second time, a second API call to the at least one advertisement engine server; and
receive, based at least in part on transmitting the second API call to the at least one advertisement engine server, a third manifest comprising a plurality of URIs corresponding to a plurality of chunks of a second advertising content for display at the second time, wherein the third manifest is dynamically generated based at least in part on information associated with the client device.

### Claim 17 (depends on 16)

The system of claim 16, wherein the control circuitry is further configured to:
generate a play session token for consumption of the live media content; and
wherein a generation of the second manifest comprising the plurality of URIs corresponding to the plurality of chunks of the first advertising content and the generation of the third manifest comprising the plurality of URIs corresponding to the plurality of chunks of the second advertising content are coordinated based on the play session token.

### Claim 18 (depends on 15)

The system of claim 15, wherein:
the control circuitry is further configured to:
configure a tracking beacon for monitoring playback parameters of the live media content; and
the input/output circuitry is further configured to:
transmit data gathered by the tracking beacon to at least one server.

### Claim 19 (depends on 15)

The system of claim 15,, wherein the second manifest is dynamically generated based at least in part on information associated with the client device.

### Claim 20 (depends on 15)

The system of claim 15, wherein the second manifest comprises one or more instructions for predetermined behaviors to be implemented on the client device during the display of the plurality of chunks of the first advertising content, the predetermined behaviors comprising at least one of:
displaying an interstitial banner, displaying an overlay advertisement, blocking fast-forward controls, enabling interactive content, or providing a tracking beacon.

### Claim 21 (depends on 15)

The method of claim 15, wherein the second manifest is generated based on stored rules and identifying information associated with the client device.
