Method and device for processing media data, method and device for generating a bit stream that includes media and memory data

Abstract

An exemplary device for processing media data is configured to perform parsing of a bitstream that includes the media data, wherein the bitstream is formatted according to Common Media Application Format (cmaf), to detect, during parsing, a file type value (ftyp) for a cmaf track file of the bitstream, to determine that a cmaf header of the cmaf track file begins with the ftyp value, and to process one or more cmaf fragments following the cmaf header of the cmaf track file. The device may additionally be configured to detect one or more segment type values ​​(styp) in the bitstream, to determine that each of the one or more styp values ​​corresponds to the beginning of a respective fragment among the cmaf fragments, and to process each of the cmaf fragments starting from the corresponding styp value.

Description

1 / 71 METHOD AND DEVICE FOR PROCESSING MEDIA DATA, METHOD AND DEVICE FOR GENERATING A BIT STREAM THAT INCLUDES MEDIA AND MEMORY DATA

[0001] This request claims the benefit of Provisional Application No. US 62 / 481,594, filed Tuesday, April 4, 2017, the full content of which is incorporated herein by reference. FIELD OF TECHNIQUE

[0002] This disclosure relates to the storage and transport of media data. BACKGROUND

[0003] Digital video capabilities can be incorporated into a wide variety of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), laptop or desktop computers, digital cameras, digital recording devices, digital media players, electronic gaming devices, electronic game consoles, satellite or cellular radio telephones, video teleconferencing devices, and the like. Digital video devices employ compression techniques, such as those described in the standards defined by MPEG-2, MPEG-4, ITU-T H.263 or ITU-T H.264 / MPEG-4, Part 10, Advanced Video Coding (AVC), ITU-T H.265 (also referred to as High Efficiency Video Coding (HEVC)), and extensions of these standards, to transmit and receive digital video information more efficiently.

[0004] After the media data has been encoded, the media data can be packaged for transmission or storage. The media data can be Petition 870250035104, dated 04 / 30 / 2025, page 13 / 18 2 / 71 gathered into a video file conforming to any one of a variety of standards, such as the International Organization for Standardization (ISO) base media file format and extensions thereof, such as AVC. SUMMARY

[0005] In general, this disclosure describes techniques for using data types (e.g., segment types and / or file types) as delimiters, type indicators, and delivery indicators. These techniques can enable the use of these data types in a simple and flexible way to provide any or all of these indications. In this way, the generated content can be used in different consumption and / or delivery environments, but also provides packaging as discussed in more detail below. [000 6] In one example, a media data processing method includes performing syntactic analysis, by a processor implanted in the circuit set, of a bitstream that includes data formatted according to the Common Media Application Format (CMAF), detecting, by the processor and during the syntactic analysis, a file type value (FTYP) for a CMAF track file from the bitstream, determining, by the processor, that a CMAF header of the CMAF track file starts with the FTYP value, and processing, by the processor, one or more CMAF fragments following the CMAF header of the CMAF track file.

[0007] In another example, a device for processing media data includes memory for storing media data; and one or more processors deployed in Petition 870190098196, dated 10 / 01 / 2019, page 6 / 106 3 / 71 circuit set and configured to: perform syntactic analysis of a bitstream that includes media data, where the bitstream is formatted according to the Common Media Application Format (CMAF); detect, during syntactic analysis, a file type value (FTYP) for a CMAF track file of the bitstream; determine that a CMAF header of the track file CMAF starts with the FTYP value; and processes one or more CMAF fragments following the CMAF header of the CMAF track file.

[0008] In another example, a device for processing media data includes means for performing syntactic analysis of a bitstream that includes data formatted according to the Common Media Application Format (CMAF); means for detecting, during syntactic analysis, a file type value (FTYP) for a CMAF track file of the bitstream; means for determining that a CMAF header of the CMAF track file begins with the FTYP value; and means for processing one or more CMAF fragments following the CMAF header of the track file. CMAF.

[0009] In another example, a computer-readable storage medium (which may be non-transient) has stored instructions that, when executed, lead a processor to perform parsing of a bitstream that includes data formatted according to Common Media Application Format (CMAF); detect, during parsing, a file type value (FTYP) for a CMAF track file from the bitstream; determine that a CMAF header of the file Petition 870190098196, dated 10 / 01 / 2019, page 7 / 106 4 / 71 CMAF track starts with the FTYP value; and process one or more CMAF fragments following the CMAF header of the CMAF track file.

[0010] In another example, a method for generating a bitstream that includes media data includes generating, by a processor deployed in the circuit suite, a Common Media Application Format (CMAF) header from a CMAF track file; setting, by the processor, a value as a file type value (FTYP) of the CMAF header that indicates the beginning of the CMAF header; encapsulating, by the processor, one or more media data samples in one or more CMAF fragments following the CMAF header of the CMAF track file; and generating, by the processor, a bitstream that includes the CMAF header and the CMAF track file, wherein the one or more CMAF fragments follow the CMAF header in the CMAF track file.

[0011] In another example, a device for generating a bitstream that includes media data includes memory configured to store media data; and one or more processors deployed in the circuit assembly and configured to: generate, by a processor deployed in the circuit assembly, a Common Media Application Format (CMAF) header from a CMAF track file for the media data; set a value as a file type value (FTYP) of the CMAF header indicating the start of the CMAF header; encapsulate one or more samples of the media data in one or more CMAF fragments following the CMAF header of the CMAF track file; and generate a bitstream that includes the header. Petition 870190098196, dated 10 / 01 / 2019, page 8 / 106 5 / 71 CMAF and the CMAF track file, wherein one or more CMAF fragments follow the CMAF header in the CMAF track file.

[0012] In another example, a device for generating a bitstream that includes media data includes means for generating a Common Media Application Format (CMAF) header from a CMAF track file; means for setting a value as a file type value (FTYP) of the CMAF header that indicates the start of the CMAF header; means for encapsulating one or more samples of the media data in one or more CMAF fragments following the CMAF header of the CMAF track file; and means for generating a bitstream that includes the CMAF header and the CMAF track file, wherein one or more CMAF fragments follow the CMAF header in the CMAF track file.

[0013] In another example, a computer-readable storage medium (which may be non-transient) has stored on it instructions that, when executed, cause a processor to generate a Common Media Application Format (CMAF) header from a CMAF track file; set a value as a file type value (FTYP) of the CMAF header that indicates the start of the CMAF header; encapsulate one or more media data samples in one or more CMAF fragments following the CMAF header of the CMAF track file; and generate a bitstream that includes the CMAF header and the CMAF track file, wherein one or more CMAF fragments follow the CMAF header in the CMAF track file.

[0014] The details of one or more examples are Petition 870190098196, dated 10 / 01 / 2019, page 9 / 106 6 / 71 presented in the attached drawings and in the description below. Other details, objectives and advantages will be evident from the description and drawings and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a block diagram illustrating an exemplary system that implements techniques for continuously transmitting media data across a network.

[0016] Figure 2 is a block diagram that illustrates an exemplary set of components of the recovery unit of Figure 1 in greater detail.

[0017] Figure 3 is a conceptual diagram that illustrates elements of exemplary multimedia content.

[0018] Figure 4 is a block diagram that illustrates elements of an example video file, which may correspond to a segment of a representation.

[0019] Figure 5 is a conceptual diagram that illustrates an exemplary Common Media Application Format (CMAF) fragment.

[0020] Figure 6 is a conceptual diagram illustrating an exemplary CMAF range.

[0021] Figure 7 is a conceptual diagram that illustrates an exemplary CMAF segment.

[0022] Figures 8A and 8B are conceptual diagrams that illustrate exemplary parts of CMAF.

[0023] Figure 9 is a conceptual diagram that illustrates an exemplary system according to the techniques of this disclosure. Petition 870190098196, dated 10 / 01 / 2019, page 10 / 106 7 / 71

[0024] Figure 10 is a conceptual diagram that illustrates an exemplary decomposition within a WAVE application using HTML-5 APIs across platform, content, and application, each of which can use data according to the techniques of this disclosure.

[0025] Figure 11 is a conceptual diagram that illustrates an exemplary sequence of boxes and the containment of a part of CMAF.

[0026] Figure 12 is a flowchart that illustrates an exemplary method for generating a bitstream in accordance with the techniques of this disclosure.

[0027] Figure 13 is a flowchart that illustrates an example of a method for processing media data in accordance with the techniques of this disclosure. DETAILED DESCRIPTION

[0028] In general, this disclosure describes techniques for using data types (e.g., segment types and / or file types) as delimiters, type indicators, and delivery indicators.

[0029] Continuous Adaptive Transmission Dynamics over HTTP (DASH) describes the use of segments as deliverable containers for media data (e.g., files with unique Uniform Resource Locators (URLs)). Segments have a type, described by a segment type syntax element or "styp". Files also have a file type, described by a file type syntax element or "ftyp". These syntax elements can be part of the file format information according to, for example, the ISO base media file format (BMFF ISO) or a file extension. Petition 870190098196, dated 10 / 01 / 2019, page 11 / 106 8 / 71 BMFF ISO.

[0030] A file that conforms to BMFF ISO or a BMFF ISO extension may additionally include media data formatted according to the Common Media Application Format (CMAF). CMAF content is used at different stages: at the content preparation stage, at the delivery level, and at the content consumption stage (for example, for an interface to a receiving device, such as a media source extension (MSE) interface).

[0031] In general, CMAF data structures are identified without a manifest file, such as a DASH Media Presentation Description (MPD). After content preparation, delimiters are typically included in byte streams / continuous files to identify CMAF data structures. At the delivery level, the types for delivered objects must be identifiable. Interfaces to playback mechanisms, such as MSEs, data structures can be identified for extraction, for example, to allow playback and switching through different CMAF controls. In general, the identification of CMAF data structures should be simple and follow the CMAF structure.

[0032] The techniques of this disclosure can be applied to video files in conformance to video data encapsulated according to any of the ISO base media file format, Scalable Video Coding (SVC) file format, Advanced Video Coding (AVC) file format, Third Generation Partnership Project (3GPP) file format, and / or Petition 870190098196, dated 10 / 01 / 2019, page 12 / 106 9 / 71 Multiview Video Coding (MVC) file format, or other similar video file formats.

[0033] In HTTP streaming, frequently used operations include HEAD, GET, and partial GET. The HEAD operation retrieves a header of a file associated with a given Uniform Resource Locator (URL) or Uniform Resource Name (URN), without retrieving a payload associated with the URL or URN. The GET operation retrieves a complete file associated with a given URL or URN. The operation Partial GET receives a byte range as an input parameter and retrieves a continuous number of bytes from a file, where the number of bytes corresponds to the received byte range. Therefore, movie fragments can be provided for HTTP streaming, due to the fact that a partial GET operation can obtain one or more individual movie fragments. Within a movie fragment, there can be multiple fragments of different track sizes. In HTTP streaming, a media presentation can be a structured collection of data that is accessible to the client. The client can request and download media data information to present a streaming service to a user.

