Substribution of subsegment-based stream operation in edrap-based

By allowing EDRAP sample points to not start segments and requiring the same presentation time in ESR, the problems of insufficient stream operation granularity and decoding consistency in DASH technology are solved, and efficient, flexible control and consistent bitstream of video streams are achieved.

CN119013958APending Publication Date: 2024-11-22DOUYIN CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033960.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-12
Filing Date
2023-04-12
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In the existing DASH technology, the EDRAP sample points in MSR do not allow the segment to be started, which limits the flow operation based on sub-segment, and lacks the bitstream requirement to support the splicing consistency between the ESR segment and the MSR segment, resulting in insufficient flow control granularity and Decoding error.

Method used

Allows EDRAP sample points in MSR not to start segments, and requires segments or sub-segments with the same earliest presentation time in the associated ESR, ensuring that the splicing of ESR and MSR segments or sub-segments produces a consistent bit stream, supporting segments Both the sub-segment start the flow operation.

Benefits of technology

A more fine-grained control of the video stream is achieved, ensuring the standardization and decoding consistency of the bitstream, avoiding errors in stream operations, and improving the flexibility and decoding of the stream.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119013958A_ABST
    Figure CN119013958A_ABST
Patent Text Reader

Abstract

A mechanism for processing video data is disclosed. The conversion is performed between the visual media data and the media data file based on one or more extension dependent random access point (EDRAP) sample points. Each EDRAP sample should be a first sample in a segment or sub-segment of a mainstream representation (MSR).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 330,210, filed by Ye-Kui Wang on April 12, 2022, entitled “Support of subsegments based streaming operations in EDRAP based video streaming,” which is hereby incorporated herein by reference. Technical Field

[0003] This patent document relates to the generation, storage and consumption of digital audio-visual media information in file format. Background Art

[0004] Digital video accounts for the largest share of bandwidth used on the Internet and other digital communications networks. As the number of connected user devices capable of receiving and displaying video increases, bandwidth demands for digital video usage are likely to continue to grow. Summary of the invention

[0005] A first aspect relates to a method for processing video data, comprising: performing conversion between visual media data and a media data file based on one or more Extended Dependent Random Access Point (EDRAP) samples, wherein each EDRAP sample should be the first sample in a segment or subsegment of a Main Stream Representation (MSR).

[0006] A second aspect relates to a device for processing video data, comprising: a processor; and a non-volatile memory having instructions thereon, wherein the instructions, when executed by the processor, cause the processor to perform any of the aforementioned aspects.

[0007] A third aspect relates to a non-transitory computer-readable medium comprising a computer program product for use with a video codec device, the computer program product comprising computer-executable instructions, wherein the computer-executable instructions are stored on the non-transitory computer-readable medium so that when executed by a processor, the video codec device performs the method of any of the preceding aspects.

[0008] A fourth aspect relates to a non-transitory computer-readable recording medium storing a bitstream of a video generated by a method performed by a video processing device, wherein the method includes determining based on one or more extended dependent random access point (EDRAP) samples to perform conversion between visual media data and a media data file, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR); and generating a bitstream based on the determination.

[0009] A fifth aspect relates to a method for storing a bitstream of a video, comprising: determining, based on one or more extended dependent random access point (EDRAP) samples, to perform conversion between visual media data and a media data file, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR); generating a bitstream based on the determination; and storing the bitstream in a non-transitory computer-readable recording medium.

[0010] A sixth aspect relates to a method, apparatus or system described in this document.

[0011] For purposes of clarity, any of the aforementioned embodiments may be combined with any one or more of the other aforementioned embodiments to create new embodiments within the scope of the present disclosure.

[0012]

[0011] These and other features will become more clearly understood from the following detailed description and claims taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] 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 and detailed description, wherein like reference numerals represent like parts.

[0014] Figure 1 is a diagram of an example mechanism for random access when decoding a bitstream using intra random access point (IRAP) pictures.

[0015] Figure 2 is a diagram of an example mechanism for random access when decoding a bitstream using Dependent Random Access Point (DRAP) pictures.

[0016] Figure 3 is a diagram of an example mechanism for random access when decoding a bitstream using Extended Dependent Random Access Point (EDRAP) pictures.

[0017] Figure 4 is a diagram of an example mechanism for signaling that an external bitstream supports EDRAP-based random access.

[0018] Figure 5 An example of EDRAP-based random access is shown.

[0019] Figure 6 is a block diagram illustrating an example video processing system.

[0020] Figure 7 is a block diagram of an example video processing device.

[0021] Figure 8is a flow chart of an example method for video processing.

[0022] Fig. 9 is a block diagram illustrating an example video codec system.

[0023] Fig.10 is a block diagram illustrating an example encoder.

[0024] Fig.11 is a block diagram illustrating an example decoder.

[0025] Fig.12 is a schematic diagram of an example encoder.

[0026] Fig.13 is a flow chart of an example method for video processing. DETAILED DESCRIPTION

[0027] First, it should be understood that although illustrative implementations of one or more embodiments are provided below, the disclosed systems and / or methods may be used with any number of technical facts, whether currently known or yet to be developed. The present disclosure should not be limited in any way to the example implementations, drawings, and techniques shown below, including the example designs and implementations shown and described herein, but may be modified within the full scope of the appended claims and their equivalents.

[0028] The section headings used in this document are for ease of understanding and do not limit the applicability of the techniques and embodiments disclosed in each section to only that section. In addition, the use of H.266 terminology in some descriptions is only for ease of understanding and is not intended to limit the scope of the disclosed technology. Therefore, the techniques described herein are also applicable to other video codec protocols and designs. In this document, with respect to drafts of the Common Video Codec (VVC) specification or the ISO Base Media File Format (ISOBMFF) file format specification, editorial changes to text are shown with bold italics to indicate canceled text and with bold underlining to indicate added text.

[0029] 1. Preliminary Discussion

[0030] This document relates to video streaming. Specifically, it relates to support for subsegment-based streaming operations in video streaming based on Extended Dependent Random Access Points (EDRAP). EDRAP-based streaming involves the use of Main Stream Representation (MSR) and External Stream Representation (ESR) in Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH). These ideas can be applied alone or in various combinations to media streaming systems, for example based on the DASH standard or its extensions.

[0031] 2. Video Codec Introduction

[0032] 2.1 Video Codec Standards

[0033] Video codec standards have evolved primarily through the development of standards by the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) and the International Organization for Standardization (ISO) / International Electrotechnical Commission (IEC). ITU-T produced H.261 and H.263, ISO / IEC produced the Moving Picture Experts Group (MPEG-1) and MPEG-4 Vision, and the two organizations jointly produced the H.262 / MPEG-2 Video and H.264 / MPEG-4 Advanced Video Codec (AVC) and H.265 / High Efficiency Video Codec (HEVC) [1] standards. Since H.262, video codec standards have been based on a hybrid video codec structure that utilizes temporal prediction plus transform coding. To explore future video codec technologies beyond HEVC, the Video Codec Experts Group (VCEG) and MPEG jointly established the Joint Video Exploration Team (JVET) in 2015. JVET has adopted many of the approaches and put them into a reference software called the Joint Exploration Model (JEM) [2]. When the Versatile Video Codec (VVC) project was officially launched, JVET was renamed the Joint Video Experts Team (JVET). VVC[3] is a codec standard that aims to reduce the bit rate by 50% compared to HEVC.

[0034] The Versatile Video Codec (VVC) standard (ITU-T H.266 | ISO / IEC 23090-3) [3][4] and the associated Versatile Supplementary Enhancement Information (VSEI) standard (ITU-T H.274 | ISO / IEC 23002-7) [5][6] are designed for the widest range of applications, including both traditional uses (such as television broadcasting, video conferencing or playback from storage media), and also newer and more advanced use cases such as adaptive bitrate streaming, video region extraction, content synthesis and merging from multiple codec video bitstreams, multi-view video, scalable layered codecs and viewport-adaptive 360° immersive media.

[0035] The Essential Video Codec (EVC) standard (ISO / IEC 23094-1) is another video codec standard developed by MPEG.

[0036] 2.2 File Format Standards

[0037] Media streaming applications are based on Internet Protocol (IP), Transmission Control Protocol (TCP) and Hypertext Transfer Protocol (HTTP) transport methods and rely on file formats such as ISO Base Media File Format (ISOBMFF) [7]. One such streaming system is Dynamic Adaptive Streaming over HTTP (DASH) [8]. In order to use video formats with ISOBMFF and DASH, file format specifications specific to the video format are required, such as the AVC file format and the HEVC file format in [9], to encapsulate the video content in ISOBMFF tracks and DASH representations and segments. Important information about the video bitstream (e.g., profile, tier, and level, etc.) needs to be exposed as file format level metadata and / or DASH Media Presentation Description (MPD) to facilitate content selection, e.g., selecting appropriate media segments for initialization at the start of a streaming session and for stream adaptation during a streaming session.

[0038] Similarly, in order to use an image format with ISOBMFF, a file format specification specific to the image format (such as the AVC image file format and the HEVC image file format in

[10] ) is required.

[0039] MPEG is developing the VVC video file format, a file format based on ISOBMFF for storing VVC video content. The draft specification of the VVC video file format is included in

[11] .

[0040] MPEG is developing the VVC picture file format, a file format based on ISOBMFF for storing picture content using the VVC codec. A draft specification for the VVC picture file format is included in

[12] .

[0041] 2.3DASH

[0042] In Dynamic Adaptive Streaming over HTTP (DASH) [8], there may be multiple representations of video and / or audio data of multimedia content, and different representations may correspond to different codec characteristics (e.g., different profiles or video codec standard levels, different bit rates, different spatial resolutions, etc.). A list of such representations may be defined in a Media Presentation Description (MPD) data structure. A media presentation may correspond to a structured set of data accessible to a DASH streaming client device. A DASH streaming client device may request and download media data information to present a streaming service to a user of the client device. A media presentation may be described in an MPD data structure and may include updates to the MPD.

