Method, device, and computer-readable medium for processing alternative media presentation descriptions - Patents.com

By separating event start time and duration parameters in alternative MPD events, the method addresses inefficiencies in dynamic adaptive streaming, ensuring precise switching and improved advertising management in media streaming.

JP2024542607AActive Publication Date: 2024-11-15TENCENT AMERICA LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024531533
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-04-17
Filing Date
2023-04-18
Publication Date
2024-11-15
Estimated Expiration
2043-04-18

AI Technical Summary

Technical Problem

Existing media streaming technologies face challenges in handling alternative Media Presentation Description (MPD) events, particularly in dynamic adaptive streaming, leading to issues such as incorrect switching times and durations for advertisements, which affect the efficiency of pre-roll and mid-roll advertising.

Method used

A method and apparatus for processing alternative MPD events by separating the event start time and duration parameters, allowing precise switching between main and alternate media presentations, and incorporating return points for on-demand content, thereby enhancing the handling of advertising events.

Benefits of technology

This approach improves the accuracy and efficiency of media streaming by correctly managing switching times and durations for advertisements, enabling effective pre-roll and mid-roll advertising in dynamic adaptive streaming.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024542607000001_ABST
    Figure 2024542607000001_ABST
Patent Text Reader

Abstract

The present disclosure generally relates to media streaming technologies, and more particularly to a method and apparatus for processing an alternate media presentation description (MPD) using a main media presentation description (MPD) from a content server. The method includes receiving a manifest of the alternate MPD from a content server by a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device, parsing the manifest to extract a set of parameters of the alternate MPD, the set of parameters including at least one of a value of a DASH event stream, a presentation time, or a duration, switching from the main media presentation to the alternate media presentation based on the presentation time, and playing the main media presentation at a return point according to the value of the DASH event stream in response to an end of the alternate media presentation.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is based on and claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 332,590, filed April 19, 2022, which is incorporated by reference in its entirety. This application also is based on and claims the benefit of priority to U.S. Nonprovisional Patent Application No. 18 / 135,250, filed April 17, 2023, which is incorporated by reference in its entirety.

[0002] The present disclosure relates generally to media streaming technologies, and more particularly, to a method and apparatus for processing alternative media presentation descriptions (MPDs) in adaptive streaming. [Background technology]

[0003] This background discussion provided herein is intended to generally present the context of the present disclosure. To the extent described in this Background section, the inventors' work described herein, as well as aspects of the description that may not be admitted as prior art at the time of the effective filing of this application, are not admitted expressly or impliedly as prior art to the present disclosure.

[0004] Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) from Moving Picture Expert Group (MPEG) provides a standard for streaming multimedia content over IP networks. In the DASH standard, a Media Presentation Description (MPD) is used to provide information for a DASH client to adaptively stream media content by downloading media segments from a DASH server. The DASH standard enables streaming of multi-rate content. One aspect of the DASH standard includes the transport of MPD events and in-band events, and the client processing model used to handle the events.

[0005] The Common Media Application Format (CMAF) is a standard used to package and deliver various forms of HyperText Transfer Protocol (HTTP)-based media. The standard simplifies the delivery of media to playback devices, for example, by working with HTTP Live Streaming (HLS) and DASH protocols to package data under a uniform transport container file. It also uses chunked encoding and chunked transfer encoding to reduce latency.

[0006] MPEG DASH can provide several means for streaming multimedia content over IP networks, along with alternative MPD events for signaling media presentation between two timelines. There are various issues / problems with how to handle alternative MPD events.

[0007] This disclosure describes various embodiments for handling alternative MPD events that address at least one of the problems / challenges and advance the art of media streaming. Summary of the Invention [Means for solving the problem]

[0008] The present disclosure relates generally to media streaming technologies, and more particularly to a method and apparatus for processing alternative MPD events in dynamically adaptive streaming. The alternative MPD events may be sent by a media content server to a media streaming client, and then processed by the media streaming client.

[0009] According to one aspect, an embodiment of the present disclosure provides a method by a media streaming device for processing an alternate MPD using a main media presentation description (MPD) from a content server. The method includes the steps of receiving, by the media streaming device, a manifest for the alternate MPD from the content server, parsing the manifest to extract a set of parameters for the alternate MPD, the set of parameters including at least one of an event stream value, a presentation time, or a duration, where the presentation time indicates an offset at which the alternate media presentation starts in a timeline of the main media presentation, and the duration indicates a period during which the alternate media presentation is active, switching from the main media presentation to the alternate media presentation based on the presentation time, and playing the main media presentation at a return point according to the value of the event stream in response to an end of the alternate media presentation. The media streaming device includes a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device, and the event stream includes a DASH event stream.

[0010] According to another aspect, an embodiment of the present disclosure provides a method by a media streaming content server for configuring an alternate MPD using a main media presentation description (MPD) and sending the alternate MPD to a media streaming device. The configured MPD is configured to cause the media streaming device to perform any one of the method embodiments described in the present disclosure. The media streaming device includes a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device.

[0011] Aspects of the present disclosure also provide a media streaming device or apparatus including circuitry configured to perform any one of the above method embodiments.

[0012] Aspects of the present disclosure also provide a non-transitory computer-readable medium storing instructions that, when executed by a media streaming device, are configured to cause the media streaming device to perform any one of the method embodiments described above.

[0013] These and other aspects and implementations thereof are described in further detail in the drawings, specification, and claims.

[0014] Further features, nature and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 illustrates a system according to one embodiment of the present disclosure. [Diagram 2] FIG. 1 illustrates a Dynamic Adaptive Streaming over HTTP (DASH) system according to one embodiment of the present disclosure. [Figure 3A] FIG. 1 illustrates a DASH client architecture according to one embodiment of the present disclosure. [Figure 3B]FIG. 2 illustrates another DASH client architecture according to an embodiment of the present disclosure. [Figure 4] FIG. 1 illustrates a flow diagram of an exemplary embodiment of the present disclosure. [Diagram 5] FIG. 1 is a schematic diagram of a computer system according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The present invention will now be described in detail with reference to the accompanying drawings, which form a part hereof and which show, by way of illustration, specific examples of embodiments. It should be noted, however, that the present invention may be embodied in many different forms, and thus, the subject matter covered or claimed is not intended to be construed as being limited to any of the embodiments set forth below. It should also be noted that the present invention may be embodied as a method, device, component, or system. Thus, embodiments of the present invention may take the form of, for example, hardware, software, firmware, or any combination thereof.

