WO2019057212A1 - Procédé, appareil et dispositif permettant de planifier un service dans un nœud cdn, et support de stockage - Google Patents
Procédé, appareil et dispositif permettant de planifier un service dans un nœud cdn, et support de stockage Download PDFInfo
- Publication number
- WO2019057212A1 WO2019057212A1 PCT/CN2018/107387 CN2018107387W WO2019057212A1 WO 2019057212 A1 WO2019057212 A1 WO 2019057212A1 CN 2018107387 W CN2018107387 W CN 2018107387W WO 2019057212 A1 WO2019057212 A1 WO 2019057212A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- cache server
- content resource
- resource
- cdn
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004422 calculation algorithm Methods 0.000 claims abstract description 24
- 230000004044 response Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 238000013507 mapping Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000003068 static effect Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000013021 overheating Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
Definitions
- the present disclosure relates to the field of wireless mobile communications, for example, to a content delivery network (CDN) intra-node intra-service scheduling method, apparatus, device, and storage medium.
- CDN content delivery network
- the CDN system has to carry more and more content and more and more storage content, including Android market, Apple market application download (some applications exceed 500M), massive video online playback, And 4096 ⁇ 2160 pixel resolution (4K resolution), virtual reality (Virtual Reality, VR) and other high-definition video gradually increased.
- the scheduling of multiple cache servers in a CDN node must have high performance: the traditional algorithm based on file distribution centralized record update can not meet such requirements, because the content distribution index of Server Load Balancing (SLB) is the same.
- SLB Server Load Balancing
- the content storage of multiple cache servers is consistent, and a high data consistency algorithm is designed to efficiently process the index of massive content (the latency of SLB scheduling is very low, such as less than 1ms).
- the number of levels of content of multiple cache servers in a CDN node is increased: in the traditional sense, a large file is generally a single file, and one or more cache servers exist in the file content.
- HLS HyperText Transfer Protocol Live Streaming
- many video content is stored in the form of fragmented files.
- a movie recorded an index on the content storage address, and now based on the score.
- the method record number of the slice can be 300 times of the original. If the record mode is based on the centralized content index, the load of the SLB and the content consistency of the content in the SLB and the cache server are greatly increased.
- the present disclosure provides a CDN intra-node service scheduling method and apparatus, in order to solve the problem that the load balancing load in the CDN node is high, the load balancing, and the cache server are difficult to maintain data consistency in the mass content scenario.
- Equipment and storage media are used to satisfy the load balancing load in the CDN node.
- the CDN intra-node service scheduling method provided by the present disclosure is applied to a cache server, including:
- the present disclosure further provides a CDN intra-node service scheduling apparatus, including: a receiving module, a first computing module, and a second computing module:
- the receiving module is configured to: when receiving the request message for acquiring the content resource, extract a uniform resource locator of the content resource in the request message;
- the first calculating module is configured to determine an ID of the content resource according to the uniform resource locator
- the second calculating module is configured to select, according to the ID of the content resource, a root cache server for acquiring the content resource in all cache servers in the CDN node according to a preset selection algorithm.
- the present disclosure also provides a CDN intra-node service scheduling device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, the computer program being The processor performs the above-described CDN intra-node service scheduling method when executed by the processor.
- the present disclosure further provides a storage medium on which a CDN intra-node service scheduler is stored, and the CDN intra-node service scheduler is implemented by the processor to implement the above-mentioned CDN intra-node service. Scheduling method.
- the storage medium is a computer readable storage medium.
- FIG. 1 is a schematic flowchart of a method for allocating a service scheduling in a CDN node according to an embodiment of the present disclosure
- FIG. 2 is a schematic structural diagram of a service scheduling allocation device in a CDN node according to an embodiment of the present disclosure
- FIG. 3 is a schematic diagram showing the structure of a CDN node and its relationship with an external network element
- Example 4 is a schematic flowchart of a service scheduling allocation method in a CDN node in Example 1;
- Example 5 is a schematic flowchart of a service scheduling allocation method in a CDN node in Example 2.
- FIG. 6 is a schematic structural diagram of a service scheduling distribution device in a CDN node according to an embodiment of the present disclosure.
- the present disclosure provides a CDN intra-node service scheduling method and apparatus, in order to solve the problem that the load balancing load in the CDN node is high, the load balancing, and the cache server are difficult to maintain data consistency in the mass content scenario.
- Apparatus and Storage Media The following disclosure is described with reference to the accompanying drawings. The embodiments described herein are merely illustrative of the disclosure and are not limiting of the disclosure.
- a CDN node can be understood as a logical concept rather than a physical entity.
- a CDN node may include load balancing, a cluster of cache servers, and one or more auxiliary modules (eg, alarm modules) that implement non-core functions.
- the cache server cluster may include one or more cache servers, that is, when one cache server has limited capabilities, multiple cache servers may be employed, and the functions of the multiple cache servers are the same as one cache server.
- FIG. 1 is a schematic flowchart of a service scheduling allocation method in a CDN node according to an embodiment of the present disclosure.
- the CDN intra-node service scheduling method of the disclosed embodiment includes:
- Step 110 When receiving the request message for acquiring the content resource, extract the uniform resource locator of the content resource in the request message.
- the cache server before receiving the request message for acquiring the content resource, the cache server further includes: the SLB receiving the Transmission Control Protocol (TCP) link establishment request sent by the user, according to the TCP connection situation. (including but not limited to the number of connections, the frequency of requests, the number of active connections, etc.), load balancing user requests to a cache server (assumed to be A).
- TCP Transmission Control Protocol
- Step 120 Determine an ID of the content resource according to the uniform resource locator.
- the determining the ID of the content resource according to the uniform resource locator includes: extracting domain name information in the uniform resource locator; and using a preset according to the uniform resource locator
- Step 130 Select, according to the ID of the content resource, a root cache server for acquiring the content resource in all cache servers in the CDN node according to a preset selection algorithm.
- the method further includes:
- the cache server and the root cache server are the same server, searching the cache server, acquiring the content resource, and performing a request response;
- the cache server is not the same server as the root cache server, sending the request message to the root cache server, and performing a request response according to the content resource fed back by the root cache server.
- the searching the cache server to obtain the content resource comprises: sending the request message to a superior node or a source station when the content server is not in the cache server, to obtain The content resource and cache the content resource. That is, when the cache server and the root cache server are the same server, and when the content resource is not in the cache server, the source is returned to the upper node or the source station to obtain the content resource, and the cache is obtained.
- the content resource when the cache server and the root cache server are the same server, and when the content resource is included in the cache server, Content resources are sent directly to the user.
- the superior node can be understood as a back-end server, ie, a database server, and the source station can be understood as a location where the data source of the CDN is stored.
- the first CDN node, the second CDN node, and the third CDN node are included, and when the content resource requested by the terminal does not exist in the first CDN node, the second CDN node is searched, and when the second CDN node is also If there is no content resource requested by the terminal, the third CDN node may be searched. If the content resource requested by the terminal does not exist in the third CDN node, the content resource is obtained from the source station, and the source station is the source of the content resource.
- the content resource requested by the terminal exists in the third CDN node, the content resource is provided to the terminal, and the node that wants the content resource to the next-level CDN node is the upper node, that is, the second CDN node is the upper node of the first CDN node.
- the third CDN node is a superior node of the second CDN node.
- the method further includes: when the source-to-root cache server still cannot obtain the content resource, continue to return the source to the upper-level node or the source station to obtain the content resource, And caching the content resource to the root cache server.
- the method further includes: when the cache server and the root cache server are not the same server, but the content server is included in the cache server, The content resource is sent directly to the user.
- the method further includes: counting the number of times the content resource is accessed, and determining whether the content resource is hot content according to the number of times the content resource is accessed; The content resource is hot content, and when the hot content fed back by the root cache server is received, the hot content is cached.
- the number of times the content resource is accessed is counted, and whether the content resource is hot content is calculated according to the number of times the content resource is accessed, and the following manner may be adopted:
- Method 1 Calculate whether the content is a hotspot according to the time dimension and the ID dimension of the content resource.
- Method 2 Calculate the content access traffic according to the time dimension and the ID dimension of the content resource, and calculate whether the content is hot.
- step 130 may also be represented as the following steps:
- a and B are different cache servers, there are two cases: the first case is: when the content resource is non-hotspot content: the A proxy returns the source to B, and the content is not cached when the content passes the A; The situation is: when the content resource is hot content: when the content passes A, the content is cached.
- the CDN intra-node service scheduling method can fully utilize the algorithm mode without recording and synchronizing the content in one or more cache server indexes when performing internal content scheduling of the CDN node, thereby greatly reducing the SLB scheduling load. It avoids the problems caused by inconsistent content index, unsynchronized synchronization, and SLB abnormality. At the same time, it can improve the load balance of one or more cache servers in the CDN node, reduce the overheating of a cache server due to hot spots, and avoid the traditional adoption.
- the content consistency record is generated by the scheme of accurate content index recording in the mass content scene.
- the embodiment of the present disclosure further provides a CDN intra-node service scheduling apparatus, which is applied to a cache server.
- FIG. 2 is a schematic structural diagram of a service scheduling distribution apparatus in a CDN node according to an embodiment of the present disclosure, as shown in FIG. 2
- the CDN intra-node service scheduling apparatus of the embodiment of the present disclosure includes a receiving module 20, a first computing module 22, and a second computing module 24:
- the receiving module 20 is configured to: when receiving the request message for acquiring the content resource, extract the uniform resource locator of the content resource in the request message;
- the first calculating module 22 is configured to determine an ID of the content resource according to the uniform resource locator
- the second calculating module 24 is configured to select, according to the ID of the content resource, a root cache server for acquiring the content resource in all cache servers in the CDN node according to a preset selection algorithm.
- the content proxy return source module 26 is further included:
- the content proxy back to the source module 26 is configured to determine whether the cache server and the root cache server are the same server;
- the cache server and the root cache server are the same server, searching the cache server, acquiring the content resource, and performing a request response;
- the cache server is not the same server as the root cache server, sending the request message to the root cache server, and performing a request response according to the content resource fed back by the root cache server.
- the content proxy back source module 26 is configured to:
- the request message is sent to a superior node or a source station to obtain the content resource, and the content resource is cached.
- the CDN in-node service scheduling apparatus of the present disclosure further includes a content hotspot statistics module 28 and a content cache module 30:
- the content hotspot statistic module 28 is configured to count the number of times the content resource is accessed, and calculate whether the content resource is hot content according to the number of times the content resource is accessed;
- the content caching module 30 is configured to cache the hot content when the content resource is hot content and when receiving the hot content fed back by the root cache server.
- the first computing module 22 is configured to:
- the second computing module 24 is configured to:
- the root cache server of the ID mapping of the content resource is obtained in a set of all cache servers in the CDN node by using a preset consistency hash algorithm.
- FIG. 3 is a schematic diagram showing the structure of a CDN node and its relationship with an external network element.
- the CDB and the N cache servers (N is a positive integer greater than or equal to 1) are included in the CDN node, wherein a cache server is included as an example, and the content deduplication module is included in the cache server ( The first calculation module 22 and the second calculation module 24), the content hotspot statistics module 28, the content proxy return source module 26, the content cache module 30, and the content replication module are included.
- the CDN intra-node service scheduling apparatus can fully utilize an algorithm manner without recording and synchronizing content actually in one or more cache server indexes when performing internal content scheduling of a CDN node, thereby greatly reducing the SLB scheduling load. It avoids the problems caused by inconsistent content index, unsynchronized synchronization, and SLB abnormality. At the same time, it can improve the load balance of one or more cache servers in the CDN node, reduce the overheating of a cache server due to hot spots, and avoid the traditional adoption.
- the content consistency record is generated by the scheme of accurate content index recording in the mass content scene.
- FIG. 4 is a schematic flowchart of a service scheduling allocation method in a CDN node in Example 1, as shown in FIG. 4, including the following step:
- the user 211 initiates a TCP link establishment request to the SLB of the CDN node, and the SLB receives the user to send a TCP link establishment request, and loads the user request to the cache server 231 according to the TCP connection situation (for example, the number of connections, the request frequency, and the number of active connections).
- the TCP connection situation for example, the number of connections, the request frequency, and the number of active connections.
- the cache server 231 receives the Hypertext Transfer Protocol (HTTP) information that the user 211 initiates to acquire the content resource request from the CDN node, including the request URI, and the domain name Domain.
- HTTP Hypertext Transfer Protocol
- the cache server 231 calculates a unique ID of the content resource corresponding to the request according to the URI request, the domain name information, and the pre-configured regular expression of the corresponding content resource of the domain name. For example, ss0.bdstatic.com/5aV1bjqh_Q23odCf/static/superman/img/logo/bd_logo1_31bdc765.png is used as the key KEY.
- the unique ID of the content resource is calculated by the message digest algorithm MD5 as fb6667636553c773d7d3fd13bc6d4d4e.
- the cache server 231 determines whether the content of the ID is fb6667636553c773d7d3fd13bc6d4d4e is hot content by counting the number of accesses in the content unit time and the predefined hotspot calculation algorithm. Assume that the content whose ID is fb6667636553c773d7d3fd13bc6d4d4e is non-hotspot content.
- the cache server 231 uses the consistency hash algorithm to calculate the root cache server ID of the content as cacheid3 by using the fb6667636553c773d7d3fd13bc6d4d4e, cacheid1, cacheid2, and cacheid3, that is, the root cache server is the cache server 231.
- the cache server 231 When the cache server 231 does not cache the content of the ID fb6667636553c773d7d3fd13bc6d4d4e, the upper CDN node or the source station 241 acquires the content resource in real time and returns the content resource to the user 211. At the same time, the cache server 231 also caches the content resources locally.
- FIG. 5 is a schematic flowchart of a method for allocating a service scheduling in a CDN node in the example 2, as shown in FIG. 5, including the following steps:
- the user 211 initiates a TCP link establishment request to the SLB of the CDN node, and the SLB receives the TCP connection request from the user, and load balances the user request to the cache server 232 according to the TCP connection situation (for example, the number of connections, the request frequency, and the number of active connections).
- the TCP connection situation for example, the number of connections, the request frequency, and the number of active connections.
- the cache server 232 receives the user 211 to initiate a request for acquiring a content resource to the CDN node, including requesting a URI, requesting HTTP information such as a domain name.
- a content resource to the CDN node, including requesting a URI, requesting HTTP information such as a domain name.
- the cache server 232 calculates a unique ID of the content resource corresponding to the request according to the URI request, the domain name information, and the pre-configured regular expression of the corresponding content resource of the domain name. For example, use ss0.bdstatic.com/5aV1bjqh_Q23odCf/static/superman/img/logo/bd_logo1_31bdc765.png to do KEY.
- the unique ID of the content resource calculated by MD5 is fb6667636553c773d7d3fd13bc6d4d4e.
- the cache server 232 calculates the content of the ID as fb6667636553c773d7d3fd13bc6d4d4e as the hot content by the hot content statistics.
- the cache server 232 uses the consistency hash algorithm to calculate the root cache server of the content as the cache server 231 by calculating the information such as the cache server ID list and the like by fb6667636553c773d7d3fd13bc6d4d4e.
- the cache server 232 initiates a proxy return request to the cache server 231.
- the cache server 231 does not cache the content of the ID bb6667636553c773d7d3fd13bc6d4d4e
- the upper CDN node or the source station 241 acquires the content resource in real time, and returns the content resource to the cache server 231.
- the cache server 231 also caches the content locally.
- the cache server 232 returns the content data to the user and caches the content fb6667636553c773d7d3fd13bc6d4d4e locally.
- FIG. 6 is a schematic structural diagram of a service scheduling distribution device in a CDN node according to an embodiment of the present disclosure.
- the present disclosure also provides a CDN intra-node service scheduling device, including a memory 610 and a processor 620 having stored thereon a computer program executable on the processor 620, the computer program being processed
- the CDN intra-node service scheduling method as described in the embodiment of the present disclosure is implemented when the device is executed.
- the present disclosure provides a computer readable storage medium having a CDN intra-node service scheduler stored thereon, the CDN intra-node service scheduler being implemented by a processor to implement the above Service scheduling method within a CDN node.
- the CDN intra-node service scheduling method, apparatus, device and computer readable storage medium can fully utilize an algorithm manner without recording and synchronizing content actually in one or more caches when performing internal content scheduling of a CDN node.
- the server index greatly reduces the SLB scheduling load, avoids the problems caused by content index inconsistency, unsynchronized synchronization, and SLB exceptions.
- it can improve the load balance of one or more cache servers in the CDN node and reduce the sudden hotspots. This causes a cache server to overheat and circumvents the difficulty of content consistency caused by the traditional scheme of using accurate content index records in massive content scenarios.
Abstract
L'invention concerne un procédé, un appareil et un dispositif permettant de planifier un service dans un noeud de réseau de distribution de contenu (CDN), et un support de stockage. Le procédé comprend les étapes suivantes : lors de la réception d'un message de demande d'acquisition d'une ressource de contenu, extraire, à partir du message de demande, un dispositif de localisation de ressource uniforme de la ressource de contenu (110) ; selon le dispositif de localisation de ressource uniforme, déterminer une identification (ID) de la ressource de contenu (120) ; et selon l'ID de la ressource de contenu, et selon un algorithme de sélection prédéfini, sélectionner, parmi tous les serveurs de cache à l'intérieur du noeud CDN, un serveur de cache racine utilisé pour acquérir la ressource de contenu (130).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710867903.3A CN109542613A (zh) | 2017-09-22 | 2017-09-22 | 一种cdn节点内服务调度的分配方法、装置及存储介质 |
CN201710867903.3 | 2017-09-22 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019057212A1 true WO2019057212A1 (fr) | 2019-03-28 |
Family
ID=65811023
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/107387 WO2019057212A1 (fr) | 2017-09-22 | 2018-09-25 | Procédé, appareil et dispositif permettant de planifier un service dans un nœud cdn, et support de stockage |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN109542613A (fr) |
WO (1) | WO2019057212A1 (fr) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112243027A (zh) * | 2020-09-30 | 2021-01-19 | 武汉兴图新科电子股份有限公司 | 一种基于集群技术解决海量媒体流分发问题的系统及方法 |
CN113238836A (zh) * | 2021-04-15 | 2021-08-10 | 网宿科技股份有限公司 | 一种分布式内容调度方法、调度系统及中心服务器 |
CN113992760A (zh) * | 2021-10-22 | 2022-01-28 | 北京百度网讯科技有限公司 | 回源流量的调度方法、装置、设备以及存储介质 |
CN114793234A (zh) * | 2022-03-31 | 2022-07-26 | 北京百度网讯科技有限公司 | 消息处理方法、装置、设备和存储介质 |
CN114900562A (zh) * | 2022-05-09 | 2022-08-12 | 北京百度网讯科技有限公司 | 一种资源获取方法、装置、电子设备和存储介质 |
CN115473857A (zh) * | 2022-09-14 | 2022-12-13 | 北京奇艺世纪科技有限公司 | 一种资源分发方法、装置、系统、电子设备及存储介质 |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111787040A (zh) * | 2019-04-04 | 2020-10-16 | 阿里巴巴集团控股有限公司 | 回源、资源请求处理方法和装置、电子设备及计算机可读存储介质 |
CN110098978B (zh) * | 2019-04-12 | 2021-02-26 | 网宿科技股份有限公司 | 一种dns调度的测试方法、装置、网络设备及存储介质 |
CN110134896B (zh) * | 2019-05-17 | 2023-05-09 | 山东渤聚通云计算有限公司 | 一种代理服务器的监控过程及智能缓存方法 |
CN112513830A (zh) * | 2019-07-15 | 2021-03-16 | 华为技术有限公司 | 内容分发网络中的回源方法及相关装置 |
CN110601802B (zh) * | 2019-08-16 | 2022-05-20 | 网宿科技股份有限公司 | 一种降低集群回父带宽的方法及装置 |
CN110708369B (zh) * | 2019-09-25 | 2022-09-16 | 深圳市网心科技有限公司 | 设备节点的文件部署方法、装置、调度服务器及存储介质 |
CN112953984B (zh) * | 2019-12-10 | 2023-07-28 | 贵州白山云科技股份有限公司 | 数据处理方法、装置、介质及系统 |
CN111767991B (zh) * | 2020-06-29 | 2023-08-15 | 重庆大学 | 一种基于深度q学习的测控资源调度方法 |
CN113472852B (zh) * | 2021-06-02 | 2023-07-25 | 乐视云网络技术(北京)有限公司 | 一种cdn节点的回源方法、装置、设备以及存储介质 |
CN114244903A (zh) * | 2021-11-01 | 2022-03-25 | 网宿科技股份有限公司 | 资源调度方法、系统、服务器及存储介质 |
CN114301848B (zh) * | 2021-12-10 | 2023-08-29 | 阿里巴巴(中国)有限公司 | 基于cdn的通信方法、系统、设备及存储介质 |
CN114338686A (zh) * | 2021-12-21 | 2022-04-12 | 江苏云工场信息技术有限公司 | 一种cdn节点服务器的回源方法及装置 |
CN115002132A (zh) * | 2022-05-23 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | 一种用于pcdn网络预缓存资源的分发方法、系统及计算机设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013078687A1 (fr) * | 2011-12-02 | 2013-06-06 | 华为技术有限公司 | Procédé d'acheminement de données sur un réseau de distribution de contenu, et système et terminal d'utilisateur correspondants |
CN104159132A (zh) * | 2014-08-22 | 2014-11-19 | 华为软件技术有限公司 | 视频定制化服务的实现方法及装置 |
CN104272705A (zh) * | 2012-05-15 | 2015-01-07 | 瑞典爱立信有限公司 | 用于显示运营商通告的方法和装置 |
CN104951480A (zh) * | 2014-03-31 | 2015-09-30 | 杭州迪普科技有限公司 | 一种cdn系统中资源存储的索引装置及方法 |
CN106657196A (zh) * | 2015-11-02 | 2017-05-10 | 华为技术有限公司 | 一种缓存内容淘汰方法及缓存装置 |
-
2017
- 2017-09-22 CN CN201710867903.3A patent/CN109542613A/zh not_active Withdrawn
-
2018
- 2018-09-25 WO PCT/CN2018/107387 patent/WO2019057212A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013078687A1 (fr) * | 2011-12-02 | 2013-06-06 | 华为技术有限公司 | Procédé d'acheminement de données sur un réseau de distribution de contenu, et système et terminal d'utilisateur correspondants |
CN104272705A (zh) * | 2012-05-15 | 2015-01-07 | 瑞典爱立信有限公司 | 用于显示运营商通告的方法和装置 |
CN104951480A (zh) * | 2014-03-31 | 2015-09-30 | 杭州迪普科技有限公司 | 一种cdn系统中资源存储的索引装置及方法 |
CN104159132A (zh) * | 2014-08-22 | 2014-11-19 | 华为软件技术有限公司 | 视频定制化服务的实现方法及装置 |
CN106657196A (zh) * | 2015-11-02 | 2017-05-10 | 华为技术有限公司 | 一种缓存内容淘汰方法及缓存装置 |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112243027A (zh) * | 2020-09-30 | 2021-01-19 | 武汉兴图新科电子股份有限公司 | 一种基于集群技术解决海量媒体流分发问题的系统及方法 |
CN112243027B (zh) * | 2020-09-30 | 2023-04-07 | 武汉兴图新科电子股份有限公司 | 一种基于集群技术解决海量媒体流分发问题的系统及方法 |
CN113238836A (zh) * | 2021-04-15 | 2021-08-10 | 网宿科技股份有限公司 | 一种分布式内容调度方法、调度系统及中心服务器 |
CN113992760A (zh) * | 2021-10-22 | 2022-01-28 | 北京百度网讯科技有限公司 | 回源流量的调度方法、装置、设备以及存储介质 |
CN113992760B (zh) * | 2021-10-22 | 2024-03-01 | 北京百度网讯科技有限公司 | 回源流量的调度方法、装置、设备以及存储介质 |
CN114793234A (zh) * | 2022-03-31 | 2022-07-26 | 北京百度网讯科技有限公司 | 消息处理方法、装置、设备和存储介质 |
CN114793234B (zh) * | 2022-03-31 | 2023-04-25 | 北京百度网讯科技有限公司 | 消息处理方法、装置、设备和存储介质 |
CN114900562A (zh) * | 2022-05-09 | 2022-08-12 | 北京百度网讯科技有限公司 | 一种资源获取方法、装置、电子设备和存储介质 |
CN115473857A (zh) * | 2022-09-14 | 2022-12-13 | 北京奇艺世纪科技有限公司 | 一种资源分发方法、装置、系统、电子设备及存储介质 |
CN115473857B (zh) * | 2022-09-14 | 2023-12-15 | 北京奇艺世纪科技有限公司 | 一种资源分发方法、装置、系统、电子设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN109542613A (zh) | 2019-03-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019057212A1 (fr) | Procédé, appareil et dispositif permettant de planifier un service dans un nœud cdn, et support de stockage | |
US20220382899A1 (en) | Systems and Methods for Facilitating Access to Private Files Using a Cloud Storage System | |
KR102133951B1 (ko) | 짧은 링크 처리 방법, 디바이스, 및 서버 | |
US9628554B2 (en) | Dynamic content delivery | |
CN107231402B (zh) | Http请求处理方法、装置及系统 | |
US9390200B2 (en) | Local caching device, system and method for providing content caching service | |
US20110289126A1 (en) | Content delivery network | |
US9065796B2 (en) | Dynamic application programming interface | |
US8533296B2 (en) | Schema-based feed generation for media syndication | |
US20150215405A1 (en) | Methods of managing and storing distributed files based on information-centric network | |
CN108683668B (zh) | 内容分发网络中的资源校验方法、装置、存储介质及设备 | |
JP2009157444A (ja) | サービス提供システム、ゲートウェイ、およびサーバ | |
WO2021253889A1 (fr) | Procédé et appareil d'équilibrage de charge, dispositif mandataire, dispositif antémémoire et noeud de desserte | |
US9386099B2 (en) | Local caching device, system and method for providing content caching service | |
US10574703B1 (en) | Content delivery employing multiple security levels | |
US20210158353A1 (en) | Methods, systems, apparatuses, and devices for processing request in consortium blockchain | |
TW201405324A (zh) | 雲端資料儲存系統及基於該系統的資料儲存與共用方法 | |
CN116578740A (zh) | 计算机实现的方法、存储系统和计算机可读存储介质 | |
CN108540510B (zh) | 一种云主机创建方法、装置及云服务系统 | |
US11841842B2 (en) | Method and system for using external content type object types | |
WO2022057525A1 (fr) | Procédé et dispositif de récupération de données, dispositif électronique et support de stockage | |
EP3579526B1 (fr) | Procédé et appareil de rétroaction de fichier de ressource | |
CN112866406B (zh) | 一种数据存储方法、系统、装置、设备及存储介质 | |
CN107241422B (zh) | 一种实时将外部用户及用户组信息同步进Apache Ranger的方法 | |
US9432238B2 (en) | Communicating large amounts of data over a network with improved efficiency |
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: 18858152 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09.09.2020) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18858152 Country of ref document: EP Kind code of ref document: A1 |