Storage and distribution of video data for video coding

Abstract

A device for processing video data may be configured to receive a configuration record for decoding a bitstream of the video data, wherein the configuration record for the bitstream includes a toolset indication syntax element that includes information identifying a tool from a set of video decoding tools that is needed to decode the bitstream associated with the configuration record; determine whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; and, based on the decision to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

Description

[Technical field]

[0001]

[0001] This application claims priority to U.S. Application No. 17 / 143,611, filed January 7, 2021, which claims the benefit of U.S. Provisional Application No. 62 / 958,561, filed January 8, 2020, the entire contents of which are incorporated herein by reference.

[0002] FIELD OF THE DISCLOSURE

[0002] This disclosure relates to the storage and delivery of video data. [Background technology]

[0003] Digital video capabilities may be incorporated into a wide range of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), laptop or desktop computers, tablet computers, e-book readers, digital cameras, digital recording devices, digital media players, video gaming devices, video game consoles, cellular or satellite radio telephones, so-called "smartphones," video teleconferencing devices, video streaming devices, and the like. Digital video devices implement video coding techniques, such as those described in standards defined by MPEG-2, MPEG-4, ITU-T H.263, ITU-T H.264 / MPEG-4, Part 10, Advanced Video Coding (AVC), ITU-T H.265 / High Efficiency Video Coding (HEVC), and extensions to such standards. By implementing such video coding techniques, video devices may more efficiently transmit, receive, encode, decode, and / or store digital video information.

[0004]

[0004] Video coding techniques include spatial (intra-picture) prediction and / or temporal (inter-picture) prediction to reduce or remove redundancy inherent in video sequences. In block-based video coding, a video slice (e.g., a video picture or a portion of a video picture) may be partitioned into video blocks, which may also be referred to as coding tree units (CTUs), coding units (CUs) and / or coding nodes. Video blocks in an intra-coded (I) slice of a picture are encoded using spatial prediction with respect to reference samples in neighboring blocks in the same picture. Video blocks in an inter-coded (P or B) slice of a picture may use spatial prediction with respect to reference samples in neighboring blocks in the same picture or temporal prediction with respect to reference samples in other reference pictures. A picture may be referred to as a frame, and a reference picture may be referred to as a reference frame. Summary of the Invention

[0005]

[0005] Generally, this disclosure describes techniques for storage and distribution of bitstreams that conform to a video coding standard based on a file format. This disclosure also describes examples of media format profiles for the video coding standard and distribution using streaming techniques. As an example, the video coding standard is the essential video coding (EVC) standard, and the file format is the International Organization for Standardization's base media file format. The International Organization for Standardization's base media file format is called ISOBMFF. An example of a media format profile is the Common Media Application Format (CMAF) profile, and an example of a streaming technique is Dynamic Adaptive Streaming over HTTP (DASH). This disclosure may also describe encryption requirements and codec parameters to be used with Multipurpose Internet Mail Extensions (MIME) types. Although described with respect to EVC, ISOBMFF, CMAF, and DASH, the example techniques should not be considered as so limited.

[0006]

[0006] According to one example of the present disclosure, a method for processing a video stream or video file includes receiving a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record, determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, and based on the decision to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding.

[0007]

[0007] According to another example of the present disclosure, a device for processing a video stream includes a memory configured to store the video stream, and one or more processors implemented in a circuit and coupled to the memory and configured to receive a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record, determine whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, and based on the decision to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0008]

[0008] According to another example of the present disclosure, a computer-readable storage medium stores instructions that, when executed by one or more processors, cause the one or more processors to receive a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element that includes information that identifies, from a set of video decoding tools, a tool needed to decode the bitstream associated with the configuration record, determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, and based on the decision to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0009]

[0009] According to another example of the present disclosure, an apparatus for processing a video stream or video file includes means for receiving a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record, means for determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, means for retrieving the bitstream based on a decision to retrieve the bitstream associated with the configuration record, and means for outputting the bitstream to a video decoder for decoding.

[0010]

[0010] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will become apparent from the description, drawings, and claims. [Brief description of the drawings]

[0011] [Figure 1]

[0011] A block diagram illustrating an example video encoding and decoding system in which the techniques of this disclosure may be implemented. [Figure 2A]

[0012] 1 is a conceptual diagram illustrating an exemplary Quad Tree Binary Tree (QTBT) structure. [Figure 2B] A conceptual diagram showing a corresponding coding tree unit (CTU). [Diagram 3]

[0013] 1 is a block diagram illustrating an example video encoder that may implement the techniques of this disclosure. [Figure 4]

[0014] 1 is a block diagram illustrating an example video decoder that may implement the techniques of this disclosure. [Diagram 5]

[0015] 1 is a conceptual diagram illustrating an example structure of a file, in accordance with one or more techniques of this disclosure. [Figure 6]

[0016] FIG. 1 is a conceptual diagram illustrating elements of exemplary multimedia content. [Figure 7]

[0017] 1 is a block diagram showing elements of an exemplary video file. [Figure 8]

[0018] 1 is a flowchart illustrating an example method for processing video data in accordance with techniques of this disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012]

[0019] The Essential Video Coding (EVC) standard developed by ISO / IEC JTC1 / SC29 / WG11 (MPEG) provides an efficient, low-complexity video coding solution. EVC elementary streams are structured as Network Abstraction Layer (NAL) units. Storage of NAL units in the ISO Base Media File Format (ISOBMFF) follows similar principles as other NAL structured video formats, such as the High Efficiency Video Coding (HEVC) and / or Versatile Video Coding (VVC) standards.

[0013]

[0020] The storage of an EVC elementary stream can be subdivided into two parts: static information that is used globally in the elementary stream, and dynamic information that can change on a sample-by-sample basis. The sequence parameter set (SPS) and picture parameter set (PPS) may be part of the information that changes rarely and may be considered static. A set of flags may be used to indicate if a parameter set is expected to change in the stream. In such cases, a sample grouping is defined that indicates the samples for which the parameter set changes.

[0014]

[0021] Adaptation Parameter Set (APS) may be dynamic information that may change on a sample-by-sample basis. APS is used to carry Adaptive Loop Filter (ALF) information. The presence of ALF is signaled through a flag, and samples carrying APS information may belong to the same sample group.

[0015]

[0022] A box may refer to a basic syntax structure in ISOBMFF, including a four-character coded box type, the number of bytes in the box, and a payload. ISOBMFF files contain a sequence of boxes, which may contain other boxes. A movie box ("moov") contains metadata for the continuous media streams present in the file, each represented as a track in the file.

[0016]

[0023] Metadata for a track may be enclosed in a track box ("trak"), while the media content of a track may be either enclosed in a media data box ("mdat") or directly in another file. The media content for a track includes a sequence of samples, such as audio or video access units. An access unit is generally a unit of data that contains coded media (e.g., picture) data for a common time instance. A sample is an access unit defined by a particular specification, such as the video coding specifications described herein. A sample entry may provide a description of the corresponding sample.

[0017]

[0024] The ISOBMFF defines the following types of tracks: media tracks, which contain elementary media streams; hint tracks, which either contain media transmission instructions or represent the received packet stream; and timed metadata tracks, which comprise time-synchronized metadata.

[0018]

[0025] This disclosure describes a configuration record for a bitstream of video data that includes a toolset-indicating syntax element that includes information identifying tools required to decode the bitstream associated with the configuration record. This disclosure also describes techniques for including a multipurpose internet mail extensions (MIME) type parameter in an HTTP transmission that includes, for example, a key value pair. The key may indicate that a MIME type identifies a video decoding tool, and the value may identify the tool required to decode the bitstream. In general, a tool may be considered required if the tool is enabled in at least one parameter set for a media stream. By using such toolset-indicating syntax elements and MIME types, the techniques of this disclosure may advantageously enable a video processing device to determine whether a video decoder of the video processing device can decode a file without having to parse large portions of the file.

[0019]

[0026] 1 is a block diagram illustrating an example video encoding and decoding system 100 that may implement the techniques of this disclosure. The techniques of this disclosure are generally directed to coding (encoding and / or decoding) video data. Generally, video data includes any data for processing video. Thus, video data may include raw uncoded video, coded video, decoded (e.g., reconstructed) video, and video metadata, such as signaling data.

[0020]

[0027] 1, system 100 includes a source device 102 that provides encoded video data to be decoded and displayed by a destination device 116, in this example. In particular, source device 102 provides the video data to destination device 116 via a computer-readable medium 110. Source device 102 and destination device 116 may comprise any of a wide range of devices, including desktop computers, notebook (i.e., laptop) computers, tablet computers, set-top boxes, telephone handsets such as smartphones, televisions, cameras, display devices, digital media players, video gaming consoles, video streaming devices, and the like. In some cases, source device 102 and destination device 116 may be equipped for wireless communication and therefore may be referred to as wireless communication devices.

[0021]

[0028] In the example of FIG. 1, source device 102 includes video source 104, memory 106, video encoder 200, and output interface 108. Destination device 116 includes input interface 122, video decoder 300, memory 120, and display device 118. According to this disclosure, source device 102 and destination device 116 may be configured to apply techniques for storage and distribution of bitstreams that conform to a video coding standard based on a file format (e.g., Essential Video Coding (EVC) elementary bitstream based on ISO Base Media File Format (ISOBMFF)). This disclosure also describes media profiles (e.g., Common Media Application Format (CMAF Media Profile for EVC)), describes distribution using Dynamic Adaptive Streaming over HTTP (DASH), describes encryption requirements, and describes codec parameters to be used with Multipurpose Internet Mail Extensions (MIME) types that may be utilized by video encoder 200 and video decoder 300. Thus, source device 102 represents one example of a client device configured to perform video encoding and transmission, while destination device 116 represents one example of a destination device configured to receive and decode encoded video. In other examples, the source and destination devices may include other components or arrangements. For example, source device 102 may receive video data from an external video source, such as an external camera. Similarly, destination device 116 may interface with an external display device rather than including an integrated display device.

[0022]

[0029] The system 100 shown in FIG. 1 is only an example. In general, any digital video encoding and / or decoding device may perform techniques for storage and distribution of bitstreams conforming to a video coding standard based on a file format (e.g., EVC elementary bitstream based on ISOBMFF). This disclosure also describes media profiles (e.g., CMAF media profile for EVC), distribution using DASH, encryption requirements, and codec parameters to be used with MIME types that may be utilized by the video encoder 200 and the video decoder 300. The source device 102 and the destination device 116 are only examples of coding devices such that the source device 102 generates coded video data for transmission to the destination device 116. This disclosure refers to a "coding" device as a device that performs coding (encoding and / or decoding) of data. Thus, the video encoder 200 and the video decoder 300 represent examples of coding devices, in particular, video encoders and video decoders, respectively. In some examples, source device 102 and destination device 116 may operate substantially symmetrically, such that source device 102 and destination device 116 each include video encoding and decoding components. Thus, system 100 may support one-way or two-way video transmission between source device 102 and destination device 116, for example, video streaming, video playback, video broadcasting, or video telephony.

[0023]

[0030] Generally, video source 104 represents a source of video data (i.e., raw, unencoded video data) and provides a continuous series of pictures (also called “frames”) of the video data to video encoder 200, which encodes the data for the pictures. Video source 104 of source device 102 may include a video capture device, such as a video camera, a video archive containing previously captured raw video, and / or a video feed interface for receiving video from a video content provider. As a further alternative, video source 104 may generate computer graphics-based data or a combination of live, archival, and computer-generated video as the source video. In each case, video encoder 200 encodes the captured, pre-captured, or computer-generated video data. Video encoder 200 may reorder the pictures from a received order (sometimes called a “display order”) into a coding order for coding. Video encoder 200 may generate a bitstream including the encoded video data. The source device 102 may then output the encoded video data via the output interface 108 onto a computer-readable medium 110, for receipt and / or retrieval by, for example, an input interface 122 of the destination device 116.

[0024]

[0031] The memory 106 of the source device 102 and the memory 120 of the destination device 116 represent general purpose memories. In some examples, the memories 106, 120 may store raw video data, e.g., raw video from the video source 104 and raw decoded video data from the video decoder 300. Additionally or alternatively, the memories 106, 120 may store software instructions executable by, e.g., the video encoder 200 and the video decoder 300, respectively. Although the memories 106 and 120 are shown in this example as separate from the video encoder 200 and the video decoder 300, it should be understood that the video encoder 200 and the video decoder 300 may also include internal memories for functionally similar or equivalent purposes. Additionally, the memories 106, 120 may store encoded video data, e.g., the output from the video encoder 200 and the input to the video decoder 300. In some examples, portions of the memory 106, 120 may be allocated as one or more video buffers, for example, to store raw decoded and / or encoded video data.

[0025]

[0032] The computer-readable medium 110 may represent any type of medium or device capable of transporting encoded video data from the source device 102 to the destination device 116. In one example, the computer-readable medium 110 represents a communication medium for enabling the source device 102 to transmit encoded video data directly to the destination device 116 in real time, for example, via a radio frequency network or a computer-based network. In accordance with a communication standard, such as a wireless communication protocol, the output interface 108 may modulate a transmission signal including the encoded video data, and the input interface 122 may demodulate a received transmission signal. The communication medium may comprise any wireless or wired communication medium, such as a radio frequency (RF) spectrum or one or more physical transmission lines. The communication medium may form part of a packet-based network, such as a local area network, a wide area network, or a global network such as the Internet. The communication medium may include routers, switches, base stations, or any other equipment that may be useful to facilitate communication from the source device 102 to the destination device 116.

[0026]

[0033] In some examples, source device 102 may output encoded data from output interface 108 to storage device 112. Similarly, destination device 116 may access encoded data from storage device 112 via input interface 122. Storage device 112 may include any of a variety of distributed or locally accessed data storage media, such as a hard drive, Blu-ray disc, DVD, CD-ROM, flash memory, volatile or non-volatile memory, or any other suitable digital storage medium for storing encoded video data.

[0027]