[0034] In the example of continuously transmitting 3GPP data using HTTP continuous transmission, there may be multiple representations for video and / or audio data of the multimedia content. As explained below, different representations may correspond to different encoding characteristics (e.g., different profiles or levels of a video encoding standard), different encoding standards, or standard extensions. Petition 870190098196, dated 10 / 01 / 2019, page 13 / 106 10 / 71 encoding (such as scalable and / or multiview extensions), or different bitrates. The manifest of these representations can be defined in a Media Presentation Description (MPD) data structure. A media presentation can correspond to a structured collection of data that is accessible to a streaming HTTP client device. The streaming HTTP client device can request and download media data information to present a streaming service to a client device user. A media presentation can be described in the MPD data structure, which may include MPD updates.

[0035] A media presentation may contain a sequence of one or more Periods. Each period may extend to the beginning of the next Period, or to the end of the media presentation in the case of the last period. Each period may contain one or more representations for the same media content. A representation may be one of a number of alternative encoded versions of audio, video, timed text, or other such data. Representations may differ by encoding types, for example, by bitrate, resolution and / or codec for video data and bitrate, language and / or codec for audio data. The term representation may be used to refer to a section of encoded video or audio data corresponding to a particular period of the multimedia content and encoded in a particular way.

[0036] Representations of a particular period may be assigned to a group indicated by a Petition 870190098196, dated 10 / 01 / 2019, page 14 / 10611 / 71 attribute in MPD indicating a matching set to which representations belong. Representations within the same matching set are generally considered alternatives to each other, where a client device can dynamically and continuously switch between these representations, for example, to perform bandwidth matching. For example, each video data representation for a particular period can be assigned to the same matching set, so that any of the representations can be selected for decoding in order to present media data, such as video data or audio data, from the multimedia content for the corresponding period. The media content within a period can be represented by a representation from group 0, if present, or the combination of at most one representation from each non-zero group, in some examples.The timing data for each representation of a period can be expressed relative to the period's start time.

[0037] 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. In general, the initialization segment does not contain media data. A segment may be uniquely referenced by an identifier, such as a Uniform Resource Locator (URL), Uniform Resource Name (URN), or Uniform Resource Identifier (URI). The MPD may provide the identifiers for each segment. Petition 870190098196, dated 10 / 01 / 2019, page 15 / 106 12 / 71 In some examples, MPD can also provide byte ranges in the form of a range attribute, which can correspond to the data for a segment within a file accessible by URL, URN, or URI.

[0038] Different representations can be selected for substantially simultaneous retrieval for different types of media data. For example, a client device might select an audio representation, a video representation, and a timed text representation from which to retrieve segments. In some instances, the client device might select particular adaptation sets to perform bandwidth adaptation. That is, the client device might select an adaptation set that includes video representations, an adaptation set that includes audio representations, and / or an adaptation set that includes timed text. Alternatively, the client device might select adaptation sets for certain media types (e.g., video), and directly select representations for other media types (e.g., audio and / or timed text).

[0039] Figure 1 is a block diagram illustrating an exemplary system that employs techniques for continuously transmitting media data over a network. In this example, system 0 includes content preparation device 20, server device 60, and client device 40. Client device 40 and server device 60 are communicatively coupled by network 74, which may comprise the Internet. In some examples, the content preparation device Petition 870190098196, dated 10 / 01 / 2019, page 16 / 106 13 / 71 and the server device 60 can also be coupled via network 74 or another network, or they can be coupled communicatively directly. In some examples, the content preparation device 20 and the server device 60 may comprise the same device.

[0040] Content preparation device 20, in the example of Figure 1, comprises audio source 22 and video source 24. Audio source 22 may comprise, for example, a microphone that produces electrical signals representing captured audio data to be encoded by audio encoder 26. Alternatively, audio source 22 may comprise a storage medium that stores previously recorded audio data, an audio data generator such as a computer synthesizer, or any other audio data source. Video source 24 may comprise a video camera that produces video data to be encoded by video encoder 28, a storage medium encoded with previously recorded video data, a video data generation unit such as a computer graphics source, or any other video data source.The content preparation device 20 is not necessarily communicatively coupled to the server device 60 in all examples, but it may store multimedia content on a separate medium that is read by the server device 60.

[0041] Raw video and audio data may comprise digital or analog data. Analog data may be digitized before being encoded. Petition 870190098196, dated 10 / 01 / 2019, page 17 / 106 14 / 71 via audio encoder 26 and / or video encoder 28. Audio source 22 can obtain audio data from a speaking participant at the same time as the speaking participant is speaking, and video source 24 can simultaneously obtain video data from the speaking participant. In other examples, audio source 22 may comprise a computer-readable storage medium containing stored audio data, and video source 24 may comprise a computer-readable storage medium containing stored video data. In this way, the techniques described in this disclosure can be applied to real-time video and audio data, in live continuous transmission, or to pre-recorded archived video and audio data.

[0042] Audio frames that correspond to video frames are generally audio frames containing audio data that were captured (or generated) by audio source 22 at the same time as the video data captured (or generated) by video source 24 that are contained within the video frames. For example, while a speaking participant generally produces audio data while speaking, audio source 22 captures the audio data, and video source 24 captures the video data of the speaking participant at the same time, that is, while audio source 22 is capturing the audio data. Therefore, an audio frame may temporally correspond to one or more particular video frames. Consequently, an audio frame corresponding to a video frame generally corresponds to a situation where audio data and video data were captured at the same time and Petition 870190098196, dated 10 / 01 / 2019, page 18 / 106 15 / 71 for which an audio frame and a video frame comprise, respectively, the audio data and the video data that were captured at the same time.

[0043] In some examples, audio encoder 26 may encode a timestamp in each encoded audio frame representing a time at which the audio data for the encoded audio frame was recorded, and similarly, video encoder 28 may encode a timestamp in each encoded video frame representing a time at which the video data for the encoded video frame was recorded. In these examples, an audio frame corresponding to a video frame may comprise an audio frame comprising a timestamp and a video frame comprising the same timestamp. The content preparation device 20 may include an internal clock from which audio encoder 26 and / or video encoder 28 may generate the timestamps, or which audio source 22 and video source 24 may use to associate audio and video data, respectively, with a timestamp.

[0044] In some examples, audio source 22 may send data to audio encoder 26 corresponding to a time when audio data was recorded, and video source 24 may send data to video encoder 28 corresponding to a time when video data was recorded. In some examples, audio encoder 26 may encode a sequence identifier in the encoded audio data to indicate a relative temporal ordering of the encoded audio data. Petition 870190098196, dated 10 / 01 / 2019, page 19 / 106 16 / 71 but without necessarily indicating an absolute time at which the audio data was recorded, and similarly, the video encoder 28 can also use sequence identifiers to indicate a relative temporal ordering of the encoded video data. Similarly, in some examples, a sequence identifier can be mapped or otherwise correlated to a timestamp.

[0045] Audio encoder 26 generally produces a stream of encoded audio data, while video encoder 28 produces a stream of encoded video data. Each individual data stream (whether audio or video) can be referred to as an elementary stream. An elementary stream is a single digitally encoded (possibly compressed) component of a representation. For example, the encoded video and audio portion of the representation can be an elementary stream. An elementary stream can be converted into a packed elementary stream (PES) before being encapsulated within a video file. Within the same representation, a stream ID can be used to distinguish the PES packets belonging to one elementary stream from another. The basic data unit of an elementary stream is a packed elementary stream (PES) packet. Therefore, encoded video data generally corresponds to elementary video streams.Similarly, audio data corresponds to one or more respective elementary streams.

[0046] Many video coding standards, such as ITU-T H.264 / AVC and the following High Efficiency Video Coding (HEVC) standard, define the Petition 870190098196, dated 10 / 01 / 2019, page 20 / 106 17 / 71 syntax, semantics, and decoding process for error-free bitstreams, any of which conform to a given profile or level. Video coding standards typically do not specify the encoder, but the encoder is tasked with ensuring that the generated bitstreams conform to the standard for a decoder. In the context of video coding standards, a profile corresponds to a subset of algorithms, particularities, or tools and constraints that apply to them. As defined by the H.264 standard, for example, a profile is a subset of the entire bitstream syntax that is specified by the H.264 standard. A level corresponds to the limitations of decoder resource consumption, such as decoder computation and memory, which are related to picture resolution, bitrate, and block processing rate.A profile can be indicated with a profile_idc value (profile indicator), while a level can be indicated with a level_idc value (level indicator).

[0047] The H.264 standard, for example, recognizes that, within the limits imposed by the syntax of a given profile, it is still possible to demand a large variation in the performance of encoders and decoders depending on the values ​​taken by the syntax elements in the bitstream, such as the specified size of the decoded pictures. The H.264 standard further recognizes that, in many applications, it is neither practical nor economical to deploy a decoder capable of handling all hypothetical uses of the syntax within a profile. Petition 870190098196, dated 10 / 01 / 2019, page 21 / 106 18 / 71 particular. Consequently, the H.264 standard defines a level as a specified set of constraints imposed on the values ​​of syntax elements in the bitstream. These constraints can be simple limits on values. Alternatively, these constraints can take the form of constraints on arithmetic combinations of values ​​(e.g., engraving width multiplied by engraving height multiplied by the number of engravings decoded per second). The H.264 standard provides that individual deployments can support a different level for each supported profile.

[0048] A decoder conforming to a profile typically supports all the features defined in the profile. For example, as a coding feature, B-engraving is not supported in the base H.264 / AVC profile, but it is supported in other H.264 / AVC profiles. A decoder conforming to a level should be able to decode any bitstream that does not require resources beyond the limitations defined at the level. Profile and level definitions can be useful for interpretability. For example, during video transmission, a pair of profile and level definitions can be negotiated and agreed upon for an entire transmission session. More specifically, in H.264 / AVC, a level can define limitations on the number of macroblocks that need to be processed, decoded write buffer size (DPB), encoded write buffer size (CPB), vertical motion vector range, maximum number of motion vectors per two consecutive MBs, and whether one. Petition 870190098196, dated 10 / 01 / 2019, page 22 / 106 19 / 71 block B can have sub-macroblock partitions smaller than 8x8 pixels. In this way, a decoder can determine if the decoder has the capacity to properly decode the bitstream.

[0049] In the example of Figure 1, encapsulation unit 30 of content preparation device 20 receives elementary streams comprising encoded video data from video encoder 28 and elementary streams comprising encoded audio data from audio encoder 26. In some examples, video encoder 28 and audio encoder 26 may each include packers to form PES packets from encoded data. In other examples, video encoder 28 and audio encoder 26 may each interface with respective packers to form PES packets from encoded data. In still other examples, encapsulation unit 30 may include packers to form PES packets from encoded audio and video data.

