WO2019148498A1 - Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau - Google Patents

Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau Download PDF

Info

Publication number
WO2019148498A1
WO2019148498A1 PCT/CN2018/075303 CN2018075303W WO2019148498A1 WO 2019148498 A1 WO2019148498 A1 WO 2019148498A1 CN 2018075303 W CN2018075303 W CN 2018075303W WO 2019148498 A1 WO2019148498 A1 WO 2019148498A1
Authority
WO
WIPO (PCT)
Prior art keywords
dash
middleware
representation base
dane
manifest
Prior art date
Application number
PCT/CN2018/075303
Other languages
English (en)
Inventor
Jie LING
Thorsten Lohmar
Jinyang Xie
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to US15/757,586 priority Critical patent/US10601886B2/en
Priority to EP18903650.2A priority patent/EP3750303B1/fr
Priority to PCT/CN2018/075303 priority patent/WO2019148498A1/fr
Publication of WO2019148498A1 publication Critical patent/WO2019148498A1/fr
Priority to US16/804,857 priority patent/US11038941B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/764—Media network packet handling at the destination 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/70—Media network packetisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/765—Media network packet handling intermediate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/845—Structuring of content, e.g. decomposing content into time segments
    • H04N21/8456—Structuring of content, e.g. decomposing content into time segments by decomposing the content in the time domain, e.g. in time segments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
    • H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL

