WO2012079223A1 - Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus - Google Patents

Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus Download PDF

Info

Publication number
WO2012079223A1
WO2012079223A1 PCT/CN2010/079757 CN2010079757W WO2012079223A1 WO 2012079223 A1 WO2012079223 A1 WO 2012079223A1 CN 2010079757 W CN2010079757 W CN 2010079757W WO 2012079223 A1 WO2012079223 A1 WO 2012079223A1
Authority
WO
WIPO (PCT)
Prior art keywords
streaming media
request
media
uri
description file
Prior art date
Application number
PCT/CN2010/079757
Other languages
English (en)
Chinese (zh)
Inventor
陈骞
高云超
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201080006601.3A priority Critical patent/CN102282825B/zh
Priority to PCT/CN2010/079757 priority patent/WO2012079223A1/fr
Publication of WO2012079223A1 publication Critical patent/WO2012079223A1/fr

Links

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/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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and device for streaming media request address mapping in a content delivery network, and a cache node.
  • CDN Content Delivery Network
  • MDN Media Delivery Network
  • CDN In the traditional IP network, the user requests directly to the original server based on the network address, and the CDN service provides a service layer, supplements and extends the Internet network, and promotes frequently accessed content to the user as much as possible, providing processing-based content.
  • a new capability for traffic forwarding, directing routing to the best server, CDN can be used as a solution for efficient streaming.
  • the core of the CDN is to use caching technology to cache hot content, including web pages, pictures, audio and video, etc., to an edge server that is closer to the user. This can reduce the load on the central server and reduce the bandwidth consumption of the backbone network. At the same time accelerate the response to users and enhance the user experience.
  • the streaming media protocols mainly include: HTTP (Hyper Text Transfer Protocol), RTSP (Real Time Streaming Protocol), and Real Time Message Protocol (RTMP). .
  • HTTP Hyper Text Transfer Protocol
  • RTSP Real Time Streaming Protocol
  • RTMP Real Time Message Protocol
  • RTSP/RTMP/HTTP passes URI (Uniform Resource) when streaming media on demand Identifier, Uniform Resource Identifier, indicates that the playback object is the video content.
  • URI Uniform Resource
  • the same video content may exist in many different formats, such as mp4, flv, etc. The difference is mainly the format of the media data package.
  • it is necessary to save the same amount, which wastes the storage space of the original server and the cache node that caches the playback object according to the URI.
  • the RTSP/RTMP/HTTP protocol supports requests for part of the video content, such as requesting a segment of the entire video content, or requesting to play from the nth minute of the video, but the requests supported by different protocols are in standard form, and Non-standard form. Cache nodes can be identified and cached when requesting a range of standard forms, but requests for non-standard forms are not semantically identified. Usually the entire URI is used as an identifier to cache objects, which wastes cache space.
  • RTP Real-time Transport Protocol
  • the entire RTP package is usually cached.
  • Embodiments of the present invention provide a method, a device, and a cache node for streaming media request address mapping in a content delivery network, so as to improve utilization of a cache space in a CDN.
  • the technical solution adopted by the embodiment of the present invention is:
  • a method for streaming address request address mapping in a content delivery network comprising:
  • Extracting a request parameter in the URI where the request parameter includes: a requested streaming media path, a streaming media name, and a request range information;
  • the media description file is a file describing fragmentation information of an audio and video object
  • a device for streaming address request address mapping in a content delivery network comprising:
  • a receiving unit configured to receive a streaming media request of the user, where the streaming media request carries the streaming media
  • An extracting unit configured to extract a request parameter in the URI, where the request parameter includes: a requested streaming media path, a streaming media name, and a request range information;
  • a file obtaining unit configured to acquire a media description file corresponding to the name of the streaming media, where the media description file is a file describing fragmentation information of the audio and video object;
  • a file parsing unit configured to parse the media description file to obtain fragmentation information corresponding to the request scope information
  • a converting unit configured to convert, according to the fragmentation information, a URI of the streaming media to a URI corresponding to a fragment of the streaming media.
  • a cache node in a content delivery network comprising: a fluidization control module, a cache module, and an address mapping module;
  • the streaming control module is configured to receive a streaming media request of the user, and perform fragmentation on the streaming media obtained by the cache node, and save the fragment of the streaming media to the cache module;
  • the address mapping module is configured to convert a URI of the streaming media carried in the streaming media to a URI corresponding to the fragment of the streaming media;
  • the streaming control module is further configured to: obtain a fragment of the streaming media from the cache module according to a URI of the fragment of the streaming media, and send the fragment of the streaming media to the user.
  • the method and device for streaming media request address mapping in a content delivery network and a cache node, in order to improve cache space utilization, perform preprocessing operations on the streaming media files injected into the CDN network and perform fragmentation according to a unified format.
  • the mode is saved on the cache node of the CDN network, after receiving the streaming media request of the user, the URI in the streaming request of the user is converted into a URI corresponding to the fragment of the streaming media, that is, different protocols, different formats, Different ranges of requests are mapped to fragmentation requests to the internal unified format, so that corresponding streaming media fragments can be obtained from the cache nodes according to the fragmentation request.
  • FIG. 1 is a flowchart of a method for streaming address request address mapping in a CDN according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of an apparatus for streaming media request address mapping in a CDN according to an embodiment of the present invention
  • FIG. 3 is another schematic structural diagram of an apparatus for streaming media request address mapping in a CDN according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a cache node in a CDN according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of an application of a cache node in a CDN network according to an embodiment of the present invention.
  • the cache object is usually managed by using the object's URI or the value obtained after a certain operation on the URI as an identifier, that is, receiving the URI of the user request object, directly or indirectly in the cache.
  • the matching is performed in the management unit. If the matching succeeds, the object is already cached. If the cached object is valid, the object can be directly obtained through the cache to respond to the user request. Otherwise, the object needs to be obtained from the source server, and the object is cached. .
  • the audio and video injected into the CDN system can be pre-processed in advance, stored in a unified format on the source server of the CDN system, and a media description file is generated to describe the audio and video.
  • the object is fragmented by time and/or byte, thereby increasing the utilization of the CDN cache space.
  • the corresponding one or more fragments are packaged into different formats according to different protocols, different formats, and the scope of the request. Respond to the user with different protocols.
  • the cache node performs semantic analysis on the request from the user, and maps requests of different protocols, different formats, and different ranges into fragments of the internal unified format. request.
  • FIG. 1 it is a flowchart of a method for streaming address request address mapping in a CDN according to an embodiment of the present invention, which includes the following basic steps:
  • Step 101 Receive a streaming media request of the user, where the streaming media request carries a URI of the streaming media.
  • a matching rule corresponding to different request formats may be established in advance, so that when the request parameter in the URI is extracted, the URI of the streaming media may be extracted by a regular expression corresponding to the matching rule.
  • Request parameters may be established in advance, so that when the request parameter in the URI is extracted, the URI of the streaming media may be extracted by a regular expression corresponding to the matching rule.
  • the regular expression refers to a single string used to describe or match a series of strings that conform to a syntax rule.
  • a regular expression is a formula that uses a pattern to match a type of string.
  • the user's streaming request can be semantically parsed using a regular expression, and relevant parameters are extracted.
  • the matching rules of regular expressions can be pre-configured. Multiple matching rules can be configured for different streaming request formats. For example, you can pre-configure the matching rules shown in Table 1 below.
  • Each matching rule corresponds to one row of the table, and each row is divided into two parts: input and output, and the input part is used to output related parameters extracted from the URI of the streaming media according to the corresponding regular expression. Part is the converted format.
  • the time/byte indicates a streaming media request matching the row, and if the range information is carried, is the time unit or the byte unit;
  • the FULL PATH indicates the format of the full path outputted by the URI of the streaming media; the MDF name indicates the name of the corresponding media description file.
  • matching rules corresponding to each request format can be separately established, so that corresponding request parameters can be correctly extracted from the URIs of the respective requests.
  • the request parameters mainly include: a requested streaming media path, a streaming media name, and a request range information.
  • the request parameter may further include any one or more of the following: bit rate, start byte and end byte, start time and end time, extension, and the like.
  • the embodiment of the present invention does not limit the specific implementation manner of extracting the request parameter in the URI, and may also adopt other methods, such as keyword matching.
  • Step 103 Obtain a media description file corresponding to the name of the streaming media, where the media description file is a file describing fragmentation information of the audio and video object, for example, may describe the audio and video object by time and/or byte. Fragmentation information.
  • the process of generating a media description file by performing a pre-processing operation on an audio-video object is not limited.
  • the pre-generated media description file may be stored in the cache node of the CDN, or may be stored in the source server of the CDN.
  • the streaming media name can be extracted from the URI requested by the user, and the name of the corresponding media description file, that is, the MDF name in Table 1 above, can be generated according to the name.
  • the file name is searched on the cache node according to the file name sample.xml. If the corresponding media description file is found, the media description file is directly obtained from the cache node; Find the corresponding media description file, then you can find it from the source server through the proxy. The location on the source server can be customized.
  • Step 104 Parse the media description file to obtain fragmentation information corresponding to the request scope information.
  • the media description file is a file describing fragmentation information of an audio and video object, according to The request parameter extracted in step 102, parsing the media description file, can obtain the fragmentation information corresponding to the range of the user request.
  • Step 105 Convert the URI of the streaming media to a URL corresponding to the fragment of the streaming media according to the fragmentation information.
  • the streaming media obtained by the cache node is fragmented according to the fragmentation information in the media description file, and the fragment of the streaming media is saved into the cache node.
  • the subsequent cache node receives the streaming media request for the same object, regardless of which streaming media protocol such as HTTP/RTSP/RTMP is used for the request, and regardless of the media format requested by the user, such as flv/mp4,
  • the URI in the request is converted into a fragment URI, and then the corresponding streaming media fragment is obtained from the cache node according to the fragment URI.
  • the media data is saved in the cache node by the same format of the fragment, but only when responding to the user request, the corresponding fragments are encapsulated according to different protocols, different formats, and the scope of the request. Different formats respond to users with different protocols, which greatly increases cache space utilization.
  • the cache node should also have the media format conversion capability in order to meet the user's requirements for different media formats.
  • the process of generating a media description file by performing a pre-processing operation on an audio-video object is not limited.
  • rates can also be described in the media description file and then selected accordingly based on the user's actual request rate.
  • the fragmentation information is listed in the media description file sample.xml, which mainly includes: media metadata fragment sample_1636000_moovfrag, sample_1636000_mfra, and 6 seconds of media data fragmentation, where the fragmentation is performed in units of time. Assume that the time for each shard is 2 seconds.
  • the method for streaming address request address mapping in the CDN can be applied to a streaming media request initiated by using an HTTP, an RTSP, or an RTMP protocol.
  • the HTTP protocol is the most important protocol used by Web applications.
  • the HTTP protocol is also used to transport streaming media. It can be used to download and play audio and video content.
  • the HTTP protocol supports requests for partial video content, such as requesting a segment of the entire video content, or requesting to play from the nth minute of the video.
  • HTTP also supports requesting in bytes. There are two ways, one is standard, and the range of bytes played by the Range Header is carried in the GET message. Standard, its form may be like:
  • the RTSP protocol is an application layer protocol that controls the transmission of streaming media data over an IP network, enabling control over streaming media playback.
  • RTSP provides remote control of the streaming media server, and it does not transmit streaming media data itself.
  • Streaming media data is usually transmitted using RTP (Real-time Transport Protocol).
  • RTP Real-time Transport Protocol
  • the RTSP protocol indicates the time range for playback by carrying a Range Header in the PLAY command.
  • RTMP is a TCP/IP protocol designed to efficiently transmit video and audio data. It implements real-time video and audio transmission by establishing a binary TCP connection or connecting to an HTTP tunnel.
  • the RTMP protocol indicates the time range for playing by carrying the Start and Duration fields in the PLAY command.
  • Example 1 A streaming media request is sent by the HTTP protocol, and the time range information is carried in the non-standard format in the streaming request.
  • the URIs in the streaming request input by the user are matched by the above regular expression, and the extracted parameters are as follows:
  • the output is:
  • the matching rule is read in the system initialization.
  • the matching rule is used to match, and the matching parameter is extracted.
  • the media description file needs to be obtained. If the CDN cache node is not local, it needs to be obtained by the HTTP protocol to the source server in the CDN system. The location of the specific sample.xml on the source server can be agreed upon by itself.
  • the media description file is parsed according to the range of 2 ⁇ 4 seconds requested by the user, and the corresponding second fragment is known, as follows:
  • the sample_1636000 object requested by the user is 2 to 4 seconds, and actually corresponds to one video fragment sample_1636000_00001 and one audio fragment sample_a_00001. If the media description file does not give a shard file name, you can also generate a corresponding shard file name by using the configured FULL PATH.
  • the metadata is some control information of the streaming media, and this part of the data also needs to be acquired at the same time. If there is a voxel: according to the information, it is also described in the media description file, such as sample_1636000_moovfrag and sample_1636000_mfra in sample.xml.
  • Example 2 The user's streaming request is sent through the RTSP/RTMP protocol, and the time range information is carried in the standard format in the streaming request.
  • the RTSP protocol indicates the time range for playing by carrying the Range Header in the PLAY command;
  • the RTMP protocol indicates the time range of playing by carrying the Start and Duration fields in the PLAY command.
  • the Range Header of the RTSP supports several formats, such as NPT (Normal Play Time), which is the playback time point relative to the video start position, SMPTE (time stamp), etc., which is used to describe the time range for requesting playback.
  • NPT Normal Play Time
  • SMPTE time stamp
  • the regular expression that can be set is: (.*V)([a-zA-Z]+)(?:_( ⁇ d+)? ⁇ .(flvlmp4)).
  • the regular expression uses the "(), parentheses to extract the subexpressions on the match, that is, the parameters, so it is necessary to keep the total number of the same as the total number of parameters in the matching rule.
  • the URIs in the streaming request input by the user are matched by the above regular expression, and the extracted parameters are as follows:
  • the output is:
  • the matching rule is read in the system initialization.
  • the matching rule is used to match, and the matching parameter is extracted.
  • the media description file needs to be obtained. If the CDN cache node is not local, it needs to be obtained by the HTTP protocol to the source server in the CDN system. The location of the specific sample.xml on the source server can be agreed upon by itself.
  • the media description file may be parsed according to the range of the user request for 10 ⁇ 15 seconds, the corresponding fragment is found, and then the received RTSP request is converted into a fragmentation request of the HTTP protocol, and the specific process is similar to that in the above example 1. , will not be described in detail here.
  • the range of 10-15 seconds requested by the user is not obtained by using a regular expression, but is obtained by directly parsing the Range Header in the RTSP request.
  • the streaming media request is initiated by using the HTTP protocol and the RTSP protocol, and the time-based range information is carried in the streaming media request is described, and the processing of the byte-based range information is performed.
  • the media description file needs to include the fragmentation information described in bytes. When parsing the media description file, it needs to parse according to the user request byte range to find the corresponding fragment. This is further illustrated in detail below.
  • Example 3 A user's streaming request is sent over the HTTP protocol, and byte range information is carried in the non-standard format in the streaming request.
  • the regular expression uses the "(), parentheses to extract the subexpressions on the match, that is, the parameters, so the total number of parameters must be the same as the total number of parameters in the matching rule.
  • the URIs in the streaming request input by the user are matched by the above regular expression, and the extracted parameters are as follows:
  • the output is:
  • the media description file can be known, and the byte range of the request corresponds to three fragments of 3, 4, and 5, so that the received HTTP request can be converted into a fragment of the HTTP protocol.
  • the request is as follows:
  • the corresponding fragment file name can be generated by the FULL PATH of the configuration file. For example, for this example, it can be set to $PATH/$NAME_%5d, where path, The name parameter is known, and %5d means that the fragment number is represented by a 5-digit integer.
  • %5d means that the fragment number is represented by a 5-digit integer.
  • the HTTP protocol also supports the byte format request of the standard format, that is, by carrying the Range Header field in the GET message to indicate the byte range of the request, the specific processing is similar to the above, except that the value of the requested byte range is not Obtained by the regular expression, but can be obtained directly from the Range Header of the resolution protocol, and will not be described here.
  • the method for streaming address request address mapping in the content delivery network is for the case where the cache node performs unified management on the streaming media requested by the user in units of fragments, and requests the streaming media through the user.
  • Converting the URI in the stream converting it to the URI of the slice corresponding to the streaming media, so that the media data is saved in the cache node by the same format of the slice, but only in response to the user request, according to Different protocols, different formats, and the scope of the request encapsulate the corresponding fragments into different formats and respond to the user with different protocols, which greatly improves the cache space utilization.
  • a cache node does not perform semantic recognition for a non-standard form of range request, and the object is usually cached by using the entire URI as an identifier, for example:
  • the cache node In the prior art, the cache node The objects of the two requests are saved or not saved. After the method of streaming media request address mapping in the content delivery network of the embodiment of the present invention is applied, the cache node can save only the content of the first request.
  • the cache node for the standard form of the range request such as the scope request of the RTSP protocol
  • its data stream is usually transmitted by RTP package
  • the prior art cache is usually to save the entire RTP package;
  • the range request will result in a lot of fragmentation.
  • the prior art often uses the processing in dealing with these problems, that is, the request for the scope of these standard forms, or not to save at all, or to save the entire complete content.
  • the cache node can save only the content corresponding to the user request range.
  • the embodiment of the present invention further provides a device for mapping a streaming media request address in a content delivery network, as shown in FIG. 2, which is a schematic structural diagram of the device.
  • the apparatus 200 includes:
  • the receiving unit 201 is configured to receive a streaming media request of the user, where the streaming media request carries a URI of the streaming media;
  • the extracting unit 202 is configured to extract a request parameter in the URI, where the request parameter includes: a requested streaming media path, a streaming media name, and a request range information;
  • a file obtaining unit 203 configured to acquire a media description file corresponding to the name of the streaming media, where the media description file is a file describing fragmentation information of the audio and video object;
  • the file parsing unit 204 is configured to parse the media description file to obtain fragmentation information corresponding to the request scope information;
  • the converting unit 205 is configured to convert the URI of the streaming media into a URI corresponding to the fragment of the streaming media according to the fragmentation information.
  • matching rules corresponding to different request formats may be pre-established, so that when the request parameters in the URI are extracted, the streaming media may be extracted by a regular expression corresponding to the matching rule.
  • Request parameters in the URI may be pre-established, so that when the request parameters in the URI are extracted, the streaming media may be extracted by a regular expression corresponding to the matching rule.
  • the apparatus may further include: a rule establishing unit (not shown) for establishing matching rules corresponding to different request formats.
  • the extracting unit 202 may specifically extract the request parameter in the URI of the streaming media by using a regular expression corresponding to the matching rule.
  • the embodiment of the present invention does not limit the specific implementation manner in which the extracting unit 202 extracts the request parameter in the URI of the streaming media, and may also be implemented in other manners, for example, by keyword matching or the like.
  • the media description file may be pre-generated and saved in a cache node in the CDN, or may be saved on a source server in the CDN.
  • the file obtaining unit 204 may acquire the media description file from the cache node or obtain the media description file from the source server.
  • the device for mapping the streaming media request address in the content delivery network in the embodiment of the present invention converts the URI into the URI of the fragment corresponding to the streaming media by converting the URI in the streaming request of the user, so that the cache node Uniform the same format of fragmentation to save media data, but in response to user requests, according to different protocols, different formats and the scope of the request, etc., the corresponding fragments are encapsulated into different formats and responded with different protocols. To the user, this greatly increases the cache space utilization.
  • FIG. 3 it is another schematic structural diagram of an apparatus for streaming media request address mapping in a content delivery network according to an embodiment of the present invention.
  • the apparatus 300 further includes: a saving unit 206 and a fragmenting unit 207. among them:
  • the fragmentation unit 207 is configured to slice the streaming media obtained by the cache node according to the fragmentation information in the media description file.
  • the saving unit 206 is configured to save the fragment of the streaming media processed by the fragmentation unit 207 into the cache node.
  • the saving unit 206 and the fragmentation unit 207 can be independently set in the cache node as a functional module of the cache node.
  • the embodiment of the present invention further provides a cache node in the CDN, as shown in FIG. 4, which is a schematic structural diagram of the cache node.
  • the cache node includes: a fluidization control module 401, a cache module 402, and an address mapping module 403.
  • the streaming control module 401 is configured to receive a streaming media request of the user, and perform fragmentation on the streaming media obtained by the cached node, and save the fragment of the streaming media to the cache module 402.
  • the address mapping module 403 is configured to convert a URI of the streaming media carried in the streaming media to a URI corresponding to the fragment of the streaming media, so that the streaming control module according to the streaming media
  • the URI of the slice acquires the slice of the streaming media from the cache module.
  • the fluidization control module 401 includes: a receiving unit, a fragmentation unit, a storage unit, and a sending unit. among them:
  • the receiving unit is configured to receive a streaming media request of the user, where the streaming media request carries a URI of the streaming media;
  • the fragmentation unit is configured to: use the media description file to obtain the streaming media obtained by the cache node. Fragmentation information in the slice;
  • the saving unit is configured to save the fragment of the streaming media output by the fragmentation unit to the cache module;
  • the sending unit is configured to obtain a fragment of the streaming media from the cache module according to a URI of the fragment of the streaming media, and send the fragment of the streaming media to the user.
  • the address mapping module 403 includes: an extracting unit, a file obtaining unit, a file parsing unit, and a converting unit. For the specific structure, refer to the apparatus shown in FIG. 3.
  • the address mapping module 403 may further include: a rule establishing unit, configured to establish a matching rule corresponding to different request formats.
  • the extracting unit is specifically configured to extract a request parameter in the URI of the streaming media by using a regular expression corresponding to the matching rule.
  • the media description file may be pre-generated and saved on the cache module 402, or may be saved on the source server in the CDN.
  • the file obtaining unit may acquire the media description file from the cache module 402 or obtain the media description file from the source server.
  • the cache node in the embodiment of the present invention converts the URI in the streaming media request of the user into a URI corresponding to the fragment of the streaming media, so that the shard of the same format is unified in the cache node.
  • the way to save the media data is to respond to the user request, according to different protocols, different formats and the scope of the request, etc., the corresponding fragments are encapsulated into different formats and responded to the user with different protocols, which greatly improves the user's request. Cache space utilization.
  • the cache node further includes: a proxy module 404, configured to acquire, when the media description file is not in the cache module 402, from the source server 500 in the content delivery network. a media description file, and the media description file is transmitted to the fluidization control module 401; and is further configured to: when the streaming media file requested by the user is not in the cache module 402, from the content delivery network The streaming media file is obtained by the source server 500, and the streaming media file is transmitted to the streaming control module 401.
  • a proxy module 404 configured to acquire, when the media description file is not in the cache module 402, from the source server 500 in the content delivery network.
  • a media description file, and the media description file is transmitted to the fluidization control module 401; and is further configured to: when the streaming media file requested by the user is not in the cache module 402, from the content delivery network
  • the streaming media file is obtained by the source server 500, and the streaming media file is transmitted to the streaming control module 401.
  • Embodiments of the invention may be utilized in numerous general or special purpose computing system environments or configurations, and may be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

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