[0043] A media presentation may include a sequence of one or more cycles. Each cycle may extend to the beginning of the next cycle, or in the case of the last cycle, to the end of the media presentation. Each cycle may include one or more representations of the same media content. The representation may be one of multiple alternative coded versions of audio, video, timed text or other such data. The representation may vary depending on the type of encoding, for example, depending on the bit rate, resolution and / or codec of the video data and the bit rate, language and / or codec of the audio data. The term "representation" may be used to refer to a segment of coded audio or video data that corresponds to a specific cycle of multimedia content and is encoded in a specific manner.

[0044] Representations of a particular period may be assigned to a group indicated by an attribute in the MPD that indicates the adaptation set to which these representations belong. Representations in the same adaptation set are generally considered to be alternatives to each other because client devices can dynamically and seamlessly switch between these representations, for example, to perform bandwidth adaptation. For example, each representation of video data for a particular period may be assigned to the same adaptation set so that any of these representations may be selected for decoding to present media data of the multimedia content of the corresponding period, such as video data or audio data. In some examples, the media content within a period may be represented by a combination of one representation from group 0 (if present) or at most one representation from each non-zero group. The time data for each representation of a period may be expressed relative to the start time of the period.

[0045] A representation may include one or more segments. Each representation may include an initialization segment, or each segment of a representation may be self-initializing. When present, the initialization segment may contain initialization information for accessing the representation. Generally, the initialization segment does not contain media data. A segment may be uniquely referenced by an identifier such as a uniform resource locator (URL), a uniform resource name (URN), or a uniform resource identifier (URI). The MPD may provide an identifier for each segment. In some examples, the MPD may also provide a byte range in the form of a range attribute, which may correspond to data for a segment within a file accessible via a URL, URN, or URI.

[0046] Different representations may be selected to retrieve different types of media data substantially simultaneously. For example, a client device may select an audio representation, a video representation, and a timed text representation from which to retrieve a segment. In some examples, a client device may select a particular adaptation set to perform bandwidth adaptation. That is, a client device may select an adaptation set that includes a video representation, an adaptation set that includes an audio representation, and / or an adaptation set that includes timed text. Alternatively, a client device may select an adaptation set for certain types of media (e.g., video) and directly select representations for other types of media (e.g., audio and / or timed text).

[0047] An example DASH streaming process is shown by the following steps:

[0048] 1) The client obtains the MPD.

[0049] 2) The client estimates the downstream bandwidth and selects the video representation and the audio representation according to the estimated downstream bandwidth as well as the codec, decoding capability, display size, audio language setting, etc.

[0050] 3) Unless the media presentation ends, the client requests the media segments of the selected representation and presents the streaming content to the user.

[0051] 4) The client maintains the estimated downstream bandwidth. When the bandwidth changes significantly in one direction (e.g., becomes lower), the client selects a different video representation to match the new estimated bandwidth and goes to step 3.

[0052] 2.4 DASH segments and sub-segments

[0053] In DASH, a segment is a unit of data associated with an HTTP-URL and optionally with a byte range specified by an MPD or with a data URL. A subsegment is a unit within a segment indexed by a Segment Index. The Segment Index is independent of the MPD as a compact index of time range to byte range mapping within a segment.

[0054] Given the length of a segment, sub-segment based streaming operations allow for finer granularity control of the streaming process by requesting media data at a finer granularity. To request a sub-segment in a segment, the segment index needs to be requested in advance to obtain the sub-segment information, and a local HTTP GET request is used.

[0055] 2.5 Video Coding, Decoding, Storage and Streaming Based on Extended Dependent Random Access Points (EDRAP)

[0056] 2.5.1 Concept and Standard Support

[0057] This paper describes the concepts of video encoding, decoding, storage and streaming based on EDRAP.

[0058] like Figure 1 As shown, the application (e.g., adaptive streaming) determines the frequency of random access points (RAPs), for example, the RAP period is 1s or 2s. In the example, the RAP is provided by the codec of the IRAP picture. Note that the inter-frame prediction references of non-critical pictures between RAP pictures are not shown and are in output order from left to right. When randomly accessed from clean random access (CRA) 4, the decoder receives CRA4, CRA5, etc. and the related inter-frame prediction pictures and decodes them correctly.

[0059] Figure 2The DRAP method is shown, which improves codec efficiency by allowing DRAP pictures (and subsequent pictures) to refer to the previous IRAP picture for inter-frame prediction. Note that inter-frame prediction of non-critical pictures between RAP pictures is not shown and is in output order from left to right. When randomly accessing from DRAP4, the decoder receives instantaneous decoder refresh (IDR) 0, DRAP4, DRAP5, etc. and the related inter-frame predicted pictures and decodes them correctly.

[0060] Figure 3 The EDRAP method is shown, which provides greater flexibility by allowing EDRAP pictures (and subsequent pictures) to reference some earlier RAP pictures (IRAP or EDRAP). Note that inter-frame prediction of non-critical pictures between RAP pictures is not shown and is in output order from left to right. When randomly accessing from EDRAP4, the decoder receives IDR0, EDRAP2, EDRAP4, EDRAP5, etc. and the related inter-frame predicted pictures and decodes them correctly.

[0061] Figure 4 An example of the EDRAP method using the MSR segment and the ESR segment is shown. Figure 5 An example of random access from EDRAP4 is shown. When randomly accessing or switching to a segment starting with EDRAP4, the decoder receives and decodes segments including IDR0, EDRAP2, EDRAP4, EDRAP5, etc. and related inter-frame prediction pictures.

[0062] EDRAP-based video codecs are supported by the EDRAP indication SEI message included in

[13] (i.e., the VSEI standard amendment); the storage part is supported by the EDRAP sample group and associated external stream track reference included in

[14] (i.e., the ISOBMFF standard amendment); and the streaming part is supported by the main stream representation (MSR) and external stream representation (ESR) descriptors included in

[15] (i.e., the DASH standard amendment). These standards support are described below.

[0063] 2.5.2 EDRAP Indication SEI Message

[0064] An amendment to the VSEI standard is under development. An example draft specification for this amendment is included in JVET-Y2006

[13] , including the specification of the EDRAP indication SEI message.

[0065] The syntax and semantics of the EDRAP indication SEI message are as follows.

[0066]

[0067] A picture associated with the Extended DRAP (EDRAP) indication SEI message is called an EDRAP picture.

[0068] The presence of an EDRAP indication SEI message indicates that the constraints on picture order and picture references specified in this subclause apply. These constraints enable a decoder to correctly decode an EDRAP picture and pictures located in the same layer and following the EDRAP picture in decoding order and output order without decoding any other pictures in the same layer, except for a list of referenceablePictures that includes a list of IRAP or EDRAP pictures located in the same codec layer video sequence (CLVS) in decoding order and identified by the edrap_ref_rap_id[i] syntax element.

[0069] The constraints (which shall all apply) for indicating the presence of SEI messages via EDRAP are as follows:

[0070] -EDRAP picture is a trailing picture.

[0071] - EDRAP pictures have a temporal sub-layer identification equal to 0.

[0072] - An EDRAP picture does not include any pictures in the same layer in its active entry in the reference picture list

[0073] (except referenceablePictures).

[0074] - Any picture located in the same layer and following the EDRAP picture in both decoding order and output order does not include in its active entry in the reference picture list any picture located in the same layer and preceding the EDRAP picture in decoding order or output order, except for referenceablePictures.

[0075] - No picture in the list referenceablePictures includes in its active entry in the reference picture list any picture that is in the same layer and is not a picture at an earlier position in the list referenceablePictures. NOTE - Thus, even if the first picture in referenceablePictures is an EDRAP picture instead of an IRAP picture, it does not include in its active entry in the reference picture list any picture from the same layer.

[0076] edrap_rap_id_minus1 plus 1 specifies the RAP picture identifier of the EDRAP picture, which is denoted as RapPicId.

[0077] Each IRAP or EDRAP picture is associated with a RapPicId value. The RapPicId value of an IRAP picture is inferred to be equal to 0. The RapPicId values ​​of any two EDRAP pictures associated with the same IRAP picture shall be different.

[0078] edrap_leading_pictures_decodable_flag equal to 1 specifies that both of the following constraints apply:

[0079] - Any picture in the same layer that follows an EDRAP picture in decoding order shall follow in output order any picture in the same layer that precedes the EDRAP picture in decoding order.

[0080] - Any picture located in the same layer and following the EDRAP picture in decoding order but preceding the EDRAP picture in output order shall not include in its active entry in the reference picture list any pictures located in the same layer and preceding the EDRAP picture in decoding order, except for referenceablePictures.

[0081] edrap_leading_pictures_decodable_flag equal to 0 does not impose such constraints.

[0082] In bitstreams conforming to this version of this specification, edrap_reserved_zero_12bits shall be equal to 0. Other values ​​of edrap_reserved_zero_12bits are reserved for use by ITU-T | ISO / IEC. A decoder shall ignore the value of edrap_reserved_zero_12bits.

[0083] edrap_num_ref_rap_pics_minus1 plus 1 indicates the number of IRAP or EDRAP pictures that are located within the same CLVS as the EDRAP picture and that can be included in the active entry of the reference picture list of the EDRAP picture.

[0084] edrap_ref_rap_id[i] indicates the RapPicId of the ith RAP picture that may be included in the active entry of the reference picture list of the EDRAP picture. The ith RAP picture shall be an IRAP picture associated with the current EDRAP picture or an EDRAP picture associated with an IRAP picture like the current EDRAP picture.

[0085] 2.5.3 EDRAP sample groups and associated external stream track references

[0086] An amendment to the ISOBMFF standard is under development. The draft specification for this amendment is included in