[0034] In some examples, the source device 102 may output the encoded video data to a file server 114 or another intermediate storage device that may store the encoded video generated by the source device 102. The destination device 116 may access the stored video data from the file server 114 via streaming or download. The file server 114 may be any type of server device capable of storing encoded video data and transmitting the encoded video data to the destination device 116. The file server 114 may represent a web server (e.g., for a website), a file transfer protocol (FTP) server, a content delivery network device, or a network attached storage (NAS) device. The destination device 116 may access the encoded video data from the file server 114 through any standard data connection, including an Internet connection. This may include a wireless channel (e.g., a Wi-Fi connection), a wired connection (e.g., a digital subscriber line (DSL), a cable modem, etc.), or a combination of both, that is suitable for accessing the encoded video data stored in the file server 114. The file server 114 and the input interface 122 may be configured to operate according to a streaming transmission protocol, a download transmission protocol, or a combination thereof.

[0028]

[0035] The output interface 108 and the input interface 122 may represent a wireless transmitter / receiver, a modem, a wired networking component (e.g., an Ethernet card), a wireless communication component operating according to any of the various IEEE 802.11 standards, or other physical components. In examples in which the output interface 108 and the input interface 122 comprise wireless components, the output interface 108 and the input interface 122 may be configured to transfer data, such as encoded video data, according to a cellular communication standard, such as 4G, 4G-LTE (Long Term Evolution), LTE Advanced, 5G, etc. In some examples in which the output interface 108 comprises a wireless transmitter, the output interface 108 and the input interface 122 may be configured to transfer data, such as encoded video data, according to other wireless standards, such as the IEEE 802.11 specification, the IEEE 802.15 specification (e.g., ZigBee), the Bluetooth standard, etc. In some examples, the source device 102 and / or the destination device 116 may include respective system-on-chip (SoC) devices. For example, the source device 102 may include a SoC device for performing functions attributable to the video encoder 200 and / or the output interface 108, and the destination device 116 may include a SoC device for performing functions attributable to the video decoder 300 and / or the input interface 122.

[0029]

[0036] The techniques of this disclosure may be applied to video coding supporting any of a variety of multimedia applications, such as over-the-air television broadcast, cable television transmission, satellite television transmission, Internet streaming video transmission such as Dynamic Adaptive Streaming over HTTP (DASH), digital video encoded on a data storage medium, decoding of digital video stored on a data storage medium, or other applications.

[0030]

[0037] The input interface 122 of the destination device 116 receives the encoded video bitstream from the computer-readable medium 110 (e.g., a communication medium, a storage device 112, a file server 114, etc.). The encoded video bitstream may include signaling information defined by the video encoder 200 that is also used by the video decoder 300, such as syntax elements having values ​​that describe characteristics and / or processing of video blocks or other coded units (e.g., slices, pictures, groups of pictures, sequences, etc.). The display device 118 displays decoded pictures of the decoded video data to a user. The display device 118 may represent any of a variety of display devices, such as a cathode ray tube (CRT), a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display device.

[0031]

[0038] 1, in some examples, the video encoder 200 and the video decoder 300 may each be integrated with an audio encoder and / or an audio decoder and may include an appropriate MUX-DEMUX unit, or other hardware and / or software, to handle multiplexed streams that include both audio and video in a common data stream. Where applicable, the MUX-DEMUX unit may conform to the ITU H.223 multiplexer protocol or other protocols, such as the User Datagram Protocol (UDP).

[0032]

[0039] The video encoder 200 and the video decoder 300 may each be implemented as any of a variety of suitable encoder and / or decoder circuits, or any combination thereof, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic, software, hardware, firmware, etc. When the techniques are implemented partially in software, a device may store instructions for the software on a suitable non-transitory computer-readable medium and execute the instructions in hardware using one or more processors to implement the techniques of this disclosure. Each of the video encoder 200 and the video decoder 300 may be included in one or more encoders or decoders, any of which may be integrated as part of a combined encoder / decoder (CODEC) in the respective device. A device including the video encoder 200 and / or the video decoder 300 may comprise an integrated circuit, a microprocessor, and / or a wireless communication device such as a cellular phone.

[0033]

[0040] Video encoder 200 and video decoder 300 may operate according to other proprietary or industry standards, such as ITU-T H.266, also known as the Joint Exploration Test Model (JEM), or Versatile Video Coding (VVC). A recent draft of the VVC standard is described in Bross et al., "Versatile Video Coding (Draft 7)," Joint Video Experts Team (JVET) of ITU-T SG16 WP3 and ISO / IEC JTC1 / SC29 / WG11, 16th Meeting, Geneva, Switzerland, October 1-11, 2019, JVET-P2001-v14 (hereinafter, "VVC Draft 7"). Video encoder 200 and video decoder 300 may operate according to the EVC standard developed by ISO / IEC JTC1 / SC29 / WG11 (MPEG). However, the techniques of this disclosure are not limited to any particular coding standard.

[0034]

[0041] Generally, the video encoder 200 and the video decoder 300 may perform block-based coding of pictures. The term “block” generally refers to a structure that includes data to be processed (e.g., encoded, decoded, or otherwise used in an encoding and / or decoding process). For example, a block may include a two-dimensional matrix of samples of luminance and / or chrominance data. Generally, the video encoder 200 and the video decoder 300 may code video data represented in a YUV (e.g., Y, Cb, Cr) format. That is, rather than coding red, green, and blue (RGB) data for a sample of a picture, the video encoder 200 and the video decoder 300 may code a luminance component and a chrominance component, where the chrominance component may include both red and blue hues of chrominance components. In some examples, the video encoder 200 converts received RGB format data to a YUV representation prior to encoding, and the video decoder 300 converts the YUV representation to an RGB format. Alternatively, pre-processing and post-processing units (not shown) may perform these conversions.

[0035]

[0042] This disclosure may generally refer to coding (e.g., encoding and decoding) a picture to include processes of encoding or decoding data for a picture. Similarly, this disclosure may refer to coding a block of a picture to include processes of encoding or decoding data for the block, e.g., predictive and / or residual coding. A coded video bitstream generally includes a series of values ​​for syntax elements that represent coding decisions (e.g., coding modes) and partitioning of a picture into blocks. Thus, references to coding a picture or a block should be understood generally as coding values ​​for the syntax elements that form the picture or block.

[0036]

[0043] Various video coding standards define various blocks that may be called coding units (CUs), prediction units (PUs), and transform units (TUs). A video coder (such as video encoder 200) partitions coding tree units (CTUs) into CUs according to a quad-tree structure. That is, the video coder partitions CTUs and CUs into four equal non-overlapping squares, and each node of the quad-tree has either zero or four child nodes. A node without children may be called a "leaf node," and a CU of such a leaf node may include one or more PUs and / or one or more TUs. A video coder may further partition PUs and TUs. For example, a residual quad-tree (RQT) represents a partition of TUs, where PUs represent inter-predicted data, while TUs represent residual data. An intra-predicted CU includes intra-prediction information, such as an intra-mode indication.

[0037]

[0044] As another example, the video encoder 200 and the video decoder 300 may be configured to operate according to JEM, VVC, EVC, or any other such standard. A video coder (such as the video encoder 200) partitions a picture into multiple coding tree units (CTUs). The video encoder 200 may partition the CTUs according to a tree structure, such as a quad-tree binary tree (QTBT) structure or a multi-type tree (MTT) structure. The QTBT structure eliminates the concept of multiple partition types, such as the separation between CUs, PUs, and TUs. The QTBT structure includes two levels, a first level partitioned according to a quad-tree partition and a second level partitioned according to a binary tree partition. The root node of the QTBT structure corresponds to a CTU. The leaf nodes of the binary tree correspond to coding units (CUs).

[0038]

[0045] In the MTT partitioning structure, blocks may be partitioned using quad tree (QT) partitioning, binary tree (BT) partitioning, and one or more types of triple tree (TT) (also called ternary tree (TT)) partitioning. A triple tree or ternary tree partitioning is a partitioning in which a block is split into three sub-blocks. In some examples, a triple tree or ternary tree partitioning splits a block into three sub-blocks without splitting the original block through the center. The partitioning types in MTT (e.g., QT, BT, and TT) may be symmetric or asymmetric.

[0039]

[0046] In some examples, the video encoder 200 and the video decoder 300 may use a single QTBT or MTT structure to represent each of the luminance and chrominance components, and in other examples, the video encoder 200 and the video decoder 300 may use two or more QTBT or MTT structures, such as one QTBT / MTT structure for the luminance component and another QTBT / MTT structure for both chrominance components (or two QTBT / MTT structures for each chrominance component).

[0040]

[0047] Video encoder 200 and video decoder 300 may be configured to use quadtree partitioning, QTBT partitioning, MTT partitioning, or other partition structures. For purposes of explanation, the description of the techniques of this disclosure is presented with respect to QTBT partitioning. However, it should be understood that the techniques of this disclosure may also be applied to video coders configured to use quadtree partitioning, or other types of partitioning as well.

[0041]

[0048] Blocks (e.g., CTUs or CUs) may be grouped in various ways in a picture. As an example, a brick may refer to a rectangular region of a CTU row in a particular tile in a picture. A tile may be a rectangular region of a CTU in a particular tile column and a particular tile row in a picture. A tile column refers to a rectangular region of a CTU having a height equal to the height of the picture and a width specified by a syntax element (e.g., in a picture parameter set). A tile row refers to a rectangular region of a CTU having a height specified by a syntax element (e.g., in a picture parameter set) and a width equal to the width of the picture.

[0042]

[0049] In some examples, a tile may be partitioned into multiple bricks, each of which may include one or more CTU rows within the tile. A tile that is not partitioned into multiple bricks may also be referred to as a brick. However, a brick that is a true subset of a tile may not be referred to as a tile.

[0043]

[0050] The bricks in a picture may also be arranged into slices. A slice may be an integer number of bricks of a picture that may be contained entirely in a single Network Abstraction Layer (NAL) unit. In some examples, a slice includes either several complete tiles or only a continuous sequence of complete bricks of one tile.

[0044]

[0051] This disclosure may use "NxN" and "N by N", e.g., 16x16 samples or 16 by 16 samples, interchangeably to refer to sample dimensions of a block (such as a CU or other video block) in terms of vertical and horizontal dimensions. Generally, a 16x16 CU has 16 samples in the vertical direction (y=16) and 16 samples in the horizontal direction (x=16). Similarly, an NxN CU generally has N samples in the vertical direction and N samples in the horizontal direction, where N represents a non-negative integer value. Samples in a CU may be arranged in rows and columns. Moreover, a CU does not necessarily have to have the same number of samples in the horizontal direction as in the vertical direction. For example, a CU may comprise NxM samples, where M is not necessarily equal to N.

[0045]

[0052] The video encoder 200 encodes video data for a CU that represents prediction and / or residual information, as well as other information. The prediction information indicates how the CU should be predicted to form a predictive block for the CU. The residual information generally represents sample-by-sample differences between samples of the CU prior to encoding and the predictive block.

[0046]

[0053] To predict a CU, the video encoder 200 may generally form a predictive block for the CU through inter-prediction or intra-prediction. Inter-prediction generally refers to predicting a CU from data of a previously coded picture, while intra-prediction generally refers to predicting a CU from previously coded data of the same picture. To perform inter-prediction, the video encoder 200 may generate a predictive block using one or more motion vectors. The video encoder 200 may generally perform a motion search to identify a reference block that closely matches the CU, for example, with respect to the difference between the CU and the reference block. The video encoder 200 may calculate a difference metric using a sum of absolute differences (SAD), sum of squared differences (SSD), mean absolute difference (MAD), mean squared difference (MSD), or other such difference calculation to determine whether the reference block closely matches the current CU. In some examples, the video encoder 200 may predict the current CU using unidirectional or bidirectional prediction.

[0047]

[0054] The video coding standard also provides an affine motion compensation mode, which may be considered an inter-prediction mode. In an affine motion compensation mode, video encoder 200 may determine two or more motion vectors that represent non-translational motion, such as zooming in or out, rotation, perspective motion, or other irregular motion types.

[0048]

[0055] To perform intra prediction, video encoder 200 may select an intra prediction mode to generate a predictive block. For example, video encoder 200 may utilize 67 or some other number of intra prediction modes, including various directional modes, as well as planar and DC modes. In general, video encoder 200 selects an intra prediction mode that describes neighboring samples relative to a current block (e.g., a block of a CU) from which samples of the current block should be predicted. Such samples may generally be above, to the left of, or to the left of the current block in the same picture as the current block, assuming that video encoder 200 codes CTUs and CUs in raster scan order (left to right, top to bottom).

[0049]

[0056] Video encoder 200 encodes data representing a prediction mode for the current block. For example, in an inter prediction mode, video encoder 200 may encode data representing which of various available inter prediction modes is used, as well as motion information for the corresponding mode. For example, in unidirectional or bidirectional inter prediction, video encoder 200 may encode motion vectors using advanced motion vector prediction (AMVP) or merge mode. Video encoder 200 may use similar modes to encode motion vectors for affine motion compensation modes.

[0050]

[0057] Following prediction, such as intra- or inter-prediction, of a block, the video encoder 200 may calculate residual data for the block. The residual data, such as a residual block, represents sample-by-sample differences between the block and a predictive block for the block formed using a corresponding prediction mode. The video encoder 200 may apply one or more transforms to the residual block to generate transform data in a transform domain rather than the sample domain. For example, the video encoder 200 may apply a discrete cosine transform (DCT), an integer transform, a wavelet transform, or a conceptually similar transform to the residual video data. Additionally, the video encoder 200 may apply a secondary transform, such as a mode-dependent non-separable secondary transform (MDNSST), a signal-dependent transform, a Karhunen-Loeve transform (KLT), etc., following the first transform. The video encoder 200 generates transform coefficients following application of the one or more transforms.

[0051]

