Automatic generation of video content in response to network disruption

Abstract

An example apparatus for presenting media data includes a memory configured to store media data; and one or more processors implemented in the circuitry and configured to: receive a first set of media data of a media bitstream; in response to determining that a second set of media data following the first set of media data of the media bitstream will not be received within the time period, predictively generating replacement media data for the second set of media data using at least a subset of the first set of media data; and presenting the first set of media data and the replacement media data.

Description

[0001] This application claims priority to U.S. Patent Application No. 17 / 933,791, filed on September 20, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present disclosure relates to transmission of media data. Background Art

[0003] Digital video capabilities may be incorporated into a wide range of devices, including digital televisions, digital direct broadcast systems, wireless broadcast systems, personal digital assistants (PDAs), laptop or desktop computers, digital cameras, digital recording devices, digital media players, video gaming devices, video game consoles, cellular or satellite radio telephones, video teleconferencing equipment, etc. Digital video devices implement video 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 known as High Efficiency Video Coding (HEVC)), and extensions of such standards, to more efficiently send and receive digital video information.

[0004] Video compression techniques perform spatial prediction and / or temporal prediction to reduce or remove the inherent redundancy in a video sequence. For block-based video coding, a video frame or slice may be segmented into macroblocks. Each macroblock may be further segmented. Macroblocks in an intra-coded (I) frame or slice are encoded using spatial prediction relative to neighboring macroblocks. Macroblocks in an inter-coded (P or B) frame or slice may use spatial prediction relative to neighboring macroblocks in the same frame or slice or temporal prediction relative to other reference frames.

[0005] After the video data has been encoded, the video data may be packaged for transmission or storage. The video data may be assembled into a video file that conforms to any of a number of standards, such as the International Organization for Standardization (ISO) base media file format and its extensions, e.g., AVC. Summary of the invention

[0006] In general, the present disclosure describes techniques for automatically generating media content (e.g., image content, video content, and / or audio content) in response to determining that the requested media content will not be received within a specific time period (e.g., a time period of availability). For example, media data can be streamed from a source device to a destination device via a computer-based network. A network interruption (e.g., a connection interruption between a source device and a destination device) can prevent a portion of the media data from being sent from the source device to the destination device in a timely manner to allow seamless playback of subsequent media data. The network interruption can be caused by network errors such as packet loss and / or during handover between cells of a radio access network (RAN).

[0007] In response to such a network interruption, the destination device can generate replacement media data for media data that will not be delivered to the destination device. For example, the destination device can apply artificial intelligence and / or machine learning processes to generate replacement media data. The media data can be part of a live media session between two user devices, such as a multimedia call (e.g., a video conference call or an extended reality (XR) session, such as an augmented reality (AR), mixed reality (MR), or virtual reality (VR) session). In this way, the destination device can avoid requesting retransmission of media data that will not be delivered (which can avoid increasing latency in the media communication session), while also improving the user experience by avoiding black screens or duplicated / copied frames.

[0008] In one example, a method for presenting media data includes: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received within a time period, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0009] In another example, a device for presenting media data includes: a memory configured to store media data; and one or more processors implemented in a circuit and configured to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received within a time period, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0010] In another example, an apparatus for presenting media data includes: a device for receiving a first media data set of a media bitstream; a device for predictively generating replacement media data for a second media data set following the first media data set in response to determining that the media bitstream will not be received within a time period, using the first media data set; and a device for presenting the first media data set and the replacement media data.

[0011] In another example, a computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received within a time period, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

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

[0013] Figure 1 is a block diagram illustrating an example system that implements techniques for streaming media data over a network.

[0014] Figure 2 is a block diagram illustrating an example collection of components of a retrieval unit.

[0015] Figure 3 is a conceptual diagram illustrating elements of example multimedia content.

[0016] Figure 4 is a block diagram illustrating elements of an example video file that may correspond to a segment of a representation.

[0017] Figure 5 is a conceptual diagram illustrating an example of generating a replacement frame according to the technology of the present disclosure.

[0018] Figure 6 is a flow chart illustrating an example method of generating and presenting replacement media data according to the techniques of this disclosure.

[0019] Figure 7 is a flow chart illustrating another example method of generating and presenting replacement media data according to the techniques of this disclosure.

[0020] Figure 8is a flow chart illustrating an example method of generating and presenting media data according to the techniques of this disclosure.

[0021] Fig. 9 is a block diagram illustrating an example system including devices that may be configured to perform the techniques of this disclosure.

[0022] Fig.10 is a block diagram illustrating an example system including a user equipment (UE) device and a companion device. DETAILED DESCRIPTION

[0023] In general, the present disclosure describes techniques for generating replacement media data for a media streaming session between two or more media devices. For example, two user equipment (UE) devices may participate in a multimedia conference call or multimedia session, such as a video conference call or an extended reality (XR) session, e.g., an augmented reality (AR), mixed reality (MR), or virtual reality (VR) session. The two UE devices may exchange media data via a computer-based network (e.g., a cellular network, a local area network, or a short-range data transmission network).

[0024] For example, one or two UE devices may be carried by a user moving between cells of a radio access network (RAN).When moving between cells, the UE device may perform a handover procedure from a base station of one cell to a base station of a different cell.

[0025] During such a handover, the UE device and the base station may exchange radio resource control (RRC) messages and follow a random access channel (RACH) procedure. The RACH procedure may take approximately 50 ms or longer to execute. When a handover is performed from one cell to another, data transmission as part of an ongoing communication session (such as a media conference call) is interrupted, so that multiple video frames (or other media data, such as XR data or image data) will not meet the delivery deadline, which may significantly affect the user's experience.

[0026] A UE device according to the technology of the present disclosure may detect the network interruption, and in response, generate replacement media data for media data that will not be received within a time period due to the interruption, rather than simply presenting a black screen or a copied (e.g., duplicated) video frame. The media data that will not be received may be media data that will be completely lost, destroyed, and / or delayed to the extent that the delayed media data arrives later than the expected presentation time at the UE device. The UE device may use artificial intelligence (AI) and / or machine learning (ML) processes to generate replacement media data. The UE device may provide the most recently received media data to the AI / ML process, and the AI / ML process may predictively generate replacement media data for media data that will not be received within a time period due to the network interruption. The time period may be a time when the media data would otherwise be available (e.g., decodable and presentable).

[0027] Certain applications (e.g., Apple FaceTime, Microsoft Teams, Zoom Cloud Meeting, Google Meet, Facebook Messenger, etc.) installed on the UE that perform media communication sessions can be configured to allow enabling or disabling the generation of replacement media data according to the technology of the present disclosure. For example, the application can be configured to enable or disable the generation of replacement media data.

[0028] The UE device may request user consent to generate replacement media data before initiating (or establishing) a media session, when initiating (or establishing) a media session, and / or in response to detecting a network interruption, for example, as a setting for a media conferencing application. In some cases, the user may not want to have replacement media data, for example, if the media session involves a newsworthy event, such as a live sporting event, a political event, or other such event. Similarly, the UE device may be configured to not generate replacement data for certain types of media data (such as pre-recorded movies or television programs) to avoid intellectual property (e.g., copyright) rights infringement and / or certain types of media sessions (such as personal video conference calls (as opposed to work-related sessions)). In other words, in some implementations, whether to allow (or enable) the generation of replacement media data at the UE device can be further (or alternatively) based on one or more characteristics of the media data, the type of media data, and / or the type of media session.

[0029] By applying the techniques of the present disclosure, a UE device can generate replacement media data in response to determining that certain media data will not be received within a time period (e.g., a time period during which the media data is available (decodable and presentable by a specified output time)). By performing these techniques, the UE device can avoid requesting retransmission of media data that will not be received, which will introduce latency into the media streaming session and consume additional network resources (e.g., bandwidth). Likewise, the UE device can also present replacement media data, which is an improvement in the user experience of presenting copied (e.g., duplicated) frames or a blank screen. In this way, the techniques of the present disclosure provide technical improvements to the fields of media transmission, generation, and presentation, as well as technical improvements to the operation of UE devices and other network devices involved in media transmission and presentation.

[0030] The techniques of this disclosure may be applied to video files that conform to video data encapsulated according to any of the ISO base media file format, the scalable video coding (SVC) file format, the advanced video coding (AVC) file format, the third generation partnership project (3GPP) file format, and / or the multi-view video coding (MVC) file format, or other similar video file formats.

[0031] In HTTP streaming, frequently used operations include HEAD, GET, and partial GET. The HEAD operation retrieves the header of a file associated with a given uniform resource locator (URL) or uniform resource name (URN), without retrieving the payload associated with the URL or URN. The GET operation retrieves the entire file associated with a given URL or URN. The partial GET operation receives a byte range as an input parameter and retrieves a continuous number of bytes of the file, where the number of bytes corresponds to the received byte range. Therefore, movie fragments can be provided for HTTP streaming, because the partial GET operation can obtain one or more individual movie fragments. In a movie fragment, there may be several track fragments of different tracks. In HTTP streaming, media presentation may be a structured collection of data accessible to a client. A client may request and download media data information to present a streaming service to a user.

[0032] In the example of streaming 3GPP data using HTTP streaming, there may be multiple representations of video and / or audio data of multimedia content. As explained below, different representations may correspond to different coding characteristics (e.g., different profiles or levels of a video coding standard), different coding standards or extensions of a coding standard (e.g., multi-view and / or scalable extensions), or different bit rates. A list of such representations may be defined in a media presentation description (MPD) data structure. A media presentation may correspond to a structured collection of data accessible to an HTTP streaming client device. An HTTP streaming client device may request and download media data information to present a streaming service to a user of the client device. A media presentation may be described in an MPD data structure, which may include updates to the MPD.

[0033] A media presentation may contain a sequence of one or more periods. Each period may extend until the beginning of the next period, or in the case of the last period until the end of the media presentation. Each period may contain one or more representations for the same media content. A representation may be one of several alternative coded versions of audio, video, timed text, or other such data. Representations may differ by encoding type, for example, by the bit rate, resolution, and / or codec used for video data, and by the bit rate, language, and / or codec used for audio data. The term representation may be used to refer to a section of coded audio or video data that corresponds to a specific period of multimedia content and is coded in a specific manner.

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

[0035] 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, an initialization segment may contain initialization information for accessing a representation. Generally, an initialization segment does not contain media data. A segment may be uniquely referenced by an identifier, such as a uniform resource locator (URL), a uniform resource name (URN), or a uniform resource identifier (URI). The MPD may provide an identifier for each segment. In some examples, the MPD may also provide a byte range in the form of a range attribute, which may correspond to data for a segment within a file accessible by a URL, URN, or URI.

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

