Patent Description:
The present disclosure describes embodiments generally related to methods and apparatuses for dynamic adaptive streaming over hypertext transfer protocol (DASH).

Work of the presently named inventor, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Moving picture expert group (MPEG) dynamic adaptive streaming over hypertext transfer protocol (DASH) provides a standard for streaming multimedia content over Internet Protocol (IP) networks. The DASH standard allows carrying event message boxes in media segments.

<NPL>, proposes a method for URL customization through SBD.

"<NPL>, describes methods, interfaces and data for session-based operations to be used with the DASH standard.

According to a first aspect of the invention, there is provided a method according to independent claim <NUM>. According to a second aspect of the invention, there is provided an apparatus according to independent claim <NUM>. According to a third aspect of the invention, there is provided a non-transitory computer-readable storage medium according to independent claim <NUM>. Further embodiments are set out in the dependent claims.

Dynamic adaptive streaming over hypertext transfer protocol (DASH) is an adaptive bitrate streaming technique that enables streaming of media content using hypertext transfer protocol (HTTP) infrastructures, such as web servers, content delivery networks (CDNs), various proxies and caches, and the like. DASH supports both on-demand and live streaming from a DASH server to a DASH client, and allows the DASH client to control a streaming session, so that the DASH server does not need to cope with an additional load of stream adaptation management in large scale deployments. DASH also allows the DASH client a choice of streaming from various DASH servers, and therefore achieving further load-balancing of the network for the benefit of the DASH client. DASH provides dynamic switching between different media tracks, for example, by varying bit-rates to adapt to network conditions.

In DASH, a media presentation description (MPD) file provides information for the DASH client to adaptively stream media content by downloading media segments from the DASH server. The MPD file can be fragmented and delivered in parts to reduce session start-up delay. The MPD file can be also updated during the streaming session. In some examples, the MPD file supports expression of content accessibility features, ratings, and camera views. DASH also supports delivering of multi-view and scalable coded content.

The MPD file can contain a sequence of one or more periods. Each of the one or more periods can be defined by a period element in the MPD file. The MPD file can include an availableStartTime attribute for the MPD and a start attribute for each period. For media presentations with a dynamic type (e.g., used for live services), a sum of the start attribute of the period and the MPD attribute availableStartTime and the duration of the media segment can indicate the availability time of the period in coordinated universal time (UTC) format, in particular the first media segment of each representation in the corresponding period. For media presentations with a static type (e.g., used for on-demand services), the start attribute of the first period can be <NUM>. For any other period, the start attribute can specify a time offset between the start time of the corresponding period relative to the start time of the first period. Each period can extend until the start of the next period, or until the end of the media presentation in the case of the last period. Period start times can be precise and reflect the actual timing resulting from playing the media of all prior periods.

Each period can contain one or more adaptations sets, and each of the adaptation sets can contain one or more representations for the same media content. A representation can be one of a number of alternative encoded versions of audio or video data. The representations can differ by encoding types, e.g., by bitrate, resolution, and/or codec for video data and bitrate, and/or codec for audio data. The term representation can be used to refer to a section of encoded audio or video data corresponding to a particular period of the multimedia content and encoded in a particular way.

Adaptation sets of a particular period can 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 for a particular period can be assigned to the same group, such that any of the adaptation set can be selected for decoding to display video data of the multimedia content for the corresponding period. The media content within one period can be represented by either one adaptation set from group <NUM>, if present, or the combination of at most one adaptation set from each non-zero group, in some examples. Timing data for each representation of a period can be expressed relative to the start time of the period.

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

Each representation can also include one or more media components, where each media component can correspond to an encoded version of one individual media type, such as audio, video, or timed text (e.g., for closed captioning). Media components can be time-continuous across boundaries of consecutive media segments within one representation.

In some embodiments, the DASH client can access and download the MPD file from the DASH server. That is, the DASH client can retrieve the MPD file for use in initiating a live session. Based on the MPD file, and for each selected representation, the DASH client can make several decisions, including determining what is the latest segment that is available on the server, determining the segment availability start time of the next segment and possibly future segments, determining when to start playout of the segment and from which timeline in the segment, and determining when to get/fetch a new MPD file. Once the service is played out, the client can keep track of drift between the live service and its own playout, which needs to be detected and compensated.