[0017] Throughout this specification and the claims, terms may have subtle meanings that are suggested or implied in the context beyond the meaning explicitly stated. The phrases "in one embodiment" or "in some embodiments" used in this disclosure do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used in this disclosure do not necessarily refer to different embodiments. Similarly, the phrases "in one embodiment" or "in some embodiments" used in this specification do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used in this specification do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include all or part of the exemplary embodiments / implementations.

[0018] Generally, technical terms may be understood at least in part from their usage in context. For example, terms such as "and", "or", or "and / or" as used herein may include various meanings that may depend at least in part on the context in which such terms are used. Typically, "or" when used to relate a list such as A, B, or C is intended to mean A, B, and C, which are used herein in an inclusive sense, as well as A, B, or C, which are used herein in an exclusive sense. In addition, the terms "one or more" or "at least one" as used herein may be used to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense, depending at least in part on the context. Similarly, terms such as "a", "an", or "the" may also be understood to convey a singular usage or a plural usage, depending at least in part on the context. In addition, the terms "based on" or "determined by" may be understood as not necessarily intended to convey an exclusive set of factors, but instead may allow for the existence of additional factors not necessarily explicitly recited, also depending at least in part on the context.

[0019] Streaming via HyperText Transfer Protocol (HTTP) FIG. 1 illustrates an exemplary content delivery system 100 in which a remote information processing device 120 is configured to request content from one or more centralized or distributed content servers 110 via a communication network 130. In particular, the information processing device 120 may include a dedicated hardware component, a software component operating on general-purpose hardware, or a combination thereof, functioning as a content consumption application. The content consumption application may generate one or more requests that specify the content being requested and characteristics of the requested content. Each request may be built based on a stack of network protocols and communicated to the content server 110 via the communication network 130. In response, the content server may generate a bitstream according to the request, package the bitstream using the stack of network protocols, and communicate the bitstream package to the content consumption application.

[0020] In some exemplary implementations, content may be requested all at once. In other words, the entire media content may be requested, received, and stored locally by a content consumption application. The locally stored content may be processed (e.g., extracted, decoded, played) and consumed as needed, for example, by a media player, either as part of the content consumption application or separate from the content consumption application. Such a process may be referred to as downloading.

[0021] In some other implementations, content may be streamed as it is consumed, rather than downloaded for later consumption. In such implementations, the entirety of the requested content may not need to be stored in the content consumption application. Rather, only a limited amount of content is continuously received from the content server 110 on a rolling basis and managed by an input / output local buffer for content processing and playback. Such implementations may be referred to as streaming. Although some media playback functions, such as rewinding, fast-forwarding, and seeking, may involve complex media bitstream control and buffering, media streaming is typically more general purpose and better suited to the delivery of content that includes timed sequences of media that are not consumed repeatedly.

[0022] In the following disclosure, the terms "content" and "media" may be used interchangeably. The requested content may include various information items necessary for its consumption, including, but not limited to, the content itself and various metadata. The content itself may further include various media components, such as different tracks, including, but not limited to, video components / tracks, audio components / tracks, subtitles, etc. Metadata to describe the media content or provide additional processing information may be treated as one or more separate tracks. Such content with its metadata may be generated by the content server 120 as a bitstream that can be parsed and decoded according to a set of protocols or rules known to the content consumption application. The singular term "content server" is used to represent a single server or multiple servers located in a central location or distributed at various geographic locations. Such content servers may be implemented as dedicated computing machines or may be built as virtual machines and / or virtually housed in a cloud computing environment. Furthermore, in the following disclosure, the terms "information processing device" (see 120 in FIG. 1) and "content consumption application" may be used interchangeably. Alternatively, these terms may be referred to as "client", "client device / apparatus", "playback device / apparatus / client", etc. Note that although only one information processing device 120 is shown in Fig. 1, there may be multiple independent information processing devices. In other words, a set of content servers 110 may be configured to simultaneously and independently provide streaming services to multiple content consumption applications.

[0023] In some exemplary implementations, content generated for delivery by content server 110 can be segmented to facilitate their streaming. For example, a timed sequence of media content, such as a movie, can be chopped into time segments, each including several media frames. Each media segment can be self-contained such that its processing, including, for example, parsing, decoding, and playing, does not require information for other media segments. Media content may be pre-segmented. Thus, media content may be stored and managed by content server 120 on a segment-by-segment basis. Alternatively, media segments may be generated in real-time from contiguously stored media content as required during the streaming process. In some further implementations, media segmentation may be hierarchical, including multiple levels of segmentation.

[0024] In some particular implementations for streaming, the decision as to which media segment or which portion of a media segment to request from the content server 110 may be determined by the content consumption application in real time, as controlled by user playback instructions via a user application interface. In this manner, the content server may be configured to respond to the request, generate or retrieve the segment or portion of the content with their metadata in accordance with the request, and deliver the segment or portion of the segment over the network 130 to the requesting content consumption application.

[0025] In some exemplary implementations, the same media track of the media content may be prepared as different versions. For example, the same movie track may be prepared at different resolutions and / or frame rates. As another example, the same movie track may be prepared at different bit rates. As another example, the same audio movie may be prepared at different sound qualities and / or different numbers of audio channels (e.g., 5-channel sound, or 7-channel sound). Thus, the content consumption application may determine which version of the media track to stream and include such a selection in the request for the media content. Such a determination by the content consumption application may be based on one or more of several exemplary factors, including, but not limited to, the playback capabilities of the information processing device 120 (e.g., display resolution, decoding speed, processing power, buffer size, etc.), network bandwidth and throughput, etc. Thus, streaming sessions may be adapted between different media consumption applications according to their device capabilities. A streaming architecture configured in such a way may be referred to as adaptive streaming. The streaming process may further be adaptive within each media consumption application in that different versions of a media track may be selected and requested at different times during a streaming session, for example according to real-time network conditions (e.g., bandwidth and throughput, and bitrate supported by the network bandwidth). Streaming architectures so configured may further be referred to as dynamic adaptive streaming. In particular, streaming architectures configured to adapt to the bitrate of the media content may be referred to as dynamic adaptive bitrate streaming.