[14] , including the specification of EDRAP sample point groups and the associated external flow orbit references.

[0087] The specifications of these two ISOBMFF features are as follows.

[0088] 3.2 Abbreviations

[0089] EDRAP extension relies on random access points

[0090] 8.3.3.4 Associated external stream track reference

[0091] A track reference of type "aest" (standing for "associated external stream track") may be included in a video track, thereby referencing the associated video track.

[0092] When a video track has a track reference of type 'aest', the following applies:

[0093] - A video track shall have at least one sample containing an EDRAP picture.

[0094] - For each sample sampleA in a video track containing an EDRAP picture, there shall be one and only one sample sampleB in the associated video track that has the same decoding time as sampleA, and multiple consecutive samples starting from sampleB in the associated video track shall only include all pictures that are not included in the video track containing sampleA and are required when randomly accessing the EDRAP picture contained in sampleA.

[0095] Each sample in the referenced track shall be identified as a synchronization sample. The referenced track header flags shall set both track_in_movie and track_in_preview to 0.

[0096] Each referenced orbital should use the following constrained scheme:

[0097] 1) At least one sample entry type in each sample entry of a track shall be equal to "resv".

[0098] NOTE 1: When a track undergoes several transformations, "resv" need not be the sample entry type of the SampleEntry directly contained in the SampleDescriptionBox.

[0099] 2) The untransformed sample entry type is stored in the OriginalFormatBox contained in the RestrictedSchemeInfoBox.

[0100] 3) The scheme_type field in the SchemeTypeBox in the RestrictedSchemeInfoBox is equal to "aest",

[0101] Indicates that samples in a track may contain more than one codec picture.

[0102] Bit 0 of the flags field of SchemeTypeBox is equal to 0, making the value of (flags & 0x000001) equal to 0.

[0103] 10.11 Extended DRAP (EDRAP) Sample Group

[0104] 10.11.1 Definitions

[0105] This sample group is similar to the DRAP sample group specified in subclause 10.8; however, it enables more flexible cross-RAP referencing.

[0106] An EDRAP sample is a sample such that all samples following the EDRAP sample in decoding order and output order can be correctly decoded if the nearest SAP sample of type 1, 2, or 3 preceding the EDRAP sample and zero or more other identified EDRAP samples that are earlier in decoding order are available for reference.

[0107] NOTE: Similarly for DRAP points, EDRAP points can only be used in combination with SAP points of types 1, 2 and 3.

[0108] 10.11.2 Syntax

[0109]

[0110] 10.11.3 Semantics

[0111] edrap_type is a non-negative integer. When edrap_type is in the range 1 to 3, it indicates the SAP_type (as specified in Annex I) to which the EDRAP sample should correspond, provided that it does not depend on the nearest previous SAP or other EDRAP samples. Other type values ​​are reserved.

[0112] num_ref_edrap_pics indicates the number of other EDRAP samples that are earlier than the EDRAP sample in decoding order and that need to be referenced when decoding starts from the EDRAP sample in order to be able to correctly decode the EDRAP sample and all samples that follow the EDRAP sample in decoding order and output order.

[0113] reserved shall be equal to 0. The semantics of this subclause applies only to sample group description entries with reserved equal to 0. A parser shall allow and ignore sample group description entries with reserved greater than 0 when parsing this sample group.

[0114] ref_edrap_idx_delta[i] indicates the difference between the sample group index of the EDRAP sample (i.e., the index into the list of all samples in the sample group in decoding order) and the sample group index of the i-th RAP sample that is earlier than the EDRAP sample in decoding order and that needs to be referenced when decoding starts from the EDRAP sample in order to be able to correctly decode the EDRAP sample and all samples that follow the EDRAP sample in decoding order and output order. A value of 1 indicates that the i-th RAP sample is the most recent RAP sample in the sample group and precedes the EDRAP sample in decoding order, a value of 2 indicates that the i-th RAP sample is the second most recent RAP sample in the sample group and precedes the EDRAP sample in decoding order, and so on.

[0115] 2.5.4 MSR and ESR Descriptors

[0116] An amendment to the DASH standard is under development. The draft specification for this amendment is included in

[15] , including the specification of MSR and ESR descriptors for supporting EDRAP-based video streaming in DASH.

[0117] The specifications of MSR and ESR descriptors are as follows.

[0118] 3.2 Abbreviations

[0119] EDRAP Extended Dependent Random Access Point

[0120] ESR External Stream Representation

[0121] MSR mainstream representation

[0122] 5.8.5.15 MSR and ESR Descriptors

[0123] 5.8.5.15.1 Overall

[0124] An adaptation set may have an EssentialProperty descriptor with @schemeIdUri equal to urn:mpeg:dash:msr:2021. This descriptor is called an MSR descriptor. The presence of an MSR descriptor in an adaptation set indicates that each representation in the adaptation set is an MSR, which carries the Main Stream Track (MST) specified in ISO / IEC 14496 12:2021 AMD1.

[0125] An adaptation set may have an EssentialProperty descriptor with @schemeIdUri equal to urn:mpeg:dash:esr:2021. This descriptor is called an ESR descriptor. The presence of an ESR descriptor in an adaptation set indicates that each representation in the adaptation set is an ESR, which carries an External Stream Track (EST) as specified in ISO / IEC 14496 12:2021 AMD1. An ESR should only be consumed or played back with its associated MSR.

[0126] Each ESR shall be associated with an MSR via the presentation level attributes @associationId and @associationType in the MSR as follows: The @id of the associated ESR shall be referenced by the value contained in the attribute @associationId, for which the corresponding value in the attribute @associationType is equal to "aest". Each MSR shall have an associated ESR.

[0127] For MSR and ESR in relation to each other, the following applies:

[0128] - For each media sample with a specific presentation time in the ESR, there should be a corresponding media sample with the same presentation time in the MSR.

[0129] - Each media sample in the MSR that has a corresponding ESR media sample is called an EDRAP sample.

[0130] - The first byte position of each EDRAP sample in the MSR is the starting access unit index (I SAU ), if the corresponding ESR media sample is provided to the media decoder immediately before the EDRAP sample and subsequent samples in the MSR, playback of the media stream in the MSR is achieved.

[0131] - Each EDRAP sample in the MSR should be the first sample in a segment (ie, each EDRAP sample should start a segment).

[0132] - For each segment in the MSR that starts with an EDRAP sample point, there should be a segment in the ESR with the same segment start time as the MSR segment.

[0133] - The concatenation of any segment in the ESR and the corresponding segment with all subsequent segments in the MSR shall produce a consistent bitstream.

[0134] - For each MSR segment that does not start with an EDRAP sample point, there shall be no corresponding segment in the ESR with the same segment start time as the MSR segment.

[0135] 5.8.5.15.2 Example Content Preparation and Client Operation (Informative)

[0136] The following are example content preparation and client operations based on the MSR and its associated ESR.

[0137] Examples of content preparation operations are as follows:

[0138] 1) Video content is encoded into one or more representations, each with a specific spatial resolution, temporal resolution, and quality.

[0139] 2) Each representation of the video content is represented by a pair of MSR and ESR associated with each other.

[0140] 3) The MSR of the video content is included in one adaptation set. The ESR of the video content is included in another adaptation set.

[0141] The following are examples of client operations:

[0142] 1) The client obtains the MPD for media presentation, parses the MPD, selects the MSR, and determines the start presentation time of the content to be consumed.

[0143] 2) The client requests segments of the MSR, starting with the segment containing samples whose presentation time is equal to (or close enough to) the determined start presentation time.

[0144] a. If the first sample in the starting segment is an EDRAP sample, then also request the corresponding segment in the associated ESR (with the same segment start time), preferably before requesting the MSR segment. Otherwise, do not request the segment of the associated ESR.

[0145] 3) When switching to a different MSR, the client requests the segments of the MSR to which it switches (switch-to MSR), starting from the first segment whose segment start time is greater than the last requested segment of the MSR from which it switches (switch-from MSR).

[0146] a. If the first sample point in the starting segment switched to the MSR is an EDRAP sample point, the corresponding segment in the associated ESR is also requested, preferably before requesting the MSR segment. Otherwise, no segment of the associated ESR is requested.

[0147] 4) When operating continuously on the same MSR (after decoding the start segment after a seek or stream switch operation),

[0148] There is no need to request the associated ESR segment, including when requesting any subsequent segment starting with the EDRAP sample point. 3. Technical Problems Solved by the Disclosed Technical Solution

[0149] DASH supports EDRAP-based video streaming through the specifications of MSR and ESR. However, there are the following problems: 1) It is specified that each EDRAP sample in the MSR should be the first sample in the segment (i.e., each EDRAP sample should start a segment). Therefore, it is not allowed that the EDRAP sample in the MSR does not start a segment, and sub-segment-based EDRAP streaming is not supported, and configurations such as segments starting with IRAP samples and sub-segments starting with EDRAP samples are not allowed. Given the length of the segment, sub-segment-based streaming operations allow the streaming process to be controlled at a finer granularity by requesting media data at a finer granularity.

[0150] 2) When an EDRAP sample in an MSR is allowed not to start a segment, and when it starts a subsegment that is not the first subsegment in a segment, there is no requirement that a corresponding segment or subsegment exists in the associated ESR.

[0151] 3) When it is allowed that an EDRAP sample in an MSR does not start a segment, there is a lack of a requirement that any segment in an ESR and the concatenation of the corresponding MSR segment or subsegment with all subsequent MSR segments or subsegments shall produce a conforming bitstream. 4) When it is allowed that an EDRAP sample in an MSR does not start a segment, there is a lack of a requirement that for each MSR segment or subsegment that does not start with an EDRAP sample, there shall not be a corresponding ESR segment with the same earliest presentation time as the MSR segment or subsegment.

[0152] 5) When the EDRAP sample in the MSR is allowed not to start a segment, the example streaming operation based on the sub-segment starting with the EDRAP sample is missing.