[0058] As mentioned above, following any transformation to generate transform coefficients, the video encoder 200 may perform quantization of the transform coefficients. Quantization generally refers to a process in which transform coefficients are quantized to possibly reduce the amount of data used to represent the transform coefficients, providing further compression. By performing a quantization process, the video encoder 200 may reduce the bit depth associated with some or all of the transform coefficients. For example, the video encoder 200 may round an n-bit value to an m-bit value during quantization, where n is greater than m. In some examples, to perform quantization, the video encoder 200 may perform a bitwise right shift of the value to be quantized.

[0052]

[0059] Following quantization, the video encoder 200 may scan the transform coefficients to generate a one-dimensional vector from a two-dimensional matrix including the quantized transform coefficients. The scan may be designed to place higher energy (and therefore lower frequency) transform coefficients at the front of the vector and lower energy (and therefore higher frequency) transform coefficients at the rear of the vector. In some examples, the video encoder 200 may utilize a predefined scan order to scan the quantized transform coefficients to generate a serialized vector and then entropy encode the quantized transform coefficients of the vector. In other examples, the video encoder 200 may perform an adaptive scan. After scanning the quantized transform coefficients to form a one-dimensional vector, the video encoder 200 may entropy encode the one-dimensional vector, e.g., according to context-adaptive binary arithmetic coding (CABAC). The video encoder 200 may also entropy encode values ​​for syntax elements describing metadata associated with the encoded video data for use by the video decoder 300 in decoding the video data.

[0053]

[0060] To implement CABAC, the video encoder 200 may assign a context in a context model to a symbol to be transmitted. The context may relate, for example, to whether neighboring values ​​of the symbol are zero-valued or not. The probability determination may be based on the context assigned to the symbol.

[0054]

[0061] Video encoder 200 may further generate syntax data, such as block-based syntax data, picture-based syntax data, and sequence-based syntax data, for video decoder 300, e.g., in a picture header, block header, slice header, or other syntax data, such as a sequence parameter set (SPS), a picture parameter set (PPS), or a video parameter set (VPS). Video decoder 300 may similarly decode such syntax data to determine how to decode corresponding video data.

[0055]

[0062] In this manner, video encoder 200 may generate a bitstream including encoded video data, e.g., syntax elements that describe partitions of a picture into blocks (e.g., CUs) as well as predictive and / or residual information for the blocks. Finally, video decoder 300 may receive the bitstream and decode the encoded video data.

[0056]

[0063] In general, the video decoder 300 performs an inverse process to that performed by the video encoder 200 to decode the encoded video data of the bitstream. For example, the video decoder 300 may decode values ​​for syntax elements of the bitstream using CABAC in a manner that is inverse to, but substantially similar to, the CABAC encoding process of the video encoder 200. The syntax elements may define partition information of a picture into CTUs and partitions of each CTU according to a corresponding partition structure, such as a QTBT structure, to define CUs of the CTU. The syntax elements may further define prediction and residual information for blocks (e.g., CUs) of video data.

[0057]

[0064] The residual information may be represented, for example, by quantized transform coefficients. The video decoder 300 may dequantize and inverse transform the quantized transform coefficients of the block to reconstruct a residual block for the block. The video decoder 300 uses the signaled prediction mode (intra- or inter-prediction) and associated prediction information (e.g., motion information for inter-prediction) to form a predictive block for the block. The video decoder 300 may then combine (sample-by-sample) the predictive block and the residual block to reconstruct the original block. The video decoder 300 may perform additional processing, such as performing a deblocking process to reduce visual artifacts along block boundaries.

[0058]

[0065] This disclosure may generally refer to "signaling" certain information, such as a syntax element. The term "signaling" may generally refer to communication of values ​​for syntax elements and / or other data used to decode encoded video data. That is, video encoder 200 may signal values ​​for syntax elements in a bitstream. Generally, signaling refers to generating values ​​in a bitstream. As mentioned above, source device 102 may transport the bitstream to destination device 116 in substantially real-time or may transport the bitstream to destination device 116 in non-real-time, such as may be done when storing syntax elements to storage device 112 for later retrieval by destination device 116.

[0059]

[0066] The following describes example techniques of EVC. In some examples, the EVC techniques may be similar to VVC and / or HEVC techniques (e.g., block-based coding techniques, etc.).

[0060]

[0067] An EVC sample contains access units as defined in ISO / IEC 23094-1, Section 3.1: Information technology - General video coding - Part 1: Essential video coding. In EVC, there may be a canonical order and some restrictions for a bitstream to be EVC compliant. A canonical stream format is an EVC elementary stream that satisfies the following conditions in addition to the general conditions in ISO / IEC 14496-15: Information technology - Coding of audio-visual objects - Part 15: Advanced Video Coding (AVC) file format, Section 4.3.2: a. Access unit delimiter NAL unit: The constraints obeyed by the access unit delimiter NAL unit are defined in ISO / IEC 23094-1. b. SPS and PPS: The SPS or PPS to be used in a picture may (and in some instances must) be sent before the sample containing that picture or in the sample for that picture. At least the SPS and PPS with id equal to 0 may be stored in the sample entry of the track containing the EVC elementary stream. c. APS: The APS to be used in a slice may (and in some instances must) be sent prior to the VCL NAL unit containing the slice. The APS may be stored in the sample entry and / or the sample. d. SEI Messages: SEI messages that are of a declarative nature may be stored in the sample entry and there is no provision for removing such SEI messages from the sample. e. Filler Data: Video data shall naturally be represented as variable bit rate in the file format and filled in for transmission as needed.

[0061]

[0068] The removal or addition of filler data NAL units, start codes, SEI messages, or filler data SEI messages can change the bitstream characteristics with respect to compatibility with a hypothetical reference decoder (HRD) when operating the HRD in constant bit rate (CBR) mode, as specified in ISO / IEC 23094-1, Annex C.

[0062]

[0069] The following are EVC decoder configuration records and descriptions. The video decoder 300 may be configured in accordance with an EVC decoder configuration in some examples. As part of the description of the EVC decoder configuration, the following specifies decoder configuration information for ISO / IEC 23094-1 video content.

[0063]

[0070] This record contains a version field. A file format parser (e.g., a reader) MAY not (e.g., should not) attempt to decode this record or the stream to which it applies if the version number is not recognized.

[0064]

[0071] Compatible extensions to this record may extend it and not change the configuration version code. A reader may ignore unrecognized data beyond the definition of the data the reader is configured to parse.

[0065]

[0072] The values ​​for profile_idc, level_idc, toolset_idc, chroma_format_idc, pic_width_in_luma_samples, pic_height_in_luma_samples, bit_depth_luma_minus8, and bit_depth_chroma_minus8 may be valid (and in some examples shall be valid) for all parameter sets (referred to as "all parameter sets") that are activated when the stream is decoded. In particular, the following restrictions may apply: a. The profile directive profile_idc may (e.g., SHALL) indicate the profile to which the stream associated with this configuration record conforms. If the SPS is marked with different profiles, the stream may require inspection to determine which profile, if any, the entire stream conforms to. If the entire stream is not inspected, or if inspection reveals that there is no profile to which the entire stream conforms, the entire stream may (e.g., SHALL) be split into two or more sub-streams with separate configuration records in which these rules may be satisfied. b. The level indication level_idc may (eg, shall) indicate a level of capability equal to or greater than the highest level indicated in all parameter sets for this configuration record. c.pic_width_in_luma_samples and pic_height_in_luma_samples may (e.g., shall) contain the highest value of all parameters set for this configuration record. d. The toolset indication toolset_idc may (e.g., shall) signal all tools needed to decode the stream associated with this configuration record. The tools flags may (e.g., shall) conform to the conformance requirements as provided in Table A.6 (reproduced below) of ISO / IEC 23094-1 and may (e.g., shall be) identical to the toolset_idc field signaled in the SPS. e. The value of chroma_format_idc in all parameter sets may be (e.g., shall be) the same. f. The value of bit_depth_luma_minus8 in all parameter sets may be (eg, shall be) the same. g. The value of bit_depth_chroma_minus8 in all parameter sets may be (eg, shall be) the same.

[0066]

[0073] An explicit indication is provided within the EVC Decoder Configuration Record for the chroma format and bit depth used by the EVC video elementary stream. Each type of such information, if present, may (e.g., shall) be identical across all parameter sets within a single EVC Configuration Record. If two sequences differ in any type of such information, two different EVC sample entries may (e.g., shall) be used.

[0067]

[0074] There is a set of arrays for carrying initialization NAL units. The NAL unit types may be restricted to indicate only SPS, PPS, APS, and SEI NAL units. NAL unit types reserved in ISO / IEC 23094-1 and herein may be defined, and NAL units with unrecognized NAL unit types may be ignored. This "tolerant" behavior (e.g., ignoring unrecognized NAL unit types) may be designed to be error-free and allows for the possibility of backward-compatible extensions to these arrays in future specifications.

[0068]

[0075] The length field, if stored in the sample entry, may be used in each sample to indicate the length and parameter set of its contained NAL unit. In some examples, the array is in the following order: SPS, PPS, APS, SEI.

[0069]

[0076] Table A.6 of ISO / IEC23094-1 is as follows:

[0070] [Table 1]

[0071]

[0077] The following describes the syntax used by video encoder 200 and video decoder 300. aligned(8) class EVCDecoderConfigurationRecord{ unsigned int(8) configurationVersion=1; unsigned int(8) profile_idc; unsigned int(8) level_idc; unsigned int(32) toolset_idc; unsigned int(2) chroma_format_idc; unsigned int(3) bit_depth_luma_minus8; unsigned int(3) bit_depth_chroma_minus8; unsigned int(32) pic_width_in_luma_samples; unsigned int(32) pic_height_in_luma_samples; unsidned int(5) reserved='00000'b; unsigned int(1) sps_in_stream; unsigned int(1) pps_in_stream; unsigned int(1) aps_in_stream; unsigned int(8) numOfArrays; for(j=0;j <numOfArrays;j++){ bit(2) reserved='00'b; unsigned int(6) NAL_unit_type; unsigned int(16) numNalus; for(i=0;i <numNalus;i++){ unsigned int(16) nalUnitLength; bit(8*nalUnitLength)nalUnit; } } }

[0078] The following description provides semantics for defining the terms in the above syntax. The syntax elements profile_idc, level_idc, toolset_idc, chroma_format_idc, toolset_idc, bit_depth_luma_minus8, and bit_depth_chroma_minus8 contain matching values ​​for fields in the PPS for all parameter sets of the configuration record. The notation "(32)" indicates that the syntax element toolset_idc is 32 bits. These 32 bits may include one-bit flags, each corresponding to a particular tool, or in some cases, multiple bits of the 32 bits may correspond, for example, to a combination of tools or a selection of a tool from a set of tools.

[0072]

[0079] The syntax elements pic_width_in_luma_samples and pic_height_in_luma_samples contain the maximum values ​​for the fields in all SPSs of this configuration record when the value of the sps_in_stream field is "0". These syntax elements may contain the maximum values ​​for the fields in all SPSs of this configuration record and all SPSs in the stream when the value of the sps_in_stream field is "1". The value "0" may be used (e.g., shall be used) when the maximum values ​​of these fields in the SPSs for all parameter sets in this record are not indicated through this field when the value of the sps_in_stream field is "0", or when the value of the sps_in_stream field is "1", the values ​​of these fields in the SPSs in the stream have values ​​greater than the maximum values ​​of the fields in this record.

[0073]

[0080] The syntax element sps_in_stream indicates that the stream may contain additional SPSs that are not included in the array of NAL units of this configuration record. The syntax element pps_in_stream indicates that the stream may contain additional PPSs that are not included in the array of NAL units of this configuration record. The syntax element aps_in_stream indicates that the stream may contain additional APSs that are not included in the array of NAL units of this configuration record.

[0074]

[0081] The syntax element numArrays indicates the number of arrays of NAL units of the indicated type. The syntax element NAL_unit_type indicates the type of the NAL units in the following array, which may be (e.g., shall be) all of that type. NAL_unit_type takes values ​​defined in ISO / IEC 23094-1 and may be restricted to take one of the values ​​indicating SPS, PPS, APS, or SEI NAL units.

[0075]

[0082] The syntax element numNalus indicates the number of NAL units of the indicated type contained in the configuration record for the stream to which this configuration record applies. The syntax element nalUnitLength indicates the length in bytes of a NAL unit. The syntax element nalUnit contains an SPS, PPS, APS, or SEI NAL unit as specified in ISO / IEC 23094-1.

[0076]

[0083] The ISO Base Media File Format, and its extensions, video files, store data in a series of objects called "boxes." The following describes the ISO Base Media File Format, including EVC video stream definitions, and sample entry names and formats. a. Sample entries and box types: "evc1", "evcC" b.Container:sampletablebox("stb1") c. Required: The "evc1" sample entry is required. d. Quantity: There can be one or multiple sample entries.

[0077]

[0084] An EVC visual sample entry may (eg, shall) include an EVC configuration box, as defined below, which contains an EVC DecoderConfigurationRecord.

[0078]

[0085] An optional BitRateBox may be present in the EVC visual sample entry to signal the bitrate information of the EVC video stream.

[0079]

[0086] Multiple sample entries may be used, as permitted by the ISO Base Media File Format specification, to indicate sections of the video that use different configurations or parameter sets.

[0080]

[0087] When the sample entry name is "evc1", the stream to which this sample entry applies may be (e.g., shall be) a compliant EVC stream as seen by an EVC decoder (e.g., video decoder 300) operating under the configuration (including profile, level, and toolset) given in the EVCConfigurationBox.

[0081]

[0088] The "evc1" sample entry allows storage of both sample entries and parameter sets in a stream. sps_in_stream, pps_in_stream, and aps_in_stream, when set to 0, indicate that the array of NAL units of the corresponding type is complete.

[0082]

[0089] Below is an example set of syntax for a configuration box for a file format. class EVCConfigurationBox extends Box('evcC'){ EVCDecoderConfigurationRecord()EVCConfig; } class EVCSampleEntry() extends VisualSampleEntry('evc1'){ EVCConfigurationBox config; MPEG4ExtensionDescriptorsBox(); / / optional }