Definitions

  • the present invention generally relates to DASH players and, more specifically, to a method for switching between a default content delivery network and a secondary content delivery network for fetching media segments.
  • Multimedia Broadcast Multicast Services is a point-to-multipoint interface specification for existing and upcoming 3GPP cellular networks.
  • the interface specification is developed to provide for an efficient delivery of broadcast and multicast services.
  • the specification is referred to as Evolved Multimedia Broadcast Multicast Services, eMBMS, when transmissions are delivered through an Long Term Evolution, LTE, network.
  • eMBMS is also known as LTE Broadcast.
  • Typical application that may utilize the MBMS include radio broadcasting, live streaming video, mobile television, as well as file delivery and emergency alerts.
  • the third generation Partnership Project, 3GPP has defined Multimedia Broadcast Multicast Services, MBMS, operation on Demand, MooD, within 3GPP Release 12.
  • the prescribed solution is based on a Device Local HTTP Proxy Server, which is capable of forwarding media content received from a unicast content delivery network or from a broadcast content delivery network.
  • a Moving Picture Experts Group, MPEG, Server and Network Assisted Dynamic Adaptive Streaming over HTTP, MPEG-DASH, based solution was studied and documented, informatively, in TR 26.946.
  • MPEG SAND has introduced server and network assistant DASH and is defined in MPEG as ISO/IEC 23009-5. SAND defines a set of messages, which can be used for QoE reporting and network assistance, for example:
  • PER Parameters Enhancing Reception
  • SAND messages have been adopted in 3GPP, see for example 26.247. Work is currently on-going to use a SAND out-of-band DANE to enable switching between unicast and broadcast (MooD) . Parts of the prescribed solution is, informatively, described in TR 26.946 -Section 7.2.4.
  • the DASH Media Presentation Description, MPD for example an XML document containing information about media segments, contains multiple representations. Some representations are only available for unicast retrieval. Some other representations are available for unicast retrieval and are also broadcasted inside of an MBMS coverage area.
  • the MBMS User Service Description, USD contains information around switchable representations. The idea is that the DANE controls, which representations are available, when the device is in broadcast coverage and which ones not.
  • the DASH Player When starting the Streaming session, the DASH Player opens a SAND communication channel to the DANE, which is aware about unicast and broadcast coverage. The DASH Player is the steered using SAND PER messages.
  • the current SAND based MooD solution requires a prepared manifest (MPD) .
  • MPD This manifest is called unified MPD.
  • the manifest contains an absolute base URL so that the segments can be fetched from a different server than the manifest. Further, the manifest must contain unique based URLs for a local server and a remote server.
  • the Broadcast Multicast Service Center is responsible to create and provide the unified MPD, including all the extra elements, to the MBMS User Equipment.
  • Some of the information is the hostname of the local HTTP server. Every device vendor may select an own hostname, depending on other local services.
  • the BM-SC would need to condition the manifest only to describe the broadcasted available representations.
  • the BM-SC or the MBMS client do not condition the manifest, i.e. for this particular switching situation between unicast and broadcast.
  • the problem may also be phrased more general.
  • Many SAND messages require a unique identification of representations inside the manifest.
  • the packager is responsible of creating the manifest according to the produced content. It seems to become a restriction and unnecessary constrain to require, that the packager creates a SAND compliant manifest, with all the SAND specific information in it. It is also not preferred to condition the manifest.
  • UE User Equipment
  • a Dynamic Adaptive Streaming over HTTP, DASH, player to fetch media segments from a network.
  • the method comprises the steps of:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • ManifestModificationCommand message comprises one or more representation base URI’s of any of said default representation base URI and said secondary representation base URI that are to modify a representation base URI in said manifest.
  • the basic concept of the present disclosure is that the DANE middleware does not need to alter the manifest.
  • the DANE middleware transmits a ManifestModificationCommand to the DASH player, thereby instructing the DASH player to modify the representation base URI’s in the manifest.
  • the DANE middleware may request the DASH player to update, modify or extend the representation base URI in the manifest whenever there is a switch required between the source of the media segments, i.e. between a default content delivery network and a secondary content delivery network.
  • the above is valid for situations in which there is a switch between a unicast content delivery network and a broadcast content delivery network or between multi unicast content delivery networks or between multi broadcast content delivery networks.
  • the DANE middleware is able to steer the DASH player by making the specific media segments available, or unavailable, at the default content delivery network or the secondary content delivery network.
  • the manifest may be in MPD format as received from a particular server, for example an XML file, or in DASH Player internal representation.
  • a DASH Player parses the manifest in a first step and then brings the manifest into a generic software-internal representation, like a hierarchical organized object.
  • MPEG-DASH allows several different manifest types.
  • the advantage of the present disclosure is that the need for manifest conditioning for the DANE middleware is reduced. Instead, only a SAND channel may be defined, inside of the manifest or outside, and the DANE middleware can interact with the DASH player to add, modify or extend missing identifiers.
  • the method further comprises the step of:
  • the DASH player may, actively, request the DANE middleware for a modification of the manifest. For example, the DASH player may notice that it is not able to fetch particular media segments from a default content delivery CDN. As a result, it may request a manifest modification from the DANE middleware.
  • the DANE middleware may push the modification of the manifest towards the DASH player.
  • the DANE middleware comprises a Multimedia Broadcast Multicast Service, MBMS, client for receiving said manifest, said default representation base URl and said secondary representation base URl, wherein:
  • said default representation base URI is a broadcast representation base URI which is available in a broadcast mode for fetching said media segments from a broadcast content delivery network, CDN;
  • said secondary representation base URI is a unicast representation base URI which is available in a unicast mode for fetching said media segments from a unicast content delivery network, CDN.
  • the above is directed to the example in which the default content delivery network is a broadcast CDN and wherein the secondary content delivery network is a unicast CDN.
  • the step of transmitting said manifest to said DASH player comprises defining a Server and Network Assisted DASH, SAND, channel between said DASH player and said DANE middleware.
  • the step of defining may comprise any of:
  • the method further comprises the step of:
  • said method further comprises any of the steps of:
  • a Dynamic Adaptive Streaming over HTTP, DASH, player to fetch media segments from a telecommunication network, wherein said method comprises the steps of:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • a ManifestModificationCommand message comprising one or more representation base URI’s of any of:
  • the method further comprises the step of:
  • the step of receiving said manifest from said DANE middleware comprises defining a Server and Network Assisted DASH, SAND, channel between said DASH player and said DANE middleware.
  • the step of defining comprises any of:
  • the method further comprises the step of:
  • said method further comprises any of the steps of:
  • a User Equipment arranged for enabling a Dynamic Adaptive Streaming over HTTP, DASH, player to fetch media segments from a network
  • said UE comprises DASH Aware Network Element, DASH, middleware comprising:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • ManifestModificationCommand message comprises one or more representation base URI’s of any of said default representation base URI and said secondary representation base URI that are to modify a representation base URI in said manifest.
  • the receive equipment is further arranged for receiving, from said DASH player, a ManifestModificationRequest message for requesting a modification of said manifest.
  • said transmit equipment is further arranged for defining a Server and Network Assisted DASH, SAND, channel between said DASH player and said DANE middleware.
  • the transmit equipment is arranged for defining said SAND channel by:
  • the DANE middleware comprises a Multimedia Broadcast Multicast Service, MBMS, client for receiving said manifest, said default representation base URI and said secondary representation base URI, wherein:
  • said default representation base URI is a broadcast representation base URI which is available in a broadcast mode for fetching said media segments from a broadcast content delivery network, CDN;
  • said secondary representation base URI is a unicast representation base URI which is available in a unicast mode for fetching said media segments from a unicast content delivery network, CDN.
  • the receive equipment is further arranged for receiving, from said DASH player, a SAND message for multi content delivery network operations for checking resource availability for said representation base URI in said manifest,
  • said DANE middleware further comprises inform equipment arranged for any of:
  • a User Equipment arranged to fetch media segments from a network
  • said UE comprises a Dynamic Adaptive Streaming over HTTP, DASH, player which comprises:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • said receive equipment is further arranged for receiving, from said DANE middleware, a ManifestModificationCommand message comprising one or more representation base URI’s of any of a
  • the UE further comprises transmit equipment arranged for
  • the receive equipment is further arranged for receiving said manifest from said DANE middleware by defining a Server and Network Assisted DASH, SAND, channel between said DASH player and said DANE middleware.
  • the defining comprises any of:
  • the UE comprises transmit equipment arranged for transmitting, to said DANE middleware, a SAND message for multi content delivery network operations for checking resource availability for said representation base URI in said manifest,
  • said receive equipment is further arranged for receiving, from said DANE middleware, information that said secondary representation base URI is available in case secondary mode is unavailable and default mode is available;
  • said receive equipment is further arranged for receiving, from said DANE middleware, information that said default representation base URI is available in case default mode available.
  • a computer program product containing computer program code which, when executed by a User Equipment, UE, cause the UE to implement a method according to any of the examples as provided above.
  • Figure 1 discloses an architecture enabling the exchange of SAND messages
  • Figure 2 discloses an architecture in which a particular device is able to switch between a default content delivery network and a secondary content delivery network
  • Figure 3 discloses an architecture in which an embodiment according to the present disclosure is explained
  • Figure 4 discloses a workflow describing an example of how DASH a player, a DANE and MBMS Client work together with network entities to achieve the MooD and service continuity;
  • Figure 5 discloses a flowchart illustrating an example of a method in accordance with the present disclosure
  • Figure 6 discloses a flowchart illustrating another example of a method in accordance with the present disclosure.
  • Figure 1 discloses an architecture 10 enabling the exchange of SAND messages.
  • the architecture 10 comprises a metrics server 13, a DASH client 12 and two DANE’s 11.
  • SAND defines a set of messages, which can be used for Quality of Experience, QoE, reporting.
  • Parameters Enhancing Reception, PER, messages 14 are sent from the DANE’s 11 to the DASH client 12.
  • Status messages 15 are sent from the DASH client 12 to the DANE’s .
  • Other SAND messages like PED messages 16 and metrics messages 17, are exchanged between the DANE’s 11 and between the DASH client 12 and the Metrics server 13, respectively.
  • SAND messages have been adopted in 3GPP which are focussed on the use of a SAND out-of-band DANE to enable switching between unicast, for example a default content delivery network, and broadcast, for example a secondary content delivery network.
  • Figure 2 discloses an architecture 50 in which a particular device 51 is able to switch between a default content delivery network 56 and a secondary content delivery network 57, which all of those originate from an encoder and packager 58.
  • the architecture 50 is explained in more detail here below.
  • a manifest is required by the DASH player 52 to fetch the media segments from a content delivery network.
  • the manifest contains a base URL so that the segments may be fetched from a different server.
  • the Broadcast Multicast Service Center, BM-SC 57 is responsible for creating the manifest and for providing the manifest to the local server 55 of an MBMS client 53.
  • the DASH player 52 may communicate with the local server 55, and may communicate with the DANE 54 using, for example, SAND messages.
  • the secondary content delivery network 56 is responsible, in unicast mode, 59, to provide for the media segments.
  • Figure 3 discloses an architecture 100 in which an embodiment according to the present disclosure is explained.
  • the UE 101 comprises a DASH player 52, a client application 103 and a DANE middleware 104, 11.
  • the DASH content encoder 114 is responsible for the encoding of the content and for pushing the manifest, for example an XML file, to the content delivery network An operator will select one track for the broadcasting. Dash Encoding may put the selected track segment files to BM-SC 57, or the BM-SC 57 will pull the segment file from the CDN 56.
  • the operator may create the broadcast service, and may send the service announcement to the corresponding UEs through the broadcast delivery or unicast delivery, i.e. via the CDN 56 of the BM-SC 57.
  • the service announcement may include the original manifest, source URIs for the broadcast and unicast access.
  • the UE may receive the service announcement, and may consume the service based on the broadcast coverage to use the unicast access or broadcast access.
  • the broadcast mode may be viewed as the default content delivery network and the unicast mode may be viewed as the secondary content delivery network.
  • the media segments may be provided to the UE 101 using the RAN 106 via which the UE 101 is connected to the network, i.e. the Evolved Packet Core, EPC ⁇ 107 or the MBMS-GW 108.
  • the DANE may pull PER messages from the DANE or the DAN may push PER messages to the DASH player.
  • the DASH player is to pull PER messages from the DANE.
  • the DASH Player 52 may receives a manifest, which may define a SAND communication channel between the DASH player 52 and the DANE 11.
  • a manifest may define a SAND communication channel between the DASH player 52 and the DANE 11.
  • the SAND channel may be defined inside of the manifest or as part of, for example, HTTP response headers.
  • the DASH player 52 may send a ManifestModificationRequest SAND PER message to the DANE 11.
  • a message requests the DAN player for a modification of the manifest.
  • the message may be sent, by the DASH player 11, in case it has found issues with obtaining the media segments from a particular content delivery network, for example.
  • the DANE 11 may then generate and transmit a ManifestModificationCommand message, wherein that particular message comprises one or more representation base URI’s of a default representation base URI and a secondary representation base URI that is to modify a representation base URI in the manifest.
  • the DANE 11 provides a message to the DASH player 11 instructing the dash player to use a different location for fetching the media segments compared to the location that is actually present in the manifest.
  • the DASH player 52 receives the ManifestModificationCommand message and the DASh player 52 amends the manifest accordingly.
  • Figure 4 discloses a workflow describing an example of how DASH a player, a DANE and MBMS Client work together with network entities to achieve the MooD and service continuity.
  • the DAS player is indicated with reference numeral 52
  • MBMS middleware is indicated with reference numeral 104
  • the DANE is indicated with reference numeral 11
  • the MBMS client is indicated with reference numeral 103
  • the RAN is indicated with reference numeral 106
  • the BM-SC is indicated with reference numeral 57
  • the CDN is indicated with reference numeral 56.
  • the default content delivery network is related to the content received via the BM-SC and the secondary content delivery network is related to the content received via the CDN having reference numeral 56.
  • the BM-SC 57 may perform a Service Announcement towards MBMS middleware 104 residing within a particular UE.
  • the MBMS Client 103 may receive the service announcement information which may contain:
  • BroadcastAppService describing the representations which are available in broadcast, i.e. in a default content delivery network
  • UnicastAppService describing the representations which are available in unicast, i.e. in a secondary content delivery network.
  • the BM-SC 57 may trigger the session start for the service, which enables the contents for the selected representations to be broadcasted over RAN 106. If the service is interested for the user, the MBMS Client 103 may receive the broadcasted contents and make them cached locally.
  • the DASH player 52 may request, i.e. GET, the manifest from the MBMS client 103.
  • the MBMS client 103 may include a SAND channel element in the manifest for the DANE address for setting up the SAND communication channel, and may return the updated manifest to the DASH player 52.
  • the DASH player may perform a SAND capability exchange procedure with the DAN 11 based on the DANE address as it received during the fourth step 204.
  • the DASH player 52 may sent a ManifestModificationRequest message to the DANE 11 for requesting a modification of said manifest.
  • the DANE 11 may generate the resource base URIs for the representations based on the BroadcastAppService and UnciastAppService received in step 1, i.e. having reference numeral 201.
  • the DANE 11 may then return the resource base URIs to the DASH player 52 in a Manifest Modification Response, in an eight step 208.
  • the DASH player 52 may modify, replace and/or extend the resource base URIs for the representations according to the information from Manifest Modification Response.
  • the DASH player 52 may send a SAND message for MBMS operations to the DANE 11 to check the resource availability situation for the media segments it intends to fetch.
  • the DANE 11 may inform the DASH player 52 that the broadcast URIs defined in BroadcastAppService are unavailable and the unicast URIs defined in UnicastAppService are available.
  • the DASH player 52 may fetch the media segments from the CDN 56 based on the unicast URIs for the selected representations.
  • the DANE 11 may inform the DASH player 52 that the broadcast URIs defined in BroadcastAppService are available and the unicast URIs defined in UnicastAppService are unavailable.
  • the ASH player 52 may fetch 215 the media segments from the MBMS Client 103 based on the broadcast URIs for the selected representations.
  • MBMS Client returns the segment files to the DASH player 52 which are received in step 2.
  • Figure 5 discloses a flowchart 300 illustrating an example of a method in accordance with the present disclosure.
  • the flow chart illustrates a method of enabling a Dynamic Adaptive Streaming over HTTP, DASH, player to fetch media segments from a network.
  • the method comprises the steps of:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • ManifestModificationCommand message comprises one or more representation base URI’s of any of said default representation base URI and said secondary representation base URI that are to modify a representation base URI in said manifest
  • Figure 6 discloses a flowchart 350 illustrating another example of a method in accordance with the present disclosure.
  • the flowchart 350 is directed to a method for a Dynamic Adaptive Streaming over HTTP, DASH, player to fetch media segments from a telecommunication network.
  • the method comprises the steps of:
  • said manifest comprises a representation base Uniform Resource Identifier, URI, for indicating a location to said DASH player for fetching said media segments;
  • a ManifestModificationCommand message comprising one or more representation base URI’s of any of:
  • a computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. Any reference signs in the claims should not be construed as limiting the scope thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé de lecteur d'activation d'une diffusion en continu adaptative dynamique sur HTTP, DASH, pour extraire des segments multimédia d'un réseau, ledit procédé comprenant les étapes consistant à recevoir, par un intergiciel d'élément de réseau sensible à DASH, DANE, à partir dudit réseau, un manifeste, ledit manifeste comprenant un identifiant de ressource uniforme, URI, de base de représentation, pour indiquer un emplacement audit lecteur DASH pour extraire lesdits segments multimédia, un URI de base de représentation par défaut qui est disponible dans un mode par défaut pour extraire lesdits segments multimédia à partir d'un réseau de distribution de contenu, CDN, par défaut, un URI de base de représentation secondaire qui est disponible dans un mode secondaire pour extraire lesdits segments multimédia d'un CDN secondaire, transmettre, par ledit intergiciel DANE, ledit manifeste audit lecteur DASH, transmettre, par ledit intergiciel DANE, audit lecteur DASH, un message de commande de modification, ledit message de modification de manifeste comprenant une ou plusieurs URI de base de représentation de l'un quelconque desdits URI de base de représentation par défaut et dudit URI de base de représentation secondaire qui sont destinés à modifier une URI de base de représentation dans ledit manifeste.
