CDN access method, device, computer equipment and readable storage medium

Abstract

The present invention provides a CDN access method, device, computer equipment and readable storage medium, which relate to the field of communication technology. The access method is applied to a CDN connector, and the CDN connector is respectively connected to multiple CDN source stations and multiple virtual content distribution network vCDN nodes. The access method includes: receiving request information from a user. Determine a first vCDN node among multiple vCDN nodes. Forward the request information to the first vCDN node. And, obtain the content corresponding to the request information from the first vCDN node or the first CDN source station, and return the content corresponding to the request information to the user. The present invention can realize fast user access to CDN by configuring a CDN connector on the MEC platform, and can also support multi-CDN application scenarios.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a CDN access method, device, computer equipment, and readable storage medium. Background Art

[0002] Currently, internet companies' content delivery networks (CDNs) can only be deployed in the Internet Data Center (IDC) computer rooms provided by operators. This means that CDN nodes are only physically close to end users, not network-close. For example, they cannot be deployed in operator-side computer rooms behind residential communities or base stations. With the development of the internet, mainstream CDN vendors have clearly identified edge computing (MEC) as the evolutionary direction of CDN. This is because emerging services such as 4K (resolution of 3840×2160 pixels) / 8K (resolution of 7680×4320 pixels) video and virtual reality (VR) / augmented reality (AR) technologies require CDN nodes to have not only storage and distribution capabilities but also computing power.

[0003] In order to support edge computing, the fifth generation mobile communication technology (5G) network can adopt a distributed gateway architecture. The 5G core network (5G Core, 5GC) allows the user plane gateway UPF (User Profile Function) to be independently deployed to the edge of the mobile network, as well as multiple UPF cascades. At the same time, the storage, distribution and computing capabilities of the MEC platform enable the method of deploying CDN based on MEC to have both network conditions and infrastructure conditions. Among the current CDN deployment modes based on MEC in the industry, there is a deployment mode called shared CDN deployment mode, which refers to deploying cache applications on MEC to transparently cache and regenerate hot content. Users share CDN nodes deployed in the fixed network.

