Managing reference pictures in video coding

Abstract

To provide, e.g., a method of decoding a coded video bitstream.SOLUTION: The method includes parsing a parameter set represented in the coded video bitstream. The parameter set contains a set of syntax elements that include a set of reference picture list structures. The method also includes parsing a slice header of a current slice represented in the coded video bitstream. The slice header contains an index of a reference picture list structure in the set of reference picture list structures in the parameter set. The method further includes deriving, based on the set of syntax elements in the parameter set and the index of the reference picture list structure, a reference picture list of the current slice. The method also includes obtaining, based on the reference picture list, at least one reconstructed block of the current slice.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] Cross-reference of related applications This application was filed on August 17, 2018. Filing of a U.S. patent application The benefits of issues 62 / 719,360 This asserts the interests of Japanese Patent Application No. 2021-507884, filed on 16 August 2019, which are incorporated herein by reference. . This disclosure relates, in general terms, to techniques for managing reference pictures in video coding. More specifically, this disclosure describes techniques for building a reference picture list and marking reference pictures. [Background technology]

[0002] Even relatively short videos can require a considerable amount of video data, which can pose challenges when the data needs to be streamed or otherwise transmitted over communication networks with limited bandwidth. Therefore, video data is generally compressed before being transmitted over modern communication networks. Video size can also be a concern when videos are stored on storage devices, as memory resources may also be limited. Often, video compression devices use software and / or hardware at the source to encode the video data before transmission or storage, thereby reducing the amount of data required to represent the digital video image. The compressed data is then received at the destination by a video decompression device that decodes the video data. Given limited network resources and the increasing demand for higher video quality, improved compression and decompression techniques that increase the compression ratio with little to no sacrifice of image quality are desirable. [Overview of the project] [Means for solving the problem]

[0003] The first aspect relates to a method for decoding a coded video bitstream. The method includes the steps of: parsing a parameter set indicated in the coded video bitstream, wherein the parameter set includes a set of syntax elements including a set of reference picture list structures; parsing a slice header of the current slice indicated in the coded video bitstream, wherein the slice header includes an index of a reference picture list structure from the set of reference picture list structures in the parameter set; deriving a reference picture list of the current slice based on the set of syntax elements and the index of the reference picture list structure in the parameter set; and obtaining at least one reconstructed block of the current slice based on the reference picture list.

[0004] The method provides a technique that simplifies and makes signaling of reference picture lists more efficient. Therefore, the entire coding process is improved.

[0005] In the first implementation of the method by the first embodiment itself, the order of entries in the reference picture list structure is the same as the order of the corresponding reference pictures in the reference picture list.

[0006] In a second implementation of the method according to the first aspect itself, or in any of the aforementioned implementations of the first aspect, the order is from zero to the indicated value.

[0007] In a third implementation of the method according to the first aspect itself, or in any of the aforementioned implementations of the first aspect, the indicated value ranges from zero to the value indicated by sps_max_dec_pic_buffering_minus1.

[0008] In a fourth implementation of the method according to the first aspect itself, or in any of the aforementioned implementations of the first aspect, the reference picture list is the specified RefPictList[0].

[0009] In a fifth implementation of the method according to the first aspect itself, or in any of the aforementioned implementations of the first aspect, the reference picture list is the specified RefPictList[1].

[0010] In a sixth implementation of the method according to the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, at least one reconstructed block is used to generate an image to be displayed on the display of an electronic device.

[0011] In a seventh implementation of the method according to the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, the reference picture list includes a list of reference pictures used for interpretation.

[0012] In the eighth implementation of the method according to the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, the inter prediction is for P slices or for B slices.

[0013] In the ninth implementation of the method according to the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, the parameter set includes a sequence parameter set (SPS).

[0014] In the tenth implementation of the method according to the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, the set of syntax elements from the parameter set is placed in the raw byte sequence payload (RBSP) of the network abstraction layer (NAL) unit.

[0015] In the eleventh implementation of the method according to the first aspect itself, or in any of the aforementioned implementations of the first aspect, the reference picture list is a specified RefPictList[0] or RefPictList[1], and the order of entries in the reference picture list structure is the same as the order of the corresponding reference pictures in the reference picture list.

[0016] In a twelfth implementation of the method by the first embodiment itself, or in any of the aforementioned implementations of the first embodiment, the method further includes the steps of: parsing a parameter set shown in a coded video bitstream, wherein the parameter set includes a set of syntax elements including a set of reference picture list structures; obtaining a reference picture list structure shown in a coded video bitstream; deriving a first reference picture list of the current slice based on the reference picture list structure, wherein the first reference picture list includes at least one active entry and at least one inactive entry, the at least one inactive entry referring to a reference picture that is not used for interpretation of the current slice but is referenced by an active entry of a second reference picture list, the second reference picture list being a reference picture list of slices that follow the current slice in decoding order or a reference picture list of pictures that follow the current picture in decoding order; and obtaining at least one reconstructed block of the current slice based on at least one active entry of the first reference picture list.

[0017] A second aspect relates to a decoding device, the decoding device comprising a receiver configured to receive a coded video bitstream, a memory connected to the receiver for storing instructions, and a processor connected to the memory for executing instructions stored in the memory, wherein the instruction involves parsing a parameter set indicated in the coded video bitstream, the parameter set comprising a set of syntax elements comprising a set of reference picture list structures, parsing a slice header of the current slice indicated in the coded video bitstream, the slice header comprising an index of a reference picture list structure from the set of reference picture list structures in the parameter set, deriving a reference picture list of the current slice based on the set of syntax elements and the index of the reference picture list structures in the parameter set, and causing the processor to obtain at least one reconstructed block of the current slice based on the reference picture list.

[0018] The decoding device provides a technique that simplifies and makes the signaling of the reference picture list more efficient. Therefore, the entire coding process is improved.

[0019] In a first implementation of the decoding device by a second embodiment, the decoding device further includes a display configured to show the current picture generated based on at least one reconstructed block.

[0020] A third aspect relates to a coding apparatus, the coding apparatus including a receiver configured to receive a bitstream to be decoded, a transmitter connected to the receiver and configured to transmit a decoded image to a display, a memory connected to at least one of the receiver or the transmitter and configured to store instructions, and a processor connected to the memory and configured to execute the instructions stored in the memory to execute the method according to any of the preceding aspects or implementations.

[0021] A fourth aspect relates to a system including an encoder and a decoder communicating with the encoder. The encoder or the decoder includes a decoding device or a coding apparatus according to any of the preceding aspects or implementations.

[0022] The system provides a technique for simplifying and making more efficient the signaling of reference picture lists. Accordingly, the entire coding process is improved.

[0023] A fifth aspect relates to means for coding, the means for coding including receiving means configured to receive a picture to be encoded or a bitstream to be decoded, transmitting means connected to the receiving means and configured to transmit the bitstream to a decoder or the decoded image to display means, storage means connected to at least one of the receiving means or the transmitting means and configured to store instructions, and processing means connected to the storage means and configured to execute the instructions stored in the storage means to execute the method according to any of the preceding aspects or implementations.

[0024] The means for coding provides a technique for simplifying and making more efficient the signaling of reference picture lists. Accordingly, the entire coding process is improved.

[0025] For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in conjunction with the accompanying drawings in which like reference numerals represent like parts, and in which:

Brief Description of the Drawings

[0026] [Figure 1] FIG. 8 is a block diagram showing an exemplary coding system that may utilize bidirectional prediction techniques. [Figure 2] FIG. 11 is a block diagram showing an exemplary video encoder that may implement bidirectional prediction techniques. [Figure 3] FIG. 14 is a block diagram showing an example of a video decoder that may implement bidirectional prediction techniques. [Figure 4] FIG. 17 is a schematic diagram showing a reference picture set (RPS) having pictures along with entries for all subsets of the RPS. [Figure 5] FIG. 20 is a diagram of an embodiment of a method for decoding a coded video bitstream. [Figure 6] FIG. 23 is a schematic diagram of a video coding device. [Figure 7] FIG. 26 is a schematic diagram of an embodiment of means for coding.

Best Mode for Carrying Out the Invention

[0027] Figure 1 is a block diagram illustrating an exemplary coding system 10 that may utilize video coding technology as described herein. As shown in Figure 1, the coding system 10 includes a source device 12 that provides coded video data to be later decoded by a destination device 14. In particular, the source device 12 may provide the video data to the destination device 14 via a computer-readable medium 16. The destination devices 12 and 14 may include any of a wide range of devices, including desktop computers, notebook (e.g., laptop) computers, tablet computers, set-top boxes, telephone handsets such as so-called "smart" phones, so-called "smart" pads, televisions, cameras, display devices, digital media players, video game consoles, and video streaming devices. In some cases, the source device 12 and destination device 14 may be capable of wireless communication.

[0028] The destination device 14 may receive encoded video data that is decoded via a computer-readable medium 16. The computer-readable medium 16 may include any type of medium or device that can move the encoded video data from the source device 12 to the destination device 14. For example, the computer-readable medium 16 may include a communication medium that enables the source device 12 to directly transmit the encoded video data to the destination device 14 in real time. The encoded video data may be modulated according to a communication standard, such as a wireless communication protocol, and transmitted to the destination device 14. The communication medium may include any wireless or wired communication medium, such as a radio frequency (RF) spectrum or one or more physical transmission lines. The communication medium may form part of a packet-based network, such as a local area network, a wide area network, or a global network such as the Internet. The communication medium may include routers, switches, base stations, or any other equipment that may help facilitate communication from the source device 12 to the destination device 14.

[0029] In some examples, the encoded data may be output to a storage device via the output interface 22. Similarly, the encoded data may be accessed from the storage device via the input interface. The storage device may include any of a variety of distributed or locally accessed data storage media, such as a hard drive, Blu-ray disc, digital video disc (DVD), compact disc read-only memory (CD-ROM), flash memory, volatile or non-volatile memory, or any other suitable digital storage medium for storing the encoded video data. In further examples, the storage device may correspond to a file server or another intermediate storage device that may store the encoded video generated by the source device 12. The destination device 14 may access the stored video data from the storage device by streaming or downloading. The file server may be any type of server that can store the encoded video data and send that encoded video data to the destination device 14. Exemplary file servers include, for example, a web server (for a website), a File Transfer Protocol (FTP) server, a network-attached storage (NAS) device, or a local disk drive. The destination device 14 may access the encoded video data through any standard data connection, including an internet connection. This may include wireless channels (e.g., Wi-Fi connections), wired connections (e.g., digital subscriber lines (DSL), cable modems, etc.), or a combination of both, which are suitable for accessing encoded video data stored on a file server. Transmission of encoded video data from the storage device may be streaming transmission, download transmission, or a combination of both.

[0030] The technology of this disclosure is not necessarily limited to wireless applications or configurations. The technology may be applied to video coding to assist any of a variety of multimedia applications, such as radio television broadcasting, cable television transmission, satellite television transmission, internet streaming video transmission such as dynamic adaptive streaming over HTTP (DASH), digital video encoded to a data storage medium, decoding of digital video stored on a data storage medium, or other applications. In some examples, the coding system 10 may be configured to support one-way or two-way video transmission to support applications such as video streaming, video playback, video broadcasting, and / or video conferencing.

[0031] In the example in Figure 1, the source device 12 includes a video source 18, a video encoder 20, and an output interface 22. The destination device 14 includes an input interface 28, a video decoder 30, and a display device 32. According to this disclosure, the video encoder 20 of the source device 12 and / or the video decoder 30 of the destination device 14 may be configured to apply techniques for video coding. In other examples, the source and destination devices may include other components or configurations. For example, the source device 12 may receive video data from an external video source, such as an external camera. Similarly, the destination device 14 may interface with an external display device rather than including an integrated display device.

[0032] The coding system 10 shown in Figure 1 is merely an example. Techniques for video coding may be performed by any digital video coding and / or decoding device. While the techniques of this disclosure are generally performed by video coding devices, the techniques may also be performed by video encoders / decoders, commonly referred to as “codecs.” Furthermore, the techniques of this disclosure may also be performed by video preprocessors. Video encoders and / or decoders may be graphics processing units (GPUs) or similar devices.

[0033] The source device 12 and destination device 14 are merely examples of such coding devices, where the source device 12 generates coded video data to be transmitted to the destination device 14. In some examples, the source device 12 and destination device 14 may operate in a substantially symmetrical manner, such that each of the source and destination devices 12 and 14 includes video coding and decoding components. Thus, the coding system 10 may support one-way or two-way video transmission between video devices 12 and 14 for, for example, video streaming, video playback, video broadcasting, or video conferencing.

[0034] The video source 18 of the source device 12 may include a video recording device such as a video camera, a video archive containing previously recorded video, and / or a video feed interface for receiving video from a video content provider. As a further alternative, the video source 18 may generate data based on computer graphics as source video, or generate a combination of live video, archived video, and computer-generated video.

[0035] In some cases, when the video source 18 is a video camera, the source device 12 and the destination device 14 may form a so-called camera phone or video phone. However, as stated above, the technology described in this disclosure may generally be applicable to video coding and may be applicable to wireless and / or wired applications. In each case, captured, pre-recorded, or computer-generated video may be encoded by the video encoder 20. The encoded video information may then be output to a computer-readable medium 16 via the output interface 22.

[0036] The computer-readable medium 16 may include transient media such as wireless broadcasting or wired network transmission, or storage media such as hard disks, flash drives, compact discs, digital video discs, Blu-ray discs, or other computer-readable media (i.e., non-transient storage media). In some examples, a network server (not shown) may receive encoded video data from a source device 12 via network transmission, for example, and provide the encoded video data to a destination device 14. Similarly, a computing device in a media manufacturing facility, such as a disc stamping facility, may receive encoded video data from a source device 12 and manufacture a disc containing the encoded video data. Thus, the computer-readable medium 16 may be understood to include one or more computer-readable media in various forms in various examples.

[0037] The input interface 28 of the destination device 14 receives information from the computer-readable medium 16. The information on the computer-readable medium 16 may include syntax information defined by the video encoder 20, which is also used by the video decoder 30. The syntax information includes syntax elements that describe the features and / or processing of blocks and other coded units, such as groups of pictures (GOP). The display device 32 displays the decoded video data to the user and may include any of the various display devices, such as a cathode ray tube (CRT), liquid crystal display (LCD), plasma display, organic light-emitting diode (OLED) display, or another type of display device.

[0038] The video encoder 20 and video decoder 30 may operate in accordance with video coding standards such as the High Efficiency Video Coding (HEVC) standard currently under development, and may comply with the HEVC Test Model (HM). Alternatively, the video encoder 20 and video decoder 30 may operate in accordance with other proprietary standards or industry standards such as the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) H.264 standard, H.265 / HEVC, also known as Moving Picture Expert Group (MPEG)-4, Part 10, Advanced Video Coding (AVC), or extensions of such standards. However, the technology of this disclosure is not limited to any particular coding standard. Other examples of video coding standards include MPEG-2 and ITU-T H.263. Although not shown in Figure 1, in some embodiments, the video encoder 20 and video decoder 30 may be integrated with an audio encoder and decoder, respectively, and may include a suitable multiplexer-demultiplexer (MUX-DEMUX) unit or other hardware and software for handling the encoding of both audio and video in a common data stream or separate data streams. Where appropriate, the MUX-DEMUX unit may comply with the ITU H.223 Multiplexer Protocol or other protocols such as the User Datagram Protocol (UDP).

[0039] The video encoder 20 and video decoder 30 may each be implemented 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 technology is partially implemented in software, the device may store instructions for the software in a suitable non-temporary computer-readable medium and execute the instructions in hardware using one or more processors to perform the technology of this disclosure. Each of the video encoder 20 and video decoder 30 may be comprised of one or more encoders or decoders, and either of those encoders or decoders may be integrated as part of a combined encoder / decoder (codec) in each device. A device comprising the video encoder 20 and / or video decoder 30 may include an integrated circuit, a microprocessor, and / or a wireless communication device such as a cellular phone.

[0040] Figure 2 is a block diagram showing an example of a video encoder 20 that may implement video coding techniques. The video encoder 20 may perform intra and intercoding of video blocks within a video slice. Intra coding relies on spatial prediction to reduce or eliminate spatial redundancy of video in a given video frame or picture. Intercoding relies on temporal prediction to reduce or eliminate temporal redundancy of video in nearby frames or pictures in a video sequence. Intra mode (I mode) may refer to any of several space-based coding modes. Inter modes, such as uni-prediction (also known as uni prediction), P-mode, or bi-prediction (also known as bi prediction) (B mode), may refer to any of several time-based coding modes.

[0041] As shown in Figure 2, the video encoder 20 receives the current video block within the video frame to be encoded. In the example in Figure 2, the video encoder 20 includes a mode selection unit 40, a reference frame memory 64, an adder 50, a transformation unit 52, a quantization unit 54, and an entropy coding unit 56. Furthermore, the mode selection unit 40 includes a motion compensation unit 44, a motion estimation unit 42, an intra-prediction (also known as intra-prediction) unit 46, and a partitioning unit 48. For the reconstruction of the video block, the video encoder 20 also includes an inverse quantization unit 58, an inverse transformation unit 60, and an adder 62. A deblocking filter (not shown in Figure 2) may also be included to filter the block boundaries to remove blocking artifacts from the reconstructed video. If necessary, the deblocking filter generally filters the output of the adder 62. Further filters (in-loop or after-loop) may also be used in addition to the deblocking filter. Such filters are not shown for brevity, but if necessary, they may filter the output of adder 50 (as an in-loop filter).

[0042] During the encoding process, the video encoder 20 receives a video frame or slice to be coded. The frame or slice may be divided into multiple video blocks. The motion estimation unit 42 and the motion compensation unit 44 perform inter-predictive coding of the received video block for one or more blocks within one or more reference frames to provide temporal predictions. The intra-predictive unit 46 may, alternatively, perform intra-predictive coding of the received video block for one or more neighboring blocks within the same frame or slice as the block to be coded to provide spatial predictions. The video encoder 20 may perform multiple coding passes, for example, to select the appropriate coding mode for each block of video data.

[0043] Furthermore, the partitioning unit 48 may partition blocks of video data into lower blocks based on an evaluation of the previous partitioning scheme in the previous coding pass. For example, the partitioning unit 48 may first partition a frame or slice into a maximum coding unit (LCU), and then partition each LCU into lower coding units (lower CUs) based on rate distortion analysis (e.g., rate distortion optimization). The mode selection unit 40 may further generate a quadtree data structure that shows the partitioning of LCUs into lower CUs. The leaf nodes CU of the quadtree may contain one or more prediction units (PUs) and one or more transformation units (TUs).

[0044] This disclosure uses the term “block” to refer to a CU, PU, ​​or TU in the context of HEVC, or to a similar data structure in the context of other standards (e.g., a macroblock and its subblocks in H.264 / AVC). A CU includes a coding node, a PU, and a TU associated with the coding node. The size of a CU corresponds to the size of the coding node and is square in shape. The size of a CU can range from 8x8 pixels to the size of a tree block of up to 64x64 pixels or more. Each CU may contain one or more PUs and one or more TUs. Syntax data associated with a CU may, for example, describe the partitioning of the CU into one or more PUs. The partitioning mode may differ between skip or direct mode encoding, intra-prediction mode encoding, or inter-prediction mode encoding. PUs may be partitioned to have a non-square shape. Syntax data associated with a CU may, for example, describe the partitioning of the CU into one or more TUs by a quadtree. TU can be square or non-square (for example, rectangular).

[0045] The mode selection unit 40 may, for example, select one of the coding modes, intra or inter, based on the error result, and provide the resulting intra or intercoded block to the adder 50 to generate residual block data and to the adder 62 to reconstruct the coded block for use as a reference frame. The mode selection unit 40 also provides syntax elements such as motion vectors, intra mode indicators, partitioning information, and other such syntax information to the entropy coding unit 56.