PCT/CN2018/075303 2018-02-05 2018-02-05 Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau WO2019148498A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US15/757,586 US10601886B2 (en) 2018-02-05 2018-02-05 Method, a user equipment and a computer program product for enabling a dynamic adaptive streaming over HTTP, DASH, player to fetch media segments from a network
EP18903650.2A EP3750303B1 (fr) 2018-02-05 2018-02-05 Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau
PCT/CN2018/075303 WO2019148498A1 (fr) 2018-02-05 2018-02-05 Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau
US16/804,857 US11038941B2 (en) 2018-02-05 2020-02-28 Enabling a dynamic adaptive streaming over HTTP player to fetch media segments from a network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/075303 WO2019148498A1 (fr) 2018-02-05 2018-02-05 Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/757,586 A-371-Of-International US10601886B2 (en) 2018-02-05 2018-02-05 Method, a user equipment and a computer program product for enabling a dynamic adaptive streaming over HTTP, DASH, player to fetch media segments from a network
US16/804,857 Continuation US11038941B2 (en) 2018-02-05 2020-02-28 Enabling a dynamic adaptive streaming over HTTP player to fetch media segments from a network

Publications (1)

Publication Number Publication Date
WO2019148498A1 true WO2019148498A1 (fr) 2019-08-08

Family

ID=67479508

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075303 WO2019148498A1 (fr) 2018-02-05 2018-02-05 Procédé, équipement utilisateur et produit programme d'ordinateur d'activation d'un lecteur de diffusion en continu adaptative dynamique sur http, dash, pour extraire des segments multimédia d'un réseau