[0090] Below is an example set of semantics for the syntax described above.

[0083]

[0091] The Compressorname in the base class VisualSampleEntry indicates the name of the compressor to be used with the recommended value "\012EVC Coding" (\012 is 10 and is the length of the string in bytes). The EVCDecoderConfigurationRecord is defined in section 5.3.3 (which could be, for example, but not limited to, ISO / IEC23904-1).

[0084]

[0092] The following describes the parameter sets. In summary, at least the initial SPS and PPS with id equal to 0 may be (e.g., shall be) carried in the sample entry. If sps_in_stream and / or pps_in_stream are set to "1", additional SPS and / or PPS may be present in-band in the stream.

[0085]

[0093] A sample carrying a parameter set may belong (e.g., shall belong) to a sample group corresponding to the type of that parameter set. Three sample group_types "pss1" are defined herein. Further grouping type parameters are used to distinguish between SPS, PPS, and APS, where "sps1" identifies a sample group of samples carrying SPS, "pps1" identifies a sample group of samples carrying PPS, and "aps1" identifies a sample group of samples carrying APS.

[0086]

[0094] The following describes the Parameter Set Sample Group entries, including definitions. a.Group type: "pss1" b. Container: Sample Group Description Box ("sgpd") c. Required: No d.Quantity: 0 or more

[0095] The parameter set sample group identifies samples that contain parameter sets of type SPS, PPS, or APS. The grouping_type_parameter further identifies the type of parameter set and can take the values ​​"sps1", "pps1", or "aps1".

[0087]

[0096] The following describes some syntax for the parameter set sample group entries. class PSSSampleEntry() extends VisualSampleGroupEntry ('pss1') { }

[0097] The following describes the synchronization sample: A synchronization sample in the "evc1" track may (e.g., shall) include a VCL NAL unit that indicates that a coded picture with nuh_temporal_id equal to 0 in the sample is an Instantaneous Decoding Refresh (IDR) picture.

[0088]

[0098] Table 1 shows the mapping between EVC VCL NAL unit types, ISOBMFF synchronization sample statuses, and SAP types documented in ISOBMFF.

[0089]

[0099]

[0090] [Table 2]

[0091]

[0100] The following is the definition of subsamples for EVC. For use of the SubSampleInformationBox (8.7.7 of ISO / IEC 14496-12) in an EVC stream, subsamples are defined based on the value of the flags field of the Subsample Information Box specified below. The presence of this box is optional, but if present in a track containing EVC data, the "codec_specific_parameters" field in the box may (e.g., shall) have the semantics defined herein.

[0092]

[0101] The flags specify the type of subsample information given in this box as follows: a.0: NAL unit-based subsample: A subsample contains one or more consecutive NAL units. b.1: Tile-based subsample: A subsample contains a VCL NAL unit with all the CTUs of one tile, together with any associated non-VCL NAL units, if any. c.2: Slice-based subsample: A subsample contains one slice (ie, one VCL NAL unit) and associated non-VCL NAL units, if any. d. Other values ​​of flags are reserved.

[0093]

[0102] The subsample_priority field may be (eg, shall be) set to a value according to the specification of this field in ISO / IEC 14496-12.

[0094]

[0103] The discardable field may (e.g., shall) be set to 1 if and only if this sample is still decodable if this subsample is discarded (e.g., the subsample consists of an SEI NAL unit).

[0095]

[0104] When the first byte of a NAL unit is included in a subsample, the preceding length field may also be included (eg, shall be included) in the same subsample.

[0096]

[0105] The codec_specific_parameters field of the SubSampleInformationBox is defined for EVC as follows:

[0097] if(flags==1) { unsigned int(16)tile_col_idx; unsigned int(16)tile_row_idx; }

[0106] tile_col_idx for tile-based subsamples: this parameter indicates the 0-based index of the tile column that contains this subsample's tile.

[0098]

[0107] tile_row_idx for tile-based subsamples: this parameter indicates the 0-based index of the tile row that contains this subsample's tile.

[0099]

[0108] The following describes the CMAF media profile. ISO / IEC 23000-19 Common Media Application Format (CMAF) defines structural constraints on ISOBMFF files on top of ISO / IEC 14496-12, for example for adaptive streaming or delivery of encrypted files. Conformance to these structural constraints is signaled by the presence of a CMAF-defined structural brand in the FileTypeBox.

[0100]

[0109] If an ISO BMFF track uses the brand "cevc", it is called a CMAF EVC track and the following constraints defining a CMAF media profile for EVC apply: a. It may (eg, shall) use the "evc1" sample entry defined in clause 6.3 of ISO / IEC 23094-1. b. The track may conform (e.g., shall conform) to the general CMAF track constraints in ISO / IEC 23000-19, Section 7. c. The track may conform (e.g., shall conform) to the general CMAF video track constraints in ISO / IEC 23000-19, Section 9.

[0101]

[0110] When EVC media is provided within a CMAF switching set, a. All CMAF tracks in the CMAF switching set may be (e.g., shall be) compliant with the CMAF EVC tracks. b. The CMAF switching set may conform (e.g., shall conform) to the general CMAF switching set constraints in ISO / IEC 23000-19, clause 7. c. The general CMAF video track switching set constraints defined in ISO / IEC 23000-19, clause 9.

[0102]

[0111] A CMAF Switching Set that conforms to these requirements is defined as the CMAF EVC Media Profile "cevc". Encryption of CMAF EVC Tracks and CMAF EVC Switching Sets may conform to (e.g., shall conform to) ISO / IEC 23000-19, Clause 8, using either the "cenc" AES-CTR method or the "cbcs" AES-CBC subsample pattern encryption method, as specified in ISO / IEC 23001-7, Clauses 10.1 and 10.4, respectively.

[0103]

[0112] Additionally, of the "cbcs" mode of common encryption, pattern encryption as defined in clause 9.6 of ISO / IEC 23001-7 may be used, and then a pattern block length of 10 and an encryption skip pattern of 1:9 may be applied (e.g., shall be applied) (e.g., as described in clause 10.4 of ISO / IEC 23001-7).

[0104]

[0113] The following describes the mapping to a DASH delivery: If EVC encoded media is provided in a DASH media presentation in an adaptation set, the adaptation set may (e.g., shall) conform to the DASH profile for CMAF defined in ISO / IEC 23009-1. The following parameters may (e.g., shall) be present at the adaptation set level and on the set: a. @codecs is set in accordance with Appendix A. b. @mimeType is set to match "video / mp4 profiles='cevc'".

[0105]

[0114] Below are descriptions of the sub-parameters of the MIME type "codes" parameter. DASH and other applications require defined values ​​for the Codecs parameter specified in IETF RFC6381 for ISO BMFF media tracks. The codes parameter string for the EVC codec is:<sample entry 4CC> . <key1> <value1> . <key2> <value2> .…. <keyn> <valuen>

[0115] The keys are defined as 4CC. The initial set of keys and associated value pairs are defined in Table 2. Additional keys may be specified as 4CC. In some examples, the keys are aligned with ISO / IEC 23091-2.

[0106]

[0116] If a particular key is not provided, a specified default value applies, or if not advertised (n / a), the value of the key is unknown.

[0107] [Table 3]

[0108]

[0117] For example, codecs="evc1.vprf3.vlev51.vtoo03FF.vbit20.vcss420.vcpr09.vtrc16.vmac09.vsar01" represents EVC Main Profile, level 5.1, with (0,0) luma sample and colocated 4:2:0 chroma subsampling, limited toolset, ITU-R BT.2100 color primaries, ITU-R BT.2100PQ transfer characteristic, ITU-R BT.2100YCbCr color matrix, and sample aspect ratio 1:1. If the evc1 sample entry is recognized, then all keys in Table 2 may be recognized (e.g., must be recognized). If a key is not recognized, the key value pair is ignored. In some examples, only other keys, e.g., 2CC, may be defined.

[0109]

[0118] The 'vtoo' and toolset_idc key-value pair conveys the same information as the toolset_idc syntax element in a decoder configuration record, but represents a different way of exposing this information to a video processing device.

[0110]

[0119] According to the techniques described above, the destination device 116 may be configured to receive a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools required to decode the bitstream associated with the configuration record, determine whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, retrieve the bitstream associated with the configuration record based on the decision to retrieve the bitstream associated with the configuration record, and output the bitstream to a video decoder for decoding. The destination device 116 may additionally or alternatively receive a MIME type parameter including a key-value pair, where the key indicates that the MIME type identifies a video decoding tool, and the value identifies a tool from the video decoding tools required to decode the bitstream. The bitstream of video data may include one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream may be enabled in at least one of the one or more parameter sets.

[0111]

[0120] The toolset indication syntax element is signaled in a configuration box of the file format information. The toolset indication syntax element, which includes information identifying the tools required to decode the bitstream associated with the configuration record, may identify all tools required to decode the bitstream associated with the configuration record. The toolset indication syntax element may be an unsigned 32-bit integer value, where each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

[0112]

[0121] The configuration records may be formatted according to the Essential EVC standard. A configuration record for a bitstream may include a profile syntax element and / or a level syntax element before the toolset indicating syntax element. A configuration record for a bitstream may include a chroma format syntax element after the toolset indicating syntax element.

[0113]

[0122] 2A and 2B are conceptual diagrams illustrating an exemplary quad-tree binary tree (QTBT) structure 130 and corresponding coding tree unit (CTU) 132. Solid lines represent quad-tree splitting, and dotted lines indicate binary tree splitting. At each split (i.e., non-leaf) node of the binary tree, one flag is signaled to indicate which splitting type (i.e., horizontal or vertical) is used, where in this example, 0 indicates horizontal splitting and 1 indicates vertical splitting. In quad-tree splitting, there is no need to indicate the splitting type, since the quad-tree node splits the block horizontally and vertically into four sub-blocks with equal size. Thus, video encoder 200 may encode, and video decoder 300 may decode, syntax elements (such as splitting information) for the region tree level (i.e., solid lines) of QTBT structure 130 and syntax elements (such as splitting information) for the prediction tree level (i.e., dashed lines) of QTBT structure 130. Video encoder 200 may encode, and video decoder 300 may decode, video data, such as prediction and transform data, for CUs represented by terminal leaf nodes of QTBT structure 130.

[0114]

[0123] 2B may be associated with parameters that define the sizes of blocks corresponding to nodes of the QTBT structure 130 at the first and second levels. These parameters may include a CTU size (representing the size of the CTU 132 in a sample), a minimum quad tree size (MinQTSize representing the minimum allowable quad tree leaf node size), a maximum binary tree size (MaxBTSize representing the maximum allowable binary tree root node size), a maximum binary tree depth (MaxBTDepth representing the maximum allowable binary tree depth), and a minimum binary tree size (MinBTSize representing the minimum allowable binary tree leaf node size).

[0115]

[0124] The root node of the QTBT structure corresponding to the CTU may have four child nodes at the first level of the QTBT structure, each of which may be partitioned according to a quadtree partition. That is, the nodes at the first level are either leaf nodes (without child nodes) or have four child nodes. The example QTBT structure 130 represents such a node including a parent node and a child node with solid lines for branching. If the nodes at the first level are not larger than the maximum allowed binary tree root node size (MaxBTSize), the nodes may be further partitioned by their respective binary trees. The binary tree splitting of one node may be repeated until the nodes resulting from the split reach the minimum allowed binary tree leaf node size (MinBTSize) or the maximum allowed binary tree depth (MaxBTDepth). The example QTBT structure 130 represents such a node with dashed lines for branching. The binary tree leaf nodes are called coding units (CUs), and the CUs are used for prediction (e.g., intra-picture or inter-picture prediction) and transformation without further partitioning. As explained above, a CU may also be referred to as a "video block" or a "block."

[0116]

[0125] In one example of a QTBT partitioning structure, the CTU size is set as 128x128 (luma samples and two corresponding 64x64 chroma samples), MinQTSize is set as 16x16, MaxBTSize is set as 64x64, MinBTSize is set as 4 (for both width and height), and MaxBTDepth is set as 4. Quad tree partitioning is first applied to the CTU to generate quad tree leaf nodes. The quad tree leaf nodes can have sizes from 16x16 (i.e., MinQTSize) to 128x128 (i.e., CTU size). If the leaf quad tree node is 128x128, it is not further split by the binary tree since the size exceeds MaxBTSize (i.e., 64x64 in this example). Otherwise, the leaf quad tree node is further partitioned by the binary tree. Therefore, the quad tree leaf node is also the root node for the binary tree and has the binary tree depth as 0. When the binary tree depth reaches MaxBTDepth (4 in this example), no further splitting is allowed. When a binary tree node has a width equal to MinBTSize (4 in this example), it implies that no further horizontal splitting is allowed. Similarly, a binary tree node having a height equal to MinBTSize implies that no further vertical splitting is allowed for that binary tree node. As mentioned above, the leaf nodes of the binary tree are called CUs and are further processed according to the prediction and transformation without further partitioning.

[0117]

[0126] 3 is a block diagram illustrating an example video encoder 200 that may implement the techniques of this disclosure. FIG. 3 is provided for illustrative purposes and should not be considered as limiting the techniques broadly illustrated and described in this disclosure. For illustrative purposes, this disclosure describes a video encoder 200 according to JEM, EVC, VVC (ITU-T H.266 under development), and HEVC (ITU-T H.265) techniques. However, the techniques of this disclosure may be performed by video encoding devices configured for other video coding standards.

[0118]

[0127] 3, the video encoder 200 includes a video data memory 230, a mode selection unit 202, a residual generation unit 204, a transform processing unit 206, a quantization unit 208, an inverse quantization unit 210, an inverse transform processing unit 212, a reconstruction unit 214, a filter unit 216, a decoded picture buffer (DPB) 218, and an entropy coding unit 220. Any or all of the video data memory 230, the mode selection unit 202, the residual generation unit 204, a transform processing unit 206, a quantization unit 208, an inverse quantization unit 210, an inverse transform processing unit 212, a reconstruction unit 214, a filter unit 216, a DPB 218, and an entropy coding unit 220 may be implemented in one or more processors or processing circuits. For example, the units of video encoder 200 may be implemented as one or more circuits or logic elements, as part of a hardware circuit, or as part of a processor in an FPGA, an ASIC, etc. Moreover, video encoder 200 may include additional or alternative processors or processing circuits for performing these and other functions.