[0026] In some example implementations, requests by content consumption applications in dynamic adaptive streaming for specific versions or portions of segments of media content may be built based on a media manifest as a streaming session progresses. The term "manifest" may be used to refer to any collection of information items that describe media content, including segmentation, version, network location, and any other information that may be needed by a content consumption application to determine how and what to request at different times during a streaming session. A manifest may be generically referred to as a "Media Presentation Description" (MPD).

[0027] Such a manifest may be prepared at the content server side when a particular media content is created or generated. Such a manifest may be requested by a content consumption application and received from the content server at the start of a streaming session. The content consumption application may further request any updates to the manifest during the streaming session. Such a manifest may be used by the content consumption device as a blueprint for building subsequent requests for particular versions of segments or portions of segments of the media content during the streaming session.

[0028] In some exemplary implementations, the media server may be configured to function similarly to a web server from the standpoint of an external application. Thus, requests for media manifests and / or media segments or portions of media segments by a content consumption application may be made, for example, based on the HyperText Transfer Protocol (HTTP). In this manner, the request may be constructed as a URL and the requested content may be delivered as a response to the HTTP request from the content server.

[0029] The details of how the manifest is specified, the content is segmented, organized, versioned, and the HTTP request is constructed may depend on the particular adaptive streaming protocol, such as Dynamic Adaptive Streaming over HTTP (DASH), HTTP Live Streaming (HLS), Smooth Streaming Transport Protocol (SSTP), etc. Various additional exemplary embodiments below may be described in the context of DASH. However, the underlying principles are applicable to any type of adaptive streaming over HTTP. Additionally, the underlying principles are applicable to media content request mechanisms based on network protocols other than HTTP.

[0030] Dynamic Adaptive Streaming over HTTP (DASH) One exemplary protocol for implementing adaptive media streaming includes Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH). As mentioned above, DASH represents one of the adaptive bitrate streaming implementations that enables streaming of media content using a content delivery network (CDN) based on a hypertext transfer protocol (HTTP) infrastructure, including content servers configured as web servers with various proxies and caches. Such content servers may be referred to as DASH servers. Thus, the content consumption application described above may be referred to as a DASH client.

[0031] DASH supports live streaming from DASH servers to DASH clients and allows DASH clients to control the streaming session so that the DASH server does not have to deal with the additional burden of stream adaptation management in large-scale deployments. As mentioned above, DASH also allows DASH clients to select streaming from various DASH servers, thereby achieving further load balancing of the network for the benefit of the DASH clients. DASH further provides dynamic switching between different media versions of a media track, for example by varying the bit rate to adapt to the network conditions and processing capabilities of the DASH client.

[0032] In DASH, the above media manifest may be specifically referred to as an MPD (although the term MPD may be used generally to refer to any type of manifest in adaptive streaming systems other than those based on DASH). For example, an MPD in DASH may be constructed as a file that is fully or partially downloadable by a DASH client and provides items of information used by the DASH client to stream media content by selectively and adaptively requesting streaming media segments from a DASH server.

[0033] The MPD may be configured in various formats. For example, the MPD may be constructed in the form of an Extensible Markup Language (XML) document or file. The MPD file may be requested and delivered to the DASH client. The MPD file may be requested by HTTP, for example via an HTTP GET request. The MPD file may be delivered completely at the start of a streaming session. Alternatively, the MPD file may be fragmented and delivered in parts. In this way, parts of the MPD file may be requested and delivered before the start of streaming, and other parts of the MPD file may be requested and delivered to reduce session start delay (so that streaming can start from a previous media segment without having to wait for information items related to a later segment of media). The MPD file may also be updated during a streaming session (e.g., with segment information that is needed but not yet obtained).

[0034] In some exemplary implementations, an MPD file describes the segmentation of media content, the organization of the segments, and the available versions of the segments. MPD may support representation of content accessibility features, ratings, camera views, metadata, etc. DASH may also support delivery of multi-view and scalable coded content.

[0035] In some example implementations, an MPD file may include a series of descriptions of one or more periods along a media consumption timeline (e.g., playback time of video content). Each of the one or more periods may be defined, for example, by a "period" information element tag in the MPD file. Media content may be represented by an MPD file organized into multiple contiguous periods. The MPD file may identify a start time for each of the periods in the playback timeline. The start times may be defined as absolute start times from the beginning of the media content or as relative offsets from other reference points in the playback timeline.

[0036] In some example implementations, for each media period, the MPD file may further specify one or more adaptation sets. Different adaptation sets may be specified to capture different combinations (or subsets) of one or more of the media components. For example, video and audio may be different adaptation sets. Different versions of audio (stereo or multi-channel audio) may be different adaptation sets. Audio in different languages ​​may be different adaptation sets. In one particular example, the MPD file may specify that each period includes one video adaptation set and multiple audio adaptation sets, one for each supported language. The adaptation sets may also include subtitles and any metadata.

[0037] In some exemplary implementations, the adaptation sets of a particular period may be assigned to a group indicated by a group attribute in the MPD file. Adaptation sets in the same group are generally considered alternatives to each other. For example, each adaptation set of video data of a particular period may be assigned to the same group, so that any adaptation set may be selected for video data of the multimedia content of the corresponding period. Media content in one period may be from either one adaptation set or a combination of adaptation sets, with each group contributing at most one adaptation set.

[0038] In some exemplary implementations, each adaptation set may be specified by the MPD file as including one or more representations of the same media component of a corresponding duration. For example, a representation may be one of several alternative encoded versions of audio or video data. The representations may differ by encoding type, e.g., bitrate, resolution, and / or codec of the video data and bitrate and / or codec of the audio data. The term representation may be used to refer to a section of encoded media data that corresponds to a particular duration of multimedia content and that has been encoded in a particular way to achieve a particular range of average bitrates. In some exemplary implementations, for each representation in an adaptation set, the MPD file may specify attributes of the representation, including, but not limited to, video / audio type, video / audio codec, video frame width in pixels, video frame height in pixels, video / audio frame rate, and bandwidth (representing the average encoded bitrate).