[0050] The video encoder 28 can encode video data from multimedia content in a variety of ways, to produce different representations of the multimedia content at various bitrates and with various characteristics, such as pixel resolutions, frame rates, conformance to various encoding standards, conformance to various profiles and / or profile levels for various encoding standards, representations that have one or multiple views (e.g., for two-dimensional or three-dimensional playback), or other such characteristics. A representation, as used Petition 870190098196, dated 10 / 01 / 2019, page 23 / 106 20 / 71 in this disclosure, may comprise one of audio data, video data, text data (e.g., for closed captions), or other such data. The representation may include an elementary stream, such as an elementary audio stream or an elementary video stream. Each PES packet may include a stream_id that identifies the elementary stream to which the PES packet belongs. The encapsulation unit 30 is responsible for assembling elementary streams into video files (e.g., segments) of various representations.

[0051] The encapsulation unit 30 receives PES packets for elementary streams of a representation from the audio encoder 26 and the video encoder 28 and forms corresponding Network Abstraction Layer (NAL) units from the PES packets. The encoded video segments can be organized into NAL units, which provide a network-friendly video representation that addresses applications such as video telephony, storage, broadcasting, or streaming. NAL units can be categorized into Video Coding Layer (VCL) NAL units and non-VCL NAL units. VCL units may contain the core compression mechanism and may include block, macroblock, and / or slice-level data. Other NAL units may be non-VCL NAL units.In some examples, a recording encoded in a time instance, typically presented as a primary encoded recording, may be contained within an access unit, which may include one or more NAL units.

[0052] NAL units not VCL can Petition 870190098196, dated 10 / 01 / 2019, p. 24 / 106 21 / 71 include parameter set NAL units and SEI NAL units, among others. Parameter sets can contain sequence-level header information (in sequence parameter sets (SPS)) and infrequently changing engraving-level header information (in engraving parameter sets (PPS)). With parameter sets (e.g., PPS and SPS), infrequently changing information does not need to be repeated for each sequence or engraving, therefore encoding efficiency can be improved. Furthermore, the use of parameter sets can enable out-of-band transmission of important header information, avoiding the need for redundant transmissions for error resilience. In out-of-band transmission examples, parameter set NAL units can be transmitted on a different channel than other NAL units, such as SEI NAL units.

[0053] Improvement Information Supplemental Information (SEI) messages may contain information that is not necessary for decoding the encoded engraving samples from VCL NAL units, but may assist in processes related to decoding, display, error resilience, and other purposes. SEI messages may be contained in non-VCL NAL units. SEI messages are the normative part of some standard specifications and are therefore not always mandatory for standard-compliant decoder deployment. SEI messages can be sequence-level SEI messages or engraving-level SEI messages. Some sequence-level information... Petition 870190098196, dated 10 / 01 / 2019, page 25 / 106 22 / 71 sequences may be contained within SEI messages, such as scalability information SEI messages in the SVC example and view scalability information SEI messages in MVC. These example SEI messages may convey information about, for example, operation point extraction and operation point characteristics. Additionally, encapsulation unit 30 may form a manifest file, such as a Media Presentation Descriptor (MPD) that describes representation characteristics. Encapsulation unit 30 may format the MPD according to Extensible Markup Language (XML).

[0054] The encapsulation unit 30 can provide data for one or more multimedia content representations, along with the manifest file (e.g., the MPD) to the output interface 32. The output interface 32 can comprise a network interface or an interface for writing to a storage medium, such as a Universal Serial Bus (USB) interface, a CD or DVD burner or recorder, an interface for flash or magnetic storage media, or other interfaces for storing or transmitting media data. The encapsulation unit 30 can provide data from each of the multimedia content representations to the output interface 32, which can send the data to the server device 60 via the storage medium or network transmission. In the example in Figure 1, the server device 60 includes storage media 62 that stores various multimedia contents 64, each including a respective file. Petition 870190098196, dated 10 / 01 / 2019, p. 26 / 106 23 / 71 of manifest 66 and one or more representations 68A-68N (representations 68). In some examples, the output interface 32 can also send data directly to the network 74.

[0055] In some examples, representations may be separated into adaptation sets. That is, various subsets of representations 68 may include respective common sets of features, such as codec, profile and level, resolution, number of views, file format for segments, text type information that may identify a language or other characteristics of the text to be displayed with the representation and / or audio data to be decoded and presented, for example, by loudspeakers, camera angle information that may describe a real-world camera angle or camera perspective of a scene for representations in the adaptation set, rating information that describes the suitability of content for particular audiences, or similar.

[0056] The manifest file 66 may include data indicating the subsets of representations 68 corresponding to particular adaptation sets, as well as common characteristics for adaptation sets. The manifest file 66 may also include data representing individual characteristics, such as bit rates, for individual representations of adaptation sets. In this way, an adaptation set may provide simplified network bandwidth adaptation. The representations in an adaptation set may be indicated using child elements of a Petition 870190098196, dated 10 / 01 / 2019, page 27 / 106 24 / 71 element of the manifest file adaptation set 66.

[0057] Server device 60 includes request processing unit 70 and network interface 72. In some instances, server device 60 may include a plurality of network interfaces. Furthermore, any or all of the features of server device 60 may be deployed on other devices in a content delivery network, such as routers, bridges, proxy devices, switches, or other devices. In some instances, the intermediate devices of a content delivery network may cache multimedia content data 64, and include components that substantially conform to those of server device 60. In general, network interface 72 is configured to send and receive data over the network 74.

[0058] Request processing unit 70 is configured to receive network requests from client devices, such as client device 40, for storage media data 62. For example, request processing unit 70 may deploy Hypertext Transfer Protocol (HTTP) version 1.1, as described in RFC 2616, “Hypertext Transfer Protocol - HTTP / 1.1”, by R. Fielding et al, Network Working Group, IETF, June 1999. That is, request processing unit 70 may be configured to receive HTTP GET or partial GET requests and provide multimedia content data 64 in response to the requests. Requests may specify a segment Petition 870190098196, dated 10 / 01 / 2019, page 28 / 106 25 / 71 of one of the 68 representations, for example, using a segment URL. In some examples, requests may also specify one or more byte ranges of the segment, which therefore comprise partial GET requests. The request processing unit 70 can be further configured to serve HTTP HEAD requests to provide header data from a segment of one of the 68 representations. In any case, the request processing unit 70 can be configured to process requests in order to provide requested data to a requesting device, such as client device 40.

[0059] Alternatively, the request processing unit 70 can be configured to deliver media data via a broadcast or selective broadcast protocol, such as eMBMS. The content preparation device 20 can create DASH segments and / or subsegments substantially in the same way as described, but the server device 60 can deliver these segments or subsegments using eMBMS or another broadcast or selective broadcast network transport protocol. For example, the request processing unit 70 can be configured to receive a selective broadcast group join request from the client device 40. That is, the server device 60 can advertise an Internet Protocol (IP) address associated with a selective broadcast group to the client devices, which include client device 40, associated with the particular media content (e.g., a broadcast of a live event). Petition 870190098196, dated 10 / 01 / 2019, page 29 / 106 26 / 71 Client device 40, in turn, can submit a request to join the selective broadcast group. This request can be propagated throughout network 74, for example, routers that make up network 74, so that the routers are led to direct traffic destined for the IP address associated with the selective broadcast group to subscribe client devices, such as client device 40.

[0060] As illustrated in the example in Figure 1, multimedia content 64 includes manifest file 66, which may correspond to a media presentation description (MPD). Manifest file 66 may contain descriptions of different alternative representations 68 (e.g., video services with different qualities) and the description may include, for example, codec information, a profile value, a level value, a bitrate, and other descriptive characteristics of the representations 68. Client device 40 can retrieve the MPD of a media presentation to determine how to access segments of representations 68.

[0061] In particular, recovery unit 52 can retrieve configuration data (not shown) from client device 40 to determine the decoding capabilities of the video decoder 48 and the rendering capabilities of the video output 44. The configuration data may also include any or all of the language preference selected by a user of client device 40, one or more camera perspectives corresponding to depth preferences defined by the user of client device 40, and / or a preference for Petition 870190098196, dated 10 / 01 / 2019, page 30 / 106 27 / 71 user-selected classification of client device 40. The retrieval unit 52 may comprise, for example, a web browser or a media client configured to present HTTP GET and partial GET requests. The retrieval unit 52 may correspond to software instructions executed by one or more processors or processing units (not shown) of client device 40. In some examples, all or portions of the functionality described in relation to the retrieval unit 52 may be implemented in hardware, or a combination of hardware, software and / or firmware, wherein necessary hardware may be provided in order to execute instructions for software or firmware.

[0062] The retrieval unit 52 can compare the decoding and rendering capabilities of the client device 40 to representation characteristics 68 indicated by the manifest file information 66. The retrieval unit 52 can initially retrieve at least a portion of the manifest file 66 to determine representation characteristics 68. For example, the retrieval unit 52 can request a portion of the manifest file 66 that describes characteristics of one or more adaptation sets. The retrieval unit 52 can select a subset of representations 68 (e.g., an adaptation set) that has characteristics that can be satisfied by the encoding and rendering capabilities of the client device 40. The retrieval unit 52 can then determine bitrates for representations in the adaptation set, determine a quantity Petition 870190098196, dated 10 / 01 / 2019, page 31 / 106 28 / 71 currently available network bandwidth and retrieve segments from one of the representations that have a bit rate that can be satisfied by the network bandwidth.

[0063] In general, higher bitrate representations can yield higher quality video playback, while lower bitrate representations can provide sufficient quality video playback when available network bandwidth decreases. Consequently, when available network bandwidth is relatively high, recovery unit 52 can retrieve data from relatively high bitrate representations, whereas when available network bandwidth is low, recovery unit 52 can retrieve data from relatively low bitrate representations. In this way, client device 40 can transmit multimedia data over network 74 while also adapting to the changing network bandwidth availability of network 74.

[0064] Alternatively, retrieval unit 52 can be configured to receive data according to a broadcast or selective broadcast network protocol, such as eMBMS or IP selective broadcast. In these examples, retrieval unit 52 can submit a request to join a selective broadcast network group associated with the particular media content. After joining the selective broadcast group, retrieval unit 52 can receive data from the selective broadcast group without additional requests being issued to Petition 870190098196, dated 10 / 01 / 2019, page 32 / 106 29 / 71 the server device 60 or content preparation device 20. The retrieval unit 52 may submit a request to leave the selective broadcast group when the data from the selective broadcast group is no longer needed, for example, to stop playback or to change channels to a different selective broadcast group.