[0119]

[0128] The video data memory 230 may store video data to be encoded by the components of the video encoder 200. The video encoder 200 may receive video data stored in the video data memory 230, for example, from the video source 104 (FIG. 1). The DPB 218 may act as a reference picture memory that stores reference video data for use in predicting subsequent video data by the video encoder 200. The video data memory 230 and the DPB 218 may be formed by any of a variety of memory devices, such as synchronous dynamic random access memory (DRAM), including DRAM (SDRAM), magnetoresistive RAM (MRAM), resistive RAM (RRAM), or other types of memory devices. The video data memory 230 and the DPB 218 may be provided by the same memory device or separate memory devices. In various examples, the video data memory 230 may be on-chip with the other components of the video encoder 200, as shown, or off-chip relative to those components.

[0120]

[0129] In this disclosure, references to video data memory 230 should not be construed as limited to memory internal to video encoder 200 unless specifically so described, or to memory external to video encoder 200 unless specifically so described. Instead, references to video data memory 230 should be understood as a reference memory that stores video data that video encoder 200 receives for encoding (e.g., video data for a current block to be encoded). Memory 106 of FIG. 1 may also provide temporary storage of outputs from various units of video encoder 200.

[0121]

[0130] The various units in FIG. 3 are shown to aid in understanding the operations performed by the video encoder 200. The units may be implemented as fixed-function circuits, programmable circuits, or a combination thereof. A fixed-function circuit refers to a circuit that provides a specific function and is preset with respect to the operations that may be performed. A programmable circuit refers to a circuit that may be programmed to perform various tasks and to provide flexible functionality in the operations that may be performed. For example, a programmable circuit may execute software or firmware that causes the programmable circuit to operate in a manner defined by the software or firmware instructions. A fixed-function circuit may execute software instructions (e.g., to receive parameters or output parameters), but the type of operations that the fixed-function circuit performs is generally unchanging. In some examples, one or more of the units may be separate circuit blocks (fixed function or programmable), and in some examples, one or more of the units may be an integrated circuit.

[0122]

[0131] The video encoder 200 may include an arithmetic logic unit (ALU), a basic functional unit (EFU), a programmable core formed of digital circuits, analog circuits, and / or programmable circuits. In examples in which the operations of the video encoder 200 are implemented using software executed by a programmable circuit, the memory 106 (FIG. 1) may store instructions (e.g., object code) of the software that the video encoder 200 receives and executes, or another memory (not shown) within the video encoder 200 may store such instructions.

[0123]

[0132] The video data memory 230 is configured to store the received video data. The video encoder 200 may retrieve pictures of the video data from the video data memory 230 and provide the video data to the residual generation unit 204 and the mode selection unit 202. The video data in the video data memory 230 may be raw video data to be encoded.

[0124]

[0133] The mode selection unit 202 includes a motion estimation unit 222, a motion compensation unit 224, and an intra prediction unit 226. The mode selection unit 202 may include additional functional units for performing video prediction according to other prediction modes. By way of example, the mode selection unit 202 may include a palette unit, an intra block copy unit (which may be part of the motion estimation unit 222 and / or the motion compensation unit 224), an affine unit, a linear model (LM) unit, etc.

[0125]

[0134] The mode selection unit 202 generally coordinates multiple encoding passes to test combinations of encoding parameters and resulting rate-distortion values ​​for such combinations. The encoding parameters may include partitioning of the CTU into CUs, prediction modes for the CUs, transform types for residual data of the CUs, quantization parameters for residual data of the CUs, etc. The mode selection unit 202 may finally select a combination of encoding parameters that has a rate-distortion value that is better than other tested combinations.

[0126]

[0135] Video encoder 200 may partition a picture retrieved from video data memory 230 into a series of CTUs and encapsulate one or more CTUs in a slice. Mode select unit 202 may partition the CTUs of a picture according to a tree structure, such as the QTBT structure or quadtree structure described above. As described above, video encoder 200 may form one or more CUs from partitioning the CTUs according to the tree structure. Such CUs may also be generally referred to as "video blocks" or "blocks."

[0127]

[0136] In general, the mode selection unit 202 also controls its components (e.g., the motion estimation unit 222, the motion compensation unit 224, and the intra prediction unit 226) to generate a prediction block for a current block (e.g., the current CU, or the overlapping portion of the PU and TU). For inter prediction of the current block, the motion estimation unit 222 may perform a motion search to identify one or more closely matching reference blocks in one or more reference pictures (e.g., one or more previously coded pictures stored in the DPB 218). In particular, the motion estimation unit 222 may calculate values ​​representing how similar a potential reference block is to the current block according to, for example, a sum of absolute differences (SAD), a sum of squared differences (SSD), a mean absolute difference (MAD), a mean squared difference (MSD), and the like. The motion estimation unit 222 may generally perform these calculations using a sample-by-sample difference between the current block and the reference block under consideration. The motion estimation unit 222 may identify the reference block having the lowest value obtained from these calculations, which indicates the reference block that most closely matches the current block.

[0128]

[0137] The motion estimation unit 222 may form one or more motion vectors (MVs) that define the position of a reference block in a reference picture relative to the position of a current block in a current picture. The motion estimation unit 222 may then provide the motion vectors to the motion compensation unit 224. For example, in unidirectional inter prediction, the motion estimation unit 222 may provide a single motion vector, while in bidirectional inter prediction, the motion estimation unit 222 may provide two motion vectors. The motion compensation unit 224 may then generate a predictive block using the motion vectors. For example, the motion compensation unit 224 may use the motion vectors to retrieve data of the reference block. As another example, if the motion vectors have sub-sample precision, the motion compensation unit 224 may interpolate values ​​for the predictive block according to one or more interpolation filters. Moreover, in bidirectional inter prediction, the motion compensation unit 224 may retrieve data for the two reference blocks identified by the respective motion vectors and combine the retrieved data, for example, through sample-wise averaging or weighted averaging.

[0129]

[0138] As another example, for intra prediction, or intra predictive coding, the intra prediction unit 226 may generate a predictive block from samples neighboring a current block. For example, in a directional mode, the intra prediction unit 226 may generally mathematically combine values ​​of neighboring samples and populate these calculated values ​​in a defined direction across the current block to generate a predictive block. As another example, in a DC mode, the intra prediction unit 226 may calculate an average of neighboring samples for the current block and generate a predictive block to include this resulting average for each sample of the predictive block.

[0130]

[0139] The mode selection unit 202 provides the prediction block to the residual generation unit 204. The residual generation unit 204 receives a raw uncoded version of the current block from the video data memory 230 and receives the prediction block from the mode selection unit 202. The residual generation unit 204 calculates sample-by-sample differences between the current block and the prediction block. The resulting sample-by-sample differences define a residual block for the current block. In some examples, the residual generation unit 204 may also determine differences between sample values ​​in the residual block to generate the residual block using residual differential pulse code modulation (RDPCM). In some examples, the residual generation unit 204 may be formed using one or more subtractor circuits that perform binary subtraction.

[0131]

[0140] In an example where the mode selection unit 202 partitions a CU into PUs, each PU may be associated with a luma prediction unit and a corresponding chroma prediction unit. The video encoder 200 and the video decoder 300 may support PUs having various sizes. As indicated above, the size of a CU may refer to the size of the luma coding block of the CU, and the size of a PU may refer to the size of the luma prediction unit of the PU. Assuming that the size of a particular CU is 2N×2N, the video encoder 200 may support a PU size of 2N×2N or N×N for intra prediction, and a symmetric PU size of 2N×2N, 2N×N, N×2N, N×N, or the like for inter prediction. The video encoder 200 and the video decoder 300 may also support asymmetric partitioning of PU sizes of 2N×nU, 2N×nD, nL×2N, and nR×2N for inter prediction.

[0132]

[0141] In examples where the mode select unit 202 does not further partition the CUs into PUs, each CU may be associated with a luma coding block and a corresponding chroma coding block. As described above, the size of a CU may refer to the size of the luma coding block of the CU. The video encoder 200 and the video decoder 300 may support CU sizes of 2N×2N, 2N×N, or N×2N.

[0133]

[0142] In other video coding techniques, such as intra block copy mode coding, affine mode coding, and linear model (LM) mode coding, as some examples, the mode selection unit 202 generates a predictive block for the current block being coded via a respective unit associated with the coding technique. In some examples, such as palette mode coding, the mode selection unit 202 may not generate a predictive block, but instead generate syntax elements that indicate how the block should be reconstructed based on a selected palette. In such modes, the mode selection unit 202 may provide these syntax elements to be coded to the entropy coding unit 220.

[0134]

[0143] As described above, the residual generation unit 204 receives the video data for a current block and the corresponding predictive block. The residual generation unit 204 then generates a residual block for the current block. To generate the residual block, the residual generation unit 204 calculates sample-by-sample differences between the predictive block and the current block.

[0135]

[0144] Transform processing unit 206 applies one or more transforms to the residual block to generate a block of transform coefficients (referred to herein as a "transform coefficient block"). Transform processing unit 206 may apply various transforms to the residual block to form the transform coefficient block. For example, transform processing unit 206 may apply a discrete cosine transform (DCT), a directional transform, a Karhunen-Loeve transform (KLT), or a conceptually similar transform to the residual block. In some examples, transform processing unit 206 may perform multiple transforms on the residual block, e.g., a linear transform and a secondary transform such as a rotation transform. In some examples, transform processing unit 206 does not apply a transform to the residual block.

[0136]

[0145] The quantization unit 208 may quantize the transform coefficients in the transform coefficient block to generate a quantized transform coefficient block. The quantization unit 208 may quantize the transform coefficients of the transform coefficient block according to a quantization parameter (QP) value associated with the current block. The video encoder 200 (e.g., via the mode selection unit 202) may adjust the degree of quantization applied to the transform coefficient block associated with the current block by adjusting the QP value associated with the CU. Quantization may result in loss of information, and thus the quantized transform coefficients may have less precision than the original transform coefficients generated by transform processing unit 206.

[0137]

[0146] Inverse quantization unit 210 and inverse transform processing unit 212 may apply inverse quantization and inverse transform to the quantized transform coefficient block, respectively, to reconstruct a residual block from the transform coefficient block. Reconstruction unit 214 may generate a reconstructed block that corresponds to the current block (potentially with some distortion) based on the reconstructed residual block and the predictive block generated by mode selection unit 202. For example, reconstruction unit 214 may add samples of the reconstructed residual block to corresponding samples from the predictive block generated by mode selection unit 202 to generate the reconstructed block.

[0138]

[0147] Filter unit 216 may perform one or more filter operations on the reconstructed block. For example, filter unit 216 may perform a deblocking operation to reduce blockiness artifacts along the edges of a CU. The operations of filter unit 216 may be skipped in some examples.

[0139]

[0148] The video encoder 200 stores the reconstructed blocks in the DPB 218. For example, in examples where the operation of the filter unit 216 is not required, the reconstruction unit 214 may store the reconstructed blocks in the DPB 218. In examples where the operation of the filter unit 216 is required, the filter unit 216 may store the filtered reconstructed blocks in the DPB 218. The motion estimation unit 222 and the motion compensation unit 224 may retrieve reference pictures formed from the reconstructed (and potentially filtered) blocks from the DPB 218 to inter predict blocks of a later-encoded picture. Additionally, the intra prediction unit 226 may use the reconstructed blocks in the DPB 218 of the current picture to intra predict other blocks in the current picture.

[0140]

[0149] In general, the entropy encoding unit 220 may entropy encode syntax elements received from other functional components of the video encoder 200. For example, the entropy encoding unit 220 may entropy encode quantized transform coefficient blocks from the quantization unit 208. As another example, the entropy encoding unit 220 may entropy encode predictive syntax elements (e.g., motion information for inter prediction, or intra mode information for intra prediction) from the mode selection unit 202. The entropy encoding unit 220 may perform one or more entropy encoding operations on syntax elements, which are another example of video data, to generate entropy encoded data. For example, the entropy encoding unit 220 may perform a context-adaptive variable length coding (CAVLC) operation, a CABAC operation, a variable-to-variable (V2V) length coding operation, a syntax-based context-adaptive binary arithmetic coding (SBAC) operation, a probability interval partitioned entropy (PIPE) coding operation, an exponential-Golomb coding operation, or another type of entropy coding operation on the data. In some examples, the entropy encoding unit 220 may operate in a bypass mode in which syntax elements are not entropy coded.

[0141]

[0150] The video encoder 200 may output a bitstream that includes entropy coding syntax elements needed to reconstruct blocks of a slice or picture. In particular, the entropy coding unit 220 may output the bitstream.

[0142]

[0151] The operations described above are described with respect to blocks. Such descriptions should be understood as being operations for luma coding blocks and / or chroma coding blocks. As described above, in some examples, the luma coding blocks and chroma coding blocks are luma and chroma components of a CU. In some examples, the luma coding blocks and chroma coding blocks are luma and chroma components of a PU.

[0143]

[0152] In some examples, operations performed with respect to luma coding blocks do not need to be repeated for chroma coding blocks. As an example, operations for identifying motion vectors (MVs) and reference pictures for luma coding blocks do not need to be repeated to identify MVs and reference pictures for chroma blocks. Rather, the MVs for luma coding blocks may be scaled to determine the MVs for chroma blocks, and the reference pictures may be the same. As another example, the intra prediction process may be the same for luma coding blocks and chroma coding blocks.

[0144]

[0153] Video encoder 200 represents an example of a device configured to encode video data, including a memory configured to store the video data and one or more processing units implemented in circuitry and configured to perform one or more example techniques described in this disclosure.