[0039] Each representation of an adaptation set may also contain one or more media components, depending on the combination of media components included in the adaptation set. Each media component in a representation may correspond to an encoded version of one particular media type, such as audio, video, or timed text (e.g., for closed captioning). Media components may be temporally contiguous across boundaries of consecutive media segments within one representation.

[0040] In some example implementations, a representation may include one or more segments. Each representation may include an initialization segment, or each segment of a representation may be self-initialized. If present, the initialization segment may include initialization information for accessing the representation. In some cases, the initialization segment does not include media data. Segments that include media data may represent time-segmented content. Segments between different representations may be aligned in time. For each media segment, the MPD file may include a unique identifier. Such an identifier, when combined with a base URL, base URN, or base Uniform Resource Identifier (URI), may form a unique URL, URN, or URI that represents the network location of the media segment, which may be included in an HTTP request for this media segment and used by the content server to locate the requested segment for delivery.

[0041] For example, the URL for requesting a media segment must have a fixed scheme of "http" or "https". <absolute-uri>A byte range may be defined as a range of bytes, possibly further supplemented by a byte range if a range attribute is provided with the URL. A byte range may be expressed to identify a contiguous range of bytes within a segment.

[0042] In some further exemplary implementations, a sub-representation may be specified and described in an MPD file as being embedded (or included) in a regular representation, for example using a sub-representation element / indicator. A sub-representation element may be used to describe properties of one or more media content components embedded in a representation. For example, a sub-representation element may be used to describe properties of an embedded audio component (e.g., codec, sampling rate, etc.), an embedded subtitle (e.g., codec), or a sub-representation element may be used to describe some embedded lower quality video layers (e.g., some lower frame rate, etc.). Sub-representations and representation elements may share some common attributes and elements.

[0043] In some exemplary implementations, a DASH client can be configured to access, download, and request all or part of an MPD file from a DASH server. That is, the DASH client can obtain an MPD file that is used to start a live streaming session. Based on the MPD file and the selection of the representation, the DASH client can make several further decisions, including determining what the latest segment is available on the server, determining the segment availability start time of the next segment and possibly future segments, determining when to start playing a segment, and determining when to obtain / fetch / request a new MPD file.

[0044] In some example implementations, the MPD may further include information about DASH events to signal non-periodic information to a DASH client or DASH application. Events may be timed starting from a particular media presentation time having a duration. Additionally or alternatively, the event information may include a control message for a media player associated with a particular time during playback of a media presentation, such as an ad insertion cue. Media that may be inserted during streaming may be provided from a separate server, such as an ad server. In addition to signaling events by the MPD separately from the media representations, events may be in-band multiplexed within selected media representations, in only one or a few selected adaptation sets, or in all representations.

[0045] An exemplary DASH system 200 is shown in Figure 2. The DASH system 200 may include one or more centralized or distributed content servers 210 and information processing devices 230 connected by a network 250. The DASH system (200) may also include one or more supplemental content servers, such as one or more advertisement servers 220.

[0046] The content server 210 may provide the primary content (e.g., a main program) and its MPD to the information processing device 230. The manifest file may be generated by the MPD generator 214. The primary content and the manifest file may be provided by the same server or different servers.

[0047] The information processing device 230 may include a DASH client 232 that communicates directly with the content server 210. The DASH client 232 is controlled by a DASH application 234 of the information processing device 230 and may request and / or receive an MPD, or may request and obtain primary content from an HTTP server 212 of the content server 210 based on the MPD. The MPD may be processed by the DASH client 232. Furthermore, the DASH client 232 may obtain advertising content from the advertising server 220 or other content (e.g., interactive content) from one or more supplemental content servers in response to a DASH event. The main content and advertising content may be processed by the DASH client 232 or the DASH application 234 and displayed on a display device 236 of the information processing device 230. The display device 236 may be integrated with the information processing device 230 or may be external to the information processing device. Additionally, the DASH client 232 can extract other event information from one or more timed metadata tracks and send the extracted event information to the DASH application 234 for further processing. The DASH application 234 may be configured to display supplemental content based on the event information, for example.

[0048] An example of the DASH client 232 is shown in FIG. 3A. The exemplary DASH client 232 can include a DASH access engine 304, a selection logic 302, and media engines 306 and 308. The DASH access engine 302 can be configured to communicate with a content server, for example, to obtain a portion or all of the MPD of the streaming media, to request and obtain segment data of the streaming media that is dynamically requested, and to request supplemental media (advertisements) according to the MPD DASH events. The selection logic 304 can be configured to determine the next segment or segments to request, including the selection of an adaptation set and a representation. Such a determination can be determined, for example, by a user instruction and other real-time information such as network bandwidth and throughput. The media engine 306 can be configured to process the segment data received by the DASH access engine 302 according to the format (e.g., MPEG) of the media segments and the timing of the media segments to generate a main media output. The media engine 308 can be configured to process media content associated with timed DASH events from the DASH access engine 302, for example, to generate supplemental media output (e.g., advertisements) that can be inserted into the main media output.

[0049] 3B illustrates another exemplary DASH / CMAF client architecture for processing DASH and / or CMAF events, according to one embodiment of the disclosure. A DASH / CMAF client (or DASH / CMAF player) communicates with an application (390) and can be configured to process various types of events, including (i) MPD events, (ii) in-band events, and (iii) timed metadata events.

[0050] The manifest parser (305) parses a manifest (e.g., MPD). The manifest is provided, for example, by a content server (110, 210). The manifest parser (305) extracts event information about MPD events, in-band events, and timed metadata events embedded in timed metadata tracks. The extracted event information can be provided to the DASH logic (310) (e.g., control, selection, and heuristic logic of a DASH player). Based on the event information, the DASH logic (310) can inform the application (390) of the event scheme signaled in the manifest.

[0051] The event information may include event scheme information for distinguishing between different event streams. An application (390) may use the event scheme information to subscribe to event schemes of interest. The application (390) may further indicate a desired delivery mode for each of the subscribed schemes via one or more subscription APIs. For example, the application (390) may send a subscription request to a DASH client that identifies one or more event schemes of interest and any desired corresponding delivery modes.