[0037] Figure 1 is a block diagram illustrating an example system 10 implementing techniques for streaming media data over a network. In this example, system 10 includes content preparation device 20, server device 60, and client device 40. Client device 40 and server device 60 are communicatively coupled via network 74, which may include the Internet. In some cases, connection via network 74 or other connection to the devices may encompass a wireless wide area network (WWAN), a wireless local area network (WLAN), Bluetooth, or other long or short range wireless connection. In some examples, content preparation device 20 and server device 60 may also be coupled via network 74 or another network, or may be directly communicatively coupled. In some examples, content preparation device 20 and server device 60 may include the same device.

[0038] exist Figure 1In the example of , content preparation device 20 includes an audio source 22 and a video source 24. Audio source 22 may include, for example, a microphone that generates an electrical signal representing captured audio data to be encoded by audio encoder 26. Alternatively, audio source 22 may include a storage medium storing previously recorded audio data, an audio data generator such as a computerized synthesizer, or any other audio data source. Video source 24 may include a camera that generates 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. In all examples, content preparation device 20 is not necessarily communicatively coupled to server device 60, but rather may store multimedia content to a separate medium that is read by server device 60.

[0039] The raw audio and video data may include analog or digital data. The analog data may be digitized before being encoded by the audio encoder 26 and / or the video encoder 28. The audio source 22 may obtain audio data from the speaking participant while the speaking participant is speaking, and the video source 24 may simultaneously obtain video data of the speaking participant. In other examples, the audio source 22 may include a computer-readable storage medium containing stored audio data, and the video source 24 may include a computer-readable storage medium containing stored video data. In this way, the techniques described in the present disclosure may be applied to live, streaming, real-time audio and video data or archived, pre-recorded audio and video data.

[0040] An audio frame corresponding to a video frame is typically an audio frame containing audio data that is captured (or generated) by audio source 22 at the same time as the video data captured (or generated) by video source 24 contained within the video frame. For example, although a speaking participant typically generates audio data by speaking, audio source 22 captures audio data and video source 24 captures video data of the speaking participant simultaneously (i.e., at the same time as audio source 22 captures audio data). Thus, an audio frame may correspond in time to one or more specific video frames. Thus, an audio frame corresponding to a video frame generally corresponds to a situation where audio data and video data are captured simultaneously and the audio frame and video frame include the simultaneously captured audio data and video data, respectively.

[0041] In some examples, audio encoder 26 may encode a timestamp in each encoded audio frame indicating the time at which the audio data of the encoded audio frame was recorded, and similarly, video encoder 28 may encode a timestamp in each encoded video frame indicating the time at which the video data of the encoded video frame was recorded. In such examples, an audio frame corresponding to a video frame may include an audio frame including a timestamp and a video frame including the same timestamp. Content preparation device 20 may include an internal clock from which audio encoder 26 and / or video encoder 28 may generate timestamps, or which audio source 22 and video source 24 may use to associate audio and video data with timestamps, respectively.

[0042] In some examples, audio source 22 may send data corresponding to the time at which the audio data was recorded to audio encoder 26, and video source 24 may send data corresponding to the time at which the video data was recorded to video encoder 28. 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, but not necessarily an absolute time at which the audio data was recorded, and similarly, video encoder 28 may also use the sequence identifier to indicate a relative temporal ordering of the encoded video data. Similarly, in some examples, the sequence identifier may be mapped or otherwise associated with a timestamp.

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

[0044] Many video coding standards (e.g., ITU-T H.264 / AVC, High Efficiency Video Coding (HEVC), Versatile Video Coding (VVC), Enhanced Video Coding (EVC), and AOMedia Video 1 (AV1)) define the syntax, semantics, and decoding process of error-free bitstreams, any of which conforms to a certain profile or level. Video coding standards generally do not specify encoders, but it is the task of the encoder to ensure that the generated bitstream is compliant with the standard for the decoder. In the context of video coding standards, a "profile" corresponds to a subset of algorithms, features, or tools and the constraints applied thereto. For example, as defined by the H.264 standard, a "profile" is a subset of the entire bitstream syntax specified by the H.264 standard. A "level" corresponds to a limit on decoder resource consumption, such as decoder memory and computation, which is related to the resolution, bit rate, and block processing rate of the picture. The profile can be signaled with a profile_idc (profile indicator) value, while the level can be signaled with a level_idc (level indicator) value.

[0045] For example, the H.264 standard recognizes that, within the limits imposed by the syntax of a given profile, large variations in the performance of encoders and decoders may still be required, depending on the values ​​taken by syntax elements in the bitstream (e.g., the specified size of the decoded picture). The H.264 standard also recognizes that in many applications, it is neither practical nor economical to implement a decoder that can handle all hypothetical uses of the syntax within a particular profile. Therefore, the H.264 standard defines a "level" as a set of specified constraints imposed on the values ​​of syntax elements in the bitstream. These constraints can be simple restrictions on values. Alternatively, these constraints can take the form of constraints on arithmetic combinations of values ​​(e.g., picture width multiplied by picture height multiplied by the number of pictures decoded per second). The H.264 standard also provides that a separate implementation can support different levels for each supported profile.

[0046] Decoders that conform to the profile generally support all features defined in the profile. For example, as a decoding feature, B picture decoding is not supported in the baseline profile of H.264 / AVC, but B picture decoding is supported in other profiles of H.264 / AVC. Decoders that conform to the level should be able to decode any bitstream that does not require resources beyond the limits defined in the level. The definition of profiles and levels may contribute to interpretability. For example, during video transmission, a pair of profile and level definitions may be negotiated and agreed upon for the entire transmission session. More specifically, in H.264 / AVC, the level may define the number of macroblocks that need to be processed, the size of the decoded picture buffer (DPB), the size of the decoded picture buffer (CPB), the range of vertical motion vectors, the maximum number of motion vectors per two consecutive MBs, and whether the B block can have a sub-macroblock partition of less than 8×8 pixels. In this way, the decoder can determine whether the decoder can properly decode the bitstream.

[0047] exist Figure 1 In the example of , encapsulation unit 30 of content preparation device 20 receives an elementary stream including decoded video data from video encoder 28, and receives an elementary stream including decoded audio data from audio encoder 26. In some examples, video encoder 28 and audio encoder 26 may each include a packetizer for forming PES packets from the encoded data. In other examples, video encoder 28 and audio encoder 26 may each interface with a respective packetizer for forming PES packets from the encoded data. In other examples, encapsulation unit 30 may include a packetizer for forming PES packets from the encoded audio and video data.

[0048] Video encoder 28 may encode video data of multimedia content in a variety of ways, thereby producing different representations of the multimedia content at various bit rates and with various characteristics, such as pixel resolution, frame rate, compliance with various decoding standards, compliance with various profiles and / or profile levels of various decoding standards, representations with one or more views (e.g., for two-dimensional or three-dimensional playback), or other such characteristics. As used in the present disclosure, a representation may include one of audio data, video data, text data (e.g., for closed captions), or other such data. A representation may include an elementary stream, such as an audio elementary stream or a video elementary stream. Each PES packet may include a stream_id that identifies the elementary stream to which the PES packet belongs. Encapsulation unit 30 is responsible for assembling the elementary streams into video files (e.g., segments) of various representations.

[0049] Encapsulation unit 30 receives PES packets of elementary streams represented from audio encoder 26 and video encoder 28, and forms corresponding network abstraction layer (NAL) units from the PES packets. Coded video segments may be organized into NAL units that provide a "network-friendly" video representation that addresses applications such as video telephony, storage, broadcast, or streaming. NAL units may be classified into video coding layer (VCL) NAL units and non-VCL NAL units. VCL units may contain the core compression engine and may include block, macroblock, and / or slice level data. Other NAL units may be non-VCL NAL units. In some examples, a coded picture in one time instance (typically presented as a primary coded picture) may be contained in an access unit, which may include one or more NAL units.

[0050] Non-VCL NAL units may include parameter set NAL units and SEI NAL units, among others. Parameter sets may contain sequence-level header information (in a sequence parameter set (SPS)) and infrequently changing picture-level header information (in a picture parameter set (PPS)). With parameter sets (e.g., PPS and SPS), infrequently changing information does not need to be repeated for each sequence or picture; therefore, coding efficiency may be improved. In addition, the use of parameter sets may enable out-of-band transmission of important header information, thereby avoiding the need for redundant transmission for error resilience. In an out-of-band transmission example, parameter set NAL units may be sent on a different channel than other NAL units (e.g., SEI NAL units).

[0051] Supplemental enhancement information (SEI) may contain information that is not necessary for decoding coded picture samples from VCL NAL units, but may assist processes related to decoding, display, error recovery, and other purposes. SEI messages may be included in non-VCL NAL units. SEI messages are a normative part of some standard specifications and are therefore not always mandatory for standard-compliant decoder implementations. SEI messages may be sequence-level SEI messages or picture-level SEI messages. Some sequence-level information may be included in SEI messages, such as scalability information SEI messages in the example of SVC and view scalability information SEI messages in MVC. These example SEI messages may convey information about, for example, extraction of operation points and characteristics of operation points. In addition, encapsulation unit 30 may form a manifest file, such as a media presentation descriptor (MPD) that describes the characteristics of a representation. Encapsulation unit 30 may format the MPD according to extensible markup language (XML).

[0052] Encapsulation unit 30 may provide data of one or more representations of multimedia content along with a manifest file (e.g., an MPD) to output interface 32. Output interface 32 may include a network interface or an interface for writing to a storage medium, such as a universal serial bus (USB) interface, a CD or DVD writer or burner, an interface to a magnetic or flash storage medium, or other interface for storing or transmitting media data. Encapsulation unit 30 may provide data of each of the representations of multimedia content to output interface 32, which may send the data to server device 60 via a network transmission or storage medium. Figure 1 In the example of , the server device 60 includes a storage medium 62 storing various multimedia content 64, each multimedia content 64 including a corresponding manifest file 66 and one or more representations 68A to 68N (representations 68). In some examples, the output interface 32 can also send data directly to the network 74.

[0053] In some examples, representations 68 may be separated into adaptation sets. That is, various subsets of representations 68 may include respective common sets of characteristics, such as codecs, profiles and levels, resolutions, number of views, file formats of segments, text type information that may identify the language or other characteristics of text to be displayed with the representations and / or audio data to be decoded and presented (e.g., by speakers), camera angle information that may describe the camera angle or real-world camera perspective of a scene of a representation in an adaptation set, rating information that describes suitability of the content for a particular audience, or the like.

