WO2022127319A1 - 数据刷新的方法、装置、电子设备及计算机可读存储介质 - Google Patents

数据刷新的方法、装置、电子设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2022127319A1
WO2022127319A1 PCT/CN2021/123638 CN2021123638W WO2022127319A1 WO 2022127319 A1 WO2022127319 A1 WO 2022127319A1 CN 2021123638 W CN2021123638 W CN 2021123638W WO 2022127319 A1 WO2022127319 A1 WO 2022127319A1
Authority
WO
WIPO (PCT)
Prior art keywords
refresh
data
target data
cache
local cache
Prior art date
Application number
PCT/CN2021/123638
Other languages
English (en)
French (fr)
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 北京金山云网络技术有限公司
Publication of WO2022127319A1 publication Critical patent/WO2022127319A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0806—Multiuser, multiprocessor or multiprocessing cache systems
    • G06F12/0815—Cache consistency protocols
    • G06F12/0817—Cache consistency protocols using directory methods
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0804—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches with main memory updating

Definitions

  • the present application relates to the technical field of data processing, and in particular, to a data refresh method, apparatus, electronic device, and computer-readable storage medium.
  • CDN nodes usually contain multiple cache devices, usually more than 10 depending on the size, and the same resource (such as video, picture, etc.) is often only cached in the node on one or more cache devices, but the client does not know which devices are cached on. Therefore, the traditional CDN node refresh method is to send a resource refresh request to all cache devices in the node to ensure successful refresh. However, this refresh method will invalidate a request. For example, suppose that there are 10 devices in a CDN node, but only one device has cached the target resource. If the refresh request of the target resource is sent to all the nodes in the node 10 devices is equivalent to amplifying the refresh request by 9 times, which increases the difficulty of the customer's operation and the cache pressure of the CDN.
  • the purpose of this application is to provide a data refresh method, apparatus, electronic device and computer-readable storage medium, which can alleviate the problem of many invalid refresh requests in CDN node refresh and reduce the cache pressure of CDN nodes , which improves the refresh efficiency.
  • an embodiment of the present application provides a data refresh method, which is applied to a node server.
  • the method includes: receiving a refresh request for target data; determining whether the local cache stores the target data; and if the local cache stores the target data The target data is refreshed according to the refresh request.
  • the above-mentioned step of determining whether the local cache stores the target data includes: obtaining an index directory of the cached data in the local cache; searching for an index of the target data from the index directory; and according to the target data The index lookup result to determine whether the target data is stored in the local cache.
  • the above step of obtaining the index directory of the cached data in the local cache includes: obtaining the index directory of the cached data in the local cache through a preset refresh proxy service and a cache service corresponding to the local cache; wherein, The refresh proxy service runs on the node server, and the refresh proxy service is connected in communication with the cache service, and the cache service is set to generate an index directory of the cache data.
  • the above-mentioned step of obtaining the index directory of the cached data in the local cache through the preset refresh proxy service and the cache service corresponding to the local cache includes: when monitoring that the refresh proxy service is started, establishing the A communication connection between the cache service and the refresh proxy service; and through the cache service, the index directory of the cached data in the local cache is synchronized to the refresh proxy service in a heartbeat manner.
  • the above method further includes: if the local cache does not store the target data, returning a refresh success.
  • an embodiment of the present application further provides a data refresh device, which is applied to a node server, and the device includes: a refresh request receiving module configured to receive a refresh request for target data; a judgment module configured to determine a local cache whether the target data is stored; and a refresh module, configured to refresh the target data according to the refresh request if the local cache stores the target data.
  • the above judgment module is further configured to: obtain an index directory of the cached data in the local cache; search the index of the target data from the index directory; and determine the local cache according to the index search result of the target data Whether the target data is stored.
  • the above refresh module is further configured to: if it is determined that the target data is not stored in the local cache, return refresh success.
  • an embodiment of the present application further provides an electronic device, the electronic device includes a processor and a memory, the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions In order to achieve the above data refresh method.
  • embodiments of the present application further provide a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions The processor is prompted to implement the above data refresh method.
  • FIG. 1 is a schematic diagram of a scenario of accessing a CDN network according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of the architecture of a content distribution network according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for data refresh provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another data refresh method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a CDN node refresh provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an apparatus for data refresh provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • 61-refresh request receiving module 62-judging module; 63-refreshing module; 71-processor; 72-memory; 73-bus; 74-communication interface.
  • each CDN node is equivalent to a website server placed around it.
  • DNS Domain Name System, Domain Name System
  • the user's request is transparently directed to its nearest node.
  • the CDN server in the node will respond to the user's request like the original server of the website. Because it is closer to the user, the response time must be faster.
  • the intelligent scheduling DNS is a key system in the CDN service. When a user accesses a website that joins the CDN service, the domain name resolution request will be finally handled by the intelligent scheduling DNS. It uses a set of pre-defined policies. The node address is provided to users, so that users can get fast service. At the same time, the intelligent scheduling DNS also needs to maintain communication with the distributed CDN nodes, track the health status and capacity of each node, and ensure that user requests are allocated to the nearest available nodes.
  • FIG. 1 it is a schematic diagram of a scenario of accessing a CDN network, wherein, when a user client accesses the CDN network, the interaction with the domain name system DNS and the edge nodes in the CDN network is a necessary process. , The interaction between the upper node and the source station is an optional process. If the cache is hit in the edge node, the visit does not involve the interaction between the edge node and other nodes (that is, it will not pass through the dotted line in Figure 1). process).
  • FIG. 2 it is a schematic diagram of the architecture of a content distribution network, wherein the CDN node includes multiple caches and multiple proxy servers nginx, and each nginx communicates with a Linux virtual server (Linux Virtual Server, LVS) Connection, in actual operation, the user's access request is sent to each proxy server nginx through LVS, and the proxy server nginx provides load balancing service, and distributes the access request to the cache to respond to the access request.
  • LVS Linux Virtual Server
  • edge nodes directly serve users (netizens), and the number is also the largest; middle-level nodes mainly aggregate back-to-source requests from edge nodes, and do not directly serve netizens, and the number is small; The upper-level nodes mainly aggregate the back-to-source requests of the middle-level nodes, and do not directly serve the netizens, and the number is relatively small. Also, usually users do not need to pay for the bandwidth generated by the middle/upper tier nodes.
  • the embodiments of the present application provide a data refresh method, apparatus and electronic device, and the technology can be applied to Data refresh, especially in the node refresh scenario in the CDN network.
  • a data refresh method disclosed in this embodiment of the present application is first introduced in detail.
  • FIG. 3 is a schematic flowchart of a method for data refresh provided by an embodiment of the present application, wherein the method is applied to a node server, and as can be seen from FIG. 3 , the method includes the following steps:
  • Step S302 Receive a refresh request for target data.
  • the above-mentioned target data may be videos, pictures, documents, etc., and refreshing the target data may include at least one of adding data, deleting data, and modifying data.
  • the above-mentioned node server may be an edge node server in the CDN network, which directly receives the user's refresh request for the target data, and is set to forward the refresh request to the cache device in the node, so that the cache device can refresh the data according to the refresh request. .
  • Step S304 Determine whether the target data is stored in the local cache. If the target data is stored, step S306 is performed; if the target data is not stored, step S308 is performed.
  • the node server After receiving the refresh request, the node server first determines whether the target data is stored in the local cache. If the target data is stored, the target data is refreshed according to the refresh request; if the target data is not stored, the refresh success is directly returned. , without forwarding the flush request to the cache device within the node.
  • each CDN node will contain multiple cache devices, but for a specific resource, such as video, picture, etc., it will only be cached on one or more of the cache devices, and the client itself does not know the resource cache In which cache device, therefore, in order to ensure the success of the refresh, the traditional refresh method is to send the refresh request for the resource to all the cache devices in the node, which will cause the invalidation of the refresh request to be multiplied.
  • the node server prejudges whether the target data to be refreshed is stored in the local cache. If the target data to be refreshed is not stored in the local cache, it is unnecessary to forward the refresh request to the cache device in the node. Eliminate invalid refreshes and transparently transmit valid refresh requests to the cache device.
  • Step S306 Refresh the target data according to the refresh request.
  • the node server If the node server confirms that the target data is stored in the local cache, it will release the refresh request, transparently transmit the refresh request to the cache device, and the cache device will perform a data refresh operation according to the refresh request.
  • Step S308 Return to refresh success.
  • the node server If the node server confirms that the target data is not stored in the local cache, it indicates that the refresh request is an "invalid" request, that is, even if the refresh request is sent to each cache device, no data update will actually be generated, so it is unnecessary refresh operation. In this embodiment, if the target data is not stored in the local cache, the refresh success is directly returned. Therefore, this method saves the operation of sending the refresh request to each cache device, and each cache device does not need to perform "invalid" refresh according to the refresh request.
  • a data refresh method In a data refresh method provided by an embodiment of the present application, when a refresh request for target data is received, it is first determined whether the target data is stored in the local cache, and if the target data is stored in the local cache, according to the refresh request Refresh the target data. If the target data is not stored in the local cache, the refresh success is directly returned.
  • the node server pre-filters the refresh requests, and only transmits the refresh information of the data existing in the local cache to the cache device for refresh, thereby filtering out invalid refresh requests, reducing the cache pressure of CDN nodes, and improving the Refresh efficiency and refresh success rate.
  • this embodiment describes the implementation of step S304 (determining whether the target data is stored in the local cache) in the above embodiment, so as to facilitate a deeper understanding of the solution .
  • FIG. 4 it is a schematic flowchart of another method for data refresh.
  • the method is applied to a node server.
  • the method includes the following steps:
  • Step S402 Receive a refresh request for target data.
  • Step S404 Obtain the index directory of the cached data in the local cache.
  • a refresh proxy service may be set on the node server, and when the node server detects that the refresh proxy service is started, a communication connection between the cache service corresponding to the local cache and the refresh proxy service is established .
  • the refresh proxy service may also be set to be started at startup.
  • the cache service is further configured to generate an index directory of the local cached data, so that the refresh proxy service can obtain the index directory of the cached data from the cache service, and then determine whether there is target data in the local cache according to the index directory.
  • the index directory of the cached data in the local cache can be synchronized to the refresh proxy service in real time in a heartbeat manner, so that the refresh proxy service can know the cache device. The latest cached data in the case.
  • Step S406 Search the index of the target data from the index directory.
  • the above refresh proxy service can be used to search according to the obtained index directory to determine whether there is an index of the target data in the index directory.
  • Step S408 According to the index search result of the target data, determine whether the target data is stored in the local cache, if the target data is stored, go to step S410; if the target data is not stored, go to step S412.
  • the index of the target data is found in the index directory, it indicates that the target data is stored in the local cache, so that the target data is refreshed according to the refresh request.
  • the refresh request is released and sent to the cache device, so that the cache device refreshes the target data according to the refresh request.
  • the refresh request is intercepted, and the refresh request is not sent to the cache device, but the refresh success is directly returned.
  • a prompt may also be returned to the user, indicating that the target data is not stored in the local cache.
  • Step S410 Refresh the target data according to the refresh request.
  • Step S412 Return to refresh success.
  • steps S410 and S412 correspond to steps S306 to S308, and the description of the corresponding content may refer to the corresponding parts, which will not be repeated here.
  • FIG. 5 is a schematic flowchart of a CDN node refresh provided by an embodiment of the present application.
  • a process of refreshing a CDN node by using the data refresh method in the above embodiment is shown, Among them, there is a refresh agent service (refreshd) running on the CDN node, and the refresh process is as follows:
  • the customer submits a refresh request to the refresh center through the console or API (Application Programming Interface), and the refresh center then distributes the refresh request to the agent (agent) on the relay (relay) machine of the CDN node.
  • the agent changes from directly requesting the cache device (cache) to communicating with the refresh agent service (refreshed).
  • the refresh proxy service when the refresh proxy service is started, it actively connects to the cache device cache, obtains all directory information from the cache device cache request, establishes a local directory structure, and then maintains this long connection with the cache service of the cache device in a heartbeat mode.
  • the refresh proxy service when the cache device is in normal service, the newly added or deleted cache files are synchronized in real time to the refresh proxy service through a long connection.
  • the refresh proxy service maintains a content directory in the cache device, and the two are consistent.
  • the refresh proxy service filters the refresh request according to the directory information of the cached data. If the target resource requested to refresh exists in the local cache, it means that the refresh needs to be processed, so that the refresh The request is passed to the cache device and waits for the refresh to succeed before returning to the client.
  • the pictures on the product event details page need to be updated in real time. It is estimated that a single machine needs to support refresh requests of 20k QPS (Queries-per-second, query rate per second), and such a high Frequent refresh requests will cause huge pressure on the cache device in the node and affect the access of normal netizens.
  • the refresh proxy service is set in the node server, and the requirement of filtering the refresh request is separated from the cache service to the refresh proxy service, the basic storage function of the cache service can be further restored.
  • FIG. 6 is a schematic structural diagram of a data refresh device, and the device is applied to a node server. It can be seen from FIG. 6 that the device includes a refresh request receiving module 61, a judgment module 62 and a refresh module 63 connected in sequence, wherein the functions of each module are as follows:
  • the refresh request receiving module 61 is configured to receive a refresh request for the target data
  • the judgment module 62 is set to determine whether the local cache stores the target data
  • the refresh module 63 is configured to refresh the target data according to the refresh request if the target data is stored in the local cache.
  • the above judgment module 62 is further configured to: obtain the index directory of the cached data in the local cache; search for the index of the target data from the index directory; and according to the index search result of the target data, Determines whether the target data is stored in the local cache.
  • the above refresh module 63 is further configured to: if it is determined that the target data is not stored in the local cache, return refresh success.
  • the above judgment module 62 is further configured to: obtain the index directory of the cached data in the local cache through a preset refresh proxy service and a cache service corresponding to the local cache; wherein, the refresh proxy service runs On the node server, and the refresh proxy service is in communication connection with the cache service, the cache service is set to generate an index directory of the cached data.
  • the above judgment module 62 is further configured to: when monitoring that the refresh proxy service is started, establish a communication connection between the cache service and the refresh proxy service; and through the cache service, to The heartbeat method synchronizes the index directory of the cached data in the local cache to the refresh proxy service.
  • FIG. 7 is a schematic structural diagram of the electronic device, wherein the electronic device includes a processor 71 and a memory 72 , and the memory 72 stores data that can be used by the processor 71 The machine-executable instructions to be executed, the processor 71 executes the machine-executable instructions to implement the above data refresh method.
  • the electronic device further includes a bus 73 and a communication interface 74, wherein the processor 71, the communication interface 74 and the memory 72 are connected through the bus.
  • the memory 72 may include a high-speed random access memory (RAM, Random Access Memory), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
  • the communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 74 (which may be wired or wireless), which may use the Internet, a wide area network, a local network, a metropolitan area network, and the like.
  • the bus can be an ISA bus, a PCI bus, an EISA bus, or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bidirectional arrow is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the processor 71 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in the processor 71 or an instruction in the form of software.
  • the above-mentioned processor 71 can be a general-purpose processor, including a central processing unit (Central Processing Unit, referred to as CPU), a network processor (Network Processor, referred to as NP), etc.; it can also be a digital signal processor (Digital Signal Processing, referred to as DSP) ), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor 71 reads the information in the memory 72, and completes the steps of the data refresh method in the foregoing embodiment in combination with its hardware.
  • Embodiments of the present application further provide a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by the processor, the machine-executable instructions cause the processor to
  • the machine-readable storage medium stores machine-executable instructions
  • the machine-executable instructions when called and executed by the processor, the machine-executable instructions cause the processor to
  • the data refresh method, data refresh apparatus, and computer program product of an electronic device provided by the embodiments of the present application include a computer-readable storage medium storing program codes, and the instructions included in the program codes can be configured to execute the foregoing method implementation.
  • the data refresh method described in the example reference may be made to the method embodiment for implementation, which will not be repeated here.
  • the functions, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-executable non-volatile computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the related technology or the part of the technical solution.
  • the computer software product is stored in a storage medium, including several The instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or CD and other media that can store program codes .
  • a data refresh method, device, electronic device, and computer-readable storage medium provided by the embodiments of the present application receive a refresh request for target data; determine whether the local cache stores the target data; if the local cache stores the target data , and refresh the target data according to the refresh request.
  • the node server filters the refresh requests in advance, and only transmits the refresh information of the data existing in the local cache to the cache device for refresh, thereby filtering out invalid refresh requests and reducing the cache pressure of CDN nodes. , which improves the refresh efficiency and refresh success rate.
  • the basic storage function of the cache service can be further restored.
  • the terms “installed”, “connected” and “connected” should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or the internal communication between the two components.
  • installed should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or the internal communication between the two components.
  • the present application is applied to the technical field of data processing, and provides a data refresh method, device, electronic device and computer-readable storage medium.
  • the refresh request is filtered in advance by the node server, and only the refresh information of the data existing in the local cache is stored. It is passed to the cache device for refresh, thereby filtering out invalid refresh requests, reducing the cache pressure of CDN nodes, and improving the refresh efficiency and refresh success rate.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种数据刷新的方法、装置、电子设备及计算机可读存储介质，涉及数据处理技术领域，该方法包括接收针对目标数据的刷新请求（S302）；确定本地缓存是否存储有该目标数据（S304）；如果本地缓存存储有该目标数据，根据该刷新请求刷新该目标数据（S306）。该方法通过节点服务器预先对刷新请求进行过滤，只将本地缓存中存在的数据的刷新信息传递给缓存设备，以进行刷新，从而过滤掉了无效的刷新请求，降低了CDN节点的缓存压力，提高了刷新效率和刷新成功率。