[0046] The motion estimation unit 42 and the motion compensation unit 44 may be highly integrated but are shown separately for conceptual purposes. The motion estimation performed by the motion estimation unit 42 is the process of generating motion vectors that estimate the motion of a video block. The motion vectors may, for example, indicate the displacement of the PU of a video block in the current video frame or picture relative to a predicted block in a reference frame (or other coded unit) related to the current block being coded in the current frame (or other coded unit). The predicted block is a block that has been found to closely match the coded block in terms of pixel differences, which may be determined by the difference absolute sum of differences (SAD), difference square sum of differences (SSD), or other difference metrics. In some examples, the video encoder 20 may compute pixel position values ​​of the reference picture that are finer than integers, stored in the reference frame memory 64. For example, the video encoder 20 may interpolate values ​​of quarter-pixel, eighth-pixel, or other fractional pixel positions of the reference picture. Therefore, the motion estimation unit 42 may perform motion searches related to full pixel positions and fractional pixel positions and output motion vectors with fractional pixel accuracy.

[0047] The motion estimation unit 42 calculates motion vectors for the PU of video blocks in the intercoded slice by comparing the PU's position with the predicted block's position in the reference picture. The reference picture may be selected from a first reference picture list (List 0) or a second reference picture list (List 1), each of which identifies one or more reference pictures stored in the reference frame memory 64. The motion estimation unit 42 transmits the calculated motion vectors to the entropy coding unit 56 and the motion compensation unit 44.

[0048] The motion compensation performed by the motion compensation unit 44 may include retrieving or generating a predicted block based on the motion vector determined by the motion estimation unit 42. Again, the motion estimation unit 42 and the motion compensation unit 44 may be functionally integrated in some examples. Upon receiving a motion vector for the PU of the current video block, the motion compensation unit 44 may find the predicted block pointed to by the motion vector in one of the reference picture lists. The adder 50 forms a residual video block by subtracting the pixel values ​​of the predicted block from the pixel values ​​of the current video block being coded, as will be considered below, to form a pixel difference value. Generally, the motion estimation unit 42 performs motion estimation related to the lumen component, and the motion compensation unit 44 uses a motion vector calculated based on the lumen component for both the chromen and lumen components. The mode selection unit 40 may also generate syntax elements related to the video block and video slice for use by the video decoder 30 when decoding the video block of the video slice.

[0049] The intra-prediction unit may inter-predict the current block as an alternative to the inter-prediction performed by the motion estimation unit 42 and the motion compensation unit 44 as described above. In particular, the intra-prediction unit 46 may determine the intra-prediction mode to use to encode the current block. In some examples, the intra-prediction unit 46 may encode the current block using various intra-prediction modes during separate encoding paths, for example, and the intra-prediction unit 46 (or the mode selection unit 40 in some examples) may select the appropriate intra-prediction mode to use from the tested modes.

[0050] For example, the intra-prediction unit 46 may calculate rate distortion values ​​using rate distortion analysis on various tested intra-prediction modes and select the intra-prediction mode with the best rate distortion characteristics among the tested modes. Rate distortion analysis generally determines the amount of distortion (or error) between the encoded block and the original unencoded block encoded to produce the encoded block, and the bit rate (i.e., number of bits) used to produce the encoded block. The intra-prediction unit 46 may calculate ratios from the distortion and rates on various encoded blocks to determine which intra-prediction mode exhibits the best rate distortion value for a block.

[0051] Furthermore, the intra-prediction unit 46 may be configured to code depth blocks of the depth map using a depth modeling mode (DMM). The mode selection unit 40 may, for example, use rate-distortion optimization (RDO) to determine whether an available DMM mode produces better coding results than the intra-prediction mode or other DMM modes. Data regarding the texture image corresponding to the depth map may be stored in the reference frame memory 64. The motion estimation unit 42 and the motion compensation unit 44 may also be configured to inter-predict depth blocks of the depth map.

[0052] After selecting an intra-prediction mode for a block (for example, one of the normal intra-prediction mode or DMM mode), the intra-prediction unit 46 may provide the entropy coding unit 56 with information indicating the selected intra-prediction mode for the block. The entropy coding unit 56 may encode the information indicating the selected intra-prediction mode. The video encoder 20 may include in the transmit bitstream configuration data, which may contain multiple intra-prediction mode index tables and multiple modified intra-prediction mode index tables (also known as codeword mapping tables), definitions of coding contexts for various blocks, as well as indications of the most likely intra-prediction mode, intra-prediction mode index table, and modified intra-prediction mode index table to use for each context.

[0053] The video encoder 20 forms a residual video block by subtracting predicted data from the mode selection unit 40 from the original video block being coded. The adder 50 represents one or more components that perform this subtraction.

[0054] The transformation processing unit 52 applies a transformation, such as a discrete cosine transform (DCT) or a similar transformation, to the residual block to generate a video block containing residual transformation coefficient values. The transformation processing unit 52 may perform other transformations similar to the DCT. Wavelet transforms, integer transforms, subband transforms, or other types of transformations may also be used.

[0055] The transformation processing unit 52 applies the transformation to the residual block to generate a block of residual transformation coefficients. The transformation may convert the residual information from the pixel value domain to a transformation domain such as the frequency domain. The transformation processing unit 52 may send the resulting transformation coefficients to the quantization unit 54. The quantization unit 54 quantizes the transformation coefficients to further reduce the bit rate. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may be modified by adjusting the quantization parameters. In some examples, the quantization unit 54 may then perform a scan of the matrix containing the quantized transformation coefficients. Alternatively, the entropy coding unit 56 may perform the scan.

[0056] After quantization, the entropy coding unit 56 entropy codes the quantized transformation coefficients. For example, the entropy coding unit 56 may perform context-adaptive variable length coding (CAVLC), context-adaptive binary arithmetic coding (CABAC), syntax-based context-adaptive binary arithmetic coding (SBAC), probability interval partitioning entropy (PIPE) coding, or another entropy coding technique. In the case of context-based entropy coding, the context may be based on neighboring blocks. After entropy coding by the entropy coding unit 56, the encoded bitstream may be sent to another device (e.g., video decoder 30) or archived for later transmission or retrieval.

[0057] The inverse quantization unit 58 and the inverse transform unit 60 apply inverse quantization and inverse transform, respectively, to reconstruct the residual block in the pixel region for later use as a reference block. The motion compensation unit 44 may compute the reference block by adding the residual block to a predicted block of one of the frames in the reference frame memory 64. The motion compensation unit 44 may also apply one or more interpolation filters to the reconstructed residual block to compute pixel values ​​finer than integers for use in motion estimation. The adder 62 adds the reconstructed residual block to the motion-compensated predicted block generated by the motion compensation unit 44 to produce a reconstructed video block for storage in the reference frame memory 64. The reconstructed video block may be used by the motion estimation unit 42 and the motion compensation unit 44 as a reference block for intercoding blocks of subsequent video frames.

[0058] Figure 3 is a block diagram showing an example of a video decoder 30 that may implement video coding techniques. In the example in Figure 3, the video decoder 30 includes an entropy decoding unit 70, a motion compensation unit 72, an intra-prediction unit 74, an inverse quantization unit 76, an inverse transform unit 78, a reference frame memory 82, and an adder 80. In some examples, the video decoder 30 may perform a decoding path that is generally the reverse of the coding path described in relation to the video encoder 20 (Figure 2). The motion compensation unit 72 may generate prediction data based on motion vectors received from the entropy decoding unit 70, while the intra-prediction unit 74 may generate prediction data based on an intra-prediction mode indicator received from the entropy decoding unit 70.

[0059] During the decoding process, the video decoder 30 receives an encoded video bitstream from the video encoder 20, representing the video blocks and associated syntax elements of the encoded video slice. The entropy decoding unit 70 of the video decoder 30 entropy-decodes the bitstream to generate quantized coefficients, motion vectors or intra-predictive mode indicators, and other syntax elements. The entropy decoding unit 70 transfers the motion vectors and other syntax elements to the motion compensation unit 72. The video decoder 30 may receive syntax elements at the video slice level and / or at the video block level.

[0060] When a video slice is coded as an intra-coded (I) slice, the intra-prediction unit 74 may generate prediction data about the video blocks of the current video slice based on the signaled intra-prediction mode and data from already decoded blocks of the current frame or picture. When a video frame is coded as an intercoded (e.g., B, P, or GPB) slice, the motion compensation unit 72 generates prediction blocks about the video blocks of the current video slice based on motion vectors and other syntax elements received from the entropy decoding unit 70. The prediction blocks may be generated from one of the reference pictures in one of the reference picture lists. The video decoder 30 may construct reference frame lists List 0 and List 1 using default construction techniques based on the reference pictures stored in the reference frame memory 82.

[0061] The motion compensation unit 72 determines prediction information about the video block of the current video slice by analyzing motion vectors and other syntax elements, and uses the prediction information to generate a prediction block about the current video block being decoded. For example, the motion compensation unit 72 uses some of the received syntax elements to determine the prediction mode used to code the video block of the video slice (e.g., intra or interprediction), the slice type of interprediction (e.g., B slice, P slice, or GPB slice), construction information about one or more of the reference picture lists for the slice, motion vectors for each intercoded video block of the slice, the status of the interprediction for each intercoded video block of the slice, and other information for decoding the video block in the current video slice.

[0062] The motion compensation unit 72 may also perform interpolation based on an interpolation filter. The motion compensation unit 72 may use the interpolation filter used by the video encoder 20 during the encoding of the video block to calculate the interpolated values ​​for pixels finer than the integers of the reference block. In this case, the motion compensation unit 72 may determine the interpolation filter used by the video encoder 20 from the received syntax elements and use the interpolation filter to generate the predicted block.

[0063] Data relating to the texture image corresponding to the depth map may be stored in the reference frame memory 82. The motion compensation unit 72 may also be configured to interpret depth blocks of the depth map.

[0064] Image and video compression has grown rapidly, giving rise to various coding standards. Such video coding standards include Advanced Video Coding (AVC), also known as ITU-T H.261, ISO / IEC Expert Group on Video (MPEG)-1 Part 2, ITU-T H.262 or International Organization for Standardization (ISO) / International Electrotechnical Commission (IEC) MPEG-2 Part 2, ITU-T H.263, ISO / IEC MPEG-4 Part 2, ITU-T H.264 or ISO / IEC MPEG-4 Part 10, and High Efficiency Video Coding (HEVC), also known as ITU-T H.265 or MPEG-H Part 2. AVC includes extensions such as Scalable Video Coding (SVC), Multiview Video Coding (MVC), Multiview Video Coding plus Depth (MVC+D), and 3D AVC (3D-AVC). HEVC includes extensions such as Scalable HEVC (SHVC), Multi-View HEVC (MV-HEVC), and 3D HEVC (3D-HEVC).

[0065] Versatile Video Coding (VVC) is a new video coding standard being developed by the ITU-T and ISO / IEC Joint Video Experts Team (JVET). As of the writing of this specification, the latest working draft (WD) of VVC is included in JVET-K1001-v1. JVET document JVET-K0325-v3 includes high-level syntax revisions for VVC.

[0066] In general, this disclosure describes the technology based on the VVC standard under development. However, the technology also conforms to the specifications of other video / media codecs.

[0067] Video compression techniques reduce or eliminate redundancy inherent in video sequences by performing spatial (intra-picture) prediction and / or temporal (inter-picture) prediction. For block-based video coding, a video slice (e.g., a video picture or part of a video picture) may be divided into video blocks, which may also be called tree blocks, coding tree blocks (CTBs), coding tree units (CTUs), coding units (CUs), and / or coding nodes. Video blocks in an intra-coded (I) slice of a picture are coded using spatial predictions related to reference samples in neighboring blocks within the same picture. Video blocks in an inter-coded (P or B) slice of a picture may use spatial predictions related to reference samples in neighboring blocks within the same picture or temporal predictions related to reference samples in other reference pictures. A picture may be called a frame, and a reference picture may be called a reference frame.

[0068] Spatial or temporal prediction yields a predicted block for the block to be coded. Residual data represents the difference in pixels between the original block to be coded and the predicted block. The intercoded block is encoded by motion vectors pointing to the reference sample block forming the predicted block, and residual data showing the difference between the coded block and the predicted block. The intracoded block is encoded by the intracoding mode and residual data. For further compression, the residual data may be transformed from a pixel region to a transformation region, yielding residual transformation coefficients, which may then be quantized. The quantized transformation coefficients, initially arranged in a two-dimensional array, may be scanned to generate a one-dimensional vector of transformation coefficients, and entropy coding may be applied to achieve further compression.

[0069] In video codec specifications, a picture is identified for multiple purposes, including use as a reference picture in interpretation, for outputting the picture from the decoded picture buffer (DPB), for scaling motion vectors, and for weighted prediction. In AVC and HEVC, a picture may be identified by a picture order count (POC). In AVC and HEVC, a picture in the DPB may be marked as "used for short-term reference," "used for long-term reference," or "not used for reference." When a picture is marked as "not used for reference," it can no longer be used for prediction. When a picture is no longer needed for output, it may be removed from the DPB.

[0070] In AVC, there are two types of reference pictures: short-term and long-term. A reference picture can be marked as "not for reference" when it is no longer needed for reference in predictions. The transition between these three statuses (short-term, long-term, and not for reference) is controlled by the decoded reference picture marking process. There are two alternative decoded reference picture marking mechanisms: the implicit sliding window process and the explicit memory management control operation (MMCO) process. The sliding window process marks a short-term reference picture as "not for reference" when the number of reference frames equals a given maximum number (max_num_ref_frames in the Sequence Parameter Set (SPS)). Short-term reference pictures are stored in a first-in, first-out (FIFO) order so that the most recently decoded short-term picture is held in the DPB.

[0071] An explicit MMCO process may include multiple MMCO commands. An MMCO command may mark one or more short-term or long-term reference pictures as "not for reference," may mark all pictures as "not for reference," or may mark a current reference picture or an existing short-term reference picture as long-term and then assign a long-term picture index to that long-term reference picture.

[0072] In AVC, the process of marking reference pictures and outputting and deleting pictures from the DPB is performed after the pictures have been decoded.

[0073] HEVC introduces a different method for managing reference pictures called the Reference Picture Set (RPS). The most fundamental difference between the RPS concept and AVC's MMCO / Moving Window process is that, for each particular slice, a complete set of reference pictures used by the current picture or any subsequent picture is provided. Thus, the complete set of all pictures that must be held in the DPB for use by the current or future pictures is signaled. This differs from the AVC method, where only changes relative to the DPB are signaled. According to the RPS concept, information from earlier pictures in the decoding order is not needed to maintain the correct status of reference pictures in the DPB.

[0074] The order of picture decoding and the behavior of the DPB in HEVC are modified compared to AVC to take advantage of the RPS and improve error tolerance. In AVC, picture marking and buffering (both outputting and deleting decoded pictures from the DPB) are generally applied after the current picture has been decoded. In HEVC, the RPS is decoded first from the slice header of the current picture, and then the picture marking and buffering are generally applied before the current picture is decoded.

[0075] Each slice header in HEVC may contain parameters for signaling the RPS for the picture containing the slice. The only exception is that the RPS is not signaled for Instantaneous Decoding Refresh (IDR) slices. Instead, the RPS is presumed to be empty. For I slices that do not belong to an IDR picture, an RPS may be provided even if those I slices belong to an I picture, because there may be pictures that follow the I picture in the decoding order, using interpretation from the picture that preceded the I picture in the decoding order. The number of pictures in the RPS does not exceed the DPB size limit specified by the sps_max_dec_pic_buffering syntax element of the SPS.

[0076] Each picture is associated with a POC value that represents the order of the output. The slice header contains a fixed-length codeword, pic_order_cnt_lsb, which represents the least significant bit (LSB) of the complete POC value, also known as the POC LSB. The length of the codeword is signaled within the SPS and can be, for example, between 4 and 16 bits. The RPS concept uses the POC to identify the reference picture. In addition to its own POC value, each slice header either directly contains or inherits from the SPS a coded representation of the POC value (or LSB) of each picture in the RPS.

[0077] Each picture's RPS consists of five different lists of reference pictures, also known as the five RPS subsets. RefPicSetStCurrBefore consists of all short-term reference pictures that are before the current picture in both the decoding order and the output order and may be used in the inter-prediction of the current picture. RefPicSetStCurrAfter consists of all short-term reference pictures that are before the current picture in the decoding order and after the current picture in the output order and may be used in the inter-prediction of the current picture. RefPicSetStFoll consists of all short-term reference pictures that may be used in the inter-prediction of one or more pictures that follow the current picture in the decoding order and are not used in the inter-prediction of the current picture. RefPicSetLtCurr consists of all long-term reference pictures that may be used in the inter-prediction of the current picture. RefPicSetLtFoll consists of all long-term reference pictures that may be used in interpretation of one or more pictures that follow the current picture in the decoding order, but are not used in interpretation of the current picture.

[0078] RPS is signaled using up to three loops that are repeated for different types of reference pictures: short-term reference pictures with a smaller POC value than the current picture, short-term reference pictures with a larger POC value than the current picture, and long-term reference pictures. In addition, a flag (used_by_curr_pic_X_flag) is sent for each picture to indicate whether the reference picture is used for referencing by the current picture (included in one of the lists RefPicSetStCurrBefore, RefPicSetStCurrAfter, or RefPicSetLtCurr) or not (included in one of the lists RefPicSetStFoll or RefPicSetLtFoll).

[0079] Figure 4 shows RPS 400 with the current picture B14, along with the entries (e.g., pictures) for all subsets 402 of RPS 400. In the example in Figure 4, the current picture B14 contains exactly one picture in each of the five subsets 404 (aka RPS subsets). P8 is the picture in subset 402 called RefPicSetStCurrBefore because the picture is before B14 in output order and is used by B14. P12 is the picture in subset 402 called RefPicSetStCurrAfter because the picture is after B14 in output order and is used by B14. P13 is the picture in subset 402 called RefPicSetStFoll because the picture is a short-term reference picture that is not used by B14 (but must be held in the DPB because the picture is used by B15). P4 is a picture in subset 402 called RefPicSetLtCurr because it is a long-term reference picture used by B14. I0 is a picture in subset 402 called RefPicSetLtFoll because it is a long-term reference picture not used by the current picture (but it must be held in DPB because it is used by B15).

[0080] The short-term portion of RPS 400 may be directly included in the slice header. Alternatively, the slice header may contain only a syntax element representing an index referencing a predefined list of RPS sent within an active SPS. The short-term portion of RPS 402 may be signaled using either two different methods, interRPS described below or intraRPS described here. When intraRPS is used, num_negative_pics and num_positive_pics, representing the lengths of two different lists of reference pictures, are signaled. These lists contain reference pictures with negative and positive POC differences compared to the current picture, respectively. Each element of these lists is encoded by a variable-length coding that represents the difference in POC values ​​related to the previous element in the list minus 1. For the first picture in each list, the signaling relates to the value of the current picture minus 1.

[0081] When encoding recurring RPSs within a sequence parameter set, it is possible to encode elements of one RPS (e.g., RPS 400) by referencing another already encoded RPS within the sequence parameter set. This is called interRPS. Since all RPSs in a sequence parameter set reside within the same Network Abstraction Layer (NAL) unit, there are no error robustness issues associated with this method. The syntax for interRPS takes advantage of the fact that the RPS of the current picture can be predicted from the RPS of already decoded pictures. This is because all reference pictures of the current picture must either be reference pictures of previous pictures or already decoded pictures themselves. It is sufficient to indicate which of these pictures is the reference picture and which should be used for predicting the current picture. Therefore, the syntax includes the following: an index pointing to the RPS to be used as the predictor, a delta_POC added to the predictor's delta_POC to obtain the delta POC of the current RPS, and a set of indicators showing which pictures are reference pictures and whether those pictures are used only for predicting future pictures.