[0054] The manifest file 66 may include data indicating a subset of representations 68 corresponding to a particular adaptation set and common characteristics of the adaptation set. The manifest file 66 may also include data indicating individual characteristics (e.g., bit rate) of individual representations of the adaptation set. In this way, the adaptation set may provide simplified network bandwidth adaptation. A sub-element of the adaptation set element of the manifest file 66 may be used to indicate a representation in an adaptation set.

[0055] The server device 60 includes a request processing unit 70 and a network interface 72. In some examples, the server device 60 may include multiple network interfaces. In addition, any or all features of the server device 60 may be implemented on other devices of the content delivery network, such as routers, bridges, proxy devices, switches, or other devices. In some examples, an intermediate device of the content delivery network may cache data of the multimedia content 64 and include components that substantially conform to the components of the server device 60. Typically, the network interface 72 is configured to send and receive data via the network 74.

[0056] The request processing unit 70 is configured to receive a network request for data of the storage medium 62 from a client device (e.g., the client device 40). For example, the request processing unit 70 may implement the Hypertext Transfer Protocol (HTTP) version 1.1, as described in RFC2616, "Hypertext Transfer Protocol-HTTP / 1.1" by R. Fielding et al., Network Working Group, IETF, June 1999. That is, the request processing unit 70 may be configured to receive an HTTP GET or partial GET request, and provide data of the multimedia content 64 in response to the request. The request may specify a segment of one of the representations 68, for example, using a URL of the segment. In some examples, the request may also specify one or more byte ranges of the segment, thus comprising a partial GET request. The request processing unit 70 may further be configured to service an HTTP HEAD request to provide header data of a segment of one of the representations 68. In any case, the request processing unit 70 may be configured to process the request to provide the requested data to the requesting device, such as the client device 40.

[0057] Additionally or alternatively, the request processing unit 70 may be configured to deliver media data via a broadcast or multicast protocol (e.g., eMBMS). The content preparation device 20 may create DASH segments and / or sub-segments in substantially the same manner as described, but the server device 60 may deliver these segments or sub-segments using eMBMS or another broadcast or multicast network transmission protocol. For example, the request processing unit 70 may be configured to receive a multicast group joining request from a client device 40. That is, the server device 60 may announce an Internet Protocol (IP) address associated with a multicast group to client devices (including the client device 40) associated with a particular media content (e.g., a broadcast of a live event). The client device 40 may in turn submit a request to join the multicast group. The request may be propagated throughout the network 74 (e.g., routers constituting the network 74) such that the routers direct traffic destined for the IP address associated with the multicast group to subscribing client devices, such as the client device 40.

[0058] like Figure 1 As illustrated in the example of , multimedia content 64 includes a 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 descriptions may include, for example, codec information, profile values, level values, bit rates, and other descriptive characteristics of representation 68. Client device 40 may retrieve the MPD for the media presentation to determine how to access segments of representation 68.

[0059] Specifically, the retrieval unit 52 may retrieve configuration data (not shown) of the 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 a language preference selected by a user of the client device 40, one or more camera viewing angles corresponding to a depth preference set by a user of the client device 40, and / or a rating preference selected by a user of the client device 40. The retrieval unit 52 may include, for example, a web browser or media client configured to submit 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 the client device 40. In some examples, all or part of the functionality described with respect to the retrieval unit 52 may be implemented in hardware, or a combination of hardware, software, and / or firmware, where the necessary hardware may be provided to execute instructions for the software or firmware.

[0060] Retrieval unit 52 may compare the decoding and rendering capabilities of client device 40 with characteristics of representation 68 indicated by information of manifest file 66. Retrieval unit 52 may initially retrieve at least a portion of manifest file 66 to determine the characteristics of representation 68. For example, retrieval unit 52 may request a portion of manifest file 66 that describes characteristics of one or more adaptation sets. Retrieval unit 52 may select a subset of representation 68 (e.g., an adaptation set) that has characteristics that can be satisfied by the decoding and rendering capabilities of client device 40. Retrieval unit 52 may then determine the bit rates of the representations in the adaptation set, determine the currently available amount of network bandwidth, and retrieve segments from one of the representations that has a bit rate that can be satisfied by the network bandwidth.

[0061] In general, a higher bit rate representation may produce a higher quality video playback, while a lower bit rate representation may provide adequate quality video playback when the available network bandwidth decreases. Thus, when the available network bandwidth is relatively high, the retrieval unit 52 may retrieve data from a relatively high bit rate representation, and when the available network bandwidth is low, the retrieval unit 52 may retrieve data from a relatively low bit rate representation. In this manner, the client device 40 may stream multimedia data over the network 74 while also adapting to the changing network bandwidth availability of the network 74.

[0062] Additionally or alternatively, the retrieval unit 52 may be configured to receive data according to a broadcast or multicast network protocol (e.g., eMBMS or IP multicast). In such an example, the retrieval unit 52 may submit a request to join a multicast network group associated with a particular media content. After joining the multicast group, the retrieval unit 52 may receive data for the multicast group without issuing further requests to the server device 60 or the content preparation device 20. When the data of the multicast group is no longer needed, the retrieval unit 52 may submit a request to leave the multicast group, for example to stop playback or change the channel to a different multicast group.

[0063] The network interface 54 may receive data for the segments of the selected representation and provide the data to the retrieval unit 52, which in turn may provide the segments to the decapsulation unit 50. The decapsulation unit 50 may decapsulate the elements of the video file into constituent PES streams, depacketize the PES streams to retrieve the encoded data, and send the encoded data to the audio decoder 46 or the video decoder 48, depending on whether the encoded data is part of an audio stream or a video stream (e.g., as indicated by a PES packet header of the stream). The audio decoder 46 decodes the encoded audio data and sends the decoded audio data to the audio output 42, while the video decoder 48 decodes the encoded video data and sends the decoded video data (which may include multiple views of the stream) to the video output 44.

[0064] The video encoder 28, video decoder 48, audio encoder 26, audio decoder 46, encapsulation unit 30, retrieval unit 52, and decapsulation unit 50 may each be implemented as any of a variety of suitable processing circuits, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic circuits, software, hardware, firmware, or any combination thereof, as applicable. Each of the video encoder 28 and the video decoder 48 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined video encoder / decoder (CODEC). Similarly, each of the audio encoder 26 and the audio decoder 46 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined CODEC. An apparatus including the video encoder 28, video decoder 48, audio encoder 26, audio decoder 46, encapsulation unit 30, retrieval unit 52, and / or decapsulation unit 50 may include an integrated circuit, a microprocessor, and / or a wireless communication device, such as a cellular phone.

[0065] Client device 40, server device 60, and / or content preparation device 20 may be configured to operate according to the techniques of this disclosure. For purposes of example, this disclosure describes these techniques with respect to client device 40 and server device 60. However, it should be understood that content preparation device 20 may also be configured to perform these techniques instead of (or in addition to) server device 60.

[0066] Encapsulation unit 30 may form a NAL unit including a header identifying the program to which the NAL unit belongs and a payload, such as audio data, video data, or data describing the transport or program stream to which the NAL unit corresponds. For example, in H.264 / AVC, a NAL unit includes a 1-byte header and payloads of varying sizes. A NAL unit including video data in its payload may include video data at various levels of granularity. For example, a NAL unit may include a block of video data, multiple blocks, a slice of video data, or an entire picture of video data. Encapsulation unit 30 may receive encoded video data in the form of PES packets of elementary streams from video encoder 28. Encapsulation unit 30 may associate each elementary stream with a corresponding program.

[0067] Encapsulation unit 30 may also assemble access units from multiple NAL units. In general, an access unit may include one or more NAL units representing a frame of video data and audio data corresponding to the frame (when such audio data is available). An access unit typically includes all NAL units for one output time instance, for example, all audio and video data for one time instance. For example, if each view has a frame rate of 20 frames per second (fps), each time instance may correspond to a time interval of 0.05 seconds. During this time interval, specific frames of all views of the same access unit (same time instance) may be rendered simultaneously. In one example, an access unit may include a coded picture in one time instance, which may be presented as a primary coded picture.

[0068] Thus, an access unit may include all audio and video frames of a common time instance, for example, all views corresponding to time X. The present disclosure also refers to the coded pictures of a specific view as "view components", that is, a view component may include coded pictures (or frames) of a specific view at a specific time. Thus, an access unit may be defined as including all view components of a common time instance. The decoding order of access units does not necessarily need to be the same as the output or display order.

[0069] The 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 the description may include, for example, codec information, profile values, and level values. An MPD is an example of a manifest file (e.g., manifest file 66). Client device 40 may retrieve the MPD for a media presentation to determine how to access movie fragments of the various presentations. The movie fragments may be located in a movie fragment box (moof box) of a video file.

[0070] Manifest file 66, which may include, for example, an MPD, may announce the availability of segments of representation 68. That is, the MPD may include information indicating a wall-clock time when a first segment of one of representations 68 becomes available, as well as information indicating the duration of the segments within representation 68. In this way, retrieval unit 52 of client device 40 may determine when each segment is available based on the start time and duration of the segments that precede the particular segment.

[0071] After encapsulation unit 30 has assembled NAL units and / or access units into a video file based on the received data, encapsulation unit 30 passes the video file to output interface 32 for output. In some examples, encapsulation unit 30 may store the video file locally or send the video file to a remote server via output interface 32, rather than sending the video file directly to client device 40. Output interface 32 may include, for example, a transmitter, a transceiver, a device for writing data to a computer-readable medium, such as, for example, an optical drive, a magnetic media drive (e.g., a floppy disk drive), a universal serial bus (USB) port, a network interface, or other output interface. Output interface 32 outputs the video file to a computer-readable medium, such as, for example, a transmission signal, a magnetic medium, an optical medium, a memory, a flash drive, or other computer-readable medium.

[0072] The network interface 54 may receive the NAL units or access units via the network 74 and provide the NAL units or access units to the decapsulation unit 50 via the retrieval unit 52. The decapsulation unit 50 may decapsulate the elements of the video file into constituent PES streams, depacketize the PES streams to retrieve the encoded data, and send the encoded data to the audio decoder 46 or the video decoder 48, depending on whether the encoded data is part of an audio stream or a video stream (e.g., as indicated by a PES packet header of the stream). The audio decoder 46 decodes the encoded audio data and sends the decoded audio data to the audio output 42, while the video decoder 48 decodes the encoded video data and sends the decoded video data (which may include multiple views of the stream) to the video output 44.

[0073] In some examples, a single user equipment (UE) device may include each component of content preparation device 20, server device 60, and client device 40. The UE device may participate in a media telecommunication session with another UE device that also includes components of content preparation device 20, server device 60, and client device 40 or similar components. In this way, each UE device may send and receive media data (e.g., video, audio, and / or image data) as part of the media telecommunication session. The techniques of the present disclosure are generally described with respect to one of content preparation device 20, server device 60, or client device 40, but these techniques may also be performed by a UE device that includes components of content preparation device 20, server device 60, and client device 40 or similar components.