[0052] If an application (390) subscribes to one or more event schemes that are delivered as part of one or more timed metadata tracks, the in-band event and "moof" parser (325) can stream one or more timed metadata tracks to the timed metadata track parser (330). For example, the in-band event and "moof" parser (325) parses a movie fragment box ("moof") and subsequently parses the timed metadata track based on control information from the DASH logic (310).

[0053] The timed metadata track parser (330) can extract event messages embedded in the timed metadata tracks. The extracted event messages can be stored in an event buffer (335) (e.g., an event buffer). The synchronizer / dispatcher module (340) (e.g., an event and timed metadata synchronizer and dispatcher) can emit (or send) subscribed events to an application (390).

[0054] MPD events described in the MPD may be parsed by a manifest parser (305) and stored in a buffer (335). For example, the manifest parser (305) parses each event stream element of the MPD and parses each event described in each event stream element. For each event signaled in the MPD, event information such as presentation time and event duration may be stored in a buffer (335) associated with the event.

[0055] An in-band event and "moof" parser (325) can parse the media segments to extract in-band event messages. Any such identified in-band events and associated presentation times and durations can be stored in a buffer (335).

[0056] Thus, the buffer (335) may store MPD events, in-band events, and / or timed metadata events therein. The buffer (335) may be, for example, a first-in, first-out (FIFO) buffer. The buffer (335) may be managed in correspondence with the media buffer (350). For example, as long as a media segment is present in the media buffer (350), any events or timed metadata corresponding to that media segment may be stored in the buffer (335).

[0057] The DASH Access Application Programming Interface (API) (315) can manage the fetching and receipt of content streams (or data flows) including media content and various metadata via the HTTP protocol stack (320). The DASH Access API (315) can separate the received content streams into different data flows. The data flows provided to the in-band event and moof parser can include media segments, one or more timed metadata tracks, and in-band event signaling included in the media segments. In one embodiment, the data flows provided to the manifest parser (305) can include an MPD.

[0058] The DASH Access API (315) can forward the manifest to the manifest parser (305). In addition to describing events, the manifest can also provide information about media segments to the DASH logic (310), which can communicate with the application (390) and the in-band event and "moof" parser (325). The application (390) can be associated with media content processed by the DASH client. Control and synchronization signals exchanged between the application (390), the DASH logic (310), the manifest parser (305), and the DASH Access API (315) can control the fetching of media segments from the HTTP stack (320) based on the information about the media segments described in the manifest.

[0059] The in-band event and moof parser (325) can parse the media data flow into media segments containing the media content, timed metadata in the timed metadata tracks, and any signaled in-band events in the media segments. The media segments containing the media content can be parsed by the file format parser (345) and stored in the media buffer (350).

[0060] The events stored in the buffer (335) can enable the synchronizer / dispatcher (340) to communicate available events related to (or of interest to) the application via an event / metadata API. Applications can be configured to process available events (e.g., MPD events, in-band events, or timed metadata events) and subscribe to specific events or timed metadata by notifying the synchronizer / dispatcher (340). Any events stored in the buffer (335) that are not related to an application but are instead related to the DASH client itself can be forwarded by the synchronizer / dispatcher (340) to the DASH logic (310) for further processing.

[0061] Depending on the application (390) subscribing to a particular event, the synchronizer / dispatcher (340) can communicate the application's event instances (or samples of timed metadata) that correspond to the event scheme to which the application subscribes. The event instances may be communicated according to a dispatch mode indicated by the subscription request or a default dispatch mode (e.g., for a particular event scheme). For example, in a dispatch-on-receive mode, the event instances may be sent to the application (390) upon receipt in the buffer (335), whereas in a dispatch-on-start mode, the event instances may be sent to the application (390) at their associated presentation times, for example, in synchronization with a timing signal from the media decoder (355).

[0062] In some implementations, the media segment engine (MSE) (395) can include a file format parser (345), a media buffer (350), and a media decoder (355). The MSE can receive media segments and generate decoded media outputs.

[0063] Configuring and Processing Alternative MPDs Some implementations enable streaming of multi-rate content and utilize alternate MPD events to switch media presentations between two timelines, i.e., one timeline for the main MPD events for the main media presentation and another timeline for the alternate MPD events for the alternate media presentation. There can be several issues / problems with the method of providing a client post-processing model.

[0064] For example, some implementations using the DASH design may include one or more of the following issues / challenges: no return point for on-demand content, an assumption that switch times are the same as event start times, and / or an assumption that advertisement (ad) durations are the same as event durations.

[0065] Various embodiments describe processing models for DASH clients to provide, dispatch, and post-process alternate MPD events. Some implementations provide different signaling and improved post-processing models to correctly handle alternate MPD events, for example, to enable pre-roll and / or mid-roll advertising efficiently and effectively.

[0066] Various embodiments may also address one or more of the problems described in this disclosure. For example, some embodiments may improve the media streaming field by one or more of adding a return point for on-demand content, separating these two parameters (switch time and event start time) to accurately achieve pre-rolls and mid-rolls, and / or separating these two parameters (ad duration and event duration) to correctly achieve switching to and from advertisements.

[0067] 3B, a client can request a media segment based on the address described in the manifest. The MSE buffer can include a pipeline of a file format parser, a media buffer, and a media decoder.

[0068] 4 shows an example flow diagram of an example method 400 by a media streaming device (e.g., a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device) for processing an alternative MPD using a main media presentation description (MPD) from a content server. The method 400 may include some or all of: receiving 410, by the DASH media streaming device, a manifest for the alternative MPD from the content server; parsing 420 the manifest to extract a set of parameters for the alternative MPD, the set of parameters including at least one of a value of an event stream (e.g., a DASH event stream), a presentation time, or a duration, where the presentation time indicates an offset at which the alternative media presentation starts in a timeline of the main media presentation, and the duration indicates a period for which the alternative media presentation is active; switching 430 from the main media presentation to the alternative media presentation based on the presentation time; and / or playing 440 the main media presentation at a return point according to a value of the DASH event stream in response to an end of the alternative media presentation.

[0069] In various embodiments, this disclosure provides a method for a media streaming content server to configure an alternate MPD using a main media presentation description (MPD), which the media streaming content server can send to a media streaming device, which can configure the media streaming device to perform part or all of method 400 or any other implementation described in this disclosure.