It is noted that the MPD file can be generic for all DASH clients. In order to make the MPD file specific for a session of the DASH client, moving picture expert group (MPEG) provides session-based DASH operations. In session-based DASH operations, the DASH client can receive a side file, such as a session-based description (SBD) file, which provides instructions for the DASH client to customize the MPD file per session and possibly per client. However, in some related examples, the session-based DASH operation is application-specific. That is, for each new application, a new SBD format is required.

This disclosure includes methods for customizing or modifying a URL in a session-based DASH.

<FIG> shows an exemplary DASH system (<NUM>) according to an embodiment of the disclosure. In the DASH system (<NUM>), an MPD file is sent from a DASH server (<NUM>) (e.g., a content server) to a DASH client (<NUM>). The DASH client (<NUM>) can receive media segments from a server, such as the DASH server (<NUM>), based on the MPD file. The DASH client (<NUM>) can send a request to the DASH server (<NUM>) for updating the MPD file. The DASH server (<NUM>) can provide a content stream, including primary content (e.g., a main program) and one or more timed metadata tracks. In addition, the DASH client (<NUM>) can receive an SBD file from a server, such as the DASH server (<NUM>) or a third party (e.g., session controller).

According to aspects of the disclosure, the SBD file can include a plurality of time ranges and corresponding key-value pairs (or name-value pairs), along with additional metadata. The SBD file can be referenced in the MPD file by, for example, a URL. The SBD file can be used to customize the MPD file received by the DASH client (<NUM>) to be specific for a session of the DASH client (<NUM>). For example, the SBD file can allow adding session-specific elements to segment URLs without generating unique per-session MPDs.

<FIG> shows another exemplary session-based DASH operation architecture <NUM> according to an embodiment of the disclosure. In the session-based DASH operation architecture <NUM>, multimedia content is prepared and generated by a content generation device (<NUM>) (e.g., smartphone) which can include an audio source (e.g., microphone) and a video source (e.g., video camera). The multimedia content can be stored by the content generation device (<NUM>) or sent to a content server (<NUM>) which can store various multimedia contents. The content server (<NUM>) can receive a request from client devices, such as a DASH access client (<NUM>), for one or more media segments of the multimedia content. The multimedia content is described by an MPD file, which can be stored and updated by the content server (<NUM>) and accessed by the client devices including the DASH access client (<NUM>) to retrieve the media segments.

In order to retrieve a session-specific media segment, the DASH access client (<NUM>) can send a request to an SBD client (<NUM>) (e.g., session client) to access an SBD file that is received by the SBD client (<NUM>) and includes a plurality of time ranges and corresponding key-value pairs for the current session. For example, the DASH access client (<NUM>) can send a key name and a time range to the SBD client (<NUM>), which then parses the key name and the time range and returns a value corresponding to the key name and the time range to the DASH access client (<NUM>). The DASH access client (<NUM>) can include the value in a query of a segment URL which can be sent to the content server (<NUM>) for requesting the session-specific media segment when the segment request is a HTTP GET or partial GET request.

It is noted that the SBD client (<NUM>) can receive multiple SBD files from different session controllers, such as a session controller (<NUM>) and a session controller (<NUM>).

According to aspects of the disclosure, any or all of the features of the content server (<NUM>) (e.g., DASH server) can be implemented on one or more devices of a content delivery network (CDN), such as routers, bridges, proxy devices, switches, or other devices. The content server (<NUM>) can include a request processing unit configured to receive network requests from the client devices (e.g., DASH access client (<NUM>)). For example, the request processing unit can be configured to receive HTTP GET or partial GET requests and provide data of multimedia contents in response to the requests. The requests can specify a segment using a URL of the segment. In some examples, the requests can also specify one or more byte ranges of the segment, thus comprising partial GET requests. The request processing unit can further be configured to service HTTP HEAD requests to provide header data of a segment.

In some embodiments, the content generation device (<NUM>) and the content server (<NUM>) can be coupled by a wireless network or a wired network, or can be directly communicatively coupled.

In some embodiments, the content generation device (<NUM>) and the content server (<NUM>) can be included in a same device.

In some embodiments, the content server (<NUM>) and the session controllers (<NUM>)-(<NUM>) can be included in a same device.

In some embodiments, the content server (<NUM>) and the DASH access client (<NUM>) can be coupled by a wireless network or a wired network.