[0153] 5. List of solutions and implementation examples

[0154] This article discloses a mechanism that allows EDRAP to support various video stream functions without generating errors. As mentioned above, EDRAP pictures are access points to bitstreams. EDRAP pictures can be sent using less data than IRAP pictures, but EDRAP pictures rely on IRAP pictures (e.g., IDR pictures) and / or other EDRAP pictures in external bitstreams. Therefore, only when corresponding IRAP and / or EDRAP pictures have been obtained from external bitstreams, a portion of the main bitstream that starts with an EDRAP picture is decoded. By ensuring that corresponding IRAP and / or EDRAP pictures with the same earliest presentation time exist in the external bitstream, the present disclosure allows the segments and sub-segments of the main bitstream to be initialized by EDRAP pictures. In this way, the segments and / or sub-segments in the main bitstream are guaranteed to be decodable. Therefore, adding these requirements ensures that the bitstream complies with the standard, is always decodable, and supports starting the stream from both the segments and sub-segments of the main bitstream. In addition, errors are avoided by requiring that any main bitstream EDRAP and corresponding external bitstream picture can be linked together with subsequent EDRAP pictures in the main bitstream while still being fully decodable (e.g., producing a consistent bitstream). For simplicity, the external bitstream only includes pictures at presentation times corresponding to EDRAP pictures in the main bitstream. When there is no EDRAP picture at a presentation time in the main bitstream, there should be no corresponding picture at the same presentation time in the external bitstream. Specific mechanisms for starting streams (e.g., from the client's perspective) from both segments and sub-segments using the main bitstream and the external bitstream are also disclosed. Various solutions to these and other problems are mentioned below.

[0155] In order to solve the above problems, the methods summarized as follows are disclosed. Each aspect should be regarded as an example to explain the general concept and should not be interpreted narrowly. In addition, these examples can be applied individually or combined in any way.

[0156] 1) To solve the first problem, the EDRAP sample point in the MSR is allowed not to start a segment.

[0157] a. In one example, it is specified that each EDRAP sample in the MSR should be the first sample in a segment or subsegment (ie, each EDRAP sample should start a segment or subsegment).

[0158] 2) To solve the second problem, it is specified that for each segment or subsegment in an MSR starting with an EDRAP sample point, there should be a segment in the associated ESR with the same earliest presentation time as the MSR segment or subsegment.

[0159] a. In one example, it may additionally be specified that the ESR has only segments and no subsegments, and each sample point in the ESR is in its own segment.

[0160] b. Alternatively, ESRs are allowed to have subsegments, and it is specified that for each segment or subsegment in an MSR starting with an EDRAP sample point, there should be a segment or subsegment in the associated ESR that has the same earliest presentation time as the MSR segment or subsegment.

[0161] 3) To address the third issue, it is specified that the concatenation of any segment in an ESR and the corresponding MSR segment or sub-segment (i.e., the segment or sub-segment in the associated MSR and having the same earliest presentation time as the ESR segment) with all subsequent MSR segments or sub-segments should produce a consistent bitstream.

[0162] 4) To address the fourth issue, it is specified that for each MSR segment or subsegment that does not start with an EDRAP sample point, there should not be a corresponding ESR segment with the same earliest presentation time as the MSR segment or subsegment.

[0163] 5) To solve the fifth problem, one or more of the following example stream operations are specified:

[0164] a. The client obtains the MPD for media presentation, parses the MPD, and selects the MSR.

[0165] b. When initiating a session or performing a seek, the client determines the starting presentation time of the content to be consumed and requests a segment or subsegment of the MSR starting with SAP and containing a presentation time equal to (or earlier than but close enough to)

[0166] The segment or sub-segment starts at the sample point of the determined start presentation time. In order to request a sub-segment in a segment, the segment index is requested in advance to obtain the information of the sub-segment, and a partial HTTP GET request is used.

[0167] i. If there is a segment in the associated ESR with the same earliest presentation time as the starting MSR segment or sub-segment, that ESR segment is also requested, preferably before requesting the starting MSR segment or sub-segment.

[0168] Otherwise, the segment of the associated ESR is not requested.

[0169] c. When switching to a different MSR, the client requests segments or subsegments of the switched-to MSR, starting with the first segment or subsegment whose earliest presentation time is greater than the last requested segment or subsegment of the switch-from MSR.

[0170] i. If there is a segment in the associated ESR with the same earliest presentation time as the starting segment or sub-segment of the switched-to MSR, then that ESR segment is also requested, preferably before requesting the starting segment or sub-segment of the switched-to MSR. Otherwise, the segment of the associated ESR is not requested.

[0171] d. When subsequent segments or sub-segments of an MSR are continuously requested and consumed after session initialization, seeking, or stream switching, there is no need to request segments of the associated ESR, including when requesting any subsequent MSR segments or sub-segments starting with an EDRAP sample point.

[0172] 6. Examples

[0173] The following are some example embodiments of all the public items and most of their sub-items summarized above in Section 4. These embodiments are applicable to DASH. The changes are marked relative to the design text in Section 2.4.4. Most of the relevant parts that have been added or modified are shown in bold, while some deleted parts are shown in italic bold. There may be some other changes that are editorial in nature and are therefore not highlighted.

[0174] 3.2 Abbreviations

[0175] EDRAP Extended Dependent Random Access Point

[0176] ESR External Stream Representation

[0177] MSR mainstream representation

[0178] 5.8.5.15 MSR and ESR Descriptors

[0179] 5.8.5.15.1 Overall

[0180] An adaptation set may have an EssentialProperty descriptor with @schemeIdUri equal to urn:mpeg:dash:msr:2022. This descriptor is called an MSR descriptor. The presence of an MSR descriptor in an adaptation set indicates that each representation in the adaptation set is an MSR that carries a video track with a track reference of type "aest" as specified in ISO / IEC 14496 12:2021AMD1.

[0181] An adaptation set may have an EssentialProperty descriptor with @schemeIdUri equal to urn:mpeg:dash:esr:2022. This descriptor is called an ESR descriptor. The presence of an ESR descriptor in an adaptation set indicates that each representation in the adaptation set is an ESR, which carries video tracks referenced by a track reference of type "aest" as specified in ISO / IEC 14496 12:2021AMD1. An ESR shall only be consumed or played back together with its associated MSR.

[0182] Each ESR shall be associated with an MSR via the presentation level attributes @associationId and @associationType in the MSR as follows: The @id of the associated ESR shall be referenced by the value contained in the attribute @associationId, for which the corresponding value in the attribute @associationType is equal to "aest". Each MSR shall have an associated ESR.

[0183] For MSR and ESR in relation to each other, the following applies:

[0184] - For each media sample with a specific presentation time in the ESR, there should be a corresponding media sample with the same presentation time in the MSR.

[0185] - Each media sample in the MSR that has a corresponding ESR media sample is called an EDRAP sample.

[0186] -The first byte position of each EDRAP sample in the MSR is the I of SAP SAU If the corresponding ESR media sample is provided to the media decoder immediately before the EDRAP sample and subsequent samples in the MSR, playback of the media stream in the MSR is achieved.

[0187] - Each EDRAP sample in the MSR should be the first sample in a segment or subsegment (ie, each EDRAP sample should start a segment or subsegment).

[0188] - For each segment or sub-segment in the MSR that starts with an EDRAP sample point, there should be a segment in the ESR with the same earliest presentation time as the MSR segment or sub-segment.

[0189] - The concatenation of any segment in an ESR and the corresponding MSR segment or sub-segment (i.e., an MSR segment or sub-segment having the same earliest presentation time as the ESR segment) with all subsequent MSR segments or sub-segments shall produce a consistent bitstream.

[0190] - For each MSR segment or sub-segment that does not start with an EDRAP sample point, there shall be no corresponding ESR segment with the same earliest presentation time as the MSR segment or sub-segment.

[0191] 5.8.5.15.2 Example Content Preparation and Client Operation (Informative)

[0192] The following are example content preparation and client operations based on the MSR and its associated ESR.

[0193] Examples of content preparation operations are as follows:

[0194] 1) Video content is encoded into one or more representations, each with a specific spatial resolution, temporal resolution, and quality.

[0195] 2) Each representation of the video content is represented by a pair of MSR and ESR associated with each other.

[0196] 3) The MSR of the video content is included in one adaptation set. The ESR of the video content is included in another adaptation set.

[0197] The following are examples of client operations:

[0198] 1) The client obtains the MPD for media presentation, parses the MPD, and selects the MSR.

[0199] 2) When initiating a session or performing a seek, the client determines the start presentation time of the content to be consumed, and requests segments or sub-segments of the MSR, starting with the segment or sub-segment that starts with SAP and contains a sample whose presentation time is equal to (or earlier than but close enough to) the determined start presentation time. In order to request a sub-segment in a segment, the segment index is requested in advance to obtain the information of the sub-segment, and a partial HTTP GET request is used.

[0200] a. If there is a segment in the associated ESR with the same earliest presentation time as the starting MSR segment or sub-segment, then request that ESR segment as well, preferably before requesting the starting MSR segment or sub-segment. Otherwise, do not request the segments of the associated ESR.

[0201] 3) When switching to a different MSR, the client requests segments or subsegments of the MSR to switch to, starting with the first segment or subsegment whose earliest presentation time is greater than the last requested segment or subsegment of the MSR from which the switch started.

[0202] a. If there is a segment in the associated ESR with the same earliest presentation time as the starting segment or sub-segment of the switched-to MSR, then that ESR segment is also requested, preferably before requesting the starting segment or sub-segment in the switched-to MSR. Otherwise, the segment of the associated ESR is not requested.

[0203] 4) When subsequent segments or sub-segments of an MSR are continuously requested and consumed after session initialization, seeking, or stream switching, there is no need to request segments of the associated ESR, including when requesting any subsequent MSR segments or sub-segments starting with an EDRAP sample point.