[0082] Encoders that wish to utilize long-term reference pictures must set the SPS syntax element long_term_ref_pics_present_flag to 1. In this case, long-term reference pictures can be signaled in the slice header by a fixed-length codeword poc_lsb_lt representing the least significant bit of the complete POC value for each long-term picture. Each poc_lsb_lt is a copy of the pic_order_cnt_lsb codeword signaled for a particular long-term picture. It is also possible to signal a set of long-term pictures in the SPS as a list of POC LSB values. In this case, the POC LSBs for the long-term pictures can be signaled in the slice header as an index to this list.

[0083] The delta_poc_msb_cycle_lt_minus1 syntax element may be further signaled to enable the calculation of the full POC distance of long-term reference pictures to the current picture. The codeword delta_poc_msb_cycle_lt_minus1 is required to be signaled for each long-term reference picture that has the same POC LSB value as any other reference picture in the RPS.

[0084] Regarding the marking of reference pictures in HEVC, generally, several pictures exist in the DPB before the picture is decoded. Some pictures are available for prediction and may therefore be marked as "Used for reference". Other pictures may not be available for prediction but are waiting for output and may therefore be marked as "Not used for reference". When the slice header is parsed, the picture marking process is performed before the slice data is decoded. Pictures that exist in the DPB and are marked as "Used for reference" but are not included in the RPS are marked as "Not used for reference". When used_by_curr_pic_X_flag is equal to zero, pictures that do not exist in the DPB but are included in the reference picture set are ignored. However, if used_by_curr_pic_X_flag is equal to 1 instead, this reference picture was intended to be used for prediction in the current picture but is missing. In that case, the unintended loss of a picture is inferred, and the decoder should take appropriate action.

[0085] After the current picture is decrypted, it will be marked as "to be used for short-term reference."

[0086] Next, the construction of reference picture lists in HEVC is considered. In HEVC, the term interpretation is used to refer to predictions derived from data elements (e.g., sample values ​​or motion vectors) of reference pictures other than the picture currently being decoded. Similar to AVC, a picture can be predicted from multiple reference pictures. The reference pictures used for interpretation are organized into one or more reference picture lists. A reference index identifies which of the reference pictures in the list should be used to generate the prediction signal.

[0087] A single reference picture list, List 0, is used for the P slice, and two reference picture lists, List 0 and List 1, are used for the B slice. Similar to AVC, building reference picture lists in HEVC involves initializing and modifying the reference picture lists.

[0088] In AVC, the initialization process for List 0 differs for P slices (where the decoding order is used) and B slices (where the output order is used). In HEVC, the output order is used in both cases.

[0089] Initializing the reference picture list generates default List 0 and List 1 (if the slice is a B slice) based on three RPS subsets: RefPicSetStCurrBefore, RefPicSetStCurrAfter, and RefPicSetLtCurr. First, short-term pictures in the order of earlier (later) outputs are inserted into List 0 (List 1) in ascending order of their POC distance from the current picture. Then, short-term pictures in the order of later (later) outputs are inserted into List 0 (List 1) in ascending order of their POC distance from the current picture, and finally, long-term pictures are inserted last. In terms of RPS, with respect to List 0, entries for RefPicSetStCurrBefore are inserted into the initial list, followed by entries for RefPicSetStCurrAfter. Then, if available, entries for RefPicSetLtCurr are appended to the end.

[0090] In HEVC, if the number of entries in the list is less than the target number of active reference pictures (signaled in the picture parameter set or slice header), the process described above is repeated (reference pictures already added to the reference picture list are added again). If the number of entries is greater than the target number, the list is truncated.

[0091] After the referenced picture list is initialized, it can be modified based on referenced picture list modification commands so that the referenced pictures for the current picture can be arranged in any order, including cases where a particular referenced picture may appear in more than one position in the list. When a flag indicating the presence of list modification is set to 1, a fixed number of commands (equal to the target number of entries in the referenced picture list) are signaled, with each command inserting one entry into the referenced picture list. The referenced picture is identified within the command by an index to the list of referenced pictures for the current picture, derived from the RPS signaling. This differs from the modification of the referenced picture list in H.264 / AVC, where a picture is identified either by a picture number (derived from the frame_num syntax element) or a long-term referenced picture index, and fewer commands may be required, for example, to swap the first two entries in the initial list or to insert one entry at the beginning of the initial list and shift the other entries.

[0092] The reference picture list is not allowed to include any reference picture with a TemporalId greater than the current picture. An HEVC bitstream can consist of several temporal sublayers. Each NAL unit belongs to a specific sublayer indicated by its TemporalId (equal to temporal_id_plus1 - 1).

[0093] The management of reference pictures is based directly on the reference picture list. JCT-VC document JCTVC-G643 includes a technique for directly using three reference picture lists, reference picture list 0, reference picture list 1, and idle reference picture list, for the management of reference picture lists in the DPB, thereby avoiding the need for signaling and decoding processes that include either 1) the AVC move window and MMCO process and reference picture list initialization and modification process, or 2) the HEVC reference picture set and reference picture list initialization and modification process.

[0094] Methods for managing reference pictures can have several problems. The AVC method involves complex move windows, MMCO processes, and reference picture list initialization and modification processes. Furthermore, the loss of a picture can lead to a loss of DPB status in terms of which pictures should have been in the DPB for further interpretation purposes. The HEVC method does not have the problem of DPB status loss. However, the HEVC method involves complex reference picture set signaling and derivation processes as well as complex reference picture list initialization and modification processes. The JCTVC-G643 method, which directly uses three reference picture lists—reference picture list 0, reference picture list 1, and idle reference picture list—for managing reference pictures within a DPB, includes the following points: a third reference picture list, i.e., the idle reference picture list; two-part coding of the difference of the POC as a "short-term" portion and a ue(v)-coded "long-term" portion; granularity of the POC based on TemporalId for coding the difference of the POC; the use of two-part coding of the difference of the POC to determine whether to mark it as "used for short-term references" or "used for long-term references"; the description of a subset of reference picture lists that gives the ability to specify a reference picture by deleting the reference picture from the end of the description of a particular prior reference picture list; a reference picture list copy mode enabled by the syntax element ref_pic_list_copy_flag; and the reference picture list description process. Each of the points mentioned above unnecessarily complicates the method. Furthermore, the decoding process for the JCTVC-G643 reference picture list is also complex. Long-term reference picture signaling may require signaling of POC cycles within the slice header, which is inefficient.

[0095] To address the problems listed above, the following solutions are disclosed herein, each of which can be applied individually, and some of which can be applied in combination: 1) The marking of a reference picture is directly based on two reference picture lists, namely, reference picture list 0 and reference picture list 1. 1a) Information for the derivation of the two reference picture lists is signaled based on syntax elements and syntax structures in the SPS, PPS, and / or slice header. 1b) Each of the two reference picture lists for a picture is explicitly signaled within a reference picture list structure. 1b.i) One or more reference picture list structures can be signaled within the SPS, and each of those reference picture list structures can be referenced by an index from the slice header. 1b.ii) Each of reference picture lists 0 and 1 can be directly signaled within the slice header. 2) Information for the derivation of two reference picture lists is signaled with respect to all types of slices, namely B (double prediction), P (short prediction), and I (intra) slices. The term slice refers to a set of coding tree units, such as slices of HEVC or modern VVC WD, and the term slice may also refer to any other set of coding tree units, such as tiles of HEVC. 3) Two reference picture lists are generated with respect to all types of slices, namely B, P, and I slices. 4) The two reference picture lists are constructed directly without using a reference picture list initialization process and a reference picture list modification process. 5) In each of the two reference picture lists, reference pictures that may be used for interpretation of the current picture may only be referenced by the first few entries of the list. These entries are called the active entries of the list, while the other entries are called the inactive entries of the list. Both the total number of entries in the list and the number of active entries can be derived.6) A picture referenced by an inactive entry in a reference picture list may not be referenced by another entry in the reference picture list or any other entry in the reference picture list. 7) Long-term reference pictures may be identified by only a certain number of POC LSBs, which may be greater than the number of POC LSBs signaled in the slice header for the derivation of the POC value, and this number is shown in the SPS. 8) The reference picture list structure may be signaled only in the slice header, and both short-term and long-term reference pictures may be identified by the POC LSBs of those reference pictures, which may be represented by a different number of bits than the number of bits used to represent the POC LSBs signaled in the slice header for the derivation of the POC value, and the number of bits used to represent the POC LSBs for identifying short-term and long-term reference pictures may be different. 9) The reference picture list structure is signaled only within the slice header, and no distinction is made between short-term and long-term reference pictures; all reference pictures are simply called reference pictures, and the reference pictures are identified by the POC LSB of those reference pictures, which may be represented by a different number of bits than the number of bits used to represent the POC LSB that is signaled within the slice header for the derivation of the POC value.

[0096] A first embodiment of the present disclosure is provided. The description relates to the latest VVC WD. In this embodiment, two sets of reference picture list structures are signaled in the SPS, one for each of reference picture list 0 and reference picture list 1.

[0097] Definitions for some of the terms used herein are given. Intra-random access point (IRAP) picture: A coded picture in which each video coding layer (VCL) NAL unit has a nal_unit_type equal to IRAP_NUT. Non-IRAP picture: A coded picture in which each VCL NAL unit has a nal_unit_type equal to NON_IRAP_NUT. Reference picture list: A list of reference pictures used for interpretation of P or B slices. Two reference picture lists, reference picture list 0 and reference picture list 1, are generated for each slice of non-IRAP picture. The set of unique pictures referenced by all entries in the two reference picture lists associated with a picture consists of all reference pictures that may be used for interpretation of the associated picture or any picture that follows the associated picture in the order of decoding. To decode the slice data of a P slice, only reference picture list 0 is used for interpretation. To decode the slice data of a B slice, both reference picture lists are used for interpretation. To decode the slice data of an I-slice, the reference picture list is not used for interpretation. Long-term reference picture (LTRP): A picture marked as "used for long-term reference". Short-term reference picture (STRP): A picture marked as "used for short-term reference".

[0098] The terms “used for short-term reference,” “used for long-term reference,” and “not used for reference” are defined in Section 8.3.3 Decoding process for reference picture marking in VVC, in Section 8.3.2 Decoding process for reference picture set in HEVC, and in Section 7.4.3.3 Decoded reference picture marking semantics in AVC. When used herein, the terms have the same meaning.

[0099] The relevant syntax and semantics for the first embodiment are given below.

[0100] Syntax of NAL unit headers

[0101] [Table 1]

[0102] Syntax of the raw byte sequence payload (RBSP) for the sequence parameter set

[0103] [Table 2]

[0104] RBSP syntax for picture parameter sets

[0105] [Table 3]

[0106] Slice header syntax

[0107] [Table 4]

[0108] Syntax of the reference picture list structure

[0109] [Table 5]

[0110] NAL Unit Header Semantics

[0111] `forbidden_zero_bit` is equal to 0. `nal_unit_type` specifies the type of RBSP data structure included in the NAL unit.

[0112] [Table 6]

[0113] The value obtained by subtracting 1 from nuh_temporal_id_plus1 specifies the temporal identifier for the NAL unit. The value of nuh_temporal_id_plus1 is not equal to 0. The variable TemporalId is specified as follows: TemporalId = nuh_temporal_id_plus1 - 1. When nal_unit_type is equal to IRAP_NUT, the coded slice belongs to an IRAP picture, and TemporalId is equal to 0. The value of TemporalId is the same for all VCL NAL units of an access unit. The value of TemporalId for a coded picture or access unit is the value of TemporalId for the VCL NAL unit of the coded picture or access unit. The value of TemporalId for non-VCL NAL units is constrained as follows: When nal_unit_type is equal to SPS_NUT, TemporalId is equal to 0, and the TemporalId of an access unit containing a NAL unit is equal to 0. If nal_unit_type is not equal to EOS_NUT or EOB_NUT, then TemporalId is equal to 0. Otherwise, TemporalId is greater than or equal to the TemporalId of the access unit containing the NAL unit. When the NAL unit is a non-VCL NAL unit, the value of TemporalId is equal to the smallest of the TemporalId values ​​of all access units to which the non-VCL NAL unit belongs. When nal_unit_type is equal to PPS_NUT, TemporalId may be greater than or equal to the TemporalId of the containing access unit, since all Picture Parameter Sets (PPS) may be included at the beginning of the bitstream and the first coded picture has a TemporalId equal to 0.When nal_unit_type is equal to PREFIX_SEI_NUT or SUFFIX_SEI_NUT, TemporalId may be greater than or equal to the TemporalId of the containing access unit, because the SEI NAL unit may contain information applicable to a subset of the bitstream containing access units that have a TemporalId value greater than the TemporalId of the access unit containing the SEI NAL unit. nuh_reserved_zero_7bits is equal to '0000000'. Other values ​​for nuh_reserved_zero_7bits may be specified in the future by ITU_T | ISO / IEC. The decoder ignores (i.e., removes and discards) NAL units with nuh_reserved_zero_7bits values ​​that are not equal to '0000000'.

[0114] Semantics of RBSP for sequence parameter sets

[0115] log2_max_pic_order_cnt_lsb_minus4 specifies the value of the variable MaxPicOrderCntLsb, which is used in the decoding process for picture order count, as follows: MaxPicOrderCntLsb = 2( log2_max_pic_order_cnt_lsb_minus4 + 4 ). The value of log2_max_pic_order_cnt_lsb_minus4 is in the range of 0 to 12, including 0 and 12. The value of sps_max_dec_pic_buffering_minus1 plus 1 specifies the maximum required size of the decoded picture buffer for CVS in units of picture storage buffer. The value of sps_max_dec_pic_buffering_minus1 is in the range of 0 to MaxDpbSize - 1, including 0 and MaxDpbSize - 1, where MaxDpbSize is specified elsewhere. A long_term_ref_pics_flag equal to 0 specifies that LTRP will not be used for interpretation of any coded pictures in CVS. A long_term_ref_pics_flag equal to 1 specifies that LTRP may be used for interpretation of one or more coded pictures in CVS. additional_lt_poc_lsb specifies the value of the variable MaxLtPicOrderCntLsb used in the decoding process for the reference picture list, i.e., MaxLtPicOrderCntLsb = 2( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_lt_poc_lsb ). The value of additional_lt_poc_lsb is in the range from 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4. If it does not exist, the value of additional_lt_poc_lsb is presumed to be equal to 0.num_ref_pic_lists_in_sps[i] specifies the number of ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structures in the SPS whose listIdx is equal to i. The value of num_ref_pic_lists_in_sps[i] is in the range of 0 to 64, including 0 and 64. For each value of listIdx (equal to 0 or 1), the decoder should allocate memory for a total of num_ref_pic_lists_in_sps[i] + 1 ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structures, since there may be one ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure directly signaled within the slice header of the current picture.

[0116] RBSP semantics of picture parameter sets

[0117] The value obtained by adding 1 to num_ref_idx_default_active_minus1[i] specifies the inferred value of the variable NumRefIdxActive[0] for P or B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 0, and specifies the inferred value of NumRefIdxActive[1] for B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 1. The value of num_ref_idx_default_active_minus1[i] is in the range of 0 to 14, including 0 and 14.

[0118] Slice header semantics

[0119] When present, the values ​​of the slice header syntax elements slice_pic_parameter_set_id and slice_pic_order_cnt_lsb are the same for all slice headers of the coded picture. ... slice_type specifies the coding type of the slice according to Table 7-3.

[0120] [Table 7]

[0121] When nal_unit_type is equal to IRAP_NUT, i.e., the picture is an IRAP picture, slice_type is equal to 2. ... slice_pic_order_cnt_lsb specifies the modulo MaxPicOrderCntLsb of the picture order count for the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4 + 4 bits. The value of slice_pic_order_cnt_lsb is in the range from 0 to MaxPicOrderCntLsb - 1, including 0 and MaxPicOrderCntLsb - 1. When slice_pic_order_cnt_lsb does not exist, it is inferred that slice_pic_order_cnt_lsb is equal to 0. A ref_pic_list_sps_flag[i] equal to 1 specifies that the current picture's reference picture list i is derived based on one of the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structures in the active SPS where listIdx is equal to i. A ref_pic_list_sps_flag[i] equal to 0 specifies that the current picture's reference picture list i is derived based on the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure where listIdx is equal to i and is directly included in the slice header of the current picture. When num_ref_pic_lists_in_sps[i] is equal to 0, the value of ref_pic_list_sps_flag[i] is equal to 0. ref_pic_list_idx[i] specifies an index to a list of ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structures in the active SPS where listIdx is equal to i, which is used to derive the reference picture list i of the current picture.The syntax element ref_pic_list_idx[i] is represented by the Ceil( Log2(num_ref_pic_lists_in_sps[i]) ) bit. If it does not exist, the value of ref_pic_list_idx[i] is presumed to be equal to 0. The value of ref_pic_list_idx[i] is in the range from 0 to num_ref_pic_lists_in_sps[i] - 1, including 0 and num_ref_pic_lists_in_sps[i] - 1. A num_ref_idx_active_override_flag equal to 1 specifies that the syntax element num_ref_idx_active_minus1[0] exists for P and B slices, and that the syntax element num_ref_idx_active_minus1[1] exists for B slices. A num_ref_idx_active_override_flag equal to 0 indicates that the syntax elements num_ref_idx_active_minus1[0] and num_ref_idx_active_minus1[1] do not exist. When num_ref_idx_active_minus1[i] exists, it specifies the value of the variable NumRefIdxActive[i] as follows: NumRefIdxActive[i] = num_ref_idx_active_minus1[i] + 1. The value of num_ref_idx_active_minus1[i] is in the range of 0 to 14, including 0 and 14.

[0122] The value of NumRefIdxActive[i] - 1 specifies the largest reference index for reference picture list i that may be used to decode the slice. When the value of NumRefIdxActive[i] is equal to 0, the reference index for reference picture list i may not be used to decode the slice. For i equal to 0 or 1, if the current slice is a B slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[i] is presumed to be equal to num_ref_idx_default_active_minus1[i] + 1. If the current slice is a P slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[0] is presumed to be equal to num_ref_idx_default_active_minus1[0] + 1. If the current slice is a P slice, NumRefIdxActive[1] is presumed to be equal to 0. When the current slice is an I slice, it is inferred that both NumRefIdxActive[0] and NumRefIdxActive[1] are equal to 0.

[0123] Alternatively, for i equal to 0 or 1, the following applies after the above: rplsIdx1 is set to be equal to ref_pic_list_sps_flag[i] ? ref_pic_list_idx[i] : num_ref_pic_lists_in_sps[i], and numRpEntries[i] is equal to num_strp_entries[i][rplsIdx1] + num_ltrp_entries[i][rplsIdx1]. When NumRefIdxActive[i] is greater than numRpEntries[i], the value of NumRefIdxActive[i] is set to be equal to numRpEntries[i].

[0124] Semantics of the reference picture list structure