[0074] The client device 40 may represent, for example, any of a cellular phone, a smart phone, a tablet computer, a laptop computer, a head mounted display (HMD), etc. The server device 60 may represent a network server, a second UE device, such as a second cellular phone, a smart phone, a tablet computer, a laptop computer, etc. In some examples, the server device 60 may be configured as a UE, and the client device 40 may be configured as a companion device to the server device 60, such that the network 74 may represent a relatively short-range communication coupling, such as a wireless local area network (WLAN), WiFi, or Bluetooth wireless link between the server device 60 and the client device 40.

[0075] In some examples, the server device 60 (e.g., the network interface 72) or the content preparation device 20 may be configured to detect a network interruption within the network 74. For example, a UE device including components of the content preparation device 20 and / or the server device 60 and sending media data to the client device 40 may experience a network handoff from one base station to another. In response, the video encoder 28 forms data (e.g., non-video content data referred to as metadata or non-VCL data) to be sent to the client device 40 indicating the network interruption. For example, the video encoder 28 may form non-VCL data (e.g., supplemental enhancement information (SEI) message) indicating that the client device 40 should enter an autonomous driving mode, during which the client device 40 will generate replacement data. The video encoder 28 or another component of the content preparation device 20 and / or the server device 60 may form data (e.g., SEI message) to indicate a start time for entering (e.g., transitioning to) an autonomous driving mode and an end time for ending (e.g., transitioning out of) the autonomous driving mode. In some examples, the data may also include the sending and receiving of messages that cause the client device 40 to issue a prompt to request user consent to enter the autonomous driving mode. In other examples, network interface 72 may form a message including the start time and end time of the autonomous driving mode according to a communication protocol (eg, Real-time Transport Protocol (RTP)) instead of sending the SEI message.

[0076] In some examples, the application of the client device 40 may include configuration data indicating whether the autonomous driving mode is enabled. Assuming that the autonomous driving mode is enabled according to the configuration data, in response to receiving data indicating the entry into the autonomous driving mode, the video decoder 48 or another component of the client device 40 may prompt its user to agree to use the autonomous driving mode. In some cases, the configuration data for enabling the autonomous driving mode may be provided by the user so that only a pre-authorization for enabling the autonomous driving mode is used, while in other examples, when the autonomous driving mode is enabled by the configuration data, the user may still receive a prompt to provide consent as to whether to enter the autonomous driving mode. If the client device 40 receives an affirmative consent from the user to use the autonomous driving mode or determines that the user has previously authorized consent to use the autonomous driving mode, the video decoder 48 (or another unit of the client device 40) may generate replacement video content (e.g., using AI / ML), starting at a specified start time and stopping at a specified end time, or at least until the received media data has been decoded in a timely manner. In some examples, the replacement media data may be continuously generated by the video decoder 48 during the media telecommunication session, but only presented during the autonomous driving mode.

[0077] As described above, in some examples, a media telecommunication session may include XR / AR / VR / MR data in addition to or in lieu of video data. The techniques of this disclosure may also be used to generate replacement XR / AR / VR / MR data in addition to or in lieu of video data. XR content (e.g., AR, VR, or MR content) may be, for example, computer-generated 2D or 3D graphics data to be presented to a user.

[0078] In another example, the client device 40 may be configured to detect a network outage within the network 74. For example, a UE device including components of the client device 40 for receiving and presenting media data via the network 74 may determine that the UE device is experiencing a network handoff from one base station to another or other network outage. In response, the video decoder 48 (or another element of the client device 40) may prompt a user of the client device 40 to consent to enter the autonomous driving mode (i.e., generate replacement media data for media data that will not be received during the network outage). If the client device 40 receives input from the user indicating affirmative consent to enter the autonomous driving mode, and if the autonomous driving mode is enabled, the client device 40 may generate replacement media data for media data that will not be received during the network outage, for example using an AI / ML process.

[0079] In some examples, the client device 40 may also send data to the content preparation device 20 and / or the server device 60 indicating that a network interruption has occurred. The data may indicate a start time and an end time (e.g., an estimate of the end time) of the time period of the network interruption. In response, the content preparation device 20 and / or the server device 60 may stop sending media data during the indicated time period. In some examples, the video encoder 28 may generate the next video frame to be sent to the client device 40 as an intra-frame prediction coding frame (I frame) in response to the data from the client device 40. In some examples, the video encoder 28 may change the reference picture of the subsequent picture to an uninterrupted frame (e.g., the last uninterrupted unidirectional inter-frame prediction frame (P frame)). In some examples, the video encoder 28 may use the same AI / ML model as the video decoder 48 to generate reference pictures, and then use these generated reference pictures to perform inter-frame prediction of subsequent frames, which are to be sent to the client device 40 once the autonomous driving mode period ends.

[0080] In some examples, after the network interruption has ended, video decoder 48 may mix the received media data with the generated replacement media data so that the transition from the replacement media data to the received media data is less perceptible to a user of client device 40 .

[0081] Although DASH explains Figure 1 , but the technology of the present disclosure can be used in combination with any of a variety of different media communication protocols. For example, the technology of the present disclosure can also be used (in addition or alternatively) in combination with the real-time transport protocol (RTP), the real-time streaming protocol (RTSP), the network real-time communication (WebRTC), the secure reliable transport (SRT), etc. or any combination thereof.

[0082] Figure 2 is shown in more detail Figure 1 1 is a block diagram of an example set of components of a retrieval unit 52 of FIG. 5 . In this example, the retrieval unit 52 includes an eMBMS middleware unit 100 , a DASH client 110 , and a media application 112 .

[0083] In this example, the eMBMS middleware unit 100 further includes an eMBMS receiving unit 106, a cache memory 104, and a proxy server unit 102. In this example, the eMBMS receiving unit 106 is configured to receive data via eMBMS, such as according to File Delivery over Unidirectional Transport (FLUTE), as described in T. Paila et al., "FLUTE-File Delivery over Unidirectional Transport" (Network Working Group, RFC 6726, November 2012, available at tools.ietf.org / html / rfc6726). That is, the eMBMS receiving unit 106 may receive files via broadcast from, for example, a server device 60 that may act as a broadcast / multicast service center (BM-SC).

[0084] When the eMBMS middleware unit 100 receives data of a file, the eMBMS middleware unit may store the received data in the cache memory 104. The cache memory 104 may include a computer-readable storage medium such as a flash memory, a hard disk, a RAM, or any other suitable storage medium.

[0085] The proxy server unit 102 may act as a server for the DASH client 110. For example, the proxy server unit 102 may provide an MPD file or other manifest file to the DASH client 110. The proxy server unit 102 may advertise the availability times of the segments in the MPD file, as well as hyperlinks from which the segments may be retrieved. These hyperlinks may include a local host address prefix corresponding to the client device 40 (e.g., 127.0.0.1 for IPv4). In this way, the DASH client 110 may request the segments from the proxy server unit 102 using an HTTP GET or partial GET request. For example, for a segment available from the link http: / / 127.0.0.1 / rep1 / seg3, the DASH client 110 may construct an HTTP GET request including a request for http: / / 127.0.0.1 / rep1 / seg3 and submit the request to the proxy server unit 102. Proxy server unit 102 may retrieve requested data from cache 104 and provide the data to DASH client 110 in response to such requests.

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

[0087] MPD 122 may include a data structure separate from representation 124. MPD 122 may correspond to Figure 1 Likewise, representation 124 may correspond to Figure 1 In general, the MPD 122 may include data generally describing characteristics of the representation 124, such as coding and presentation characteristics, adaptation sets, a profile to which the MPD 122 corresponds, text type information, camera angle information, rating information, trick mode information (e.g., information indicating that a representation includes a temporal subsequence), and / or information for retrieving remote time slots (e.g., for inserting targeted advertisements into media content during playback).

[0088] The header data 126, when present, may describe characteristics of the segment 128, such as the temporal location of a random access point (RAP, also referred to as a stream access point (SAP), which of the segments 128 includes a random access point, a byte offset from a random access point within the segment 128, a uniform resource locator (URL) for the segment 128, or other aspects of the segment 128. The header data 130, when present, may describe similar characteristics of the segment 132. Additionally or alternatively, such characteristics may be included entirely within the MPD 122.

[0089] Segments 128, 132 include one or more coded video samples, each of which may include a frame or slice of video data. Each of the coded video samples of segment 128 may have similar characteristics, such as height, width, and bandwidth requirements. Such characteristics may be described by data of MPD 122, but Figure 3 Such data is not shown in the example of . MPD 122 may include characteristics as described in the 3GPP specifications, with the addition of any or all of the signaled information described in this disclosure.

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

[0091] Figure 4 is a block diagram illustrating elements of an example video file 150 that may correspond to a segment of a representation, such as Figure 3 Each of the segments 128, 132 may include a substantially conforming Figure 4 The video file 150 can be said to be an encapsulated segment. As described above, a video file according to the ISO base media file format and its extensions stores data in a sequence of objects, called "boxes". Figure 4 In the example of FIG. 1 , the video file 150 includes a file type (FTYP) box 152, a movie (MOOV) box 154, a segment index (sidx) box 162, a movie fragment (MOOF) box 164, and a movie fragment random access (MFRA) box 166. Figure 4An example of a video file is shown, but it should be understood that other media files may include other types of media data (eg, audio data, timed text data, etc.) similar to the data structure of the video file 150 according to the ISO base media file format and its extensions.

[0092] The file type (FTYP) box 152 generally describes the file type of the video file 150. The file type box 152 may include data identifying specifications describing the optimal use of the video file 150. The file type box 152 may alternatively be placed before the MOOV box 154, the movie fragment box 164, and / or the MFRA box 166.

[0093] In some examples, a segment of, for example, video file 150 may include an MPD update box (not shown) preceding FTYP box 152. The MPD update box may include information indicating that an MPD corresponding to a representation including video file 150 is to be updated, along with information for updating the MPD. For example, the MPD update box may provide a URI or URL of a resource to be used to update the MPD. As another example, the MPD update box may include data for updating the MPD. In some examples, the MPD update box may immediately follow a segment type (STYP) box (not shown) for video file 150, where the STYP box may define the segment type of video file 150.

[0094] exist Figure 4 In the example of , the MOOV box 154 includes a movie header (MVHD) box 156, a track (TRAK) box 158, and one or more movie extension (MVEX) boxes 160. In general, the MVHD box 156 may describe general characteristics of the video file 150. For example, the MVHD box 156 may include data describing the time when the video file 150 was originally created, the time when the video file 150 was last modified, the time stamp of the video file 150, the playback duration of the video file 150, or other data generally describing 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 (TKHD) box that describes characteristics of the track corresponding to TRAK box 158. In some examples, TRAK box 158 may include coded video pictures, while in other examples, the coded video pictures of the track may be included in movie fragments 164, which may be referenced by data of TRAK box 158 and / or sidx box 162.

[0096] In some examples, the video file 150 may include more than one track. Thus, the MOOV box 154 may include a number of TRAK boxes equal to the number of tracks in the video file 150. The TRAK box 158 may describe characteristics of a corresponding track of the video file 150. For example, the TRAK box 158 may describe temporal and / or spatial information of the corresponding track. Figure 3 ) includes a parameter set track in a video file, such as video file 150, a TRAK box, similar to TRAK box 158 of MOOV box 154, may describe characteristics of the parameter set track. Encapsulation unit 30 may signal the presence of a sequence level SEI message in the parameter set track within a TRAK box that describes the parameter set track.