[0145]

[0154] In some examples, a source device may be configured to receive an output from video encoder 200 and determine (e.g., generate) a configuration record for a bitstream that encapsulates video data encoded by video encoder 200 according to the Essential Video Coding (EVC) standard that includes information for decoding the bitstream. The configuration record may include a toolset indication syntax element (e.g., toolset_idc). The configuration record may be provided at the file format level, e.g., as file format level data, or at a level that encapsulates video coding layer (VCL) level encoded media data. For example, as described herein, the configuration record may be included in a configuration box in a media file, where the configuration box is separate from a movie fragment box or other box that contains the actual encoded media data. In some examples, the toolset indication syntax element may include information of all tools needed to decode the bitstream associated with the configuration record. The toolset indication syntax element may indicate a tool that matches another toolset_idc field signaled in a sequence parameter set (SPS).

[0146]

[0155] In some examples, the toolset indicating syntax element may be considered to include the tools needed to play the file in the sample entry that is part of the coding parameters. To validate the toolset indicating syntax element, a coding scheme for the coding parameters in the MIME type may be utilized.

[0147]

[0156] 4 is a block diagram illustrating an example video decoder 300 that may implement the techniques of this disclosure. FIG. 4 is provided for illustrative purposes and is not intended to limit the techniques broadly illustrated and described in this disclosure. For illustrative purposes, this disclosure describes a video decoder 300 according to JEM, EVC, VVC (ITU-T H.266 under development), and HEVC (ITU-T H.265) techniques. However, the techniques of this disclosure may be implemented by video coding devices configured for other video coding standards.

[0148]

[0157] In the example of FIG. 4, the video decoder 300 includes a coded picture buffer (CPB) memory 320, an entropy decoding unit 302, a prediction processing unit 304, an inverse quantization unit 306, an inverse transform processing unit 308, a reconstruction unit 310, a filter unit 312, and a decoded picture buffer (DPB) 314. Any or all of the CPB memory 320, the entropy decoding unit 302, the prediction processing unit 304, the inverse quantization unit 306, the inverse transform processing unit 308, the reconstruction unit 310, the filter unit 312, and the DPB 314 may be implemented in one or more processors or processing circuits. For example, the units of the video decoder 300 may be implemented as one or more circuits or logic elements, as part of a hardware circuit, or as part of a processor of an FPGA, an ASIC. Moreover, the video decoder 300 may include additional or alternative processors or processing circuits for performing these and other functions.

[0149]

[0158] Prediction processing unit 304 includes a motion compensation unit 316 and an intra prediction unit 318. Prediction processing unit 304 may include additional units for performing prediction according to other prediction modes. By way of example, prediction processing unit 304 may include a palette unit, an intra block copy unit (which may form part of motion compensation unit 316), an affine unit, a linear model (LM) unit, etc. In other examples, video decoder 300 may include more, fewer, or different functional components.

[0150]

[0159] The CPB memory 320 may store video data, such as an encoded video bitstream, to be decoded by components of the video decoder 300. The video data stored in the CPB memory 320 may be obtained, for example, from the computer-readable medium 110 (FIG. 1). The CPB memory 320 may include a CPB that stores encoded video data (e.g., syntax elements) from the encoded video bitstream. The CPB memory 320 may also store video data other than syntax elements of a coded picture, such as temporary data representing output from various units of the video decoder 300. The DPB 314 generally stores decoded pictures that the video decoder 300 may output and / or use as reference video data when decoding subsequent data or pictures of the encoded video bitstream. The CPB memory 320 and the DPB 314 may be formed by any of a variety of memory devices, such as DRAM, including SDRAM, MRAM, RRAM, or other types of memory devices. The CPB memory 320 and the DPB 314 may be provided by the same memory device or separate memory devices. In various examples, the CPB memory 320 may be on-chip with other components of the video decoder 300 or off-chip relative to those components.

[0151]

[0160] Additionally or alternatively, in some examples, video decoder 300 may retrieve coded video data from memory 120 (FIG. 1). That is, memory 120 may store data as described above along with CPB memory 320. Similarly, memory 120 may store instructions to be executed by video decoder 300 when some or all of the functionality of video decoder 300 is implemented in software to be executed by processing circuitry of video decoder 300.

[0152]

[0161] The various units shown in FIG. 4 are shown to aid in understanding the operations performed by the video decoder 300. The units may be implemented as fixed-function circuits, programmable circuits, or a combination thereof. As with FIG. 3, a fixed-function circuit refers to a circuit that provides a specific function and is preset with respect to the operations that may be performed. A programmable circuit refers to a circuit that may be programmed to perform various tasks and to provide flexible functionality in the operations that may be performed. For example, a programmable circuit may execute software or firmware that causes the programmable circuit to operate in a manner defined by the software or firmware instructions. A fixed-function circuit may execute software instructions (e.g., to receive parameters or output parameters), but the types of operations that the fixed-function circuit performs are generally unchanging. In some examples, one or more of the units may be separate circuit blocks (fixed function or programmable), and in some examples, one or more of the units may be an integrated circuit.

[0153]

[0162] The video decoder 300 may include a programmable core formed from an ALU, an EFU, digital circuits, analog circuits, and / or programmable circuits. In examples in which the operations of the video decoder 300 are performed by software executing on programmable circuits, on-chip or off-chip memory may store instructions (e.g., object code) of the software that the video decoder 300 receives and executes.

[0154]

[0163] The entropy decoding unit 302 may receive the encoded video data from the CPB and entropy decode the video data to recover the syntax elements. The prediction processing unit 304, the inverse quantization unit 306, the inverse transform processing unit 308, the reconstruction unit 310, and the filter unit 312 may generate decoded video data based on the syntax elements extracted from the bitstream.

[0155]

[0164] In general, the video decoder 300 reconstructs a picture on a block-by-block basis. The video decoder 300 may perform a reconstruction operation on each block individually (wherein the block currently being reconstructed, i.e., the block currently being decoded, may be referred to as the “current block”).

[0156]

[0165] The entropy decoding unit 302 may entropy decode syntax elements defining the quantized transform coefficients of the quantized transform coefficient block, as well as transform information such as a quantization parameter (QP) and / or a transform mode indication(s). The inverse quantization unit 306 may use the QP associated with the quantized transform coefficient block to determine the degree of quantization and, similarly, the degree of inverse quantization that the inverse quantization unit 306 should apply. The inverse quantization unit 306 may perform, for example, a bitwise left shift operation to inverse quantize the quantized transform coefficients. The inverse quantization unit 306 may thereby form a transform coefficient block including the transform coefficients.

[0157]

[0166] After the inverse quantization unit 306 forms the transform coefficient block, the inverse transform processing unit 308 may apply one or more inverse transforms to the transform coefficient block to generate a residual block associated with the current block. For example, the inverse transform processing unit 308 may apply an inverse DCT, an inverse integer transform, an inverse Karhunen-Loeve transform (KLT), an inverse rotational transform, an inverse transform, or another inverse transform to the transform coefficient block.

[0158]

[0167] Further, prediction processing unit 304 generates a predictive block according to the prediction information syntax element entropy decoded by entropy decoding unit 302. For example, if the prediction information syntax element indicates that the current block is inter predicted, motion compensation unit 316 may generate a predictive block. In this case, the prediction information syntax element may indicate a reference picture in DPB 314 from which to retrieve a reference block, as well as a motion vector that identifies the location of the reference block in the reference picture relative to the location of the current block in the current picture. Motion compensation unit 316 may generally perform an inter prediction process in a manner substantially similar to that described with respect to motion compensation unit 224 (FIG. 3).

[0159]

[0168] As another example, if the prediction information syntax element indicates that the current block is intra predicted, the intra prediction unit 318 may generate a predictive block according to the intra prediction mode indicated by the prediction information syntax element. Again, the intra prediction unit 318 may generally perform an intra prediction process in a manner substantially similar to that described with respect to the intra prediction unit 226 (FIG. 3). The intra prediction unit 318 may retrieve data of neighboring samples for the current block from the DPB 314.

[0160]

[0169] The reconstruction unit 310 may reconstruct the current block using the predictive block and the residual block. For example, the reconstruction unit 310 may add samples of the residual block to corresponding samples of the predictive block to reconstruct the current block.

[0161]

[0170] Filter unit 312 may perform one or more filter operations on the reconstructed block. For example, filter unit 312 may perform a deblocking operation to reduce blockiness artifacts along edges of the reconstructed block. The operations of filter unit 312 are not necessarily performed in all examples.

[0162]

[0171] The video decoder 300 may store the reconstructed blocks in the DPB 314. For example, in examples where the operations of the filter unit 312 are not performed, the reconstruction unit 310 may store the reconstructed blocks in the DPB 314. In examples where the operations of the filter unit 312 are performed, the filter unit 312 may store the filtered reconstructed blocks in the DPB 314. As described above, the DPB 314 may provide reference information to the prediction processing unit 304, such as samples of the current picture for intra prediction and previously decoded pictures for subsequent motion compensation. Moreover, the video decoder 300 may output decoded pictures (e.g., decoded video) from the DPB 314 for subsequent presentation on a display device, such as the display device 118 of FIG. 1.

[0163]

[0172] In this manner, the video decoder 300 represents an example of a video decoding device that includes a memory configured to store video data and one or more processing units implemented in circuitry and configured to perform the example techniques described in this disclosure.

[0164]

[0173] In some examples, a client device may be configured to receive a configuration record for decoding a bitstream of video data according to the Essential Video Coding (EVC) standard. The configuration record may include a toolset indication syntax element (e.g., toolset_idc). In some examples, the toolset indication syntax element may include information of all tools required to decode a bitstream associated with the configuration record. The toolset indication syntax element of the configuration record may match a toolset indication syntax element signaled in a sequence parameter set (SPS). Based on the toolset indication syntax element, the client device may determine whether to retrieve a bitstream associated with the configuration record. Based on a decision to retrieve a bitstream associated with the configuration record, the client device may retrieve the bitstream and output the bitstream to the video decoder 300 for decoding.

[0165]

[0174] In some examples, the toolset indicating syntax element may be considered to include the tools needed to play the file in the sample entry that is part of the coding parameters. To validate the toolset indicating syntax element, a coding scheme for the coding parameters in the MIME type may be utilized.

[0166]

[0175] FIG. 5 is a conceptual diagram illustrating an example structure of a file 500 in accordance with one or more techniques of this disclosure. In the example of FIG. 5, the file 500 includes a movie box 502 and a number of media data boxes 504. Although shown in the example of FIG. 5 as being in the same file, in other examples, the movie box 502 and the media data box 504 may be in separate files. As noted above, a box may be an object-oriented building block defined by a unique type identifier and a length. For example, a box may be a basic syntax structure in ISOBMFF that includes a four-character coded box type, a byte count of the box, and a payload.

[0167]

[0176] The movie box 502 may contain metadata for tracks of the file 500. Each track of the file 500 may comprise a continuous stream of media data. Each of the media data boxes 504 may contain one or more samples 505. Each of the samples 505 may comprise an audio or video access unit. Each access unit may comprise multiple coded pictures for multiview coding or scalable video coding. For example, an access unit may include one or more coded pictures for each layer.

[0168]

[0177] Further, in the example of FIG. 5, the movie box 502 includes a track box 506. The track box 506 may encapsulate metadata for a track of the file 500. In other examples, the movie box 502 may include multiple track boxes for different tracks of the file 500. The track box 506 includes a track reference box 508 and a media box 510. The track reference box 508 may include a track reference type box 509. The track reference type box 509 may be associated with a type (e.g., "tbas") and a track identifier that identifies another track. According to a sixth technique of this disclosure, the track reference box of a tile track may or may not include a track reference type box associated with the type identifier "tbas".

[0169]

[0178] The Media Box 510 may contain all objects that declare information about the media data in the track. The Media Box 510 includes a Media Info Box 512. The Media Info Box 512 may contain all objects that declare media characteristic information of the track. The Media Info Box 512 includes a Sample Table Box 514. The Sample Table Box 514 may specify sample specific metadata.

[0170]

[0179] In the example of FIG. 5, the sample table box 514 includes a sample description box 516, which includes a sample entry 518. The sample entry 518 includes an EVC decoder configuration 520, which may include a toolset indication syntax element, as described above. In other examples, the sample table box 514 may include other boxes in addition to the sample description box 516 and the sample entry 518. Although not shown in FIG. 5, the sample entry 518 may include a decoder configuration record. As described in more detail above, this disclosure describes techniques for including new types of important information in a sample entry, such as the sample entry 518.

[0171]

[0180] Figure 6 is a conceptual diagram illustrating elements of an exemplary multimedia content 620. In the example of Figure 6, the multimedia content 620 includes an MPD 622 and multiple representations 624A-N (representations 624). Representation 624A includes optional header data 626 and segments 628A-N (segments 628), while representation 624N includes optional header data 630 and segments 632A-N (segments 632). The letter N is used for convenience to designate the last movie fragment in each of the representations 624. In some examples, there may be different numbers of movie fragments among the representations 624.

[0172]

[0181] The MPD 622 may comprise a data structure separate from the representations 624. In general, the MPD 422 may include data that generally describes characteristics of the representations 424, such as coding and rendering characteristics, adaptation sets, profiles to which the MPD 422 supports, text type information, camera angle information, rating information, trick mode information (e.g., information that indicates the representation includes a time subsequence), and / or information for retrieving remote periods (e.g., for targeted advertisement insertion into the media content being played).

[0173]

[0182] Header data 626, when present, can describe characteristics of segment 628, such as the time location of a random access point (RAP, also called a stream access point (SAP)) of segment 628, including the random access point, a byte offset to the random access point within segment 628, a uniform resource locator (URL) for segment 628, or other aspects of segment 628. Header data 630, when present, may describe similar characteristics for segment 632. Additionally or alternatively, such characteristics may be contained entirely within the MPD 622.

[0174]