[0004] like Figure 1As shown in the figure, in the deployment mode of shared CDN, the 5G network is generally used to configure a whitelist for the edge UPF (eUPF) through the core network PCF (Policy Control Function) network element. The whitelist contains the domain names and / or IP addresses of the business applications supported by the shared CDN. If the eUPF finds through analysis that the access domain name / IP address of the user data packet is on the whitelist, it will forward the data packet directly to the shared CDN. The deployment mode of shared CDN is just to deploy the cache application to MEC, rather than deploying the CDN node itself to MEC. If the cache fails (for example, the user's first visit, or the cached content is replaced by new content), the user can only directly access the original CDN node (that is, the CDN node where the content comes from), which requires the eUPF to be able to connect to Figure 1 On the shared CDN node shown in .

[0005] It can be seen that in the shared CDN deployment model, when the cache fails, users can only directly access the original CDN node, which cannot solve the problem that the user is still "physically close" to the CDN node rather than "network close". Summary of the Invention

[0006] The technical problem to be solved by the present invention is that in the existing technology, when the cache of the shared CDN deployment model fails, users can only directly access the original CDN node, which cannot solve the problem of "close physical distance".

[0007] In view of the above-mentioned deficiencies in the prior art, the following solutions are provided:

[0008] In a first aspect, the present invention provides an access method for a content distribution network CDN, which is applied to a CDN connector, wherein the CDN connector is respectively connected to multiple CDN source stations and multiple virtual content distribution network (virtual CDN, vCDN) nodes, and the access method includes: receiving request information from a user. Determine a first vCDN node among multiple vCDN nodes. Forward the request information to the first vCDN node. And, obtain the content corresponding to the request information from the first vCDN node or the first CDN source station, and return the content corresponding to the request information to the user. The first vCDN node is a vCDN node corresponding to the first CDN source station, and the first vCDN node is on the mobile edge computing MEC platform where the CDN connector is located. The first CDN source station is a CDN source station corresponding to the request information among multiple CDN source stations.

[0009] Specifically, the request information includes the address information of the CDN connector; the address information of the CDN connector is obtained by querying the Domain Name System (DNS).

[0010] Specifically, determining a first vCDN node from among multiple vCDN nodes includes: determining an MEC platform where the CDN connector is located based on address information of the CDN connector; determining a CDN origin site corresponding to the request information based on a local DNS record on the MEC platform where the CDN connector is located, and using the CDN origin site as the first CDN origin site; and determining a first vCDN node corresponding to the first CDN origin site based on a pre-set correspondence between CDN origin sites and vCDN nodes.

[0011] Specifically, receiving the request information from the user includes: receiving the request information from the user forwarded by the base station via the edge user plane gateway. The edge user plane gateway is configured with address information of the CDN connector.

[0012] Specifically, returning the content corresponding to the request information to the user includes: returning the content corresponding to the request information to the base station via the edge user plane gateway, so that the base station forwards the content corresponding to the request information to the user.

[0013] Specifically, obtaining the content corresponding to the request information from the first vCDN node or the first CDN origin includes: determining whether the content corresponding to the request information is cached in the first vCDN node, and if so, obtaining the content corresponding to the request information cached in the first vCDN node.

[0014] Specifically, it also includes: if the content corresponding to the request information is not cached in the first vCDN node, receiving a back-to-source request from the first vCDN node, and forwarding the back-to-source request to the first CDN source station to obtain the content corresponding to the request information from the first CDN source station.

[0015] Specifically, the method further includes: forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.

[0016] In a second aspect, the present invention provides an access device for a content distribution network CDN, comprising a CDN connector, wherein the CDN connector comprises a receiving module, a determining module, a sending module and an acquiring module. The receiving module is configured to receive request information from a user. The determining module is configured to determine a first vCDN node among multiple vCDN nodes. The first vCDN node is a vCDN node corresponding to a first CDN source station, and the first vCDN node is located on a mobile edge computing MEC platform where the CDN connector is located. The first CDN source station is a CDN source station corresponding to the request information among multiple CDN source stations. The sending module is configured to forward the request information to the first vCDN node. The acquiring module is configured to acquire content corresponding to the request information from the first vCDN node or the first CDN source station. The sending module is also configured to return content corresponding to the request information to the user.

[0017] Specifically, the request information includes the address information of the CDN connector. The address information of the CDN connector is obtained by the user through a DNS query.

[0018] Specifically, the determination module is configured to: determine the MEC platform where the CDN connector is located based on the address information of the CDN connector; determine the CDN origin site corresponding to the request information based on the local DNS record on the MEC platform where the CDN connector is located, and use it as the first CDN origin site; and determine the first vCDN node corresponding to the first CDN origin site based on a pre-set correspondence between CDN origin sites and vCDN nodes.

[0019] Specifically, the receiving module is configured to receive request information from a user forwarded by the base station via an edge user plane gateway, wherein the edge user plane gateway is configured with address information of the CDN connector.

[0020] Specifically, the sending module is configured to return the content corresponding to the request information to the base station via the edge user plane gateway, so that the base station forwards the content corresponding to the request information to the user.

[0021] Specifically, the system further includes a determination module configured to determine whether the content corresponding to the request information has been cached in the first vCDN node. The acquisition module is configured to acquire the content corresponding to the request information cached in the first vCDN node if the determination module determines that the content corresponding to the request information has been cached in the first vCDN node.

[0022] Specifically, if the determination module determines that the content corresponding to the request information is not cached at the first vCDN node, the receiving module is configured to receive a back-to-origin request from the first vCDN node. The sending module is configured to forward the back-to-origin request from the first vCDN node to the first CDN origin site. The acquiring module is configured to acquire the content corresponding to the request information from the first CDN origin site.

[0023] Specifically, the sending module is further configured to: forward the content corresponding to the request information from the first CDN source site to the first vCDN node.

[0024] In a third aspect, the present invention provides a computer device including a memory and a processor, wherein a computer program is stored in the memory. When the processor runs the computer program stored in the memory, the processor executes the above-mentioned CDN access method.

[0025] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processor executes the above-mentioned CDN access method.

[0026] The present invention provides a CDN access method, device, computer equipment and readable storage medium. By configuring a CDN connector on the MEC platform, users can quickly access the CDN and support multi-CDN application scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is a schematic diagram of CDN access in the shared CDN deployment mode;

[0028] Figure 2 This is a schematic diagram of CDN access in the cooperative CDN deployment mode;

[0029] Figure 3 This is a schematic diagram of CDN access in a multi-CDN deployment mode;

[0030] Figure 4 Schematic diagram of CDN access in a multi-CDN deployment mode according to an embodiment of the present invention;

[0031] Figure 5 This is a flow chart of a CDN access method according to an embodiment of the present invention;

[0032] Figure 6 This is a flowchart of another CDN access method according to an embodiment of the present invention;

[0033] Figure 7 This is a flowchart of another CDN access method according to an embodiment of the present invention;

[0034] Figure 8 This is a flowchart of another CDN access method according to an embodiment of the present invention;

[0035] Figure 9 This is a structural block diagram of a CDN access device according to an embodiment of the present invention;

[0036] Figure 10 This is a structural block diagram of another CDN access device according to an embodiment of the present invention;

[0037] Figure 11 This is a structural block diagram of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the technical solutions of the present invention, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0039] It should be understood that the specific embodiments and drawings described herein are only used to explain the present invention rather than to limit the present invention.