[0204] 7. References

[0205] [1]ITU-T and ISO / IEC,“High efficiency video coding”,Rec.ITU-T H.265|ISO / IEC23008-2(in force edition).

[0207] [2]J.Chen,E.Alshina,G.J.Sullivan,J.-R.Ohm,J.Boyce,“Algorithmdescription ofJoint Exploration Test Model 7(JEM7),”JVET-G1001,Aug.2017.

[0208] [3]Rec.ITU-T H.266|ISO / IEC 23090-3,“Versatile Video Coding”,2020.

[0209] [4]B.Bross,J.Chen,S.Liu,Y.-K.Wang(editors),“Versatile Video Coding(Draft 10),”JVET-S2001.

[0211] [5]Rec.ITU-T Rec.H.274|ISO / IEC 23002-7,“Versatile SupplementalEnhancementInformation Messages for Coded Video Bitstreams”,2020.

[0212] [6]J.Boyce,V.Drugeon,G.J.Sullivan,Y.-K.Wang(editors),“Versatilesupplementalenhancement information messages for coded video bitstreams(Draft5),”JVET-S2007.

[0214] [7]ISO / IEC 14496-12:"Information technology—Coding of audio-visualobjects—Part12:ISO base media file format".

[0216] [8]ISO / IEC 23009-1:"Information technology—Dynamic adaptivestreaming overHTTP(DASH)—Part 1:Media presentation description and segmentformats".The

[0217] 4th edition text of the DASH standard specification can be found inMPEG inputdocument m52458.

[0218] [9]ISO / IEC 14496-15:"Information technology—Coding of audio-visualobjects—Part

[0219] 15:Carriage of network abstraction layer(NAL)unit structured video inthe ISO basemedia file format".

[0220]

[10] ISO / IEC 23008-12:"Information technology—High efficiency codingand mediadelivery in heterogeneous environments—Part 12:Image File Format".

[0221]

[11] ISO / IEC JTC 1 / SC 29 / WG 03output document N0035,"Potentialimprovements onCarriage of VVC and EVC in ISOBMFF",Nov.2020.

[0222]

[12] ISO / IEC JTC 1 / SC 29 / WG 03output document N0038,"Informationtechnology—

[0223] High efficiency coding and media delivery in heterogeneousenvironments—Part 12:

[0224] Image File Format—Amendment 3: Support for VVC, EVC, slideshows and other improvements (CD stage)", Nov. 2020.

[0225]

[13] J.Boyce, GJSullivan, Y.-K.Wang (editors), "Additional SEI messages for VSEI (Draft 6)," JVET-Y2006.

[0227]

[14] ISO / IEC JTC 1 / SC 29 / WG 03output document N0471,"Text of CDAM ISO / IEC

[0228] 14496-12:2021AMD 1Improved brand documentation and other improvements", Feb. 2022.

[0230]

[15] ISO / IEC JTC 1 / SC 29 / WG 03output document N0486, "WD of ISO / IEC23009-1 5thedition AMD2 EDRAP streaming and other extensions", Jan.2022.

[0231] Figure 6 4000 is a block diagram illustrating an example video processing system 4000 in which various techniques disclosed herein may be implemented. Various embodiments may include some or all of the components of system 4000. System 4000 may include an input 4002 for receiving video content. The video content may be received in a raw or uncompressed format, such as 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. Input 4002 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interfaces include wired interfaces such as Ethernet, a passive optical network (PON), and wireless interfaces such as Wi-Fi or a cellular interface.

[0232] System 4000 may include a codec component 4004 that can implement various codecs or encoding methods described in this document. Codec component 4004 can reduce the average bit rate of the video from input 4002 to the output of codec component 4004 to generate a codec representation of the video. Codec technology is therefore sometimes referred to as video compression or video transcoding technology. The output of codec component 4004 can be stored or sent via a communication connection as represented by component 4006. The bitstream (or codec) representation of the storage or communication transmission of the video received at input 4002 can be used by component 4008 to generate pixel values ​​or transmit to the displayable video of display interface 4010. The process of generating user-visible video from bitstream representation is sometimes referred to as video decompression. In addition, although some video processing operations are referred to as "codec" operations or tools, it will be understood that codec tools or operations are used at the encoder, and the corresponding decoding tools or operations of the inverse codec results will be performed by the decoder.

[0233] Examples of peripheral bus interfaces or display interfaces may include Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), DisplayPort, etc. Examples of storage interfaces include Serial Advanced Technology Attachment (SATA), Peripheral Component Interconnect (PCI), Integrated Drive Electronics (IDE) interface, etc. The technology described in this document may be embodied in various electronic devices, such as mobile phones, laptops, smart phones, or other devices capable of performing digital data processing and / or video display.

[0234] Figure 7 4100. The apparatus 4100 may be used to implement one or more methods described herein. The apparatus 4100 may be embodied in a smartphone, a tablet computer, a computer, an Internet of Things (IoT) receiver, etc. The apparatus 4100 may include one or more processors 4102, one or more memories 4104, and a video processing circuit 4106. The processor(s) 4102 may be configured to implement one or more methods described in this document. The memory(s) 4104 may be used to store data and code for implementing the methods and techniques described herein. The video processing circuit 4106 may be used to implement some of the techniques described in this document in a hardware circuit system. In some embodiments, the video processing circuit 4106 may be at least partially included in a processor 4102 (e.g., a graphics coprocessor).

[0235] Figure 84200 is a flow chart of an example method 4200 for video processing. The method 4200 includes, at step 4202, an EDRAP sample point in an MSR is not positioned as the beginning of a segment of a media data file. At step 4204, a conversion is performed between visual media data and a media data file based on the EDRAP sample point.

[0236] It should be noted that the method 4200 may be implemented in an apparatus for processing video data, the apparatus comprising a processor and a non-transitory memory having instructions thereon, such as the video encoder 4400, the video decoder 4500, and / or the encoder 4600. In this case, the instructions, when executed by the processor, cause the processor to perform the method 4200. In addition, the method 4200 may be performed by a non-transitory computer-readable medium including a computer program product for use by a video codec device. The computer program product includes computer executable instructions stored on a non-transitory computer-readable medium, such that when executed by the processor, the video codec device performs the method 4200.

[0237] Fig. 9 43 is a block diagram illustrating an example video codec system 4300 that can utilize the techniques of the present disclosure. The video codec system 4300 may include a source device 4310 and a target device 4320. The source device 4310 generates encoded video data, where the source device 4310 may be referred to as a video encoding device. The target device 4320 may decode the encoded video data generated by the source device 4310, where the target device 4320 may be referred to as a video decoding device.

[0238] Source device 4310 may include video source 4312, video encoder 4314 and input / output (I / O) interface 4316. Video source 4312 may include a source, such as a video capture device, an interface for receiving video data from a video content provider, and / or a computer graphics system for generating video data, or a combination of these sources. Video data may include one or more pictures. Video encoder 4314 encodes video data from video source 4312 to generate a bit stream. The bit stream may include a bit sequence that forms a codec representation of video data. The bit stream may include a codec picture and related data. The codec picture is a codec representation of a picture. Related data may include sequence parameter sets, picture parameter sets and other syntax structures. I / O interface 4316 may include a modulator / demodulator (modem) and / or a transmitter. Encoded video data may be directly sent to target device 4320 via network 4330 via I / O interface 4316. Encoded video data may also be stored on storage medium / server 4340 for access by target device 4320.

[0239] The target device 4320 may include an I / O interface 4326, a video decoder 4324, and a display device 4322. The I / O interface 4326 may include a receiver and / or a modem. The I / O interface 4326 may obtain coded video data from the source device 4310 or the storage medium / server 4340. The video decoder 4324 may decode the coded video data. The display device 4322 may display the decoded video data to the user. The display device 4322 may be integrated with the target device 4320, or may be external to the target device 4320 that may be configured to interface with an external display device.

[0240] The video encoder 4314 and the video decoder 4324 may operate according to a video compression standard, such as the High Efficiency Video Codec (HEVC) standard, the Versatile Video Codec (VVC) standard, and other current and / or additional standards.

[0241] Fig.10 is a block diagram showing an example of a video encoder 4400, which may be Fig. 9 4300. Video encoder 4400 may be configured to perform any or all of the techniques of the present disclosure. Video encoder 4400 includes multiple functional components. The techniques described in this disclosure may be shared between various components of video encoder 4400. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.

[0242] The functional components of the video encoder 4400 may include a segmentation unit 4401, a prediction unit 4402 (which may include a mode selection unit 4403, a motion estimation unit 4404, a motion compensation unit 4405 and an intra-frame prediction unit 4406), a residual generation unit 4407, a transform processing unit 4408, a quantization unit 4409, an inverse quantization unit 4410, an inverse transform unit 4411, a reconstruction unit 4412, a buffer 4413 and an entropy coding and decoding unit 4414.

[0243] In other examples, the video encoder 4400 may include more, fewer, or different functional components. In an example, the prediction unit 4402 may include an intra-block copy (IBC) unit. The IBC unit may perform prediction in IBC mode, where at least one reference picture is a picture in which the current video block is located.

[0244] Furthermore, some components, such as the motion estimation unit 4404 and the motion compensation unit 4405 , may be highly integrated, but are represented separately in the example of the video encoder 4400 for purposes of explanation.

[0245] The segmentation unit 4401 may segment the picture into one or more video blocks. The video encoder 4400 and the video decoder 4500 may support various video block sizes.

[0246] The mode selection unit 4403 may select one of the coding modes (e.g., intra or inter) based on the error result, and provide the resulting intra-coded block or inter-coded block to the residual generation unit 4407 to generate residual block data, and to the reconstruction unit 4412 to reconstruct the coded block for use as a reference picture. In some examples, the mode selection unit 4403 may select a combination of intra and inter prediction modes (CIIP), where the prediction is based on an inter prediction signal and an intra prediction signal. In the case of inter prediction, the mode selection unit 4403 may also select a resolution of the motion vector of the block (e.g., sub-pixel or integer pixel precision).