Abstract

La présente invention concerne un procédé, un système et un nœud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus ou "CDN" (Content Delivery Network). Ce procédé consiste: à recevoir en provenance d'un utilisateur une demande de flux multimédia comportant l'identifiant uniforme de ressource ou "URI" (Uniform Resource Identifier) du flux multimédia; à extraire dans l'URI les paramètres de demande comportant le chemin de flux multimédia de la demande, le nom de flux multimédia, et l'information de longueur de la demande; à obtenir le fichier de description multimédia correspondant au nom de flux multimédia, lequel fichier de description multimédia est le fichier décrivant l'information de fragment des objets audio et vidéo; à analyser le fichier de description multimédia de façon à obtenir l'information de fragment correspondant à l'information de longueur de la demande; et à convertir l'URI du flux multimédia en URI correspondant au fragment du flux multimédia conformément à l'information de fragment. L'utilisation des modes de réalisation de l'invention permet d'améliorer le taux d'utilisation de l'espace tampon dans un réseau CDN.
PCT/CN2010/079757 2010-12-14 2010-12-14 Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus WO2012079223A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201080006601.3A CN102282825B (zh) 2010-12-14 2010-12-14 内容传送网络中流媒体请求地址映射的方法及装置、缓存节点
PCT/CN2010/079757 WO2012079223A1 (fr) 2010-12-14 2010-12-14 Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/079757 WO2012079223A1 (fr) 2010-12-14 2010-12-14 Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus

Publications (1)

Publication Number Publication Date
WO2012079223A1 true WO2012079223A1 (fr) 2012-06-21

Family

ID=45106833

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/079757 WO2012079223A1 (fr) 2010-12-14 2010-12-14 Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus

Country Status (2)

Country Link
CN (1) CN102282825B (fr)
WO (1) WO2012079223A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916678A (zh) * 2012-12-31 2014-07-09 中国移动通信集团广东有限公司 多媒体数据转码方法、转码设备及多媒体数据播放系统
CN105141660A (zh) * 2015-07-24 2015-12-09 网宿科技股份有限公司 一种流媒体管理方法及系统
CN114925249A (zh) * 2022-05-20 2022-08-19 东南大学 一种面向自适应流媒体的视频传输指纹快速生成方法
CN115277651A (zh) * 2022-06-22 2022-11-01 肯特智能技术（深圳）股份有限公司 基于xml文件的配置式流媒体软件方法及系统

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102307195B (zh) * 2011-08-23 2018-10-12 南京中兴新软件有限责任公司 基于流媒体的频道轮播方法及流媒体服务器
CN103457907A (zh) * 2012-05-28 2013-12-18 中国移动通信集团公司 一种多媒体内容分发方法、设备及系统
CN103475679B (zh) * 2012-06-06 2017-09-26 百度在线网络技术（北京）有限公司 对分片请求进行定长对齐的缓存方法、系统及装置
CN103826137B (zh) * 2012-11-19 2018-02-16 中国电信股份有限公司 视频访问方法和系统、cdn服务器的视频代理
WO2015058334A1 (fr) * 2013-10-21 2015-04-30 华为技术有限公司 Procédé de gestion de ressource multimédia en continu, serveur et client
CN103685302A (zh) * 2013-12-24 2014-03-26 乐视网信息技术（北京）股份有限公司 连接内容传送网络的处理方法与系统
CN103747065B (zh) * 2013-12-27 2017-02-08 河海大学 客户端http检索全索引容器格式媒体资源时间片段的方法
CN103956175B (zh) * 2014-04-18 2017-04-26 华为技术有限公司 一种多媒体文件的播放方法及播放设备
CN105376657A (zh) * 2014-08-15 2016-03-02 中国电信股份有限公司 媒体内容提供方法、播放方法和装置以及服务系统
CN104202616A (zh) * 2014-09-11 2014-12-10 北京阅联信息技术有限公司 一种基于裸流直播方法、回看方法及其系统
CN104506493B (zh) * 2014-12-04 2018-02-27 武汉市烽视威科技有限公司 一种实现hls内容回源和缓存的方法
CN104506637B (zh) * 2014-12-29 2018-03-23 国家电网公司 解决网络拥挤的缓存方法、系统及url转发服务器
CN105872587A (zh) * 2015-11-25 2016-08-17 乐视云计算有限公司 视频请求的处理方法及装置
CN105898387A (zh) * 2016-03-30 2016-08-24 乐视控股（北京）有限公司 一种流媒体数据发送方法及装置
CN105812833A (zh) * 2016-04-07 2016-07-27 网宿科技股份有限公司 文件处理方法和装置
CN105978936A (zh) * 2016-04-25 2016-09-28 乐视控股（北京）有限公司 Cdn服务器及其缓存数据的方法
CN109788014A (zh) * 2017-11-14 2019-05-21 阿里巴巴集团控股有限公司 一种消息处理、物联网系统的消息处理方法和装置
CN108234639A (zh) * 2017-12-29 2018-06-29 北京奇虎科技有限公司 一种基于内容分发网络cdn的数据访问方法和装置
CN108322772A (zh) * 2018-01-30 2018-07-24 北京奇艺世纪科技有限公司 一种视频文件处理方法、装置及电子设备
CN108540816B (zh) * 2018-03-28 2020-03-17 腾讯科技（深圳）有限公司 一种直播视频获取方法、装置及存储介质
CN113254412A (zh) * 2020-02-12 2021-08-13 彩虹无线（北京）新技术有限公司 一种数据转换方法和装置
CN115221453B (zh) * 2022-09-20 2023-03-10 太平金融科技服务(上海)有限公司深圳分公司 媒体资源管理方法、装置、服务器、介质
CN116610823B (zh) * 2023-04-28 2024-05-07 江苏传智播客教育科技股份有限公司 一种统一访问多媒体资源的方法和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242422A (zh) * 2007-02-06 2008-08-13 中国电信股份有限公司 适应多业务融合的内容分发网络系统和方法
CN101534204A (zh) * 2008-03-10 2009-09-16 中国网通集团宽带业务应用国家工程实验室有限公司 流媒体信息分发系统和方法及客户端
CN101552800A (zh) * 2008-04-01 2009-10-07 华为技术有限公司 提供媒体内容的方法、装置和系统
CN101677325A (zh) * 2008-09-16 2010-03-24 华为技术有限公司 发布媒体描述信息和获取媒体的方法、装置、系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242422A (zh) * 2007-02-06 2008-08-13 中国电信股份有限公司 适应多业务融合的内容分发网络系统和方法
CN101534204A (zh) * 2008-03-10 2009-09-16 中国网通集团宽带业务应用国家工程实验室有限公司 流媒体信息分发系统和方法及客户端
CN101552800A (zh) * 2008-04-01 2009-10-07 华为技术有限公司 提供媒体内容的方法、装置和系统
CN101677325A (zh) * 2008-09-16 2010-03-24 华为技术有限公司 发布媒体描述信息和获取媒体的方法、装置、系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916678A (zh) * 2012-12-31 2014-07-09 中国移动通信集团广东有限公司 多媒体数据转码方法、转码设备及多媒体数据播放系统
CN105141660A (zh) * 2015-07-24 2015-12-09 网宿科技股份有限公司 一种流媒体管理方法及系统
CN105141660B (zh) * 2015-07-24 2018-04-24 网宿科技股份有限公司 一种流媒体管理方法及系统
CN114925249A (zh) * 2022-05-20 2022-08-19 东南大学 一种面向自适应流媒体的视频传输指纹快速生成方法
CN115277651A (zh) * 2022-06-22 2022-11-01 肯特智能技术（深圳）股份有限公司 基于xml文件的配置式流媒体软件方法及系统
CN115277651B (zh) * 2022-06-22 2024-05-24 肯特智能技术（深圳）股份有限公司 基于xml文件的配置式流媒体软件方法及系统