[0183] The segments 628, 632 include one or more coded video samples, each of which may include a frame or slice of video data. Each of the coded video samples of the segment 628 may have similar characteristics, e.g., height, width, and bandwidth requirements. Such characteristics may be described by data in the MPD 622, although such data is not shown in the example of FIG. 6. The MPD 622 may include characteristics described by 3GPP specifications in addition to any or all of the signaled information described in this disclosure.

[0175]

[0184] Each of the segments 628, 632 may be associated with a unique Uniform Resource Locator (URL). Thus, each of the segments 628, 632 may be independently retrievable using a streaming network protocol such as DASH. In this manner, a destination device may use an HTTP GET request to retrieve a segment 628 or 632. In some examples, a destination device may use an HTTP partial GET request to retrieve a particular byte range of a segment 628 or 632.

[0176]

[0185] FIG. 7 is a block diagram illustrating elements of an exemplary video file 750. Video file 750 may be said to encapsulate segments. As explained above, video files according to the ISO Base Media File Format and its extensions store data in a series of objects called "boxes." In the example of FIG. 7, video file 750 includes a file type (FTYP) box 752, a movie (MOOV) box 754, a segment index (sidx) box 762, a movie fragment (MOOF) box 764, and a movie fragment random access (MFRA) box 766. Although FIG. 7 represents an example of a video file, it should be understood that other media files may include other types of media data (e.g., audio data, timed text data, etc.) structured similarly to the data of video file 750 according to the ISO Base Media File Format and its extensions.

[0177]

[0186] The FTYP box 752 generally describes the file type for the video file 750. The file type box 752 may contain data identifying specifications that describe the best use of the video file 750. The file type box 752 may alternatively be placed before the MOOV box 754, the Movie Fragment box 764, and / or the MFRA box 766.

[0178]

[0187] In some examples, a segment such as video file 750 may include an MPD update box (not shown) prior to FTYP box 752. The MPD update box may include information indicating that the MPD corresponding to a representation that includes video file 750 should be updated, along with information for updating the MPD. For example, the MPD update box may provide a URI or URL for a resource used to update the MPD. As another example, the MPD update box may include data for updating the MPD. In some examples, the MPD update box may immediately follow a segment type (STYP) box (not shown) of video file 750, where the STYP box may define the segment type of video file 750.

[0179]

[0188] 7, the MOOV box 754 includes a Movie Header (MVHD) box 756, a Track (TRAK) box 758, and one or more Movie Extension (MVEX) boxes 760. Generally, the MVHD box 756 may describe general characteristics of the video file 750. For example, the MVHD box 756 may include data describing when the video file 750 was originally created, when the video file 750 was last modified, a timeline of the video file 750, the duration of playback of the video file 750, or other data generally describing the video file 750.

[0180]

[0189] The TRAK box 758 may contain data about a track of the video file 750. The TRAK box 758 may contain a Track Header (TKHD) box that describes characteristics of the track that corresponds to the TRAK box 758. In some examples, the TRAK box 758 may contain coded video pictures, while in other examples, the coded video pictures for the track may be contained in a movie fragment 764 that may be referenced by data in the TRAK box 758 and / or the sidx box 762.

[0181]

[0190] In some examples, video file 750 may include more than one track. Thus, MOOV box 754 may include a number of TRAK boxes equal to the number of tracks in video file 750. TRAK box 758 may describe characteristics of the corresponding track of video file 750. For example, TRAK box 758 may describe time and / or spatial information for the corresponding track. When parameter set tracks are included in a video file such as video file 750, a TRAK box similar to TRAK box 758 of MOOV box 754 may describe characteristics of the parameter set tracks. The presence of a sequence level SEI message may be signaled in the parameter set track within a TRAK box that describes the parameter set track.

[0182]

[0191] The MVEX box 760 may describe characteristics of the corresponding movie fragment 764, for example, to signal that the video file 750 includes movie fragments 764 in addition to the video data contained in the MOOV box 754. In the context of streaming video data, coded video pictures may be included in the movie fragments 764 rather than the MOOV box 754. Thus, all coded video samples may be included in the movie fragments 764 rather than the MOOV box 754.

[0183]

[0192] The MOOV box 754 may contain a number of MVEX boxes 760 equal to the number of movie fragments 764 in the video file 750. Each of the MVEX boxes 760 may describe the characteristics of a corresponding one of the movie fragments 764. For example, each MVEX box may include a Movie Extension Header Box (MEHD) box that describes the duration for the corresponding one of the movie fragments 764.

[0184]

[0193] A sequence data set may be stored in a video sample that does not contain actual coded video data. A video sample may generally correspond to an access unit, which is a representation of a coded picture at a particular time instance. In the context of AVC, a coded picture includes one or more VCL NAL units that contain information to configure all pixels of an access unit, and other associated non-VCL NAL units, such as SEI messages. Thus, a sequence data set, which may include a sequence level SEI message, may be included in one of the movie fragments 764. The presence of a sequence data set and / or a sequence level SEI message may be signaled as being present in one of the movie fragments 764 in one of the MVEX boxes 760 that corresponds to one of the movie fragments 764.

[0185]

[0194] The SIDX box 762 is an optional element of the video file 750; that is, a video file that conforms to the 3GPP file format, or other such file formats, does not necessarily include a SIDX box 762. According to an example 3GPP file format, a SIDX box may be used to identify a subsegment of a segment (e.g., a segment contained within the video file 750). The 3GPP file format defines a subsegment as "a self-contained set of one or more consecutive Movie Fragment boxes with a corresponding Media Data box and a Media Data box containing data referenced by the Movie Fragment box, which must follow that Movie Fragment box and precede the next Movie Fragment box containing information about the same track." The 3GPP file format also indicates that a SIDX box "contains a sequence of references to subsegments of the (sub)segment documented by the box. The referenced subsegments are contiguous in presentation time. Similarly, the bytes referenced by a Segment Index box are always contiguous within the segment. The referenced size gives a count of the number of bytes in the referenced material."

[0186]

[0195] The SIDX box 762 generally provides information describing one or more subsegments of a segment contained in the video file 750. For example, such information may include the playback time at which the subsegment starts and / or ends, the byte offset of the subsegment, whether the subsegment contains (e.g., starts at) a Stream Access Point (SAP), the type of SAP (e.g., whether the SAP is an Instantaneous Decoder Refresh (IDR) picture, a Clean Random Access (CRA) picture, a Cut Link Access (BLA) picture, etc.), the location of the SAP (with respect to playback time and / or byte offset) within the subsegment, etc.

[0187]

[0196] The movie fragments 764 may include one or more coded video pictures. In some examples, the movie fragments 764 may include one or more groups of pictures (GOPs), each of which may include several coded video pictures, e.g., frames or pictures. Additionally, as described above, the movie fragments 764 may include a sequence data set in some examples. Each of the movie fragments 764 may include a Movie Fragment Header Box (MFHD, not shown in FIG. 7). The MFHD box may describe characteristics of the corresponding movie fragment, such as the sequence number of the movie fragment. The movie fragments 764 may be included in the video file 750 in order of sequence number.

[0188]

[0197] The MFRA box 766 may describe random access points within the movie fragments 764 of the video file 750. This may help to implement trick modes, such as performing a seek to a particular time location (i.e., play time) within a segment encapsulated by the video file 750. The MFRA box 766 is generally optional, and in some examples, need not be included in the video file. Similarly, a client device does not necessarily need to reference the MFRA box 766 to correctly decode and display the video data of the video file 750. The MFRA box 766 may include a number of track fragment random access (TFRA) boxes (not shown) equal to the number of tracks of the video file 750, or, in some examples, equal to the number of media tracks (e.g., non-hint tracks) of the video file 750.

[0189]

[0198] In some examples, the movie fragment 764 may include one or more stream access points (SAPs), such as an IDR picture. Similarly, the MFRA box 766 may provide an indication of the location within the video file 750 of the SAPs. Thus, a temporal subsequence of the video file 750 may be formed from the SAPs of the video file 750. The temporal subsequence may also include other pictures, such as P-frames and / or B-frames, that are dependent on the SAPs. The frames and / or slices of the temporal subsequence may be organized into segments such that frames / slices of the temporal subsequence that depend on other frames / slices of the subsequence may be properly decoded. For example, in a hierarchical organization of data, data used for prediction of other data may also be included in the temporal subsequence.

[0190]

[0199] The video file 750, in this example, also includes a sample description box 768. In particular, the sample description box 768, in this example, is contained within the TRAK box 758. In the example of Figure 7, the sample description box 768 does not include video data encoded according to a codec.

[0191]

[0200] An exemplary sample description box 768 may be defined as follows: Sample entries and box types: "hvc2", "hev2", "lhv1", "lhe1", "lhvC" Container: Sample Description Box ("STSD") · REQUIRED: The "hvc1", "hev1", "hvc2", "hev2", "lhv1", or "lhe1" sample entry is required. · Quantity: There can be one or multiple sample entries.

[0192]

[0201] In this example definition for sample description box 768, when the sample entry name is "lhv1", the default and required value of array_completeness is 4 for arrays of all types of parameter sets and 0 for all other arrays. When the sample entry name is "lhe1", the default value of array_completeness is 0 for all arrays.

[0193]

[0202] 8 is a flowchart illustrating an example method for processing video data in accordance with the techniques of this disclosure. Although described with respect to destination device 116 of FIG. 1, it should be understood that other devices may be configured to perform a method similar to that of FIG.

[0194]

[0203] A destination device 116 may be configured to receive a configuration record for decoding a bitstream of video data (800). The configuration record for the bitstream may include a toolset indication syntax element that includes information identifying a tool from a set of video decoding tools that is needed to decode the bitstream associated with the configuration record. Based on the toolset indication syntax element in the configuration record, the destination device 116 may determine whether to retrieve the bitstream associated with the configuration record (802). The destination device 116 may then retrieve the bitstream (804). The destination device 116 may output the bitstream to a video decoder for decoding (806). The destination device 116 may additionally or alternatively receive a MIME type parameter including a key-value pair, where the key indicates that the MIME type identifies a video decoding tool and the value identifies a tool from the video decoding tools that is needed to decode the bitstream. The bitstream of video data may include one or more parameter sets, and each of the tools identified in the configuration record that are needed to decode the bitstream may be enabled in at least one of the one or more parameter sets.

[0195]

[0204] The toolset indication syntax element is signaled in the configuration box of the file format information. The toolset indication syntax element, which includes information identifying the tools required to decode the bitstream associated with the configuration record, may identify all tools required to decode the bitstream associated with the configuration record. The toolset indication syntax element may be an unsigned 32-bit integer value, where each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

[0196]

[0205] The configuration records may be formatted according to the Essential EVC standard. A configuration record for a bitstream may include a profile syntax element and / or a level syntax element before the toolset indication syntax element. A configuration record for a bitstream may include a chroma format syntax element after the toolset indication syntax element.

[0197]

[0206] In accordance with the above examples, it should be appreciated that some acts or events of any of the techniques described herein may be performed in a different sequence, added, merged, or omitted entirely (e.g., not all described acts or events may be necessary to the practice of the techniques). Moreover, in some examples, acts or events may be performed simultaneously rather than sequentially, for example, through multi-threaded processing, interrupt processing, or multiple processors.

[0198]

[0207] The following clauses represent example implementations of the systems and techniques described above.

[0199]

[0208] Clause 1. A method for processing a video stream or video file, the method comprising: receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record; determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; and based on the decision to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding.

[0200]

[0209] Clause 2. The method of clause 1, further comprising receiving a Multipurpose Internet Mail Extensions (MIME) type parameter including a key-value pair, where the key indicates that the MIME type identifies a video decoding tool and the value identifies a tool needed to decode the bitstream from the video decoding tool.

[0201]

[0210] Clause 3. The method of clause 1 or 2, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0202]

[0211] Clause 4. A method according to any of clauses 1 to 3, wherein a toolset indication syntax element containing information identifying tools required to decode a bitstream associated with the configuration record identifies all tools required to decode a bitstream associated with the configuration record.

[0203]

[0212] Clause 5. The method of any of clauses 1 to 4, wherein the configuration record is formatted in accordance with the Essential Video Coding (EVC) standard.

[0204]

[0213] Clause 6. The method according to any one of clauses 1 to 5, wherein the toolset indication syntax element is signalled in a configuration box of the file format information.

[0205]

[0214] Clause 7. The method of any of clauses 1 to 6, wherein the toolset indication syntax element comprises an unsigned 32-bit integer value.

[0206]

[0215] Clause 8. The method of clause 7, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

[0207]

[0216] Clause 9. The method of any of clauses 1 to 8, wherein the configuration record for the bitstream includes a profile syntax element before the toolset indication syntax element.

[0208]

[0217] Clause 10. The method of any of clauses 1 to 9, wherein the configuration record for the bitstream includes a level syntax element before the toolset indication syntax element.

[0209]

[0218] Clause 11. The method of any of clauses 1 to 10, wherein the configuration record for the bitstream includes a toolset indication syntax element followed by a chroma format syntax element.

[0210]

[0219] Clause 12. A method as described in any of clauses 1 to 11, wherein the configuration record comprises file format level data encapsulating video coding layer (VCL) level encoded media data in a bitstream of video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0211]

[0220] Clause 13. A device for processing video data, the device comprising: a memory; and one or more processors implemented in circuitry and coupled to the memory, configured to receive a configuration record for decoding a bitstream of the video data, where the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record, determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, and based on the decision to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0212]

[0221] Clause 14. The device of clause 13, wherein the one or more processors are further configured to receive a Multipurpose Internet Mail Extensions (MIME) type parameter including a key-value pair, where the key indicates that the MIME type identifies a video decoding tool and the value identifies a tool needed to decode the bitstream from the video decoding tool.

[0213]

[0222] Clause 15. A device as described in clause 13 or 14, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0214]

[0223] Clause 16. A device according to any of clauses 13 to 15, wherein the toolset indication syntax element containing information identifying tools required to decode a bitstream associated with the configuration record identifies all tools required to decode a bitstream associated with the configuration record.

