Method, device and storage medium for returning to the source of CDN edge nodes

Abstract

The present disclosure provides a method, device and storage medium for returning to the source of edge nodes of a CDN. A method for returning to the source of edge nodes of a content distribution network CDN is provided, the method comprising: in the case where the edge node initiating the request is not hit: triggering a return-to-source path selector in the edge node initiating the request to read a blockchain account book, wherein the blockchain account book stores multiple records, each record is information associated with the historical return to the source of each edge node in the CDN, including the address of the edge node initiating the return to the source, the address of the regional node storing the file, the return to the source file name and the return to the source time; selecting a regional node that may store the requested file based on the information from the blockchain account book; returning to the selected regional node to obtain the requested file.

Description

Technical Field

[0001] The present disclosure relates to the field of data communication, and in particular to a method, device and storage medium for returning to the source of edge nodes of a CDN (Content Delivery Network). Background Art

[0002] CDN systems usually adopt a three-level cache architecture, with cache nodes including center, region, and edge. Among them, edge nodes are closest to users, followed by regional nodes, and the farthest from users are center nodes. When a terminal request for a resource does not hit an edge node, a back-to-source occurs. The existing back-to-source path allocation method is usually that the central scheduler screens the back-to-source list after receiving the edge back-to-source request, and randomly selects healthy regional nodes close to the edge from the regional cluster nodes for service.

[0003] The existing method of allocating back-to-source paths is to adopt a centralized scheduling method. Edge back-to-source always has to go through the central scheduler, which selects regional nodes for service based on distance and health. The edge cannot directly select the upper cache node that stores the back-to-source resources. It is difficult to hit the back-to-source in one go, and the back-to-source process is complicated and time-consuming. In addition, the health of the central scheduler will directly affect the back-to-source performance of the CDN. When the back-to-source volume is too large and the central scheduler is under too much processing pressure, it cannot guarantee a quick response to the back-to-source request, resulting in a poor user experience. Summary of the invention

[0004] According to a first aspect of the present disclosure, a method for tracing back to the source of an edge node of a content delivery network (CDN) is provided, the method comprising: in a case where the edge node initiating a request is not hit: triggering a tracing back to the source path selector in the edge node initiating the request to read a blockchain ledger, wherein the blockchain ledger stores a plurality of records, each record being information associated with a historical tracing back to the source of each edge node in the CDN, including an address of the edge node initiating the tracing back to the source, an address of a regional node storing a file, a tracing back to the source file name, and a tracing back to the source time; selecting a regional node that may store the requested file based on the information from the blockchain ledger; tracing back to the selected regional node to obtain the requested file.

[0005] According to a second aspect of the present disclosure, there is provided a device for traversing the edge nodes of a content delivery network (CDN), the device comprising: a traversal path selector, the traversal path selector being configured to, in the case where the edge node initiating the request is not hit: read a blockchain ledger, wherein the blockchain ledger stores a plurality of records, each record being information associated with a historical traversal of each edge node in the CDN, including an address of the edge node initiating the traversal, an address of a regional node storing a file, a traversal file name and a traversal time, and selecting a regional node that may store the requested file based on the information from the blockchain ledger; wherein the device is configured to traverse the selected regional node to obtain the requested file.

[0006] According to a third aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a program is stored, characterized in that when the program is executed by a computer, the computer is caused to execute the method according to the first aspect of the present disclosure.

[0007] According to a fourth aspect of the present disclosure, a device for returning to the source of an edge node of a content delivery network CDN is provided, comprising a memory and a processor, wherein the memory is communicatively coupled to the processor, and a program is stored in the memory, and when the program is executed by the processor, the processor executes the method described in the first aspect of the present disclosure.

[0008] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the method according to the first aspect of the present disclosure is implemented.

[0009] Other features and advantages of the present invention will become more apparent from the following detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0011] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0012] Figure 1 is a schematic diagram of a CDN system architecture according to an embodiment of the present disclosure;