[0097] The MVEX box 160 may describe characteristics of the corresponding movie fragment 164, e.g., to signal that in addition to the video data (if present) included within the MOOV box 154, the video file 150 includes the movie fragment 164. In the context of streaming video data, coded video pictures may be included in the movie fragment 164 instead of the MOOV box 154. Thus, all coded video samples may be included in the movie fragment 164 instead of the MOOV box 154.

[0098] The MOOV box 154 may include a plurality of MVEX boxes 160 equal to the number of movie fragments 164 in the video file 150. Each of the MVEX boxes 160 may describe characteristics of a corresponding one of the movie fragments 164. For example, each MVEX box may include a Movie Extension Header box (MEHD) box that describes the duration of a corresponding one of the movie fragments 164.

[0099] As mentioned above, encapsulation unit 30 may store a sequence data set in a video sample that does not include actual coded video data. A video sample may generally correspond to an access unit, which is a representation of a coded picture at a particular time instance. In the context of AVC, a coded picture includes one or more VCL NAL units that contain information, such as SEI messages, for all pixels used to construct an access unit and other associated non-VCL NAL units. Thus, encapsulation unit 30 may include a sequence data set in one of the movie fragments 164, which may include a sequence-level SEI message. Encapsulation unit 30 may further signal the presence of the sequence data set and / or sequence-level SEI message as being present in one of the movie fragments 164 within one of the MVEX boxes 160 corresponding to one of the movie fragments 164.

[0100] SIDX box 162 is an optional element of video file 150. That is, video files conforming to the 3GPP file format or other such file formats do not necessarily include SIDX box 162. According to the example of the 3GPP file format, the SIDX box can be used to identify sub-segments of a segment (e.g., a segment contained within video file 150). The 3GPP file format defines a sub-segment as "a self-contained collection of one or more consecutive movie fragment boxes with corresponding media data boxes, and the media data box containing data referenced by the movie fragment box must be after the movie fragment box and before the next movie fragment box containing information about the same track." The 3GPP file format also indicates that the SIDX box "contains a sequence of references to sub-segments of the (sub)segments recorded by the box. The referenced sub-segments are consecutive in presentation time. Similarly, the bytes referenced by the segment index box are always consecutive within the segment. The referenced size gives a count of the number of bytes in the referenced material."

[0101] The SIDX box 162 generally provides information representing one or more sub-segments of a segment included in the video file 150. For example, this information may include the playback time at which the sub-segment begins and / or ends, the byte offset of the sub-segment, whether the sub-segment includes (e.g., starts at) a stream access point (SAP), the type of SAP (e.g., whether the SAP is an instantaneous decoder refresh (IDR) picture, a clean random access (CRA) picture, a broken link access (BLA) picture, etc.), the location of the SAP in the sub-segment (in terms of playback time and / or byte offset), etc.

[0102] Movie fragments 164 may include one or more coded video pictures. In some examples, movie fragments 164 may include one or more groups of pictures (GOPs), each of which may include a number of coded video pictures, such as frames or pictures. Additionally, as described above, in some examples, movie fragments 164 may include sequence data sets. Each of movie fragments 164 may include a movie fragment header box (MFHD, Figure 4 MFHD box may describe characteristics of the corresponding movie fragment, such as a sequence number of the movie fragment. The movie fragments 164 may be included in the video file 150 in the order of the sequence number.

[0103] MFRA box 166 may describe random access points within movie fragments 164 of video file 150. This may assist in performing trick modes, such as performing seeks to specific time locations (i.e., playback times) within segments encapsulated by video file 150. In some examples, MFRA box 166 is generally optional and need not be included in the video file. Likewise, a client device (e.g., client device 40) may not necessarily need to reference MFRA box 166 to properly decode and display video data of video file 150. MFRA box 166 may include a number of track segment random access (TFRA) boxes (not shown) equal to the number of tracks of video file 150, or, in some examples, equal to the number of media tracks (e.g., non-hint tracks) of video file 150.

[0104] In some examples, the movie fragment 164 may include one or more stream access points (SAPs), such as IDR pictures. Similarly, the MFRA box 166 may provide an indication of the location within the video file 150 of the SAP. Therefore, a temporal subsequence of the video file 150 may be formed by the SAPs of the video file 150. The temporal subsequence may also include other pictures, such as P frames and / or B frames that depend on the SAP. The frames and / or slices of the temporal subsequence may be arranged in a segment so that the frames / slices of the temporal subsequence that depend on other frames / slices of the subsequence may be properly decoded. For example, in a hierarchical arrangement of data, data for prediction of other data may also be included in the temporal subsequence.

[0105] Figure 5 is a conceptual diagram showing an example of generating a replacement frame according to the technology of the present disclosure. Figure 5 In the example of , source device 190 transmits media data 180 via network 192. Media data 180 includes frames 182A to 182D (frames 182). In response to detection or indication of switching period 186, replacement data generator 194 generates replacement frames 184A-184C (replacement frames 184).

[0106] The replacement data generator 194 may include one or more AI / ML models for generating replacement frames 184. In particular, the replacement data generator 194 may receive at least one of the frames 182A, 182B and apply at least one of the frames 182A, 182B to an AI / ML model to generate one or more of the replacement frames 184 using at least one of the frames 182A, 182B.

[0107] In some examples, the replacement data generator 194 may be included in the client device 40 ( Figure 1 ). Thus, if client device 40 experiences a network outage, client device 40 may generate replacement frame 184. In some examples, replacement data generator 194 may be included in network 74 ( Figure 1 ) or an intermediate network device within network 192 (such as a service device or service card of a network device (such as a router). Therefore, if source device 190 experiences a network interruption, the intermediate network device can generate a replacement frame 184 and encode the frame, and then send the encoded replacement frame to client device 40.

[0108] As described above, in some examples, client device 40 may send data to source device 190 indicating that client device 40 has experienced a network outage. In response, in some examples, source device 190 may generate frame 182C as a forced I-frame. That is, if frame 182C was originally to be encoded as a P-frame or a bidirectionally predicted frame (B-frame), source device 190 may instead encode frame 182C as an I-frame. In some examples, in response to the network outage, source device 190 may encode frame 182C using only one or both of frames 182A, 182B as reference frames. That is, if one or more frames between frames 182B and 182C can otherwise be used as reference frames, source device 190 may avoid using these frames as reference frames and instead use only one or both of frames 182A, 182B as reference frames for inter-frame prediction of frame 182C. In some examples, in response to the network interruption, source device 190 may also include its own replacement data generator that applies the same AI / ML model to frames 182A, 182B and may also generate replacement frame 184 for use as a reference frame so that frames 182C, 182D can be predicted from replacement frame 184.

[0109] Figure 6 is a flow chart illustrating an example method of generating and presenting replacement media data according to the techniques of this disclosure. Figure 6 In the example of Figure 1 Server device 60 of the embodiment of the present invention detects a network interruption, such as network 74 (200). For example, server device 60 may determine that it is experiencing a handover, such as a switch between base stations of a radio access network. In response, server device 60 generates an autonomous driving mode indication message (202). The autonomous driving mode indication message may include data indicating a start time and an end time of the autonomous driving mode. In some examples, the autonomous driving mode indication message may also include data indicating a client device (such as client device 40 ( Figure 1 )) Data prompting the user to agree to enter the autonomous driving mode. As described above, the autonomous driving mode may generally cause the client device 40 to generate replacement media data for the media data that would otherwise be received between the indicated start time and the indicated end time.

[0110] The server device 60 may determine that the start time is, for example, the time of the start of a network handover between base stations of a radio access network. The server device 60 may estimate the end time as a typical time to complete a network handover, for example, 50 ms. Thus, the start time may be the time T at which the handover process starts, and the end time may be T+S, where S is a typical time to complete a network handover. If S is 50 ms, the start time may be T, and the end time may be T+50 ms.

[0111] Then, server device 60 may send an automatic driving mode indication message to client device 40 (204). Client device 40 may receive an automatic driving mode indication message from server device 60 (206). Figure 6 , but assume that the server device 60 has sent media data to the client device 40 as part of a media streaming session. In this example, in response to receiving the autonomous driving mode indication message, the client device 40 enters the autonomous driving mode (208), for example, to generate replacement media data (e.g., video data) using previously received media data starting at time T indicated in the autonomous driving mode indication message. The client device 40 may then generate the replacement media data (210), for example, using one or more AI / ML models and the previously received media data. The client device 40 may present the replacement media data (212). The client device 40 may continue to generate and present the replacement media data until the end time indicated in the autonomous driving mode indication message is reached. After the autonomous driving mode ends, the client device 40 may resume normal operation, i.e., receiving, decoding, and presenting the media data of the bitstream from the server device 60.

[0112] In this way, Figure 6 The method represents an example of a method for presenting media data, the method comprising: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0113] Figure 7is a flowchart illustrating another example method of generating and presenting replacement media data according to the techniques of the present disclosure. In this example, client device 40 detects a network interruption (220). For example, client device 40 may determine that it is experiencing a switch from one base station to another base station. In response, client device 40 may generate an autonomous driving mode indication message (222) and send the autonomous driving mode indication message to server device 60 (224). Again, the autonomous driving mode indication message may include data indicating a start time and an end time of the autonomous driving mode. Thus, server device 60 may receive the autonomous driving mode indication message (226) and stop sending media data (228) during an autonomous driving period, where the autonomous driving period corresponds to the time between the start time and the end time of the autonomous driving mode.

[0114] During this time, client device 40 may enter an autonomous driving mode (230). While in the autonomous driving mode, client device 40 may generate replacement media data (232), for example, using one or more AI / ML models and media data previously received from server device 60. Likewise, client device 40 may present the replacement media data (234). After the autonomous driving period ends, server device 60 may resume sending media data (236). Client device 40 may receive the sent media data (238) and present the received media data (238).

[0115] In this way, Figure 7 The method represents an example of a method for presenting media data, the method comprising: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0116] Figure 8 1 is a flow chart illustrating an example method of generating and presenting media data according to the techniques of the present disclosure. Initially, client device 40 may receive a first set of media data for a media session from server device 60 (250). Client device 40 may communicate with server device 60 via separate channels, such as a signaling channel and a data communication channel. Client device 40 and server device 60 may exchange low-bandwidth signaling messages via the signaling channel and exchange higher-bandwidth media data via the data communication channel. Client device 40 may decode and present the first set of media data (252).