In some embodiments, the SBD client (<NUM>) and the session controllers (<NUM>)-(<NUM>) can be coupled by a wireless network or a wired network, or can be directly communicatively coupled.

In some embodiments, the DASH access client (<NUM>) and the SBD client (<NUM>) can be included in a same device.

According to aspects of the disclosure, in order to link multiple SBDs to an MPD, one or more essential property descriptors for session-based DASH can be used at an MPD level and each essential property descriptor for session-based DASH includes similar or same essential property descriptor attributes. Note that presentation descriptor can be either an essential property descriptor or a supplemental property descriptor. For an essential property, the media presentation author expresses that the successful processing of the descriptor is essential to properly use the information in the parent element that contains this descriptor unless the element shares the same @id with another EssentialProperty element. By contrast, for a supplemental property, the media presentation author expresses that the descriptor contains supplemental information that may be used by the DASH Client for optimized processing.

<FIG> shows an exemplary DASH client architecture according to an embodiment of the disclosure. The DASH client (or DASH player) can be configured to communicate with an application (<NUM>) and process various types of events, including (i) MPD events, (ii) inband events, and (iii) timed metadata events.

A manifest parser (<NUM>) can parse a manifest (e.g., an MPD). The manifest can be provided by the DASH server (<NUM>) for example. The manifest parser (<NUM>) can extract event information about MPD events, inband events, and timed metadata events embedded in timed metadata tracks. The extracted event information can be provided to a DASH logic (<NUM>) (e.g., DASH player control, selection, and heuristic logic). The DASH logic (<NUM>) can notify the application (<NUM>) of event schemes signaled in the manifest based on the event information.

The event information can include event scheme information for distinguishing between different event streams. The application (<NUM>) can use the event scheme information to subscribe to event schemes of interest. The application (<NUM>) can further indicate a desired dispatch mode for each of the subscribed schemes through one or more subscription application programming interfaces (APIs). For example, the application (<NUM>) can send a subscription request to the DASH client that identifies one or more event schemes of interest and any desired corresponding dispatch modes.

If the application (<NUM>) subscribes to one or more event schemes that are delivered as part of one or more timed metadata tracks, an inband event and 'moof' parser (<NUM>) can stream the one or more timed metadata tracks to a timed metadata track parser (<NUM>). For example, the inband event and `moof' parser (<NUM>) parses a movie fragment box ("moof") and subsequently parses the timed metadata track based on control information from the DASH logic (<NUM>).

The timed metadata track parser (<NUM>) can extract event messages embedded in the timed metadata track. The extracted event messages can be stored in an event and timed metadata buffer (<NUM>). A synchronizer/dispatcher module (<NUM>) (e.g., event and timed metadata synchronizer and dispatcher) can dispatch (or send) the subscribed events to the application (<NUM>).

MPD events described in the MPD can be parsed by the manifest parser (<NUM>) and stored in the event and timed metadata buffer (<NUM>). For example, the manifest parser (<NUM>) 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 can be stored in the event and timed metadata buffer (<NUM>) in association with the event.

The inband event and `moof p parser (<NUM>) can parse media segments to extract inband event messages. Any such identified inband events and associated presentation times and durations can be stored in the event and timed metadata buffer (<NUM>).

Accordingly, the event and timed metadata buffer (<NUM>) can store therein MPD events, inband events, and/or timed metadata events. The event and timed metadata buffer (<NUM>) can be a First-In-First-Out (FIFO) buffer, for example. The event and timed metadata buffer (<NUM>) can be managed in correspondence with a media buffer (<NUM>). For example, as long as a media segment exists in the media buffer (<NUM>), any events or timed metadata corresponding to that media segment can be stored in the event and timed metadata buffer (<NUM>).

A DASH Access API (<NUM>) can manage the fetching and reception of a content stream (or dataflow) including media content and various metadata through an HTTP protocol stack (<NUM>). The DASH Access API (<NUM>) can separate the received content stream into different dataflows. The dataflow provided to the inband event and 'moof' parser (<NUM>) can include media segments, one or more timed metadata tracks, and inband event signaling included in the media segments. In an embodiment, the dataflow provided to the manifest parser (<NUM>) can include an MPD.