[0065] Network interface 54 can receive and provide segment data of a selected representation to recovery unit 52, which can in turn provide the segments to decapsulation unit 50. Decapsulation unit 50 can decapsulate elements of a video file into constituent PES streams, unpack the PES streams in order to recover encoded data, and send the encoded data to audio decoder 46 or video decoder 48, depending on whether the encoded data is part of an audio or video stream, for example, as indicated by the stream's PES packet headers. Audio decoder 46 decodes encoded audio data and sends the decoded audio data to audio output 42, while video decoder 48 decodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to video output 44.

[0066] Video encoder 28, Video decoder 48, Audio encoder 26, Audio decoder 46, Encapsulation unit 30, Recovery unit 52 and unit of Petition 870190098196, dated 10 / 01 / 2019, page 33 / 106 30 / 71 decapsulation 50 can each be deployed as any one of a variety of suitable processing circuit sets, as applicable, such as one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), distinct logic circuit sets, software, hardware, firmware, or any combination thereof. Each of the video encoder 28 and video decoder may be included in one or more encoders or decoders, one of which may be integrated as part of a combined video encoder / decoder (CODEC). Similarly, each of the audio encoder 26 and audio decoder 46 may be included in one or more encoders or decoders, any of which may be integrated as part of a combined CODEC.An apparatus that includes a video encoder 28, a video decoder 48, an audio encoder 26, an audio decoder 46, an encapsulation unit 30, a recovery unit 52 and / or a decapsulation unit 50 may comprise an integrated circuit, a microprocessor and / or a wireless communication device, such as a mobile phone.

[0067] Client device 40, server device 60, and / or content preparation device 20 can be configured to operate in accordance with the techniques of this disclosure. For example purposes, this disclosure describes these techniques with respect to client device 40 and server device 60. However, it should be understood that the content preparation device Petition 870190098196, dated 10 / 01 / 2019, page 34 / 106 31 / 71 content 20 can be configured to perform these techniques, instead of (or in addition to) server device 60.

[0068] The encapsulation unit 30 can form NAL units comprising a header that identifies a program to which the NAL unit belongs, as well as a payload, for example, audio data, video data, or data describing the program or transport stream to which the NAL unit corresponds. For example, in H.264 / AVC, a NAL unit includes a 1-byte header and a payload of varying size. A NAL unit that includes video data in its payload can comprise various levels of granularity of the video data. For example, a NAL unit can comprise a block of video data, a plurality of blocks, a slice of the video data, or an entire recording of the video data. The encapsulation unit 30 can receive video data encoded from the video encoder 28 in the form of PES packets of elementary streams. The encapsulation unit 30 can associate each elementary stream with a corresponding program.

[0069] The encapsulation unit 30 can also gather access units from a plurality of NAL units. In general, an access unit can comprise one or more NAL units to represent a video data frame, as well as audio data corresponding to the frame when such audio data is available. An access unit generally includes all NAL units for an output time instance, for example, all audio and video data for a Petition 870190098196, dated 10 / 01 / 2019, page 35 / 106 32 / 71 time instance. For example, if each view has a frame rate of 20 frames per second (fps), then each time instance can correspond to a time interval of 0.05 seconds. During this time interval, frames specific to all views of the same access unit (the same time instance) can be rendered simultaneously. In one example, an access unit might comprise an image encoded in a time instance, which can be presented as a primary encoded image.

[0070] Consequently, an access unit can comprise all audio and video frames of a common temporal instance, for example, all views corresponding to time X. This revelation also refers to an encoded recording of a particular view as a “view component”. That is, a view component can comprise an encoded recording (or frame) for a particular view at a particular time. Consequently, an access unit can be defined as comprising all view components of a common temporal instance. The decoding order of the access units does not necessarily have to be the same as the output or display order.

[0071] A media presentation may include a media presentation description (MPD), which may contain descriptions of different alternative representations (e.g., video services with different qualities) and a description may include, for example, codec information, a profile value, and a level value. An MPD is an example of a manifest file, such as a file of Petition 870190098196, dated 10 / 01 / 2019, page 36 / 106 33 / 71 manifest 66. Client device 40 can retrieve the MPD from a media presentation to determine how to access movie fragments from various presentations. Movie fragments may be located in movie fragment boxes (moof boxes) of video files.

[0072] The manifest file 66 (which may comprise, for example, an MPD) may announce the availability of segments of representations 68. That is, the MPD may include information indicating the total time in which a first segment of one of the representations 68 becomes available, as well as information indicating the durations of the segments within the representations 68. In this way, the recovery unit 52 of the client device 40 can determine when each segment is available, based on the start time as well as the durations of the segments preceding a particular segment.

[0073] After the encapsulation unit 30 has assembled NAL units and / or access units into a video file based on the received data, the encapsulation unit 30 passes the video file to the output interface 32 for transmission. In some examples, the encapsulation unit 30 may store the video file locally or send the video file to a remote server via the output interface 32, instead of sending the video file directly to the client device 40. The output interface 32 may comprise, for example, a transmitter, a transceiver, a device for recording data to computer-readable media such as, for example, an optical drive, a magnetic media drive (e.g., floppy disk drive), a port of Petition 870190098196, dated 10 / 01 / 2019, page 37 / 106 34 / 71 Universal Serial Bus (USB), a network interface, or another output interface. Output interface 32 outputs the video file to a computer-readable medium, such as a broadcast signal, magnetic media, optical media, memory, a flash drive, or other computer-readable media.

[0074] A network interface 54 can receive a NAL unit or access unit via the network 74 and provide the NAL unit or access unit to the decapsulation unit 50 via the recovery unit. 52. The decapsulation unit 50 can decapsulate elements of a video file into constituent PES streams, unpack the PES streams in order to recover encoded data, and send the encoded data to the audio decoder 46 or video decoder 48, depending on whether the encoded data is part of an audio or video stream, for example, as indicated by the stream's PES packet headers. The audio decoder 46 decodes encoded audio data and sends the decoded audio data to the audio output 42, while the video decoder 48 decodes encoded video data and sends the decoded video data, which may include a plurality of views of a stream, to the video output 44.

[0075] According to the techniques of this disclosure, the encapsulation unit 30 can use a single type of signaling for a variety of purposes, for example, any or all of a content preparation stage, delivery level and / or a content consumption stage. Similarly, the retrieval unit 52 can Petition 870190098196, dated 10 / 01 / 2019, page 38 / 106 35 / 71 use this single type of signage for any or all of these purposes. [007 6] In one example, the single signaling type is a file type box (ftyp) that includes a value that acts as an identifier for one or more CMAF controls. Therefore, encapsulation unit 30 can set a value for the ftyp box, and retrieval unit 52 can read a value for the ftyp box. Additionally, request processing unit 70 can also read the value for the ftyp box. These components can use the ftyp box value during any or all content preparation, delivery, and / or consumption.

[0077] Alternatively, the single signaling type may be a segment type box (styp) that includes a value that acts as an identifier for one or more CMAF controls. The styp box may act as a delimiter to identify CMAF part and / or fragment thresholds, identifiers for CMAF data structures, identifiers for DASH segments (or segments for other continuous network streaming technologies), and / or identifiers for processing requirements. Therefore, encapsulation unit 30 may specify values ​​for one or more styp boxes of a segment to represent any or all of the segment's CMAF part and / or fragment thresholds, the identifiers for the segment's CMAF data structures, an identifier for the DASH segment, and / or identifiers for processing requirements for the segment's media data. In general, styp boxes are Petition 870190098196, dated 10 / 01 / 2019, page 39 / 106 36 / 71 are optional and can be used or not, to avoid problems with backward compatibility and overload.

[0078] Table 1 below represents type value marks, according to the techniques of this disclosure, including locations of each type of mark and exemplary conformance requirements: TABLE 1 Location Markup Conformance Requirements 'cmfc' FileTypeBox and SegmentTypeBo x Common Media Application Track Format 'cmfs' SegmentTypeBo x CMAF Segments 'cmfl' SegmentTypeBo x CMAF Parts 'cmfr SegmentTypeBo x CMAF Fragment (identifies the presence of the first samples of the CMAF fragment)

[0079] Tables 2 to 6 below represent illustrative data structures that can be used in accordance with the techniques of this disclosure: TABLE 2 - CMAF Range File NL0 Format Requirement Specification Requirements Description CMAFHeader 1 CMAF CMAF 7.2 CMAF Header sidx 0 / 1 Segment Index Petition 870190098196, dated 10 / 01 / 2019, page 40 / 106 37 / 71 CMAF fragment. Entire CMAF range. CMAF. CMAF. CMAF fragments. TABLE 3 - CMAF Header NL0 ISOBMFF Format Requirement CMAF Restrictions Description ftyp 1 [ISOBMFF] 4.3 CMAF 7.2 File Type and Compatibility cmfc moov 1 [ISOBMFF] 8.2.1 Container for functional metadata TABLE 4 - CMAF Segment NL0 Format Req. Specification Requirements Description styp 0 / 1 [ISOBMFF] 8.16.2 Segment Type; Signaling Compatibility for CMAF Segment emfs CMAF Fragment 1 + CMAF 7.3.2.3 CMAF Fragment Petition 870190098196, dated 10 / 01 / 2019, page 41 / 106 38 / 71 TABLE 5 - CMAF fragment NL 0 Format Req. Specification Requirements Description styp 0 / 1 [ISOBMFF] 8.16.2 Segment Type; Signaling compatibility for CMAF fragment cmff CMAF Part 1 + CMAF Logo Above CMAF Part TABLE 6 - Part of CMAF NL 0 Format Req. Specification Requirements Description styp 0 / 1 [ISOBMFF] 8.16.2 Segment Type; Signaling compatibility for CMAF part cmfl prft 0 / 1 [ISOBMFF] 8.16.5 Producer Reference Time emsg * [DASH] CMAF 7.4.5 Event Message moof 1 [ISOBMFF] 8.8.4 Film Fragment mdat 1 [ISOBMFF] 8.2.2 CMAF 7.5.18 Media Data Container for media samples

[0080] Regarding delivery and consumption, in some examples, ftyp and styp provide indications of type compatibility and how the type can be used. A Petition 870190098196, dated 10 / 01 / 2019, page 42 / 106 Box 39 / 71 can be at the beginning of the object, and therefore easy to find and perform syntactic analysis (e.g., by retrieval unit 52 and / or decapsulation unit 50). Multiple compatibility types can be used to signal different types. The box type can also be exposed as an Internet Media Type using the profiles parameter and, for example, be used in the case of HTTP (e.g., for streaming DASH or other HTTP streaming technologies). This can enable different distribution modes.

[0081] Regarding the use of types as delimiters, type values ​​can delimit parts within fragments, delimit fragments within segments and track files, and / or delimit tracks to provide proper interpretation. The delimiter (e.g., type value) can also represent types, for a receiving element (e.g., recovery unit 52 and / or decapsulation unit 50) to determine the type of data (e.g., media data) included in the part, fragment, segment, track file, or similar. No subsequent field indexing is required, and therefore, these techniques can support real-time processing.