[0215]

[0224] Clause 17. The device of any of clauses 13 to 16, wherein the configuration record is formatted in accordance with the Essential Video Coding (EVC) standard.

[0216]

[0225] Clause 18. A device according to any of clauses 13 to 17, wherein the toolset indication syntax element is signalled in a configuration box of the file format information.

[0217]

[0226] Clause 19. A device according to any of clauses 13 to 15, wherein the toolset indication syntax element comprises an unsigned 32-bit integer value.

[0218]

[0227] Clause 20. The device of clause 19, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

[0219]

[0228] Clause 21. A device according to any of clauses 13 to 20, wherein the configuration record for the bitstream includes a profile syntax element before the toolset indication syntax element.

[0220]

[0229] Clause 22. The device of any of clauses 13 to 21, wherein the configuration record for the bitstream includes a level syntax element before the toolset indication syntax element.

[0221]

[0230] Clause 23. The device of any of clauses 13 to 22, wherein the configuration record for the bitstream includes a chroma format syntax element after the toolset indication syntax element.

[0222]

[0231] Clause 24. A device as described in any of clauses 13 to 23, wherein the configuration record comprises file format level data encapsulating video coding layer (VCL) level encoded media data in a bitstream of video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0223]

[0232] Clause 25. A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to: receive a configuration record for decoding a bitstream of video data, where the configuration record for the bitstream includes a toolset indication syntax element including information that identifies a tool from a set of video decoding tools needed to decode the bitstream associated with the configuration record, determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element, and based on the decision to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0224]

[0233] Clause 26. The computer-readable storage medium of clause 25, wherein the instructions cause one or more processors to receive a Multipurpose Internet Mail Extensions (MIME) type parameter including a key-value pair, where the key indicates that the MIME type identifies a video decryption tool and the value identifies, from the video decryption tool, a tool needed to decrypt the bitstream.

[0225]

[0234] Clause 27. A computer-readable storage medium as described in clause 25 or 26, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0226]

[0235] Clause 28. A computer-readable storage medium according to any of clauses 25 to 27, wherein a toolset indication syntax element containing information identifying tools required to decode a bitstream associated with the configuration record identifies all tools required to decode a bitstream associated with the configuration record.

[0227]

[0236] Clause 29. A computer-readable storage medium as described in any of clauses 25 to 28, wherein the configuration record comprises file format level data encapsulating video coding layer (VCL) level encoded media data in a bitstream of video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

[0228]

[0237] Clause 30. An apparatus for processing a video stream or video file, comprising: means for receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools required to decode the bitstream associated with the configuration record; means for determining whether to retrieve the bitstream associated with the configuration record; means for retrieving the bitstream based on a decision to retrieve the bitstream associated with the configuration record; and means for outputting the bitstream to a video decoder for decoding.

[0229]

[0238] Clause 31. A method for processing video data, comprising: receiving a configuration record for decoding a bitstream of the video data in accordance with an Essential Video Coding (EVC) standard, wherein the configuration record for the bitstream includes a toolset indication syntax element that includes information of all tools required to decode the bitstream associated with the configuration record; determining whether to retrieve a bitstream associated with the configuration record based on the toolset indication syntax element; and based on the decision to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding.

[0230]

[0239] Clause 32. A method for processing video data, comprising: determining a configuration record for a bitstream of the video data generated by a video encoder in accordance with an Essential Video Coding (EVC) standard; and signaling a configuration record, wherein the configuration record for the bitstream includes information for decoding the bitstream, the configuration record including a toolset indication syntax element including information of all tools required to decode the bitstream associated with the configuration record.

[0231]

[0240] Clause 33. The method according to clause 31 or 32, wherein the toolset indication syntax element is signalled in a configuration box of the file format information.

[0232]

[0241] Clause 34. A device for processing video data, the device comprising processing circuitry configured to perform the method described in any one or combination of clauses 1 to 3.

[0233]

[0242] Clause 35. The device of clause 34, further comprising a memory for storing video data.

[0234]

[0243] Clause 36. The device of any of clauses 34 and 35, further comprising a display configured to display the decoded video data.

[0235]

[0244] Clause 37. A device according to any of clauses 34 to 36, wherein the device comprises one or more of a camera, a computer, a mobile device, a broadcast receiver device, or a set-top box.

[0236]

[0245] Clause 38. A computer-readable storage medium storing instructions that, when executed, cause one or more processors to perform the method of any of clauses 31 to 33.

[0237]

[0246] Clause 39. A device for processing video data, comprising means for performing the method according to any of clauses 31 to 33.

[0238]

[0247] In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code and executed by a hardware-based processing unit. A computer-readable medium may include a computer-readable storage medium corresponding to a tangible medium, such as a data storage medium, or a communication medium including any medium that enables the transfer of a computer program from one place to another, for example according to a communication protocol. In this manner, a computer-readable medium may generally correspond to (1) a tangible computer-readable storage medium that is non-transitory, or (2) a communication medium such as a signal or carrier wave. A data storage medium may be any available medium that may be accessed by one or more computers or one or more processors to retrieve instructions, code and / or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

[0239]

[0248] By way of example and not limitation, such computer-readable storage media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Also, any connection is properly referred to as a computer-readable medium. For example, if the instructions are transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but instead cover non-transitory tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0240]

[0249] The instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Thus, the terms "processor" and "processing circuitry" as used herein may refer to any of the above structures, or any other structures suitable for implementing the techniques described herein. Furthermore, in some aspects, the functionality described herein may be provided in dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a composite codec. Also, the techniques may be fully implemented in one or more circuits or logic elements.

[0241]

[0250] The techniques of the present disclosure may be implemented in a wide variety of devices or apparatuses, including wireless handsets, integrated circuits (ICs) or sets of ICs (e.g., chipsets). In this disclosure, various components, modules, or units have been described to highlight functional aspects of devices configured to implement the disclosed techniques, but those components, modules, or units do not necessarily require realization by different hardware units. Rather, as described above, the various units may be combined in a codec hardware unit or provided by a collection of interoperable hardware units, including one or more processors described above, along with suitable software and / or firmware.

[0242]

[0251] Various examples have been described. These and other examples are within the scope of the following claims. The invention as described in the claims of the original application is set forth below. [C1] A method for processing a video stream or a video file, comprising the steps of: receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool, from a set of video decoding tools, that is needed to decode the bitstream associated with the configuration record; determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; retrieving the bitstream associated with the configuration record based on the decision to retrieve the bitstream and outputting the bitstream to a video decoder for decoding. A method comprising: [C2] Receiving a Multipurpose Internet Mail Extensions (MIME) type parameter that contains key-value pairs. Further equipped with The method of claim 1, wherein the key indicates that the MIME type identifies the video decoding tool, and the value identifies the tool needed to decode the bitstream from the video decoding tool. [C3] The method of C1, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C4] The method of C1, wherein the toolset indication syntax element containing information identifying the tools required to decode the bitstream associated with the configuration record identifies all tools required to decode the bitstream associated with the configuration record. [C5] The method of C1, wherein the configuration record is formatted according to the Essential Video Coding (EVC) standard. [C6] The method of C1, wherein the toolset indication syntax element is signaled in a configuration box of file format information. [C7] The method of C1, wherein the toolset indication syntax element comprises an unsigned 32-bit integer value. [C8] The method of C7, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream. [C9] The method of C1, wherein the configuration record for the bitstream includes a profile syntax element before the toolset indication syntax element. [C10] The method of C1, wherein the configuration record for the bitstream includes a level syntax element before the toolset indication syntax element. [C11] The method of C1, wherein the configuration record for the bitstream includes a chroma format syntax element following the toolset indication syntax element. [C12] The method of C1, wherein the configuration record comprises file format level data encapsulating Video Coding Layer (VCL) level encoded media data in the bitstream of the video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C13] A device for processing video data, comprising: Memory, implemented in a circuit and coupled to the memory; receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools required to decode the bitstream associated with the configuration record; determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; retrieving the bitstream associated with the configuration record based on the decision to retrieve the bitstream and outputting the bitstream to a video decoder for decoding. one or more processors configured to A device comprising: [C14] The one or more processors: Receives Multipurpose Internet Mail Extensions (MIME) type parameters that contain key-value pairs The method further comprises: wherein the key indicates that the MIME type identifies the video decoding tool, and the value identifies the tool needed to decode the bitstream from the video decoding tool. [C15] The device of C13, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C16] The device described in C13, wherein the toolset indication syntax element including information identifying the tools required to decode the bitstream associated with the configuration record identifies all tools required to decode the bitstream associated with the configuration record. [C17] The device of C13, wherein the configuration record is formatted according to an Essential Video Coding (EVC) standard. [C18] The device described in C13, wherein the toolset indication syntax element is signaled in a configuration box of file format information. [C19] The device of C13, wherein the toolset indication syntax element comprises an unsigned 32-bit integer value. [C20] The device of C19, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream. [C21] The device of C13, wherein the configuration record for the bitstream includes a profile syntax element before the toolset indication syntax element. [C22] The device of C13, wherein the configuration record for the bitstream includes a level syntax element before the toolset indication syntax element. [C23] The device of C13, wherein the configuration record for the bitstream includes a chroma format syntax element after the toolset indication syntax element. [C24] The device of C13, wherein the configuration record comprises file format level data encapsulating Video Coding Layer (VCL) level encoded media data in the bitstream of the video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C25] A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to: receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool, from a set of video decoding tools, that is needed to decode the bitstream associated with the configuration record; determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; retrieving the bitstream associated with the configuration record based on the decision to retrieve the bitstream and outputting the bitstream to a video decoder for decoding. A computer-readable storage medium for causing a computer to perform the above steps. [C26] The instructions cause the one or more processors to: receiving a Multipurpose Internet Mail Extensions (MIME) type parameter including a key-value pair, where the key indicates that the MIME type identifies the video decoding tool, and the value identifies the tool needed to decode the bitstream from the video decoding tool; A computer-readable storage medium as described in C25. [C27] The computer-readable storage medium of C25, wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C28] The computer-readable storage medium of C25, wherein the toolset indication syntax element including information identifying the tools required to decode the bitstream associated with the configuration record identifies all tools required to decode the bitstream associated with the configuration record. [C29] The computer-readable storage medium of C25, wherein the configuration record comprises file format level data encapsulating Video Coding Layer (VCL) level encoded media data in the bitstream of the video data, wherein the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets. [C30] An apparatus for processing a video stream or video file, comprising: means for receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool, from a set of video decoding tools, required to decode the bitstream associated with the configuration record. means for determining whether to retrieve the bitstream associated with the configuration record based on the toolset indication syntax element; means for retrieving the bitstream associated with the configuration record based on the decision to retrieve the bitstream; means for outputting the bitstream to a video decoder for decoding; An apparatus comprising: < / valuen> < / keyn> < / value2> < / key2> < / value1> < / key1>

Claims

1. 1. A method for storing and distributing a video bitstream conforming to a video coding standard based on a video file format, comprising: receiving a configuration record for decoding a bitstream of video data at a file format level separate from encoded media data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools required to decode the bitstream associated with the configuration record; determining whether the video file can be decoded with a video decoder based on the toolset indication syntax element in the configuration record; based on a determination that the video file can be decoded by the video decoder, retrieving the bitstream associated with the configuration record and outputting the bitstream to the video decoder for decoding; A method comprising:

2. Receiving a Multipurpose Internet Mail Extensions (MIME) type parameter including a key-value pair Further equipped with 2. The method of claim 1 , wherein the key of the key-value pair indicates a MIME type identifying the video decoding tool, and the value of the key-value pair identifies the tool needed to decode the bitstream from the video decoding tool.

3. 2. The method of claim 1 , wherein the bitstream of video data comprises one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

4. 2. The method of claim 1, wherein the toolset indication syntax element containing information identifying the tools needed to decode the bitstream associated with the configuration record identifies all tools needed to decode the bitstream associated with the configuration record.

5. The method of claim 1 , wherein the configuration records are formatted according to an Essential Video Coding (EVC) standard.

6. The method of claim 1 , wherein the toolset indication syntax element is signaled in a configuration box of file format information.

7. The method of claim 1 , wherein the toolset indicating syntax element comprises an unsigned 32-bit integer value.

8. 8. The method of claim 7, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

9. The method of claim 1 , wherein the configuration record for the bitstream includes a profile syntax element before the toolset indication syntax element.

10. The method of claim 1 , wherein the configuration record for the bitstream includes a level syntax element before the toolset indication syntax element.

11. The method of claim 1 , wherein the configuration record for the bitstream includes a chroma format syntax element after the toolset indication syntax element.

12. 2. The method of claim 1, wherein the configuration record at the file format level comprises data encapsulating Video Coding Layer (VCL) level encoded media data in the bitstream of the video data, where the VCL level encoded media data includes one or more parameter sets, and each of the tools identified in the configuration record required to decode the bitstream is enabled in at least one of the one or more parameter sets.

13. An apparatus for storing and distributing a video bitstream conforming to a video coding standard based on a video file format, the apparatus comprising: means for receiving a configuration record for decoding a bitstream of video data, the configuration record being at a file format level separate from encoded media data, wherein the configuration record for the bitstream includes a toolset indication syntax element including information identifying a tool from a set of video decoding tools required to decode the bitstream associated with the configuration record; a means for determining whether to retrieve the bitstream associated with the configuration record, the means using the toolset indication syntax element in the configuration record to determine whether a video file can be decoded with a video decoder. means for retrieving the bitstream associated with the configuration record in response to the determination that the bitstream associated with the configuration record can be decoded by a video decoder; means for outputting the bitstream to a video decoder for decoding; An apparatus comprising:

14. 14. The apparatus of claim 13, further comprising one or more processors implemented in a memory and circuitry, the one or more processors coupled to the memory configured as the means for receiving, the means for determining, the means for retrieving, and the means for outputting, the one or more processors further configured to perform the method of any one of claims 2 to 12.

Images