[0125] The ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure can exist within the SPS or within the slice header. Depending on whether the syntax structure is in the slice header or the SPS, the following applies: If it is in the slice header, the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure specifies the listIdx of the reference picture list for the current picture (the picture containing the slice). If not (present in SPS), the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure specifies a candidate for listIdx of the reference picture list, and the term “current picture” in the semantics explicitly stated for the remainder of this section refers to each picture in a CVS that has 1) one or more slices containing ref_pic_list_idx[listIdx] equal to an index to a list of ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structures present in the SPS, and 2) the SPS as the active SPS. num_strp_entries[listIdx][rplsIdx] specifies the number of STRP entries in the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. num_ltrp_entries[listIdx][rplsIdx] specifies the number of LTRP entries in the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. If none exist, the value of num_ltrp_entries[listIdx][rplsIdx] is presumed to be equal to 0.The variable NumEntriesInList[listIdx][rplsIdx] is derived as follows: NumEntriesInList[listIdx][rplsIdx] = num_strp_entries[listIdx][rplsIdx] + num_ltrp_entries[listIdx][rplsIdx]. The value of NumEntriesInList[listIdx][rplsIdx] is in the range from 0 to sps_max_dec_pic_buffering_minus1, including 0 and sps_max_dec_pic_buffering_minus1. lt_ref_pic_flag[listIdx][rplsIdx][i] equal to 1 specifies that the i-th entry of the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure is an LTRP entry. A value of lt_ref_pic_flag[listIdx][rplsIdx][i] equal to 0 specifies that the i-th entry of the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure is a STRP entry. If it does not exist, the value of lt_ref_pic_flag[listIdx][rplsIdx][i] is presumed to be equal to 0. A bitstream compliance requirement is that the sum of lt_ref_pic_flag[listIdx][rplsIdx][i] for all values ​​of i within the range from 0 to NumEntriesInList[listIdx][rplsIdx] - 1, including 0 and NumEntriesInList[listIdx][rplsIdx] - 1, is equal to num_ltrp_entries[listIdx][rplsIdx].delta_poc_st[listIdx][rplsIdx][i] specifies the difference between the picture order count value of the current picture and the picture order count value of the picture referenced by the i-th entry, when the i-th entry is the first STRP entry in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure, or when the i-th entry is a STRP entry in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure but is not the first STRP entry, it specifies the difference between the picture order count value of the picture referenced by the i-th entry and the picture order count value of the picture referenced by the previous STRP entry in the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. The value of delta_poc_st[listIdx][rplsIdx][i] is in the range of -215 to 215 - 1, including -215 and 215 - 1. poc_lsb_lt[listIdx][rplsIdx][i] specifies the value of MaxLtPicOrderCntLsb, modulo the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. The length of the poc_lsb_lt[listIdx][rplsIdx][i] syntax element is Log2(MaxLtPicOrderCntLsb) bits.

[0126] The decryption process is considered. The decryption process operates as follows with respect to the current picture CurrPic: Decryption of NAL units is defined below. The process below defines the following decryption process using syntax elements above the slice header layer. Variables and functions related to the picture order count are derived. This should only be called for the first slice of the picture. At the beginning of the decryption process for each slice of a non-IRAP picture, the decryption process for constructing the reference picture list is called to derive reference picture list 0 (RefPicList[0]) and reference picture list 1 (RefPicList[1]). The decryption process for marking reference pictures is called, and reference pictures may be marked as "not used for reference" or "used for long-term reference". This should only be called for the first slice of the picture. The decryption process for coding tree units, scaling, transformation, in-loop filtering, etc. is called. After all slices of the current picture have been decrypted, the current decrypted picture is marked as "used for short-term reference".

[0127] A NAL unit decoding process is considered. The input to this process is the NAL units of the current picture and their associated non-VCL NAL units. The output of this process is the analyzed RBSP syntax structure encapsulated in the NAL units. For each NAL unit, the decoding process extracts the RBSP syntax structure from the NAL unit and then analyzes the RBSP syntax structure.

[0128] A slice decoding process is considered that includes a decoding process for the picture order count. The output of this process is PicOrderCntVal, the picture order count of the current picture. The picture order count is used to identify the picture in order to derive motion parameters in merge mode and motion vector prediction and to check the decoder's compliance. Each coded picture is associated with a picture order count variable represented as PicOrderCntVal. When the current picture is not an IRAP picture, the variables prevPicOrderCntLsb and prevPicOrderCntMsb are derived as follows: Assume that prevTid0Pic is the previous picture in the decoding order, with a TemporalId equal to 0. The variable prevPicOrderCntLsb is set to be equal to slice_pic_order_cnt_lsb of prevTid0Pic. The variable prevPicOrderCntMsb is set to be equal to the PicOrderCntMsb of prevTid0Pic.

[0129] The variable PicOrderCntMsb for the current picture is derived as follows: If the current picture is an IRAP picture, PicOrderCntMsb is set to equal to 0. Otherwise, PicOrderCntMsb is derived as follows: if( ( slice_pic_order_cnt_lsb < prevPicOrderCntLsb ) && ( ( prevPicOrderCntLsb - slice_pic_order_cnt_lsb ) >= ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb + MaxPicOrderCntLsb else if( (slice_pic_order_cnt_lsb > prevPicOrderCntLsb ) && ( ( slice_pic_order_cnt_lsb - prevPicOrderCntLsb ) > ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb - MaxPicOrderCntLsb else PicOrderCntMsb = prevPicOrderCntMsb

[0130] PicOrderCntVal is derived as follows: PicOrderCntVal = PicOrderCntMsb + slice_pic_order_cnt_lsb.

[0131] Since slice_pic_order_cnt_lsb is inferred to be 0 for IRAP pictures, and both prevPicOrderCntLsb and prevPicOrderCntMsb are set to be equal to 0, all IRAP pictures have a PicOrderCntVal equal to 0. The value of PicOrderCntVal is in the range of -231 to 231 - 1, including -231 and 231 - 1. In a single CVS, the PicOrderCntVal values ​​for any two coded pictures are not the same.

[0132] At any given moment during the decoding process, the values ​​of PicOrderCntVal & (MaxLtPicOrderCntLsb - 1) for any two reference pictures in the DPB are not the same. The function PicOrderCnt(picX) is specified as follows: PicOrderCnt(picX) = PicOrderCntVal for picture picX. The function DiffPicOrderCnt(picA, picB) is specified as follows: DiffPicOrderCnt(picA, picB) = PicOrderCnt(picA) - PicOrderCnt(picB). The bitstream does not contain data that would result in a value of DiffPicOrderCnt(picA, picB) used in the decoding process that is not within the range of -215 to 215 - 1, including -215 and 215 - 1. Assuming X is the current picture and Y and Z are two other pictures in the same coded video sequence (CVS), Y and Z are considered to be in the same output order direction from X when both DiffPicOrderCnt(X, Y) and DiffPicOrderCnt(X, Z) are positive or both are negative.

[0133] A decoding process for constructing a reference picture list is considered. This process is called at the beginning of the decoding process for each slice of a non-IRAP picture. Reference pictures are addressed by a reference index, which is an index to the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (i.e., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, both reference picture list 0 and reference picture list 1 (i.e., RefPicList[1]) are used in decoding the slice data. At the beginning of the decoding process for each slice of a non-IRAP picture, reference picture lists RefPicList[0] and RefPicList[1] are derived. The reference picture lists are used in marking reference pictures or in decoding slice data. For I-slices of non-IRAP pictures that are not the first slice of a picture, RefPicList[0] and RefPicList[1] may be derived for the purpose of checking bitstream compliance, but their derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. For P-slices that are not the first slice of a picture, RefPicList[1] may be derived for the purpose of checking bitstream compliance, but its derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { if( ref_pic_list_sps_flag[i] ) RplsIdx[i] = ref_pic_list_idx[i] else RplsIdx[i] = num_ref_pic_lists_in_sps[i] for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[i][RplsIdx[i]]; j++ ) { if( !lt_ref_pic_flag[i][RplsIdx[i]][j] ) { RefPicPocList[i][j] = pocBase - delta_poc_st[i][RplsIdx[i]][j] if (There exists a reference picture picA in the DPB where PicOrderCntVal is equal to RefPicPocList[i][j]) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" pocBase = RefPicPocList[i][j] else { if (PicOrderCntVal & ( MaxLtPicOrderCntLsb - 1 ) is equal to poc_lsb_lt[i][RplsIdx[i]][j], there exists a reference picture picA in the DPB) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" } } }

[0134] For each i equal to 0 or 1, the following applies: The first NumRefIdxActive[i] entries in RefPicList[i] are called the active entries of RefPicList[i], and the other entries in RefPicList[i] are called the inactive entries of RefPicList[i]. For j in the range from 0 to NumEntriesInList[i][RplsIdx[i]] - 1, including 0 and NumEntriesInList[i][RplsIdx[i]] - 1, each entry in RefPicList[i][j] is called a STRP entry if lt_ref_pic_flag[i][RplsIdx[i]][j] is equal to 0, and is called an LTRP entry otherwise. A particular picture can be referenced by both an entry in RefPicList[0] and an entry in RefPicList[1]. A particular picture may be referenced by two or more entries in RefPicList[0] or by two or more entries in RefPicList[1]. Active entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that may be used for interpretation of the current picture and one or more pictures that follow the current picture in the decoding order. Inactive entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that are not used for interpretation of the current picture but may be used for interpretation of one or more pictures that follow the current picture in the decoding order. There may be one or more entries in RefPicList[0] or RefPicList[1] that are equal to "no reference picture" because the corresponding picture does not exist in the DPB. Each inactive entry in RefPicList[0] or RefPicList[0] that is equal to "no reference picture" should be ignored.For each active entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture", an unintended loss of picture should be inferred.

[0135] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i][RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0136] Decryption process for marking reference pictures

[0137] This process is called once per picture, after the decoding process for decoding the slice header and building the reference picture list for the slice, but before decoding the slice data. This process may result in one or more reference pictures in the DPB being marked as "Not for Reference" or "Used for Long-Term Reference". A decoded picture in the DPB can be marked as "Not for Reference", "Used for Short-Term Reference", or "Used for Long-Term Reference", however, at any given moment during the operation of the decoding process, it can be marked as just one of these three. Assigning one of these markings to a picture implicitly removes another of these markings, where applicable. When we say a picture is marked as "Used for Reference", this means collectively that the picture is marked as either "Used for Short-Term Reference" or "Used for Long-Term Reference" (but not both). When the current picture is an IRAP picture, all reference pictures (if any) currently in the DPB are marked as "Not for Reference". STRPs are identified by their PicOrderCntVal values. LTRPs are identified by the Log2(MaxLtPicOrderCntLsb) LSB of their PicOrderCntVal values. The following applies: For each LTRP entry in RefPicList[0] or RefPicList[1], if the referenced picture is a STRP, the picture is marked as "Used for long-term reference". Each referenced picture in the DPB that is not referenced by any entry in RefPicList[0] or RefPicList[1] is marked as "Not used for reference".

[0138] A detailed description of a second embodiment of the present disclosure is given. This section provides documentation of the second embodiment of the present disclosure as described above. The description relates to the latest VVC WD. In this embodiment, one set of reference picture list structures is signaled within the SPS and shared by reference picture list 0 and reference picture list 1.

[0139] RBSP syntax for sequence parameter sets

[0140] [Table 8]

[0141] RBSP syntax for picture parameter sets

[0142] [Table 9]

[0143] Slice header syntax

[0144] [Table 10]

[0145] Syntax of the reference picture list structure

[0146] [Table 11]

[0147] The semantics of the NAL unit header will be examined.

[0148] Semantics of RBSP for sequence parameter sets

[0149] log2_max_pic_order_cnt_lsb_minus4 specifies the value of the variable MaxPicOrderCntLsb, which is used in the decoding process for picture order count, as follows: MaxPicOrderCntLsb = 2( log2_max_pic_order_cnt_lsb_minus4 + 4 ). The value of log2_max_pic_order_cnt_lsb_minus4 is in the range of 0 to 12, including 0 and 12. The value of sps_max_dec_pic_buffering_minus1 plus 1 specifies the maximum required size of the decoded picture buffer for CVS in units of picture storage buffers. The value of sps_max_dec_pic_buffering_minus1 is in the range of 0 to MaxDpbSize - 1, including 0 and MaxDpbSize - 1, where MaxDpbSize is specified elsewhere. num_ref_pic_lists_in_sps specifies the number of ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structures included in the SPS. The value of num_ref_pic_lists_in_sps is in the range of 0 to 128, including 0 and 128. The decoder should allocate memory for a total of num_short_term_ref_pic_sets + 2 ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structures, as there may be two ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structures that are directly signaled within the slice header of the current picture. A long_term_ref_pics_flag equal to 0 specifies that LTRP is not used for interpretation of any coded pictures in the CVS. A long_term_ref_pics_flag equal to 1 indicates that LTRP may be used for interpretation of one or more coded pictures in CVS.`additional_lt_poc_lsb` specifies the value of the variable `MaxLtPicOrderCntLsb`, which is used in the decoding process for the reference picture list, as follows: `MaxLtPicOrderCntLsb = 2( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_lt_poc_lsb )`. The value of `additional_lt_poc_lsb` is in the range of 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4. If it does not exist, the value of `additional_lt_poc_lsb` is presumed to be equal to 0.

[0150] The semantics of the RBSP for the picture parameter set will be examined.

[0151] Slice header semantics

[0152] When present, the values ​​of the slice header syntax elements slice_pic_parameter_set_id and slice_pic_order_cnt_lsb are the same for all slice headers of the coded picture. slice_type specifies the coding type of the slice according to Table 7-3 (Table 12).

[0153] [Table 12]

[0154] When nal_unit_type is equal to IRAP_NUT, i.e., the picture is an IRAP picture, slice_type is equal to 2. ... slice_pic_order_cnt_lsb specifies the modulo MaxPicOrderCntLsb of the picture order count for the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4 + 4 bits. The value of slice_pic_order_cnt_lsb is in the range from 0 to MaxPicOrderCntLsb - 1, including 0 and MaxPicOrderCntLsb - 1. When slice_pic_order_cnt_lsb does not exist, it is inferred that slice_pic_order_cnt_lsb is equal to 0. A ref_pic_list_sps_flag[i] equal to 1 specifies that the current picture's reference picture list i is derived based on one of the ref_pic_list_struct(rplsIdx, ltrpFlag) in the active SPS. A ref_pic_list_sps_flag[i] equal to 0 specifies that the current picture's reference picture list i is derived based on the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure directly contained in the slice header of the current picture. When num_ref_pic_lists_in_sps is equal to 0, the value of ref_pic_list_sps_flag[i] is equal to 0. ref_pic_list_idx[i] specifies an index to a list of ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structures contained in the active SPS, which is used to derive the reference picture list i of the current picture. The syntax element ref_pic_list_idx[i] is represented by Ceil( Log2(num_ref_pic_lists_in_sps) ) bits.When it does not exist, the value of ref_pic_list_idx[i] is presumed to be equal to 0. The value of ref_pic_list_idx[i] is in the range from 0 to num_ref_pic_lists_in_sps - 1, including 0 and num_ref_pic_lists_in_sps - 1. A num_ref_idx_active_override_flag equal to 1 specifies that the syntax element num_ref_idx_active_minus1[0] exists for P and B slices, and that the syntax element num_ref_idx_active_minus1[1] exists for B slices. A num_ref_idx_active_override_flag equal to 0 specifies that the syntax elements num_ref_idx_active_minus1[0] and num_ref_idx_active_minus1[1] do not exist.

[0155] num_ref_idx_active_minus1[i], when present, specifies the value of the variable NumRefIdxActive[i] as follows: NumRefIdxActive[i] = num_ref_idx_active_minus1[i] + 1. The value of num_ref_idx_active_minus1[i] is in the range of 0 to 14, including 0 and 14. The value of NumRefIdxActive[i] - 1 specifies the largest reference index on reference picture list i that may be used to decode the slice. When the value of NumRefIdxActive[i] is equal to 0, the reference index on reference picture list i may not be used to decode the slice. For i equal to 0 or 1, if the current slice is a B slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[i] is presumed to be equal to num_ref_idx_default_active_minus1[i] + 1. When the current slice is a P slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[0] is presumed to be equal to num_ref_idx_default_active_minus1[0] + 1. When the current slice is a P slice, NumRefIdxActive[1] is presumed to be equal to 0. When the current slice is an I slice, both NumRefIdxActive[0] and NumRefIdxActive[1] are presumed to be equal to 0.

[0156] Alternatively, for i equal to 0 or 1, the following applies after the above: rplsIdx1 is set to be equal to ref_pic_list_sps_flag[i] ? ref_pic_list_idx[i] : num_ref_pic_lists_in_sps[i], and numRpEntries[i] is equal to num_strp_entries[i][rplsIdx1] + num_ltrp_entries[i][rplsIdx1]. When NumRefIdxActive[i] is greater than numRpEntries[i], the value of NumRefIdxActive[i] is set to be equal to numRpEntries[i].

[0157] Semantics of the reference picture list structure

[0158] The ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure can reside either within an SPS or within a slice header. Depending on whether the syntax structure is contained within a slice header or within an SPS, the following applies: If it resides within a slice header, the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure specifies a reference picture list for the current picture (the picture containing the slice). If it does not reside within an SPS, the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure specifies a candidate reference picture list, and the term "current picture" in the semantics explicitly stated for the remainder of this section refers to each picture in a CVS that has 1) one or more slices containing ref_pic_list_idx[i] equal to an index to a list of ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structures contained within an SPS, and 2) the SPS as the active SPS. num_strp_entries[rplsIdx] specifies the number of STRP entries in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure. num_ltrp_entries[rplsIdx] specifies the number of LTRP entries in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure. If none exist, the value of num_ltrp_entries[rplsIdx] is presumed to be equal to 0.

[0159] The variable NumEntriesInList[rplsIdx] is derived as follows: NumEntriesInList[rplsIdx] = num_strp_entries[rplsIdx] + num_ltrp_entries[rplsIdx]. The value of NumEntriesInList[rplsIdx] is in the range from 0 to sps_max_dec_pic_buffering_minus1, including 0 and sps_max_dec_pic_buffering_minus1. lt_ref_pic_flag[rplsIdx][i] equal to 1 specifies that the i-th entry of the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure is an LTRP entry. A value of lt_ref_pic_flag[rplsIdx][i] equal to 0 specifies that the i-th entry of the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure is a STRP entry. If it does not exist, the value of lt_ref_pic_flag[rplsIdx][i] is presumed to be equal to 0. A bitstream compliance requirement is that the sum of lt_ref_pic_flag[rplsIdx][i] for all values ​​of i within the range from 0 to NumEntriesInList[rplsIdx] - 1, including 0 and NumEntriesInList[rplsIdx] - 1, is equal to num_ltrp_entries[rplsIdx].delta_poc_st[rplsIdx][i] specifies the difference between the picture sequence count of the current picture and the picture sequence count of the picture referenced by the i-th entry, when the i-th entry is the first STRP entry in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure, or when the i-th entry is a STRP entry in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure but is not the first STRP entry, it specifies the difference between the picture sequence count of the picture referenced by the i-th entry and the picture sequence count of the picture referenced by the previous STRP entry in the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure. The value of delta_poc_st[rplsIdx][i] is in the range of 0 to 215 - 1, including 0 and 215 - 1. poc_lsb_lt[rplsIdx][i] specifies the modulo MaxLtPicOrderCntLsb value of the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(rplsIdx, ltrpFlag) syntax structure. The length of the poc_lsb_lt[rplsIdx][i] syntax element is Log2(MaxLtPicOrderCntLsb) bits.

[0160] The overall decoding process, as expressed as part of the detailed description of the first embodiment of this disclosure, is applicable. The NAL unit decoding process is described. The NAL unit decoding process, as expressed as part of the detailed description of the first embodiment of this disclosure, is applicable.

[0161] A slice decoding process is provided.

[0162] Decoding process related to picture sequence count

[0163] A decoding process relating to picture sequence counts, as expressed as part of the detailed description of the first embodiment of this disclosure, is applied.

[0164] Decryption process for building the reference picture list

[0165] This process is called at the beginning of the decoding process for each slice of a non-IRAP picture. The reference picture is addressed by a reference index, which is an index to the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (i.e., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, both reference picture list 0 and reference picture list 1 (i.e., RefPicList[1]) are used in decoding the slice data. At the beginning of the decoding process for each slice of a non-IRAP picture, the reference picture lists RefPicList[0] and RefPicList[1] are derived. The reference picture lists are used in marking the reference picture or in decoding the slice data. For I slices of non-IRAP pictures that are not the first slice of a picture, RefPicList[0] and RefPicList[1] may be derived for the purpose of checking bitstream compliance, but their derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. For P slices that are not the first slice of a picture, RefPicList[1] may be derived for the purpose of checking bitstream compliance, but its derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order.

[0166] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { if( ref_pic_list_sps_flag[i] ) RplsIdx[i] = ref_pic_list_idx[i] else RplsIdx[i] = num_ref_pic_lists_in_sps for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[RplsIdx[i]]; j++ ) { if( !lt_ref_pic_flag[RplsIdx[i]][j] ) { RefPicPocList[i][j] = pocBase - delta_poc_st[RplsIdx[i]][j] if (There exists a reference picture picA in the DPB where PicOrderCntVal is equal to RefPicPocList[i][j]) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" pocBase = RefPicPocList[i][j] else { if (PicOrderCntVal & ( MaxLtPicOrderCntLsb - 1 ) is equal to poc_lsb_lt[RplsIdx[i]][j] and there exists a reference picA in the DPB) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" } } }

[0167] For each i equal to 0 or 1, the following applies: The first NumRefIdxActive[i] entries in RefPicList[i] are called the active entries of RefPicList[i], and the other entries in RefPicList[i] are called the inactive entries of RefPicList[i]. For j in the range from 0 to NumEntriesInList[RplsIdx[i]] - 1, including 0 and NumEntriesInList[RplsIdx[i]] - 1, each entry in RefPicList[i][j] is called a STRP entry if lt_ref_pic_flag[RplsIdx[i]][j] is equal to 0, and an LTRP entry otherwise. A particular picture can be referenced by both an entry in RefPicList[0] and an entry in RefPicList[1]. A particular picture may be referenced by two or more entries in RefPicList[0] or by two or more entries in RefPicList[1]. Active entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that may be used for interpretation of the current picture and one or more pictures that follow the current picture in the decoding order. Inactive entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that are not used for interpretation of the current picture but may be used for interpretation of one or more pictures that follow the current picture in the decoding order. There may be one or more entries in RefPicList[0] or RefPicList[1] that are equal to "no reference picture" because the corresponding picture does not exist in the DPB. Each inactive entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture" should be ignored.For each active entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture", an unintended loss of picture should be inferred.

[0168] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0169] A decoding process for marking the reference picture will be considered.

