Media storage

• US 10,701,377 B2
• Filed: 09/14/2016
• Issued: 06/30/2020
• Est. Priority Date: 09/14/2016
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Dunham, Jeremiah M., Tunall, Andrew, Black, Benjamin, Kosmatka, Kristopher, Schwartz, Benjamin Aldouby, LaPier, Jason, Abrahms, Justin
• Primary Examiner(s): Cattungal, Rowina J
• Application Number:
  US15/265,513
• Publication Number:
  US 20180077420A1
• Time in Patent Office: 1,385 Days
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: G06F 16/70 of video data
• CPC Class Codes: G06F 16/71 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/73 Querying
• CPC Class Codes: G06F 16/738 Presentation of query results
• CPC Class Codes: G06F 16/7867 using information manually generated, e.g. tags, keywords, comments, title and artist information, manually generated time, location and usage information, user ratings
• CPC Class Codes: H04N 19/37 with arrangements for assigning different transmission priorities to video input data or to video coded data
• CPC Class Codes: 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

Abstract

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.

Claims

1. A computer-implemented method, comprising:

receiving, to a storage system including a first type of storage, an asset including a mezzanine file and one or more related files;

extracting metadata from the asset;

associating the metadata with the mezzanine file and with the one or more related files as stored in the storage system;

determining a workflow to be applied for the asset, the workflow being associated with the mezzanine file, the one or more related files, and any subsequently generated files associated with the asset in the storage system, wherein the workflow comprises at least a transcoding operation comprising transcoding the mezzanine file into one or more transcoded files of formats specified by the workflow;

detecting an event corresponding to completion of the transcoding operation;

moving the mezzanine file to a second type of storage based on the event, the second type of storage including lower accessibility than the first type of storage; and

associating the metadata with the one or more transcoded files.

2. The computer-implemented method of claim 1, further comprising:

creating, for the asset, at least one hierarchical primitive relating to the mezzanine file and the one or more related files; and

associating the workflow and the metadata with the at least one hierarchical primitive, wherein the workflow and the metadata are automatically associated with the mezzanine file, the one or more related files, and the subsequently generated files and wherein actions of the workflow can be applied according to the at least one hierarchical primitive.

3. The computer-implemented method of claim 2, further comprising:

providing one or more tools enabling a user to interact with the asset according to the at least one hierarchical primitive, wherein an action performed in response to user input through the one or more tools is performed at an asset level or a sub-asset 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 mezzanine file; and

triggering the moving of the mezzanine file to the second type of storage in response to the event, the second type of storage specified as part of the at least one of a rule, a policy, or a lifecycle.

5. The computer-implemented method of claim 1, further comprising causing a workflow to be performed in response to a user call to an application programming interface (API) or an action triggered by a rules engine managing the workflow on behalf of the asset.

6. The computer-implemented method of claim 1, further comprising

storing the metadata associated with the mezzanine file to the second type of storage and storing the one or more transcoded files to the first type of storage.

7. The computer-implemented method of claim 1, further comprising:

determining a filename for the media asset;

segmenting the 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.

8. The computer-implemented method of claim 1, further comprising:

indexing the mezzanine file based at least in part upon time code information extracted from the mezzanine file; and

providing an interface enabling querying of the mezzanine file based at least in part upon the time code information.

9. The computer-implemented method of claim 1, further comprising:

receiving the mezzanine file to a proxy service for the storage system, the proxy service having a dedicated address for receiving the mezzanine file.

10. The computer-implemented method of claim 1, wherein the metadata includes at least one of a title, format, bitrate, or file size for the 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, to a storage system, an asset including a mezzanine file and one or more related files;

extract metadata from the asset;

store at least the mezzanine file to the first type of storage;

associate the metadata with the mezzanine file and with the one or more related files in the storage system;

obtain a workflow to be applied for the asset, the workflow being associated with the mezzanine file, the one or more related files, and any subsequently generated files associated with the asset in the storage system, wherein the workflow comprises at least a transcoding operation comprising transcoding the mezzanine file into one or more transcoded files with formats specified by the workflow;

detect an event corresponding to completion of the transcoding operation;

move the mezzanine file to a second type of storage based on the event; and

associate the metadata with the one or more transcoded files.

12. The storage system of claim 11, wherein the instructions when executed further cause the system to:

create, for the asset, at least one hierarchical primitive relating to the mezzanine file, the one or more related files, and the subsequently generated files; and

associate the workflow and the metadata with the at least one hierarchical primitive, wherein the workflow and the metadata are automatically associated with the mezzanine file, the one or more related files, and the subsequently generated files and actions of the workflow 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 asset;

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 mezzanine file; and

causing the advertisement to be displayed during playback of the transcoded file.

14. The storage system of claim 11, wherein the instructions when executed further cause the system to:

store the metadata associated with the mezzanine file to the second type of storage and store the one or more transcoded files to the first 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 asset;

segment the 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, to a storage system, an asset including a mezzanine file and one or more related files;

extract metadata from the asset;

store at least the mezzanine file to a first type of storage of the storage system;

associate the metadata with the mezzanine file and with the one or more related files in the storage system;

obtain a workflow to be applied for the asset, the workflow being associated with the mezzanine file, the one or more related files, and any subsequently generated files associated with the asset in the storage system, wherein the workflow comprises at least a transcoding operation comprising transcoding the mezzanine file into one or more transcoded files with formats specified by the workflow;

detect an event corresponding to completion of the transcoding operation

move the mezzanine file to a second type of storage based on the event, the second type of storage including lower accessibility than the first type of storage; and

associate the metadata with the one or more transcoded files.

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, for the asset, at least one hierarchical primitive relating to the mezzanine file, the one or more related files, and the subsequently generated files; and

associate the workflow and the metadata with the at least one hierarchical primitive, wherein the workflow and the metadata are automatically associated with the mezzanine file, the one or more related files, and the subsequently generated files and actions of the workflow can be applied according to the at least one hierarchical primitive.

18. 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:

receive a set of advertisements to be displayed with the asset;

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 mezzanine file; and

causing the advertisement to be displayed during playback of the transcoded file.

19. 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:

store the metadata associated with the mezzanine file to the second type of storage and store the one or more transcoded files to the first type of storage.

20. 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:

determine a filename for the media asset;

segment the 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.