Storage and transfer 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 video data, wherein the configuration record for the bitstream includes a toolset indication syntax element, and the toolset indication syntax element includes information identifying, from a set of video decoding tools, the tools needed to decode the bitstream associated with the configuration record; determine, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on a determination to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

Description

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

[0002] The present disclosure relates to the storage and transmission of video data. Background Art

[0003] Digital video capabilities can be integrated into a variety of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), portable or desktop computers, tablet computers, e-book readers, digital cameras, digital recording devices, digital media players, video game devices, video game consoles, cellular or satellite radiotelephones, so-called "smart phones", video teleconferencing devices, video streaming devices, and the like. Digital video devices implement video encoding techniques such as those described in the 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 of such standards. By implementing such video encoding techniques, video devices can more efficiently send, receive, encode, decode, and / or store digital video information.

[0004] Video encoding techniques include spatial (intra-picture) prediction and / or temporal (inter-picture) prediction to reduce or eliminate redundancy inherent in a video sequence. For block-based video encoding, a video slice (e.g., a video picture or a portion of a video picture) can be divided 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 reference samples in adjacent blocks in the same picture. Video blocks in an inter-coded (P or B) slice of a picture can be encoded using spatial prediction with reference samples in adjacent blocks in the same picture or temporal prediction with 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] Generally, this disclosure describes techniques for the storage and delivery of a bitstream compliant with a video coding standard based on a file format. This disclosure also describes examples of media format profiles for a video coding standard, as well as delivery 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 (ISO's) Base Media File Format. The ISO's Base Media File Format is known as 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 for use with Multipurpose Internet Mail Extensions (MIME) types. Although described with respect to EVC, ISOBMFF, CMAF, and DASH, the example techniques should not be considered limited.

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

[0007] According to another example of this disclosure, a device for processing video data includes a memory configured to store a video stream, and one or more processors implemented in circuitry, coupled to the memory, and configurable to receive a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element that includes information identifying, from a set of video decoding tools, the tools needed to decode the bitstream associated with the configuration record; determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on a determination to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding.

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

[0009] According to another example of the present disclosure, an apparatus for processing a video stream or a video file includes: 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, and the toolset indication syntax element includes information that identifies, from a set of video decoding tools, the tools required to decode the bitstream associated with the configuration record; means for determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; means for retrieving the bitstream based on the determination to retrieve the bitstream associated with the configuration record; and means for outputting the bitstream to a video decoder for decoding.

[0010] Details of one or more examples are set forth in the accompanying drawings and the following description. Other features, objects, and advantages will be apparent from the specification, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a block diagram illustrating an example video encoding and decoding system that can perform the techniques of the present disclosure.

[0012] Figure 2A and 2B is a conceptual diagram illustrating an example quadtree plus binary tree (QTBT) structure and a corresponding coding tree unit (CTU).

[0013] Figure 3 is a block diagram illustrating an example video encoder that can perform the techniques of the present disclosure.

[0014] Figure 4 is a block diagram illustrating an example video decoder that can perform the techniques of the present disclosure.

[0015] Figure 5 is a conceptual diagram illustrating an example structure of a file according to one or more techniques of the present disclosure.

[0016] Figure 6It is a conceptual diagram showing elements of example multimedia content.

[0017] Figure 7 It is a block diagram showing elements of an example video file.

[0018] Figure 8 It is a flowchart showing an example method for processing video data according to the technology of the present disclosure. Detailed implementation

[0019] The Essential Video Coding (EVC) standard developed by ISO / IEC JTC 1 / SC 29 / WG 11 (MPEG) provides an efficient and low-complexity video coding solution. The EVC elementary stream is structured as Network Abstraction Layer (NAL) units. The storage of NAL units in the ISO Base Media File Format (ISOBMFF) follows principles similar to those of other NAL-structured video formats (e.g., High Efficiency Video Coding (HEVC) and / or Versatile Video Coding (VVC) standards).

[0020] The storage of the EVC elementary stream can be divided into two parts: static information globally used in the elementary stream and dynamic information that may vary for each sample. The Sequence Parameter Set (SPS) and the Picture Parameter Set (PPS) may be part of the information that rarely changes and can be considered static. A set of flags can be used to indicate whether a parameter set is expected to change in the stream. In this case, sample grouping will be defined to indicate samples for which the parameter set does change.

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

[0022] A box can refer to a basic syntax structure in ISOBMFF, including the four-character code box type, the byte count of the box, and the payload. The ISOBMFF file consists of a series of boxes, and a box can contain other boxes. The Movie box ("moov") contains metadata for the continuous media streams present in the file, with each piece of metadata represented as a track in the file.

[0023] The metadata of an orbit can be enclosed in an orbit box (“trak”), while the media content of the orbit can either be enclosed in a media data box (“mdat”) or directly in a separate file. The media content of an orbit includes a series of samples, such as audio or video access units. An access unit is typically a data unit that includes encoded media (e.g., picture) data for a common time instance. A sample is an access unit defined by a specific specification, such as the video encoding specification described herein. A sample entry can provide a description of the corresponding sample.

[0024] ISOBMFF specifies the following types of orbits: a media orbit, which contains a basic media stream; a hint orbit, which either includes media transport instructions or represents a received packet stream; and a timing metadata orbit, which includes time-synchronized metadata.

[0025] This disclosure describes a configuration record for a bitstream of video data, the configuration record including a toolset indication syntax element that includes information identifying tools required to decode the bitstream associated with the configuration record. This disclosure also describes techniques for including Multipurpose Internet Mail Extensions (MIME) type parameters in, for example, an HTTP transmission, the MIME type parameters including key-value pairs. The key can indicate that the MIME type identifies a video decoding tool, and the value can identify the tool required to decode the bitstream. Typically, a tool can be considered required if it is enabled in at least one parameter set for the media stream. By using such a toolset indication syntax element and MIME type, the techniques of this disclosure can advantageously enable a video processing device to determine whether the video decoder of the video processing device can decode a file without having to parse most of the file.

[0026] Figure 1 is a block diagram illustrating an example video encoding and decoding system 100 that can perform the techniques of this disclosure. The techniques of this disclosure generally relate to transcoding (encoding and / or decoding) video data. Generally, video data includes any data for processing video. Thus, video data can include raw, unencoded video, encoded video, decoded (e.g., reconstructed) video, and video metadata (such as signaling data).

[0027] As Figure 1As shown, system 100 includes a source device 102 which, in this example, provides encoded video data to be decoded and displayed by a destination device 116. Specifically, source device 102 provides the video data to destination device 116 via a computer-readable medium 110. Source device 102 and destination device 116 can include any wide range of devices, including desktop computers, notebooks (i.e., laptops) computers, tablet computers, set-top boxes, mobile phones (such as smart phones), televisions, cameras, display devices, digital media players, video game consoles, video streaming devices, etc. In some cases, source device 102 and destination device 116 can be equipped for wireless communication and can thus be referred to as wireless communication devices.

[0028] In Figure 1 the example, source device 102 includes a video source 104, a memory 106, a video encoder 200, and an output interface 108. Destination device 116 includes an input interface 122, a video decoder 300, a memory 120, and a display device 118. In accordance with the present disclosure, source device 102 and destination device 116 can be configured to apply techniques for the storage and delivery of bitstreams compliant with a video coding standard based on a file format (e.g., an Essential Video Coding (EVC) elementary bitstream based on the ISO Base Media File Format (ISOBMFF)). The present disclosure also describes media profiles (e.g., Common Media Application Format (CMAF media profile for EVC)), describes delivery 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 can be utilized by video encoder 200 and video decoder 300. Thus, source device 102 represents an example of a client device configured to perform video encoding and transmission, while destination device 116 represents an example of a destination device configured to receive and decode the encoded video. In other examples, source devices and destination devices can include other components or arrangements. For example, source device 102 can receive video data from an external video source (such as an external camera). Similarly, destination device 116 can interface with an external display device rather than include an integrated display device.

[0029] As Figure 1The system 100 shown is merely an example. Generally, any digital video encoding and / or decoding device may perform techniques for storage and delivery of a bitstream compliant with a video coding standard based on a file format (e.g., an ISOBMFF-based EVC elementary bitstream). This disclosure also describes media profiles (e.g., a CMAF media profile for EVC), describes delivery using DASH, describes encryption requirements, and describes codec parameters to be used with MIME types that may be utilized by video encoder 200 and video decoder 300. Source device 102 and destination device 116 are merely examples of such encoding / decoding devices, where source device 102 generates encoded video data for transmission to destination device 116. This disclosure refers to an "encoding / decoding" device as a device that performs encoding / decoding (encoding and / or decoding) of data. Thus, video encoder 200 and video decoder 300 respectively represent examples of encoding / decoding devices (specifically, a video encoder and a video decoder). In some examples, source device 102 and destination device 116 may operate in a substantially symmetric manner such that each of source device 102 and destination device 116 includes 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, e.g., for video streaming, video replay, video broadcast, or video telephony.

[0030] Generally, video source 104 represents a source of video data (i.e., raw, unencoded video data) and provides a series of consecutive pictures (also referred to as "frames") of video data to video encoder 200, which encodes the data of the pictures. Source device 102 of video source 104 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 another alternative, video source 104 may generate computer graphics-based data as source video, or a combination of live video, archived video, and computer-generated 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 the received order (sometimes referred to as "display order") to an encoding order for encoding. Video encoder 200 may generate a bitstream including the encoded video data. Then, source device 102 may output the encoded video data via output interface 108 to computer-readable medium 110 for reception and / or retrieval by, for example, input interface 122 of destination device 116.

[0031] The memory 106 of the source device 102 and the memory 120 of the destination device 116 represent general 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, e.g., software instructions executable by the video encoder 200 and the video decoder 300, respectively. Although the memory 106 and the memory 120 are shown separately from the video encoder 200 and the video decoder 300 in this example, 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. Further, the memories 106, 120 may store, e.g., encoded video data output from the video encoder 200 and input to the video decoder 300. In some examples, portions of the memories 106, 120 may be allocated as one or more video buffers, e.g., to store raw, decoded, and / or encoded video data.

[0032] The computer-readable medium 110 may represent any type of medium or device capable of transferring the 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 directly send the encoded video data to the destination device 116 in real time, e.g., via a radio frequency network or a computer-based network. According to communication standards such as wireless communication protocols, the output interface 108 may modulate the transmission signal including the encoded video data, and the input interface 122 may demodulate the received transmission signal. The communication medium may include any wireless or wired communication medium, such as the 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 facilitating communication from the source device 102 to the destination device 116.

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

[0034] In some examples, the source device 102 may output the encoded video data to a file server 114 or another intermediate storage device, which 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 downloading. The file server 114 may be any type of server device capable of storing the encoded video data and sending 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 via any standard data connection including an Internet connection. This may include a wireless channel (e.g., Wi-Fi connection), a wired connection (e.g., Digital Subscriber Line (DSL), cable modem, etc.), or a combination of both suitable for accessing the encoded video data stored on the file server 114. The file server 114 and the input interface 122 may be configured to operate according to a streaming protocol, a download transfer protocol, or a combination thereof.

[0035] The output interface 108 and the input interface 122 may represent a wireless transmitter / receiver, a modem, a wired network 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 where the output interface 108 and the input interface 122 include wireless components, the output interface 108 and the input interface 122 may be configured to transmit data such as the encoded video data according to a cellular communication standard (such as 4G, 4G-LTE (Long Term Evolution), Advanced LTA, 5G, etc.). In some examples where the output interface 108 includes a wireless transmitter, the output interface 108 and the input interface 122 may be configured to transmit data such as the encoded video data according to other wireless standards (such as the IEEE 802.11 specification, the IEEE 802.15 specification (e.g., ZigBee TM ), Bluetooth TM standards, 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 an SoC device to perform the functions attributed to the video encoder 200 and / or the output interface 108, and the destination device 116 may include an SoC device to perform the functions attributed to the video decoder 300 and / or the input interface 122.

[0036] The techniques of the present disclosure may be applied to video encoding in support of any of a variety of multimedia applications, such as over-the-air television broadcasts, cable television transmissions, satellite television transmissions, Internet streaming video transmissions (such as via HTTP Dynamic Adaptive Streaming over HTTP (DASH)), digital video encoded onto a data storage medium, decoding of digital video stored on a data storage medium, or other applications.

[0037] The input interface 122 of the destination device 116 receives the encoded video bitstream from a 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 and also used by the video decoder 300, such as syntax elements that describe the characteristics and / or processing of video blocks or other encoded units (e.g., slices, pictures, picture groups, sequences, etc.). The display device 118 displays the decoded pictures of the decoded video data to the 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.

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

[0039] Each of the video encoder 200 and the video decoder 300 may be implemented as any of a variety of suitable encoder and / or decoder circuits, 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, or any combination thereof. When the techniques are implemented partially in software, the device may store the instructions of the software in a suitable non-transitory computer-readable medium and execute the instructions in hardware using one or more processors to perform the techniques of the present 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 a corresponding device. Devices that include the video encoder 200 and / or the video decoder 300 may include integrated circuits, microprocessors, and / or wireless communication devices, such as cellular telephones.

[0040] The video encoder 200 and the video decoder 300 may operate according to other proprietary or industry standards such as the Joint Exploration Test Model (JEM) or ITU-T H.266, also known as Versatile Video Coding (VVC). In the Joint Video Exploration Team (JVET) of ITU-T SG 16 WP3 and ISO / IEC JTC 1 / SC29 / WG 11, 16th meeting: Geneva, CH, October 1 - 11, 2019, JVET-P2001-v14, "Versatile Video Coding (Draft 7)" by Bross et al. (hereinafter referred to as "VVC Draft 7"), a recent draft of the VVC standard is described. The video encoder 200 and the video decoder 300 may operate according to the EVC standard developed by ISO / IEC JTC 1 / SC 29 / WG 11 (MPEG). However, the techniques of the present disclosure are not limited to any particular coding standard.

[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 the 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 perform codec operations on video data represented in the YUV (e.g., Y, Cb, Cr) format. That is, instead of performing codec operations on the red, green, and blue (RGB) data of the samples of a picture, the video encoder 200 and the video decoder 300 may perform codec operations on the luminance and chrominance components, where the chrominance components may include both the red and blue chrominance components. In some examples, the video encoder 200 converts the received RGB - format data into a YUV representation before encoding, and the video decoder 300 converts the YUV representation into the RGB format. Alternatively, pre - processing and post - processing units (not shown) may perform these conversions.

[0042] The present disclosure may generally refer to the codec operations (e.g., encoding and decoding) of a picture as including the process of encoding or decoding the data of the picture. Similarly, the present disclosure may refer to the codec operations of a block of a picture as including the process of encoding or decoding the data of the block, e.g., prediction and / or residual codec. An encoded video bitstream generally includes a series of values representing codec decisions (e.g., codec modes) and syntax elements that partition the picture into blocks. Thus, the reference to performing codec operations on a picture or a block should generally be understood as performing codec operations on the values of the syntax elements that form the picture or the block.

[0043] Various video coding standards define various blocks, sometimes referred to as coding units (CUs), prediction units (PUs), and transform units (TUs). A video encoder (e.g., video encoder 200) divides a coding tree unit (CTU) into CUs according to a quadtree structure. That is, the video encoder divides the CTU and CUs into four equal non-overlapping squares, and each node of the quadtree has zero or four children. A node without children can be referred to as a "leaf node", and the CU of such a leaf node can include one or more PUs and / or one or more TUs. The video encoder can further divide the PUs and TUs. For example, a residual quadtree (RQT) represents the division of TUs, and PUs represent inter-prediction data, while TUs represent residual data. The CU for intra-prediction includes intra-prediction information, such as an intra-mode indication.

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

[0045] In the MTT division structure, quadtree (QT) division, binary tree (BT) division, and one or more types of ternary tree (TT) (also known as trinary tree (TT)) division can be used to divide blocks. Ternary tree or trinary tree division is a way of dividing a block into three sub-blocks. In some examples, ternary tree or trinary tree division divides a block into three sub-blocks without dividing the original block through the center. The division types in MTT (e.g., QT, BT, and TT) can be symmetric or asymmetric.

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

[0047] The video encoder 200 and the video decoder 300 can be configured to use quadtree partitioning, QTBT partitioning, MTT partitioning, or other partitioning structures. For purposes of explanation, the description of the techniques of the present disclosure is presented with respect to QTBT partitioning. However, it should be understood that the techniques of the present disclosure can also be applied to video encoders configured to use quadtree partitioning or other types of partitioning.

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

[0049] In some examples, a tile can be divided into multiple bricks, and each brick can include one or more CTU rows in the tile. A tile that is not divided into multiple bricks can also be referred to as a brick. However, a brick that is a proper subset of a tile cannot be referred to as a tile.

[0050] Bricks in a picture can also be arranged in slices. A slice can be an integer number of bricks of a picture that can be uniquely contained in a single network abstraction layer (NAL) unit. In some examples, a slice includes several complete tiles or a contiguous sequence of complete bricks that includes only one tile.

[0051] The present disclosure can interchangeably use "N x N" and "N by N" to refer to the sample dimensions of a block (such as a CU or other video block) in terms of vertical and horizontal dimensions, e.g., 16x16 samples or 16 by 16 samples. Generally, a 16x16 CU will have 16 samples in the vertical direction (y = 16) and 16 samples in the horizontal direction (x = 16). Similarly, an N x N 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 can be arranged in rows and columns. Additionally, a CU does not have to have the same number of samples in the horizontal direction as in the vertical direction. For example, a CU can contain N x M samples, where M does not necessarily equal N.

[0052] The video encoder 200 encodes video data of a CU representing prediction and / or residual information and other information. The prediction information indicates how the CU is to be predicted to form a prediction block of the CU. The residual information generally represents the sample-by-sample difference between the CU before encoding and the prediction block.

[0053] To predict a CU, the video encoder 200 can generally form a prediction block of the CU through inter - frame prediction or intra - frame prediction. Inter - frame prediction generally refers to predicting the CU from the data of previously encoded pictures, while intra - frame prediction generally refers to predicting the CU from the previously encoded data of the same picture. To perform inter - frame prediction, the video encoder 200 can use one or more motion vectors to generate a prediction block. The video encoder 200 can generally perform a motion search to identify a reference block that closely matches the CU, for example, in terms of the difference between the CU and the reference block. The video encoder 200 can calculate a difference metric using the sum of absolute differences (SAD), the sum of squared differences (SSD), the mean absolute difference (MAD), the mean squared difference (MSD), or other such difference calculations to determine whether the reference block closely matches the current CU. In some examples, the video encoder 200 can use uni - directional prediction or bi - directional prediction to predict the current CU.

[0054] Some video coding standards also provide an affine motion compensation mode, which can be regarded as an inter - frame prediction mode. In the affine motion compensation mode, the video encoder 200 can determine two or more motion vectors representing non - translational motion (such as zooming in or out, rotation, perspective motion, or other irregular motion types).

[0055] To perform intra - frame prediction, the video encoder 200 can select an intra - frame prediction mode to generate a prediction block. For example, the video encoder 200 can utilize 67 or some other number of intra - frame prediction modes, including various directional modes as well as the planar mode and the DC mode. Generally, the video encoder 200 selects an intra - frame prediction mode that describes the neighboring samples of the current block (e.g., the block of the CU) and predicts the samples of the current block from the neighboring samples. Assuming the video encoder 200 compiles and decodes CTUs and CUs in raster scan order (from left to right, top to bottom), such samples can generally be located above, in the upper - left, or to the left of the current block in the same picture as the current block.

[0056] The video encoder 200 encodes the data representing the prediction mode of the current block. For example, for an inter - frame prediction mode, the video encoder 200 can encode the data indicating which one of the various available inter - frame prediction modes is used and the motion information for the corresponding mode. For uni - directional or bi - directional inter - frame prediction, for example, the video encoder 200 can use advanced motion vector prediction (AMVP) or the merge mode to encode the motion vectors. The video encoder 200 can use a similar mode to encode the motion vectors for the affine motion compensation mode.

[0057] After prediction, such as intra prediction or inter prediction of a block, the video encoder 200 may compute residual data for the block. The residual data, such as a residual block, represents a sample-by-sample difference between the block and a predicted block of the block formed using a corresponding prediction mode. The video encoder 200 may apply one or more transforms to the residual block to produce transformed data in a transform domain rather than a 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 after the first transform, such as a mode-dependent non-separable second-order transform (MDNSST), a signal-dependent transform, a Karhunen-Loeve transform (KLT), etc. The video encoder 200 produces transform coefficients after applying one or more transforms.

[0058] As described above, after performing any transform to produce transform coefficients, the video encoder 200 may perform quantization of the transform coefficients. Quantization generally refers to the process of quantizing the transform coefficients to possibly reduce the amount of data used to represent the transform coefficients, which provides further compression. By performing the 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 down 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.

[0059] After quantization, the video encoder 200 may scan the transform coefficients to produce a one-dimensional vector from a two-dimensional matrix including the quantized transform coefficients. The scan may be designed to place higher-energy (and thus lower-frequency) transform coefficients at the front of the vector and lower-energy (and thus higher-frequency) transform coefficients at the back of the vector. In some examples, the video encoder 200 may scan the quantized transform coefficients using a predefined scan order to produce a serialized vector, and then entropy code 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 the one-dimensional vector, the video encoder 200 may entropy code the one-dimensional vector, for example, according to context-adaptive binary arithmetic coding (CABAC). The video encoder 200 may also entropy code the values of syntax elements that describe metadata associated with the encoded video data for use by the video decoder 300 when decoding the video data.

[0060] To perform CABAC, the video encoder 200 may assign a context to a symbol to be sent in a context model. The context may relate to, for example, whether an adjacent value of the symbol is a zero value. Probability determination may be based on the context assigned to the symbol.

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

[0062] In this way, the video encoder 200 may generate a bitstream including the encoded video data, for example, describing the partitioning of a picture into blocks (e.g., CUs) and syntax elements for prediction and / or residual information for the blocks. Eventually, the video decoder 300 may receive the bitstream and decode the encoded video data.

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

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

[0065] The present disclosure may generally relate to "signaling" certain information, such as syntax elements. The term "signaling" generally refers to the communication of values of syntax elements and / or other data used to decode encoded video data. That is, video encoder 200 may signal the value of a syntax element in a bitstream. Generally, signaling refers to generating a value in a bitstream. As described above, source device 102 may transmit the bitstream to destination device 116 either substantially in real time or not in real time, such as may occur when storing the syntax elements in storage device 112 for later retrieval by destination device 116.

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

[0067] An EVC sample contains access units, as defined in ISO / IEC 23094-1, Clause 3.1: Information technology – Generic video coding – Part 1: Essential video coding. In EVC, there may be a bitstream conforming to the EVC specification order, and there may be certain restrictions. The canonical stream format is an EVC elementary stream that, 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, Clause 4.3.2, also satisfies the following conditions:

[0068] a. Access unit delimiter NAL unit: The constraints followed by the access unit delimiter NAL unit are defined in ISO / IEC 23094-1.

[0069] b. SPS and PPS: The SPS or PPS to be used in a picture may (and in some examples must) be sent before or in the samples of the picture that contains it. The SPS and PPS with at least an id equal to 0 may be stored in the sample entry of the track containing the EVC elementary stream.

[0070] c. APS: The APS to be used in a slice may (in some examples must) be sent before the VCL NAL unit that contains the slice. The APS may be stored in the sample entry and / or in the sample.

[0071] d. SEI messages: SEI messages of a declarative nature may be stored in the sample entry; there is no provision for removing such SEI messages from the sample.

[0072] e. Padding data. Video data is naturally represented in a file format with variable bitrate and should be padded when needed for transmission.

[0073] When operating the HRD in a Constant Bit Rate (CBR) mode as specified in Annex C of ISO / IEC 23094-1, the deletion or addition of padding data NAL units, start codes, SEI messages, or padding data SEI messages may change the bitstream characteristics with respect to conformance to the Hypothetical Reference Decoder (HRD).

[0074] The following is the EVC decoder configuration record and description. In some examples, the video decoder 300 may be configured according to the EVC decoder configuration. As part of the description of the EVC decoder configuration description, the following specifies the decoder configuration information for ISO / IEC 23094-1 video content.

[0075] This record contains a version field. If the version number cannot be recognized, the file format parser (e.g., reader) may (e.g., should) not attempt to decode this record or its applicable stream.

[0076] The compatible extensions of this record may extend it and may not change the configuration version code. The reader may ignore unrecognized data that is outside the definition of the data that the reader is configured to parse.

[0077] The values of 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 (and in some examples, should be) valid for all parameter sets (referred to as "all parameter sets") that are active when decoding the stream. Specifically, the following restrictions may apply:

[0078] a. The profile indication profile_idc may (e.g., should) indicate the profile to which the stream associated with this configuration record conforms. If the SPS is marked with a different profile, it may be necessary to examine the stream to determine which profile (if any) the entire stream conforms to. If the entire stream is not examined, or if the examination reveals that the entire stream does not conform to any profile, the entire stream may (e.g., should) be split into two or more sub-streams with separate configuration records in which these rules can be satisfied.

[0079] b. The level indication level_idc may (e.g., should) indicate the capability level that is equal to or greater than the highest level indicated in all parameter sets of this configuration record.

[0080] c. pic_width_in_luma_samples and pic_height_in_luma_samples may (e.g., shall) contain the highest values of all parameter sets of this configuration record.

[0081] d. The toolset indication toolset_idc may (e.g., shall) signal all tools required to decode the stream associated with this configuration record. This tool flag may (e.g., shall) comply with the conformance requirements provided in Table A.6 of ISO / IEC 23094-1 (reproduced below) and may (e.g., shall) be the same as the toolset_idc field signaled in the SPS.

[0082] e. The values of chroma_format_idc in all parameter sets may (e.g., shall) be the same.

[0083] f. The values of bit_depth_luma_minus8 in all parameter sets may (e.g., shall) be the same.

[0084] g. The values of bit_depth_chroma_minus8 in all parameter sets may (e.g., shall) be the same.

[0085] The EVC decoder configuration record provides explicit indication of the chroma format and bit depth used by the EVC video elementary stream. Such information of each type may (e.g., shall) be the same in all parameter sets (if any) 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.

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

[0087] If stored in the sample entry, the length field may be used in each sample to indicate the NAL unit and the length of the parameter set it contains. In some examples, the arrays are in the order of SPS, PPS, APS, SEI.

[0088] Table A.6 of ISO / IEC 23094-1 is as follows:

[0089]

[0090]

[0091]

[0092] The following describes the syntax used by the video encoder 200 and the video decoder 300.

[0093]

[0094]

[0095] The following description explains the semantics used to define 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 the matching values of the fields in the PPS that hold all parameter sets of the configuration record. The annotation "(32)" indicates that the syntax element toolset_idc is 32 bits. These 32 bits can include one-bit flags, each corresponding to a specific tool, or in some cases, multiple bits among these 32 bits can, for example, correspond to a combination of tools or a selection of tools from the toolset.

[0096] When the value of the sps_in_stream field is "0", the syntax elements pic_width_in_luma_samples and pic_height_in_luma_samples contain the maximum values of the fields in all SPSs of this configuration record. When the value of the sps_in_stream field is "1", these syntax elements can contain the maximum values of the fields in all SPSs of this configuration record and all SPSs in the stream. If the maximum values of these fields in the SPSs of all parameter sets in this record are not indicated by this field when the value of the sps_in_stream field is "0", or if the values of these fields in the SPSs in the stream are greater than the maximum values of the fields in this record when the value of the sps_in_stream field is "1", then the value "0" can be (e.g., should be) used.

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

[0098] The syntax element numArrays indicates the number of NAL unit arrays of the indicated type. The syntax element NAL_unit_type indicates the type of NAL units in the subsequent array (which may (e.g., should) 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.

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

[0100] Video files according to the ISO base media file format and its extensions store data in a series of objects, which are called "boxes". The ISO base media file format is described below, including the EVC video stream definition and example entry names and formats.

[0101] a. Sample entries and box types: 'evc1', 'evcC'

[0102] b. Container: Sample Table Box ('stb1')

[0103] c. Mandatory: The 'evc1' sample entry is mandatory

[0104] d. Quantity: There may be one or more sample entries

[0105] The EVC visual sample entry may (e.g., should) contain an EVC configuration box defined as follows. This includes the EVCDecoderConfigurationRecord.

[0106] The optional BitRateBox may appear in the EVC visual sample entry to signal the bitrate information of the EVC video stream.

[0107] When permitted by the ISO Base Media File Format specification, multiple sample entries can be used to indicate video sections using different configurations or parameter sets.

[0108] When the sample entry name is 'evc1', the stream to which this sample entry applies can (e.g., should) 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.

[0109] The 'evc1' sample entry allows parameter sets to be stored both in the sample entry and in the stream. When sps_in_stream, pps_in_stream, and aps_in_stream are set to 0, it indicates that the arrays of NAL units of the corresponding types are complete.

[0110] The following is a set of syntax examples for the configuration boxes of the file format.

[0111]

[0112] The following is a set of example semantics for the syntax as described above.

[0113] The Compressorname in the base class VisualSampleEntry indicates the name of the compressor recommended to be used with the value "\012EVC codec" (\012 is 10, the length of the string in bytes). The EVCDecoderConfigurationRecord is defined in Section 5.3.3 (e.g., such as but not limited to ISO / IEC 23904-1).

[0114] The parameter sets are described below. As an overview, at least the initial SPS and PPS with id equal to 0 should (e.g., should) 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.

[0115] Samples carrying parameter sets can (e.g., should) belong to the sample group corresponding to the type of that parameter set. Three sample group_type 'pss1' are defined in this specification. Another grouping type parameter is used to distinguish between SPS, PPS, and APS, where'sps1' identifies the sample group of samples carrying SPS, 'pps1' identifies the sample group of samples carrying PPS, and 'aps1' identifies the sample group of samples carrying APS.

[0116] The sample group entries for parameter sets including the definitions are described below.

[0117] a. Grouping type: 'pss1'

[0118] b. Container: Sample grouping description box ('sgpd')

[0119] c. Mandatory: None

[0120] d. Quantity: Zero or more

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

[0122] Some syntax for parameter set sample grouping entries is described below.

[0123] class PSSSampleEntry() extends VisualSampleGroupEntry('pss1')

[0124] {

[0125] }

[0126] A synchronization example is described below. Synchronization samples in the 'evc1' track can (e.g., should) contain VCL NAL units that indicate that the decoded picture with nuh_temporal_id equal to 0 in the sample is an Instantaneous Decoding Refresh (IDR) picture.

[0127] Table 1 indicates the mapping between EVC VCL NAL unit types, ISOBMFF synchronization sample status, and SAP types as recorded in ISOBMFF.

[0128] Table 1 - Mapping of Synchronization Sample Status and SAP Types to NAL Unit Types

[0129] NAL Unit Type ISOBMFF Sync Sample Status DASH SAP Type IDR_N_LP True 1

[0130] The following is the definition of subsamples in EVC. To use the SubSampleInformationBox (8.7.7 of ISO / IEC 14496-12) in an EVC stream, the subsamples are defined based on the values of the flag fields of the subsample information box specified as follows. The presence of this box is optional; however, if it is present in a track containing EVC data, the 'codec_specific_parameters' field in the box can (e.g., should) have the semantics defined here.

[0131] The flags specify the type of subsample information given in this box as follows:

[0132] a.0: NAL unit-based subsamples: A subsample consists of one or more consecutive NAL units.

[0133] b.1: Tile-based subsamples: A subsample consists of the VCL NAL units of all CTUs of a tile, together with any associated non-VCL NAL units (if any).

[0134] c.2: Slice-based subsamples: A subsample consists of a slice (i.e., a VCL NAL unit) and the associated non-VCL NAL units (if any).

[0135] d. Other values of the flag are reserved.

[0136] The subsample_priority field may (e.g., should) be set to the value according to the specification of this field in ISO / IEC 14496-12.

[0137] The discardable field may (e.g., should) be set to 1 only if the sample can still be decoded if this subsample is discarded (e.g., a subsample consisting of SEI NAL units).

[0138] When the first byte of the NAL unit is included in the subsample, the previous length field may (e.g., should) also be included in the same subsample.

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

[0140]

[0141] tile_col_idx for tile-based subsamples, this parameter indicates the 0-based index of the tile column of the tile containing this subsample.

[0142] tile_row_idx for tile-based subsamples, this parameter indicates the 0-based index of the tile row of the tile containing this subsample.

[0143] The CMAF media profile is described below. ISO / IEC 23000-19 Common Media Application Format (CMAF) defines structural constraints on ISOBMFF files outside of ISO / IEC 14496-12, for purposes such as encrypted adaptive streaming or delivery of files. Conformance to these structural constraints is signaled by the presence of the CMAF-defined structural brand in the FileTypeBox.

[0144] If an ISO BMFF track uses the flag 'cevc', it is called a CMAF EVC track and the following constraints apply (defining the CMAF media profile for EVC):

[0145] a. It may (e.g., should) use the 'evc1' sample entry defined in Clause 6.3 of ISO / IEC 23094-1.

[0146] b. The track may (e.g., should) conform to the general CMAF track constraints in Clause 7 of ISO / IEC 23000-19

[0147] c. The track may (e.g., should) conform to the general CMAF video track constraints in Clause 9 of ISO / IEC 23000-19

[0148] If EVC media is provided in the CMAF exchange set, then

[0149] a. Each CMAF track in the CMAF exchange set may (e.g., should) conform to the CMAF EVC track

[0150] b. The CMAF exchange set may (e.g., should) conform to the general CMAF exchange set constraints in Clause 7 of ISO / IEC 23000-19, and

[0151] c. The general CMAF video track exchange set constraints defined in Clause 9 of ISO / IEC 23000-19.

[0152] A CMAF exchange set that follows these requirements is defined as the CMAF EVC media profile 'cevc'. Encryption of CMAF EVC tracks and CMAF EVC exchange sets may (e.g., should) conform to Clause 8 of ISO / IEC 23000-19 using the 'cenc' AES-CTR scheme or the 'cbcs' AES-CBC subsample mode encryption scheme specified in Clauses 10.1 and 10.4 of ISO / IEC 23001-7 respectively.

[0153] Furthermore, if the 'cbcs' mode of generic encryption using mode encryption as defined in Clause 9.6 of ISO / IEC 23001-7 is used, then a mode block length of 10 and an encryption:skip mode of 1:9 may (e.g., should) be applied (e.g., as described in Clause 10.4 of ISO / IEC 23001-7).

[0154] The mapping to DASH delivery is described below. If media encoded with EVC is provided in the DASH media representation of an adaptation set, the adaptation set can (e.g., should) conform to the DASH profile of CMAF as defined in ISO / IEC 23009-1. The following parameters can (e.g., should) appear at the "adaptation set" level and on the set:

[0155] a. @codecs is set according to Annex A

[0156] b. @mimeType is set to be compatible with "video / mp4 profile='cevc' "

[0157] The following is an explanation of the sub-parameters of the 'codes' parameter for the MIME type. DASH and other applications require the defined values of the codec parameters specified in IETF RFC 6381 for ISO BMFF media tracks. The codec parameter string for the EVC codec is as follows: <Example entry 4CC>. <key1> <value1> . <key2> <value2> ..... <keyn> <valuen>

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

[0159] If a specific key is not provided, a specified default value will be applied, or if not declared (n / a), the value of the key is unknown.

[0160] Definition of the initial set of keys and values defined for EVC in Table 2

[0161]

[0162]

[0163] For example, codecs = "evc1.vprf3.vlev51.vtoo03FF.vbit20.vcss420.vcpr09.vtrc16.vmac09.vsar01” represents the EVC main profile, level 5.1, with 4:2:0 chroma subsampling with (0,0) luminance samples juxtaposed, a restricted toolset, ITU-R BT.2100 color primaries, ITU-R BT.2100PQ transfer characteristics, ITU-R BT.2100 YCbCr color matrix, and a sample aspect ratio of 1:1. If an evc1 sample entry is recognized, all keys in Table 2 can be (e.g., must be) recognized. If a key cannot be recognized, the key-value pair is ignored. In some examples, other keys can be defined, such as 2CC only.

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

[0165] According to the above technique, the destination device 116 can be configured to receive a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element that includes identifying, from a set of video decoding tools, the tools required to decode the bitstream associated with the configuration record; determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on the determination to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding. The destination device 116 can additionally or alternatively receive a MIME type parameter that includes key-value pairs, wherein the key indicates that the MIME type identifies a video decoding tool and the value identifies, from the video decoding tools, the tools required to decode the bitstream. The bitstream of video data can include one or more parameter sets, and each tool identified as required to decode the bitstream in the configuration record can be enabled in at least one of the one or more parameter sets.

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

[0167] The configuration record can be formatted according to the necessary EVC standard. The configuration record for the bitstream can include a profile syntax element and / or a level syntax element before the toolset indication syntax element. The configuration record for the bitstream can include a chroma format syntax element after the toolset indication syntax element.

[0168] Figure 2A and 2B It is a conceptual diagram showing an example quadtree plus binary tree (QTBT) structure 130 and a corresponding coding tree unit (CTU) 132. Solid lines represent quadtree splits, while dashed lines represent binary tree splits. In each split (i.e., non-leaf) node of the binary tree, a flag is signaled to indicate which split type (i.e., horizontal or vertical) is used. In this example, 0 indicates a horizontal split and 1 indicates a vertical split. For quadtree splits, since a quadtree node splits a block horizontally and vertically into 4 sub-blocks of equal size, there is no need to indicate the split type. Thus, the video encoder 200 can encode syntax elements (such as split information) at the region tree level (i.e., solid lines) of the QTBT structure 130 and syntax elements (such as split information) at the prediction tree level (i.e., dashed lines) of the QTBT structure 130, and the video decoder 300 can decode them. The video encoder 200 can encode video data (such as prediction and transform data) of the CUs represented by the terminal leaf nodes of the QTBT structure 130, and the video decoder 300 can decode them.

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

[0170] The root node of the QTBT structure corresponding to a CTU can have four child nodes at the first level of the QTBT structure, and each of them can be divided according to quadtree partitioning. That is, the nodes at the first level are leaf nodes (without child nodes) or have four child nodes. An example of the QTBT structure 130 represents such a node as including a parent node and child nodes with solid branch lines. If the node at the first level is not larger than the maximum allowable binary tree root node size (MaxBTSize), then the node can be further divided by the corresponding binary tree. The binary tree splitting of a node can be iterative until the nodes generated by the splitting reach the minimum allowable binary tree leaf node size (MinBTSize) or the maximum allowable binary tree depth (MaxBTDepth). An example of the QTBT structure 130 represents such a node as having dashed lines for the branches. The binary tree leaf nodes are called coding units (CUs), which are used for prediction (e.g., intra-picture or inter-picture prediction) and transformation without any further partitioning. As discussed above, a CU can also be referred to as a "video block" or a "block".

[0171] In an example of the QTBT partitioning structure, the CTU size is set to 128x128 (luminance samples and two corresponding 64x64 chrominance samples), MinQTSize is set to 16x16, MaxBTSize is set to 64x64, MinBTSize (for both width and height) is set to 4, and MaxBTDepth is set to 4. First, quadtree partitioning is applied to the CTU to generate quadtree leaf nodes. The size of the quadtree leaf nodes can range from 16x16 (i.e., MinQTSize) to 128x128 (i.e., the CTU size). If the quadtree leaf node is 128x128, then since the size exceeds MaxBTSize (which is 64x64 in this example), this quadtree leaf node will not be further split by the binary tree. Otherwise, the quadtree leaf node will be further divided by the binary tree. Therefore, the quadtree leaf node is also the root node of the binary tree, and the binary tree depth is 0. When the binary tree depth reaches MaxBTDepth (4 in this example), further splitting is not allowed. When the width of a binary tree node is equal to MinBTSize (4 in this example), it means that further horizontal splitting is not allowed. Similarly, a binary tree node with a height equal to MinBTSize means that this binary tree node is not allowed to be further vertically split. As described above, the leaf nodes of the binary tree are called CUs, and they are further processed according to prediction and transformation without further partitioning.

[0172] Figure 3 is a block diagram of an example video encoder 200 that can perform the techniques of the present disclosure. Figure 3 It is provided for illustrative purposes and should not be considered a limitation of the technologies widely illustrated and described in this disclosure. For illustrative purposes, this disclosure describes video encoder 200 according to the technologies of JEM, EVC, VVC (ITU-T H.266, under development), and HEVC (ITU-T H.265). However, the technologies of this disclosure can be performed by video encoding devices configured for other video coding standards.

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

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

[0175] In the present disclosure, a reference to the video data memory 230 should not be construed as being limited to a memory internal to the video encoder 200 (unless so specifically described), or to a memory external to the video encoder 200 (unless so specifically described). Rather, a reference to the video data memory 230 should be understood as a reference memory that stores video data received by the video encoder 200 for encoding (e.g., video data of a current block to be encoded). Figure 1 The memory 106 can also provide temporary storage of outputs from various units of the video encoder 200.

[0176] illustrates Figure 3 various units to assist in understanding the operations performed by the video encoder 200. These units can 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 in terms of the operations that can be performed. A programmable circuit refers to a circuit that can be programmed to perform various tasks and provides flexible functionality in terms of the operations that can be performed. For example, a programmable circuit can run software or firmware that causes the programmable circuit to operate in a manner defined by the instructions of the software or firmware. A fixed-function circuit can run software instructions (e.g., to receive parameters or output parameters), but the type of operations performed by the fixed-function circuit is generally immutable. In some examples, one or more units can be different circuit blocks (fixed-function or programmable), and in some examples, one or more units can be integrated circuits.

[0177] The video encoder 200 can include an arithmetic logic unit (ALU), a basic function unit (EFU), digital circuits, analog circuits, and / or a programmable core formed by programmable circuits. In an example where software run by programmable circuits is used to perform the operations of the video encoder 200, the memory 106 ( Figure 1 ) can store the instructions (e.g., object code) of the software received and run by the video encoder 200, or another memory (not shown) in the video encoder 200 can store such instructions.

[0178] The video data memory 230 is configured to store received video data. The video encoder 200 can retrieve a picture 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 can be the original video data to be encoded.

[0179] 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 to perform video prediction according to other prediction modes. As an example, the mode selection unit 202 may include a palette unit, a 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.

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

[0181] The video encoder 200 may divide a picture retrieved from the video data memory 23 into a series of CTUs and encapsulate one or more CTUs in a slice. The mode selection unit 202 may divide the CTUs of the picture according to a tree structure such as the QTBT structure or the quadtree structure described above. As described above, the video encoder 200 may form one or more CUs by dividing CTUs according to a tree structure. Such CUs may also generally be referred to as "video blocks" or "blocks".

[0182] Generally, 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 predicted 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 encoded 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, for example, according to the sum of absolute differences (SAD), the sum of squared differences (SSD), the mean absolute difference (MAD), the mean squared difference (MSD), etc. The motion estimation unit 222 may generally perform these calculations using the sample-by-sample differences between the current block and the considered reference block. 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.

[0183] 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 the current picture. Then, the motion estimation unit 222 may provide the motion vectors to the motion compensation unit 224. For example, for uni-directional inter prediction, the motion estimation unit 222 may provide a single motion vector, and for bi-directional inter prediction, the motion estimation unit 222 may provide two motion vectors. Then, the motion compensation unit 224 may use the motion vectors to generate a prediction block. For example, the motion compensation unit 224 may use the motion vectors to retrieve the data of the reference block. As another example, if the motion vectors have fractional sample precision, the motion compensation unit 224 may interpolate the values of the prediction block according to one or more interpolation filters. In addition, for bi-directional inter prediction, the motion compensation unit 224 may retrieve the data of two reference blocks identified by the respective motion vectors and combine the retrieved data, for example, by per-sample averaging or weighted averaging.

[0184] As another example, for intra prediction or intra prediction coding / decoding, the intra prediction unit 226 may generate a prediction block from samples adjacent to the current block. For example, for the directional mode, the intra prediction unit 226 may generally mathematically combine the values of adjacent samples and fill the calculated values along a defined direction on the current block to produce a prediction block. As another example, for the DC mode, the intra prediction unit 226 may calculate the average value of the adjacent samples of the current block and generate a prediction block to include the obtained average value for each sample of the prediction block.

[0185] The mode selection unit 202 provides the prediction block to the residual generation unit 204. The residual generation unit 204 receives the original 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 the sample-by-sample difference between the current block and the prediction block. The resulting sample-by-sample difference defines the residual block of the current block. In some examples, the residual generation unit 204 may also determine the differences between the sample values in the residual block to generate the residual block using residual differential pulse code modulation (RDPCM). In some examples, one or more subtractor circuits that perform binary subtraction may be used to form the residual generation unit 204.

[0186] In an example where the mode selection unit 202 divides a CU into PUs, each PU may be associated with a luminance prediction unit and a corresponding chrominance prediction unit. The video encoder 200 and the video decoder 300 may support PUs of various sizes. As indicated above, the size of a CU may refer to the size of the luminance coding block of the CU, and the size of a PU may refer to the size of the luminance prediction unit of the PU. Assuming that the size of a specific CU is 2Nx2N, the video encoder 200 may support PU sizes of 2Nx2N or NxN for intra prediction, and 2Nx2N, 2NxN, Nx2N, NxN, or similar symmetric PU sizes for inter prediction. The video encoder 200 and the video decoder 300 may also support asymmetric partitioning of PU sizes of 2NxnU, 2NxnD, nLx2N, and nRx2N for inter prediction.

[0187] In an example where the mode selection unit 202 no longer further divides a CU into PUs, each CU may be associated with a luminance coding block and a corresponding chrominance coding block. As described above, the size of a CU may refer to the size of the luminance 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.

[0188] For other video coding techniques such as intra block copy mode coding / decoding, affine mode coding / decoding, and linear model (LM) mode coding / decoding, as a few examples, the mode selection unit 202 generates a prediction block of the current block being encoded via a corresponding unit associated with the coding / decoding technique. In some examples, such as palette mode coding, the mode selection unit 202 may not generate a prediction block, but instead generate a syntax element indicating the way to reconstruct a block based on the selected palette. In such a mode, the mode selection unit 202 may provide these syntax elements to the entropy coding unit 220 for encoding.

[0189] As described above, the residual generation unit 204 receives the video data of the current block and the corresponding prediction block. Then, the residual generation unit 204 generates a residual block of the current block. To generate the residual block, the residual generation unit 204 calculates the sample-by-sample difference between the prediction block and the current block.

[0190] The 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"). The transform processing unit 206 may apply various transforms to the residual block to form a transform coefficient block. For example, the transform processing unit 206 may apply a discrete cosine transform (DCT), an orientation transform, a Karhunen-Loeve transform (KLT), or a conceptually similar transform to the residual block. In some examples, the transform processing unit 206 may perform multiple transforms on the residual block, such as a primary transform and a secondary transform (such as a rotation transform). In some examples, the transform processing unit 206 does not apply a transform to the residual block.

[0191] The quantization unit 208 may quantize the transform coefficients in the transform coefficient block to produce a quantized transform coefficient block. The quantization unit 208 may quantize the transform coefficients of the transform coefficient block according to the 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 information loss, and thus, the quantized transform coefficients may have lower precision than the original transform coefficients generated by the transform processing unit 206.

[0192] The inverse quantization unit 210 and the inverse transform processing unit 212 may apply inverse quantization and inverse transform, respectively, to the quantized transform coefficient block to reconstruct the residual block from the transform coefficient block. The reconstruction unit 214 may generate a reconstructed block corresponding to the current block (although there may be some degree of distortion) based on the reconstructed residual block and the prediction block generated by the mode selection unit 202. For example, the reconstruction unit 214 may add the samples of the reconstructed residual block to the corresponding samples of the prediction block generated by the mode selection unit 202 to generate the reconstructed block.

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

[0194] Video encoder 200 stores the reconstructed blocks in DPB 218. For example, in an example where the operation of filter unit 216 is not required, reconstruction unit 214 may store the reconstructed blocks into DPB 218. In an example where the operation of filter unit 216 is required, filter unit 216 may store the filtered reconstructed blocks into DPB 218. Motion estimation unit 222 and motion compensation unit 224 may retrieve a reference picture from DPB 218, which is formed by the reconstructed (and potentially filtered) blocks, for performing inter prediction on blocks of a subsequent encoded picture. Additionally, intra prediction unit 226 may use the reconstructed blocks of the current picture in DPB 218 to perform intra prediction on other blocks in the current picture.

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

[0196] Video encoder 200 may output a bitstream including the entropy-coded syntax elements required for reconstructing slices or blocks of a picture. In particular, entropy coding unit 220 may output the bitstream.

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

[0198] In some examples, operations performed on a luma coding block need not be repeated for a chroma coding block. As an example, operations for identifying a motion vector (MV) and a reference picture for a luma coding block need not be repeated to identify an MV and a reference picture for a chroma block. Instead, an MV for a luma coding block can be scaled to determine an MV for a chroma block, and the reference picture can be the same. As another example, intra prediction processing can be the same for luma coding blocks and chroma coding blocks.

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

[0200] In some examples, a source device can 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, including information for decoding the bitstream. The configuration record can include a toolset indication syntax element (e.g., toolset_idc). The configuration record can be provided at a file format level (e.g., as file format level data) or at a level of media data encoded at an encapsulated video coding layer (VCL) level. For example, as discussed herein, the configuration record can be included in a configuration box of a media file, where the configuration box is separate from a movie fragment box or other box including the actual encoded media data. In some examples, the toolset indication syntax element can include information about all tools needed to decode the bitstream associated with the configuration record. The toolset indication syntax element can indicate tools that match another toolset_idc field signaled in a sequence parameter set (SPS).

[0201] In some examples, the toolset indication syntax element can be considered to include tools necessary to play a file in a sample entry, which is part of the encoded parameters. To enable the toolset indication syntax element, an encoding scheme for the encoded parameters in a MIME type can be utilized.

[0202] Figure 4 is a block diagram illustrating an example video decoder 300 that can perform the techniques of this disclosure. Figure 4 It is provided for explanatory purposes and does not limit the technologies widely exemplified and described in this disclosure. For explanatory purposes, this disclosure describes a video decoder 300 of technologies according to JEM, EVC, VVC (ITU-T H.266, under development), and HEVC (ITU-T H.265). However, the technologies of this disclosure can be performed by video coding devices configured for other video coding standards.

[0203] In Figure 4 the example, 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 one 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 can be implemented in one or more processors or processing circuits. For example, the units of the video decoder 300 can be implemented as one or more circuits or logic elements, as part of a hardware circuit or as part of a processor, ASIC, FPGA. In addition, the video decoder 300 can include additional or alternative processors or processing circuits to perform these and other functions.

[0204] The prediction processing unit 304 includes a motion compensation unit 316 and an intra prediction unit 318. The prediction processing unit 304 can include additional units to perform prediction according to other prediction modes. As an example, the prediction processing unit 304 can include a palette unit, a block copy unit (which can form part of the motion compensation unit 316), an affine unit, a linear model (LM) unit, etc. In other examples, the video decoder 300 can include more, fewer, or different functional components.

[0205] The CPB memory 320 can store video data to be decoded by components of the video decoder 300, such as a coded video bitstream. For example, it can be from a computer-readable medium 110 ( Figure 1 )Obtain the video data stored in the CPB memory 320. The CPB memory 320 may include a CPB that stores the encoded video data (e.g., syntax elements) from the encoded video bitstream. Moreover, the CPB memory 320 may store video data other than the syntax elements of the encoded pictures, such as temporary data representing the outputs of the respective units from the video decoder 300. The DPB 314 generally stores the decoded pictures, and the video decoder 300 may output the decoded pictures and / or use the decoded pictures 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 of any of various storage devices such as DRAM (including SDRAM, MRAM, RRAM) or other types of storage devices. The CPB memory 320 and the DPB 314 may be provided by the same storage device or separate storage 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.

[0206] Additionally or alternatively, in some examples, the video decoder 300 may retrieve the encoded video data from the memory 120( Figure 1 ). That is, the memory 120 may store data in the CPB memory 320 as discussed above. Similarly, when some or all of the functions of the video decoder 300 are implemented in software to be executed by the processing circuitry of the video decoder 300, the memory 120 may store the instructions to be executed by the video decoder 300.

[0207] Figure 4 The various units shown in are illustrated to assist in understanding the operations performed by the video decoder 300. These units may be implemented as fixed-function circuitry, programmable circuitry, or a combination thereof. Similar to Figure 3 , fixed-function circuitry refers to circuitry that provides a specific function and is preset in the operations that can be performed. Programmable circuitry refers to circuitry that can be programmed to perform various tasks and provides flexible functionality in the operations that can be performed. For example, programmable circuitry may run software or firmware that causes the programmable circuitry to operate in the manner defined by the instructions of the software or firmware. Fixed-function circuitry may run software instructions (e.g., to receive parameters or output parameters), but the types of operations performed by the fixed-function circuitry are generally immutable. In some examples, one or more units may be different circuit blocks (fixed-function or programmable), and in some examples, one or more of these units may be an integrated circuit.

[0208] Video decoder 300 may include an ALU, an EFU, digital circuits, analog circuits, and / or a programmable core formed by programmable circuits. In an example where the operation of video decoder 300 is performed by software running on the programmable circuits, on-chip or off-chip memory may store instructions (e.g., object code) of the software received and run by video decoder 300.

[0209] Entropy decoding unit 302 may receive the encoded video data from the CPB and perform entropy decoding on the video data to reproduce syntax elements. Prediction processing unit 304, inverse quantization unit 306, inverse transform processing unit 308, reconstruction unit 310, and filter unit 312 may generate decoded video data based on the syntax elements extracted from the bitstream.

[0210] Generally, video decoder 300 reconstructs pictures on a block-by-block basis. Video decoder 300 may perform the reconstruction operation individually on each block (where the block currently being reconstructed (i.e., decoded) may be referred to as the "current block").

[0211] Entropy decoding unit 302 may perform entropy decoding on the syntax elements defining the quantized transform coefficient blocks of the quantized transform coefficients, and transform information such as quantization parameter (QP) and / or transform mode indication. Inverse quantization unit 306 may use the QP associated with the quantized transform coefficient block to determine the quantization degree, and similarly, determine the inverse quantization degree to be applied by inverse quantization unit 306. Inverse quantization unit 306 may, for example, perform a bitwise left shift operation to inverse-quantize the quantized transform coefficients. Thus, inverse quantization unit 306 may form a transform coefficient block including transform coefficients.

[0212] After inverse quantization unit 306 forms the transform coefficient block, 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, inverse transform processing unit 308 may apply an inverse DCT, inverse integer transform, inverse Karhunen-Loeve transform (KLT), inverse rotation transform, inverse orientation transform, or another inverse transform to the transform coefficient block.

[0213] In addition, prediction processing unit 304 generates a prediction block according to the prediction information syntax elements entropy decoded by entropy decoding unit 302. For example, if the prediction information syntax elements indicate that the current block is inter-predicted, motion compensation unit 316 may generate a prediction block. In this case, the prediction information syntax elements may indicate a reference picture in DPB 314, from which a reference block is retrieved, and a motion vector identifying the position of the reference block in the reference picture relative to the position of the current block in the current picture. Motion compensation unit 316 may generally operate in a manner similar to that of motion compensation unit 224 ( Figure 3 )perform inter - frame prediction processing in a manner substantially similar to the described manner.

[0214] As another example, if the prediction information syntax element indicates that the current block is intra - frame predicted, the intra - frame prediction unit 318 may generate a prediction block according to the intra - frame prediction mode indicated by the prediction information syntax element. Again, the intra - frame prediction unit 318 can generally perform intra - frame prediction processing in a manner substantially similar to the manner described with respect to the intra - frame prediction unit 226( Figure 3 )The intra - frame prediction unit 318 can retrieve data of adjacent samples of the current block from the DPB 314.

[0215] The reconstruction unit 310 can use the prediction block and the residual block to reconstruct the current block. For example, the reconstruction unit 310 can add the samples of the residual block to the corresponding samples of the prediction block to reconstruct the current block.

[0216] The filter unit 312 can perform one or more filter operations on the reconstructed block. For example, the filter unit 312 can perform a de - blocking operation to reduce blocking artifacts along the edges of the reconstructed block. The operation of the filter unit 312 is not necessarily performed in all examples.

[0217] The video decoder 300 can store the reconstructed block in the DPB 314. For example, in an example where the operation of the filter unit 312 is not performed, the reconstruction unit 310 can store the reconstructed block into the DPB 314. In an example where the operation of the filter unit 312 is performed, the filter unit 312 can store the filtered reconstructed block into the DPB 314. As discussed above, the DPB 314 can provide reference information such as samples of the current picture for intra - frame prediction and previously decoded pictures for subsequent motion compensation to the prediction processing unit 304. In addition, the video decoder 300 can output the decoded picture (e.g., decoded video) from the DPB 314 for subsequent presentation on a display device such as Figure 1 a display device 118.

[0218] In this way, 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.

[0219] 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 about all the tools required to decode the bitstream associated with the configuration record. The toolset indication syntax element of the configuration record may match the toolset indication syntax element signaled in the Sequence Parameter Set (SPS). Based on the toolset indication syntax element, the client device may determine whether to retrieve the bitstream associated with the configuration record. Based on the determination to retrieve the bitstream associated with the configuration record, the client device may retrieve the bitstream and output the bitstream to a video decoder 300 for decoding.

[0220] In some examples, the toolset indication syntax element may be considered to include the tools required to play the files in a sample entry, which is part of the encoding parameters. To enable the toolset indication syntax element, an encoding scheme for the encoded parameters in the MIME type may be utilized.

[0221] Figure 5 is a conceptual diagram illustrating an example structure of a file 500 according to one or more techniques of the present disclosure. In Figure 5 the example, the file 500 includes a movie box 502 and a plurality of media data boxes 504. Although illustrated in the same file in Figure 5 the example, in other examples, the movie box 502 and the media data boxes 504 may be in separate files. As indicated above, a box may be an object-oriented constructed box defined by a unique type identifier and length. For example, a box may be a basic syntax structure in ISOBMFF, including a four-character code box type, a byte count of the box, and a payload.

[0222] The movie box 502 may contain metadata for the tracks of the file 500. Each track of the file 500 may include a continuous media data stream. Each media data box 504 may include one or more samples 505. Each sample 505 may include an audio or video access unit. Each access unit may include a plurality of encoded pictures for multi-view coding or scalable video coding. For example, an access unit may include one or more encoded pictures for each layer.

[0223] In addition, in Figure 5 In the example, the movie box 502 includes a track box 506. The track box 506 may enclose the metadata of the 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 the sixth technique of the present disclosure, the track reference box of the tile track may or may not include a track reference type box associated with the type identifier 'tbas'.

[0224] The media box 510 may contain all objects that declare information about the media data within the track. The media box 510 includes a media information box 512. The media information box 512 may contain all objects that declare the characteristic information of the media of the track. The media information box 512 includes a sample table box 514. The sample table box 514 may specify sample-specific metadata.

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

[0226] Figure 6 is a conceptual diagram illustrating the elements of an example multimedia content 620. In Figure 6 the example, the multimedia content 620 includes an MPD 622 and multiple representations 624A - 624N (representations 624). The representation 624A includes optional header data 626 and segments 628A - 628N (segments 628), while the representation 624N includes optional header data 630 and segments 632A - 632N (segments 632). For convenience, the letter N is used to designate the last video segment in each representation 624. In some examples, there may be a different number of video segments between the representations 624.

[0227] The MPD 622 may include a data structure separate from the representation 624. Generally, the MPD 422 may include data that generally describes the characteristics of the representation 424, such as encoding and rendering characteristics, adaptation sets, the profiles corresponding to the MPD 422, text type information, camera angle information, rating information, stunt mode information (e.g., information indicating a representation including a temporal sub-sequence), and / or information for retrieving remote periods (e.g., information for inserting targeted advertisements into media content during playback).

[0228] Header data 626, when present, may describe the characteristics of the segment 628, e.g., the temporal location of a random access point (RAP, also known as a stream access point (SAP)), which of the segments 628 include a random access point, the byte offset to the random access point within the segment 628, the uniform resource locator (URL) of the segment 628, or other aspects of the segment 628. Header data 630, when present, may describe similar characteristics of the segment 632. Additionally or alternatively, such characteristics may be fully included within the MPD 622.

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

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

[0231] Figure 7 is a block diagram of the elements of an illustrated example video file 750. The video file 750 may be considered to encapsulate segments. As described above, video files according to the ISO base media file format and its extensions store data in a series of objects called "boxes". In Figure 7 In the example, the 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 Figure 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.) that are similarly structured to the data of the video file 750 according to the ISO Base Media File Format and its extensions.

[0232] The FTYP box 752 generally describes the file type of the video file 750. The file type box 752 may include data identifying a specification that describes 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.

[0233] In some examples, a segment such as the video file 750 may include an MPD update box (not shown) before the FTYP box 752. The MPD update box may include information indicating that the MPD corresponding to the representation including the video file 750 is to be updated with information for updating the MPD. For example, the MPD update box may provide a URI or URL of a resource for updating 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 the video file 750, where the STYP box may define the segment type of the video file 750.

[0234] In Figure 7 the example, the MOOV box 754 includes a Movie Header (MVHD) box 756, a Track (TRAK) box 758, and one or more Movie Extensions (MVEX) boxes 760. Generally, the MVHD box 756 may describe the general characteristics of the video file 750. For example, the MVHD box 756 may include data describing the time when the video file 750 was originally created, the time when the video file 750 was last modified, the time scale of the video file 750, the replay duration of the video file 750, or other data that generally describes the video file 750.

[0235] The TRAK box 758 may include data for the tracks of the video file 750. The TRAK box 758 may include a Track Header (TKHD) box that describes the characteristics of the track corresponding to the TRAK box 758. In some examples, the TRAK box 758 may include encoded video pictures, while in other examples, the encoded video pictures of the track may be included in the movie fragment 764, and the movie fragment 764 may be data-referred to by the TRAK box 758 and / or the sidx box 762.

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

[0237] The MVEX box 760 may describe the characteristics of the corresponding movie fragment 764, for example, to signal that in addition to the video data (if any) included within the MOOV box 754, the video file 750 also includes the movie fragment 764. In the context of streaming video data, the encoded video pictures may be included in the movie fragment 764 rather than the MOOV box 754. Thus, all encoded video samples may be included in the movie fragment 764 rather than the MOOV box 754.

[0238] The MOOV box 754 may include a plurality of MVEX boxes 760 equal to the number of movie fragments 764 in the video file 750. Each MVEX box 760 may describe the characteristics of the corresponding movie fragment in the movie fragment 764. For example, each MVEX box may include a Movie Extends Header box (MEHD) that describes the time duration of the corresponding movie fragment in the movie fragment 764.

[0239] Sequence datasets can be stored in video samples that do not include the actual encoded video data. Video samples generally can correspond to access units, which are representations of encoded pictures at a particular time instance. In the context of AVC, an encoded picture includes one or more VCL NAL units that contain information for constructing the access unit and other associated non-VCL NAL units, such as SEI messages. Thus, sequence datasets that can include sequence-level SEI messages can be included in one of the movie fragments 764. The presence of the sequence dataset and / or the sequence-level SEI message can be signaled to be present in one of the movie fragments 764 in one of the MVEX boxes 760 corresponding to one of the movie fragments 764.

[0240] The SIDX box 762 is an optional element of the video file 750. That is, a video file conforming to the 3GPP file format or other such file formats does not necessarily include the SIDX box 762. According to an example of the 3GPP file format, the SIDX box can be used to identify sub-segments of a segment (e.g., segments included in the video file 750). The 3GPP file format defines a sub-segment as "a self-contained set of one or more consecutive movie fragment boxes, having corresponding (multiple) media data boxes, and the media data box containing the data referenced by a movie fragment box 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 the SIDX box "contains a sequence of references to sub-segments of the (sub-)segment recorded by this box. The referenced sub-segments are consecutive in presentation time. Similarly, the bytes referenced by a segment index box are always consecutive within the segment. The referenced size gives a count of the number of bytes in the referenced material."

[0241] The SIDX box 762 generally provides information representing one or more sub-segments of a segment included in the video file 750. For example, such information can include the replay time at which the sub-segment starts and / or ends, the byte offset for the sub-segment, whether the sub-segment includes (e.g., at its start) a stream access point (SAP), the type of SAP (e.g., whether the SAP is an instant decoder refresh (IDR) picture, clean random access (CRA) picture, breakpoint link access (BLA) picture, etc.), the position of the SAP within the sub-segment (in terms of replay time and / or byte offset), etc.

[0242] The movie fragment 764 can include one or more encoded video pictures. In some examples, the movie fragment 764 can include one or more groups of pictures (GOPs), and each group of pictures can include multiple encoded video pictures, e.g., frames or pictures. Additionally, as described above, in some examples, the movie fragment 764 can include sequence datasets. Each movie fragment 764 can include a movie fragment header box (MFHD, Figure 7 (not shown in the figure). The MFHD box may describe the characteristics of the corresponding video segment, such as the sequence number of the video segment. The video segments 764 may be included in the video file 750 in the order of the sequence numbers.

[0243] The MFRA box 766 may describe the random access points in the video segment 764 of the video file 750. This may help to perform stunt modes, such as searching for a specific time position (i.e., replay time) in the segments encapsulated by the video file 750. In some examples, the MFRA box 766 is generally optional and does not have to be included in the video file. Similarly, the client device does not necessarily have 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 plurality 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 - cue tracks) of the video file 750.

[0244] In some examples, the video segment 764 may include one or more stream access points (SAPs), such as IDR pictures. Similarly, the MFRA box 766 may provide an indication of the position of the SAP in the video file 750. Thus, a time subsequence of the video file 750 may be formed from the SAPs of the video file 750. The time subsequence may also include other pictures, such as P - frames and / or B - frames depending on the SAPs. The frames and / or slices of the time subsequence may be arranged within the segments such that the frames / slices of the time subsequence that depend on other frames / slices of the subsequence can be decoded appropriately. For example, in a hierarchical arrangement of data, the data used for prediction of other data may also be included in the time subsequence.

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

[0246] An example sample description box 768 may be defined as follows:

[0247] Sample entries and box types: 'hvc2', 'hev2', 'lhv1', 'lhe1', 'lhvC'

[0248] · Container: sample description box ('stsd')

[0249] · Mandatory: 'hvc1', 'hev1', 'hvc2', 'hev2', 'lhv1' or 'lhe1' sample entries are mandatory · Quantity: One or more sample entries may exist

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

[0251] Figure 8 is a flowchart illustrating an example method for processing video data according to the technology of the present disclosure. Although described with respect to Figure 1 destination device 116, it should be understood that other devices may be configured to perform a method similar to Figure 8 the method.

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

[0253] The toolset indication syntax element is signaled in the configuration box of the file format information. The toolset indication syntax element including information identifying 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.

[0254] The configuration record can be formatted according to the necessary EVC standard. The configuration record for the bitstream can include profile syntax elements and / or level syntax elements before the toolset indication syntax elements. The configuration record for the bitstream can include chroma format syntax elements after the toolset indication syntax elements.

[0255] It should be recognized that, depending on the example, certain actions or events of any of the techniques described herein can be performed in a different sequence, can be added, combined, or omitted together (e.g., not all of the described actions or events are necessary to practice these techniques). Additionally, in some examples, the actions or events can be performed, for example, concurrently rather than sequentially by multi-threading, interrupt handling, or multiple processors.

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

[0257] Clause 1. A method for processing a video stream or a 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, the toolset indication syntax element including information that identifies, from a set of video decoding tools, the tools required to decode the bitstream associated with the configuration record; determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on the determination to retrieve the bitstream associated with the configuration record, retrieving the bitstream and outputting the bitstream to a video decoder for decoding.

[0258] Clause 2. The method of Clause 1, further comprising: receiving a Multipurpose Internet Mail Extensions (MIME) type parameter including key-value pairs, wherein the key indicates that the MIME type identifies a video decoding tool, and the value identifies, from the video decoding tools, the tools required to decode the bitstream.

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

[0260] Clause 4. The method of any one of Clauses 1-3, wherein the toolset indication syntax element including information that identifies the tools required to decode the bitstream associated with the configuration record identifies all the tools required to decode the bitstream associated with the configuration record.

[0261] Clause 5. The method of any one of Clauses 1-4, wherein the configuration record is formatted according to the Basic Video Coding (EVC) standard.

[0262] Clause 6. A method according to any one of Clauses 1 - 5, wherein a toolset is signaled in a configuration box of file format information to indicate a syntax element.

[0263] Clause 7. A method according to any one of Clauses 1 - 6, wherein the toolset indication of the syntax element includes an unsigned 32 - bit integer value.

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

[0265] Clause 9. A method according to any one of Clauses 1 - 8, wherein a configuration record for the bitstream includes profile syntax elements before the toolset indication of the syntax element.

[0266] Clause 10. A method according to any one of Clauses 1 - 9, wherein a configuration record for the bitstream includes level syntax elements before the toolset indication of the syntax element.

[0267] Clause 11. A method according to any one of Clauses 1 - 10, wherein a configuration record for the bitstream includes chroma format syntax elements after the toolset indication of the syntax element.

[0268] Clause 12. A method according to any one of Clauses 1 - 11, wherein the configuration record includes file format level data that encapsulates 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 wherein each tool identified in the configuration record as required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

[0269] Clause 13. A device for processing video data, the device comprising: a memory; and one or more processors implemented in circuitry, coupled to the memory and configured to: receive a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication of the syntax element, the toolset indication of the syntax element including information that identifies tools required for decoding the bitstream associated with the configuration record from a set of video decoding tools; determine whether to retrieve the bitstream associated with the configuration record based on the toolset indication of the syntax element; and based on a determination to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0270] Clause 14. The apparatus of clause 13, wherein the one or more processors are further configured to: receive Multipurpose Internet Mail Extensions (MIME) type parameters including key-value pairs, wherein the key indicates a MIME type identifying a video decoding tool, and the value identifies, from among video decoding tools, the tools needed to decode a bitstream.

[0271] Clause 15. The apparatus of clause 13 or 14, wherein the bitstream of video data includes one or more parameter sets, and wherein, in at least one of the one or more parameter sets, each tool identified in a configuration record as needed to decode the bitstream is enabled.

[0272] Clause 16. The apparatus of any one of clauses 13-15, wherein a toolset indicating syntax elements including information identifying the tools needed to decode a bitstream associated with a configuration record indicates all the tools needed to decode the bitstream associated with the configuration record.

[0273] Clause 17. The apparatus of any one of clauses 13-16, wherein the configuration record is formatted according to the Essential Video Coding (EVC) standard.

[0274] Clause 18. The apparatus of any one of clauses 13-17, wherein the toolset indicating syntax elements is signaled in a configuration box of file format information.

[0275] Clause 19. The apparatus of any one of clauses 13-15, wherein the toolset indicating syntax elements includes an unsigned 32-bit integer value.

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

[0277] Clause 21. The apparatus of any one of clauses 13-20, wherein the configuration record for the bitstream includes profile syntax elements before the toolset indicating syntax elements.

[0278] Clause 22. The apparatus of any one of clauses 13-21, wherein the configuration record for the bitstream includes level syntax elements before the toolset indicating syntax elements.

[0279] Clause 23. The apparatus of any one of clauses 13-22, wherein the configuration record for the bitstream includes chroma format syntax elements after the toolset indicating syntax elements.

[0280] Clause 24. Apparatus according to any one of Clauses 13 - 23, wherein the configuration record includes file format level data that encapsulates media data encoded at the video coding layer (VCL) level in a bitstream of video data, wherein the media data encoded at the VCL level includes one or more parameter sets, and wherein each tool identified in the configuration record as being required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

[0281] 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, wherein the configuration record for the bitstream includes a toolset indication syntax element that includes information identifying tools required for decoding the bitstream associated with the configuration record from a set of video decoding tools; determine, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on a determination to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

[0282] Clause 26. The computer-readable storage medium of Clause 25, wherein the instructions cause the one or more processors to: receive a Multipurpose Internet Mail Extensions (MIME) type parameter including key-value pairs, wherein the key indicates that the MIME type identifies a video decoding tool and the value identifies tools required for decoding the bitstream from the video decoding tools.

[0283] Clause 27. The computer-readable storage medium of Clause 25 or 26, wherein the bitstream of video data includes one or more parameter sets, and wherein each tool identified in the configuration record as being required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

[0284] Clause 28. The computer-readable storage medium of any one of Clauses 25 - 27, wherein the toolset indication syntax element including information identifying tools required for decoding the bitstream associated with the configuration record identifies all tools required for decoding the bitstream associated with the configuration record.

[0285] Clause 29. The computer-readable storage medium of any one of Clauses 25 - 28, wherein the configuration record includes file format level data that encapsulates media data encoded at the video coding layer (VCL) level in a bitstream of video data, wherein the media data encoded at the VCL level includes one or more parameter sets, and wherein each tool identified in the configuration record as being required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

[0286] Clause 30. An apparatus for processing a video stream or a video file, the apparatus 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, the toolset indication syntax element including information identifying tools required for decoding the bitstream associated with the configuration record from a set of video decoding tools; means for determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; means for retrieving the bitstream based on a determination to retrieve the bitstream associated with the configuration record; and means for outputting the bitstream to a video decoder for decoding.

[0287] Clause 31. A method for processing video data, the method comprising: receiving a configuration record for decoding a bitstream of video data according to the Basic Video Coding (EVC) standard, wherein the configuration record for the bitstream includes a toolset indication syntax element, the toolset indication syntax element including information on all tools required for decoding the bitstream associated with the configuration record; determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and retrieving the bitstream and outputting the bitstream to a video decoder for decoding based on a determination to retrieve the bitstream associated with the configuration record.

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

[0289] Clause 33. The method of Clause 31 or 32, wherein the toolset indication syntax element is signaled in a configuration box of file format information.

[0290] Clause 34. An apparatus for processing video data, the apparatus comprising: processing circuitry configured to perform the method of any one or combination of Clauses 1 - 3.

[0291] Clause 35. The apparatus of Clause 34, further comprising a memory for storing video data.

[0292] Clause 36. The apparatus of any one of Clauses 34 and 35, further comprising a display configured to display decoded video data.

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

[0294] Clause 38. A computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors to perform the method according to any one of Clauses 31 - 33.

[0295] Clause 39. An apparatus for processing video data, the apparatus comprising components for performing the method according to any one of Clauses 31 - 33.

[0296] In one or more examples, the described functions 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. The 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 facilitates transfer of a computer program from one place to another, for example, according to a communication protocol. In this manner, the computer-readable medium generally may correspond to (1) a non-transitory tangible computer-readable storage medium, or (2) a communication medium such as a signal or a carrier wave. The data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, code, and / or data structures for implementing the techniques described in this disclosure. A computer program product may include a computer-readable medium.

[0297] By way of example and not limitation, such a computer-readable storage medium can include 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 can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave from a website, server, or other remote source, then the medium's definition includes coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but rather are directed to non-transient tangible storage media. As used in this application, disk and optical disks include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and Blu-ray disk, where disks typically reproduce data magnetically, while optical disks reproduce data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0298] The instructions can be executed by one or more processors, such as one or more digital signal processors (DSPs), general microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Thus, as used in this application, the terms "processor" and "processing circuitry" can refer to any of the foregoing structures or any other structure suitable for implementing the techniques described in this application. Additionally, in some aspects, the functions described in this application can be provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated in a combined codec. Similarly, the techniques can be fully implemented in one or more circuits or logic elements.

[0299] The techniques of the present disclosure can be implemented in a variety of devices or apparatuses, including wireless handsets, integrated circuits (ICs), or a group of ICs (e.g., a chipset). In the present disclosure, various components, modules, or units are described to emphasize the functional aspects of the devices configured to perform the disclosed techniques, but do not necessarily need to be implemented by different hardware units. Rather, as described above, the various units can be combined in a codec hardware unit, or provided by a collection of interoperating hardware units, including one or more processors as described above in conjunction with suitable software and / or firmware.

[0300] Various examples have been described. These and other examples are within the scope of the appended claims.< / valuen> < / keyn> < / value2> < / key2> < / value1> < / key1>

Claims

1. A method for processing a video stream or a video file, the method comprises: receiving a configuration record for decoding a bitstream of video data, wherein the configuration record for the bitstream includes a toolset indication syntax element, and the toolset indication syntax element includes information that identifies, from a set of video decoding tools, the tools required for decoding the bitstream associated with the configuration record; determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and retrieving the bitstream and outputting the bitstream to a video decoder for decoding based on the determination to retrieve the bitstream associated with the configuration record.

2. The method according to claim 1, further comprises: receiving a Multipurpose Internet Mail Extensions (MIME) type parameter including key-value pairs, wherein the key indicates that the MIME type identifies the video decoding tool, and the value identifies, from the video decoding tools, the tools required for decoding the bitstream.

3. The method according to claim 1, wherein, the bitstream of the video data includes one or more parameter sets, and wherein, in at least one of the one or more parameter sets, each of the tools identified in the configuration record as required for decoding the bitstream is enabled.

4. The method according to claim 1, wherein, the toolset indication syntax element including information that identifies the tools required for decoding the bitstream associated with the configuration record identifies all the tools required for decoding the bitstream associated with the configuration record.

5. The method according to claim 1, wherein, the configuration record is formatted according to the Basic Video Coding (EVC) standard.

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

7. The method according to claim 1, wherein, the toolset indication syntax element includes an unsigned 32-bit integer value.

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

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

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

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

12. The method according to claim 1, wherein, The configuration record includes file format level data that encapsulates 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 where each of the tools identified in the configuration record as being required to decode the bitstream is enabled in at least one of the one or more parameter sets.

13. A device for processing video data, the device comprises: a memory; and one or more processors implemented in circuitry, 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 that includes information identifying, from a set of video decoding tools, the tools required to decode the bitstream associated with the configuration record; determine, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; and based on the determination to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

14. The device according to claim 13, wherein the one or more processors are further configured to: receive a Multipurpose Internet Mail Extensions (MIME) type parameter including key-value pairs, where the key indicates that the MIME type identifies the video decoding tool, and the value identifies, from the video decoding tools, the tools required to decode the bitstream.

15. The device according to claim 13, wherein the bitstream of the video data includes one or more parameter sets, and where each of the tools identified in the configuration record as being required to decode the bitstream is enabled in at least one of the one or more parameter sets.

16. The device according to claim 13, wherein the toolset indication syntax element including information identifying the tools required to decode the bitstream associated with the configuration record identifies all the tools required to decode the bitstream associated with the configuration record.

17. The device according to claim 13, wherein the configuration record is formatted according to the Essential Video Coding (EVC) standard.

18. The device according to claim 13, wherein the toolset indication syntax element is signaled in a configuration box of the file format information.

19. The device according to claim 13, wherein the toolset indication syntax element includes an unsigned 32-bit integer value.

20. The device according to claim 19, wherein each bit of the unsigned 32-bit integer value corresponds to a unique tool for decoding the bitstream.

21. The device according to claim 13, wherein The configuration for the bitstream includes profile syntax elements before the toolset indication syntax elements.

22. The apparatus according to claim 13, wherein, The configuration for the bitstream includes level syntax elements before the toolset indication syntax elements.

23. The apparatus according to claim 13, wherein, The configuration for the bitstream includes chroma format syntax elements after the toolset indication syntax elements.

24. The apparatus according to claim 13, wherein, The configuration record includes file format level data that encapsulates 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 wherein each of the tools identified in the configuration record as required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

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, wherein, The configuration record for the bitstream includes a toolset indication syntax element that includes information identifying, from a set of video decoding tools, the tools required for decoding 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 determination to retrieve the bitstream associated with the configuration record, retrieve the bitstream and output the bitstream to a video decoder for decoding.

26. The computer-readable storage medium according to claim 25, wherein, The instructions cause the one or more processors to: Receive a Multipurpose Internet Mail Extensions (MIME) type parameter including key-value pairs, wherein the key indicates that the MIME type identifies the video decoding tool, and the value identifies, from the video decoding tools, the tools required for decoding the bitstream.

27. The computer-readable storage medium according to claim 25, wherein, The bitstream of the video data includes one or more parameter sets, and wherein each of the tools identified in the configuration record as required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

28. The computer-readable storage medium according to claim 25, wherein, The toolset indication syntax element including information identifying the tools required for decoding the bitstream associated with the configuration record identifies all the tools required for decoding the bitstream associated with the configuration record.

29. The computer-readable storage medium according to claim 25, wherein, The configuration record includes file format level data that encapsulates 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 wherein each of the tools identified in the configuration record as being required for decoding the bitstream is enabled in at least one of the one or more parameter sets.

30. A device for processing a video stream or a video file, the device 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 that includes information identifying, from a set of video decoding tools, the tools required for decoding the bitstream associated with the configuration record; means for determining, based on the toolset indication syntax element, whether to retrieve the bitstream associated with the configuration record; means for retrieving the bitstream based on the determination to retrieve the bitstream associated with the configuration record; and means for outputting the bitstream to a video decoder for decoding.

Images