[0040] It is understood that, in the absence of conflict, the various embodiments of the present invention and the various features in the embodiments may be combined with each other.

[0041] It can be understood that, for the convenience of description, the drawings of the present invention only show parts related to the present invention, while parts unrelated to the present invention are not shown in the drawings.

[0042] It can be understood that each unit and module involved in the embodiments of the present invention may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0043] It will be understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of the present invention may occur in an order different from that marked in the drawings.

[0044] It is understood that the flowcharts and block diagrams of the present invention illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to various embodiments of the present invention. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented using a hardware-based system that implements the specified functions, or may be implemented using a combination of hardware and computer instructions.

[0045] It is understandable that the units and modules involved in the embodiments of the present invention may be implemented by software or hardware. For example, the units and modules may be located in a processor.

[0046] In some embodiments, CDN access can be achieved by directly deploying CDN services on MEC nodes (for example, directly deploying virtual content distribution network nodes, i.e., virtual CDN nodes, which can be referred to as vCDN nodes for short), on edge computing nodes. This deployment mode can be called a cooperative CDN deployment mode.

[0047] like Figure 2As shown in the figure, in the cooperative CDN deployment model, CDN providers can use telecom operators' MEC nodes to deploy CDN services at locations closer to users. That is, CDN access (Point of Presence, PoP) nodes (also known as CDNPoP nodes, i.e., vCDN nodes) can be sunk into the mobile network to provide lower latency and better user experience. Generally speaking, the cooperative CDN deployment model requires the configuration of both the request scheduling system of the MEC platform and the request scheduling system of the CDN system. For example, the MEC needs to configure the IP address of the CDN node on the MEC platform through the 5G core network element, similar to the whitelist method in the above-mentioned shared CDN deployment model. The CDN system needs to configure the public IP address pool information of the eUPF to ensure that after the 5G user is processed by the eUPF's NAPT (Network Address Port Translation), the request scheduling system of the CDN system can select the correct CDN node.

[0048] The collaborative CDN deployment model opens up the possibility of a multi-CDN deployment model. This refers to deploying multiple CDN providers on an MEC platform. Compared to deploying a single CDN on an MEC platform, a multi-CDN deployment model offers better performance and higher availability. In terms of internet connectivity, no single CDN provider adopts a uniform distribution strategy. For any given location, the number and scale of CDN nodes deployed by any CDN provider across different carrier networks vary. From the perspective of CDN users (such as video apps), using two or more CDN providers to provide services to users maximizes performance. This is the CDN service model currently adopted by most of the leading video apps in China (including Kuaishou, Douyin, and CCTV TV). A multi-CDN deployment model can leverage different metrics to direct traffic, balance traffic loads across different CDN providers, and facilitate service failover in the event of a CDN failure.