[0170] This process is called once per picture, after the decoding process for decoding the slice header and building the reference picture list for the slice, but before decoding the slice data. This process may result in one or more reference pictures in the DPB being marked as "Not for Reference" or "Used for Long-Term Reference". A decoded picture in the DPB can be marked as "Not for Reference", "Used for Short-Term Reference", or "Used for Long-Term Reference", however, at any given moment during the operation of the decoding process, it can be marked as just one of these three. Assigning one of these markings to a picture implicitly removes another of these markings, where applicable. When we say a picture is marked as "Used for Reference", this means collectively that the picture is marked as either "Used for Short-Term Reference" or "Used for Long-Term Reference" (but not both). When the current picture is an IRAP picture, all reference pictures (if any) currently in the DPB are marked as "Not for Reference". STRPs are identified by their PicOrderCntVal values. LTRPs are identified by the Log2(MaxLtPicOrderCntLsb) LSB of their PicOrderCntVal values.

[0171] The following applies: For each LTRP entry in RefPicList[0] or RefPicList[1], if the referenced picture is a STRP, the picture is marked as “Used for long-term reference.” Each referenced picture in the DPB that is not referenced by any entry in RefPicList[0] or RefPicList[1] is marked as “Not used for reference.”

[0172] Figure 5 shows an embodiment of method 500 for decoding a coded video bitstream, which is performed by a video decoder (e.g., video decoder 30). Method 500 may be performed after the decoded bitstream has been received directly or indirectly from a video encoder (e.g., video encoder 20). Method 500 may be performed to improve the decoding process (e.g., to make the decoding process more efficient or faster than the normal decoding process). Thus, as a practical matter, the performance of the codec can be improved, which leads to a better user experience.

[0173] In block 502, the parameter set shown in the coded video bitstream is parsed. In an embodiment, the parameter set includes a set of syntax elements that include a set of reference picturelist structures.

[0174] In block 504, the slice header of the current slice shown in the coded video bitstream is parsed. In an embodiment, the slice header includes an index of a reference picturelist structure from a set of reference picturelist structures in the parameter set.

[0175] In block 506, the reference picture list for the current slice is derived. In an embodiment, the reference picture list is derived based on a set of syntax elements in the parameter set and an index in the reference picture list structure. In an embodiment, the order of entries in the reference picture list structure is the same as the order of the corresponding reference pictures in the reference picture list. In an embodiment, the order is from zero to the indicated value. In an embodiment, the indicated value is from zero to the value indicated by sps_max_dec_pic_buffering_minus1.

[0176] In block 508, at least one reconstructed block of the current slice is obtained. In an embodiment, at least one reconstructed block of the current slice is reconstructed based on a reference picture list. After the reconstruction process, the video decoder can output a video or image. In an embodiment, the video or image may be displayed on the display of an electronic device (e.g., a smartphone, tablet, laptop, etc.).

[0177] In an embodiment, the reference picture list is a specified RefPictList[0] or RefPictList[1]. In an embodiment, the reference picture list includes a list of reference pictures used for interpretation. In an embodiment, the interpretation is for P-slice or B-slice. In an embodiment, a set of syntax elements from the parameter set is placed in the raw byte sequence payload (RBSP) of the network abstraction layer (NAL) unit.

[0178] Outlines of alternative embodiments based on the first and second embodiments are given.

[0179] This section provides a brief overview of other alternative embodiments of the Disclosure. The overview relates to the description of the first embodiment. However, the basic concepts of the Disclosure relating to the following alternative embodiments are also applicable to familiar implementations of the Disclosure relating to the second embodiment. Such implementations are in the same spirit as the way the embodiments are implemented with familiarity with the first embodiment.

[0180] Semantics of the differential POC entry for short-term reference picture

[0181] In one alternative embodiment of this disclosure, the semantic of a syntax element specifying the difference POC of the i-th entry in a reference picture list structure ref_pic_list_struct() is defined as the difference in POC between the current picture and the reference picture associated with the i-th entry. Some of the descriptions used herein relate to current draft standards (e.g., working draft of VVC) in which only the differences are shown or described. Deleted text is indicated by strikethrough, and any added text is highlighted.

[0182] The semantics of delta_poc_st[listIdx][rplsIdx][i] are defined as follows: delta_poc_st[listIdx][rplsIdx][i] specifies the difference between the picture order count value of the current picture and the picture order count value of the picture referenced by the i-th entry. The value of delta_poc_st[listIdx][rplsIdx][i] is in the range of -215 to 215 - 1, including -215 and 215 - 1.

[0183] The equation for the construction process of the reference picture list needs to be updated. The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0184]

number

[0185] Signaling of entries for long-term reference pictures

[0186] In one alternative embodiment of the present disclosure, entries for long-term reference pictures are not signaled within the same reference picture list structure as entries for short-term reference pictures. Entries for long-term reference pictures are signaled within a separate structure, and for each entry in the structure, there exists a syntax element that describes the intended location of the long-term reference picture for the derivation of the corresponding entry index in the final reference picture list.

[0187] RBSP syntax for sequence parameter sets

[0188] [Table 13]

[0189] Slice header syntax

[0190] [Table 14]

[0191] Syntax of the reference picture list structure

[0192] [Table 15]

[0193] Syntax of a long-term reference picturelist structure

[0194] [Table 16]

[0195] Semantics of RBSP for sequence parameter sets

[0196] num_ref_pic_lists_lt_in_sps specifies the number of ref_pic_list_lt_struct(ltRplsIdx) syntax structures included in the SPS. The value of num_ref_pic_lists_lt_in_sps is in the range of 0 to 64, including 0 and 64. If none exist, the value of num_ref_pic_lists_lt_in_sps is presumed to be equal to 0.

[0197] Slice header semantics

[0198] ref_pic_list_lt_idx[i] specifies an index to a list of ref_pic_list_lt_struct(ltRplsIdx) syntax structures contained in the active SPS used for deriving the reference picture list i of the current picture. The syntax element ref_pic_list_lt_idx[i] is represented by Ceil(Log2(num_ref_pic_lists_lt_in_sps)) bits. The value of ref_pic_list_lt_idx is in the range from 0 to num_ref_pic_lists_lt_in_sps - 1, including 0 and num_ref_pic_lists_lt_in_sps - 1.

[0199] Semantics of the reference picture list structure

[0200] The ref_pic_list_struct(listIdx, rplsIdx) syntax structure can exist either within the SPS or within the slice header. Depending on whether the syntax structure is in the slice header or the SPS, the following applies: If it is in the slice header, the ref_pic_list_struct(listIdx, rplsIdx) syntax structure specifies the listIdx of the short-term reference picture list for the current picture (the picture containing the slice). If not (present in the SPS), the ref_pic_list_struct(listIdx, rplsIdx) syntax structure specifies a candidate for listIdx of the short-term reference picture list, and the term “current picture” in the semantics explicitly stated for the remainder of this section refers to each picture in a CVS that has 1) one or more slices containing ref_pic_list_idx[listIdx] equal to an index to a list of ref_pic_list_struct(listIdx, rplsIdx) syntax structures present in the SPS, and 2) the SPS as the active SPS. num_strp_entries[listIdx][rplsIdx] specifies the number of STRP entries in the ref_pic_list_struct(listIdx, rplsIdx) syntax structure.

[0201]

number

[0202]

number

[0203]

number

[0204]

number

[0205]

number

[0206]

number

[0207] delta_poc_st[listIdx][rplsIdx][i] specifies the difference between the picture sequence count of the current picture and the picture sequence count of the picture referenced by the i-th entry, when the i-th entry is the first STRP entry in the ref_pic_list_struct(listIdx, rplsIdx) syntax structure, or when the i-th entry is a STRP entry in the ref_pic_list_struct(listIdx, rplsIdx) syntax structure but is not the first STRP entry, it specifies the difference between the picture sequence count of the picture referenced by the i-th entry and the picture sequence count of the picture referenced by the previous STRP entry in the ref_pic_list_struct(listIdx, rplsIdx) syntax structure. The value of delta_poc_st[listIdx][rplsIdx][i] is in the range of -215 to 215 - 1, including -215 and 215 - 1.

[0208]

number

[0209] Semantics of the Long-Term Reference Picture List Structure

[0210] The ref_pic_list_lt_struct(ltRplsIdx) syntax structure can reside either within an SPS or within a slice header. Depending on whether the syntax structure is contained within a slice header or within an SPS, the following applies: If it resides within a slice header, the ref_pic_list_lt_struct(ltRplsIdx) syntax structure specifies the long-term reference picture list for the current picture (the picture containing the slice). If it does not reside within an SPS, the ref_pic_list_struct(listIdx, rplsIdx) syntax structure specifies a candidate for the long-term reference picture list, and the term "current picture" in the semantics explicitly stated for the remainder of this section refers to each picture in a CVS that has 1) one or more slices containing ref_pic_list_lt_idx[i] equal to an index to a list of ref_pic_list_lt_struct(ltRplsIdx) syntax structures contained within an SPS, and 2) the SPS as the active SPS. num_ltrp_entries[ltRplsIdx] specifies the number of LTRP entries in the ref_pic_list_lt_struct(ltRplsIdx) syntax structure. poc_lsb_lt[rplsIdx][i] specifies the modulo MaxLtPicOrderCntLsb value of the picture order count of the picture referenced by the i-th entry in the ref_pic_list_lt_struct(rplsIdx) syntax structure. The length of the poc_lsb_lt[rplsIdx][i] syntax element is Log2(MaxLtPicOrderCntLsb) bits. lt_pos_idx[rplsIdx][i] specifies the index of the i-th entry in the ref_pic_list_lt_struct(rplsIdx) syntax structure in the referenced picture list after the referenced picture list has been constructed. The length of the syntax element lt_pos_idx[rplsIdx][i] is Log2(sps_max_dec_pic_buffering_minus1 + 1) bits.When num_ltrp_entries[ltRplsIdx] is greater than 1, poc_lsb_lt[rplsIdx][i] and lt_pos_idx[rplsIdx][i] are in descending order of the value of lt_pos_idx[rplsIdx][i].

[0211] The decryption process will be explained.

[0212] Decryption process for building the reference picture list

[0213] This process is called at the beginning of the decoding process for each slice of a non-IRAP picture. The reference picture is addressed by a reference index, which is an index to the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (i.e., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, both reference picture list 0 and reference picture list 1 (i.e., RefPicList[1]) are used in decoding the slice data. At the beginning of the decoding process for each slice of a non-IRAP picture, the reference picture lists RefPicList[0] and RefPicList[1] are derived. The reference picture lists are used in marking the reference picture or in decoding the slice data. For I-slices of non-IRAP pictures that are not the first slice of a picture, RefPicList[0] and RefPicList[1] may be derived for the purpose of checking bitstream compliance, but their derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. For P-slices that are not the first slice of a picture, RefPicList[1] may be derived for the purpose of checking bitstream compliance, but its derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0214]

number

[0215] For each i equal to 0 or 1, the following applies: The first NumRefIdxActive[i] entries in RefPicList[i] are called the active entries of RefPicList[i], and the other entries in RefPicList[i] are called the inactive entries of RefPicList[i]. For j in the range from 0 to NumEntriesInList[i][RplsIdx[i]] - 1, including 0 and NumEntriesInList[i][RplsIdx[i]] - 1, each entry in RefPicList[i][j] is called a STRP entry if lt_ref_pic_flag[i][RplsIdx[i]][j] is equal to 0, and is called an LTRP entry otherwise. A particular picture can be referenced by both an entry in RefPicList[0] and an entry in RefPicList[1]. A particular picture may be referenced by two or more entries in RefPicList[0] or by two or more entries in RefPicList[1]. Active entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that may be used for interpretation of the current picture and one or more pictures that follow the current picture in the decoding order. Inactive entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that are not used for interpretation of the current picture but may be used for interpretation of one or more pictures that follow the current picture in the decoding order. There may be one or more entries in RefPicList[0] or RefPicList[1] that are equal to "no reference picture" because the corresponding picture does not exist in the DPB. Each inactive entry in RefPicList[0] or RefPicList[0] that is equal to "no reference picture" should be ignored.For each active entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture", an unintended loss of picture should be inferred.

[0216] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, the number of entries in RefPicList[i] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0217] Signaling of the number of entries for short-term reference pictures will be considered.

[0218] In one alternative embodiment of this disclosure, the syntax element specifying the number of entries related to short-term reference pictures in the reference picture list structure ref_pic_list_struct() is defined as num_strp_entries_minus1[listIdx][rplsIdx] instead of num_strp_entries[listIdx][rplsIdx]. The change has two effects with respect to the signaling of reference picture lists. The change may save bits for signaling the number of entries related to short-term reference pictures in the reference picture list structure, since the element is coded using ue(v). The change implicitly imposes a constraint that each reference picture list contains at least one short-term reference picture. Several modifications related to the first embodiment are required to accommodate this idea.

[0219] Regarding the signaling of reference picture lists within slice headers, only the necessary reference picture lists are signaled depending on the slice type; that is, one reference picture list (i.e., reference picture list 0) is signaled for I or P slices, and two reference picture lists (i.e., both reference picture list 0 and reference picture list 1) are signaled for B slices. The syntax of the slice header is changed as follows:

[0220] [Table 17]

[0221] By applying the above changes to the slice header (i.e., reference picture list 0 for slices I or P and reference picture 0 and reference picture 1 for slice B), it prevents the scheme from running into problems when there is only one short-term reference picture for slice P. However, duplicate short-term reference pictures cannot be signaled in reference picture list 0 and reference picture list 1, and since the number of active entries in reference picture list 1 must be equal to 0, the entries in reference picture list 1 are inactive entries. The semantics of num_strp_entries_minus1[listIdx][rplsIdx] are changed as follows: The value of num_strp_entries_minus1[listIdx][rplsIdx] plus 1 specifies the number of STRP entries in the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. The variable NumEntriesInList[listIdx][rplsIdx] is derived as follows: NumRefPicEntriesInRpl[listIdx][rplsIdx] = num_strp_entries_minus1[listIdx][rplsIdx] + 1 + num_ltrp_entries[listIdx][rplsIdx]. The value of NumRefPicEntries[listIdx][rplsIdx] is in the range from 1 to sps_max_dec_pic_buffering_minus1, including 1 and sps_max_dec_pic_buffering_minus1.

[0222] Allow the current picture to be included in the reference picture list.

[0223] In one alternative embodiment of this disclosure, the current picture is permitted to be included in its reference picture list. To support this feature, there are no syntax and semantic changes required in connection with their descriptions in the first and second embodiments. However, the bitstream compliance constraints described in the decoding process for constructing the reference picture list must be modified as follows: The following constraints must apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i][RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: An inactive entry in RefPicList[0] or RefPicList[1] does not refer to the same picture as any other entry in RefPicList[0] or RefPicList[1]. A STRP entry in RefPicList[0] or RefPicList[1] for a slice of a picture and an LTRP entry in RefPicList[0] or RefPicList[1] for the same slice or a different slice of the same picture do not refer to the same picture.

number

[0224] Use different POC LSB bits for LTRP entries in the reference picture list.

[0225] In one alternative embodiment of the present disclosure, the number of bits used to identify long-term reference pictures in the reference picture list structure may differ between reference picture list 0 and reference picture list 1. To support this feature, the following modifications are required.

[0226] [Table 18]

[0227] The value of the variable MaxLtPicOrderCntLsb[i] used in the decoding process for the listIdx of the reference picture list equal to i is specified as follows: MaxLtPicOrderCntLsb[i] = 2( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_lt_poc_lsb[i] ). The value of additional_lt_poc_lsb[i] is in the range from 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4. If it does not exist, the value of additional_lt_poc_lsb[i] is presumed to be equal to 0.

[0228] poc_lsb_lt[listIdx][rplsIdx][i] specifies the modulo MaxLtPicOrderCntLsb[listIdx] value of the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(listIdx, rplsIdx, ltrpFlag) syntax structure. The length of the poc_lsb_lt[listIdx][rplsIdx][i] syntax element is Log2(MaxLtPicOrderCntLsb[listIdx]) bits.

[0229] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { if( ref_pic_list_sps_flag[i] ) RplsIdx[i] = ref_pic_list_idx[i] else RplsIdx[i] = num_ref_pic_lists_in_sps[i] for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[i][RplsIdx[i]]; j++ ) { if( !lt_ref_pic_flag[i][RplsIdx[i]][j] ) { RefPicPocList[i][j] = pocBase - delta_poc_st[i][RplsIdx[i]][j] if( there exists a reference picture picA in the DPB where PicOrderCntVal is equal to RefPicPocList[i][j] ) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture"<00009​​​​​​​​​​​​​​​​​​​​​​​​In one alternative embodiment of this disclosure, instead of using two flags to indicate whether reference picturelist 0 and reference picturelist 1 are derived based on the ref_pic_list_struct() syntax structure in the active SPS, one flag is used for both reference picturelists. Such an alternative constrains that either both reference picturelists are derived based on the ref_pic_list_struct() in the active SPS, or those reference picturelists are derived based on the ref_pic_list_struct() syntax structure that is directly included in the slice header of the current picture. To support this feature, the following modifications are required.

[0232] [Table 19]

[0233]

number

[0234] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0235]

number

[0236] Signaling of the most significant bit (MSB) of the differential POC for entries in long-term reference pictures.

[0237] In one alternative embodiment of the present disclosure, instead of using an additional bit to represent the POC LSB of the long-term reference picture entry in ref_pic_list_struct( ), the POC MSB cycle is signaled to distinguish long-term reference pictures. When signaled, the POC MSB cycle information is signaled for each entry in ref_pic_list_struct( ) that refers to a long-term reference picture. The ref_pic_list_struct( ) syntax structure is not signaled in the SPS and is signaled only in the slice header. To support this feature, the following changes are required.

[0238]

Table 20

[0239]

Table 21

[0240]

Table 22

[0241] <00,00969

Number

[0242]

Number

[0243]

Number

[0244] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows.

[0245]

number

[0246] Alternatively, the semantics of delta_poc_msb_cycle_lt[listIdx][i] can be expressed as a difference of differences, so that the construction of the reference picture list can be updated as follows: The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0247]

number

[0248] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i][RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0249] Each STRP is identified by its PicOrderCntVal value. For each LTRP, if it is referenced by an entry in RefPicList[0] or RefPicList[1] where delta_poc_msb_present_flag[listIdx][i] is equal to 1, then it is identified by its PicOrderCntVal value; otherwise, it is identified by the Log2(MaxPicOrderCntLsb) LSB of its PicOrderCntVal value.