[0070] In some implementations, the presentation time is a different parameter than the actual switch time.

[0071] In some implementations, the duration is a different parameter than the actual duration of the alternative media presentation.

[0072] In some implementations, the values ​​of the event stream include a first value indicating a time shift and / or the main media presentation is played until a point in time when the main media presentation is switched to the alternative media presentation.

[0073] In some implementations, the value of the event stream includes a second value indicating replacement and / or in response to the first MPD type indicating dynamic, the main media presentation is played until a live edge of the main media presentation and / or in response to a second MPD type indicating static, the main media presentation is played until the point at which the main media presentation was switched to the alternative media presentation plus the actual duration of the alternative media presentation.

[0074] In some implementations, the alternative MPDs are processed and dispatched according to Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) event processing.

[0075] In some implementations, the step of ending the alternative media presentation includes at least one of the following: ending playback of the alternative media presentation at the end of its duration or stopping playback of the alternative media presentation when a stop command is received.

[0076] In some embodiments, depending on the MPD type indicating dynamic, depending on the value indicating substitution, the return point for playing the main media presentation is a live edge of the main media presentation, and / or depending on the value indicating time shifting, the return point for playing the main media presentation is the earliest available segment at or after the actual switch time.

[0077] In some embodiments, depending on the MPD type indicating static, depending on the value indicating substitution, the return point for playing the main media presentation is the sum of the actual switch time and the actual duration of the alternative media presentation, and / or depending on the value indicating timeshift, the return point for playing the main media presentation is the actual switch time.

[0078] A parameterization descriptor for a media segment request may be referred to as an MPD data structure. As a non-limiting example, an instantiated data structure of such type in the MPD, called "UrlQueryInfo", may include various attributes or descriptors used to provide a static and dynamic parameterization mechanism for media segments. In some further exemplary implementations, such static and dynamic parameterization mechanisms may be extended to other types of HTTP requests in addition to requests for media segments. An exemplary syntax for the extended data structure type may be specified and may be used to instantiate an MPD that includes corresponding data structures for signaling and specifying various types (or attributes or values) of parameterization.

[0079] Table 1 shows non-limiting examples of modified and / or improved semantics for alternative MPD signaling.

[0080] [Table 1]

[0081] Table 2 shows other non-limiting examples of modified and / or improved semantics for alternative MPD signaling.

[0082] [Table 2]

[0083] Various embodiments include a client post-processing model for alternative MPD events. In some implementations, the alternative MPD events are processed and dispatched according to typical DASH event processing. In some implementations, the alternative MPD events may be post-processed after they are dispatched. Table 3 shows non-limiting examples of parameters on which the event post-processing procedure may be based.

[0084] [Table 3]

[0085] In this disclosure, Uniform Resource Names (URNs) such as "urn:mpeg:dash:event:alternative:2022" may be defined and used, along with any substrings defined by the owner of the URN / URL scheme.

[0086] In one non-limiting example of a client alternative MPD switching event post-processing procedure, the method may include one or more of the following steps.

[0087] For step 1, the media streaming client (or media streaming device, or client) checks whether the alternative MPD Uniform Resource Locator (URL) in the message is in its Previously Played List (PPL).

[0088] For step 2, if the client determines that the alternative MPD URL is within its PPL, the client may take no further action, and / or if the client determines that the alternative MPD URL is not within its PPL, the client may continue with one or more of the following steps.

[0089] In step 3, the client downloads the alternative MPD.

[0090] For step 4, the client decides and performs one of the following cases:

[0091] For step 4-1, if the client determines that the current playback time is >= presentation time, it proceeds immediately to the next step, step 5. In some implementations, the current playback time may indicate the current time of the main media presentation and / or presentation_time may indicate a "target" time to switch to the alternative media presentation.

[0092] For step 4-2, when the client determines that current playback time < presentation time, the client continues playing the main media presentation until current playback time = presentation time, which satisfies step 4-1, and then proceeds to the next step.

[0093] For step 5, the client sets switch_time = current playback time and switches playback from the main media presentation to the alternative media presentation unless the main media presentation has ended, at which point it stops and clears its switch_time and PLL buffer.

[0094] For step 6, the client stores the main MPD URL and the switch_time.

[0095] In step 7, the client adds the message to its PPL.

[0096] In step 8, the client downloads the main MPD from the main MPD URL at the end of the alternative media presentation. The alternative media presentation may be terminated by at least one of terminating playback of the alternative media presentation at the end of the duration (i.e., the alternative media presentation completes its configured duration) or by stopping playback of the alternative media presentation upon receiving a stop command (i.e., the user or the content server terminates playback of the alternative media presentation before the alternative media presentation completes its configured duration).

[0097] For step 9, the client continues playing the main media presentation based on one of the following steps depending on the value and / or MPD type.

[0098] For step 9-1, depending on MPD@type='dynamic', if value='replacement', the playback time position is from the live edge, and / or if value='timeshift', the playback time position is from the earliest segment available after switch_time. In some implementations, @timeshiftBufferDepth may be set to a value equal to or greater than the maximum alternative media presentation duration to ensure that a media segment is available at switch_time when playback is switched back to the main media presentation.

[0099] For step 9-2, depending on MPD@type='static', if value='replace' the play time position is from (switch_time + duration of the alternative media presentation) and / or if value='timeshift' the play time position is from switch_time.

[0100] In some implementations, the DASH client clears its URL, switch_time, and PPL values ​​starting from the first parse of the main MPD and continues to maintain them throughout the entire playback.

[0101] In some implementations, the event presentation_time and duration indicate an active time interval of a media presentation during which the media presentation is switched to an alternative media presentation. The exact time of the switch (switch_time) depends on how the player reaches the active time interval, for example by linear playback up to its start time or by random access to a point in the middle.

[0102] Various embodiments may include a method for processing alternative MPD events, where the event start time and event duration are maintained as distinct parameters as the switch time and the alternative advertisement duration. The event start time and duration define a time interval during which the switching time may occur during which the switching time may vary depending on the linear playback of the content by the player or random access to the content, and the time of the switch back is defined by the alternative advertisement duration rather than the event duration. In the processing model, these values ​​are maintained and treated separately, and the signaling of the alternative MPD event semantics is defined in light of the described processing model.