Country Status (3)

Country Link
US (2) US10601886B2 (fr)
EP (1) EP3750303B1 (fr)
WO (1) WO2019148498A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021032706A1 (fr) * 2019-08-19 2021-02-25 Koninklijke Kpn N.V. Système d'aide à la diffusion en continu et procédé mis en œuvre par ordinateur

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11128896B2 (en) * 2018-08-27 2021-09-21 Comcast Cable Communications, Llc Secondary content delivery
US10833972B2 (en) * 2018-11-30 2020-11-10 Dispersive Networks, Inc. Automatically selecting an optimized communication channel for communications with a deflect in an overlay network

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101860720A (zh) * 2009-04-10 2010-10-13 中兴通讯股份有限公司 内容定位方法及内容分发网络节点
CN102598691A (zh) * 2009-11-03 2012-07-18 瑞典爱立信有限公司 利用数据分段的可选广播传送的流传输
CN104661052A (zh) * 2009-11-03 2015-05-27 瑞典爱立信有限公司 利用数据分段的可选广播传送的流传输
CN104980416A (zh) * 2014-07-31 2015-10-14 腾讯科技（深圳）有限公司 一种内容分布网络中的数据访问方法、装置和系统
US20170019445A1 (en) * 2015-07-16 2017-01-19 Arris Enterprises, Inc. Systems and methods for providing dlna streaming to client devices

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8849950B2 (en) * 2011-04-07 2014-09-30 Qualcomm Incorporated Network streaming of video data using byte range requests
CN104040992B (zh) * 2011-11-14 2018-06-29 瑞典爱立信有限公司 移动网络中具有改善的效率的媒体流
BR122015005210A2 (pt) * 2012-06-28 2019-08-20 Ericsson Ab Método e sistema para inserção de anúncio em entrega de mídia ao vivo over the top
JP6072276B2 (ja) * 2012-11-13 2017-02-01 テレフオンアクチーボラゲット エルエム エリクソン（パブル） マルチメディアデータの処理
US9998514B2 (en) * 2012-12-12 2018-06-12 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for handling files in association with media content delivery
WO2014113183A1 (fr) * 2013-01-17 2014-07-24 Intel IP Corporation Authentification d'url de contenu pour un protocole dash
JP2016522621A (ja) * 2013-07-15 2016-07-28 ホアウェイ・テクノロジーズ・カンパニー・リミテッド ダイナミックアダプティブストリーミング・オーバー・ハイパーテキストトランスファープロトコルにおけるリモート要素のジャストインタイムデリファレンス
US20160330500A1 (en) * 2014-01-10 2016-11-10 Thomson Licensing Method for obtaining network information by a client terminal configured for receiving a multimedia content divided into segments
EP2894870A1 (fr) * 2014-01-10 2015-07-15 Thomson Licensing Procédé servant à télécharger, au niveau d'un terminal client, une séquence de segments à venir d'un contenu multimédia et terminal correspondant
US11228427B2 (en) * 2014-02-11 2022-01-18 Ericsson Ab System and method for securing content keys delivered in manifest files
US9866608B2 (en) * 2014-03-24 2018-01-09 Qualcomm Incorporated Processing continuous multi-period content
US9973345B2 (en) * 2014-09-10 2018-05-15 Qualcomm Incorporated Calculating and signaling segment availability times for segments of media data
US10193994B2 (en) * 2015-06-18 2019-01-29 Qualcomm Incorporated Signaling cached segments for broadcast
WO2017063189A1 (fr) * 2015-10-16 2017-04-20 Qualcomm Incorporated Signalisation d'échéance de diffusion de données multimédias en continu
EP3179688A1 (fr) * 2015-12-11 2017-06-14 Koninklijke KPN N.V. Mise à jour d'élément d'un fichier manifest sur la base de correctifs
US11283847B2 (en) * 2015-12-18 2022-03-22 Telefonaktiebolaget Lm Ericsson (Publ) Handling of content delivery in a client node
WO2017135181A1 (fr) * 2016-02-01 2017-08-10 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ Client, serveur, procédé de réception et procédé d'émission
WO2017134110A1 (fr) * 2016-02-02 2017-08-10 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Gestion de la section de scène et de la région d'intérêt en diffusion vidéo continue
US10313408B2 (en) * 2016-06-22 2019-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Client-assisted time-shift live media and advertisement content play for learned ABR video white spot coverage in a streaming network
EP3510744B1 (fr) * 2016-09-09 2022-05-04 Vid Scale, Inc. Procédés et appareil de réduction de la latence pour une diffusion continue adaptative de fenêtre d'affichage à 360 degrés
WO2018114814A1 (fr) * 2016-12-20 2018-06-28 Koninklijke Kpn N.V. Traitement de synchronisation entre des flux
US20190342356A1 (en) * 2017-01-02 2019-11-07 Koninklijke Kpn N.V. Selectively updating a dynamic manifest file
US11290755B2 (en) * 2017-01-10 2022-03-29 Qualcomm Incorporated Signaling data for prefetching support for streaming media data

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101860720A (zh) * 2009-04-10 2010-10-13 中兴通讯股份有限公司 内容定位方法及内容分发网络节点
CN102598691A (zh) * 2009-11-03 2012-07-18 瑞典爱立信有限公司 利用数据分段的可选广播传送的流传输
CN104661052A (zh) * 2009-11-03 2015-05-27 瑞典爱立信有限公司 利用数据分段的可选广播传送的流传输
CN104980416A (zh) * 2014-07-31 2015-10-14 腾讯科技（深圳）有限公司 一种内容分布网络中的数据访问方法、装置和系统
US20170019445A1 (en) * 2015-07-16 2017-01-19 Arris Enterprises, Inc. Systems and methods for providing dlna streaming to client devices

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3750303A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021032706A1 (fr) * 2019-08-19 2021-02-25 Koninklijke Kpn N.V. Système d'aide à la diffusion en continu et procédé mis en œuvre par ordinateur
US20230224548A1 (en) * 2019-08-19 2023-07-13 Koninklijke Kpn N.V. Streaming Assistance System and Computer-Implemented Method