[0247] In order to perform inter-frame prediction on the current video block, the motion estimation unit 4404 may generate motion information of the current video block by comparing the current video block with one or more reference frames from the buffer 4413. The motion compensation unit 4405 may determine a predicted video block of the current video block based on the motion information and decoded samples of pictures from the buffer 4413 other than the picture associated with the current video block.

[0248] The motion estimation unit 4404 and the motion compensation unit 4405 may perform different operations on the current video block, eg, depending on whether the current video block is in an I slice, a P slice, or a B slice.

[0249] In some examples, the motion estimation unit 4404 may perform unidirectional prediction on the current video block, and the motion estimation unit 4404 may search the reference picture of list 0 or list 1 for the reference video block of the current video block. The motion estimation unit 4404 may then generate a reference index indicating the reference picture in list 0 or list 1, the reference index including the reference video block and a motion vector indicating a spatial displacement between the current video block and the reference video block. The motion estimation unit 4404 may output the reference index, the prediction direction indicator, and the motion vector as the motion information of the current video block. The motion compensation unit 4405 may generate a predicted video block of the current block based on the reference video block indicated by the motion information of the current video block.

[0250] In other examples, the motion estimation unit 4404 may perform bidirectional prediction on the current video block, and the motion estimation unit 4404 may search for a reference video block of the current video block in the reference pictures in list 0, and may also search for another reference video block of the current video block in list 1. The motion estimation unit 4404 may then generate a reference index indicating the reference pictures in list 0 and list 1 containing the reference video block and a motion vector indicating a spatial displacement between the reference video block and the current video block. The motion estimation unit 4404 may output the reference index and the motion vector of the current video block as the motion information of the current video block. The motion compensation unit 4405 may generate a predicted video block of the current video block based on the reference video block indicated by the motion information of the current video block.

[0251] In some examples, motion estimation unit 4404 may output a complete set of motion information for use in a decoding process by a decoder. In some examples, motion estimation unit 4404 may not output a complete set of motion information for the current video. Instead, motion estimation unit 4404 may reference motion information of another video block to signal motion information of the current video block. For example, motion estimation unit 4404 may determine that the motion information of the current video block is sufficiently similar to the motion information of an adjacent video block.

[0252] In one example, the motion estimation unit 4404 may indicate a value in a syntax structure associated with the current video block that indicates to the video decoder 4500 that the current video block has the same motion information as another video block.

[0253] In another example, the motion estimation unit 4404 may identify another video block and a motion vector difference (MVD) in a syntax structure associated with the current video block. The motion vector difference indicates the difference between the motion vector of the current video block and the motion vector of the indicated video block. The video decoder 4500 may use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.

[0254] As discussed above, the video encoder 4400 may predictively signal motion vectors. Two examples of predictive signaling techniques that may be implemented by the video encoder 4400 include Advanced Motion Vector Prediction (AMVP) and Merge mode signaling.

[0255] The intra prediction unit 4406 may perform intra prediction on the current video block. When the intra prediction unit 4406 performs intra prediction on the current video block, the intra prediction unit 4406 may generate prediction data for the current video block based on decoded samples of other video blocks in the same picture. The prediction data for the current video block may include a predicted video block and various syntax elements.

[0256] The residual generation unit 4407 may generate residual data of the current video block by subtracting the predicted video block(s) of the current video block from the current video block. The residual data of the current video block may include residual video blocks corresponding to different sample components of the samples in the current video block.

[0257] In other examples, such as in skip mode, there may be no residual data for the current video block and the residual generation unit 4407 may not perform a subtraction operation.

[0258] The transform processing unit 4408 may generate one or more transform coefficient video blocks for the current video block by applying one or more transforms to the residual video block associated with the current video block.

[0259] After the transform processing unit 4408 generates a transform coefficient video block associated with the current video block, the quantization unit 4409 may quantize the transform coefficient video block associated with the current video block based on one or more quantization parameter (QP) values ​​associated with the current video block.

[0260] The inverse quantization unit 4410 and the inverse transform unit 4411 may apply inverse quantization and inverse transform to the transform coefficient video block, respectively, to reconstruct the residual video block from the transform coefficient video block. The reconstruction unit 4412 may add the reconstructed residual video block to the corresponding samples of one or more predicted video blocks generated by the prediction unit 4402 to generate a reconstructed video block associated with the current block for storage in the buffer 4413.

[0261] After the reconstruction unit 4412 reconstructs the video block, a loop filtering operation may be performed to reduce video blocking effects in the video block.

[0262] The entropy coding unit 4414 may receive data from other functional components of the video encoder 4400. When the entropy coding unit 4414 receives the data, the entropy coding unit 4414 may perform one or more entropy coding operations to generate entropy coded data and output a bitstream including the entropy coded data.

[0263] Fig.11 is a block diagram showing an example of a video decoder 4500, which may be Fig. 9 4300. Video decoder 4500 may be configured to perform any or all of the techniques of the present disclosure. In the example shown, video decoder 4500 includes multiple functional components. The techniques described in this disclosure may be shared between various components of video decoder 4500. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.

[0264] In the example shown, the video decoder 4500 includes an entropy decoding unit 4501, a motion compensation unit 4502, an intra prediction unit 4503, an inverse quantization unit 4504, an inverse transform unit 4505, a reconstruction unit 4506, and a buffer 4507. In some examples, the video decoder 4500 may perform a decoding process that is generally the reverse of the encoding pass described for the video encoder 4400.

[0265] The entropy decoding unit 4501 may retrieve a coded bitstream. The coded bitstream may include entropy-coded video data (e.g., coded blocks of video data). The entropy decoding unit 4501 may decode the entropy-coded video data, and from the entropy-decoded video data, the motion compensation unit 4502 may determine motion information including motion vectors, motion vector precision, reference picture list indexes, and other motion information. The motion compensation unit 4502 may determine such information, for example, by performing AMVP and Merge modes.

[0266] The motion compensation unit 4502 may generate a motion compensated block, and interpolation may be performed based on an interpolation filter. An identifier of an interpolation filter to be used with sub-pixel precision may be included in a syntax element.

[0267] The motion compensation unit 4502 may calculate interpolation of sub-integer pixels of a reference block using an interpolation filter as used by the video encoder 4400 during encoding of the video block. The motion compensation unit 4502 may determine the interpolation filter used by the video encoder 4400 based on received syntax information and use the interpolation filter to generate a prediction block.

[0268] The motion compensation unit 4502 can use some syntax information to determine the size of the blocks used to encode (multiple) frames and / or (multiple) slices of the encoded video sequence, partitioning information describing how each macroblock of the pictures of the encoded video sequence is partitioned, a mode indicating how each partition is encoded, one or more reference frames (and reference frame lists) for each inter-frame codec block, and other information used to decode the encoded video sequence.

[0269] The intra prediction unit 4503 may form a prediction block from spatially adjacent blocks using, for example, an intra prediction mode received in the bitstream. The inverse quantization unit 4504 inversely quantizes, i.e., dequantizes, the quantized video block coefficients provided in the bitstream and decoded by the entropy decoding unit 4501. The inverse transform unit 4505 applies an inverse transform.

[0270] The reconstruction unit 4506 may add the residual block to the corresponding prediction block generated by the motion compensation unit 4502 or the intra prediction unit 4503 to form a decoded block. If necessary, a deblocking filter may also be applied to filter the decoded block to remove block artifacts. The decoded video block is then stored in a buffer 4507 to provide a reference block for subsequent motion compensation / intra prediction, and also to generate a decoded video for presentation on a display device.

[0271] Fig.12 is a schematic diagram of an example encoder 4600. The encoder 4600 is suitable for implementing VVC technology. The encoder 4600 includes three loop filters, namely a deblocking filter (DF) 4602, a sample adaptive offset (SAO) 4604, and an adaptive loop filter (ALF) 4606. Unlike the DF 4602 that uses a predefined filter, the SAO 4604 and the ALF 4606 use the original samples of the current picture to reduce the mean square error between the original samples and the reconstructed samples by adding an offset and applying a finite impulse response (FIR) filter, respectively, using the auxiliary information of the codec to signal the offset and filter coefficients. The ALF 4606 is located at the last processing stage of each picture and can be regarded as a tool that attempts to capture and repair artifacts created by previous stages.

[0272] The encoder 4600 also includes an intra prediction component 4608 and a motion estimation / motion compensation (ME / MC) component 4610 configured to receive an input video. The intra prediction component 4608 is configured to perform intra prediction, and the ME / MC component 4610 is configured to perform inter prediction using a reference picture obtained from a reference picture buffer 4612. The residual block from the inter prediction or intra prediction is fed to the transform (T) component 4614 and the quantization (Q) component 4616 to generate quantized residual transform coefficients, which are fed to the entropy coding component 4618. The entropy coding component 4618 performs entropy coding and decoding on the prediction result and the quantized transform coefficients and sends them to a video decoder (not shown). The quantization component output from the quantization component 4616 can be fed to the inverse quantization (IQ) component 4620, the inverse transform component 4622 and the reconstruction (REC) component 4624. The REC component 4624 is capable of outputting images to the DF 4602 , SAO 4604 , and ALF 4606 for filtering before these pictures are stored in the reference picture buffer 4612 .

[0273] Fig.134700 is a flow chart of an example method 4700 for video processing. In step 4702, a conversion is performed between visual media data and a media data file based on one or more EDRAP samples. Each EDRAP sample should be the first sample in a segment or subsegment of an MSR. For example, it is required that each EDRAP sample is the first sample in a segment or subsegment of an MSR to produce a consistent bitstream. For example, one of the EDRAP samples can start a segment, one of the EDRAP samples can start a subsegment, or both.