[0082] Figure 2 is a block diagram that illustrates an exemplary set of components of recovery unit 52 from Figure 1 in greater detail. In this example, recovery unit 52 includes eMBMS middleware unit 100, DASH client 110, and media application 112.

[0083] In the example in Figure 2, the eMBMS 100 middleware unit additionally includes a unit of Petition 870190098196, dated 10 / 01 / 2019, page 43 / 106 40 / 71 receiving eMBMS 106, cache 104, and server unit 102. In this example, the receiving eMBMS unit 106 is configured to receive data via eMBMS, for example, according to File Delivery over Unidirectional Transport (FLUTE), described in T. Paila et al., “FLUTE-File Delivery over Unidirectional Transport”, Network Working Group, RFC 6726, November 2012, available at http: / / ferramentas.ietf.org / htm1 / rfc6726. That is, the receiving eMBMS unit 106 can receive files via broadcast from, for example, server device 60, which can act as a BM-SC.

[0084] As the eMBMS 100 middleware unit receives data for files, the eMBMS middleware unit can cache the received data 104. The 104 cache can comprise a computer-readable storage medium such as flash memory, a hard disk, RAM, or any other suitable storage medium.

[0085] Local server unit 102 can act as a server for DASH client 110. For example, local server unit 102 can provide an MPD file or other manifest file to DASH client 110. Local server unit 102 can advertise availability times for segments in the MPD file, as well as hyperlinks from which the segments can be retrieved. These hyperlinks can include a local host address prefix corresponding to client device 40 (e.g., 127.0.0.1 for 1Pv4). In this way, DASH client 110 can request segments from local server unit 102 using Petition 870190098196, dated 10 / 01 / 2019, page 44 / 106 41 / 71 HTTP GET requests or partial GET requests. For example, for a segment available from the link http: / / 127.0.0.1 / repl / seg3, the DASH client 110 can construct an HTTP GET request that includes a request to http: / / 127.0.0.1 / repl / seg3, and present the request to the local server unit 102. The local server unit 102 can retrieve requested data from the cache 104 and provide the data to the DASH client 110 in response to these requests.

[0086] Figure 3 is a conceptual diagram illustrating elements of exemplary multimedia content 120. Multimedia content 120 may correspond to multimedia content 64 (Figure 1), or other multimedia content stored on storage media 62. In the example in Figure 3, multimedia content 120 includes media presentation description (MPD) 122 and a plurality of representations 124A-124N (representations 124). Representation 124A includes optional header data 126 and segments 128A-128N (segments 128), while representation 124N includes optional header data 130 and segments 132A-132N (segments 132). The letter N is used to designate the last film fragment in each of the representations 124 as a form of convenience. In some examples, there may be different numbers of film fragments among the representations 124.

[0087] MPD 122 may comprise a separate data structure from representations 124. MPD 122 may correspond to manifest file 66 in Figure 1. Similarly, representations 124 may correspond Petition 870190098196, dated 10 / 01 / 2019, page 45 / 106 42 / 71 to representations 68 of Figure 2. In general, MPD 122 may include data that describes, in general, representation characteristics 124, such as encoding and rendering characteristics, adaptation sets, a profile to which MPD 122 corresponds, text type information, camera angle information, rate information, trick mode information (e.g., information indicative of representations that include temporal subsequences), and / or information to retrieve remote periods (e.g., for targeted ad insertion in media content during playback).

[0088] Header data 126, when present, may describe characteristics of segments 128, for example, temporal locations of random access points (RAPs, also referred to as flow access points (SAPs)), which of the segments 128 include random access points, byte offsets for random access points within segments 128, uniform resource locators (URLs) of segments 128, or other aspects of segments 128. Header data 130, when present, may describe characteristics for segments 132. Alternatively, these characteristics may be completely included within MPD 122.

[0089] Segments 128 and 132 include one or more encoded video samples, each of which may include frames or slices of video data. Each of the encoded video samples in segment 128 may have similar characteristics, for example, height, width, and bandwidth requirements. These characteristics Petition 870190098196, dated 10 / 01 / 2019, page 46 / 106 43 / 71 can be described by MPD 122 data, although this data is not illustrated in the example in Figure 3. MPD 122 may include features as described by the 3GPP Specification, with the addition of any or all of the flagged information described in this disclosure.

[0090] Each of segments 128, 132 can be associated with a unique Uniform Resource Locator (URL). Therefore, each of segments 128, 132 can be independently retrieved using a streaming network protocol, such as DASH. In this way, a destination device, such as client device 40, can use an HTTP GET request to retrieve segments 128 or 132. In some examples, client device 40 can use partial HTTP GET requests to retrieve byte ranges of segments 128 or 132.

[0091] Figure 4 is a block diagram that illustrates elements of an exemplary video file 150, which may correspond to a segment of a representation, such as one of the segments 114, 124 in Figure 3. Each of the segments 128, 132 may include data that substantially conforms to the data arrangement illustrated in the example in Figure 4. It can be said that video file 150 encapsulates one segment. As described above, video files according to the ISO base media file format and their extensions store data in a series of objects, referred to as “boxes”. In the example in Figure 4, video file 150 includes file type box (FTYP) 152, movie box (MOOV) 154, segment index boxes (sidx) 162, movie fragment boxes (MOOF) 164, and random access fragment box. Petition 870190098196, dated 10 / 01 / 2019, page 47 / 106 44 / 71 movie (MFRA) 166. Although Figure 4 represents an example of a video file, it should be understood that other media files may include other types of media data (e.g., audio data, timed text data, or similar) that are structured similarly to video file data 150, according to the ISO base media file format and its extensions.

[0092] File type box (FTYP) 152 generally describes a file type for video file 150. File type box 152 may include data identifying a specification describing a best use for video file 150. File type box 152 may alternatively be placed before MOOV box 154, film fragment boxes 164, and / or MFRA box 166.

[0093] In some examples, a Segment, such as video file 150, may include an MPD update box (not shown) before the FTYP 152 box. The MPD update box may include information indicating that an MPD corresponding to a representation that includes video file 150 should be updated, along with the information to update the MPD. For example, the MPD update box may provide a URI or URL to a resource to be used to update the MPD. As another example, the MPD update box may include data to update the MPD. In some examples, the MPD update box may immediately follow a segment type (STYP) box (not shown) of video file 150, where the STYP box may define a segment type for video file 150. Figure 7, discussed Petition 870190098196, dated 10 / 01 / 2019, page 48 / 106 45 / 71, detailed below, provides additional information regarding the MPD update box.

[0094] The MOOV box 154, in the example in Figure 4, includes the movie header box (MVHD) 156, the track box (TRAK) 158, and one or more movie extension boxes (MVEX) 160. In general, the MVHD box 156 can describe general characteristics of the video file 150. For example, the MVHD box 156 can include data describing when the video file 150 was originally created, when the video file 150 was last modified, a timescale for the video file 150, a playback duration for the video file 150, or other data that generally describes the video file 150.

[0095] TRAK box 158 may include data for a track of video file 150. TRAK box 158 may include a track header box (TKHD) that describes characteristics of the track corresponding to TRAK box 158. In some examples, TRAK box 158 may include encoded video recordings, while in other examples, the encoded video recordings of the track may be included in film fragments 164, which may be referenced by TRAK box 158 data and / or sidx boxes 162.

[0096] In some examples, video file 150 may include more than one track. Consequently, MOOV box 154 may include a number of TRAK boxes equal to the number of tracks in video file 150. TRAK box 158 may describe characteristics of a corresponding track from video file 150. For example, the Petition 870190098196, dated 10 / 01 / 2019, page 49 / 106 TRAK box 158 can describe temporal and / or spatial information for the corresponding track. A TRAK box similar to TRAK box 158 of MOOV box 154 can describe characteristics of a parameter set track, when encapsulation unit 30 (Figure 3) includes a parameter set track in a video file, such as video file 150. Encapsulation unit 30 can signal the presence of sequence-level SEI messages in the parameter set track within the TRAK box that describes the parameter set track.

[0097] MVEX boxes 160 can describe characteristics of corresponding film fragments 164, for example, to signal that video file 150 includes film fragments 164, in addition to the video data included within MOOV box 154, if any. In the context of continuous video data transmission, encoded video recordings may be included in film fragments 164 instead of in MOOV box 154. Consequently, all encoded video samples may be included in film fragments 164 instead of in MOOV box 154.

[0098] The MOOV 154 box may contain a number of MVEX 160 boxes equal to the number of movie fragments 164 in the video file 150. Each of the MVEX 160 boxes may describe characteristics of a corresponding fragment among the movie fragments 164. For example, each MVEX box may include a Movie Extension Header (MEHD) box that describes a temporal duration for the corresponding fragment among the Petition 870190098196, dated 10 / 01 / 2019, pp. 50 / 106 4Ί / Ί1 film fragments 164.

[0099] As noted above, encapsulation unit 30 can store sequence data defined in a video sample that does not include actual encoded video data. A video sample can generally correspond to an access unit, which is a representation of an encoded recording at a specific time instance. In the context of AVC, the encoded recording includes one or more VCL NAL units containing the information to construct all the pixels of the access unit and other associated non-VCL NAL units, such as SEI messages. Consequently, encapsulation unit 30 can include a sequence data set, which may include sequence-level SEI messages, in one of the film fragments 164.The encapsulation unit 30 can additionally signal the presence of a sequence data set and / or sequence-level SEI messages as being present in one of the film fragments 164 within one of the MVEX boxes 160 corresponding to one of the film fragments 164.

[00100] SIDX 162 boxes are optional elements of the 150 video file. That is, video files that conform to the 3GPP file format, or other such file formats, do not necessarily include SIDX 162 boxes. Following the example of the 3GPP file format, a SIDX box can be used to identify a subsegment of a segment (for example, a segment contained within the 150 video file). The 3GPP file format defines a subsegment as “a self-contained set of one or more boxes of Petition 870190098196, dated 10 / 01 / 2019, page 51 / 106 48 / 71 consecutive movie fragments with corresponding Media Data Box(es) and a Media Data Box containing data referenced by a Movie Fragment Box must follow that Movie Fragment Box and precede the next Movie Fragment Box containing information about the same track.” The 3GPP file format also indicates that a SIDX box “contains a sequence of references to subsegments of the (sub)segment documented by the box. The referenced subsegments are contiguous at presentation time. Similarly, the bytes referenced by a Segment Index Box are always contiguous within the segment. The referenced size provides the count of the number of bytes in the referenced material.”

[00101] The SIDX boxes 162 generally provide representative information for one or more subsegments of a segment included in the video file 150. For example, this information may include playback times at which the subsegments begin and / or end, byte offsets for the subsegments, whether the subsegments include (e.g., begin with) a stream access point (SAP), a type for the SAP (e.g., whether the SAP is an instant decoder refresh (IDR) record, a clean random access (CRA) record, a broken link access (BLA) record, or similar), a position of the SAP (in terms of playback time and / or byte offset) in the subsegment, and similar.