Also Published As

Publication number Publication date
US10601886B2 (en) 2020-03-24
US20200274907A1 (en) 2020-08-27
EP3750303A1 (fr) 2020-12-16
US11038941B2 (en) 2021-06-15
EP3750303A4 (fr) 2021-08-11
EP3750303B1 (fr) 2024-04-03
US20190379719A1 (en) 2019-12-12

Similar Documents

Publication Publication Date Title
KR101956121B1 (ko) 스트리밍 컨텐츠 제공 장치 및 방법
US9986003B2 (en) Mediating content delivery via one or more services
US8230044B2 (en) Media channel management
US11038941B2 (en) Enabling a dynamic adaptive streaming over HTTP player to fetch media segments from a network
CN102598691B (zh) 利用数据分段的可选广播传送的流传输
CN105284093A (zh) 针对网络上的媒体流式传输支持传输分集和时移缓存器
JP2007195188A (ja) マルチメディア・メッセージ方法およびシステム
US11051078B2 (en) Video distribution method and device
US11165841B2 (en) Method for transmitting content to mobile user devices
WO2015171029A1 (fr) Procédé, appareil et dispositif de communication pour traiter un contenu à diffusion générale ou à diffusion groupée
US11831702B2 (en) Method for broadcasting DASH/HLS hybrid multimedia streams
KR20170140114A (ko) MBMS(Multimedia Broadcast/Multicast Service) 수신기 및 그의 데이터 수신 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18903650

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018903650

Country of ref document: EP

Effective date: 20200907