[0250] Alternative 1 to signaling differential POC MSB for entries in long-term reference pictures

[0251] This embodiment provides an alternative to the embodiment described in the previous section. Similar to the idea in the previous section, instead of using an additional bit to represent the POC LSB of the long-term reference picture in ref_pic_list_struct(), the POC MSB cycle is signaled to distinguish the long-term reference picture. However, in this alternative, when signaled, the POC MSB cycle information is not signaled in ref_pic_list_struct(), and instead, when the POC MSB cycle information is needed, the POC MSB cycle information is signaled in the slice header. The ref_pic_list_struct() syntax structure may be signaled in the SPS and in the slice header.

[0252] [Table 23]

[0253] [Table 24A] [Table 24B]

[0254] A delta_poc_msb_present_flag[i][j] equal to 1 indicates that delta_poc_msb_cycle_lt[i][j] exists. A delta_poc_msb_present_flag[i][j] equal to 0 indicates that delta_poc_msb_cycle_lt[i][j] does not exist. If NumLtrpEntries[i] is greater than 0, and there are two or more reference pictures in the DPB where, for the j-th LTRP entry of the ref_pic_list_struct(i, rplsIdx, 1) syntax structure, the modulo MaxPicOrderCntLsb of PicOrderCntVal is equal to poc_lsb_lt[i][rplsIdx][jj] when the slice header is decoded, and jj is the entry index of the entry in the ref_pic_list_struct(i, rplsIdx, 1) syntax structure that is the j-th LTRP entry of the ref_pic_list_struct(i, rplsIdx, 1) syntax structure, then delta_poc_msb_present_flag[i][j] is equal to 1. If not, the value of delta_poc_msb_cycle_lt[i][j] is presumed to be equal to 0. delta_poc_msb_cycle_lt[i][j] is used to determine the most significant bit of the picture sequence count value for the j-th LTRP entry in the ref_pic_list_struct(i, rplsIdx, 1) syntax structure. When delta_poc_msb_cycle_lt[i][j] does not exist, it is presumed to be equal to 0.

[0255] [Table 25A] [Table 25B]

[0256] A delta_poc_msb_present_flag[i][j] equal to 1 indicates that delta_poc_msb_cycle_lt[i][j] exists. A delta_poc_msb_present_flag[i][j] equal to 0 indicates that delta_poc_msb_cycle_lt[i][j] does not exist. If NumLtrpEntries[i] is greater than 0 and there are two or more reference pictures in the DPB where the modulo MaxPicOrderCntLsb of PicOrderCntVal is equal to poc_lsb_lt[i][rplsIdx][j] when the slice header is decoded, then delta_poc_msb_present_flag[i][j] is equal to 1. If it does not exist, the value of delta_poc_msb_cycle_lt[i][j] is presumed to be equal to 0. delta_poc_msb_cycle_lt[i][j] is used to determine the most significant bit of the picture order count value for the j-th entry in the ref_pic_list_struct(i, rplsIdx, 1) syntax structure. When delta_poc_msb_cycle_lt[i][j] does not exist, it is presumed to be equal to 0.

number

[0257] Changes to the decoding process regarding picture sequence counting.

number

[0258] Regarding slice header design 1, the reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0259]

number

[0260] Alternatively, with respect to slice header design 1, the semantics of delta_poc_msb_cycle_lt[listIdx][i] can be expressed as a difference of differences, so that the construction of the reference picture list can be updated as follows: The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0261]

number

[0262] Regarding the design of the slice header 2, the reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0263]

number

[0264] Alternatively, with respect to slice header design 2, the semantics of delta_poc_msb_cycle_lt[listIdx][i] can be expressed as a difference of differences, so that the construction of the reference picture list can be updated as follows: The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows:

[0265]

number

[0266] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i][RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0267] Each STRP is identified by its PicOrderCntVal value. For each LTRP, if it is referenced by an entry in RefPicList[0] or RefPicList[1] where delta_poc_msb_present_flag[i][j] is equal to 1, then it is identified by its PicOrderCntVal value; otherwise, it is identified by the Log2(MaxPicOrderCntLsb) LSB of its PicOrderCntVal value.

[0268] Alternative 2 to signaling differential POC MSB for long-term reference picture entries

[0269] In one alternative embodiment of the present disclosure, the disclosure described in the first or second embodiment may be combined with the embodiments referred to above as “Differential POC MSB Signaling for Long-Term Reference Picture Entries” and “Alternative 1 for Differential POC MSB Signaling for Long-Term Reference Picture Entries,” respectively. The aspects of the present disclosure to be combined are the signaling of additional_lt_poc_lsb (i.e., from the first or second embodiment) and POC MSB cycle information (i.e., from the embodiments referred to above as “Differential POC MSB Signaling for Long-Term Reference Picture Entries” and “Alternative 1 for Differential POC MSB Signaling for Long-Term Reference Picture Entries”). An example of how the combination of the first embodiment and the embodiment referred to above as “Alternative 1 for Differential POC MSB Signaling for Long-Term Reference Picture Entries” may be made is shown below.

[0270] [Table 26A] [Table 26B]

[0271] A delta_poc_msb_present_flag[i][j] equal to 1 indicates that delta_poc_msb_cycle_lt[i][j] exists. A delta_poc_msb_present_flag[i][i] equal to 0 indicates that delta_poc_msb_cycle_lt[i][j] does not exist. If NumLtrpEntries[i] is greater than 0, and there are two or more reference pictures in the DPB where, for the j-th LTRP entry of the ref_pic_list_struct(i, rplsIdx, 1) syntax structure, the modulo MaxPicOrderCntLsb of PicOrderCntVal is equal to poc_lsb_lt[i][rplsIdx][jj] when the slice header is decoded, and jj is the entry index of the entry in the ref_pic_list_struct(i, rplsIdx, 1) syntax structure that is the j-th LTRP entry of the ref_pic_list_struct(i, rplsIdx, 1) syntax structure, then delta_poc_msb_present_flag[i][j] is equal to 1. If not, the value of delta_poc_msb_cycle_lt[i][j] is presumed to be equal to 0. delta_poc_msb_cycle_lt[i][j] is used to determine the most significant bit of the picture sequence count value for the j-th LTRP entry in the ref_pic_list_struct(i, rplsIdx, 1) syntax structure. When delta_poc_msb_cycle_lt[i][j] does not exist, it is presumed to be equal to 0.

[0272] Changes to the decoding process regarding picture sequence counting.

number