[00102] Film fragments 164 may include one or more encoded video recordings. In Petition 870190098196, dated 10 / 01 / 2019, page 52 / 106 49 / 71 In some examples, the 164 film fragments may include one or more picture groups (GOPs), each of which may include a number of encoded video pictures, for example, frames or engravings. Additionally, as described above, the 164 film fragments may include sequence data sets in some examples. Each of the 164 film fragments may include a Film Fragment Header Box (MFHD, not shown in Figure 4). The MFHD box may describe characteristics of the corresponding film fragment, such as a sequence number for the film fragment. The 164 film fragments may be included in sequence number order in the 150 video file. In some examples, one or more of the 164 film fragments may be preceded by a CMAF header, for example, according to Table 3 as discussed above.Furthermore, a CMAF segment can include one or more CMAF fragments, each of which can include one or more optional boxes, a movie fragment box, and a media data box.

[00103] The MFRA 166 box can describe random access points within film fragments 164 of the video file 150. This can assist with performing trick modes, such as searching for particular temporal locations (i.e., playback times) within a segment encapsulated by the video file 150. The MFRA 166 box is generally optional and does not need to be included in the video files in some instances. Similarly, a client device, such as client device 40, does not necessarily need to reference the MFRA 166 box to decode correctly. Petition 870190098196, dated 10 / 01 / 2019, page 53 / 106 50 / 71 and display video data from video file 150. The MFRA 166 box may include a number of track fragment random access boxes (TFRA) (not shown) equal to the number of tracks in video file 150, or in some examples, equal to the number of media tracks (e.g., tracks without hint) in video file 150.

[00104] In some examples, film fragments 164 may include one or more stream access points (SAPs), such as IDR engravings. Similarly, MFRA box 166 may provide indications of locations within video file 150 of SAPs. Consequently, a temporal subsequence of video file 150 may be formed from SAPs of video file 150. The temporal subsequence may also include other engravings, such as P-frames and / or B-frames that depend on SAPs. The frames and / or slices of the temporal subsequence may be arranged within the segments so that frames / slices of the temporal subsequence that depend on other frames / slices of the subsequence can be decoded appropriately. For example, in hierarchical data arrangement, data used for prediction for other data may also be included in the temporal subsequence.

[00105] Figure 5 is a conceptual diagram illustrating an exemplary CMAF 200 fragment. The CMAF 200 fragment in Figure 5 may correspond to one of the film fragments 164 in Figure 4. The CMAF 200 fragment may conform to Table 5 above. CMAF fragments, such as the CMAF 200 fragment, may be the smallest switching units that are handled by encoding. Petition 870190098196, dated 10 / 01 / 2019, page 54 / 106 51 / 71 of CMAF, delivery of CMAF and CMAF breeding stock.

[00106] In the example in Figure 5, the fragment of CMAF 200 includes zero or more optional boxes 202, a movie fragment box 204, and a media data box (mdat) 206. Optional boxes 202 are highlighted with a dashed line to indicate that optional boxes 202 are optional. The optional boxes 202 in Figure 5 may include none, any, or all of a segment type box, a producer reference time box, and / or a DASH event message box(es).

[00107] The MDAT box 206 includes random access media samples 208A-208C (random access media samples 208), which may correspond to one or more continuous encoded video streams (CVSs). A decoding time 210 of a first sample, for example, an ordinal first sample, of the MDAT box 206 (e.g., random access media sample 208A) may be indicated by a track fragment decoding time (tfdt) box, which may be included in the moof box 204. In particular, the tfdt box may be included in a track fragment (traf) box of the moof box 204, and may indicate a track fragment-based media decoding time.

[00108] In some examples, the fragments of CMAF, like the CMAF 200 fragment, conforms to the following constraints: 1. Each CMAF Fragment, in combination with its associated CMAF Header, will contain sufficient metadata to be Petition 870190098196, dated 10 / 01 / 2019, pp. 55 / 106 52 / 71 decoded, decrypted, and displayed when accessed independently. In addition to Media Profile and CMAF Track restrictions, a CMAF Track is non-compliant if a CMAF Fragment cannot be decoded when processed with its associated CMAF Header. For example, if sample groups and sample group descriptions are used to signal encryption key changes, then a SampleGroupDescriptionBox and SampleToGroupBox need to be present in the TrackFragmentBox to make the randomly accessible and decryptable CMAF Fragment. 2. The CMAF MovieFragmentBox fragment may be preceded by other boxes, including one or more SegmentTypeBoxes, ProducerReferenceTimeBoxes, and / or DASHEventMessageBoxes. (See 7.4.5 and Annex E of ISO / IEC 23000-19 for more information on Event Messages). 3. Each CMAF fragment in a CMAF strip must have a duration of at least one second, with the possible exception of the first and last fragments in the strip.

[00109] Figure 6 is a conceptual diagram illustrating an exemplary CMAF 220 range. In this example, the CMAF 220 range includes CMAF 222 header and Petition 870190098196, dated 10 / 01 / 2019, pp. 56 / 106 53 / 71 fragments of CMAF 230A, 230B (fragments of CMAF 230). Each of the CMAF 230 fragments includes a respective set of zero or more optional boxes, a moof box, and an mdat box. For example, the CMAF 230A fragment includes optional boxes 224A, moof box 226A, and mdat box 228A, while the CMAF 230B fragment includes optional boxes 224B, moof box 226B, and mdat box 228B. Thus, each of the CMAF 230 fragments can generally include elements similar to the elements of the CMAF 200 fragment in Figure 5. The CMAF 220 track in Figure 6 can be included within a video file, such as video file 150 in Figure 4, where the CMAF 222 header can correspond to the ftyp box 152 and moov box 154 in Figure 4, and CMAF 230 fragments can start at the beginning of movie fragments 164 in Figure 4. The CMAF 200 track can generally conform to Table 2 above.

[00110] According to the techniques of this disclosure, the CMAF 222 header can include an ftyp value at NL 0, as discussed above, and as shown in the example in Table 3. That is, the content preparation device 20 of Figure 1 can set the ftyp value, at least in part, to indicate the beginning of the header. CMAF 222. Similarly, client device 40 in Figure 1 (e.g., recovery unit 52 in Figure 1) can determine the location of the CMAF 222 header by syntactically analyzing a bitstream that includes the CMAF 220 range and detecting the ftyp value. In response, recovery unit 52 can determine that CMAF 230 fragments follow the CMAF 222 header. Petition 870190098196, dated 10 / 01 / 2019, pp. 57 / 106 54 / 71 (for example, ftyp box 152 and moov box 154 of Figure 4), potentially also after one or more intervening sidx boxes, such as sidx boxes 162 (Figure 4).

[00111] Furthermore, each of the CMAF 230 fragments may include styp values ​​representative of whether the CMAF 230 fragments correspond only to CMAF fragments, CMAF segments, or CMAF parts, for example, in corresponding moof boxes 226A, 226B (moof boxes 226). Therefore, recovery unit 52 can determine whether one of the CMAF 230 fragments is only a CMAF fragment, a CMAF part, or a CMAF segment, according to the styp values ​​of the respective CMAF fragments in the respective moof boxes 226.

[00112] For example, the content preparation device 20 (Figure 1) can assign a value of cmfl to the styp element of one of the moof boxes 226 of a corresponding fragment among the CMAF fragments 230 to indicate that that fragment among the CMAF fragments 230 includes a CMAF part, a value of cmff' to indicate that that fragment among the CMAF fragments 230 is only a CMAF fragment, or a value of cmfs to indicate that that fragment among the CMAF fragments 230 is included in a CMAF segment. Similarly, recovery unit 52 can determine that one of the CMAF 230 fragments includes a CMAF part when a type element of one of the moof 226 boxes has a value of cmfl, that the CMAF fragment is only a CMAF fragment when the type element of one of the moof 226 boxes has a value of cmff, or that the CMAF fragment is included in a CMAF segment when Petition 870190098196, dated 10 / 01 / 2019, pp. 58 / 106 55 / 71 the styp element of one of the moof boxes 22 6 has a value of cmfs.

[00113] Figure 7 is a conceptual diagram illustrating an exemplary CMAF 240 segment. The CMAF 240 segment in Figure 7 can be included within a CMAF track file, following a CMAF header, for example, as shown in Figure 6. The CMAF 240 segment can conform to Table 4 above.

[00114] In the example in Figure 7, the CMAF 240 segment includes two exemplary CMAF 250A, 250B fragments (CMAF 250 fragments). Each of the CMAF 250 fragments includes a respective set of zero or more optional boxes, a moof box, and an mdat box. For example, the CMAF 250A fragment includes optional boxes 244A, moof box 246A, and mdat box 248A, while the CMAF 250B fragment includes optional boxes 244B, moof box 246B, and mdat box 248B. Thus, each of the CMAF 250 fragments can, in general, include elements similar to the elements of the CMAF 200 fragment in Figure 5. The CMAF 240 segment in Figure 7 can be included within a video file, such as video file 150 in Figure 4, where the CMAF 250 fragments can start at the beginning of film fragments 164 in Figure 4.

[00115] According to the techniques of this disclosure, content preparation device 20 (Figure 1) can assign a cmfs value to a styp value of the CMAF 250A fragment moof box 246A to indicate that the CMAF 250A fragment is included within and represents the beginning of the CMAF 240 segment. Similarly, the unit Petition 870190098196, dated 10 / 01 / 2019, pp. 59 / 106 56 / 71 of recovery 52 from Figure 1 can determine that the CMAF 250A fragment represents the beginning of the CMAF 240 segment in response to the determination that a styp value of the moof box 246A of the CMAF 250A fragment has a cmfs value.

[00116] Figures 8A and 8B are conceptual diagrams illustrating exemplary CMAF fragments and CMAF parts. In particular, Figure 8A illustrates an example of just one CMAF 260 fragment. That is, the CMAF 260 fragment includes the moof box 262, mdat box 264, and coded video sequence samples 266A-266L (coded video sequence samples 266). Figure 8B illustrates an example of a CMAF 270 fragment that includes the CMAF parts 272A-272D ​​(CMAF 272 parts). Each of the CMAF 272 parts can conform to Table 6 above. That is, in this example, each of the CMAF 272 parts includes a respective moof box 274A-274D (moof boxes 274), mdat boxes 276A-276D (mdat boxes 276), and respective encoded video sequence samples 278A-278L (encoded video sequence samples 276).