[0117] Client device 40 may then determine that a second set of media data for the media session will not be received (254). For example, client device 40 may determine that it is undergoing a handoff from one base station to another base station. As another example, client device 40 may receive a message from server device 60 (e.g., via a signaling channel) indicating that server device 60 is undergoing a handoff from one base station to another base station. In some examples, client device 40 or server device 60 may determine that a signal loss or a reduction in signal strength may be due to a location and / or direction of geographic movement of client device 40, server device 60, or both. For example, certain geographic areas may historically result in signal loss, such as if either client device 40 or server device 60 is moving in a vehicle through a tunnel, through an area with low wireless coverage, in an area with high signal interference, etc.

[0118] Client device 40 may then enter the autonomous driving mode and predictively generate replacement media data for the second set of media data (256). For example, client device 40 may apply one or more AI / ML models to at least a portion of the first set of media data to generate the replacement media data. Client device 40 may also present the replacement media data (258).

[0119] Subsequently, client device 40 may begin receiving a third set of media data for the media session from server device 60 (260). Accordingly, client device 40 may cease generating replacement media data and instead present the received third set of media data (282).

[0120] In this way, Figure 8 The method represents an example of a method for presenting media data, the method comprising: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0121] Fig. 9 2 is a block diagram illustrating an example system 280 including devices that can be configured to perform the techniques of the present disclosure. Specifically, the system 280 includes user equipment (UE) devices 284, 292, base stations 282A, 282B, 290A, 290B (base stations 282, 290), and a network formed by an intermediate network device 288.

[0122] The intermediate network device 288 can generally be any of a variety of different network devices that make up a computer-based network. The intermediate network device 288 can include, for example, routers, switches, hubs, gateways, service devices, servers, bridges, controllers, etc. The base stations 282, 290 represent examples of access points for cells of a radio access network (RAN) (e.g., 5G RAN). For example, the base stations 282, 290 can be corresponding gNodeBs. The UE devices 284, 292 represent corresponding UE devices, such as cellular phones, tablet computers, mobile devices, etc.

[0123] UE devices 284, 292 may include components for sending and receiving media data, including audio, video, and / or AR / XR / MR / VR data for media or AR teleconferencing. For example, UE devices 284, 292 may include a camera, a microphone, and / or a graphics processing unit (GPU) for generating AR / XR / MR / VR data.

[0124] According to the technology of the present disclosure, UE device 284 and UE device 292 can participate in a media teleconference session, such as a video teleconference session and / or an AR / XR / MR / VR teleconference session. Therefore, UE devices 284, 292 can send and receive media data. When UE device 284 captures or generates media data, UE device 284 can encode the captured / generated media data and send it to UE device 292. Similarly, when UE device 292 captures or generates media data, UE device 292 can encode the captured / generated media data and send it to UE device 284.

[0125] According to the technology of the present disclosure, UE device 284 can move from a cell including base station 282B to a cell including base station 282A. Therefore, a handover from base station 282B to base station 282A can occur. In response, UE device 284 can send an autonomous driving mode indication message to UE device 292, for example, via a signaling channel. The autonomous driving mode indication message can indicate that for the media data currently being received by UE device 292, UE device 292 should generate replacement media data, and for the media data currently being sent by UE device 292, UE device 292 should stop sending media data until the autonomous driving mode expires. UE device 284 can construct an autonomous driving mode indication message to indicate the start time and end time of the autonomous driving period.

[0126] In some examples, one or more of the intermediate network devices 288 may be service devices configured to detect such an autonomous driving mode indication message. The service devices of the intermediate network devices 288 may generate and encode the replacement media data on behalf of the UE device 292 so that the UE device 292 does not need to change its decoding and presentation processes.

[0127] In this manner, UE devices 284, 292 represent examples of devices for presenting media data, including a memory configured to store media data; and one or more processors implemented in circuits and configured to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set for which the media bitstream will not be received, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0128] Fig.10 302 is a block diagram illustrating an example system including a user equipment (UE) device 300 and a companion device 302. The UE device 300 and the companion device 302 participate in a communication session 304. The communication session 304 may be conducted over a wireless communication protocol such as a wireless wide area network (WWAN), a wireless local area network (WLAN), WiFi, Bluetooth, etc. The UE device 300 may represent any user equipment, and the companion device 302 may represent a close proximity device used by the same user in conjunction with the UE device 300. For example, the UE device 300 may be a cellular phone, and the companion device 302 may be a wireless display, such as a monitor, a television, or an AR / XR / MR / VR headset. As another example, the UE device 300 may be a tablet or a laptop computer, and the companion device 302 may be a cellular phone, or vice versa.

[0129] Although primarily described with respect to the scenario of two UE devices communicating with each other over a network, the techniques of this disclosure may also be performed by UE device 300 and companion device 302. For example, if UE device 300 receives media data, e.g., via a media communication session with another UE device (not shown), UE device 300 may wirelessly present the media data of the media communication session via companion device 302. If the communication session 304 is briefly interrupted, e.g., because UE device 300 and companion device 302 are physically too far from each other, a physical object obstructs the communication session, or for other such reasons, companion device 302 may be configured to detect the interruption and apply the techniques of this disclosure to generate replacement media data until the communication session 304 is resumed.

[0130] In some examples, UE device 300 may determine that a communication session with another UE device (not shown) has been interrupted, as in the various examples discussed above, but offload the process of generating replacement media data to companion device 302. For example, companion device 302 may include one or more AI / ML models and AI / ML processes. UE device 300 may send the received media data and a request for replacement media data to companion device 302. In response, companion device 302 may generate replacement media data by applying the AI / ML model to the received media data, and send the replacement media data to UE device 300 via communication session 304.

[0131] The following clauses represent some examples of the techniques of this disclosure:

[0132] Item 1: A method for presenting media data, the method comprising: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0133] Clause 2: The method of clause 1, wherein receiving the first set of media data comprises receiving the first set of media data via a network, and wherein determining that the second set of media data will not be received comprises determining that a network disruption will prevent receiving the second set of media data.

[0134] Clause 3: The method according to Clause 2 also includes determining a start time of the network interruption and an end time of the network interruption, wherein predictively generating replacement data includes predictively generating replacement media data in a time period between the start time of the network interruption and the end time of the network interruption.

[0135] Clause 4: A method according to clause 1, wherein receiving the first media data set includes receiving the first media data set from a source device via a network, and wherein determining that the second media data set will not be received includes receiving data from the source device indicating that the second media data set will not be received.

[0136] Clause 5: A method according to clause 4, wherein receiving the data from the source device indicating that the second set of media data will not be received includes receiving at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0137] Clause 6: A method according to clause 4, wherein receiving a first media data set includes receiving the first media data set from a source device via a media data channel of a network, and wherein receiving data from the source device indicating that a second media data set will not be received includes receiving data from the source device via a signaling channel of the network indicating that the second media data set will not be received, the signaling channel being separate from the media data channel.

[0138] Clause 7: The method according to Clause 1 further includes: presenting a prompt to a user requesting the user to consent to predictively generate replacement media data when the media data will not be received; and receiving input data from the user, the input data indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0139] Clause 8: A method according to clause 1, wherein the media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0140] Clause 9: The method according to Clause 1 further includes: receiving a third media data set of the media bitstream; mixing at least a portion of the third media data set with the replacement media data; and presenting at least a portion of the mixture of the third media data set after the replacement media data.

[0141] Clause 10: The method of clause 1, wherein predictively generating replacement media data comprises providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0142] Item 11: A device for presenting media data, the device comprising: a memory configured to store the media data; and one or more processors implemented in a circuit and configured to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0143] Clause 12: A device according to clause 11, wherein the one or more processors are configured to receive the first media data set via a network, and wherein, in order to determine that the second media data set will not be received, the one or more network devices are configured to determine that a network interruption will prevent reception of the second media data set.

[0144] Clause 13: The apparatus of clause 12, wherein the one or more processors are further configured to determine a start time of a network interruption and an end time of the network interruption, wherein predictively generating the replacement data comprises predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0145] Clause 14: A device according to clause 11, wherein the one or more processors are configured to receive the first media data set from a source device via a network, and wherein, in order to determine that the second media data set will not be received, the one or more processors are configured to receive data from the source device indicating that the second media data set will not be received.

[0146] Clause 15: A device according to clause 14, wherein in order to receive from the source device an indication that the second media data set will not be received, the one or more processors are configured to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0147] Clause 16: A device according to clause 14, wherein the one or more processors are configured to receive the first media data set from the source device via a media data channel of the network, and wherein the one or more processors are configured to receive data from the source device via a signaling channel of the network indicating that the second media data set will not be received, the signaling channel being separate from the media data channel.

[0148] Clause 17: The device according to clause 11 further includes a display, wherein the one or more processors are further configured to: present a prompt to the user via the display requesting the user to consent to predictively generate replacement media data when the media data will not be received; and receive input data from the user indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0149] Clause 18: The apparatus of clause 11, wherein the media data comprises at least one of video data or extended reality (XR) data, the XR data comprising at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0150] Clause 19: A device according to clause 11, wherein the one or more processors are further configured to: receive a third media data set of the media bitstream; mix at least a portion of the third media data set with the replacement media data; and present at least a portion of the mixture of the third media data set after the replacement media data.

[0151] Clause 20: A device according to clause 11, wherein in order to predictively generate the replacement media data, the one or more processors are configured to provide at least a portion of the first media data set to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0152] Item 21: A device for presenting media data, the device comprising: a device for receiving a first media data set of a media bitstream; a device for predictively generating replacement media data for a second media data set following the first media data set in response to determining that the media bitstream will not be received, using the first media data set; and a device for presenting the first media data set and the replacement media data.

[0153] Clause 22: The apparatus of clause 21, wherein means for receiving the first set of media data comprises means for receiving the first set of media data via a network, and further comprising means for determining that a network disruption will prevent receiving the second set of media data.

