US 12,764,175 B2Granted

Systems and methods for encoding and sharing content between devices

AssigneeDivx, LLC

InventorsSong Cen, Reza Emdad

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods for sharing content between devices are disclosed. To request a shared piece of media content, a playback device generates and sends a request to content server. The playback device includes information in the request that indicates the playback capabilities of the device. The content server receives the request and determines the playback capabilities of the playback device from the information in the request. The content server then determines the assets that may be used by the playback device to obtain the media content and generates a top level index file for the playback device that includes information about the determined assets. The top level index file is then sent to the playback device that may then use the top level index file to obtain the media content using the indicated assets.

Claims20

Dependent claims

A method for transcoding encoded video content captured by a first playback device into one or more different encodings and generating an index file describing the one or more different encodings for use in playback of the video content by a second playback device, the method comprising:

receiving, at a playback server system, a content file from a first playback device, the content file comprising encoded video content that is encoded using a first encoding format;
obtaining, by a transcode management server system, machine load information associated with transcoding of content on a set of one or more transcode servers;
generating, by the transcode management server system, a schedule for transcoding the received content file using the set of one or more transcode servers based on the obtained machine load information;
transcoding, by the set of one or more transcode servers, the content file into one or more different encodings, wherein the set of one or more transcode servers perform the transcoding based on the generated schedule;
uploading, by the set of one or more transcode servers, the transcoded one or more different encodings of the content file to a content database;
generating, by the playback server system, an index file in response to a request from a second playback device to play back the video content, where:
the generated index file contains information indicating a location for one or more container files, and
each of the one or more container files contains at least a portion of one of the one or more different encodings of the content file;
and
providing, by the playback server system, the index file to the second playback device;
and
providing, by a storage server system, at least one of the one or more container files to the second playback device in response to requests generated by the second playback device using the index file.

9 more elements

A playback system that transcodes encoded video content captured by a first playback device into one or more different encodings, and generating an index file describing the one or more different encodings for use in playback of the video content by a second playback device, the system comprising:

a playback server system, the playback server system comprising:
a set of one or more processors;
a memory readable by the set of one or more processors;
and
an encoding application stored in the memory that configures the set of one or more processors to:
receive a content file from a first playback device, the content file comprising encoded video content that is encoded using a first encoding format;
generate an index file in response to a request from a second playback device to playback the video content, where:
the generated index file contains information indicating a location for one or more container files, and
each of the one or more container files contains at least a portion of one of the one or more different encodings of the content file;
and
provide the index file to the second playback device;
and
provide at least one of the container files to the second playback device in response to requests generated by the second playback device using the index file;
a transcode management server system, the transcode management server system comprising:
a set of one or more processors;
a memory readable by the set of one or more processors;
and
a transcode management application stored in the memory that configures the set of one or more processors to:
obtain machine load information associated with transcoding of content on a set of one or more transcode servers;
and
generate a schedule for transcoding of the received content file using the set of one or more transcode servers based on the obtained machine load information;
and
a set of one or more transcode servers, the set of one or more transcode servers is configured to:
transcode the content file into one or more different encodings, wherein the set of one or more transcode servers perform the transcoding based on the generated schedule;
and
upload the transcoded one or more different encodings of the content file to a content database.

23 more elements

Dependencies are inferred from the claim text.

Facts

Application: 19/030,677Filed 17 Jan 2025 · continuation
Priority: 6 Jan 2015
Published: US 2025/0175513 A129 May 2025
Granted: 13 Oct 2026
Term ends: Not estimatedThe source records don’t support an estimate.

Classification13 codes

H04L 65/612
For supporting one-way streaming services, e.g. Internet radio: for unicast
H04L 63/08
Network architectures or network communication protocols for network security: for authentication of entities
H04L 63/102
For controlling access to devices or network resources: entity profiles
H04L 63/107
For controlling access to devices or network resources: wherein the security policies are location-dependent, e.g. entities privileges depend on…

Family

Application62/100,299Us provisional application · filed 6 Jan 2015
Application14/989,551Parent of this continuation · filed 6 Jan 2016
Application16/292,036Parent of this continuation · filed 4 Mar 2019
US 10,225,298 B2Parent of this continuation · filed 5 Mar 2019
Application16/847,363Parent of this continuation · filed 13 Apr 2020
US 10,623,458 B2Parent of this continuation · filed 14 Apr 2020
Application17/804,501Parent of this continuation · filed 27 May 2022
US 11,349,892 B2Parent of this continuation · filed 31 May 2022
Application18/357,498Parent of this continuation · filed 24 Jul 2023
US 11,711,410 B2Parent of this continuation · filed 25 Jul 2023
US 2025/0175513 A1Pre-grant publication · published 29 May 2025
US 12,250,257 B2Parent of this continuation
US 10,091,262 B2Related patent
US 2016/0197971 A1Published application
US 2019/0268394 A1Published application
US 2020/0244714 A1Published application
US 2022/0368749 A1Published application
US 2024/0205281 A1Published application
US 12,764,175 B2This patent

From the US filing history. Foreign family members aren’t listed.