[0103] The techniques described above may be implemented as computer software using computer-readable instructions and physically stored on one or more computer-readable media. For example, Figure 5 illustrates a computer system (500) suitable for implementing certain embodiments of the disclosed subject matter.

[0104] The computer software may be coded using any suitable machine code or computer language that can undergo mechanisms such as assembly, compilation, linking, etc. to produce code containing instructions that can be executed directly by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc., or that can be executed via interpretation, microcode execution, etc.

[0105] The instructions may be executed in various types of computers or components thereof including, for example, personal computers, tablet computers, servers, smartphones, gaming consoles, Internet of Things devices, and the like.

[0106] 5 for computer system (500) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing the embodiments of the present disclosure, nor should the arrangement of components be interpreted as having a dependency or requirement regarding any one or combination of components illustrated in the exemplary embodiment of computer system (500).

[0107] The computer system (500) may include certain human interface input devices. Such human interface input devices may be responsive to input by one or more users, such as, for example, tactile input (keystrokes, swipes, data glove movements, etc.), audio input (voice, clapping, etc.), visual input (gestures, etc.), olfactory input (not shown), etc. The human interface devices may also be used to capture media that is not necessarily directly associated with conscious human input, such as sound (speech, music, ambient sounds, etc.), images (scanned images, photographic images obtained from a still image camera, etc.), video (2D video, 3D video including stereoscopic video, etc.), etc.

[0108] The input human interface devices may include one or more of a keyboard (501), a mouse (502), a trackpad (503), a touch screen (510), a data glove (not shown), a joystick (505), a microphone (506), a scanner (507), and a camera (508) (only one of each is shown).

[0109] The computer system (500) may also include certain human interface output devices. Such human interface output devices may stimulate one or more of the human user's senses, for example, through haptic output, sound, light, and smell / taste. Such human interface output devices may include haptic output devices (e.g., haptic feedback via a touch screen (510), data gloves (not shown), or joystick (505), although some haptic feedback devices may not function as input devices), audio output devices (speakers (509), headphones (not shown), etc.), visual output devices (screens (510), including CRT screens, LCD screens, plasma screens, OLED screens, etc., each with or without touch screen input capability, each with or without haptic feedback capability, some of which may output two-dimensional visual output or three or more dimensional output by means of stereographic output, virtual reality glasses (not shown), holographic displays, and smoke tanks (not shown), and printers (not shown).

[0110] The computer system (500) may also include human accessible storage devices and associated media such as optical media (521) such as CD / DVD ROM / RW (520), including CDs / DVDs, thumb drives (522), removable hard drives or solid state drives (523), legacy magnetic media such as tapes and floppy disks (not shown), and specialized ROM / ASIC / PLD based devices such as security dongles (not shown).

[0111] Those skilled in the art will also appreciate that the term "computer-readable medium" as used in connection with the subject matter disclosed herein does not include transmission media, carrier waves or other transitory signals.

[0112] The computer system (500) may further include an interface (554) to one or more communication networks (555). The network may be, for example, wireless, wired, optical. The network may further be local, wide area, metropolitan, vehicular and industrial, real-time, delay tolerant, etc. Examples of networks include local area networks such as Ethernet, cellular networks including wireless LAN, GSM, 3G, 4G, 5G, LTE, etc., wired or wireless wide area digital networks including cable television, satellite television, and terrestrial broadcast television, vehicular and industrial including CAN bus, etc. Certain networks generally require an external network interface adapter connected to a particular general-purpose data port or peripheral bus (549) (e.g., a USB port on the computer system (500)), while others are generally integrated into the core of the computer system (500) by connection to a system bus as described below (e.g., an Ethernet interface to a PC computer system or a cellular network interface to a smartphone computer system). Using any of these networks, the computer system (500) can communicate with other entities. Such communications may be unidirectional, receive only (e.g., broadcast TV), unidirectional transmit only (e.g., from a CANbus to a particular CANbus device), or bidirectional, e.g., to other computer systems using local area digital networks or wide area digital networks. Specific protocols and protocol stacks may be used in each of these networks and network interfaces, as described above.

[0113] The aforementioned human interface devices, human accessible storage devices, and network interfaces may be connected to the core (540) of the computer system (500).

[0114] The cores (540) may include one or more central processing units (CPUs) (541), graphics processing units (GPUs) (542), dedicated programmable processing units in the form of field programmable gate areas (FPGAs) (543), hardware accelerators for specific tasks (544), graphics adapters (550), etc. Such devices may be connected via a system bus (548) along with read only memory (ROM) (545), random access memory (546), internal mass storage such as internal non-user accessible hard drives, SSDs, etc. (547). In some computer systems, the system bus (548) may be accessible in the form of one or more physical plugs to allow expansion with additional CPUs, GPUs, etc. Peripheral devices may be attached directly to the core's system bus (548) or via a peripheral bus (549). In an example, a screen (510) may be connected to the graphics adapter (550). Architectures for peripheral buses include PCI, USB, etc.

[0115] The CPU (541), GPU (542), FPGA (543), and accelerator (544) may execute certain instructions that may combine to constitute the aforementioned computer code. The computer code may be stored in ROM (545) or RAM (546). Transient data may be stored in RAM (546), while permanent data may be stored, for example, in internal mass storage (547). The use of cache memory, which may be closely associated with one or more of the CPU (541), GPU (542), mass storage (547), ROM (545), RAM (546), etc., allows for fast storage and retrieval from any memory device.

[0116] The computer-readable medium may bear computer code for performing various computer-implemented operations, and the medium and computer code may be those specially designed and constructed for the purposes of the present disclosure, or they may be of the kind well known and available to those skilled in the computer software arts.

[0117] As a non-limiting example, a computer system having the architecture (500), and specifically the core (540), may provide functionality as a result of a processor (including a CPU, GPU, FPGA, accelerator, etc.) executing software embodied in one or more tangible computer-readable media. Such computer-readable media may be the user-accessible mass storage devices introduced above, as well as media associated with the particular storage of the core (540) that is non-transitory in nature, such as the core internal mass storage (547) or ROM (545).