[0154] Clause 23: The apparatus according to Clause 22 further includes a device for determining a start time of a network interruption and an end time of the network interruption, wherein the device for predictively generating the replacement data includes a device for predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0155] Clause 24: An apparatus according to clause 21, wherein the means for receiving the first media data set comprises means for receiving the first media data set from a source device via a network, and wherein the means for determining that the second media data set will not be received comprises means for receiving data from the source device indicating that the second media data set will not be received.

[0156] Clause 25: An apparatus according to clause 24, wherein the device for receiving from the source device an indication that the data of the second media data set will not be received includes a device for receiving at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0157] Clause 26: An apparatus according to clause 24, wherein the device for receiving a first media data set includes a device for receiving the first media data set from a source device via a media data channel of a network, and wherein the device for receiving data from the source device indicating that the second media data set will not be received includes a device for receiving data from the source device via a signaling channel of the network indicating that the second media data set will not be received, the signaling channel being separate from the media data channel.

[0158] Clause 27: The apparatus according to clause 21 further includes: a device for presenting a prompt to a user requesting the user to consent to predictively generate replacement media data when the media data will not be received; and a device for receiving input data from the user, the input data indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0159] Clause 28: An apparatus according to clause 21, wherein the media data includes at least one of video data or extended reality (XR) data, the XR data including at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0160] Clause 29: The apparatus according to Clause 21 further comprises: a device for receiving a third media data set of a media bitstream; a device for mixing at least a portion of the third media data set with the replacement media data; and a device for presenting at least a portion of the mixture of the third media data set after the replacement media data.

[0161] Clause 30: An apparatus according to clause 21, wherein the means for predictively generating replacement media data comprises means for providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0162] Item 31: A computer-readable storage medium having instructions stored thereon, which when executed cause a processor to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0163] Clause 32: A computer-readable storage medium according to clause 31, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set via a network, and also include instructions causing the processor to determine that a network interruption will prevent reception of the second media data set.

[0164] Clause 33: The computer-readable storage medium of clause 32 further comprising instructions causing the processor to determine a start time of a network interruption and an end time of the network interruption, wherein the instructions causing the processor to predictively generate the replacement data comprise instructions causing the processor to predictively generate replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0165] Clause 34: A computer-readable storage medium according to clause 31, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from a source device via a network, and also include instructions causing the processor to receive data from the source device indicating that the second media data set will not be received.

[0166] Clause 35: A computer-readable storage medium according to clause 34, wherein the instructions causing the processor to receive from the source device an indication that the data of the second media data set will not be received include instructions causing the processor to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0167] Clause 36: A computer-readable storage medium according to clause 34, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from the source device via a media data channel of the network, and wherein the instructions causing the processor to receive from the source device an indication that the data of the second media data set will not be received include instructions causing the processor to receive from the source device via a signaling channel of the network an indication that the data of the second media data set will not be received, the signaling channel being separate from the media data channel.

[0168] Clause 37: The computer-readable storage medium of clause 31 further comprising instructions for causing the processor to: present a prompt to a user requesting the user's consent to predictively generate replacement media data in a case where the media data will not be received; and receive input data from the user indicating that the user consents to predictively generate replacement media data for the media bitstream.

[0169] Clause 38: A computer-readable storage medium according to clause 31, wherein the media data includes at least one of video data or extended reality (XR) data, the XR data including at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0170] Clause 39: The computer-readable storage medium according to clause 31 further includes instructions for causing the processor to perform the following operations: receiving a third media data set of the media bitstream; mixing at least a portion of the third media data set with the replacement media data; and presenting at least a portion of the mixture of the third media data set after the replacement media data.

[0171] Clause 40: A computer-readable storage medium according to clause 31, wherein the instructions causing the processor to predictively generate replacement media data include instructions causing the processor to provide at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0172] Item 41: A method for presenting media data, the method comprising: receiving a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generating replacement media data for the second media data set using the first media data set; and presenting the first media data set and the replacement media data.

[0173] Clause 42: The method of clause 41, wherein receiving the first set of media data comprises receiving the first set of media data via a network, and wherein determining that the second set of media data will not be received comprises determining that a network interruption will prevent receiving the second set of media data.

[0174] Clause 43: The method according to Clause 42 also includes determining a start time of the network interruption and an end time of the network interruption, wherein predictively generating the replacement data includes predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0175] Clause 44: A method according to clause 41, wherein receiving the first media data set includes receiving the first media data set from a source device via a network, and wherein determining that the second media data set will not be received includes receiving data from the source device indicating that the second media data set will not be received.

[0176] Clause 45: A method according to clause 44, wherein receiving the data from the source device indicating that the second set of media data will not be received includes receiving at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0177] Clause 46: A method according to any one of clauses 44 and 45, wherein receiving the first media data set includes receiving the first media data set from the source device via a media data channel of the network, and wherein receiving data from the source device indicating that the second media data set will not be received includes receiving data from the source device via a signaling channel of the network indicating that the second media data set will not be received, the signaling channel being separate from the media data channel.

[0178] Clause 47: The method according to any one of clauses 41-46 further includes: presenting a prompt to a user requesting the user to consent to predictively generate replacement media data without receiving the media data; and receiving input data from the user, the input data indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0179] Clause 48: A method according to any of clauses 41-47, wherein the media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data or mixed reality (MR) data.

[0180] Clause 49: The method according to any one of clauses 41-48 further includes: receiving a third media data set of the media bitstream; mixing at least a portion of the third media data set with the replacement media data; and presenting at least a portion of the mixture of the third media data set after the replacement media data.

[0181] Clause 50: A method according to any of clauses 41-49, wherein predictively generating the replacement media data includes providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0182] Item 51: A device for presenting media data, the device comprising: a memory configured to store the media data; and one or more processors implemented in a circuit and configured to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0183] Clause 52: A device according to clause 51, wherein the one or more processors are configured to receive the first media data set via a network, and wherein in order to determine that the second media data set will not be received, the one or more network devices are configured to determine that a network interruption will prevent reception of the second media data set.

[0184] Clause 53: A device according to Clause 52, wherein the one or more processors are further configured to determine a start time of the network interruption and an end time of the network interruption, wherein predictively generating the replacement data includes predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0185] Clause 54: A device according to clause 51, wherein the one or more processors are configured to receive the first media data set from a source device via a network, and wherein in order to determine that the second media data set will not be received, the one or more processors are configured to receive data from the source device indicating that the second media data set will not be received.

[0186] Clause 55: A device according to clause 54, wherein in order to receive from the source device an indication that the data of the second media data set will not be received, the one or more processors are configured to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0187] Clause 56: A device according to any one of clauses 54 and 55, wherein the one or more processors are configured to receive the first media data set from the source device via a media data channel of the network, and wherein the one or more processors are configured to receive data indicating that the second media data set will not be received from the source device via a signaling channel of the network, the signaling channel being separate from the media data channel.

[0188] Clause 57: The device according to any one of clauses 51-56 further includes a display, wherein the one or more processors are further configured to: present a prompt to a user via the display requesting the user to consent to predictively generate replacement media data without receiving media data; and receive input data from the user, the input data indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0189] Clause 58: A device according to any of clauses 51-57, wherein the media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0190] Clause 59: A device according to any of clauses 51-58, wherein the one or more processors are further configured to: receive a third media data set of the media bitstream; mix at least a portion of the third media data set with the replacement media data; and present at least a portion of the mixture of the third media data set after the replacement media data.

[0191] Clause 60: A device according to any of clauses 51-59, wherein, in order to predictively generate the replacement media data, the one or more processors are configured to provide at least a portion of the first media data set to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0192] Item 61: A device for presenting media data, the device comprising: a device for receiving a first media data set of a media bitstream; a device for predictively generating replacement media data for a second media data set following the first media data set in response to determining that the media bitstream will not be received, using the first media data set; and a device for presenting the first media data set and the replacement media data.

[0193] Clause 62: The apparatus of clause 61, wherein means for receiving the first set of media data comprises means for receiving the first set of media data via a network, further comprising means for determining that a network disruption will prevent receiving the second set of media data.

[0194] Clause 63: The apparatus of clause 62 further comprises a device for determining a start time of a network interruption and an end time of the network interruption, wherein the device for predictively generating replacement data comprises a device for predictively generating replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0195] Clause 64: An apparatus according to clause 61, wherein the means for receiving the first media data set comprises means for receiving the first media data set from a source device via a network, and wherein the means for determining that the second media data set will not be received comprises means for receiving data from the source device indicating that the second media data set will not be received.

[0196] Clause 65: An apparatus according to clause 64, wherein the device for receiving from the source device an indication that the data of the second media data set will not be received includes a device for receiving at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0197] Clause 66: A device according to any one of clauses 64 and 65, wherein the device for receiving a first media data set includes a device for receiving the first media data set from a source device via a media data channel of a network, and wherein the device for receiving data from the source device indicating that the second media data set will not be received includes a device for receiving data from the source device via a signaling channel of the network indicating that the second media data set will not be received, the signaling channel being separate from the media data channel.

[0198] Clause 67: The apparatus of any one of clauses 61-66, further comprising: a device for presenting to a user a prompt requesting the user to consent to predictively generate replacement media data without receiving media data; and a device for receiving input data from the user, the input data indicating that the user consents to the predictively generated replacement media data for the media bitstream.

[0199] Clause 68: A device according to any of clauses 61-67, wherein the media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0200] Clause 69: The apparatus according to any one of clauses 61-68 further comprises: a device for receiving a third media data set of the media bitstream; a device for mixing at least a portion of the third media data set with the replacement media data; and a device for presenting at least a portion of the mixture of the third media data set after the replacement media data.

[0201] Clause 70: An apparatus according to any of clauses 61-69, wherein the means for predictively generating replacement media data comprises means for providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

[0202] Item 71: A computer-readable storage medium having instructions stored thereon, which when executed cause a processor to: receive a first media data set of a media bitstream; in response to determining that a second media data set following the first media data set will not be received for the media bitstream, predictively generate replacement media data for the second media data set using the first media data set; and present the first media data set and the replacement media data.

[0203] Clause 72: A computer-readable storage medium as described in clause 71, wherein the instructions for causing the processor to receive the first set of media data include instructions for causing the processor to receive the first set of media data via a network, and further include instructions for causing the processor to determine that a network interruption will prevent receipt of a second set of media data.

[0204] Clause 73: The computer-readable storage medium of clause 72 further comprising instructions for causing the processor to determine a start time of a network interruption and an end time of the network interruption, wherein the instructions for causing the processor to predictively generate replacement data comprise instructions for causing the processor to predictively generate replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

[0205] Clause 74: A computer-readable storage medium according to clause 71, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from a source device via a network, and also include instructions causing the processor to receive data from the source device indicating that the second media data set will not be received.