The DASH Access API (<NUM>) can forward the manifest to the manifest parser (<NUM>). Beyond describing events, the manifest can also provide information on media segments to the DASH logic (<NUM>), which can communicate with the application (<NUM>) and the inband event and `moof' parser (<NUM>). The application (<NUM>) can be associated with the media content processed by the DASH client. Control/synchronization signals exchanged among the application (<NUM>), the DASH logic (<NUM>), the manifest parser (<NUM>), and the DASH Access API (<NUM>) can control the fetching of media segments from the HTTP Stack (<NUM>) based on information regarding media segments provided in the manifest.

The inband event and 'moof' parser (<NUM>) can parse a media dataflow into media segments including media content, timed metadata in a timed metadata track, and any signaled inband events in the media segments. The media segments including media content can be parsed by a file format parser (<NUM>) and stored in the media buffer (<NUM>).

The events stored in the event and timed metadata buffer (<NUM>) can allow the synchronizer/dispatcher (<NUM>) to communicate to the application (<NUM>) the available events (or events of interest) related to the application (<NUM>) through an event/metadata API. The application (<NUM>) can be configured to process the available events (e.g., MPD events, inband events, or timed metadata events) and subscribe to particular events or timed metadata by notifying the synchronizer/dispatcher (<NUM>). Any events stored in the event and timed metadata buffer (<NUM>) that are not related to the application (<NUM>), but are instead related to the DASH client itself can be forwarded by the synchronizer/dispatcher (<NUM>) to the DASH logic (<NUM>) for further processing.

In response to the application (<NUM>) subscribing to particular events, the synchronizer/dispatcher (<NUM>) can communicate to the application (<NUM>) event instances (or timed metadata samples) corresponding to event schemes to which the application (<NUM>) has subscribed. The event instances can be communicated in accordance with a dispatch mode indicated by the subscription request (e.g., for a specific event scheme) or a default dispatch mode. For example, in an on-receive dispatch mode, event instances may be sent to the application (<NUM>) upon receipt in the event and timed metadata buffer (<NUM>). On the other hand, in an on-start dispatch mode, event instances may be sent to the application (<NUM>) at their associated presentation time, for example in synchronization with timing signals from the media decoder (<NUM>).

It is noted that, in the DASH client architecture, the thick dataflow lines indicate media dataflow, the narrow dataflow lines indicate even and timed metadata dataflow, and the dash dataflow lines indicates control and synchronization. In addition, the same processing model can be used for CMAF events.

Session-based DASH operation is an important approach to customize the MPD per session and possibly per client. However, in some related examples, only a single key replacement can be allowed in each part of a given URL that is used for receiving media data. In addition, certain customizations, such as a fragment customization, may not be supported in the given URL and/or a manipulation of the given URL is not allowed. Furthermore, a part of the given URL can be only replaced with a template after the template is processed. Some operations such as modifying only a subset of parts instead of all parts of the given URL may result in the modified URL invalid in some cases.

This disclosure includes methods of modifying or customizing a part of the given URL with multiple keys. The disclosure also includes methods of adding a template in an MPD file for a fragment part of the given URL. The disclosure includes methods of manipulating a part of the given URL without using a processed template. In addition, the disclosure includes methods of avoiding a creation of an invalid URL part or an invalid entire URL, if a perfect match is necessary or required at a corresponding level.

According to aspects of the disclosure, an MPD file can include an essential property descriptor for an SBD file. The essential property descriptor can be referred to as an SBD descriptor. The SBD descriptor can include one or more elements or templates, of which each can be used for allowing multiple key replacements in a corresponding part of a URL. For example, the SBD descriptor can include a URL fragment template for modifying a fragment part of a URL. In addition, the SBD descriptor can include one or more flags to avoid a partial replacement of a URL template, if the partial replacement can result in an invalid URL part and/or an invalid entire URL.

A URL can include a host part, a port, a path part, and/or a fragment part. For example, a typical URL can be expressed as URI = scheme: [//authority] path[? query] [#fragment], where the authority part can be expressed as authority=[userinfo@]host[:port].

To enable multiple key replacements for a part of a URL, a URL customization process can be performed as follows. First, a template corresponding to the URL part can be allowed to include multiple keys. Then, the keys for the URL part can be grouped together.

In the URL customization process, if a fragment part of the URL is to be customized or modified, a template corresponding to the URL fragment and a key list for the URL fragment can be included in the SBD descriptor. In an embodiment, the URL fragment can be customized or modified as follows. First, a fragment template with one or more $key$ can be included in an MPD essential property descriptor (e.g., the SBD descriptor). The 'key' is a name of a parameter to be replaced in the URL fragment. The MPD essential property descriptor can also include the key list (e.g., a list of one or more keys) for customizing the URL fragment. Then, a DASH client can pass the URL to an SBD client after parsing the MPD essential property descriptor. The SBD client, for each key provided in the key list, searches an SBD file to determine whether the respective key matches a corresponding value in the SBD file. If the key is matched, the SBD client can process the fragment template by replacing the corresponding $key$ in the fragment template with the matched value. If the key is not matched, the SBD client can process the fragment template by replacing the corresponding $key$ in the fragment template with a default value for the key. In an example, the default value for the key is indicated by the key list included in the MPD file. Finally, the SBD client can customize or modify the URL fragment based on the processed fragment template.

In an embodiment, a URL part can be modified or manipulated without using a processed template. That is, the keys in the URL part can be replaced without using the processed template. For example, if a key occurs in the URL part at least once and is also included in the SBD file, a first occurrence of the key in the URL part can be replaced with a corresponding matched value in the SBD file. The key can be indicated by a corresponding element in the SBD descriptor. For example, a host key can be indicated by a host element.

In some related examples, if one or more but not all URL parts are modified to generate a modified URL, the modified URL may be invalid. To avoid generating an invalid modified or customized URL, a first flag such as a URL full match flag can be signaled in the SBD descriptor included in the MPD file in an embodiment. The first flag can indicate whether a full match of all parts of the URL is acceptable or required.

In some related examples, if one or more but not all keys in a URL part are replaced to generate a modified URL part, the modified URL part may be invalid. To avoid generating an invalid modified or customized URL part, a second flag such as a URL part full match flag can be signaled in the SBD descriptor included in the MPD file. The second flag can be signaled for one or each part of the URL. The second flag can indicate whether a full match of all keys of the URL part is acceptable or required.

According to aspects of the disclosure, an essential property descriptor for an SBD file (e.g., an SBD descriptor) included in an MPD file can be extended to include one or more elements and/or attributes to signal the above features. An exemplary extended version of the SBD descriptor can be shown in Table <NUM>.

One way to modify a URL part with multiple keys can be achieved by using one of attributes @hostTemplate, @portTempalte, @pathTemplate, and @fragmentTempalte included in the SBD descriptor, as shown in Table <NUM>. Each of these attributes can include multiple keys for a corresponding part of the URL. For example, the attribute @hostTemplate can include multiple URL host keys for a host part of the URL. An SBD client can search an SBD file for each of the multiple URL host keys to determine whether the respective URL host key is included in the SBD file. If one of the URL host keys is included in the SBD file, the SBD client can determine a value matched to the URL host key and modify a corresponding part of a host template with the matched value. The host template can be indicated by the attribute @hostTemplate. The SBD file can be indicated by the attribute @value. In this way, the URL host part can be modified or customized with multiple keys.

Another way to modify a URL part with multiple keys and without using a processed template can be achieved by using elements Host, Port, Path, and/or Fragment included in the SBD descriptor, as shown in Table <NUM>. Each of these elements can include multiple keys for a corresponding part of the URL. For example, the element Host can include multiple URL host keys for a host part of the URL. If one of the multiple URL host keys is in the URL host part, the SBD client can search the SBD file for the URL host key to determine whether the URL host key is included in the SBD file. If the URL host key is included in the SBD file, the SBD client can determine a value matched to the URL host key and replace a first occurrence of the URL host key in the URL host part with the matched value. In this way, the URL host part can be modified or customized with multiple URL host keys and without using a processed host template.

In order to avoid generating an invalid modified URL, the attribute @urlMatch can be included in the SBD descriptor, as shown in Table <NUM>. When the attribute @urlMatch is set to be 'true' and at least one of the URL host, path, port, or fragment is not modified, other modified part(s) cannot be valid and the URL remains unchanged. When the attribute @urlMatch is set to be 'false' and at least one of the URL host, path, port, or fragment is modified, the modified part(s) can be valid and the URL can be modified based on the modified part(s). For example, if the attribute @urlMatch is set to be 'true', and the URL host part is not modified while other URL parts are modified, the modified parts are not valid and the URL remains unchanged. If the attribute @urlMatch is set to be 'false' and the URL host part is modified, the modified URL host part is valid and the URL can be modified based on the modified URL host part.

In order to avoid generating an invalid modified URL part, the attributes @hostMatch, @portMatch, @pathMatch, and/or @fragmentMatch can be included in the SBD descriptor, as shown in Table <NUM>. If one of these attributes is set to be 'true' and at least one key in a template corresponding to the attribute is not included in the SBD file, the corresponding URL part remains unchanged. For example, if the element @hostMatch is set to be 'true' and at least one key of @hostTemplate is not included in the SBD file, then the URL host part remains unchanged. If the element @hostMatch is set to be 'false' and at least one key of @hostTemplate is included in the SBD file, then the URL host part can be modified based on the at least one key of @hostTemplate included in the SBD file.

According to aspects of the disclosure, for a segment URL of an element, if the element and/or a parent of the element include an SBD descriptor indicating a URL modification process, the segment URL can be processed by the SBD client for the URL modification. Accordingly, if each of the element and the parent(s) of the element includes an SBD descriptor indicating the URL modification process and corresponds to a different SBD file, multiple SBD files can be used by the SBD client for the modification of the segment URL.

This disclosure includes a method of customizing a part of a URL with multiple keys. The URL part can be a host part, a port part, a path part, or a fragment part of the URL. For each part, a set of one or more keys and optionally the corresponding default values can be included in an SBD descriptor in an MPD file. An SBD client can go through an SBD file for each key to find a matched value of the respective key in the SBD file and replace a part of a template corresponding to the URL part with the matched value included in the SBD file. If the match valued is not included in the SBD file, the part of the template corresponding to the URL part can be replaced with a default value.

This disclosure includes a method of adding a fragment template in an SBD descriptor for a URL fragment. A replacing process can be applied to a URL fragment based on the fragment template. The SBD descriptor includes a set of one or more keys and the corresponding default values for the URL fragment. An SBD client can search a value matched to each of the set of keys in an SBD file and apply the matched value to a corresponding part of the fragment template. In this way, the URL fragment can be replaced with the processed fragment template.

This disclosure includes a method of manipulating a URL instead of replacing a part of the URL with a processed template. If a key is included in the part of the URL and is also included in an SBD file, a corresponding value in the SBD file can be used to replace a first occurrence of the key in the part of the URL.

This disclosure includes a method of signaling that only a full match of all keys for a URL part is acceptable. That is, if one or more keys for the URL part are not included in an SBD file, then the URL part is not replaced. The signaling can be provided on a URL part basis such that this constraint is not necessarily applied to each of the URL parts for the URL.

This disclosure includes a method of signaling that only a full match of all parts of a URL is acceptable. In an embodiment, if one or more parts of the URL are not replaced with a new one resulted by an SBD process, then the other replaced part(s) of the URL is not acceptable either and the entire URL shall not be changed. In an embodiment, if the essential property descriptor included in the MPD file indicates that only a subset of (but not all) the parts of the URL is to be modified, then the entire URL shall not be changed. For example, if the template and/or key list corresponding to a URL part are not included in the essential property descriptor, then the URL part is not to be modified, then the entire URL shall not be changed even the other URL part(s) are modified.

<FIG> shows a flow chart outlining a process (<NUM>) according to an embodiment of the disclosure. In various embodiments, the process (<NUM>) is executed by processing circuitry, such as the processing circuitry in the DASH client (<NUM>). In some embodiments, the process (<NUM>) is implemented in software instructions, thus when the processing circuitry executes the software instructions, the processing circuitry performs the process (<NUM>). The process (<NUM>) starts at (S410), where the process (<NUM>) receives an MPD file that includes an essential property descriptor for session-based DASH. The essential property descriptor indicates an SBD file and includes a set of keys for a part of a URL that is used for receiving the media data. Then, the process (<NUM>) proceeds to step (S420).

At step (S420), the process (<NUM>) determines a respective value for each of the set of keys based on whether the respective value is included in the SBD file. Then, the process (<NUM>) proceeds to step (S430).

At step (S430), the process (<NUM>) modifies the URL based on the set of keys and the determined values. Then, the process (<NUM>) terminates.

In an embodiment, the part of the URL is one of a host part, a port part, a path part, and a fragment part of the URL.

In an embodiment, the set of keys is one of (i) a set of URL host keys, (ii) a set of URL port keys, (iii) a set of URL path keys, and (iv) a set of URL fragments keys.

In an embodiment, the process (<NUM>) determines whether a value for one of the set of keys is included in the SBD file. The process (<NUM>) determines the value included in the SBD file for the one of the set of keys based on the value for the one of the set of keys being included in the SBD file. The process (<NUM>) determines the value for the one of the set of keys to be a default value based on the value for the one of the set of keys not being included in the SBD file. The default value is included in the essential property descriptor.

In an embodiment, the set of keys is indicated by a template included in the essential property descriptor. The process (<NUM>) processes the template based on the determined values. The template corresponds to the part of the URL. The process (<NUM>) modifies the URL based on the processed template.

In an embodiment, the template is a fragment template based on the part of the URL being a fragment part.

In an embodiment, the set of keys is included in the part of the URL and indicated by a key element that is included in the essential property descriptor and corresponds to the part of the URL. The process (<NUM>) replaces, for each of the set of keys, a first occurrence of the respective key in the part of the URL with the determined corresponding value.

In an embodiment, the key element is one of a URL host key element, a URL port key element, a URL path key element, and a URL fragment key element.

In an embodiment, the part of the URL is one of a plurality of parts of the URL, and the essential property descriptor includes a first flag indicating whether a full match of all the parts of the URL is required. The process (<NUM>) determines that the URL is not to be modified based on at least one part of the URL not being modified and the first flag indicating that the full match of all parts of the URL is required. The process (<NUM>) determines that the URL is to be modified based on the at least one part of the URL being modified and the first flag indicating that the full match of all parts of the URL is not required.

In an embodiment, the essential property descriptor includes a second flag indicating whether a full match of all keys for the part of the URL is required. The process (<NUM>) determines that the part of the URL is not to be modified based on at least one key for the part of the URL not being included in the SBD file and the second flag indicating that the full match of all keys for the part of the URL is required. The process (<NUM>) determines that the part of the URL is to be modified based on the at least one key for the part of the URL being included in the SBD file and the second flag indicating that the full match of all keys for the part of the URL is not required.

Input human interface devices may include one or more of (only one of each depicted): keyboard (<NUM>), mouse (<NUM>), trackpad (<NUM>), touch screen (<NUM>), data-glove (not shown), joystick (<NUM>), microphone (<NUM>), scanner (<NUM>), and camera (<NUM>).

These visual output devices (such as screens (<NUM>)) can be connected to a system bus (<NUM>) through a graphics adapter (<NUM>).

Computer system (<NUM>) can also include a network interface (<NUM>) to one or more communication networks (<NUM>). The one or more communication networks (<NUM>) can for example be wireless, wireline, optical. The one or more communication networks (<NUM>) can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of the one or more communication networks (<NUM>) include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, <NUM>, <NUM>, <NUM>, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters that attached to certain general purpose data ports or peripheral buses (<NUM>) (such as, for example USB ports of the computer system (<NUM>)); others are commonly integrated into the core of the computer system (<NUM>) by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks, computer system (<NUM>) can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

These devices, along with Read-only memory (ROM) (<NUM>), Random-access memory (<NUM>), internal mass storage such as internal non-user accessible hard drives, SSDs, and the like (<NUM>), may be connected through the system bus (<NUM>).

Claim 1:
A method (<NUM>) of receiving media data, comprising:
receiving (S410) a media presentation description, MPD, file that includes an essential property descriptor for session-based dynamic adaptive streaming over hypertext transfer protocol, DASH, the essential property descriptor indicating a session-based description, SBD, file and including a set of keys for a part of a uniform resource locator, URL, that is used for receiving the media data;
determining (S420) a respective value for each of the set of keys based on whether the respective value is included in the SBD file; and
modifying (S430) the URL based on the set of keys and the determined values;
wherein
the part of the URL is one of a plurality of parts of the URL,
the essential property descriptor includes a first flag indicating whether a full match of all the parts of the URL is required, and
the method further comprises:
determining that the URL is not to be modified based on at least one part of the URL not being modified and the first flag indicating that the full match of all parts of the URL is required; and
determining that the URL is to be modified based on the at least one part of the URL being modified and the first flag indicating that the full match of all parts of the URL is not required.