[0118] Software implementing various embodiments of the present disclosure may be stored in such devices and executed by the core (540). The computer-readable medium may include one or more memory devices or chips according to particular needs. The software may cause the core (540), and in particular the processor therein (including CPU, GPU, FPGA, etc.), to perform certain operations or certain parts of certain operations described herein, including defining data structures stored in RAM (546) and modifying such data structures according to software-defined operations. Additionally or alternatively, functionality may be provided as a result of hardwired or otherwise embodied logic in a circuit (e.g., accelerator (544)) that may operate in place of or together with software to perform certain processes or certain parts of certain processes described in the present application. Reference to software may encompass logic, and vice versa, as appropriate. Reference to computer-readable medium may encompass circuitry (such as integrated circuits (ICs)) that stores software for execution, circuitry that embodies logic for execution, or both, as appropriate. The present disclosure encompasses any suitable combination of hardware and software.

[0119] In the embodiments and implementations of the present disclosure, any steps and / or operations may be combined or arranged in any quantity or order as desired. Two or more of the steps and / or operations may be performed in parallel. The embodiments and implementations of the present disclosure may be used separately or combined in any order. Furthermore, each of the methods (or embodiments), clients, and servers may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program stored on a non-transitory computer-readable medium.

[0120] While this disclosure describes several exemplary embodiments, there are alterations, permutations, and various substitute equivalents that fall within the scope of this disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods that, although not explicitly shown or described herein, embody the principles of the present disclosure and are therefore within the spirit and scope of the present disclosure. [Explanation of symbols]

[0121] 100 Content Delivery System 110 Content Server 120 Information processing device 130 Communication Network 200 DASH System 210 Content Server 212 HTTP Server 214 MPD Generator 220 Ad Server 230 Information processing equipment 232 DASH client 234 DASH Applications 236 Display Devices 250 Network 302 DASH Access Engine 304 Selection Logic 305 Manifest Parser 306 Media Engine 308 Media Engine 310 DASH Logic 315 DASH Access API 320 HTTP protocol stack 325 in-band events and the 'moof' parser 330 Timed Metadata Track Parser 335 Event Buffer 340 Synchronizer / Dispatcher 345 File Format Parser 350 Media Buffer 355 Media Decoder 390 Applications 400 ways 500 Computer Systems 501 Keyboard 502 Mouse 503 Trackpad 505 Joystick 506 Mike 507 Scanner 508 Camera 509 Audio output device speaker 510 Touchscreen 520 CD / DVD ROM / RW 521 Optical Media 522 Thumb Drive 523 Solid State Drive 540 cores 541 Central Processing Unit (CPU) 542 Graphics Processing Unit (GPU) 543 Field Programmable Gate Area (FPGA) 544 Accelerator 545 Read-Only Memory (ROM) 546 Random Access Memory 547 Mass Storage 548 System Bus 549 Surrounding Bus 550 Graphics Adapter 554 Interface 555 Communication Network

Claims

1. 1. A method by a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device for processing an alternate media presentation description (MPD) using a main MPD from a content server, the method comprising: receiving, by the DASH media streaming device, a manifest for the alternative MPD from the content server; parsing the manifest to extract a set of parameters for the alternative MPD, the set of parameters including at least one of a DASH event stream value, a presentation time, or a duration, the presentation time indicating an offset at which an alternative media presentation starts in a timeline of a main media presentation, and the duration indicating a period for which the alternative media presentation is active; switching from a main media presentation to an alternative media presentation based on the presentation time; responsive to a completion of the alternative media presentation, playing the main media presentation at a return point according to the value of the DASH event stream; A method comprising:

2. The presentation time is a parameter different from the actual switching time. The method of claim 1.

3. the duration is a parameter different from the actual duration of the alternative media presentation. The method of claim 1.

4. the values ​​of the DASH event stream include a first value indicating a time shift; the main media presentation is played until a point at which the main media presentation is switched to the alternative media presentation.

4. The method according to any one of claims 1 to 3.

5. the values ​​in the DASH event stream include a second value indicating a substitution; in response to a first MPD type indicating dynamic, the main media presentation is played up to a live edge of the main media presentation; in response to a second MPD type indicating static, the main media presentation is played until the time when the main media presentation is switched to the alternative media presentation plus an actual duration of the alternative media presentation. The method of claim 1.

6. The alternative MPD is processed and dispatched according to Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) event processing. The method of claim 1.

7. The step of ending the alternative media presentation comprises: terminating playback of the alternative media presentation at the end of said duration; or stopping playing the alternative media presentation upon receiving a stop command; The method of claim 1 , comprising at least one of:

8. Depending on the MPD type that indicates dynamic, a return point for playing the main media presentation in response to the value indicating the substitution is a live edge of the main media presentation; depending on the value indicating a time shift, the return point for playing the main media presentation is the earliest segment available at or after an actual switch time.

8. The method according to any one of claims 1 to 7.

9. Depending on the MPD type, which indicates static, in response to the value indicating substitution, a return point for playing the main media presentation is the sum of an actual switch time and an actual duration of the alternative media presentation; in response to the value indicating a time shift, the return point for playing the main media presentation is the actual switch time.

8. The method according to any one of claims 1 to 7.

10. 10. A Dynamic Adaptive Streaming over HTTP (DASH) media streaming device for processing an alternative media presentation description (MPD) using a main MPD from a content server, the DASH media streaming device comprising: a memory for storing instructions; and a processor for executing the instructions to perform the method of any one of claims 1 to 9.

11. 10. A non-transitory computer-readable storage medium for storing instructions, the instructions being configured, when executed by a processor of a Dynamic Adaptive Streaming over HTTP (DASH) media streaming device for processing an alternate media presentation description (MPD) with a main media presentation description (MPD) from a content server, to cause the DASH media streaming device to perform the method of any one of claims 1 to 9.

Citation Information

Patent Citations

  • Server-side session control in media streaming by media player devices

    US20170134466A1

  • Edge media router device for facilitating distribution and delivery of media content having end-to-end encryption

    US20170195718A1

  • Playlist events for combining multiple media timelines and content-insertion in dash streaming

    US20210099746A1

  • Display device and method for controlling same

    US20220014292A1

  • Seamlessly playing a composite media presentation

    US9344472B2