[0206] Clause 75: A computer-readable storage medium according to clause 74, wherein the instructions causing the processor to receive from the source device an indication that the data of the second media data set will not be received include instructions causing the processor to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

[0207] Clause 76: A computer-readable storage medium according to any one of clauses 74 and 75, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from the source device via a media data channel of the network, and wherein the instructions causing the processor to receive from the source device an indication that the data of the second media data set will not be received include instructions causing the processor to receive from the source device via a signaling channel of the network an indication that the data of the second media data set will not be received, the signaling channel being separate from the media data channel.

[0208] Clause 77: The computer-readable storage medium of any one of clauses 71-76, further comprising instructions for causing the processor to: present a prompt to a user requesting the user's consent to predictively generate replacement media data in a scenario where the media data will not be received; and receive input data from the user, the input data indicating the user's consent to predictively generate replacement media data for the media bitstream.

[0209] Clause 78: A computer-readable storage medium as described in any of clauses 71-77, wherein the media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

[0210] Clause 79: A computer-readable storage medium according to any one of clauses 71-78, further comprising instructions for causing the processor to perform the following operations: receiving a third media data set of the media bitstream; mixing at least a portion of the third media data set with the replacement media data; and presenting at least a portion of the mixed third media data set after the replacement media data.

[0211] Clause 80: Computer-readable storage medium according to any of clauses 71-79, wherein the instructions for causing the processor to predictively generate replacement media data include instructions for causing the processor to provide at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

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

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

[0214] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures or any other structure suitable for implementation in the techniques described herein. In addition, in some aspects, 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. In addition, these techniques may be fully implemented in one or more circuits or logic elements.

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

[0216] Various examples have been described. These and other examples are within the scope of the following claims.

Claims

1. A method for presenting media data, the method comprising: Receiving a first media data set of a media bitstream; In response to determining that a second set of media data subsequent to the first set of media data for which the media bitstream will not be received within a time period, predictively generating replacement media data for the second set of media data using at least a subset of the first set of media data; as well as The first set of media data and the replacement media data are presented.

2. The method of claim 1, wherein receiving the first set of media data comprises receiving the first set of media data via a network, and wherein determining that the second set of media data will not be received comprises determining that a network interruption will prevent receiving the second set of media data.

3. The method of claim 2, further comprising determining a start time of the network interruption and an end time of the network interruption, wherein predictively generating the replacement data comprises predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

4. The method of claim 1 , wherein receiving the first media data set comprises receiving the first media data set from a source device via a network, and wherein determining that the second media data set will not be received comprises receiving data from the source device indicating that the second media data set will not be received.

5. The method of claim 4, wherein receiving data from the source device indicating that the second set of media data will not be received comprises receiving at least one of a Supplemental Enhancement Information (SEI) message or a Real-time Transport Protocol (RTP) message from the source device.

6. The method according to claim 4, wherein: Receiving the first media data set includes receiving the first media data set from the source device via a media data channel of the network, and wherein receiving the data indicating that the second media data set will not be received from the source device includes receiving the data indicating that the second media data set will not be received from the source device via a signaling channel of the network, the signaling channel being separate from the media data channel.

7. The method according to claim 1, further comprising: In the event that the media data will not be received, presenting a prompt to the user requesting the user's consent to predictively generate replacement media data; as well as Input data is received from the user, the input data indicating that the user agrees to replacement media data predictively generated for the media bitstream.

8. The method according to claim 1, wherein: The media data includes at least one of video data or extended reality (XR) data, and the XR data includes at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

9. The method according to claim 1, further comprising: Receiving a third media data set of the media bitstream; mixing at least a portion of the third set of media data with the replacement media data; as well as At least a portion of the mix of the third set of media data is presented after the replacement media data.

10. The method according to claim 1, wherein: Predictively generating replacement media data includes providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

11. A device for presenting media data, the device comprising: a memory configured to store media data; as well as One or more processors implemented in circuitry and configured to: Receiving a first media data set of a media bitstream; In response to determining that a second set of media data subsequent to the first set of media data for which the media bitstream will not be received within a time period, predictively generating replacement media data for the second set of media data using at least a subset of the first set of media data; as well as The first set of media data and the replacement media data are presented.

12. A device according to claim 11, wherein the one or more processors are configured to receive the first media data set via a network, and wherein in order to determine that the second media data set will not be received, the one or more network devices are configured to determine that a network interruption will prevent reception of the second media data set.

13. The device of claim 12, wherein the one or more processors are further configured to determine a start time of the network interruption and an end time of the network interruption, wherein predictively generating the replacement data comprises predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

14. A device according to claim 11, wherein the one or more processors are configured to receive the first media data set from a source device via a network, and wherein in order to determine that the second media data set will not be received, the one or more processors are configured to receive data from the source device indicating that the second media data set will not be received.

15. A device according to claim 14, wherein in order to receive the data indicating that the second media data set will not be received from the source device, the one or more processors are configured to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

16. A device according to claim 14, wherein the one or more processors are configured to receive the first media data set from the source device via a media data channel of the network, and wherein the one or more processors are configured to receive the data indicating that the second media data set will not be received from the source device via a signaling channel of the network, and the signaling channel is separate from the media data channel.

17. The device of claim 11, further comprising a display, wherein the one or more processors are further configured to: In the event that the media data will not be received, presenting a prompt to the user via the display requesting user consent to predictively generate replacement media data; and Input data is received from the user, the input data indicating that the user agrees to replacement media data predictively generated for the media bitstream.

18. The apparatus of claim 11, wherein the media data comprises at least one of video data or extended reality (XR) data, the XR data comprising at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

19. The device of claim 11, wherein the one or more processors are further configured to: Receiving a third media data set of the media bitstream; mixing at least a portion of the third set of media data with the replacement media data; and At least a portion of the mix of the third set of media data is presented after the replacement media data.

20. The apparatus of claim 11, wherein: To predictively generate the replacement media data, the one or more processors are configured to provide at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

21. A device for presenting media data, the device comprising: means for receiving a first set of media data of a media bitstream; means for predictively generating replacement media data for a second set of media data subsequent to the first set of media data using at least a subset of the first set of media data in response to determining that the second set of media data will not be received within a time period; as well as Means for presenting the first set of media data and the replacement media data.

22. The apparatus of claim 21, wherein means for receiving the first set of media data comprises means for receiving the first set of media data via a network, and further comprising means for determining that a network disruption will prevent reception of the second set of media data.

23. The apparatus of claim 22, further comprising a device for determining a start time of the network interruption and an end time of the network interruption, wherein the device for predictively generating the replacement data comprises a device for predictively generating the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

24. An apparatus according to claim 21, wherein the device for receiving the first media data set includes a device for receiving the first media data set from a source device via a network, and wherein the device for determining that the second media data set will not be received includes a device for receiving data from the source device indicating that the second media data set will not be received.

25. An apparatus according to claim 24, wherein the device for receiving from the source device an indication that the data of the second media data set will not be received includes a device for receiving at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

26. An apparatus according to claim 24, wherein the device for receiving the first media data set includes a device for receiving the first media data set from the source device via a media data channel of the network, and wherein the device for receiving the data indicating that the second media data set will not be received from the source device includes a device for receiving the data indicating that the second media data set will not be received from the source device via a signaling channel of the network, the signaling channel being separate from the media data channel.

27. The apparatus of claim 21, further comprising: means for presenting to the user a prompt requesting user consent to predictively generate replacement media data if the media data will not be received; as well as Means for receiving input data from the user, the input data indicating the user's agreement to replacement media data predictively generated for the media bitstream.

28. The apparatus of claim 21, wherein the media data comprises at least one of video data or extended reality (XR) data, the XR data comprising at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

29. The apparatus of claim 21, further comprising: means for receiving a third set of media data of the media bitstream; means for mixing at least a portion of the third set of media data with the replacement media data; as well as Means for presenting at least a portion of a mix of the third set of media data subsequent to the replacement media data.

30. The apparatus of claim 21, wherein: Means for predictively generating the replacement media data include means for providing at least a portion of the first set of media data to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

31. A computer readable storage medium having stored thereon instructions which, when executed, cause a processor to: Receiving a first media data set of a media bitstream; In response to determining that a second set of media data subsequent to the first set of media data for which the media bitstream will not be received within a time period, predictively generating replacement media data for the second set of media data using at least a subset of the first set of media data; and The first set of media data and the replacement media data are presented.

32. A computer-readable storage medium according to claim 31, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set via a network, and also include instructions causing the processor to determine that a network interruption will prevent reception of the second media data set.

33. The computer-readable storage medium of claim 32, further comprising instructions causing the processor to determine a start time of the network interruption and an end time of the network interruption, wherein the instructions causing the processor to predictively generate the replacement data include instructions causing the processor to predictively generate the replacement media data within a time period between the start time of the network interruption and the end time of the network interruption.

34. A computer-readable storage medium according to claim 31, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from a source device via a network, and also include instructions causing the processor to receive data from the source device indicating that the second media data set will not be received.

35. A computer-readable storage medium according to claim 34, wherein the instruction causing the processor to receive from the source device an indication that the data of the second media data set will not be received includes an instruction causing the processor to receive at least one of a supplemental enhancement information (SEI) message or a real-time transport protocol (RTP) message from the source device.

36. A computer-readable storage medium according to claim 34, wherein the instructions causing the processor to receive the first media data set include instructions causing the processor to receive the first media data set from the source device via a media data channel of the network, and wherein the instructions causing the processor to receive an indication from the source device that the data of the second media data set will not be received include instructions causing the processor to receive an indication from the source device via a signaling channel of the network that the data of the second media data set will not be received, the signaling channel being separate from the media data channel.

37. The computer-readable storage medium of claim 31 , further comprising instructions for causing the processor to: In the event that the media data will not be received, presenting a prompt to the user requesting the user's consent to predictively generate replacement media data; and Input data is received from the user, the input data indicating that the user agrees to replacement media data predictively generated for the media bitstream.

38. The computer-readable storage medium of claim 31, wherein the media data comprises at least one of video data or extended reality (XR) data, the XR data comprising at least one of augmented reality (AR) data, virtual reality (VR) data, or mixed reality (MR) data.

39. The computer-readable storage medium of claim 31 , further comprising instructions for causing the processor to: Receiving a third media data set of the media bitstream; mixing at least a portion of the third set of media data with the replacement media data; and At least a portion of the mix of the third set of media data is presented after the replacement media data.

40. A computer-readable storage medium according to claim 31, wherein the instructions causing the processor to predictively generate replacement media data include instructions causing the processor to provide at least a portion of the first media data set to an artificial intelligence (AI) process or a machine learning (ML) process configured to generate the replacement media data.

Images