[0013] Figure 2 is a flowchart of a method for returning to the source of an edge node of a CDN according to an embodiment of the present disclosure;

[0014] Figure 3is a flowchart of a method for returning to the source of an edge node of a CDN according to an embodiment of the present disclosure;

[0015] Figure 4 An exemplary configuration of a computing device capable of implementing an embodiment according to the present disclosure is shown.

[0016] For ease of understanding, the positions, sizes, and ranges of various structures shown in the drawings and the like sometimes do not represent actual positions, sizes, and ranges, etc. Therefore, the disclosure is not limited to the positions, sizes, and ranges, etc. disclosed in the drawings and the like. In addition, the drawings are not necessarily drawn to scale, and some features may be exaggerated to show details of specific components. DETAILED DESCRIPTION

[0017] Various exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0018] The following description of at least one exemplary embodiment is in fact merely illustrative and is in no way intended to limit the present disclosure and its application or use. That is, the structures and methods herein are shown in an exemplary manner to illustrate different embodiments of the structures and methods in the present disclosure. However, those skilled in the art will appreciate that they merely illustrate exemplary ways of the present disclosure that can be implemented, rather than exhaustive ways. In addition, the drawings need not be drawn to scale, and some features may be enlarged to illustrate the details of specific components.

[0019] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0020] Figure 1 FIG. 1 is a schematic diagram of a CDN system architecture 100 according to an embodiment of the present disclosure. Figure 1 As shown, the system architecture 100 shows a regional part, an edge part and a blockchain part. The regional part shows regional nodes 210, 220, and 230, but it should be noted that the number of regional nodes that the CDN can include is not limited to this, but can include more regional nodes; the edge part shows edge nodes 110, 120, and 130, but it should be noted that the number of edge nodes that the CDN can include is not limited to this, but can include more edge nodes; the blockchain part shows a blockchain ledger 310, specifically showing blockchain accounts 311, 312, and 313, but it should be noted that the number of accounts that the blockchain can include is not limited to this, but can include more accounts.

[0021] In an embodiment of the present disclosure, the edge node may be deployed with its own return path selector and return information collector. As a non-limiting example, the edge node 110 may be deployed with a return path selector 111 and a return information collector 112. Among them, the return path selector may be configured to select a return path based on the information stored in the blockchain when a return is required, and the return information collector may be configured to create a corresponding blockchain account for the edge node, collect information associated with the return when the edge node returns to the source, and upload the collected information to the blockchain. Each edge node may have a corresponding blockchain account. As a non-limiting example, the edge node 110 may correspond to the blockchain account 311, the edge node 120 may correspond to the blockchain account 312, and the edge node 130 may correspond to the blockchain account 313.

[0022] Figure 2 1 is a flowchart of a method 200 for back-to-origin of an edge node of a CDN according to an embodiment of the present disclosure. The method 200 may be executed at an edge node when the edge node that initiated the request is not hit.

[0023] like Figure 2 As shown, at S21, the back-to-source path selector in the edge node initiating the request may be triggered to read the blockchain ledger. As a non-limiting example, see Figure 1 , when the edge node 110 initiates a back-to-source request, the back-to-source path selector can read the blockchain ledger 310 through the blockchain account 311. The blockchain ledger can store multiple records, each of which is information associated with the historical back-to-source of each edge node in the CDN, including the edge node address that initiates the back-to-source, the regional node address where the file is stored, and the back-to-source file name.

[0024] In an embodiment of the present disclosure, the records stored in the blockchain ledger may be obtained by a back-to-source information collector in an edge node. As a non-limiting example, see Figure 1 The back-to-source information collector 112 of the edge node 110 can be configured to detect the back-to-source between the edge node 110 and the regional node (such as but not limited to the regional nodes 210, 220, 230, etc.), and automatically trigger the blockchain account 311 corresponding to the edge node 110 to record the information associated with the back-to-source when the back-to-source is detected.