Also Published As

Publication number Publication date
CN102282825B (zh) 2013-11-06
CN102282825A (zh) 2011-12-14

Similar Documents

Publication Publication Date Title
WO2012079223A1 (fr) Procédé, système et noeud tampon pour mappage d'adresses de demandes de flux multimédia dans un réseau de fourniture de contenus
JP6944485B2 (ja) １つの要求メッセージに基づいたネットワーク・ノードへの多数のチャンクの要求
JP6014870B2 (ja) ストリーミング・メディア・コンテンツのリアルタイム・トランスマックス変換の方法およびシステム
US20150256600A1 (en) Systems and methods for media format substitution
WO2017096830A1 (fr) Procédé de distribution de contenu et serveur mandataire de planification pour plate-forme cdn
JP2016028474A (ja) バイト範囲リクエストを使用したビデオデータのネットワークストリーミング
WO2018133601A1 (fr) Procédé et appareil de transmission de contenu multimédia diffusé en continu, serveur et terminal
US20100180043A1 (en) Systems, Methods, and Computer Program Products for Transmitting and/or Receiving Media Streams
JP2017529726A (ja) ストリーミングサービスのためのクライアント及びサーバの動作方法
US10673907B2 (en) Systems and methods for providing DLNA streaming to client devices
WO2015176470A1 (fr) Procédé et dispositif de mise à jour d'état d'antémémoire reposant sur un http et processeur associé
US20180041611A1 (en) Content-based redirection
WO2015109847A1 (fr) Procédé de diffusion rapide de programmes segmentés, serveur et client
WO2013185514A1 (fr) Système et procédé de lecture de multimédia en flux continu
TW201517610A (zh) 產生視頻快速開啟之訊框集組
CN100576906C (zh) 一种网络内容传输控制系统和方法
Van Deursen et al. On media delivery protocols in the web
US20150113101A1 (en) Method and apparatus for providing streaming content
JP6597604B2 (ja) 受信装置、送信装置、データ通信方法、およびデータ処理方法
CN108605154B (zh) 一种消息交互的方法和客户端设备
Mekuria et al. Multi-protocol video delivery with late trans-muxing
US9237178B2 (en) Combined binary string for signaling byte range of media fragments in adaptive streaming
WO2015109842A1 (fr) Procédé de traitement de programmes segmentés, serveur et dispositif client
CN113891176A (zh) 基于hls的点播流量控制方法、装置、设备及存储介质
CN101465861B (zh) 用于传输和/或接收媒体流的系统、方法和计算机编程产品

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080006601.3

Country of ref document: CN

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

Ref document number: 10860680

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10860680

Country of ref document: EP

Kind code of ref document: A1