[00117] The CMAF 272 parts, as shown, can be included within the CMAF 270 fragment, which can be included within CMAF controls and / or CMAF segments, as discussed above. In one example, CMAF parts are the smallest atomic units that are handled by CMAF encoding, CMAF delivery, and CMAF reproducers. By dividing the CMAF 270 fragment into CMAF 272 parts, for example, as shown in Figure 8B, the media data from the samples of Petition 870190098196, dated 10 / 01 / 2019, pp. 60 / 106 57 / 71 encoded video sequence 278 can be emitted more frequently than the media data from the encoded video sequence samples 266 of Figure 8A. That is, the content preparation device 20 of Figure 1, for example, can emit each of the CMAF parts 272 at the respective encoder output times 280A-280D (encoder output times 280). In contrast, the content preparation device 20 can emit the entire CMAF fragment 260 at encoder output time 268. In this way, using CMAF parts, such as CMAF parts 272, can reduce the media data transport latency for a continuous transmission service.

[00118] The parts of CMAF 272 can be labeled as having styp values ​​of cmfl in the respective moof boxes 274, according to the techniques of this disclosure. That is, the content preparation device 20 can specify the value of cmfl in the respective moof boxes 274. Similarly, the retrieval unit 52 can determine that the CMAF 270 fragment includes parts of CMAF 272 based on the value of cmfl in the respective moof boxes 274. The retrieval unit 52 can also determine the beginning of each of the parts of CMAF 272 by performing syntactic analysis of the CMAF 270 fragment and detecting the value of cmfl for styp values ​​of the respective moof boxes 274.

[00119] In some examples, the CMAF parts may conform to the following restrictions: 1. A CMAF Fragment will include one or more ISO Base Media segments. Petition 870190098196, dated 10 / 01 / 2019, pp. 61 / 106 58 / 71 [ISOBMFF, 8.16], where each contains a MovieFragmentBox, followed by one or more MediaDataBoxes containing the samples that they reference. 2. A CMAF fragment will contain a MovieFragmentHeaderBox constrained as specified in ISO / IEC 23000-19 7.5.14. 3. Each TrackFragmentBox will contain a TrackFragmentBaseMediaDecodeTimeBox. 4. All media samples in a CMAF Fragment will be byte-addressed fsets in the TrackRunBox that are relative to the first byte of the MovieFragmentBox (see [ISOBMFF] 8.8.4). 5. A MovieFragmentBox part of CMAF may be preceded by other boxes, including a SegmentTypeBox, one or more ProducerReferenceTimeBoxes, and / or DASHEventMessageBoxes. (See 7.4.5 and Annex E for more information on Event Messages).

[00120] Figure 9 is a conceptual diagram illustrating an exemplary 300 system according to the techniques of this disclosure. In this example, the 300 system is divided into four logical portions: a manifest portion, a content offering portion, a delivery portion, and a platforms and players portion. The manifest portion and the content offering portion can, Petition 870190098196, dated 10 / 01 / 2019, pp. 62 / 106 59 / 71 generally correspond to content preparation device 20 in Figure 1, the delivery portion may correspond to server device 60 in Figure 1, and the platform and player portion may correspond to client device 40 in Figure 1.

[00121] In the example in Figure 9, the system manifest portion 300 includes DASH MPD 302, playlist 304 in M3U8 live streaming over HTTP (HLS), and an application 306. DASH MPD 302 references CMAF content 308, which is included in the system content offering portion 300. CMAF content 308 is provided to a content delivery network (CDN) 310, which provides streaming and / or selective streaming services as part of the system delivery portion 300. Various platforms and players in the system platforms and players portion 300 may receive media data from CDN 310, as a standalone HTTP live streaming player (HLS) 312, a device 314 for receiving HLS as an HTML-5 video markup, a standalone DASH player 316, a device 318 for receiving DASH as an HTML-5 video markup and / or a type 3 player based on HTML-5 MSE. The techniques of this disclosure can, in general, support a type of signaling for devices configured according to any or all of these exemplary use cases.

[00122] Figure 10 is a conceptual diagram illustrating an exemplary decomposition 330 within a WAVE application 336 using HTML-5 application programming interfaces (APIs) 338 between the platform 332, content 334 and application 336, each of Petition 870190098196, dated 10 / 01 / 2019, pp. 63 / 106 60 / 71 which can use data according to the techniques of this disclosure. The WAVE 334 device platform may have a set of capabilities that are accessible to the application 336 through HTML-5 APIs 338 and detailed codec capabilities. WAVE 332 content can be played on the WAVE 334 device platform within the WAVE 336 application. The WAVE 336 application can use the capabilities of the WAVE 334 platform device for media services.

[00123] Figure 11 is a conceptual diagram illustrating an exemplary box sequence and containment of a CMAF 350 part. In this example, lower boxes indicate containment within the box above. That is, the CMAF part includes the segment type box ('styp') 352, producer reference time event box ('prft') 354, film fragment box ('moof') 356, and media data box ('mdat'). The moof box 356, in turn, includes the film fragment header box ('mfhd') 360, protection-specific header box ('pssh') 362, and track fragment box ('traf') 364. The sequence of boxes contained within the traf box 364 as shown in Figure 11 is an example.In this example, the traf box 364 includes the track fragment header box ('tfhd') 370, track fragment execution box ('trun') 372, sample encryption box ('senc') 374, sample auxiliary information sizes box ('saiz') 376, sample auxiliary information for fsets box ('saio') 378, sample grouping box ('sbgp') 380, and sample group descriptions box ('sgpd') 382. The boxes shown with... Petition 870190098196, dated 10 / 01 / 2019, pp. 64 / 106 61 / 71 dashed outlines, such as styp box 352, prtf emsg 354, and pssh box 362, may be optional. Certain trafbox 364 boxes as shown in the bottom row are conditionally required when encryption was used, in some examples.

[00124] In one example, any CMAF Part or CMAF Fragment containing the initial samples of a CMAF Fragment are to conform to the CMAF Segment mark 'cmff' and the mark must be indicated in the 'styp.'

[00125] CMAF Headers, CMAF Fragments, and CMAF Parts can be packaged and referenced as CMAF Addressable Media Objects for storage and delivery, as described in Section 6.7 of the CMAF Media Object Model. Each CMAF Addressable Media Object can be referenced as a Resource by an external specification, for example MPEG DASH.

[00126] The CMAF Header, CMAF Parts, and CMAF Fragments can be made available as CMAF Addressable Resources by simple transformation methods, for example: • Directly, • By concatenating CMAF Fragments and sending them as a CMAF Segment, and / or • By concatenating the CMAF Header with all CMAF Fragments, possibly adding a SegmentIndexBox.

[00127] In CMAF fragment mode, a CMAF header can be available as an addressable object. In this mode, the CMAF Fragment can be made directly available as a Media Object. Petition 870190098196, dated 10 / 01 / 2019, pp. 65 / 106 62 / 71 Addressable CMAF.

[00128] In CMAF segment mode, CMAF segments can be used as discussed above, for example, in relation to Table 4 and Figure 7. A CMAF segment can be defined as a CMAF Addressable Media Object that contains one or more complete CMAF Fragments in presentation order. In some examples: 1. A CMAF Segment may contain Samples from each CMAF Fragment divided into multiple film fragments sequenced in decoding order. 2. A CMAF Segment can include a SegmentTypeBox that precedes the first MovieFragmentBox of each CMAF Fragment. The SegmentTypeBox can include the CMAF Segment tag 'emfs', and any compatible_brands listed in the CMAF Header FileTypeBox of the CMAF Track.

[00129] In CMAF part mode, the CMAF Header may be available as an addressable object. Each CMAF Fragment, in this mode, may be included in one or more CMAF Parts. The CMAF Part may be made available directly as a CMAF Addressable Media Object. The initial CMAF may include two CMAF Segment tags, 'cmff' and 'cmfl', to signal compatibility with the initial CMAF Fragment part as well as the CMAF Part. Non-Initial CMAF Parts may include the CMAF Segment tag 'cmfl' to signal the Petition 870190098196, dated 10 / 01 / 2019, pp. 66 / 106 63 / 71 compatibility with this segment format.

[00130] A CMAF track file can be a CMAF Addressable Media Object defined as a CMAF track stored as a single track in a BMFF ISO file, with the first CMAF Fragment baseMediaDecodeTime equal to zero. The CMAF Header and all CMAF Fragments can be included in a single CMAF Track File. In some instances, a CMAF track file conforms to the following constraints: 1. Additional boxes, such as SegmentIndexBoxes, may be present between the CMAF Header and the first CMAF Fragment. 2. If SegmentlndexBoxes exist, each subsegment referenced in the SegmentlndexBox will be a single CMAF Fragment contained in the CMAF Track File. 3. Emsg and prtfboxes contained in CMAF Fragments are kept in the track file. If an emsg or prtf is kept for a CMAF Fragment, then the SegmentlndexBox will reference the beginning of the CMAF fragment, that is, the earliest prtf or any emsg. 4. A Video CMAF Track File may contain an offset edit list to adjust the earliest presentation time of the first sample presented to the baseMediaDecodeTime of zero by subtracting any composition delay. Petition 870190098196, dated 10 / 01 / 2019, pp. 67 / 106 64 / 71 added by using umavO TrackRunBox using positive composition of fset values ​​to reorder video frames from decoding order to presentation order. See ISO / IEC 23000-19 7.5.12. 5. A vl TrackRunBox that uses negative fset composition can be used to adjust the composition time of the earliest presented Video Sample in each CMAF Fragment to its BaseMediaDecodeTime, and the earliest Video Sample in the CMAF Track File to zero, without using an offset edit list.

[00131] Figure 12 is a flowchart illustrating an exemplary method for generating a bitstream according to the techniques of this disclosure. The method in Figure 12 is explained in relation to content preparation device 20 (Figure 1). However, it should be understood that other devices can be configured to perform this or a similar method. For example, server device 60 can perform some or all of the steps in the method in Figure 12.

[00132] Initially, audio encoder 26 and video encoder 28 (Figure 1) encode media data, such as audio or video data respectively, to form encoded samples of the media data. The encapsulation unit 30 (Figure 1) then receives the encoded samples of the media data and generates a bitstream that Petition 870190098196, dated 10 / 01 / 2019, pp. 68 / 106 65 / 71 includes the encoded samples formatted according to CMAF and in accordance with the techniques of this disclosure. In particular, encapsulation unit 30 generates a CMAF header from a CMAF track file (400). Encapsulation unit 30 can generate the CMAF header according to Table 3 above. For example, encapsulation unit 30 can set a file type (ftyp) value of the CMAF header at the beginning of the CMAF header (402). Encapsulation unit 30 can also generate a movie box (moov) from the CMAF header, for example, which includes the moov box elements 154 of Figure 4.