[0049] When using the cooperative CDN deployment model to deploy multiple CDNs, each CDN provider needs to deploy its own CDN PoP point on the edge computing node, and each vCDN node needs to interact with its own CDN system to provide CDN services. Figure 3As shown, CDN1 comes from the first CDN provider, and the first CDN provider deploys the vCDN1 node on the MEC platform (MEP) 301. CDN2 comes from the second CDN provider, and the second CDN provider deploys vCDN2 on MEP301. Thus, users can access CDN1 through vCDN1 on MEP301 or access CDN2 through vCDN2 on MEP301. However, the CDN system and the MEC request scheduling system need to be configured together to achieve the final scheduling effect, so for multi-CDN application scenarios, each CDN needs to be configured separately. For example, if a user needs to access CDN3 of a third CDN provider through MEP301, the vCDN3 node needs to be deployed on MEP301 in advance, otherwise CDN3 cannot be accessed through MEP301.

[0050] Clearly, the collaborative CDN deployment model allows CDN nodes to be deployed within the MEC platform, allowing user requests to be processed by the CDN on edge computing nodes close to the user without having to be sent to a higher-level gateway. This can significantly reduce service access latency, increase the cache hit rate at the edge of the mobile network, and significantly improve the user experience. However, the collaborative CDN deployment model requires the coordinated configuration of the request scheduling systems of the MEC platform and the CDN system to achieve CDN access.

[0051] To this end, an embodiment of the present invention provides a CDN access method, which is applied to a CDN connector, such as Figure 4 As shown, the CDN Connector can act as a connection proxy for all CDN nodes. Any vCDN deployed by a CDN provider can interact with the CDN system of that CDN provider through the CDN Connector. Moreover, the deployment information of each vCDN can be synchronized to the CDN Connector to ensure that traffic can pass through its proxy. For example, the CDN Connector can be in the form of an edge application or edge service, and its deployment is deployed through the MEC system, which is no different from other applications or services, making it more convenient in actual deployment.

[0052] Understandably, when each CDN provider deploys a vCDN node in the MEC system, it can no longer use the vCDN's own IP address information. Instead, it can uniformly adopt the IP address information of the CDN connector pre-deployed on the MEC platform to which the vCDN belongs. This ensures that the CDN connector acts as a common vCDN node. That is, this common vCDN node can be deployed in the CDN systems of different CDN providers. Obviously, at this time, the result of the relevant domain name query performed by the CDN system of any CDN provider is the IP address information of the common vCDN node, that is, the CDN connector.

[0053] Furthermore, because the CDN connector serves as a unified proxy for configuring the multiple CDN request scheduling information used by edge applications (e.g., video apps), the MEC platform's request scheduling information is as follows: the MEC configures the IP address information of the CDN connector for the eUPF via the 5G core network element. This eliminates the need for the MEC to configure the IP address information of each vCDN for the eUPF. This ensures that traffic from the application accessing each CDN first passes through the CDN connector, ensuring fast access to any CDN provider's CDN.

[0054] like Figure 5 As shown, the access method may include steps 501 to 505.

[0055] Step 501: Receive request information from a user.

[0056] In some embodiments, the address information of the CDN connector included in the request information is obtained by the user through a DNS query.

[0057] In some embodiments, the CDN connector may receive request information from the user forwarded by the base station via the eUPF, and the eUPF is configured with the address information of the CDN connector.

[0058] Step 502: Determine a first vCDN node among multiple vCDN nodes.

[0059] It is understandable that in step 502, the first vCDN node is the vCDN node corresponding to the first CDN origin station, and the first vCDN node is located on the mobile edge computing MEC platform where the CDN connector is located. The first CDN origin station is the CDN origin station corresponding to the request information among the multiple CDN origin stations.