[0025] As a non-limiting example, a record stored in a blockchain ledger may take the following form:

[0026]

[0027] Then, at S22, a regional node that may store the requested file may be selected based on information from the blockchain ledger. In an embodiment of the present disclosure, the selected regional node may include selecting: a regional node that has historically stored the requested file according to records in the blockchain ledger, a regional node that is close to the edge node that initiated the request, or a healthy regional node. In the present disclosure, a healthy node may refer to: the server of the node can provide services to the outside normally without downtime; the server's own load is lower than a certain health threshold; and the server's response time to the user's request is lower than a certain health threshold.

[0028] Figure 3 FIG. 3 is a flowchart of a method 300 for returning to the source of an edge node of a CDN according to an embodiment of the present disclosure. In an embodiment of the present disclosure, Figure 2 The selection process performed at S22 may specifically take the following steps: Figure 3 The method 300 shown. Figure 3 As shown, at S31, the blockchain account book can be read. At S32, it can be determined whether there is a record involving the requested file in the information from the blockchain account book. If there is no record involving the requested file, at S33, a healthy regional node can be selected from the default regional node list. If there is a record involving the requested file, at S34, it can be determined whether there is a record involving the requested file whose return to source time has not timed out. If there is a record that the return to source time has not timed out, at S35, the regional node in the record of the closest return to source in time can be selected. If there is no record that the return to source time has not timed out, at S36, the regional node with the shortest topological distance to the edge node that initiated the request involved in the record of the edge node closest to the edge node that initiated the request can be selected. In the present disclosure, timeout can refer to the time when the return to source occurs exceeding the time threshold from the current time. As described above, the records in the blockchain account book include the return to source time, so it can be determined whether it is timed out based on the return to source time. Since the storage capacity of the regional node itself is limited, cache resources will be replaced. Therefore, if the interval with the return time exceeds the time threshold, it is considered that the possibility of the regional node having this resource is very small.

[0029] In this way, the back-to-source path selector first queries the record set that records the last back-to-source information of the file in the blockchain account book according to the back-to-source request of the edge node, and gives priority to the regional back-to-source that is closest to the current time point. The reason is that according to the cache replacement rule, the closer the time is, the greater the probability that the regional cache has this resource. When the back-to-source information in the record set has timed out, the back-to-source information of the edge node that is close to this edge node is selected from the account book record, and the region with the shortest topological distance is selected for back-to-source.

[0030] It should be understood that Figure 2 The selection process performed at S22 is not limited to Figure 3 The method shown in .

[0031] Return to reference Figure 2 After determining the regional node to be selected at S22, at S23, the selected regional node can be returned to obtain the requested file. In this way, the regional node with stored resources can be directly found based on the blockchain; and when the regional node has resources, it can respond directly, and the edge node does not need to return to the central node.

[0032] Figure 4 An exemplary configuration of a computing device 400 capable of implementing embodiments according to the present disclosure is shown.

[0033] The computing device 400 is an example of a hardware device to which the above aspects of the present disclosure can be applied. The computing device 400 can be any machine configured to perform processing and / or computing. The computing device 400 can be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a personal data assistant (PDA), a smart phone, a vehicle-mounted computer, or a combination thereof.

[0034] like Figure 4 As shown, computing device 400 may include one or more components that may be connected or communicated with bus 402 via one or more interfaces. Bus 402 may include, but is not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, etc. Computing device 400 may include, for example, one or more processors 404. One or more processors 404 may be any type of processor, and may include, but is not limited to, one or more general-purpose processors or special-purpose processors (such as special-purpose processing chips). The processor may, for example, be configured to implement the above-mentioned reference Figure 2 and Figure 3 The method described.

