Amazon Technologies, Inc.

Benjamin Aldouby Schwartz

Jason LaPier

Jeremiah M Dunham

Justin Abrahms

Andrew Tunall

Khawaja Salman Shams

Joseph Edwin Johnson, Jr

Nathan Eugene Masters

Shiblee Imtiaz Hasan

Ryan Farris

Kristopher Kosmatka

Saurav Sengupta

Benjamin Black

Akhil Ramachandran

Dustin Encelewski

Dumanshu Goyal

Meera Jindal

Michael Vidyadhar Kale

Mark DeSpain

Serj Kazar

Ahmet Gurcan

Abilash Ravikumar

Michael Brian Stoops

Swaminathan Sivasubramanian

David Craig Yanacek

Andrew Kent Warfield

David Alexander Dunlap

Khai Tran

Usman Ahmed Shami

Prashant Pandey

Mathew Persons Jack

Saurangshu Pandey

Matei Mitaru Berceanu

Colleen Marie Toth

Mohamed Mostafa Ibrahim Elshenawy

JaeHa Oh

Manjeet Chayel Mohinder Singh

Dylan Kyle Abraham

Jimmy George

Matei Berceanu Mitaru

Jesse Robert Hepburn

Marcin Manek

Prakash Bhasker

Jason Lapier

A time code to byte conversion system is provided herein that maps time codes to byte ranges such that a user device can retrieve a portion of, but not all of, a media file by specifying a time range. For example, the time code to byte conversion system can play a media file and identify the byte at which each time code begins. The time code to byte conversion system can then store the byte to time code mapping in an index accessible by a media retrieval server. A user device can then provide a time range to the media retrieval server, the media retrieval server can query the index to identify the range of bytes that corresponds to the provided time range, and then the media retrieval server can retrieve the identified range of bytes from a media database for transmission to the user device.

Time code to byte indexer for partial object retrieval

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.

Media storage

An asset storage server is provided herein that assigns related files to an asset name and assigns permissions to the asset name such that related files with unrelated names can be assigned permissions independent of the file naming convention and without requiring a user to individually set the permissions of each file. The asset storage server may also generate modified versions of original file names and index a distributed object store based on the modified versions such that related files with related names are not listed in the same partition of the distributed object store. Indexing the distributed object store based on the modified versions of the original file names may reduce data retrieval latency.

Media asset access control system

A set of data units associated with a data object is obtained, such that respective instances of the data object can be reconstructed from respective subsets of the set. Corresponding to a request for the data object, a first subset of the set is identified. The first subset meets a uniqueness criterion with respect to other subsets of the set that are used to respond to other requests for the data object. An instance of the data object is reconstructed from the first subset.

Space-efficient techniques for generating unique instances of data objects

A media storage service may store a plurality of copies of a same media recording in cloud DVR, one copy specific to one of a plurality of clients. The client may interact directly with the media storage service based on path-based indexing techniques for playback of the media recording. The client may send a request, including a path of a manifest file associated with the copy specific to the client, to the media storage service. The manifest file may include information indicating respective paths of one or more segments of the copy. The media storage service may identify and return the manifest file to the client. The media storage service may further receive requests from the client to access the segments of the copy. The requests may include the respective paths, based on which the media storage service may retrieve the segments for the client to play.

Using path-based indexing to access media recordings stored in a media storage service

This disclosure describes techniques for distributed storage of files that represent video content across different storage tiers to reduce the amount of computing resources used to store the files, while maintaining a low latency when responding to user requests to stream the video content. Video streaming services support the streaming of video content at different resolutions to support various user devices and/or user preferences. To provide streaming of a particular video content item at different resolutions, the video streaming services may store multiple files that represent the video content item for the different resolutions and stream at different bitrates to user devices. The techniques described herein include storing files configured to stream a video content item at different bitrates (and for different display resolutions) in a tiered storage structure to reduce the amount of computing resources taken to store the files.

Distributed storage of files for video content

Transactional log data for a distributed database may be archived by a number of computing nodes scalable to a specified concurrency parameter. A log record may be mapped to a computing node for performance of an archiving operation. The log record may be stored with information indicative of a position, in a hierarchy of shards, of the shard from which the log record originated. The log record may be replayed in an order, relative to other records, that is based on the shard's position in the shard hierarchy. The log record may be replayed on a shard identified based on a time-invariant and idempotent hash function.

Archiving and restoration of distributed database log records

A media storage service may maintain an asset including information to indicate a specific media content and a specific number of replicas to be stored by the media storage service for the specific media content. The media storage service may receive content recording-related requests from a recording manager to define or update the specific number for the specific media content. The media storage service may receive one or more segments specific to the media content from an encoder. The media storage service may create and store the specific number of replicas, as indicated in the asset, for the media content.

Asset-level management of media recording in cloud DVR systems

A content streaming system and methodology for facilitating the management of content streaming. A content delivery service provides streaming content that is organized according to a set of encoded content chunks. An encoding component generates encoded chunk data for transmission to requestors. A content delivery management component can determine configuration information that indicates the size of the content chunks. The content delivery management component can then receive encoded data but will not replicate and propagate the received encoded data to distribution endpoints of the content delivery service until complete content chunks are ready for transmission. A video playback application processes the set of encoded content chunks to dynamically form a content segment for live video streaming.

Streaming chunked media segments

A database client may implement scalable tracking for database updates according to a secondary index. As update requests are generated and sent to a database, tracking attributes may be included in the update requests in order to be inserted into the database with respect to a portion of the database for which the requested update is performed. Tracking attributes may include a sequence number which may be used to determine an order in which the updates are performed at the database. Tracking attributes may also include a bucket identifier, which may categorize or label the portion of data updated as part of an update. These tracking attributes may be replicated to a secondary index maintained for the database. Queries to the secondary index based on the tracking attributes may identify updates performed to the database. Notifications of the identified updates may then be provided.

Scalable tracking for database udpates according to a secondary index

System for optimizing access to an indexed database

One or more computing nodes located in a first region may maintain a first collection of data items. A second set of one or more computing nodes in a second region may maintain a collection of data items that is at least a partial replica of the first collection. Notifications of changes to the first collection may be transmitted, via a broadcast communications channel, to a replication module, which may be included in a client application. The replication module may transmit requests to update the second collection of data based on changes to the first collection. Conflicts may be resolved through a last-write wins policy.

Cross-region replication architecture

Growing community of inventors

Portland, OR, United States of America

Benjamin Aldouby Schwartz