[0060] In some embodiments, as Figure 6 As shown, the implementation method in step 502 may include steps 5021 to 5023.

[0061] Step 5021: Determine the MEC platform where the CDN connector is located based on the address information of the CDN connector.

[0062] Step 5022: Determine the CDN source station corresponding to the request information based on the local DNS record on the MEC platform where the CDN connector is located, and use it as the first CDN source station.

[0063] Step 5023: Determine a first vCDN node corresponding to the first CDN source site according to a preset correspondence between CDN source sites and vCDN nodes.

[0064] It can be understood that the pre-set correspondence between the CDN source station and the vCDN node refers to the correspondence set when the vCDN node is deployed on the MEC platform. Therefore, after the CDN connector determines the first CDN source station, the first vCDN node can be determined based on the correspondence between the CDN source station and the vCDN.

[0065] Step 503: Forward the request information to the first vCDN node.

[0066] Step 504: Obtain content corresponding to the request information from the first vCDN node or the first CDN origin site.

[0067] In some embodiments, a method for obtaining content corresponding to the request information from a first vCDN node or a first CDN origin site may include: determining whether the content corresponding to the request information is cached at the first vCDN node. If so, obtaining the content corresponding to the request information cached at the first vCDN node. Otherwise, receiving a back-to-origin request from the first vCDN node and forwarding the back-to-origin request to the first CDN origin site to obtain the content corresponding to the request information from the first CDN origin site.

[0068] In some embodiments, the method further includes: forwarding the content corresponding to the request information from the first CDN origin site to the first vCDN node.

[0069] It can be understood that when the content corresponding to the request information is not cached in the first vCDN node, the CDN connector forwards the content corresponding to the request information from the first CDN source station to the first vCDN node after obtaining the content corresponding to the request information from the first CDN source station. The first vCDN node obtains the cache of the content corresponding to the request information, so that the next time the user visits, there is no need to go back to the first CDN source station.

[0070] Step 505: Return the content corresponding to the requested information to the user.

[0071] In some embodiments, the CDN connector may return the content corresponding to the request information to the base station via the eUPF, so that the base station forwards the content corresponding to the request information to the user.

[0072] In an example of an embodiment of the present invention, the process of an edge application (such as a video APP) accessing a CDN service through a CDN connector can be as follows: Figure 7 shown.

[0073] Step 71: The UE sends a request message, which includes the IP address (10.0.0.1) of the CDN connector.

[0074] It can be understood that the UE can obtain the IP address (10.0.0.1) of the CDN connector through DNS query.

[0075] Step 72: The base station transmits the request information to the CDN connector via the eUPF.

[0076] It can be understood that the base station traffic can be diverted through the eUPF, thereby sending the user request to the CDN connector (10.0.0.1).

[0077] Step 73: The CDN connector determines the first vCDN node.

[0078] It can be understood that the CDN connector can obtain which CDN (i.e., CDN1 or CDN2) the UE's request information belongs to from the local DNS on its MEC node based on the user request information.

[0079] It can be understood that after the CDN connector determines the first CDN source station, the first vCDN node can be determined through the correspondence between the CDN source station and the vCDN node. Figure 7 In the example shown, taking the first CDN origin site as CDN1 origin site as an example, the first CDN node is the vCDN1 node.

[0080] Step 74: The CDN connector forwards the request information to the first vCDN1 node.

[0081] Step 75: The first vCDN node obtains the content requested by the user.

[0082] It can be understood that step 75 may include steps 751 to 755.

[0083] Step 751: Check whether there is already content cache locally.

[0084] If there is already a local cache of the user requested content corresponding to the UE's request information, there is no need to return to the source, and the process directly proceeds to step 76. If there is no local content cache, the process proceeds to step 752.

[0085] Step 752: The vCDN1 node sends a back-to-origin request to the CDN connector.

[0086] Since the CDN connector is the connection agent between all vCDN nodes and the CDN origin site, vCDN1 can only initiate back-to-origin requests through the CDN connector.