[0035] The computing device 400 may also include or be connected to a non-transitory storage device 414, which may be any non-transitory storage device that can implement data storage, and may include, but is not limited to, a disk drive, an optical storage device, a solid-state memory, a floppy disk, a flexible disk, a hard disk, a tape, or any other magnetic medium, a compressed disk, or any other optical medium, a cache memory, and / or any other storage chip or module, and / or any other medium from which a computer can read data, instructions, and / or codes. The computing device 400 may also include a random access memory (RAM) 410 and a read-only memory (ROM) 412. The ROM 412 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 410 may provide volatile data storage and store instructions related to the operation of the computing device 400. The various aspects, embodiments, specific implementations, or features of the foregoing embodiments may be used individually or in any combination. The various aspects of the foregoing embodiments may be implemented by software, hardware, or a combination of hardware and software.

[0036] For example, the foregoing embodiments may be embodied as computer readable code on a computer readable medium. A computer readable medium is any data storage device that can store data that can thereafter be read by a computer system. Examples of computer readable media include read-only memory, random access memory, CD-ROM, DVD, magnetic tape, hard drive, solid state drive, and optical data storage device. The computer readable medium may also be distributed in a network coupled computer system so that the computer readable code is stored and executed in a distributed manner.

[0037] For example, the aforementioned embodiments may be in the form of hardware circuits. The hardware circuits may include any combination of combinational logic circuits, clock storage devices (such as floppy disks, flip-flops, latches, etc.), finite state machines, memories such as static random access memories or embedded dynamic random access memories, custom designed circuits, programmable logic arrays, etc.

[0038] In one embodiment, hardware circuits according to the present disclosure may be implemented by coding and designing one or more integrated circuits using a hardware description language (HDL) such as Verilog or VHDL, or in combination using discrete circuits.

[0039] In summary, according to the first aspect of the present disclosure, a method for tracing back to the source of an edge node of a content delivery network CDN is provided, the method comprising: in a case where the edge node initiating a request is not hit: triggering a tracing back to the source path selector in the edge node initiating the request to read a blockchain ledger, wherein the blockchain ledger stores a plurality of records, each record being information associated with a historical tracing back to the source of each edge node in the CDN, including an address of the edge node initiating the tracing back to the source, an address of a regional node storing a file, a tracing back to the source file name, and a tracing back to the source time; selecting a regional node that may store a requested file based on information from the blockchain ledger; tracing back to the selected regional node to obtain the requested file.

[0040] In an embodiment according to the present disclosure, the selecting includes performing one or more of the following: selecting a regional node that has historically stored the requested file; selecting a regional node that is close to the edge node that initiated the request; and selecting a healthy regional node.

[0041] In an embodiment according to the present disclosure, the selection includes: determining whether there is a record involving the requested file in the information from the blockchain ledger; if there is no record involving the requested file, selecting a healthy regional node from the default regional node list; if there is a record involving the requested file, determining whether there is a record involving the requested file whose return-to-source time has not timed out; if there is a record whose return-to-source time has not timed out, selecting a regional node in the record of the closest return-to-source in time; if there is no record whose return-to-source time has not timed out, selecting a regional node involved in the record of the edge node closest to the edge node that initiated the request and having the shortest topological distance to the edge node that initiated the request.

[0042] In an embodiment according to the present disclosure, the method further includes: utilizing a back-to-source information collector in an edge node to detect back-to-source between the edge node and a regional node, and triggering a blockchain account corresponding to the edge node to record information associated with the back-to-source when the back-to-source is detected.

[0043] According to a second aspect of the present disclosure, there is provided a device for traversing the edge nodes of a content delivery network (CDN), the device comprising: a traversal path selector, the traversal path selector being configured to, in the case where the edge node initiating the request is not hit: read a blockchain ledger, wherein the blockchain ledger stores a plurality of records, each record being information associated with a historical traversal of each edge node in the CDN, including an address of the edge node initiating the traversal, an address of a regional node storing a file, a traversal file name and a traversal time, and selecting a regional node that may store the requested file based on the information from the blockchain ledger; wherein the device is configured to traverse the selected regional node to obtain the requested file.

