# US 2019/0246159 A1 · Systems and Methods of Programmatic Video Content Distribution

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

- Number: US 2019/0246159 A1
- Document ID: US20190246159A1
- Status: Published application
- Kind: A1
- Application number: 15/887,940
- Filed: 2018-02-02
- Published: 2019-08-08
- Earliest claimed: 2018-02-02
- Assignees: Martell Broadcasting Systems, Inc.
- Applicants: Martell Broadcasting Systems, Inc.
- Inventors: Carey Ray Martell; Akim Angelo Anastopoulo
- Web page: https://patentgrep.com/patent/US20190246159A1

## CPC

- H04N 21/26258: {for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list (retrieval of multimedia data based on playlists G06F16/40)}
- H04N 21/2187: Live feed
- H04N 21/23116: {involving data replication, e.g. over plural servers (synchronization of replicated data G06F11/1658; error detection or correction by means of data replication G06F11/2053; replication in distributed file systems G06F16/10; replication in distributed file systems G06F16/27; replication or mirroring of data in data networks H04L67/1095)}
- H04N 21/2343: involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements {(video transcoding H04N19/40; media packet handling at the source H04L65/762)}
- H04N 21/2668: Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles {(information retrieval from the Internet by querying with filtering and personalisation G06F16/9535; arrangements for replacing or switching information during the broadcast H04H20/10; push services over packet-switching network H04L12/1859; adaptation of message content in packet-switching networks H04L51/063)}
- H04N 21/437: Interfacing the upstream path of the transmission network, e.g. for transmitting client requests to a VOD server {(flow control in data networks H04L47/10; streaming protocols, e.g. RTP or RTCP, H04L65/65; scheduling or organising the servicing of application requests in data packet switching networks H04L67/60)}
- H04N 21/44204: {Monitoring of content usage, e.g. the number of times a movie has been viewed, copied or the amount which has been watched (monitoring of user activities for profile generation for accessing a video database G06F16/739; protecting generic digital content where the protection is independent of the precise nature of the content G06F21/10; arrangements for monitoring the use made of the broadcast services in broadcast systems H04H60/31)}
- H04N 21/6125: {involving transmission via Internet (transmission by internet of broadcast information H04H60/82)}
- H04N 21/6437: Real-time Transport Protocol [RTP]
- H04N 21/6581: {Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application}
- H04N 21/812: {involving advertisement data (advertising per se G06Q30/02)}
- H04N 21/8456: {by decomposing the content in the time domain, e.g. in time segments}
- H04N 21/85406: {involving a specific file format, e.g. MP4 format}
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A system for distributed content distribution is presented which enables and facilitates distributed content programming. According to the system, a list of content segments that make up an episode and episode metadata are distributed from server to client. The client uses the list of content segments and the episode metadata to present a streamlined viewing experience to the user, notwithstanding different locations, formats, encoding schemes, and packetization schemes of the content underlying the list of content segments.

## Claims

### Claim 1

A distributed content system for delivering content, comprising:
a client device comprising a display and a computing device;
wherein the client device is configured to run a content controller and a content player;
wherein the content player is configured to play an object defined by the content controller;
wherein the content controller is further configured to send a content identifier to a server computing device, the server computing device being configured to receive the content identifier and to send data comprising a list of content segments and a content segment length corresponding to a content segment in the list to the client device in response to the receipt of the content identifier;
wherein the content controller is further configured to:
(a) verify that the content segment corresponds to a current time,
(b) define the object to be played by the content player by setting the content segment as the object,
(c) determine an offset time of the object based on the current time,
(d) activate the object using the offset time,
(e) determine an equivalent time elapsed for the episode based on a time elapsed since the episode began playing and the offset time of the object, and
(f) determine whether the equivalent time elapsed since the object was activated is equivalent to or greater than the content segment length of the object, and if the determination is yes, redefine the object to be played by the content player by defining a second content segment in the list of content segments as the object,
wherein each content segment in the list of content segments comprises a content resource locator; and
wherein the list of content segments comprises at least one advertisement content segment and at least one content segment not associated with an advertisement.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first content resource locator corresponds to content located on a first server, and a second content resource locator corresponds to content located on a second server, wherein the first and second servers are different.

### Claim 3 (depends on 1)

The system of claim 1, wherein the first content resource locator corresponds to content packetized according to a first protocol, and the second content resource locator corresponds to content packetized according to a second protocol, wherein the first and second protocols are different.

### Claim 4 (depends on 1)

The system of claim 1, wherein the first content resource locator corresponds to content packaged in a first package format, and the second content resource locator corresponds to content packaged in a second package format, wherein the first and second package formats are different.

### Claim 5 (depends on 1)

The system of claim 1, wherein the first content resource locator corresponds to content packetized according to MPEG-DASH protocol.

### Claim 6 (depends on 1)

The system of claim 1, wherein the first content resource locator corresponds to content packetized according to real-time messaging protocol (RTMP).

### Claim 7

A distributed content system for delivering content comprising:
a client device, configured to communicate with a first server, a second server, and a third server, wherein the client device comprises computer instructions for performing the following:
sending an episode identifier to the first server,
receiving, in response to the first server's receipt of the episode identifier, a list of content segments and episode metadata, wherein the list of content segments comprises a first content resource locator and a second content resource locator, and wherein the episode metadata comprises an episode length, wherein the list of content segments comprises at least one advertisement content segment and at least one content segment not associated with an advertisement,
sending a first request for a first content segment to the second server using the first content resource locator,
receiving, in response to the second server's receipt of the first request, the first content segment comprising first packetized digital video data,
playing the first content segment on the client device and beginning a timer near when the first content segment begins playing, wherein the timer is configured to count up an elapsed time,
sending a second request for a second content segment to the third server using the second content resource locator,
receiving, in response to the second server's receipt of the second request, the second content segment comprising second packetized digital video data that corresponds to advertisement content,
playing the second content segment on the client device,
determining, based on the timer and the episode metadata, whether the client device has completed playback of the list of content segments.

### Claim 8 (depends on 7)

The system of claim 7, wherein the first packetized digital video data is packetized according to a first protocol and the second packetized digital video data is packetized according to a second protocol, and the first and second protocols are different, and wherein the client device is further configured to play the second packetized digital video data immediately following completion of playing the first packetized digital video data.

### Claim 9 (depends on 7)

The system of claim 7, wherein the second server and the third server are different.

### Claim 10 (depends on 9)

The system of claim 9, wherein the first server, second server, and third server are different.

### Claim 11 (depends on 9)

The system of claim 9, wherein the first packetized digital video data is packaged according to a first packaging format and the second packetized digital video data is packaged according to a second packaging format, and the first and second packaging formats are different, and wherein the client device is further configured to play the second packetized digital video data immediately following completion of playing the first packetized digital video data.

### Claim 12 (depends on 9)

The system of claim 9, wherein the first packetized digital video data is encoded according to a first encoding format and the second packetized digital video data is encoded according to a second encoding format, and the first and second encoding formats are different.

### Claim 13 (depends on 7)

The system of claim 7, wherein the first packetized digital video data corresponds to a live stream.