[0274] In some examples, for each segment or subsegment in the MSR that starts with one of the EDRAP samples, the external stream representation (ESR) segment should have the same earliest presentation time as the segment or subsegment in the MSR. For example, the conversion at step 4702 can include concatenation of the ESR segment and the segment or subsegment in the MSR with all subsequent MSR segments or subsegments, which produces a consistent bitstream. In some examples, for each MSR segment or subsegment that does not start with an EDRAP sample, there is no corresponding ESR segment that has the same earliest presentation time as each MSR segment or subsegment.

[0275] In some examples, method 4700 is performed as part of a client operation on a client. In such an example, the client can obtain an MPD for a media presentation, parse the MPD, and select an MSR as part of the conversion at step 4702.

[0276] In some examples, the transition at step 4702 includes initializing a session or performing a seek. In some examples, when initializing a session or performing a seek, the client determines a start presentation time of the content to be consumed, and requests a segment or sub-segment of an MSR starting with a segment or sub-segment that starts with a SAP and contains a sample point with a presentation time equal to the determined start presentation time. In some examples, in order to request a sub-segment in a segment, a segment index is requested to obtain information of the sub-segment, and a partial HTTP GET request is used.

[0277] In some examples, when there is an ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the ESR segment is also requested before requesting the starting MSR segment or sub-segment. In some examples, when there is no ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the ESR segment is not requested.

[0278] In some examples, when switching to the switched-to MSR, the client requests segments or subsegments of the switched-to MSR starting from the first segment or subsegment of the last requested segment or subsegment of the switched-to MSR whose earliest presentation time is greater than that of the MSR from which the switching starts. For example, when there is an ESR segment with the same earliest presentation time as the starting segment or subsegment of the switched-to MSR, the ESR segment is also requested before requesting the starting segment or subsegment of the switched-to MSR. In addition, when there is no ESR segment with the same earliest presentation time as the starting segment or subsegment in the switched-to MSR, the ESR segment is not requested.

[0279] In some examples, ESR segments are not requested when seeking, stream switching, or continuously requesting and consuming subsequent segments or subsegments of an MSR after session initialization, including when requesting any subsequent MSR segments or subsegments starting with an EDRAP sample point.

[0280] In some examples, performing conversion between the visual media data and the media data file at step 4702 includes encoding the visual media data into a bitstream. In some examples, performing conversion between the visual media data and the media data file at step 4702 includes decoding the visual media data from the bitstream.

[0281] It should be noted that method 4700 may be implemented in an apparatus for processing video data, the apparatus comprising a processor and a non-transitory memory having instructions thereon, such as video encoder 4400, video decoder 4500, and / or encoder 4600. In this case, the instructions, when executed by the processor, cause the processor to perform method 4700. In addition, method 4700 may be performed by a non-transitory computer-readable medium comprising a computer program product for use by a video codec device. The computer program product comprises computer-executable instructions, wherein the computer-executable instructions are stored on a non-transitory computer-readable medium, such that when executed by the processor, the video codec device performs method 4700.

[0282] A list of solutions preferred by some examples is provided next.

[0283] The following solutions illustrate examples of the techniques discussed herein.

[0284] The following solution illustrates an example embodiment of the technique discussed in the previous section (eg, item 1).

[0285] 1. A method for processing video data (e.g., Figure 8The method 4200 depicted in the claims includes: determining (4202) that an extended dependent random access point (EDRAP) sample in a mainstream representation (MSR) is not positioned as the beginning of a segment of a media data file; and performing (4204) conversion between visual media data and the media data file based on the EDRAP sample.

[0286] 2. The method according to solution 1, wherein the EDRAP sample is the first sample in the subsegment of the media data file.

[0287] The following solution illustrates an example embodiment of the technique discussed in the previous section (eg, item 2).

[0288] 3. A method for processing video data, comprising: determining that for each segment or subsegment in a main stream representation (MSR) that starts with an extended dependent random access point (EDRAP) sample, a segment in an associated external stream representation (ESR) has the same earliest presentation time as the segment or subsegment in the MSR; and performing conversion between visual media data and a media data file based on the EDRAP sample.

[0289] 4. The method according to solution 3, wherein the ESR has only segments without sub-segments, and wherein each sample point in the ESR has a corresponding segment.

[0290] 5. A method according to solution 3, wherein the ESR has subsegments, wherein for each segment of the subsegment in the MSR starting with an EDRAP sample point, the segment or subsegment in the ESR has the same earliest presentation time as the segment or subsegment in the MSR.

[0291] The following solution illustrates an example implementation of the technique discussed in the previous section (eg, item 3).

[0292] 6. A method for processing video data, comprising: determining that any segment in an external stream representation (ESR) and a corresponding main stream representation (MSR) segment or a corresponding MSR subsegment and the concatenation of all subsequent MSR segments or MSR subsegments should produce a consistent bitstream; and performing conversion between visual media data and media data files based on the ESR and the MSR segments or MSR subsegments.

[0293] The following solution illustrates an example implementation of the technique discussed in the previous section (eg, item 4).

[0294] 7. A method for processing video data, comprising: determining that for each main stream representation (MSR) segment or sub-segment that does not start with an EDRAP sample point, there should be no corresponding external stream representation (ESR) segment with the same earliest presentation time as the MSR segment or sub-segment; and performing conversion between visual media data and a media data file based on the ESR segments and the MSR segments or sub-segments.

[0295] The following solution illustrates an example embodiment of the technique discussed in the previous section (eg, item 5).

[0296] 8. A method for processing video data, comprising: determining a start presentation time; obtaining a mainstream representation (MSR) segment or sub-segment having a presentation time equal to the start presentation time; obtaining an external stream representation (ESR) segment having the same presentation time as the MSR segment or sub-segment; and performing conversion between visual media data and a media data file based on the ESR segment and the MSR segment or sub-segment.

[0297] 9. The method according to solution 8 further includes selecting the MSR from the MPD.

[0298] 10. The method according to any one of solutions 8-9 also includes: switching to the MSR segment or sub-segment to be switched at the switching presentation time; and obtaining an ESR segment having the same switching presentation time as the MSR segment or sub-segment.

[0299] 11. A method according to any of solutions 8-10, wherein ESR segments are not requested when MSR segments or sub-segments are continuously consumed after session initialization, seeking or stream switching.

[0300] 12. A device for processing video data, comprising: a processor; and a non-temporary memory having instructions thereon, wherein the instructions, when executed by the processor, cause the processor to execute a method according to any one of solutions 1-11.

[0301] 13. A non-transitory computer-readable medium comprising a computer program product for use by a video codec device, the computer program product comprising computer-executable instructions, wherein the computer-executable instructions are stored on the non-transitory computer-readable medium, so that when executed by a processor, the video codec device performs a method according to any one of solutions 1-11.

[0302] 14. A method, apparatus or system as described in this document.

[0303] The following solutions illustrate further examples of the techniques discussed herein.

[0304] 1. A method for processing video data, comprising: performing conversion between visual media data and a media data file based on one or more extended dependent random access point (EDRAP) samples, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR).

[0305] 2. The method according to solution 1, wherein one of the EDRAP samples is allowed to start a segment.

[0306] 3. The method according to any of solutions 1-2, wherein one of the EDRAP samples is allowed to start a subsegment and not start a segment.

[0307] 4. A method according to any of solutions 1-3, wherein, for each segment or subsegment in the MSR starting with one of the EDRAP samples, there is a segment in the external stream representation (ESR) with the same earliest presentation time as the segment or subsegment in the MSR.

[0308] 5. A method according to any one of solutions 1-4, wherein the conversion includes concatenating the corresponding segments or sub-segments in the ESR segment and the MSR with all subsequent MSR segments or sub-segments to produce a consistent bit stream.

[0309] 6. The method of solution 5, wherein the corresponding segment or sub-segment in the MSR has the same earliest presentation time as the ESR segment.

[0310] 7. A method according to any one of solutions 1-6, wherein, for each MSR segment or sub-segment that does not start with an EDRAP sample point, there is no corresponding ESR segment with the same earliest presentation time as each MSR segment or sub-segment.

[0311] 8. A method according to any one of solutions 1-7, wherein the method is performed as part of a client operation on a client.

[0312] 9. A method according to any one of Solution 8, wherein the client obtains a media presentation description (MPD) of the media presentation, parses the MPD, and selects the MSR.

[0313] 10. A method according to any one of solutions 1-9, wherein, when initializing a session or performing a seek, the client determines the start presentation time of the content to be consumed and requests a segment or subsegment of the MSR starting with a segment or subsegment of a sample point starting with a stream access point (SAP) and containing a presentation time equal to the determined start presentation time.

[0314] 11. A method according to any one of solutions 1-10, wherein, in order to request a sub-segment in a segment, a segment index is requested to obtain information of the sub-segment, and wherein a partial Hypertext Transfer Protocol (HTTP) GET request is used.

[0315] 12. A method according to any one of solutions 1-11, wherein, when there is an ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the ESR segment is also requested before requesting the starting MSR segment or sub-segment.

[0316] 13. A method according to any of solutions 1-12, wherein when there is no ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the segment of the ESR is not requested.

[0317] 14. A method according to any one of solutions 1-13, wherein, when switching to the MSR to be switched to, the client requests segments or subsegments of the MSR to be switched to starting from the first segment or subsegment whose earliest presentation time is greater than the last requested segment or subsegment of the MSR from which the switching starts.

[0318] 15. A method according to any one of solutions 1-14, wherein, when there is an ESR segment with the same earliest presentation time as the starting segment or sub-segment in the MSR switched to, the ESR segment is also requested before requesting the starting segment or sub-segment in the MSR switched to.