[0044] In an embodiment according to the present disclosure, the selecting includes performing one or more of the following: selecting a regional node that has historically stored the requested file; selecting a regional node that is close to the edge node that initiated the request; and selecting a healthy regional node.

[0045] In an embodiment according to the present disclosure, the selection includes: determining whether there is a record involving the requested file in the information from the blockchain ledger; if there is no record involving the requested file, selecting a healthy regional node from the default regional node list; if there is a record involving the requested file, determining whether there is a record involving the requested file whose return-to-source time has not timed out; if there is a record whose return-to-source time has not timed out, selecting a regional node in the record of the closest return-to-source in time; if there is no record whose return-to-source time has not timed out, selecting a regional node involved in the record of the edge node closest to the edge node that initiated the request and having the shortest topological distance to the edge node that initiated the request.

[0046] In an embodiment according to the present disclosure, the device also includes a back-to-source information collector, which is configured to detect back-to-source between the edge node and the regional node, and trigger the blockchain account corresponding to the edge node to record information associated with the back-to-source when the back-to-source is detected.

[0047] According to a third aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a program is stored, characterized in that when the program is executed by a computer, the computer is caused to execute the method according to the first aspect of the present disclosure.

[0048] According to a fourth aspect of the present disclosure, a device for returning to the source of an edge node of a content delivery network CDN is provided, comprising a memory and a processor, wherein the memory is communicatively coupled to the processor, and a program is stored in the memory, and when the program is executed by the processor, the processor executes the method described in the first aspect of the present disclosure.

[0049] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the method according to the first aspect of the present disclosure is implemented.

[0050] The present disclosure proposes a blockchain-based CDN node return-to-source method, provides a return-to-source information collector and a return-to-source path selector, and thus provides a decentralized and efficient return-to-source path allocation method. After detecting that a return-to-source occurs between an edge node and a regional node, the return-to-source information collector triggers the blockchain account corresponding to the edge node to record the return-to-source related information, so that the return-to-source paths generated by each edge node can be saved on the blockchain; when a return-to-source occurs next time on an edge node, the return-to-source path selector is triggered to read the blockchain ledger, and the corresponding regional address where this resource is retained is searched. If it exists, the edge node directly returns the user request to this region. The method and device proposed in the present disclosure simplify the return-to-source path selection process, and the edge request can be directly dispatched to the regional node where the return-to-source resource is stored, and the optimal return-to-source path allocation is performed efficiently and quickly, and the decentralized return-to-source scheduling ensures the timeliness and reliability of the CDN system.

[0051] The advantages of the method and device disclosed in the present invention include: adopting a decentralized return-to-source method to avoid the performance bottleneck problem of centralized scheduling nodes, and without going through the upper-level scheduling nodes, the edge node can directly return to the regional node where the resources are stored, thereby shortening the return-to-source delay and improving the overall service quality of IPTV CDN; introducing blockchain technology to record the historical return-to-source information of each edge node, and the next time the edge returns to the source, the regional node that most recently provided this resource can be obtained through the account book, thereby ensuring that the edge return to the source hits the region once as much as possible, shortening the return-to-source path; and the blockchain's anti-tampering technology ensures the reliability of the CDN return-to-source record, greatly reducing the return-to-source failure rate when the CDN is attacked.