[0087] Step 753: The CDN connector forwards the back-to-origin request of vCDN1 to the CDN1 origin site.

[0088] Step 754: After receiving the back-to-origin request, the CDN1 origin site pushes the user requested content to the CDN connector.

[0089] Step 755: The CDN connector forwards the received user request content to the vCDN1 node.

[0090] Step 76: The vCDN1 node returns the user requested content to the CDN connector.

[0091] Step 77: Transmit the user request content to the base station via the eUPF.

[0092] Step 78: The base station transmits the user request content to the UE.

[0093] Understandably, if Figure 8 As shown, after step 754, the CDN connector has obtained the user requested content, so step 77 can be executed at the same time as step 755. The execution of step 755 is to enable the vCDN1 node to obtain the cache of the user requested content so that any user does not need to return to the source again when accessing next time.

[0094] An embodiment of the present invention provides an access device for a content delivery network CDN, such as Figure 9 As shown, the CDN access device includes a CDN connector 900, which includes a receiving module 901, a determining module 902, a sending module 903, and an obtaining module 904. The receiving module 901 is configured to receive request information from a user. The determining module 902 is configured to determine a first vCDN node among multiple vCDN nodes. The first vCDN node is a vCDN node corresponding to a first CDN source station, and the first vCDN node is located on a mobile edge computing MEC platform where the CDN connector is located. The first CDN source station is a CDN source station corresponding to the request information among multiple CDN source stations. The sending module 903 is configured to forward the request information to the first vCDN node. The obtaining module 904 is configured to obtain content corresponding to the request information from the first vCDN node or the first CDN source station. The sending module 903 is also configured to return the content corresponding to the request information to the user.

[0095] In some embodiments, the request information includes address information of the CDN connector; the address information of the CDN connector is obtained by the user through a DNS query.

[0096] In some embodiments, the determination module 902 is configured to: determine the MEC platform where the CDN connector is located based on the address information of the CDN connector; determine the CDN source station corresponding to the request information based on the local DNS record on the MEC platform where the CDN connector is located, and use it as the first CDN source station; and determine the first vCDN node corresponding to the first CDN source station based on the pre-set correspondence between the CDN source station and the vCDN node.

[0097] In some embodiments, the receiving module 901 is configured to: receive request information from a user forwarded by a base station via an edge user plane gateway; the edge user plane gateway is configured with address information of a CDN connector.

[0098] In some embodiments, the sending module 903 is configured to return the content corresponding to the request information to the base station via the edge user plane gateway, so that the base station forwards the content corresponding to the request information to the user.

[0099] In some embodiments, as Figure 10 As shown, the CDN connector 900 also includes a judgment module 905, which is configured to: determine whether the content corresponding to the request information has been cached in the first vCDN node; the acquisition module 904 is configured to: if the judgment module 905 determines that the content corresponding to the request information has been cached in the first vCDN node, then obtain the content corresponding to the request information cached in the first vCDN node.

[0100] In some embodiments, if the determination module 905 determines that the content corresponding to the request information is not cached at the first vCDN node, the receiving module 901 is configured to receive a back-to-origin request from the first vCDN node; the sending module 903 is configured to forward the back-to-origin request from the first vCDN node to the first CDN origin site. The obtaining module 904 is configured to obtain the content corresponding to the request information from the first CDN origin site.

[0101] In some embodiments, the sending module 903 is further configured to: forward the content corresponding to the request information from the first CDN origin site to the first vCDN node.

[0102] The specific solutions and beneficial effects of a communication device provided by an embodiment of the present invention can be referred to the relevant description of a CDN access method provided by an embodiment of the present invention, which will not be repeated here.

[0103] An embodiment of the present invention provides a computer device, such as Figure 11As shown, the computer device 1100 includes a memory 1101 and a processor 1102. The memory 1101 stores a computer program. When the processor 1102 runs the computer program stored in the memory 1101, the processor 1102 executes the above-mentioned CDN access method.

