Prioritized transcoding of media content
US-10191954-B1 · Jan 29, 2019 · US
US11785232B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11785232-B2 |
| Application number | US-202218083150-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 16, 2022 |
| Priority date | Sep 14, 2016 |
| Publication date | Oct 10, 2023 |
| Grant date | Oct 10, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A user of a storage system can upload files for a media asset, which can include a high quality media file and various related files. As part of the upload process, the storage system can extract metadata that describes the media asset. The user can specify one or more lifecycle policies to be applied for storage of the asset, and a rules engine can ensure the application of the one or more policies. The rules engine can also enable the use of simple media processing workflows. A filename hashing approach can be used to ensure that the segments and files for the asset are stored in a relatively random and even distribution across the partitions of the storage system. As part of the lifecycle for the asset, the high quality media file can be moved to less expensive storage once transcoding of the asset or another such action occurs.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method, comprising: receiving, by a storage system, a media file and at least one associated mezzanine file; storing at least the at least one associated mezzanine file to a high-accessibility storage type; transcoding the at least one associated mezzanine file into at least one transcoded file based, at least in part, upon one or more settings specified for the transcoding; storing the at least one transcoded file to the high-accessibility storage type; and after completion of the transcoding, moving the at least one associated mezzanine file to a reduced-accessibility storage type that is less operationally expensive than the high-accessibility storage type. 2. The computer-implemented method of claim 1 , further comprising: creating at least one hierarchical primitive relating to the at least one associated mezzanine file; associating metadata extracted from the media file with the at least one associated mezzanine file; and associating the metadata with the at least one hierarchical primitive, wherein the metadata is automatically associated with the at least one associated mezzanine file and subsequently generated files, and wherein actions of a workflow to be applied to the media file can be applied according to the at least one hierarchical primitive. 3. The computer-implemented method of claim 2 , further comprising: providing at least one tool for interaction with the media file according to the at least one hierarchical primitive, wherein an action performed in response to input via the at least one tool is performed at a file level of the hierarchical primitive. 4. The computer-implemented method of claim 2 , further comprising: determining at least one of a rule, a policy, or a lifecycle corresponding to the at least one associated mezzanine file; and triggering the moving of the at least one associated mezzanine file in response to the completion of the transcoding. 5. The computer-implemented method of claim 2 , wherein the metadata includes at least one of a title, format, bitrate, or file size for the at least one associated mezzanine file. 6. The computer-implemented method of claim 1 , further comprising causing a workflow to be performed on the media file in response to a call to an application programming interface (API) or an action triggered by a rules engine managing the workflow on behalf of the media file. 7. The computer-implemented method of claim 1 , further comprising: storing metadata associated with the at least one associated mezzanine file to the high-accessibility storage type. 8. The computer-implemented method of claim 1 , further comprising: determining a filename for the media file; segmenting the at least one associated mezzanine file into a sequence of segments; determining a variation of the filename for each segment of the sequence; and generating a unique hash code for each segment of the sequence using a hashing algorithm that considers an entirety of each variation. 9. The computer-implemented method of claim 1 , further comprising: indexing the at least one associated mezzanine file based at least in part upon time code information extracted from the at least one associated mezzanine file; and providing an interface enabling querying of the at least one associated mezzanine file based at least in part upon the time code information. 10. The computer-implemented method of claim 1 , further comprising: receiving the at least one associated mezzanine file to a proxy service for the storage system, the proxy service having a dedicated address for receiving the at least one associated mezzanine file. 11. A storage system, comprising: at least one processor; a first type of storage; a second type of storage including lower accessibility than the first type of storage; and memory including instructions that, when executed by the at least one processor, cause the storage system to: receive a media file and at least one associated mezzanine file; store at least the at least one associated mezzanine file in the first type of storage, transcode the at least one associated mezzanine file into at least one transcoded file based, at least in part, upon one or more settings specified for the transcoding; store the at least one transcoded file to the first type of storage; and after completion of the transcoding, move the at least one associated mezzanine file to the second type of storage, the second type of storage being less operationally expensive than the first type of storage. 12. The storage system of claim 11 , wherein the instructions when executed further cause the system to: create at least one hierarchical primitive relating to the at least one associated mezzanine file; associate metadata extracted from the media file with the at least one associated mezzanine file; and associate the metadata with the at least one hierarchical primitive, wherein the metadata is automatically associated with the at least one associated mezzanine file, and wherein actions of a workflow to be applied to the media file can be applied according to the at least one hierarchical primitive. 13. The storage system of claim 11 , wherein the instructions when executed further cause the system to: receive a set of advertisements to be displayed with the media file; causing the advertisements to be modified to match at least one of a video quality or an audio quality of a transcoded file generated using the at least one associated mezzanine file; and causing the advertisement to be displayed during playback of the transcoded file generated using the at least one associated mezzanine file. 14. The storage system of claim 11 , wherein the instructions when executed further cause the system to: store metadata associated with the at least one associated mezzanine file using the second type of storage. 15. The storage system of claim 11 , wherein the instructions when executed further cause the system to: determine a filename for the media file; segment the at least one associated mezzanine file into a sequence of segments; determine a variation of the filename for each segment of the sequence; and generate a unique hash code for each segment of the sequence using a hashing algorithm that considers an entirety of each variation. 16. A non-transitory computer readable storage medium storing instructions that, when executed by at least one processor of a computing device, cause the computing device to: receive, by a storage system, a media file and at least one associated mezzanine file; store at least the at least one associated mezzanine file to a first type of storage; transcode the at least one associated mezzanine file into at least one transcoded file based, at least in part, upon one or more settings specified for the transcoding; store the at least one transcoded file to the first type of storage; and after completion of the transcoding, move the at least one associated mezzanine file to a second type of storage that is less operationally expensive than the first type of storage. 17. The non-transitory computer readable storage medium of claim 16 , wherein the instructions, when executed by the at least one processor, further cause the computing device to: create at least one hierarchical primitive relating to the at least one associated mezzanine file; associate metadata extracted from the media file with the at least one associated mezzanine file; and associate the metadata with the at least one hierarchical primitive, wherein the metadata
with arrangements for assigning different transmission priorities to video input data or to video coded data · CPC title
Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title
of video data · CPC title
Indexing; Data structures therefor; Storage structures · CPC title
Querying · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.