Description

数据刷新的方法、装置、电子设备及计算机可读存储介质
相关申请的交叉引用
本申请要求于2020年12月15日提交中国专利局的申请号为202011490332.4、名称为“数据刷新的方法、装置及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据处理技术领域，尤其是涉及一种数据刷新的方法、装置、电子设备及计算机可读存储介质。
背景技术
内容分发网络(Content Delivery Network，CDN)节点内部通常包含多台缓存设备，根据规模大小不同，一般在10台以上，而对于同一个资源(如视频、图片等)往往只会缓存在该节点中的一台或多台缓存设备上，但客户不知道具体是缓存在哪些设备。因此，传统的CDN节点刷新方式是将一个资源的刷新请求打到节点内的所有缓存设备上，以保证刷新成功。但是，这种刷新方式会将一个请求无效放大，例如，假设某CDN节点中有10台设备，而仅有一台设备上缓存了目标资源，如果将该目标资源的刷新请求发送给节点内所有的10台设备，则相当于将该刷新请求放大了9倍，从而增加了客户的操作难度以及CDN的缓存压力。
整体而言，现有的CDN节点刷新方式，会导致很多无效的刷新请求，增加了CDN节点的缓存压力。
发明内容
有鉴于此，本申请的目的在于提供一种数据刷新的方法、装置、电子设备及计算机可读存储介质，可以缓解CDN节点刷新中的无效刷新请求较多的问题，减少了CDN节点的缓存压力，提高了刷新效率。
第一方面，本申请实施例提供了一种数据刷新的方法，应用于节点服务器，该方法包括：接收针对目标数据的刷新请求；确定本地缓存是否存储有该目标数据；以及如果本地缓存存储有该目标数据，根据该刷新请求刷新该目标数据。
在本申请一实施方式中，上述确定本地缓存是否存储有该目标数据的步骤，包括：获取本地缓存中缓存数据的索引目录；从该索引目录中查找该目标数据的索引；以及根据该 目标数据的索引查找结果，确定本地缓存是否存储有该目标数据。
在本申请一实施方式中，上述获取本地缓存中缓存数据的索引目录的步骤，包括：通过预设的刷新代理服务和本地缓存对应的缓存服务，获取本地缓存中缓存数据的索引目录；其中，该刷新代理服务运行在该节点服务器上，且该刷新代理服务与该缓存服务通信连接，该缓存服务设置为生成该缓存数据的索引目录。
在本申请一实施方式中，上述通过预设的刷新代理服务和本地缓存对应的缓存服务，获取本地缓存中缓存数据的索引目录的步骤，包括：当监测到该刷新代理服务启动时，建立该缓存服务与该刷新代理服务之间的通信连接；以及通过该缓存服务，以心跳的方式将本地缓存中缓存数据的索引目录同步到该刷新代理服务。
在本申请一实施方式中，上述方法还包括：如果该本地缓存没有存储该目标数据，返回刷新成功。
第二方面，本申请实施例还提供了一种数据刷新的装置，应用于节点服务器，该装置包括：刷新请求接收模块，设置为接收针对目标数据的刷新请求；判断模块，设置为确定本地缓存是否存储有该目标数据；以及刷新模块，设置为如果本地缓存存储有该目标数据，根据该刷新请求刷新该目标数据。
在本申请一实施方式中，上述判断模块还设置为：获取本地缓存中缓存数据的索引目录；从该索引目录中查找该目标数据的索引；以及根据该目标数据的索引查找结果，确定本地缓存是否存储有该目标数据。
在本申请一实施方式中，上述刷新模块还设置为：如果确定本地缓存没有存储该目标数据，返回刷新成功。
第三方面，本申请实施例还提供了一种电子设备，该电子设备包括处理器和存储器，该存储器存储有能够被该处理器执行的计算机可执行指令，该处理器执行该计算机可执行指令以实现上述数据刷新的方法。
第四方面，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令在被处理器调用和执行时，计算机可执行指令促使处理器实现上述数据刷新的方法。
本申请的其他特征和优点将在随后的说明书中阐述，或者，部分特征和优点可以从说明书推知或毫无疑义地确定，或者通过实施本申请的上述技术即可得知。
为使本申请的上述目的、特征和优点能更明显易懂，下文特举较佳实施例，并配合所附附图，作详细说明如下。
附图说明
为了更清楚地说明本申请具体实施方式或相关技术中的技术方案，下面将对具体实施方式或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施方式，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种访问CDN网络的情景示意图；
图2为本申请实施例提供的一种内容分发网络的架构示意图；
图3为本申请实施例提供的一种数据刷新的方法的流程示意图；
图4为本申请实施例提供的另一种数据刷新的方法的流程示意图；
图5为本申请实施例提供的一种CDN节点刷新的流程示意图；
图6为本申请实施例提供的一种数据刷新的装置的结构示意图；
图7为本申请实施例提供的一种电子设备的结构示意图。
附图标记说明：
61-刷新请求接收模块；62-判断模块；63-刷新模块；71-处理器；72-存储器；73-总线；74-通信接口。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
对于普通的Internet(互联网)用户，每个CDN节点就相当于一个放置在它周围的网站服务器，通过DNS(Domain Name System，域名系统)的接管，用户的请求被透明地指向离它最近的节点，节点中CDN服务器会像网站的原始服务器一样，响应用户的请求，由于它离用户更近，因而响应时间必然更快。其中，智能调度DNS是CDN服务中的关键系统，当用户访问加入CDN服务的网站时，域名解析请求将最终由智能调度DNS负责处理，它通过一组预先定义好的策略，将当时最接近用户的节点地址提供给用户，使用户可以得到快速的服务。同时，智能调度DNS还需要与分布在各地的CDN节点保持通信，跟踪各节点的健康状态、容量等，确保将用户的请求分配到就近可用的节点上。
如图1所示，其为一种访问CDN网络的情景示意图，其中，用户client访问CDN网络时，其与域名系统DNS以及CDN网络中的边缘节点的交互为必经流程，边缘节点、中层节点、上层节点和源站之间的交互为可选流程，其中，如果在边缘节点中命中缓存，则此次访问不涉及边缘节点与其他节点之间的交互(即不会经过图1中虚线部分的流程)。
参见图2，所示为一种内容分发网络的架构示意图，其中，该CDN节点中包括多个缓存cache和多个代理服务器nginx，每个nginx均与Linux虚拟服务器(Linux Virtual Server，LVS)通信连接，在实际操作中，用户的访问请求通过LVS发送到各个代理服务器nginx，并由代理服务器nginx提供负载均衡服务，将访问请求分发到缓存cache中，以响应访问请求。
在实际操作中，当用户访问CDN网络时，边缘节点直接服务于用户(网民)，个数也最多；中层节点主要是汇聚边缘节点的回源请求，不直接服务于网民，个数较少；上层节点主要是汇聚中层节点回源请求，不直接服务于网民，个数相对最少。并且，通常用户不需要为中层/上层节点产生的带宽付费。
考虑到现有的CDN节点刷新方式，会导致很多无效的刷新请求，增加了CDN节点的缓存压力的问题，本申请实施例提供一种数据刷新的方法、装置及电子设备，该技术可以应用于数据刷新、尤其是CDN网络中的节点刷新场景中。为便于对本实施例进行理解，首先对本申请实施例所公开的一种数据刷新的方法进行详细介绍。
参见图3，其为本申请实施例提供的一种数据刷新的方法的流程示意图，其中，该方法应用于节点服务器，由图3可见，该方法包括下述步骤：
步骤S302：接收针对目标数据的刷新请求。
上述目标数据可以是视频、图片、文档等等，并且，对目标数据的刷新可以包括新增数据、删除数据和修改数据中的至少一种。上述节点服务器可以是CDN网络中的边缘节点服务器，其直接接收用户对目标数据的刷新请求，并设置为将刷新请求转发至节点内的缓存设备，以由缓存设备根据刷新请求对数据进行刷新操作。
步骤S304：确定本地缓存是否存储有该目标数据，如果存储有该目标数据，则执行步骤S306；如果没有存储该目标数据，则执行步骤S308。
节点服务器在接收到刷新请求后，首先确定本地缓存中是否存储有该目标数据，如果存储有该目标数据，则根据该刷新请求刷新该目标数据；如果没有存储该目标数据，则直接返回刷新成功，而无需将刷新请求转发到节点内的缓存设备。
通常，每个CDN节点内部会包含多台缓存设备，但是对于一个具体的资源，例如视频、图片等，只会缓存在其中一台或多台缓存设备上，而客户本身并不知道该资源缓存在哪台缓存设备，因此，为了保证刷新成功，传统的刷新方式是将针对该资源的刷新请求打到节点内的所有缓存设备，因而会导致将刷新请求无效放大多倍。而在本实施例中，节点服务器预先判断本地缓存中是否存储有待刷新的目标数据，如果本地缓存中没有该待刷新的目标数据，则不必要将刷新请求转发至节点内的缓存设备，因而免去无效的刷新，实现将有效的刷新请求透传给缓存设备。
步骤S306：根据该刷新请求刷新该目标数据。
如果节点服务器确认本地缓存中存储有该目标数据，则放行该刷新请求，将该刷新请求透传给缓存设备，缓存设备根据刷新请求进行数据刷新操作。
步骤S308：返回刷新成功。
如果节点服务器确认本地缓存中没有存储该目标数据，表明该刷新请求是“无效”的请求，也即，即使将刷新请求发送到各个缓存设备，实际并不会产生数据更新，因而是不必要的刷新操作。在本实施例中，若本地缓存中没有存储该目标数据，则直接返回刷新成功。因此，这种方式节约了将刷新请求发送至各个缓存设备的操作，各个缓存设备也无需根据该刷新请求进行“无效”的刷新。
本申请实施例提供的一种数据刷新的方法，在接收到针对目标数据的刷新请求时，首先确定本地缓存是否存储有该目标数据，如果本地缓存中存储有该目标数据，则根据该刷新请求刷新该目标数据，如果本地缓存中存储没有该目标数据，则直接返回刷新成功。该方式由节点服务器预先对刷新请求进行过滤，只将本地缓存中存在的数据的刷新信息传递给缓存设备，以进行刷新，从而过滤掉了无效的刷新请求，降低了CDN节点的缓存压力，提高了刷新效率和刷新成功率。
在图1所示数据刷新的方法的基础上，本实施例针对上述实施例中步骤S304(确定本地缓存是否存储有该目标数据)的实现方式进行了说明，以促进对该方案更深入地理解。
如图4所示，其为另一种数据刷新的方法的流程示意图，该方法应用于节点服务器，由图4可见，该方法包括下述步骤：
步骤S402：接收针对目标数据的刷新请求。
步骤S404：获取本地缓存中缓存数据的索引目录。
在其中一种可能的实施方式中，可以在该节点服务器上设置刷新代理服务，当节点服务器监测到该刷新代理服务启动时，建立本地缓存对应的缓存服务与该刷新代理服务之间的通信连接。在其他可能的实施方式中，还可以设置该刷新代理服务开机启动。
其中，上述缓存服务还设置为生成本地缓存数据的索引目录，这样，刷新代理服务可以从该缓存服务获取缓存数据的索引目录，进而根据该索引目录确定本地缓存中是否有目标数据。在实际操作中，在缓存服务与该刷新代理服务建立通信连接之后，可以以心跳的方式将本地缓存中缓存数据的索引目录实时同步到该刷新代理服务，从而，该刷新代理服务可以知道缓存设备中的最新的缓存数据的情况。
步骤S406：从该索引目录中查找该目标数据的索引。
例如，可以通过上述刷新代理服务根据获取到的索引目录进行查找，确定该索引目录中是否有目标数据的索引。
步骤S408：根据该目标数据的索引查找结果，确定本地缓存是否存储有该目标数据，如果存储有该目标数据，则执行步骤S410；如果没有存储该目标数据，则执行步骤S412。
如果在索引目录中查找到目标数据的索引，表明本地缓存中存储有目标数据，从而根据该刷新请求刷新该目标数据，在一种可能的实施方式中，放行该刷新请求，将其发送至缓存设备，以使缓存设备根据该刷新请求刷新目标数据。
如果在索引目录中没有查找到目标数据的索引，表明本地缓存中没有存储该目标数据，此时，拦截该刷新请求，不将其发送至缓存设备，而直接返回刷新成功。在其他可能的实施方式中，也可以向用户返回提示，表明本地缓存中没有存储该目标数据。
步骤S410：根据该刷新请求刷新该目标数据。
步骤S412：返回刷新成功。
这里，上述步骤S410和步骤S412，对应步骤S306至步骤S308，相应内容的描述可以参考对应部分，在此不再赘述。
为了更清楚理解本实施例提供的数据刷新的方法，这里介绍一个应用实例。参见图5，其为本申请实施例提供的一种CDN节点刷新的流程示意图，在图5示出的实施方式中，展示了用上述实施例中数据刷新的方法对CDN节点进行刷新的过程，其中，在该CDN节点上运行有刷新代理服务(refreshd)，其刷新过程如下：
首先，客户通过控制台或者API(Application Programming Interface，应用程序接口)提交刷新请求到刷新中央，刷新中央再将刷新请求分发到CDN节点的relay(中继)机上的agent(代理)，在本实施例中，agent由原先直接请求缓存设备(cache)转变为与刷新代理服务(refreshd)进行通信。
其中，刷新代理服务启动时主动连接缓存设备cache，从缓存设备cache请求获得所有目录信息，建立本地的目录结构，之后再以心跳方式和缓存设备的缓存服务保持这个长连接。这里，缓存设备正常服务时，新增或删除的缓存文件，通过长连接实时同步给刷新代理服务，该刷新代理服务维护一份缓存设备中的内容目录，二者保持一致。
然后，当刷新请求到刷新代理服务时，该刷新代理服务根据缓存数据的目录信息对该刷新请求进行过滤，如果请求刷新的目标资源存在本地缓存内，则说明需要处理这个刷新，从而将这个刷新请求传给缓存设备，并等待刷新成功再返回给客户。
这样，在该CDN节点中，由于通过刷新代理服务对客户的刷新请求进行了过滤，仅仅把本地缓存存在的数据的刷新信息透传给缓存服务程序，从而降低了节点刷新压力，同时也提高了刷新效率。
在实际应用中，例如在电商大型促销活动期间，产品活动详情页的图片需要实时更新，估算单机需要支持处理20k QPS(Queries-per-second，每秒查询率)的刷新请求，而如此高 频率的刷新请求会给节点内缓存设备造成巨大压力，影响正常网民访问，通过本实施例提供的上述数据刷新的方法，可以实现刷新本地缓存中存在的资源，解决无效放大的问题，大大提高刷新效率和刷新成功率，缓解上述问题。并且，由于在节点服务器中设置刷新代理服务，并将对刷新请求进行过滤的需求从缓存服务剥离到该刷新代理服务，从而可以进一步还原缓存服务的基础存储功能。
对应于图1中所示的数据刷新的方法，本申请实施例还提供了一种数据刷新的装置，如图6所示，其为一种数据刷新的装置的结构示意图，该装置应用于节点服务器。由图6可见，该装置包括依次连接的刷新请求接收模块61、判断模块62和刷新模块63，其中，各个模块的功能如下：
刷新请求接收模块61，设置为接收针对目标数据的刷新请求；
判断模块62，设置为确定本地缓存是否存储有该目标数据；
刷新模块63，设置为如果本地缓存存储有该目标数据，根据该刷新请求刷新该目标数据。
在其中一种可能的实施方式中，上述判断模块62还设置为：获取本地缓存中缓存数据的索引目录；从该索引目录中查找该目标数据的索引；以及根据该目标数据的索引查找结果，确定本地缓存是否存储有该目标数据。
在另一种可能的实施方式中，上述刷新模块63还设置为：如果确定本地缓存没有存储该目标数据，返回刷新成功。
在另一种可能的实施方式中，上述判断模块62还设置为：通过预设的刷新代理服务和本地缓存对应的缓存服务，获取本地缓存中缓存数据的索引目录；其中，该刷新代理服务运行在该节点服务器上，且该刷新代理服务与该缓存服务通信连接，该缓存服务设置为生成该缓存数据的索引目录。
在另一种可能的实施方式中，上述判断模块62还设置为：当监测到该刷新代理服务启动时，建立该缓存服务与该刷新代理服务之间的通信连接；以及通过该缓存服务，以心跳的方式将本地缓存中缓存数据的索引目录同步到该刷新代理服务。
本申请实施例提供的数据刷新的装置，其实现原理及产生的技术效果和前述数据刷新的方法实施例相同，为简要描述，数据刷新的装置的实施例部分未提及之处，可参考前述数据刷新的方法实施例中相应内容。
本申请实施例还提供了一种电子设备，如图7所示，为该电子设备的结构示意图，其中，该电子设备包括处理器71和存储器72，该存储器72存储有能够被该处理器71执行的机器可执行指令，该处理器71执行该机器可执行指令以实现上述数据刷新的方法。
在图7示出的实施方式中，该电子设备还包括总线73和通信接口74，其中，处理器 71、通信接口74和存储器72通过总线连接。
其中，存储器72可能包含高速随机存取存储器(RAM，Random Access Memory)，也可能还包括非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口74(可以是有线或者无线)实现该系统网元与至少一个其他网元之间的通信连接，可以使用互联网、广域网、本地网、城域网等。总线可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
处理器71可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器71中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器71可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(Digital Signal Processing，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现成可编程门阵列(Field-Programmable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器71读取存储器72中的信息，结合其硬件完成前述实施例的数据刷新的方法的步骤。
本申请实施例还提供了一种机器可读存储介质，该机器可读存储介质存储有机器可执行指令，该机器可执行指令在被处理器调用和执行时，该机器可执行指令促使处理器实现上述数据刷新的方法，实现可参见前述方法实施例，在此不再赘述。
本申请实施例所提供的数据刷新的方法、数据刷新的装置和电子设备的计算机程序产品，包括存储了程序代码的计算机可读存储介质，所述程序代码包括的指令可设置为执行前述方法实施例中所述的数据刷新的方法，实现可参见方法实施例，在此不再赘述。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可执行的非易失的计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM， Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例提供的一种数据刷新的方法、装置、电子设备及计算机可读存储介质，接收针对目标数据的刷新请求；确定本地缓存是否存储有该目标数据；如果本地缓存存储有该目标数据，根据该刷新请求刷新该目标数据。该方式中，由节点服务器预先对刷新请求进行过滤，只将本地缓存中存在的数据的刷新信息传递给缓存设备，以进行刷新，从而过滤掉了无效的刷新请求，降低了CDN节点的缓存压力，提高了刷新效率和刷新成功率。
再者，还通过在节点服务器中设置刷新代理服务，并将对刷新请求进行过滤的需求从缓存服务剥离到该刷新代理服务，从而可以进一步还原缓存服务的基础存储功能。
另外，在本申请实施例的描述中，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。
在本申请的描述中，需要说明的是，术语“中心”、“上”、“下”、“左”、“右”、“竖直”、“水平”、“内”、“外”等指示的方位或位置关系为基于附图所示的方位或位置关系，仅是为了便于描述本申请和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本申请的限制。此外，术语“第一”、“第二”、“第三”仅设置为描述目的，而不能理解为指示或暗示相对重要性。
最后应说明的是：以上所述实施例，仅为本申请的具体实施方式，用以说明本申请的技术方案，而非对其限制，本申请的保护范围并不局限于此，尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，其依然可以对前述实施例所记载的技术方案进行修改或可轻易想到变化，或者对其中部分技术特征进行等同替换；而这些修改、变化或者替换，并不使相应技术方案的本质脱离本申请实施例技术方案的精神和范围，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。
工业实用性
本申请应用于数据处理技术领域，提供了一种数据刷新的方法、装置、电子设备及计算机可读存储介质，通过节点服务器预先对刷新请求进行过滤，只将本地缓存中存在的数据的刷新信息传递给缓存设备，以进行刷新，从而过滤掉了无效的刷新请求，降低了CDN节点的缓存压力，提高了刷新效率和刷新成功率。

Claims (10)

  1. 一种数据刷新的方法，应用于节点服务器，所述方法包括：
    接收针对目标数据的刷新请求；
    确定本地缓存是否存储有所述目标数据；以及
    如果所述本地缓存存储有所述目标数据，根据所述刷新请求刷新所述目标数据。
  2. 根据权利要求1所述的数据刷新的方法，其中，所述确定本地缓存是否存储有所述目标数据的步骤，包括：
    获取本地缓存中缓存数据的索引目录；
    从所述索引目录中查找所述目标数据的索引；以及
    根据所述目标数据的索引查找结果，确定本地缓存是否存储有所述目标数据。
  3. 根据权利要求2所述的数据刷新的方法，其中，所述获取本地缓存中缓存数据的索引目录的步骤，包括：
    通过预设的刷新代理服务和本地缓存对应的缓存服务，获取本地缓存中缓存数据的索引目录；
    其中，所述刷新代理服务运行在所述节点服务器上，且所述刷新代理服务与所述缓存服务通信连接，所述缓存服务设置为生成所述缓存数据的索引目录。
  4. 根据权利要求3所述的数据刷新的方法，其中，所述通过预设的刷新代理服务和本地缓存对应的缓存服务，获取本地缓存中缓存数据的索引目录的步骤，包括：
    当监测到所述刷新代理服务启动时，建立所述缓存服务与所述刷新代理服务之间的通信连接；以及
    通过所述缓存服务，以心跳的方式将本地缓存中缓存数据的索引目录同步到所述刷新代理服务。
  5. 根据权利要求1至4中任一项所述的数据刷新的方法，其中，所述方法还包括：
    如果所述本地缓存没有存储所述目标数据，返回刷新成功。
  6. 一种数据刷新的装置，应用于节点服务器，所述装置包括：
    刷新请求接收模块，设置为接收针对目标数据的刷新请求；
    判断模块，设置为确定本地缓存是否存储有所述目标数据；以及
    刷新模块，设置为如果本地缓存存储有所述目标数据，根据所述刷新请求刷新所述目标数据。
  7. 根据权利要求6所述的数据刷新的装置，其中，所述判断模块还设置为：
    获取本地缓存中缓存数据的索引目录；
    从所述索引目录中查找所述目标数据的索引；以及
    根据所述目标数据的索引查找结果，确定本地缓存是否存储有所述目标数据。
  8. 根据权利要求6所述的数据刷新的装置，其中，所述刷新模块还设置为：
    如果确定本地缓存没有存储所述目标数据，返回刷新成功。
  9. 一种电子设备，包括处理器和存储器，所述存储器存储有能够被所述处理器执行的计算机可执行指令，所述处理器执行所述计算机可执行指令以实现权利要求1至5中任一项所述的数据刷新的方法。
  10. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令在被处理器调用和执行时，计算机可执行指令促使处理器实现权利要求1至5中任一项所述的数据刷新的方法。
PCT/CN2021/123638 2020-12-15 2021-10-13 数据刷新的方法、装置、电子设备及计算机可读存储介质 WO2022127319A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011490332.4A CN112463653B (zh) 2020-12-15 2020-12-15 数据刷新的方法、装置及电子设备
CN202011490332.4 2020-12-15

Publications (1)

Publication Number Publication Date
WO2022127319A1 true WO2022127319A1 (zh) 2022-06-23

Family

ID=74802985

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/123638 WO2022127319A1 (zh) 2020-12-15 2021-10-13 数据刷新的方法、装置、电子设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN112463653B (zh)
WO (1) WO2022127319A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112463653B (zh) * 2020-12-15 2024-07-23 北京金山云网络技术有限公司 数据刷新的方法、装置及电子设备
CN113271359A (zh) * 2021-05-19 2021-08-17 北京百度网讯科技有限公司 刷新缓存数据的方法、装置、电子设备和存储介质
CN113709232B (zh) * 2021-08-24 2024-05-17 广州文远知行科技有限公司 数据包加载方法、客户端、客户端代理、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110060881A1 (en) * 2009-09-10 2011-03-10 Red Hat, Inc. Asynchronous Cache Refresh for Systems with a Heavy Load
CN105847395A (zh) * 2016-04-25 2016-08-10 乐视控股（北京）有限公司 一种缓存文件处理方法及设备
CN108173952A (zh) * 2017-12-29 2018-06-15 北京奇虎科技有限公司 一种内容分发网络cdn的数据访问方法和装置
CN111385316A (zh) * 2018-12-27 2020-07-07 阿里巴巴集团控股有限公司 资源刷新方法、访问方法及装置
CN112463653A (zh) * 2020-12-15 2021-03-09 北京金山云网络技术有限公司 数据刷新的方法、装置及电子设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1221898C (zh) * 2002-08-13 2005-10-05 国际商业机器公司 刷新网络代理高速缓存服务器对象的系统和方法
CN101472166B (zh) * 2007-12-26 2011-11-16 华为技术有限公司 一种内容缓存、查询方法及点对点媒体传输系统
CN106202112B (zh) * 2015-05-06 2019-07-02 阿里巴巴集团控股有限公司 缓存目录刷新方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110060881A1 (en) * 2009-09-10 2011-03-10 Red Hat, Inc. Asynchronous Cache Refresh for Systems with a Heavy Load
CN105847395A (zh) * 2016-04-25 2016-08-10 乐视控股（北京）有限公司 一种缓存文件处理方法及设备
CN108173952A (zh) * 2017-12-29 2018-06-15 北京奇虎科技有限公司 一种内容分发网络cdn的数据访问方法和装置
CN111385316A (zh) * 2018-12-27 2020-07-07 阿里巴巴集团控股有限公司 资源刷新方法、访问方法及装置
CN112463653A (zh) * 2020-12-15 2021-03-09 北京金山云网络技术有限公司 数据刷新的方法、装置及电子设备

Also Published As

Publication number Publication date
CN112463653A (zh) 2021-03-09
CN112463653B (zh) 2024-07-23

Similar Documents

Publication Publication Date Title
WO2022127319A1 (zh) 数据刷新的方法、装置、电子设备及计算机可读存储介质
WO2018184491A1 (zh) 资源获取方法、装置及系统
WO2018108033A1 (zh) 一种数据库迁移方法、装置、终端、系统及存储介质
WO2022068333A1 (zh) 访问请求的处理方法、装置、电子设备及计算机可读存储介质
WO2019165665A1 (zh) 一种域名解析方法、服务器及系统
WO2013078875A1 (zh) 内容的管理方法的方法、装置和系统
WO2017045538A1 (zh) 基于http协议的缓存、请求、响应方法及相应装置
WO2017080459A1 (zh) 服务内容的缓存及提供方法、装置、系统和存储介质
WO2021093763A1 (zh) 一种数据缓存方法和装置
WO2021007752A1 (zh) 内容分发网络中的回源方法及相关装置
WO2011103784A1 (zh) 一种数据操作方法和数据操作设备
US20120185950A1 (en) Method, access node, and system for obtaining data
CN109067936A (zh) 一种域名解析的方法及装置
US9686724B2 (en) Network storage method, switch device, and controller
US11750716B2 (en) Methods for publishing resource, and gateway
US20150006622A1 (en) Web contents transmission method and apparatus
WO2017107795A1 (zh) 一种网站访问加速方法及装置
WO2024198825A1 (zh) 基于全球加速网络的数据传输系统、方法及存储介质
WO2013083085A1 (zh) 数据获取方法及装置
WO2010031297A1 (zh) 一种wap网关提取业务的实现方法和系统
WO2015085794A1 (en) Data transmission method, related apparatus, and communications system
WO2020098773A1 (zh) 一种请求响应方法、装置、边缘节点和鉴权系统
WO2017092356A1 (zh) 用于提供服务数据的服务器、方法及系统
JPH1155327A (ja) 代理サーバの接続制御サーバ，代理サーバ，及びネットワーク制御方法
KR20150011087A (ko) 컨텐츠 전송 서비스를 위한 분산 캐싱 관리 방법 및 이를 위한 중앙 관리 장치

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: 21905248

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: 21905248

Country of ref document: EP

Kind code of ref document: A1