[0319] 16. A method according to any one of solutions 1-15, wherein when there is no ESR segment with the same earliest presentation time as the starting segment or sub-segment in the switched to MSR, the ESR segment is not requested.

[0320] 17. A method according to any one of solutions 1-16, wherein the ESR segment is not requested when searching, stream switching, or continuously requesting and consuming subsequent segments or subsegments of the MSR after session initialization, including when requesting any subsequent MSR segment or subsegment starting with an EDRAP sample point.

[0321] 18. The method of any one of solutions 1-17, wherein performing conversion between the visual media data and the media data file comprises encoding the visual media data into the media data file.

[0322] 19. According to the method of any one of solutions 1-17, performing conversion between visual media data and a media data file includes decoding the visual media data from the media data file.

[0323] 20. A device for processing video data, comprising: a processor; and a non-temporary memory having instructions thereon, wherein the instructions, when executed by the processor, cause the processor to execute a method according to any one of solutions 1-19.

[0324] 21. A non-transitory computer-readable medium comprising a computer program product for use by a video codec device, the computer program product comprising computer-executable instructions, wherein the computer-executable instructions are stored on the non-transitory computer-readable medium, so that when executed by a processor, the video codec device performs a method according to any one of solutions 1-19.

[0325] 22. A non-transitory computer-readable recording medium storing a bitstream of a video generated by a method performed by a video processing device, wherein the method comprises: determining based on one or more extended dependent random access point (EDRAP) samples to perform conversion between visual media data and a media data file, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR); and generating a bitstream based on the determination.

[0326] 23. A method for storing a bitstream of a video, comprising: determining based on one or more extended dependent random access point (EDRAP) samples to perform a conversion between visual media data and a media data file, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR); generating a bitstream based on the determination; and storing the bitstream in a non-transitory computer-readable recording medium.

[0327] 24. A method, apparatus or system as described in this document.

[0328] In the solution described herein, an encoder may comply with the format rules by generating a codec representation according to the format rules. In the solution described herein, a decoder may parse the syntax elements in the codec representation using the format rules to generate decoded video, knowing the presence and absence of the syntax elements according to the format rules.

[0329] In this document, the term "video processing" may refer to video encoding, video decoding, video compression, or video decompression. For example, during the conversion from a pixel representation of a video to a corresponding bitstream representation, a video compression algorithm may be applied, and vice versa. As defined by the syntax, the bitstream representation of the current video block may correspond, for example, to bits that are juxtaposed or interspersed in different places within the bitstream. For example, macroblocks may be encoded according to error residual values ​​of transforms and codecs and also using bits in headers and other fields in the bitstream. In addition, during conversion, the decoder may parse the bitstream based on the determination, knowing that some fields may or may not be present, as described in the above solution. Similarly, the encoder may determine whether to include or not include certain syntax fields, and generate the codec representation accordingly by including or excluding syntax fields from the codec representation.

[0330] The disclosed and other solutions, examples, embodiments, modules and functional operations described in this document can be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in this document and their structural equivalents), or in a combination of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium, which are used to be executed by a data processing device or control the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of substances that affect machine-readable propagation signals, or a combination of one or more of them. The term "data processing device" includes all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is an artificially generated signal generated to encode information for transmission to a suitable receiver device, such as a machine-generated electrical signal, an optical signal, or an electromagnetic signal.

[0331] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language (including compiled or interpreted languages), and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0332] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuits, and the apparatus can also be implemented as special purpose logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits).

[0333] Processors suitable for executing computer programs include, for example, general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or operably coupled to receive data from or transfer data to or from the one or more mass storage devices. However, a computer does not require such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and compact disk read-only memory (CD ROM) and digital versatile disk read-only memory (DVD-ROM) disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0334] Although this patent document contains many details, these details should not be interpreted as limitations on any subject matter or the scope of possible protection, but rather as descriptions of features specific to a particular embodiment of a particular technology. Certain features described in the context of a separate embodiment in this patent document may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may be described above as working in certain combinations and even initially claimed as such, one or more features from the claimed combination may be excluded from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0335] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all of the operations shown be performed, to achieve the desired results. In addition, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0336] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and shown in this patent document.

[0337] A first component is directly coupled to a second component when there is no intermediate component between the first component and the second component other than a line, a trace, or another medium. A first component is indirectly coupled to a second component when there is an intermediate component between the first component and the second component other than a line, a trace, or another medium. The term "coupled" and its variations include direct coupling and indirect coupling. The use of the term "approximately" is meant to include a range of ±10% of the subsequent numerical value unless otherwise stated.

[0338] Although several embodiments have been provided in the present 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 the present disclosure. The present examples are considered to be illustrative rather than restrictive, and are not intended to be limited to the details given herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

[0339] In addition, without departing from the scope of the present disclosure, the techniques, systems, subsystems and methods described and illustrated as discrete or separate in various embodiments may be combined or integrated with other systems, modules, techniques or methods. Other items shown or discussed as coupled may be directly connected, or may be indirectly coupled or communicated through some interface, device or intermediate component, whether electrically, mechanically or otherwise. Other examples of changes, substitutions and modifications may be determined by those skilled in the art and may be made without departing from the spirit and scope of the present disclosure.

Claims

1. A method for processing video data, comprising: performing conversion between visual media data and media data files based on one or more Extended Dependent Random Access Point (EDRAP) samples, Each EDRAP sample should be the first sample in a segment or sub-segment of the mainstream representation (MSR).

2. The method according to claim 1, wherein: One of the EDRAP samples is allowed to start the segment.

3. The method according to any one of claims 1 to 2, wherein: One of the EDRAP samples is allowed to start the subsegment and not start the segment.

4. The method according to any one of claims 1 to 3, wherein: For each segment or sub-segment in the MSR that starts with one of the EDRAP samples, there is a segment in the External Stream Representation (ESR) that has the same earliest presentation time as the segment or sub-segment in the MSR.

5. The method according to any one of claims 1 to 4, wherein: The conversion includes concatenation of the ESR segment and the corresponding segment or sub-segment in the MSR with all subsequent MSR segments or sub-segments to produce a consistent bitstream.

6. The method according to claim 5, wherein: The corresponding segment or sub-segment in the MSR has the same earliest presentation time as the ESR segment.

7. The method according to any one of claims 1 to 6, wherein: For each MSR segment or sub-segment that does not start with an EDRAP sample point, there is no corresponding ESR segment having the same earliest presentation time as each MSR segment or sub-segment.

8. The method according to any one of claims 1 to 7, wherein: The method is performed as part of client operations on a client.

9. The method according to any one of claims 8, wherein: The client obtains a Media Presentation Description (MPD) for a media presentation, parses the MPD, and selects an MSR.

10. The method according to any one of claims 1 to 9, wherein: When initializing a session or performing a seek, the client determines the start presentation time of the content to be consumed and requests segments or subsegments of the MSR starting with a segment or subsegment that starts with a stream access point (SAP) and contains samples with a presentation time equal to the determined start presentation time.

11. The method according to any one of claims 1 to 10, wherein: In order to request a sub-segment in a segment, the segment index is requested to obtain information of the sub-segment, and wherein a partial Hypertext Transfer Protocol (HTTP) GET request is used.

12. The method according to any one of claims 1 to 11, wherein: When there is an ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the ESR segment is also requested before requesting the starting MSR segment or sub-segment.

13. The method according to any one of claims 1 to 12, wherein: When there is no ESR segment with the same earliest presentation time as the starting MSR segment or sub-segment, the segment of the ESR is not requested.

14. The method according to any one of claims 1 to 13, wherein: When switching to the switched-to MSR, the client requests segments or subsegments of the switched-to MSR starting from the first segment or subsegment whose earliest presentation time is greater than the last requested segment or subsegment of the switched-to MSR.

15. The method according to any one of claims 1 to 14, wherein: When there is an ESR segment having the same earliest presentation time as the starting segment or sub-segment in the switched-to MSR, the ESR segment is also requested before requesting the starting segment or sub-segment in the switched-to MSR.

16. The method according to any one of claims 1 to 15, wherein: When there is no ESR segment with the same earliest presentation time as the starting segment or sub-segment in the switched-to MSR, no ESR segment is requested.

17. The method according to any one of claims 1 to 16, wherein: ESR segments are not requested when seeking, stream switching, or continuously requesting and consuming subsequent segments or subsegments of an MSR after session initialization, including when requesting any subsequent MSR segments or subsegments starting with an EDRAP sample point.

18. The method according to any one of claims 1 to 17, wherein: Performing conversion between the visual media data and the media data file includes encoding the visual media data into the media data file.

19. The method of any one of claims 1-17, performing conversion between the visual media data and the media data file comprises decoding the visual media data from the media data file.

20. An apparatus for processing video data, comprising: processor; and a non-transitory memory having instructions thereon, wherein the instructions, when executed by the processor, cause the processor to perform the method according to any one of claims 1-19.

21. A non-transitory computer-readable medium comprising a computer program product for use by a video codec device, the computer program product comprising computer-executable instructions, wherein the computer-executable instructions are stored on the non-transitory computer-readable medium so that when executed by a processor, the video codec device performs the method according to any one of claims 1-19.

22. A non-transitory computer-readable recording medium storing a bit stream of a video generated by a method performed by a video processing device, wherein the method comprises: The method comprises: performing conversion between visual media data and a media data file based on determining one or more extended dependent random access point (EDRAP) samples, wherein each EDRAP sample should be the first sample in a segment or subsegment of a main stream representation (MSR); and generating a bitstream based on the determination.

23. A method for storing a bitstream of a video, comprising: Determining based on one or more extended dependent random access point (EDRAP) samples that a conversion between visual media data and a media data file is performed, wherein each EDRAP sample should be the first sample in a segment or subsegment of a mainstream representation (MSR); generating a bitstream based on the determination; and storing the bitstream in a non-transitory computer-readable recording medium.

24. A method, apparatus or system as described in this document.