[0052] Although some specific embodiments of the present invention have been shown in detail by example, it will be appreciated by those skilled in the art that the above examples are intended to be illustrative only and do not limit the scope of the present invention. It should be appreciated that some steps in the aforementioned method are not necessarily performed in the order shown in the figure, but they can be performed simultaneously, in different orders or in an overlapping manner. In addition, those skilled in the art can add some steps or omit some steps as needed. Some components in the aforementioned system are not necessarily arranged according to the figure, and those skilled in the art can add some components or omit some components as needed. It will be appreciated by those skilled in the art that the above embodiments can be modified without departing from the scope and essence of the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A method for returning to the source of an edge node of a content delivery network (CDN), the method comprising: when the edge node that initiates the request does not hit: The back-to-source path selector in the edge node initiating the request is triggered to read the blockchain ledger, wherein: The blockchain account book stores multiple records, each of which is information associated with the historical back-to-source of each edge node in the CDN, including the edge node address that initiated the back-to-source, the regional node address where the file is stored, the back-to-source file name, and the back-to-source time; Selecting a regional node that may store the requested file based on information from the blockchain ledger; Go back to the selected regional node to obtain the requested file, The options include: Determining whether there is a record related to the requested file in the information from the blockchain ledger; If no record exists for the requested file, a healthy zone node is selected from the default zone node list. If there is a record involving the requested file, determine whether there is a record involving the requested file whose return-to-source time has not timed out; If there is a record whose return to the source has not timed out, select the regional node in the record with the most recent return to the source. If there is no record of the return-to-source time not being exceeded, then a regional node with the shortest topological distance to the edge node initiating the request and involved in the record of the edge node closest to the edge node initiating the request is selected.

2. The method according to claim 1, wherein: The selection includes performing one or more of the following: Select the regional node that has historically stored the requested file; Select a regional node that is close to the edge node that initiates the request; as well as Select healthy regional nodes, where the healthy regional nodes refer to regional nodes whose servers can provide services normally without downtime and whose server load is lower than the load threshold; And the server's response time to the user's request is lower than the time threshold.

3. The method according to claim 1, wherein: The method further comprises: The back-to-source information collector in the edge node is used to detect the back-to-source between the edge node and the regional node, and when the back-to-source is detected, the blockchain account corresponding to the edge node is triggered to record information associated with the back-to-source.

4. A device for returning to the source of an edge node of a content delivery network (CDN), the device comprising: A back-to-source path selector, wherein the back-to-source path selector is configured to: Read the blockchain ledger, where The blockchain account book stores multiple records, each of which is information associated with the historical back-to-source of each edge node in the CDN, including the edge node address that initiated the back-to-source, the regional node address where the file is stored, the back-to-source file name and the back-to-source time, as well as Selecting a regional node that may store the requested file based on information from the blockchain ledger; wherein the device is configured to go back to the selected regional node to obtain the requested file, The options include: Determining whether there is a record related to the requested file in the information from the blockchain ledger; If no record exists for the requested file, a healthy zone node is selected from the default zone node list. If there is a record involving the requested file, determine whether there is a record involving the requested file whose return-to-source time has not timed out; If there is a record whose return to the source has not timed out, select the regional node in the record with the most recent return to the source. If there is no record of the return-to-source time not being exceeded, then a regional node with the shortest topological distance to the edge node initiating the request and involved in the record of the edge node closest to the edge node initiating the request is selected.

5. The device according to claim 4, wherein: The selection includes performing one or more of the following: Select the regional node that has historically stored the requested file; Select a regional node that is close to the edge node that initiates the request; as well as Select healthy regional nodes, where the healthy regional nodes refer to regional nodes whose servers can provide services normally without downtime and whose server load is lower than the load threshold; And the server's response time to the user's request is lower than the time threshold.

6. The device according to claim 4, wherein: The device also includes a back-to-source information collector, which is configured to detect back-to-source between the edge node and the regional node, and trigger the blockchain account corresponding to the edge node to record information associated with the back-to-source when the back-to-source is detected.

7. A non-transitory computer-readable storage medium having a program stored thereon, characterized in that: When the program is executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 3.

8. A device for returning to the source of an edge node of a content distribution network (CDN), comprising a memory and a processor, wherein the memory is communicatively coupled to the processor, and a program is stored in the memory, and when the program is executed by the processor, the processor executes the method according to any one of claims 1 to 3.

9. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 3 is implemented.

Images