[0104] The specific solution and beneficial effects of a computer device provided by an embodiment of the present invention can be referred to the relevant description of a CDN access method provided by an embodiment of the present invention, which will not be repeated here.

[0105] An embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processor executes the above-mentioned CDN access method.

[0106] The specific solution and beneficial effects of a computer-readable storage medium provided by an embodiment of the present invention can be referred to the relevant description of a CDN access method provided by an embodiment of the present invention, which will not be repeated here.

[0107] It will be understood that the above embodiments are merely exemplary embodiments for illustrating the principles of the present invention, and the present invention is not limited thereto. Those skilled in the art will appreciate that various modifications and improvements can be made without departing from the spirit and substance of the present invention, and such modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method for accessing a content delivery network (CDN), characterized in that: The access method is applied to a CDN connector, wherein the CDN connector is respectively connected to a plurality of CDN origin stations and a plurality of virtual content delivery network (vCDN) nodes. The access method includes: Receive request information from users; Determine a first vCDN node from the multiple vCDN nodes; the first vCDN node is a vCDN node corresponding to a first CDN origin site, and the first vCDN node is located on a mobile edge computing MEC platform where the CDN connector is located; the first CDN origin site is a CDN origin site corresponding to the request information from among the multiple CDN origin sites; Forwarding the request information to the first vCDN node; and Obtain content corresponding to the request information from the first vCDN node or the first CDN source site, and return the content corresponding to the request information to the user.

2. The CDN access method according to claim 1, characterized in that: The request information includes the address information of the CDN connector; the address information of the CDN connector is obtained by querying the domain name system DNS.

3. The CDN access method according to claim 2, characterized in that: The determining a first vCDN node among the multiple vCDN nodes includes: Determine the MEC platform where the CDN connector is located according to the address information of the CDN connector; Determine the CDN origin site corresponding to the request information based on the local DNS record on the MEC platform where the CDN connector is located, and use it as the first CDN origin site; and According to a preset correspondence between CDN source sites and vCDN nodes, a first vCDN node corresponding to the first CDN source site is determined.

4. The CDN access method according to claim 1, wherein: The receiving of request information from the user includes: Request information from a user forwarded by a base station is received via an edge user plane gateway; the edge user plane gateway is configured with address information of the CDN connector.

5. The CDN access method according to claim 1, wherein: The returning of content corresponding to the request information to the user includes: The content corresponding to the request information is returned to the base station via the edge user plane gateway, so that the base station forwards the content corresponding to the request information to the user.

6. The CDN access method according to any one of claims 1 to 5, characterized in that: The acquiring content corresponding to the request information from the first vCDN node or the first CDN origin site includes: Determine whether the content corresponding to the request information has been cached in the first vCDN node; if so, obtain the content corresponding to the request information cached in the first vCDN node.

7. The CDN access method according to claim 6, characterized in that: Also includes: If the content corresponding to the request information is not cached in the first vCDN node, a back-to-origin request is received from the first vCDN node, and the back-to-origin request is forwarded to the first CDN source station to obtain the content corresponding to the request information from the first CDN source station.

8. The CDN access method according to claim 7, characterized in that: Also includes: Forward the content corresponding to the request information from the first CDN origin site to the first vCDN node.

9. An access device for a content delivery network (CDN), characterized in that: A CDN connector is included, wherein the CDN connector includes: A receiving module configured to receive request information from a user; A determination module configured to determine a first vCDN node from a plurality of vCDN nodes; the first vCDN node is a vCDN node corresponding to a first CDN origin station, and the first vCDN node is located on a mobile edge computing MEC platform where the CDN connector is located; The first CDN source site is a CDN source site corresponding to the request information among multiple CDN source sites; a sending module, configured to forward the request information to the first vCDN node; an acquisition module configured to acquire content corresponding to the request information from the first vCDN node or the first CDN origin site; The sending module is further configured to return content corresponding to the request information to the user.

10. A computer device, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor runs the computer program stored in the memory, the processor executes the CDN access method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the processor performs the CDN access method according to any one of claims 1 to 8.

Images