Amazon Technologies, Inc.

Eric Woodruff

Ryan Paul Hegar

Varad Joshi

Khawaja Salman Shams

Kristopher Kosmatka

Rebecca Claire Weiss

Trevor Babcock

Gustaf Carl Hegnell

Glenn LaMotte Diviney

Akshat Aranya

Darin J Klaas

Akhil Ramachandran

Brian Enigma

Thomas Jason Dytko

Norman T Bright

Erik Jason Johnson

Ai Luo

William Kennemer

John Bach

Addie Marie Beseda

Rodney Monsees

Gadi Yechiel Golan

Harsh Ramachandran

Luke Richard Pierce

Yelena Tanaomi

Mohamed Anouar Hadj Taieb

Joseph Yuhas

Sabar Mourad Souag

David William Cardwell

Karthik Bangalore Shamsunder

A first network namespace and second network namespace are created in a computing instance of a computer system, with the second network namespace being accessible to the first network namespace via an interface. A service is executed in the first namespace and an encoder is executed in the second namespace, with the encoder transforming media from one format to another format. Communication from the encoder to the service is regulated via the interface.

Video encoder network sandboxing

A video packaging and origination service can include one or more encoder components that receive content for encoding and transmitting to requesting entities. During the operation of the encoder components, a management service associated with the video packaging and origination service can receive information related to updates or modifications to the encoder components. Responsive to the information, the management service can instantiate and configure an updated encoder. Once the updated encoder component is instantiated and configured, both the updated and target encoder components receive content for streaming, encode content and generating encoding content. Additionally, the updated encoder component can initiate a notification to the target encoder component that a handover will be occurring and begin a negotiation process identifying a handover event. Based on the negotiated handover event, the target encoder component can illustratively cease operation upon evaluation and detection of the handover event.

Managing encoder updates

Systems and methods in provide approaches for channel fitting to determine a particular number of resources, such as cores, that may be used for one or more processing jobs for a particular input channel. A given channel may be evaluated to determine performance affecting parameters and those parameters may be evaluated against previously known hardware configurations or against a historical heuristic dataset. A configuration for the channel may be selected where particular cores of a set of resources are assigned to the channel to perform one or more operations, such as transcoding operations. As a result, empirically determined or historical data may be used to efficiently allocate resources for different transcoding operations to provide both predictable performance and high utilization.

Channel fitting for media processing

A content distribution environment enables acquisition of a video feed in a first format, conversion into a second format, and transmission to a cloud service using on-premises equipment managed and operated by the content provider. A gateway or bridge may facilitate operation with one or more managed services, such as a content distribution service, that provides a reliable way to ingest a video stream from a source, replicate the video stream to one or more destinations, and permit sharing of video streams to affiliates and partners. The on-premises equipment may execute a software package to provide end-to-end operations that leverage operations of a cloud service while executing on content provider owned or managed hardware.

Media gateway for transportation of media content

Systems and methods perform a failover, handoff type of process for machines actively encoding and transcoding media content or other data, including live video. Based on dynamic analyses, including detection of needed updates due to security anomalies and encoder state evaluations, the encoder instance initially receiving a stream can restart following handoff to another encoder instance. System downtime is minimized through actions such as initializing the replacement encoder and passively migrating network resources to same, without any explicit coordination or messaging between the two instances.

Network failover for migrating live encoders

Techniques for using statmuxes are described. In some examples, each statmux is to perform activities such as receiving complexity and quality data per frame per encoder of each channel of a first zone of a provider network, wherein a first channel of the first zone is associated with a first source and a second channel of the first zone is associated with a second source; receiving complexity and quality data per frame per encoder of each channel of a second zone of the provider network, wherein a first channel of the second zone is associated with the first source and a second channel of the second zone is associated with the second source; determining, based on the received complexity data and quality data, which channels are to be active, wherein an active channel's content data is to be included in the multi program transport stream output; providing an indication to the channels of which channels have been determined to be active based upon the encoder determination; receiving content data from the encoders of the active channels; and generating a multi program transport stream output from the received content data.

Architecture and algorithms for high availability statmuxing

An encoding system that distributes a live stream to end user devices is provided herein. The encoding system automatically detects failed components and implements a failover action to replace the failed component with a backup component in a manner that reduces live stream interruptions. For example, the encoding system can include a network interface that is coupled to an encoder allocated to a live stream. Instead of providing a contribution encoder that transmits the live stream with a location of the allocated encoder, the encoding system can provide the contribution encoder with a location of the network interface. Thus, the contribution encoder can transmit the live stream to the network interface. The network interface can then forward the live stream to the allocated encoder. If the allocated encoder fails, then the network interface can forward the live stream to a backup encoder.

Live media encoding failover system

A user can configure a real-time video encoding job using a profile including parameterized fields that enable a user to specify only the attributes that are specific to the video channel, as may include options for the audio and video codecs, stream packaging, input sources, video pipeline processors, and the like. When creating the profile, a user can define a set of parameters and their respective default values. Once the parameters are defined, any attribute in the profile may include one or more parameters as substrings using specific markup syntax. When persisting the data, a set of parameter records can be associated with the profile. Later, when a channel is to be created using the profile, any parameterized attribute in the profile may be overridden with a value specific to that channel as determined using the relevant set of parameter records.

Parameterizable encoding profiles

Growing community of inventors

Beaverton, OR, United States of America

Eric Woodruff