[0273] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { if( ref_pic_list_sps_flag[i] ) RplsIdx[i] = ref_pic_list_idx[i] else RplsIdx[i] = num_ref_pic_lists_in_sps[i] msbCycleIdx = 0 for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[i][RplsIdx[i]]; j++ ) { if( !lt_ref_pic_flag[i][RplsIdx[i]][j] ) { RefPicPocList[i][j] = pocBase - delta_poc_st[i][RplsIdx[i]][j] if (There exists a reference picture picA in the DPB where PicOrderCntVal is equal to RefPicPocList[i][j]) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" pocBase = RefPicPocList[i][j] else { if (delta_poc_msb_cycle_lt[i][msbCycleIdx] is equal to 0 && PicOrderCntVal & ( MaxLtPicOrderCntLsb - 1 ) is equal to poc_lsb_lt[i][RplsIdx[i]][j] and there exists a reference picture picA in the DPB) RefPicList[i][j] = picA else if ( delta_poc_msb_cycle_lt[i][msbCycleIdx] is equal to 1 && there exists a reference picture picA in the DPB where PicOrderCntVal is equal to (MaxLtPicOrderCntLsb * delta_poc_msb_cycle_lt[i][msbCycleIdx] ) + poc_lsb_lt[i][RplsIdx[i]][j] ) ) { RefPicList[i][j] = picA msbCycleIdx++ else RefPicList[i][j] = "no reference picture" } } }

[0274] Alternatively, the semantics of delta_poc_msb_cycle_lt[listIdx][i] can be expressed as a difference of differences, so that the construction of the reference picture list can be updated as follows: The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { if( ref_pic_list_sps_flag[i] ) RplsIdx[i] = ref_pic_list_idx[i] else RplsIdx[i] = num_ref_pic_lists_in_sps[i] prevMsbCycle = 0 msbCycleIdx = 0 for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[i][RplsIdx[i]]; j++ ) { if( !lt_ref_pic_flag[i][RplsIdx[i]][j] ) { RefPicPocList[i][j] = pocBase - delta_poc_st[i][RplsIdx[i]][j] if (There exists a reference picture picA in the DPB where PicOrderCntVal is equal to RefPicPocList[i][j]) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" pocBase = RefPicPocList[i][j] else { if (delta_poc_msb_cycle_lt[i][msbCycleIdx] is equal to 0 && PicOrderCntVal & ( MaxLtPicOrderCntLsb - 1 ) is equal to poc_lsb_lt[i][RplsIdx[i]][j] and there exists a reference picture picA in the DPB) RefPicList[i][j] = picA else if ( delta_poc_msb_cycle_lt[i][msbCycleIdx] is equal to 1 && there exists a reference picture picA in the DPB where PicOrderCntVal is equal to ( MaxLtPicOrderCntLsb * ( delta_poc_msb_cycle_lt[i][msbCycleIdx] + prevMsbCycle ) + poc_lsb_lt[i][RplsIdx[i]][j] ) { RefPicList[i][j] = picA prevMsbCycle += delta_poc_msb_cycle_lt[i][msbCycleIdx] msbCycleIdx++ else RefPicList[i][j] = "no reference picture" } } }

[0275] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i][RplsIdx[i]] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0276] Each STRP is identified by its PicOrderCntVal value. For each LTRP, if it is referenced by an entry in RefPicList[0] or RefPicList[1] where delta_poc_msb_present_flag[i][j] is equal to 1, then it is identified by its PicOrderCntVal value; otherwise, it is identified by the Log2(MaxLtPicOrderCntLsb) LSB of its PicOrderCntVal value.

[0277] Always signal the list of referenced pictures within the slice header to distinguish between short-term and long-term referenced pictures.

[0278] This section describes another alternative embodiment of the present disclosure. The description is relevant to the most recent VVC WD (i.e., only the differences to the most recent VVC WD of JVET-K1001-v1 are described, but the text of the most recent VVC WD not described below remains applicable). This alternative embodiment can be summarized as follows: The reference picture list structure is signaled only within the slice header. Both short-term and long-term reference pictures are identified by the POC LSB of their reference pictures, which may be represented by a different number of bits than the number of bits used to represent the POC LSB that is signaled within the slice header for the derivation of the POC value. Furthermore, the number of bits used to represent the POC LSB for identifying short-term and long-term reference pictures may differ.

[0279] Syntax of NAL unit headers

[0280] [Table 27]

[0281] RBSP syntax for sequence parameter sets

[0282] [Table 28]

[0283] RBSP syntax for picture parameter sets

[0284] [Table 29]

[0285] Slice header syntax

[0286] [Table 30]

[0287] Syntax of the reference picture list structure

[0288] [Table 31]

[0289] NAL Unit Header Semantics

[0290] `forbidden_zero_bit` is equal to 0. `nal_unit_type` specifies the type of RBSP data structure included in the NAL unit.

[0291] [Table 32]

[0292] The value obtained by subtracting 1 from nuh_temporal_id_plus1 specifies the time identifier for the NAL unit. The value of nuh_temporal_id_plus1 is not equal to 0. The variable TemporalId is specified as follows: TemporalId = nuh_temporal_id_plus1 - 1.

[0293] When nal_unit_type is equal to IRAP_NUT, the coded slice belongs to an IRAP picture, and its TemporalId is equal to 0. The value of TemporalId is the same for all VCL NAL units in an access unit. The value of TemporalId for a coded picture or access unit is the value of TemporalId for the VCL NAL unit of the coded picture or access unit. The value of TemporalId for non-VCL NAL units is constrained as follows: If nal_unit_type is equal to SPS_NUT, then TemporalId is equal to 0, and the TemporalId of an access unit containing a NAL unit is equal to 0. Otherwise, if nal_unit_type is equal to EOS_NUT or EOB_NUT, then TemporalId is equal to 0. Otherwise, TemporalId is greater than or equal to the TemporalId of an access unit containing a NAL unit. When a NAL unit is a non-VCL NAL unit, the value of TemporalId is equal to the minimum of the TemporalId values ​​of all access units to which the non-VCL NAL unit belongs. When nal_unit_type is equal to PPS_NUT, the TemporalId may be greater than or equal to the TemporalId of the containing access unit, since all Picture Parameter Sets (PPS) may be included at the beginning of the bitstream and the first coded picture has a TemporalId equal to 0. When nal_unit_type is equal to PREFIX_SEI_NUT or SUFFIX_SEI_NUT, the TemporalId may be greater than or equal to the TemporalId of the containing access unit, since the SEI NAL unit may contain information that applies to a subset of the bitstream containing access units whose TemporalId value is greater than the TemporalId of the access unit containing the Supplementary Augmentation Information (SEI) NAL unit. nuh_reserved_zero_7bits is equal to '0000000'.Other values ​​for nuh_reserved_zero_7bits may be defined in the future by ITU_T | ISO / IEC. The decoder ignores (i.e., removes and discards) NAL units with nuh_reserved_zero_7bits values ​​that are not equal to '0000000'.

[0294] Semantics of RBSP for sequence parameter sets

[0295] log2_max_pic_order_cnt_lsb_minus4 specifies the value of the variable MaxPicOrderCntLsb, which is used in the decoding process for picture order count, as follows: MaxPicOrderCntLsb = 2 ( log2_max_pic_order_cnt_lsb_minus4 + 4 )

[0296] The value of log2_max_pic_order_cnt_lsb_minus4 is in the range of 0 to 12, including 0 and 12. The value of sps_max_dec_pic_buffering_minus1 plus 1 specifies the maximum required size of the decrypted picture buffer for CVS in units of picture storage buffers. The value of sps_max_dec_pic_buffering_minus1 is in the range of 0 to MaxDpbSize - 1, including 0 and MaxDpbSize - 1, where MaxDpbSize is specified elsewhere. additional_st_poc_lsb specifies the value of the variable MaxStPicOrderCntLsb used in the decryption process for the reference picture list as follows: MaxStPicOrderCntLsb = 2 ( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_st_poc_lsb )

[0297] The value of additional_st_poc_lsb is in the range of 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4. A long_term_ref_pics_flag equal to 0 specifies that LTRP is not used for interpretation of any coded pictures in CVS. A long_term_ref_pics_flag equal to 1 specifies that LTRP may be used for interpretation of one or more coded pictures in CVS. additional_lt_poc_lsb specifies the value of the variable MaxLtPicOrderCntLsb used in the decoding process for the reference picture list as follows: MaxLtPicOrderCntLsb = 2 ( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_st_poc_lsb + additional_lt_poc_lsb ) The value of additional_lt_poc_lsb is within the range of 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4 - additional_st_poc_lsb, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4 - additional_st_poc_lsb. If it does not exist, the value of additional_lt_poc_lsb is presumed to be equal to 0.

[0298] RBSP semantics of picture parameter sets

[0299] The value obtained by adding 1 to num_ref_idx_default_active_minus1[i] specifies the inferred value of the variable NumRefIdxActive[0] for P or B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 0, and specifies the inferred value of NumRefIdxActive[1] for B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 1. The value of num_ref_idx_default_active_minus1[i] is in the range of 0 to 14, including 0 and 14.

[0300] Slice header semantics

[0301] When present, the values ​​of the slice header syntax elements slice_pic_parameter_set_id and slice_pic_order_cnt_lsb are the same for all slice headers of the coded picture. slice_type specifies the coding type of the slice according to Table 7-3 (Table 33).

[0302] [Table 33]

[0303] When nal_unit_type is equal to IRAP_NUT, i.e., when the picture is an IRAP picture, then slice_type is equal to 2.

[0304] `slice_pic_order_cnt_lsb` specifies the modulo MaxPicOrderCntLsb of the picture order count for the current picture. The length of the `slice_pic_order_cnt_lsb` syntax element is log2_max_pic_order_cnt_lsb_minus4 + 4 bits. The value of `slice_pic_order_cnt_lsb` is in the range from 0 to MaxPicOrderCntLsb - 1, including 0 and MaxPicOrderCntLsb - 1. When `slice_pic_order_cnt_lsb` does not exist, it is inferred to be equal to 0. A `num_ref_idx_active_override_flag` equal to 1 specifies that the syntax element `num_ref_idx_active_minus1[0]` exists for P and B slices, and the syntax element `num_ref_idx_active_minus1[1]` exists for B slices. A num_ref_idx_active_override_flag equal to 0 indicates that the syntax elements num_ref_idx_active_minus1[0] and num_ref_idx_active_minus1[1] do not exist. If num_ref_idx_active_minus1[i] exists, it specifies the value of the variable NumRefIdxActive[i] as follows: NumRefIdxActive[i] = num_ref_idx_active_minus1[i] + 1

[0305] The value of num_ref_idx_active_minus1[i] is in the range of 0 to 14, including 0 and 14. The value of NumRefIdxActive[i] - 1 specifies the largest reference index for reference picture list i that may be used to decode the slice. When the value of NumRefIdxActive[i] is equal to 0, the reference index for reference picture list i may not be used to decode the slice. For i equal to 0 or 1, if the current slice is a B slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[i] is presumed to be equal to num_ref_idx_default_active_minus1[i] + 1. If the current slice is a P slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[0] is presumed to be equal to num_ref_idx_default_active_minus1[0] + 1. When the current slice is a P slice, NumRefIdxActive[1] is presumed to be equal to 0. When the current slice is an I slice, both NumRefIdxActive[0] and NumRefIdxActive[1] are presumed to be equal to 0. Alternatively, for i equal to 0 or 1, the following applies after the above: rplsIdx1 is set to be equal to ref_pic_list_sps_flag[i] ? ref_pic_list_idx[i] : num_ref_pic_lists_in_sps[i], and numRpEntries[i] is equal to num_strp_entries[i][rplsIdx1] + num_ltrp_entries[i][rplsIdx1]. When NumRefIdxActive[i] is greater than numRpEntries[i], the value of NumRefIdxActive[i] is set to be equal to numRpEntries[i].

[0306] Semantics of the reference picture list structure

[0307] The ref_pic_list_struct(listIdx, ltrpFlag) syntax structure may exist within the slice header. If the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure exists within the slice header, it specifies the listIdx of the reference picture list for the current picture (the picture containing the slice). num_strp_entries[listIdx] specifies the number of STRP entries in the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure. num_ltrp_entries[listIdx] specifies the number of LTRP entries in the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure. If none exist, the value of num_ltrp_entries[listIdx] is presumed to be equal to 0. The variable NumEntriesInList[listIdx] is derived as follows: NumEntriesInList[listIdx] = num_strp_entries[listIdx] + num_ltrp_entries[listIdx]

[0308] The value of NumEntriesInList[listIdx] is within the range of 0 to sps_max_dec_pic_buffering_minus1, including 0 and sps_max_dec_pic_buffering_minus1. lt_ref_pic_flag[listIdx][i] equal to 1 specifies that the i-th entry in the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure is an LTRP entry. lt_ref_pic_flag[listIdx][i] equal to 0 specifies that the i-th entry in the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure is a STRP entry. When not present, the value of lt_ref_pic_flag[listIdx][i] is presumed to be equal to 0. A bitstream compliance requirement is that the sum of lt_ref_pic_flag[listIdx][i] for all values ​​of i within the range from 0 to NumEntriesInList[listIdx] - 1, including 0 and NumEntriesInList[listIdx] - 1, is equal to num_ltrp_entries[listIdx]. poc_lsb_st[listIdx][i] specifies the value of MaxStPicOrderCntLsb, modulo MaxStPicOrderCntLsb, of the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure when lt_ref_pic_flag[listIdx][i] is equal to 0. The length of the poc_lsb_st[listIdx][i] syntax element is Log2(MaxStPicOrderCntLsb) bits. poc_lsb_lt[listIdx][i] specifies the value of MaxLtPicOrderCntLsb, modulo MaxLtPicOrderCntLsb, of the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(listIdx, ltrpFlag) syntax structure, when lt_ref_pic_flag[listIdx][i] is equal to 1.The length of the syntax element poc_lsb_lt[listIdx][i] is Log2(MaxLtPicOrderCntLsb) bits.

[0309] The decryption process will be considered.

[0310] Overall decryption process

[0311] The decryption process operates as follows with respect to the current picture CurrPic: Decryption of NAL units is defined below. The process below defines the following decryption process using syntax elements above the slice header layer. Variables and functions related to the picture order count are derived. This should only be called for the first slice of the picture. At the beginning of the decryption process for each slice of a non-IRAP picture, the decryption process for constructing the reference picture list is called to derive reference picture list 0 (RefPicList[0]) and reference picture list 1 (RefPicList[1]). The decryption process for marking reference pictures is called, and reference pictures may be marked as "not used for reference" or "used for long-term reference". This should only be called for the first slice of the picture. The decryption process for coding tree units, scaling, transformations, in-loop filtering, etc. is called. After all slices of the current picture have been decrypted, the current decrypted picture is marked as "used for short-term reference".

[0312] NAL unit decoding process

[0313] The input to this process is the NAL units of the current picture and their associated non-VCL NAL units. The output of this process is the analyzed RBSP syntax structure encapsulated within the NAL units. The decoding process for each NAL unit extracts the RBSP syntax structure from the NAL unit and then analyzes the RBSP syntax structure.

[0314] Slice decoding process

[0315] Decoding process related to picture sequence count

[0316] The output of this process is PicOrderCntVal, the picture order count of the current picture. The picture order count is used to identify the picture in order to derive motion parameters in merge mode and motion vector prediction and to check decoder compliance. Each coded picture is associated with a picture order count variable represented as PicOrderCntVal. When the current picture is not an IRAP picture, the variables prevPicOrderCntLsb and prevPicOrderCntMsb are derived as follows: Assume that prevTid0Pic is the previous picture in the decoding order, with a TemporalId equal to 0. The variable prevPicOrderCntLsb is set to be equal to slice_pic_order_cnt_lsb of prevTid0Pic. The variable prevPicOrderCntMsb is set to be equal to PicOrderCntMsb of prevTid0Pic. The variable PicOrderCntMsb of the current picture is derived as follows: If the current picture is an IRAP picture, PicOrderCntMsb is set to equal to 0. Otherwise, PicOrderCntMsb is derived as follows: if( ( slice_pic_order_cnt_lsb < prevPicOrderCntLsb ) && ( ( prevPicOrderCntLsb - slice_pic_order_cnt_lsb ) >= ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb + MaxPicOrderCntLsb else if( (slice_pic_order_cnt_lsb > prevPicOrderCntLsb ) && ( ( slice_pic_order_cnt_lsb - prevPicOrderCntLsb ) > ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb - MaxPicOrderCntLsb else PicOrderCntMsb = prevPicOrderCntMsb

[0317] PicOrderCntVal is derived as follows: PicOrderCntVal = PicOrderCntMsb + slice_pic_order_cnt_lsb

[0318] Since slice_pic_order_cnt_lsb is inferred to be 0 for IRAP pictures, and both prevPicOrderCntLsb and prevPicOrderCntMsb are set to be equal to 0, all IRAP pictures have a PicOrderCntVal equal to 0. The value of PicOrderCntVal is in the range of -231 to 231 - 1, including -231 and 231 - 1. In a single CVS, the PicOrderCntVal values ​​for any two coded pictures are not the same. At any moment during the decoding process, the values ​​of PicOrderCntVal & (MaxStPicOrderCntLsb - 1) for any two short-term reference pictures in the DPB are not the same. At any moment during the decoding process, the values ​​of PicOrderCntVal & (MaxLtPicOrderCntLsb - 1) for any two reference pictures in the DPB are not the same.

[0319] The function PicOrderCnt(picX) is specified as follows: PicOrderCnt(picX) = PicOrderCntVal of picture picX

[0320] The function DiffPicOrderCnt(picA, picB) is specified as follows: DiffPicOrderCnt(picA, picB) = PicOrderCnt(picA) - PicOrderCnt(picB)

[0321] The bitstream is -2 15 and 2 15 - 1 including -2 15 From 2 15 - Does not contain data that results in a value for DiffPicOrderCnt(picA, picB) used in the decoding process that is not within the range of 1. Assuming X is the current picture and Y and Z are two other pictures in the same CVS, Y and Z are considered to be in the same output order direction from X when both DiffPicOrderCnt(X, Y) and DiffPicOrderCnt(X, Z) are positive or both are negative.

[0322] Decryption process for building the reference picture list

[0323] This process is called at the beginning of the decoding process for each slice of a non-IRAP picture. The reference picture is addressed by a reference index, which is an index to the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (i.e., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, both reference picture list 0 and reference picture list 1 (i.e., RefPicList[1]) are used in decoding the slice data. At the beginning of the decoding process for each slice of a non-IRAP picture, the reference picture lists RefPicList[0] and RefPicList[1] are derived. The reference picture lists are used in marking the reference picture or in decoding the slice data. For I slices of non-IRAP pictures that are not the first slice of a picture, RefPicList[0] and RefPicList[1] may be derived for the purpose of checking bitstream compliance, but their derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. For P slices that are not the first slice of a picture, RefPicList[1] may be derived for the purpose of checking bitstream compliance, but its derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order.

[0324] The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { for( j = 0; j < NumEntriesInList[i]; j++ ) { if( lt_ref_pic_flag[i][j] ) { if (PicOrderCntVal & ( MaxLtPicOrderCntLsb - 1 ) is equal to poc_lsb_lt[i][j], there exists a reference picA in the DPB) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" } } } for( i = 0; i < 2; i++ ) { for( j = 0; j < NumEntriesInList[i]; j++ ) { if( !lt_ref_pic_flag[i][j] ) { if (PicOrderCntVal & ( MaxStPicOrderCntLsb - 1 ) is equal to poc_lsb_st[i][j] and there exists a short-term reference picture picA in the DPB) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" } } }

[0325] For each i equal to 0 or 1, the following applies:

[0326] The first NumRefIdxActive[i] entries in RefPicList[i] are called the active entries of RefPicList[i], and the other entries in RefPicList[i] are called the inactive entries of RefPicList[i]. For each j in the range from 0 to NumEntriesInList[i] - 1, including 0 and NumEntriesInList[i] - 1, each entry in RefPicList[i][j] is called a STRP entry if lt_ref_pic_flag[i][j] is equal to 0, and an LTRP entry otherwise. A particular picture can be referenced by entries in both RefPicList[0] and RefPicList[1]. A particular picture can also be referenced by two or more entries in RefPicList[0] or by two or more entries in RefPicList[1]. The active entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that may be used for interpretation of the current picture and one or more pictures that follow the current picture in the decoding order. The inactive entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that are not used for interpretation of the current picture but may be used for interpretation of one or more pictures that follow the current picture in the decoding order. There may be one or more entries in RefPicList[0] or RefPicList[1] that are equal to "no reference picture" because the corresponding picture does not exist in the DPB. Each inactive entry in RefPicList[0] or RefPicList[0] that is equal to "no reference picture" should be ignored.For each active entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture", an unintended loss of picture should be inferred.

[0327] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The STRP entries in RefPicList[0] or RefPicList[1] for a slice of a picture and the LTRP entries in RefPicList[0] or RefPicList[1] for the same slice or different slices of the same picture do not refer to the same picture. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0328] Decryption process for marking reference pictures

[0329] This process is called once per picture, after the decoding process for decoding the slice header and building the reference picture list for the slice, but before decoding the slice data. This process may result in one or more reference pictures in the DPB being marked as "Not for Reference" or "Used for Long-Term Reference". A decoded picture in the DPB can be marked as "Not for Reference", "Used for Short-Term Reference", or "Used for Long-Term Reference", however, at any given moment during the operation of the decoding process, it can be marked as just one of these three. Assigning one of these markings to a picture implicitly removes another of these markings, where applicable. When we say a picture is marked as "Used for Reference", this means collectively that the picture is marked as either "Used for Short-Term Reference" or "Used for Long-Term Reference" (but not both). When the current picture is an IRAP picture, all reference pictures (if any) currently in the DPB are marked as "Not for Reference". STRPs are identified by the Log2(MaxStPicOrderCntLsb) LSB of their PicOrderCntVal values. LTRPs are identified by the Log2(MaxLtPicOrderCntLsb) LSB of their PicOrderCntVal values.

[0330] The following applies: For each LTRP entry in RefPicList[0] or RefPicList[1], if the referenced picture is a STRP, the picture is marked as “Used for long-term reference.” Each referenced picture in the DPB that is not referenced by any entry in RefPicList[0] or RefPicList[1] is marked as “Not used for reference.”

[0331] Always signal the list of referenced pictures within the slice header, without distinguishing between short-term and long-term referenced pictures.

[0332] This section describes another alternative embodiment of the present disclosure. The description is relevant to the latest VVC WD (i.e., only the differences to the latest VVC WD of JVET-K1001-v1 are described, but the text of the latest VVC WD not described below remains applicable). This alternative embodiment is summarized as follows: The reference picture list structure is signaled only within the slice header. No distinction is made between short-term and long-term reference pictures. All reference pictures are simply referred to as reference pictures. Reference pictures are identified by the POC LSB of those reference pictures, which may be represented by a different number of bits than the number of bits used to represent the POC LSB that is signaled within the slice header for the derivation of the POC value.

[0333] Abbreviation. The text of section 4 of VVC WD applies.

[0334] Syntax of NAL unit headers

[0335] [Table 34]

[0336] RBSP syntax for sequence parameter sets

[0337] [Table 35]

[0338] RBSP syntax for picture parameter sets

[0339] [Table 36]

[0340] Slice header syntax

[0341] [Table 37]

[0342] Syntax of the reference picture list structure

[0343] [Table 38]

[0344] NAL Unit Header Semantics

[0345] `forbidden_zero_bit` is equal to 0. `nal_unit_type` specifies the type of RBSP data structure included in the NAL unit.

[0346] [Table 39]

[0347] The value obtained by subtracting 1 from nuh_temporal_id_plus1 specifies the time identifier for the NAL unit. The value of nuh_temporal_id_plus1 is not equal to 0. The variable TemporalId is specified as follows: TemporalId = nuh_temporal_id_plus1 - 1

[0348] When nal_unit_type is equal to IRAP_NUT, the coded slice belongs to an IRAP picture, and its TemporalId is equal to 0. The value of TemporalId is the same for all VCL NAL units of an access unit. The value of TemporalId for a coded picture or access unit is the value of TemporalId for the VCL NAL unit of the coded picture or access unit. The value of TemporalId for non-VCL NAL units is constrained as follows:

[0349] If nal_unit_type is equal to SPS_NUT, then TemporalId is equal to 0, and the TemporalId of the access unit containing the NAL unit is equal to 0. Otherwise, if nal_unit_type is equal to EOS_NUT or EOB_NUT, then TemporalId is equal to 0. Otherwise, TemporalId is greater than or equal to the TemporalId of the access unit containing the NAL unit. When the NAL unit is a non-VCL NAL unit, the value of TemporalId is equal to the smallest of the TemporalId values ​​of all access units to which the non-VCL NAL unit applies. When nal_unit_type is equal to PPS_NUT, TemporalId may be greater than or equal to the TemporalId of the containing access unit, since all Picture Parameter Sets (PPS) may be included at the beginning of the bitstream and the first coded picture has a TemporalId equal to 0. When nal_unit_type is equal to PREFIX_SEI_NUT or SUFFIX_SEI_NUT, TemporalId may be greater than or equal to the TemporalId of the containing access unit, because the SEI NAL unit may contain information applicable to a subset of the bitstream containing access units that have a TemporalId value greater than the TemporalId of the access unit containing the SEI NAL unit. nuh_reserved_zero_7bits is equal to '0000000'. Other values ​​for nuh_reserved_zero_7bits may be specified in the future by ITU_T | ISO / IEC. The decoder ignores (i.e., removes and discards) NAL units with nuh_reserved_zero_7bits values ​​that are not equal to '0000000'.

[0350] Semantics of RBSP for sequence parameter sets

[0351] log2_max_pic_order_cnt_lsb_minus4 specifies the value of the variable MaxPicOrderCntLsb used in the decoding process for picture order count as follows. MaxPicOrderCntLsb = 2 ( log2_max_pic_order_cnt_lsb_minus4 + 4 )

[0352] The value of log2_max_pic_order_cnt_lsb_minus4 is within the range from 0 to 12, including 0 and 12. The value obtained by adding 1 to sps_max_dec_pic_buffering_minusl specifies the maximum required size of the decoded picture buffer for CVS in picture storage buffer units. The value of sps_max_dec_pic_buffering_minusl is within the range from 0 to MaxDpbSize - 1, including 0 and MaxDpbSize - 1, where MaxDpbSize is specified elsewhere. additional_ref_poc_lsb specifies the value of the variable MaxRefPicOrderCntLsb used in the decoding process for reference picture list as follows. MaxRefPicOrderCntLsb = 2 ( log2_max_pic_order_cnt_lsb_minus4 + 4 + additional_ref_poc_lsb ) [[ID=ll]]

[0353] The value of additional_ref_poc_lsb is within the range from 0 to 32 - log2_max_pic_order_cnt_lsb_minus4 - 4, including 0 and 32 - log2_max_pic_order_cnt_lsb_minus4 - 4.

[0354] Semantics of the RBSP of the picture parameter set

[0355] The value obtained by adding 1 to num_ref_idx_default_active_minus1[i] specifies the inferred value of the variable NumRefIdxActive[0] for P or B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 0, and specifies the inferred value of NumRefIdxActive[1] for B slices where num_ref_idx_active_override_flag is equal to 0 when i is equal to 1. The value of num_ref_idx_default_active_minus1[i] is in the range of 0 to 14, including 0 and 14.

[0356] Slice header semantics

[0357] When present, the values ​​of the slice header syntax elements slice_pic_parameter_set_id and slice_pic_order_cnt_lsb are the same for all slice headers of the coded picture. ... slice_type specifies the coding type of the slice according to Table 7-3 (Table 40).

[0358] [Table 40]

[0359] When nal_unit_type is equal to IRAP_NUT, i.e., the picture is an IRAP picture, slice_type is equal to 2. ... slice_pic_order_cnt_lsb specifies the modulo MaxPicOrderCntLsb of the picture order count for the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4 + 4 bits. The value of slice_pic_order_cnt_lsb is in the range from 0 to MaxPicOrderCntLsb - 1, including 0 and MaxPicOrderCntLsb - 1. When slice_pic_order_cnt_lsb does not exist, it is inferred that slice_pic_order_cnt_lsb is equal to 0. A num_ref_idx_active_override_flag equal to 1 specifies that the syntax element num_ref_idx_active_minus1[0] exists for P and B slices, and that the syntax element num_ref_idx_active_minus1[1] exists for B slices. A num_ref_idx_active_override_flag equal to 0 specifies that the syntax elements num_ref_idx_active_minus1[0] and num_ref_idx_active_minus1[1] do not exist. When num_ref_idx_active_minus1[i] exists, it specifies the value of the variable NumRefIdxActive[i] as follows: NumRefIdxActive[i] = num_ref_idx_active_minus1[i] + 1

[0360] The value of num_ref_idx_active_minus1[i] is in the range of 0 to 14, including 0 and 14. The value of NumRefIdxActive[i] - 1 specifies the largest reference index for reference picture list i that may be used to decode the slice. When the value of NumRefIdxActive[i] is equal to 0, the reference index for reference picture list i may not be used to decode the slice. For i equal to 0 or 1, if the current slice is a B slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[i] is presumed to be equal to num_ref_idx_default_active_minus1[i] + 1. If the current slice is a P slice and num_ref_idx_active_override_flag is equal to 0, NumRefIdxActive[0] is presumed to be equal to num_ref_idx_default_active_minus1[0] + 1. When the current slice is a P slice, NumRefIdxActive[1] is presumed to be equal to 0. When the current slice is an I slice, both NumRefIdxActive[0] and NumRefIdxActive[1] are presumed to be equal to 0. Alternatively, for i equal to 0 or 1, the following applies after the above: rplsIdx1 is set to be equal to ref_pic_list_sps_flag[i] ? ref_pic_list_idx[i] : num_ref_pic_lists_in_sps[i], and numRpEntries[i] is equal to num_strp_entries[i][rplsIdx1] + num_ltrp_entries[i][rplsIdx1]. When NumRefIdxActive[i] is greater than numRpEntries[i], the value of NumRefIdxActive[i] is set to be equal to numRpEntries[i].

[0361] Semantics of the reference picture list structure

[0362] The ref_pic_list_struct(listIdx) syntax structure may exist within the slice header. If the ref_pic_list_struct(listIdx) syntax structure exists within the slice header, it specifies the listIdx of the reference picture list for the current picture (the picture containing the slice). num_ref_entries[listIdx] specifies the number of entries in the ref_pic_list_struct(listIdx) syntax structure. The variable NumEntriesInList[listIdx] is derived as follows: NumRefPicEntriesInRpl[listIdx] = num_ref_entries[listIdx]

[0363] The value of NumRefPicEntries[listIdx] is in the range from 0 to sps_max_dec_pic_buffering_minus1, including 0 and sps_max_dec_pic_buffering_minus1. poc_ref_lsb[listIdx][i] specifies the value of MaxRefPicOrderCntLsb, modulo MaxRefPicOrderCntLsb, of the picture order count of the picture referenced by the i-th entry of the ref_pic_list_struct(listIdx) syntax structure. The length of the poc_ref_lsb[listIdx][i] syntax element is Log2(MaxRefPicOrderCntLsb) bits.

[0364] The decryption process will be considered.

[0365] Overall decryption process

[0366] The decryption process operates as follows with respect to the current picture CurrPic: Decryption of NAL units is defined below. The process below defines the following decryption process using syntax elements above the slice header layer. Variables and functions related to the picture order count are derived. This should only be called for the first slice of the picture. At the beginning of the decryption process for each slice of a non-IRAP picture, the decryption process for constructing the reference picture list is called to derive reference picture list 0 (RefPicList[0]) and reference picture list 1 (RefPicList[1]). The decryption process for marking reference pictures is called, and reference pictures may be marked as "not used for reference". This should only be called for the first slice of the picture. The decryption process for coding tree units, scaling, transformations, in-loop filtering, etc. is called. After all slices of the current picture have been decrypted, the current decrypted picture is marked as "used for reference".

[0367] NAL unit decoding process

[0368] The input to this process is the NAL units of the current picture and their associated non-VCL NAL units. The output of this process is the analyzed RBSP syntax structure encapsulated within the NAL units. The decoding process for each NAL unit extracts the RBSP syntax structure from the NAL unit and then analyzes the RBSP syntax structure.

[0369] Slice decoding process

[0370] Decoding process related to picture sequence count

[0371] The output of this process is PicOrderCntVal, the picture order count of the current picture. The picture order count is used to identify the picture in order to derive motion parameters in merge mode and motion vector prediction and to check decoder compliance. Each coded picture is associated with a picture order count variable represented as PicOrderCntVal. When the current picture is not an IRAP picture, the variables prevPicOrderCntLsb and prevPicOrderCntMsb are derived as follows: Assume that prevTid0Pic is the previous picture in the decoding order, with a TemporalId equal to 0. The variable prevPicOrderCntLsb is set to be equal to slice_pic_order_cnt_lsb of prevTid0Pic. The variable prevPicOrderCntMsb is set to be equal to PicOrderCntMsb of prevTid0Pic. The variable PicOrderCntMsb of the current picture is derived as follows: If the current picture is an IRAP picture, PicOrderCntMsb is set to equal to 0. Otherwise, PicOrderCntMsb is derived as follows: if( ( slice_pic_order_cnt_lsb < prevPicOrderCntLsb ) && ( ( prevPicOrderCntLsb - slice_pic_order_cnt_lsb ) >= ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb + MaxPicOrderCntLsb else if( (slice_pic_order_cnt_lsb > prevPicOrderCntLsb ) && ( ( slice_pic_order_cnt_lsb - prevPicOrderCntLsb ) > ( MaxPicOrderCntLsb / 2 ) ) ) PicOrderCntMsb = prevPicOrderCntMsb - MaxPicOrderCntLsb else PicOrderCntMsb = prevPicOrderCntMsb

[0372] PicOrderCntVal is derived as follows: PicOrderCntVal = PicOrderCntMsb + slice_pic_order_cnt_lsb

[0373] Since slice_pic_order_cnt_lsb is inferred to be 0 for IRAP pictures, and both prevPicOrderCntLsb and prevPicOrderCntMsb are set to be equal to 0, all IRAP pictures have a PicOrderCntVal equal to 0. The value of PicOrderCntVal is in the range of -231 to 231 - 1, including -231 and 231 - 1. In a single CVS, the PicOrderCntVal values ​​for any two coded pictures are not the same. At any moment during the decoding process, the values ​​of PicOrderCntVal & (MaxRefPicOrderCntLsb - 1) for any two reference pictures in the DPB are not the same.

[0374] The function PicOrderCnt(picX) is specified as follows: PicOrderCnt(picX) = PicOrderCntVal of picture picX

[0375] The function DiffPicOrderCnt(picA, picB) is specified as follows: DiffPicOrderCnt(picA, picB) = PicOrderCnt(picA) - PicOrderCnt(picB)

[0376] The bitstream does not contain data that would result in a DiffPicOrderCnt(picA, picB) value used in the decoding process that is not within the range of -215 to 215 - 1, including -215 and 215 - 1. Assuming that X is the current picture and Y and Z are two other pictures in the same CVS, Y and Z are considered to be in the same output order direction from X when both DiffPicOrderCnt(X, Y) and DiffPicOrderCnt(X, Z) are positive or both are negative.

[0377] Decryption process for building the reference picture list

[0378] This process is called at the beginning of the decoding process for each slice of a non-IRAP picture. The reference picture is addressed by a reference index, which is an index to the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (i.e., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, both reference picture list 0 and reference picture list 1 (i.e., RefPicList[1]) are used in decoding the slice data. At the beginning of the decoding process for each slice of a non-IRAP picture, the reference picture lists RefPicList[0] and RefPicList[1] are derived. The reference picture lists are used in marking the reference picture or in decoding the slice data. For I-slices of non-IRAP pictures that are not the first slice of a picture, RefPicList[0] and RefPicList[1] may be derived for the purpose of checking bitstream compliance, but their derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. For P-slices that are not the first slice of a picture, RefPicList[1] may be derived for the purpose of checking bitstream compliance, but its derivation is not required for decoding the current picture or any picture that follows the current picture in the decoding order. The reference picture lists RefPicList[0] and RefPicList[1] are constructed as follows: for( i = 0; i < 2; i++ ) { for( j = 0, pocBase = PicOrderCntVal; j < NumEntriesInList[i]; j++ ) { if (PicOrderCntVal & ( MaxRefPicOrderCntLsb - 1 ) is equal to poc_ref_lsb[i][j] and there exists a reference picA in the DPB) RefPicList[i][j] = picA else RefPicList[i][j] = "no reference picture" } }

[0379] For each i equal to 0 or 1, the first NumRefIdxActive[i] entries in RefPicList[i] are called the active entries of RefPicList[i], and the remaining entries in RefPicList[i] are called the inactive entries of RefPicList[i]. A particular picture can be referenced by both entries in RefPicList[0] and entries in RefPicList[1]. A particular picture can also be referenced by two or more entries in RefPicList[0] or by two or more entries in RefPicList[1]. The active entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that may be used for interpretation of the current picture and one or more pictures that follow the current picture in decoding order. Inactive entries in RefPicList[0] and RefPicList[1] collectively refer to all reference pictures that are not used for interpretation of the current picture but may be used for interpretation of one or more pictures that follow the current picture in the decoding order. There may be one or more entries in RefPicList[0] or RefPicList[1] that are equal to "no reference picture" because the corresponding picture does not exist in the DPB. Each inactive entry in RefPicList[0] or RefPicList[0] that is equal to "no reference picture" should be ignored. For each active entry in RefPicList[0] or RefPicList[1] that is equal to "no reference picture", an unintended loss of a picture should be inferred.

[0380] The following constraints apply to the bitstream compliance requirements: For each i equal to 0 or 1, NumEntriesInList[i] is greater than or equal to NumRefIdxActive[i]. The pictures referenced by each active entry in RefPicList[0] or RefPicList[1] exist in the DPB and have a TemporalId less than or equal to the TemporalId of the current picture. Optionally, the following constraints may be further specified: The entry index of any inactive entry in RefPicList[0] or RefPicList[1] is not used as a reference index for decoding the current picture. Optionally, the following constraints may be further specified: No inactive entry in RefPicList[0] or RefPicList[1] references the same picture as any other entry in RefPicList[0] or RefPicList[1]. The current picture itself is not referenced by any entry in RefPicList[0] or RefPicList[1]. There are no entries in RefPicList[0] or RefPicList[1] where the difference between the current picture's PicOrderCntVal and the PicOrderCntVal of the picture referenced by the entry is 224 or greater. setOfRefPics is the set of unique pictures referenced by all entries in RefPicList[0] and all entries in RefPicList[1]. The number of pictures in setOfRefPics is less than or equal to sps_max_dec_pic_buffering_minus1, and setOfRefPics is the same for all slices of the picture.

[0381] Decryption process for marking reference pictures

[0382] This process is called once per picture, after the decoding process for decoding the slice header and building the reference picture list for the slice, but before decoding the slice data. This process may result in one or more reference pictures in the DPB being marked as "not used for reference". Decoded pictures in the DPB can be marked as either "not used for reference" or "used for reference", however, at any given moment during the operation of the decoding process, they can be marked as only one of these two. Assigning one of these markings to a picture implicitly removes another of these markings, if applicable. When the current picture is an IRAP picture, all reference pictures (if any) currently in the DPB are marked as "not used for reference". Reference pictures in the DPB are identified by their PicOrderCntVal value Log2(MaxRefPicOrderCntLsb) LSB. Each referenced picture in the DPB that is not referenced by any entry in RefPicList[0] or RefPicList[1] is marked as "not used for reference".

[0383] Yet another alternative embodiment

[0384] This section describes an alternative embodiment of the technique described in detail above, which is called "always signaling the reference picture list in the slice header so as to distinguish between short-term and long-term reference pictures." In this alternative embodiment, the POC MSB cycle may be signaled in the slice header for each LTRP entry, similar to HEVC or the technique described above, but with the following constraint removed: At any given moment during the decoding process, the values ​​of PicOrderCntVal & (MaxLtPicOrderCntLsb - 1) for any two reference pictures in the DPB are not the same.

[0385] Figure 6 is a schematic diagram of a video coding device 600 (for example, a video encoder 20 or a video decoder 30) according to an embodiment of the present disclosure. The video coding device 600 is suitable for implementing embodiments disclosed as described herein. The video coding device 600 includes an incoming port 610 and a receiver unit (Rx) 620 for receiving data, a processor, logic unit, or central processing unit (CPU) 630 for processing data, a transmitter unit (Tx) 640 and an outgoing port 650 for transmitting data, and memory 660 for storing data. The video coding device 600 may also include optical-electrical (OE) and electrical-optical (EO) components connected to the incoming port 610, receiver unit 620, transmitter unit 640, and outgoing port 650 for receiving or transmitting optical or electrical signals.

[0386] The processor 630 is implemented by hardware and software. The processor 630 may be implemented as one or more CPU chips, cores (e.g., as a multi-core processor), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and digital signal processors (DSPs). The processor 630 communicates with the incoming port 610, the receiver unit 620, the transmitter unit 640, the outgoing port 650, and the memory 660. The processor 630 includes a coding module 670. The coding module 670 implements the embodiments disclosed above. For example, the coding module 670 implements, processes, prepares, or provides various networking functions. Thus, including the coding module 670 significantly improves the functionality of the video coding device 600 and enables the transition of the video coding device 600 to different states. Alternatively, the coding module 670 is implemented as instructions stored in the memory 660 and executed by the processor 630.

[0387] The video coding device 600 may also include input and / or output (I / O) devices 680 for transmitting data to and from the user. The I / O devices 680 may include output devices such as a display for showing video data and speakers for outputting audio data. The I / O devices 680 may also include input devices such as a keyboard, mouse, or trackball, and / or corresponding interfaces for interacting with such output devices.

[0388] Memory 660 may include one or more disks, tape drives, and solid-state drives and may be used as an over-flow data storage device to store such programs when selected for execution, as well as instructions and data read during program execution. Memory 660 may be volatile and / or non-volatile and may be read-only memory (ROM), random-access memory (RAM), ternary content-addressable memory (TCAM), and / or static random-access memory (SRAM).

[0389] Figure 7 is a schematic diagram of an embodiment of the coding means 700. In this embodiment, the coding means 700 is implemented in a video coding device 702 (for example, a video encoder 20 or a video decoder 30). The video coding device 702 includes a receiving means 701. The receiving means 701 is configured to receive a picture to encode or a bitstream to decode. The video coding device 702 includes a transmitting means 707 connected to the receiving means 701. The transmitting means 707 is configured to send the bitstream to the decoder or to send the decoded image to a display means (for example, one of the I / O devices 680).

[0390] The video coding device 702 includes a storage means 703. The storage means 703 is connected to at least one of the receiving means 701 or the transmitting means 707. The storage means 703 is configured to store instructions. The video coding device 702 also includes a processing means 705. The processing means 705 is connected to the storage means 703. The processing means 705 is configured to execute instructions stored in the storage means 703 for performing the method disclosed herein.

[0391] While several embodiments are given in this disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of this disclosure. These examples should be considered illustrative and not limiting, and the intent should not be limited to the details given herein. For example, various elements or components may be combined or integrated into another system, or certain features may be omitted or not implemented.

[0392] In addition, technologies, systems, subsystems, and methods described and illustrated as separate or distinct in various embodiments may be combined with or integrated with other systems, modules, technologies, or methods without departing from the scope of this disclosure. Others shown or considered as being coupled to or directly coupled to one another, or communicating to one another, may be indirectly coupled or communicating through any interface, device, or intermediate component, whether electrical, mechanical, or otherwise. Other examples of changes, substitutions, and modifications may be discovered by those skilled in the art and may be made without departing from the spirit and scope of what is disclosed herein. [Explanation of symbols]

[0393] 10 Coding Systems 12. Source device 14 Destination device 16 Computer-readable media 18 Video Sources 20 Video Encoders 22 Output Interfaces 28 Input Interfaces 30 video decoders 32 Display Devices 40 Mode Selection Unit 42 Motion Estimation Unit 44 Motion compensation unit 46 Intra Prediction Units 48 division units 50 Adder 52 Conversion Processing Unit 54 Quantization Units 56 Entropy Coding Unit 58 Inverse Quantization Unit 60 Reverse Conversion Unit 62 Adder 64 Reference frame memory 70 Entropy Decoding Unit 72 Motion Compensation Unit 74 Intra Prediction Units 76 Inverse Quantization Unit 78 Reverse Conversion Unit 80 Adder 82 Reference frame memory 400 Reference Picture Sets (RPS) 402 subset 500 ways 600 video coding devices 610 Incoming Port 620 Receiver Unit (Rx) 630 Processors, Logical Units, Central Processing Units (CPUs) 640 Transmitter Unit (Tx) 650 Outgoing Port 660 memory 670 Coding Modules 680 Input and / or Output (I / O) Devices 700 Means for coding 701 Receiving means 702 Video Coding Device 703 Memory means 705 Processing means 707 Transmission method

Claims

1. A method of encoding performed by a video encoder, Steps to build the reference picture list for the current slice, A step of obtaining at least one reconstructed block of the current slice based on the aforementioned reference picture list, A step of encoding the index of a reference picture list structure into the slice header of the current slice in the video bitstream, wherein the reference picture list structure includes the number of entries used to derive entries in the reference picture list, and the reference picture list structure is among a set of reference picture list structures in the parameter set of the video bitstream, num_ref_pic_lists_in_sps A step of encoding [i] into the video bitstream to obtain the coded video bitstream, wherein the num_ref_pic_lists_in_sps A method comprising the steps of: [i] identifying the number of reference picture list structures included in the sequence parameter set (SPS) whose list index is equal to i.

2. The method according to claim 1, wherein the order of entries in the reference picture list structure is the same as the order of corresponding reference pictures in the reference picture list, and each entry in the reference picture list structure describes a corresponding reference picture in the reference picture list.

3. The method according to claim 1 or 2, wherein the at least one reconstructed block is used to generate an image that is displayed on the display of an electronic device.

4. The method according to any one of claims 1 to 3, wherein the reference picture list includes a list of reference pictures used for interpretation of the at least one reconstructed block.

5. The method according to any one of claims 1 to 4, wherein the current slice is a P slice or is for a B slice.

6. The method according to any one of claims 1 to 5, wherein the parameter set includes a sequence parameter set (SPS).

7. The method according to any one of claims 1 to 6, wherein a set of syntax elements from the parameter set is placed in the raw byte sequence payload (RBSP) of a network abstraction layer (NAL) unit.

8. A memory connected to a receiver, which stores instructions, The memory includes a processor, and the processor is Constructing the current slice's reference picture list, Based on the aforementioned reference picture list, obtain at least one reconstructed block of the current slice, Encoding the index of a reference picture list structure into the video bitstream, into the slice header of the current slice, wherein the reference picture list structure includes the number of entries used to derive the entries of the reference picture list, and the reference picture list structure is among a set of reference picture list structures in the parameter set of the video bitstream. num_ref_pic_lists_in_sps [i] is encoded into the video bitstream, wherein the num_ref_pic_lists_in_sps [i] identifies the number of reference picture list structures included in the sequence parameter set (SPS) whose list index is equal to i, An encoding device configured to execute the instructions stored in the memory, which causes the processor to perform the above.

9. An encoder comprising a processing circuit for performing the method according to any one of claims 1 to 7.

10. A computer program comprising program code for performing the method described in any one of claims 1 to 7 when executed on a computer or processor.

11. A computer-readable non-temporary storage medium storing program code that, when executed by a computer device, causes the computer device to perform the method according to any one of claims 1 to 7.

12. A method for decoding a coded video bitstream, performed by a video decoder, A step of analyzing a set of parameters shown in the coded video bitstream, wherein the set of parameters includes a set of reference picture list structures. A step of analyzing the slice header of the current slice shown in the coded video bitstream, wherein the slice header includes an index of a reference picture list structure among the set of reference picture list structures in the parameter set; The num_ref_pic_lists_in_sps of the coded video bitstream A step of parsing the parameter set in order to obtain [i], wherein the num_ref_pic_lists_in_sps [i] is a step in which the number of reference picture list structures included in the sequence parameter set (SPS) whose list index is equal to i, The steps include: deriving the reference picture list of the current slice based on the set of reference picture list structures and the index of the reference picture list structure; A step of obtaining at least one reconstructed block of the current slice based on the aforementioned reference picture list. A method that includes this.

13. The method according to claim 12, wherein the order of entries in the reference picture list structure is the same as the order of corresponding reference pictures in the reference picture list, and each entry in the reference picture list structure describes a corresponding reference picture in the reference picture list.

14. The method according to any one of claims 12 or 13, wherein the at least one reconstructed block is used to generate an image that is displayed on the display of an electronic device.

15. The method according to any one of claims 12 to 14, wherein the reference picture list includes a list of reference pictures used for interpretation of the at least one reconstructed block.

16. The method according to any one of claims 12 to 15, wherein the current slice is a P slice or a B slice.

17. The method according to any one of claims 12 to 16, wherein the parameter set includes a sequence parameter set (SPS).

18. The method according to any one of claims 12 to 17, wherein a set of syntax elements from the parameter set is placed in the raw byte sequence payload (RBSP) of a network abstraction layer (NAL) unit.

19. A receiver configured to receive an encoded video bitstream, A memory connected to the receiver, comprising a memory for storing instructions, A processor connected to the memory, configured to execute the instructions stored in the memory. Includes, The aforementioned instruction is given to the processor, Analyzing the parameter set shown in the coded video bitstream, wherein the parameter set includes a set of reference picture list structures. Parsing the slice header of the current slice shown in the coded video bitstream, wherein the slice header includes an index of a reference picture list structure among the set of reference picture list structures in the parameter set, The num_ref_pic_lists_in_sps of the coded video bitstream A step of parsing the parameter set in order to obtain [i], wherein the num_ref_pic_lists_in_sps [i] is a step in which the number of reference picture list structures included in the sequence parameter set (SPS) whose list index is equal to i, Deriving the reference picture list of the current slice based on the set of reference picture list structures and the index of the reference picture list structure, Obtaining at least one reconstructed block of the current slice based on the aforementioned reference picture list A decryption device that performs this operation.

20. A display configured to display an image based on the at least one reconstructed block. The decoding device according to claim 19, further comprising:

21. A decoder comprising a processing circuit for performing the method according to any one of claims 12 to 18.

22. A computer program comprising program code for performing the method described in any one of claims 12 to 18 when executed on a computer or processor.

23. A computer-readable non-temporary storage medium storing program code that, when executed by a computer device, causes the computer device to perform the method according to any one of claims 12 to 18.

24. A step of obtaining a video bitstream coded by performing the method according to any one of claims 1 to 7, The steps include storing the coded video bitstream in one or more recording media, A method for providing this.

Images