[00133] The encapsulation unit 30 can then encapsulate the encoded media samples in the respective CMAF fragments (404). In several examples, the CMAF fragments may correspond to only CMAF fragments, CMAF fragments included in CMAF segments, or CMAF fragments that include parts of CMAF. Consequently, the encapsulation unit 30 can set segment type (styp) values ​​at the beginning of the CMAF fragments to indicate CMAF fragment beginnings and types for the CMAF fragments (e.g., only CMAF fragments, CMAF segments, or parts of CMAF). As noted above, the value of emfs can represent a CMAF segment, the value of cmff' can represent only a CMAF fragment, and the value of cmfl can represent a part of CMAF. The encapsulation unit 30 can set the styp values ​​in the respective moof boxes of the CMAF fragments.

[00134] The encapsulation unit 30 can then generate a bit stream (408) that includes the header Petition 870190098196, dated 10 / 01 / 2019, pp. 69 / 106 66 / 71 of CMAF and CMAF fragments, and send the bitstream to a client device (410), such as client device 40 (Figure 1). In some examples, content preparation device 20 may send the bitstream to server device 60, which may then send the bitstream to client device 40.

[00135] Thus, the method in Figure 12 represents an example of a method for generating a bitstream, wherein the method includes generating, by a processor implanted in the circuit set, a Common Media Application Format (CMAF) header from a CMAF track file; setting, by the processor, a value as a file type value (FTYP) of the CMAF header that indicates the beginning of the CMAF header; encapsulating, by the processor, one or more media data samples in one or more CMAF fragments following the CMAF header of the CMAF track file; and generating, by the processor, a bitstream that includes the CMAF header and the CMAF track file, wherein the one or more CMAF fragments follow the CMAF header in the CMAF track file.

[00136] Figure 13 is a flowchart illustrating an example of a method for processing media data in accordance with the techniques of this disclosure. The method in Figure 13 is explained in relation to client device 40 in Figure 1. However, it should be understood that other devices can be configured to perform this or a similar method in accordance with the techniques of this disclosure.

[00137] Initially, recovery unit 52 (Figure 1) of client device 40 performs the Petition 870190098196, dated 10 / 01 / 2019, pp. 70 / 106 67 / 71 Syntactic analysis of a bitstream that includes a CMAF track file (420). It should be understood that the recovery unit 52 may initially request the bitstream from, for example, the server device 60 or content preparation device 20 (Figure 1). While performing syntactic analysis of the bitstream, the recovery unit 52 may detect a file type (ftyp) value from the CMAF track file (422). As shown in Table 3 above, the ftyp value may be at the beginning of a CMAF header of the CMAF track file. Consequently, the recovery unit 52 may determine that the CMAF header starts with the ftyp value (424). The recovery unit 52 may further determine that the remainder of the CMAF header (e.g., a moov box) follows the ftyp value.

[00138] The recovery unit 52 can therefore determine that one or more CMAF fragments of the CMAF track file follow the CMAF header (and any sidx boxes, if present, for example, as shown in Table 2 above and Figure 4). In particular, the recovery unit 52 can continue to perform syntactic analysis of the bitstream following the CMAF header and detect one or more segment type (styp) values ​​following the CMAF header (426). The recovery unit 52 can detect the styp values ​​in the respective moof boxes of the CMAF fragments. According to the techniques of this disclosure, the recovery unit 52 can determine that each of the styp values ​​represents the beginning of a corresponding CMAF fragment. Furthermore, the recovery unit 52 can Petition 870190098196, dated 10 / 01 / 2019, pp. 71 / 106 68 / 71 determine types for CMAF fragments from their respective styp values. As discussed above, in some examples, the value “emfs” for styp may represent a CMAF segment, the value of “cmff” for styp may represent only a CMAF fragment, and the value of “cmfl” for styp may represent a part of CMAF.

[00139] Therefore, retrieval unit 52 can process the corresponding CMAF fragments starting at the respective styp values ​​according to the styp values ​​(428). For example, retrieval unit 52 can determine whether a CMAF fragment just follows the styp value, whether one or more CMAF fragments should be expected as part of a CMAF segment (e.g., as shown in Figure 7), or whether the CMAF fragment includes one or more CMAF parts (e.g., as shown in Figure 8B).

[00140] Thus, the method in Figure 13 represents an example of a media data processing method, wherein the method includes performing syntactic analysis, by a processor implanted in the circuit set, of a bitstream that includes data formatted according to the Common Media Application Format (CMAF), detecting, by the processor and during the syntactic analysis, a file type value (FTYP) for a CMAF track file of the bitstream, determining, by the processor, that a CMAF header of the CMAF track file starts with the FTYP value, and processing, by the processor, one or more CMAF fragments following the CMAF header of the CMAF track file.

[00141] In one or more examples, the functions Petition 870190098196, dated 10 / 01 / 2019, pp. 72 / 106 69 / 71 described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which correspond to tangible media such as data storage media, or communication media, which include any media that facilitates the transfer of a computer program from one place to another, for example, according to a communication protocol. In this way, computer-readable media may generally correspond to (1) tangible computer-readable storage media that are non-transient or (2) a communication medium such as a signal or carrier wave.Data storage media can be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, data structures, and / or code for the implementation of the techniques described in this disclosure. A computer program product may include computer-readable media.

[00142] By way of example, and not limitation, such computer-readable storage media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disc storage or other magnetic storage devices, flash memory, or any other media that can be used to store the desired program code in Petition 870190098196, dated 10 / 01 / 2019, pp. 73 / 106 70 / 71 form of instructions or data structures that can be accessed by a computer. Furthermore, any connection is properly termed computer-readable media. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital line-of-sale (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are instead directed to non-transient and tangible storage media.Magnetic disk and optical disk, as used in this document, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, wherein magnetic disks often reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the foregoing should also be included within the scope of computer-readable media.

[00143] Instructions can be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable logic arrays (FPGAs), or other equivalent integrated logic circuit sets. Petition 870190098196, dated 10 / 01 / 2019, pp. 74 / 106 71 / 71 or distinct. Consequently, the term processor, as used herein, may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some respects, the functionality described herein may be provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[00144] The techniques of this disclosure can be deployed in a wide variety of devices or appliances, including a handset, an integrated circuit (IC), or an array of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize the functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require implementation by different hardware units. Instead, as described above, multiple units can be combined into a codec hardware unit or provided by a collection of interoperable hardware units, including one or more processors, as described above, in combination with suitable software and / or firmware.

[00145] Several examples have been described. These and other examples are within the scope of the following claims. Petition 870190098196, dated 10 / 01 / 2019, pp. 75 / 106

Claims

1 / 4 CLAIMS 1. A method for processing media data, the method characterized in that it comprises: analyzing, by a processor implemented in a circuit set, a bit stream that includes data formatted according to the Common Media Application Format, CMAF, the bit stream that includes a CMAF track file comprising a CMAF header (222) that includes a file type box, FTYP, at the beginning of the CMAF header (222) and the one or more CMAF fragments (230A, 230B) located in the bit stream after the CMAF header (222); detecting, by the processor and during the analysis, the FTYP value for the CMAF track file of the bit stream; determining, by the processor, the location of the CMAF header (222) of the CMAF track file that uses the FTYP value; determine, by the processor, that one or more CMAF fragments (230A, 230B) follow the CMAF header (222);and to process, by the processor, one or more CMAF fragments (230A, 230B) from the CMAF strip file, wherein processing the one or more CMAF fragments (230A, 230B) comprises: detecting one or more segment type values, STYP, in the bitstream, wherein the STYP value has a cmff value representative of the CMAF fragments (230A, 230B) containing the initial samples of the CMAF fragment; determining that each of the one or more STYP values ​​corresponds to the beginning of a respective fragment of the CMAF fragments (230A, 230B); and processing each of the CMAF fragments (230A, 230B) starting from the corresponding STYP value.

2. Method according to claim 1, characterized in that processing one or more CMAF fragments (230A, 230B) comprises determining that the data following the CMAF header (222) represent one or more CMAF fragments (230A, 230B) in response to the detection of the FTYP value.

3. Method for generating a bitstream that includes media data, the method characterized in that it comprises: generating, by a processor implemented in a circuit set, a Common Media Application Format, CMAF, header (222) of a CMAF track file; setting, by the processor, a value for a file type value, FTYP, of the CMAF header (222) that indicates the beginning of the CMAF header (222); encapsulating, by the processor, one or more media data samples in one or more CMAF fragments (230A, 230B) following the CMAF header (222) of the CMAF track file; and generate, by the processor, a bit stream that includes the CMAF (222) header and one or more CMAF (230A, 230B) fragments, one or more CMAF (230A, 230B) fragments following the CMAF (222) header in the CMAF strip file, further comprising: determining types for each of the CMAF (230A, 230B) fragments;and define segment type values, STYP, of cmff” for each of the CMAF fragments (230A, 230B) that contain the initial samples of the CMAF fragment, the STYP values ​​being at the beginning of the corresponding CMAF fragments (230A, 230B).

4. Memory characterized by comprising instructions stored therein which, when executed, cause a processor to perform the methods defined in any of claims 1 to 3.

5. Device for processing media data, the device characterized by comprising: means for analyzing a bitstream that includes data formatted according to the Common Media Application Format, CMAF, the bitstream that includes a CMAF track file comprising a CMAF header (222) that includes a file type box, FTYP, at the beginning of the CMAF header (222) and the one or more CMAF fragments (230A, 230B) located in the bitstream after the CMAF header (222); means for detecting during the analysis, the FTYP value for the CMAF track file from the bitstream; means for determining the location of the CMAF header (222) from the CMAF track file that uses the FTYP value; means for determining that one or more CMAF fragments (230A, 230B) follow the CMAF header (222);and means for processing one or more CMAF (230A, 230B) fragments from the CMAF track file, wherein processing one or more CMAF (230A, 230B) fragments comprises: detecting one or more segment type values, STYP, in the bitstream, wherein the STYP value has a cmff value representative of the CMAF (230A, 230B) fragments containing the initial samples of the CMAF fragment; determining that each of the one or more STYP values ​​corresponds to the beginning of a respective fragment of the CMAF (230A, 230B) fragments; and processing each of the CMAF (230A, 230B) fragments starting from the corresponding STYP value. Petition 870250035104, dated 04 / 30 / 2025, p. 16 / 18 4 / 4; 6. Device for generating a bitstream that includes media data, the device characterized by comprising: means for generating a Common Media Application Format, CMAF, (222) header from a CMAF track file; means for setting a value for a file type value, FTYP, of the CMAF (222) header indicating the start of the CMAF (222) header; means for encapsulating one or more media data samples in one or more CMAF (230A, 230B) fragments following the CMAF (222) header from the CMAF track file; means for generating a bitstream that includes the CMAF (222) header and the one or more CMAF (230A, 230B) fragments following the CMAF (222) header in the CMAF track file; means to determine types for each of the CMAF fragments (230A, 230B);and means to define segment type values, STYP, of cmff for each of the CMAF fragments (230A, 230B) that contain the initial samples of the CMAF fragment. Petition 870250035104, dated 04 / 30 / 2025, pp. 17 / 18;

Images