CN116668128A - CDN access method and device, computer equipment and readable storage medium - Google Patents

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

Info

Publication number
CN116668128A
CN116668128A CN202310652728.1A CN202310652728A CN116668128A CN 116668128 A CN116668128 A CN 116668128A CN 202310652728 A CN202310652728 A CN 202310652728A CN 116668128 A CN116668128 A CN 116668128A
Authority
CN
China
Prior art keywords
cdn
node
request information
vcn
connector
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202310652728.1A
Other languages
Chinese (zh)
Inventor
陈杲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
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 China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202310652728.1A priority Critical patent/CN116668128A/en
Publication of CN116668128A publication Critical patent/CN116668128A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a CDN access method, a CDN access device, computer equipment and a readable storage medium, and relates to the technical field of communication. The access method is applied to a CDN connector, the CDN connector is respectively connected with a plurality of CDN source stations and a plurality of virtual content delivery networks vCDN nodes, and the access method comprises the following steps: request information from a user is received. A first vcn node is determined among a plurality of vcn nodes. And forwarding the request information to the first vCDN node. And acquiring the content corresponding to the request information from the first vCDN node or the first CDN source station, and returning the content corresponding to the request information to the user. According to the invention, the CDN connector is configured on the MEC platform, so that the user can quickly access the CDN, and the application scenario of multiple CDNs can be supported.

Description

CDN access method and device, computer equipment and readable storage medium
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a CDN access method, an CDN access device, a computer device, and a readable storage medium.
Background
Currently, the content delivery network (Content Delivery Network, CDN) of an internet company can only be deployed based on an internet data center (Internet Data Center, IDC) room provided by an operator, that is, CDN nodes can only be "physically close" to an end user, rather than "network close", for example, the CDN nodes cannot be deployed to an operator office room behind a cell or a base station. With the development of the internet, the mainstream CDN manufacturers have explicitly regarded edge computing (Mobile Edge Computing platform, MEC) as the evolution direction of the CDN, because emerging services such as 4K (resolution 3840×2160 pixels)/8K (resolution 7680×4320 pixels) video, virtual Reality (VR)/augmented Reality (Augmented Reality, AR) require CDN nodes to have not only storage and delivery capabilities but also computing capabilities.
To support edge computing, fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) networks may employ a distributed gateway architecture, with a 5G core network (5G core,5 gc) allowing user plane gateway UPF (User Profile Function) to be independently countersunk to the mobile network edge, and multiple UPF cascades. Meanwhile, the MEC platform has storage, distribution and calculation capabilities, so that the method for deploying the CDN based on the MEC has network conditions and infrastructure conditions at the same time. Among the present CDN deployment modes based on MEC in the industry, one deployment mode is a shared CDN deployment mode, which means that a cache application is deployed on MEC, transparent caching and content regeneration are performed on hot content, and CDN nodes deployed in a fixed network are shared by users.
As shown in fig. 1, in the deployment mode of the shared CDN, a method of configuring a whitelist for an edge UPF (eUPF) through a core network PCF (Policy Control Function) network element is generally adopted. The whitelist contains domain names and/or IP addresses of the service applications supported by the shared CDN. If the eUPF finds that the access domain name/IP address of the user data packet is on the white list through parsing, the data packet is directly forwarded to the shared CDN. The deployment mode of the shared CDN is to deploy only the caching application to the MEC, rather than deploying the CDN nodes themselves to the MEC. If the cache is dead (e.g., the first time the user accesses, or the cached content is replaced with new content), the user can only directly access the original CDN node (i.e., the CDN node from which the content originated), which requires that the eUPF need be connectable to the shared CDN node shown in fig. 1.
Therefore, under the condition of cache failure, the user still can only directly access the original CDN node, and the problem that the user is still close to the CDN node but not close to the network can not be solved.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: in the prior art, under the condition of cache failure, a user still can only directly access the original CDN node in a deployment mode of the shared CDN, and the problem of 'close physical distance' cannot be solved.
Aiming at the defects in the prior art, the following scheme is provided:
in a first aspect, the present invention provides an access method of a content delivery network CDN, applied to a CDN connector, where the CDN connector is connected to a plurality of CDN source stations and a plurality of virtual content delivery network (vcn) nodes, respectively, the access method includes: request information from a user is received. A first vcn node is determined among a plurality of vcn nodes. And forwarding the request information to the first vCDN node. And acquiring the content corresponding to the request information from the first vCDN node or the first CDN source station, and returning the content corresponding to the request information to the user. The first vcn node is a vcn node corresponding to the first CDN source station, and the first vcn 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 in the CDN source stations.
Specifically, the request information includes address information of the CDN connector; the address information of the CDN connectors is obtained by a domain name system (Domain Name System, DNS) query.
Specifically, determining a first vcn node among a plurality of vcn nodes includes: and determining the MEC platform where the CDN connector is located according to the address information of the CDN connector. And determining a CDN source station corresponding to the request information according to the record of the local DNS on the MEC platform where the CDN connector is positioned, and taking the CDN source station as a first CDN source station. And determining a first vCDN node corresponding to the first CDN source station according to the preset corresponding relation between the CDN source station and the vCDN node.
Specifically, receiving request information from a user includes: and receiving request information from the user forwarded by the base station through the edge user plane gateway. The edge user plane gateway is configured with address information of the CDN connector.
Specifically, returning content corresponding to the request information to the user includes: and returning the content corresponding to the request information to the base station through the edge user plane gateway so that the base station forwards the content corresponding to the request information to the user.
Specifically, obtaining content corresponding to the request information from the first vcn node or the first CDN source station includes: and judging whether the content corresponding to the request information is cached in the first vCDN node or not. If yes, obtaining the content corresponding to the request information cached in the first vCDN node.
Specifically, the method further comprises the following steps: if the content corresponding to the request information is not cached in the first vCDN node, receiving a source-returning request from the first vCDN node, and forwarding the source-returning request to the first CDN source station to acquire the content corresponding to the request information from the first CDN source station.
Specifically, the method further comprises the following steps: and forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.
In a second aspect, the present invention provides an access device for a content delivery network CDN, including a CDN connector, where the CDN connector includes a receiving module, a determining module, a sending module, and an obtaining module. The receiving module is configured to receive request information from a user. The determining module is configured to determine a first vcn node among the plurality of vcn nodes. The first vcn node is a vcn node corresponding to the first CDN source station, and the first vcn 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 in the CDN source stations. The sending module is configured to forward the request information to the first vcn node. The acquisition module is configured to acquire content corresponding to the request information from the first vcn node or the first CDN source station. The sending module is further configured to return content corresponding to the request information to the user.
Specifically, the request information includes address information of the CDN connector. The address information of the CDN connectors is obtained by the user via a DNS query.
Specifically, the determination module is configured to: and determining the MEC platform where the CDN connector is located according to the address information of the CDN connector. And determining a CDN source station corresponding to the request information according to the record of the local DNS on the MEC platform where the CDN connector is positioned, and taking the CDN source station as a first CDN source station. And determining a first vCDN node corresponding to the first CDN source station according to the preset corresponding relation between the CDN source station and the vCDN node.
Specifically, the receiving module is configured to: and receiving request information from the user forwarded by the base station through the edge user plane gateway. The edge user plane gateway is configured with address information of the CDN connector.
Specifically, the transmission module is configured to: and returning the content corresponding to the request information to the base station through the edge user plane gateway so that the base station forwards the content corresponding to the request information to the user.
Specifically, the device further comprises a judging module, which is configured to: and judging whether the content corresponding to the request information is cached in the first vCDN node or not. The acquisition module is configured to: and if the judging module judges that the content corresponding to the request information is cached in the first vCDN node, acquiring the content corresponding to the request information cached in the first vCDN node.
Specifically, if the judging module judges that the content corresponding to the request information is not cached in the first vcn node, the receiving module is configured to: a back source request from a first vcn node is received. The sending module is set as follows: forwarding a back source request from the first vcn node to the first CDN source station. The acquisition module is configured to acquire content corresponding to the request information from the first CDN source station.
Specifically, the transmitting module is further configured to: and forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.
In a third aspect, the present invention provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the access method of the CDN.
In a fourth aspect, the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the method of accessing a CDN as described above.
According to the CDN access method, the CDN access device, the computer equipment and the readable storage medium, the CDN connector is configured on the MEC platform, so that a user can quickly access the CDN, and an application scene of multiple CDNs can be supported.
Drawings
FIG. 1 is a schematic diagram of CDN access in a deployment mode of a shared CDN;
FIG. 2 is a schematic diagram of CDN access in a deployment mode of a collaborative CDN;
FIG. 3 is a schematic diagram of CDN access in a multi-CDN deployment mode;
FIG. 4 is a schematic diagram of CDN access in a multi-CDN deployment mode according to an embodiment of the present invention;
FIG. 5 is a flowchart of a CDN access method according to an embodiment of the present invention;
FIG. 6 is a flowchart of another CDN access method according to an embodiment of the present invention;
FIG. 7 is a flowchart of a method for accessing a CDN according to another embodiment of the present invention;
FIG. 8 is a flowchart of a method for accessing a CDN according to another embodiment of the present invention;
FIG. 9 is a block diagram illustrating a CDN access device according to an embodiment of the present invention;
FIG. 10 is a block diagram illustrating another CDN access device according to an embodiment of the present invention;
fig. 11 is a block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
In order to make the technical scheme of the present invention better understood by those skilled in the art, the following detailed description of the embodiments of the present invention will be given with reference to the accompanying drawings.
It is to be understood that the specific embodiments and figures described herein are merely illustrative of the invention, and are not limiting of the invention.
It is to be understood that the various embodiments of the invention and the features of the embodiments may be combined with each other without conflict.
It is to be understood that only the portions relevant to the present invention are shown in the drawings for convenience of description, and the portions irrelevant to the present invention are not shown in the drawings.
It should be understood that each unit and module in the embodiments of the present invention may correspond to only one physical structure, may be formed by a plurality of physical structures, or may be integrated into one physical structure.
It will be appreciated that, without conflict, the functions and steps noted in the flowcharts and block diagrams of the present invention may occur out of the order noted in the figures.
It is to be understood that the flowcharts and block diagrams of the present invention illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, devices, methods according to various embodiments of the present invention. Where each block in the flowchart or block diagrams may represent a unit, module, segment, code, or the like, which comprises executable instructions for implementing the specified functions. Moreover, each block or combination of blocks in the block diagrams and flowchart illustrations can be implemented by hardware-based systems that perform the specified functions, or by combinations of hardware and computer instructions.
It should be understood that the units and modules related in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, for example, the units and modules may be located in a processor.
In some embodiments, access to the CDN may be achieved by deploying the CDN service directly on the MEC node (e.g., deploying the virtual content delivery network node, i.e., the virtual CDN node, which may be referred to simply as the vccdn node, directly on the edge computing node), which may be referred to as a deployment mode of the collaborative CDN.
As shown in fig. 2, in the deployment mode of the collaborative CDN, the CDN provider can deploy CDN services with the MEC nodes of the telecom operator at a location closer to the user, i.e., CDN access (Point of Presence, poP) nodes (also called CDN PoP nodes, i.e., vccdn nodes) can sink into the mobile network to provide lower latency and better user experience. In general, the deployment mode of the collaborative CDN requires that the request scheduling system of the MEC platform and the request scheduling system of the CDN system be configured simultaneously. 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 method of sharing the whitelist in the deployment mode of the CDN described above. The CDN system needs to configure the public IP address pool information of the eUPF, so as to ensure that the request scheduling system of the CDN system can select the correct CDN node after the 5G user is processed by NAPT (Network Address Port Translation) of the eUPF.
The deployment mode of the collaborative CDN provides a possibility for a deployment mode of multiple CDNs, which refers to deploying multiple CDN providers (CDN providers) on the MEC platform, which may provide better performance and higher availability than deploying a single CDN on the MEC platform. In terms of the connection mode of the internet, any CDN provider does not adopt a policy of uniform distribution, and for any geographic location, the number and the scale of CDN nodes deployed by any CDN provider in different operator networks are different. From the perspective of a CDN user (e.g., a video application, i.e., a video APP), simultaneously using two or more CDN servers together to provide services to users will achieve maximum performance, and is the CDN service mode currently adopted by most of the head video APPs (including fast-handed, jittering, central video TV, etc.) in China. The deployment mode of multiple CDNs can utilize different metering indexes to realize traffic orientation, and can realize balance of traffic load among different CDN providers or service switching when a certain CDN fails.
When the deployment mode of the cooperation CDN is adopted to deploy multiple CDNs, each CDN provider needs to deploy own CDN PoP point on the edge computing node, and each vCDN node needs to interact with the CDN system to which the vCDN node belongs respectively, so that CDN service can be provided. As shown in fig. 3, CDN1 comes from a first CDN provider that deploys vcn 1 nodes on a MEC Platform (MEP) 301. CDN2 comes from a second CDN provider that deploys vcn 2 on MEP 301. Thus, a user may access CDN1 through vCDN1 on MEP301 or CDN2 through vCDN2 on MEP 301. However, the CDN system and the MEC request scheduling system need to be cooperatively configured together to achieve the final scheduling effect, so for the application scenario of multiple CDNs, each CDN needs to be separately configured. For example, if a user needs to access CDN3 of the third CDN provider through MEP301, a vcn 3 node needs to be deployed on MEP301 in advance, otherwise CDN3 cannot be accessed through MEP 301.
Obviously, the CDN nodes can be deployed into the MEC platform by adopting a deployment mode of the cooperative CDNs, so that the user request can be processed by the CDNs on the edge computing nodes close to the user without being sent to a high-level gateway, service access delay can be greatly reduced, the edge cache hit rate of the mobile network is improved, and the user service experience is remarkably improved. But the deployment mode of the cooperative CDN requires that the request scheduling system of the MEC platform and the request scheduling system of the CDN system be cooperatively configured together to achieve access to the CDN.
For this reason, the embodiment of the present invention provides a method for accessing a CDN, which is applied to a CDN Connector, as shown in fig. 4, where the CDN Connector (CDN Connector) may be used as a connection proxy for all CDN nodes, a vccdn deployed by any CDN provider may interact with a CDN system of the CDN provider through the CDN Connector, and deployment information of each vccdn may be synchronized to the CDN Connector, so as to ensure that traffic may pass through the proxy thereof. The CDN connector may be in the form of an edge application or an edge service, where the deployment is performed by the MEC system, and is not different from other applications or services, and is convenient in actual deployment.
It can be understood that when each CDN provider deploys the vcn node in the MEC system, the IP address information of the vcn may not be used any more, but the IP address information of the CDN connector deployed in advance on the MEC platform to which the vcn belongs is uniformly adopted, so that the CDN connector can be ensured to be used as a common vcn node, that is, the common vcn node can be deployed in the CDN systems of different CDN providers. Obviously, the result of the CDN system of any CDN provider performing the related domain name query at this time is the IP address information of the common vcn node, i.e., the CDN connector.
In addition, since the CDN connector is used as a unified agent to configure a plurality of CDN request scheduling information used by an edge application (e.g., a video class APP), the request scheduling information of the MEC platform is: the MEC configures IP address information of the CDN connector for the eUPF through the 5G core network element. Therefore, the MEC does not need to configure the IP address information of each vCDN for eUPF, so that the traffic of the application for accessing each CDN can be ensured to pass through the CDN connector first, and the CDN of any CDN provider can be ensured to be accessed quickly.
As shown in fig. 5, the access method may include steps 501 to 505.
Step 501, receiving request information from a user.
In some embodiments, the request information includes address information of the CDN connector obtained by the user via a DNS query.
In some embodiments, the CDN connector may receive the request information from the user forwarded by the base station via an eUPF in which address information of the CDN connector is configured.
Step 502, determining a first vcn node among a plurality of vcn nodes.
It can be appreciated that in step 502, the first vcn node is a vcn node corresponding to the first CDN source station, and the first vcn 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 in the CDN source stations.
In some embodiments, as shown in fig. 6, the implementation method in step 502 may include steps 5021 to 5023.
Step 5021, determining an MEC platform where the CDN connector is located according to the address information of the CDN connector.
Step 5022, determining a CDN source station corresponding to the request information according to a record of the local DNS on the MEC platform where the CDN connector is located, and taking the CDN source station as a first CDN source station.
Step 5023, determining a first vcn node corresponding to the first CDN source station according to a preset correspondence between CDN source stations and vcn nodes.
As can be appreciated, the preset correspondence between the CDN source station and the vccdn node refers to a correspondence set when the vccdn node is deployed on the MEC platform, so after the CDN connector determines the first CDN source station, the first vccdn node may be determined according to the correspondence between the CDN source station and the vccdn node.
Step 503, forwarding the request information to the first vcn node.
Step 504, obtain the content corresponding to the request information from the first vcn node or the first CDN source station.
In some embodiments, the implementation method for obtaining the content corresponding to the request information from the first vcn node or the first CDN source station may include: and judging whether the content corresponding to the request information is cached in the first vCDN node or not. If yes, obtaining the content corresponding to the request information cached in the first vCDN node. Otherwise, receiving a back source request from the first vCDN node, and forwarding the back source request to the first CDN source station to acquire content corresponding to the request information from the first CDN source station.
In some embodiments, the method further comprises: and forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.
It may be appreciated that, in the case where the content corresponding to the request information is not cached in the first vccdn node, after the CDN connector obtains the content corresponding to the request information from the first CDN source station, the content corresponding to the request information from the first CDN source station is forwarded to the first vccdn node, and the first vccdn node obtains the cache of the content corresponding to the request information, so that the first CDN source station is not required to be returned when the user accesses the first vccdn node next time.
Step 505, the content corresponding to the request information is returned to the user.
In some embodiments, the CDN connector may return content corresponding to the request information to the base station via the eUPF to cause the base station to forward the content corresponding to the request information to the user.
In one example of an embodiment of the present invention, the flow of an edge application (e.g., video class APP) accessing CDN services through a CDN connector may be as shown in fig. 7.
In step 71, the UE sends out request information, where the information includes the IP address (10.0.0.1) of the CDN connector.
It can be appreciated that the UE can obtain the IP address (10.0.0.1) of the CDN connector through DNS query.
Step 72, the base station transmits the request information to the CDN connector via the eUPF.
It will be appreciated that base station traffic may be split by the eUPF to send user requests to the CDN connector (10.0.0.1).
Step 73, the CDN connector determines a first vcn node.
It can be appreciated that the CDN connector may obtain, from the local DNS on the MEC node where it is located, to which CDN (i.e., which of CDN1 or CDN 2) the request information of the UE belongs, according to the user request information.
It may be appreciated that, after the CDN connector determines the first CDN source station, the first vccdn node may be determined according to the correspondence between the CDN source station and the vccdn node, and in the example shown in fig. 7, taking the first CDN source station as the CDN1 source station as an example, the first CDN node is the vccdn 1 node.
Step 74, the CDN connector forwards the request information to the first vcn 1 node.
Step 75, the first vcn node obtains the content requested by the user.
It will be appreciated that step 75 may include steps 751 through 755.
Step 751, query if there is already a content cache locally.
If there is already a local cache of the user requested content corresponding to the UE's request information, then no source back is needed, proceeding directly to step 76. If there is no local content cache, step 752 is entered.
Step 752, vcn 1 node issues a back source request to the CDN connector.
Since the CDN connector is a connection proxy between all vcn nodes and the CDN source site, vcn 1 can only initiate a back source request through the CDN connector.
Step 753, the CDN connector forwards the echo request of vcn 1 to the CDN1 source station.
Step 754, after receiving the source request, the CDN1 source station pushes the content of the user request to the CDN connector.
Step 755, the CDN connector forwards the received user request content to the vcn 1 node.
Step 76, the vcn 1 node returns the user request content to the CDN connector.
Step 77, transmitting the user request content to the base station via the eUPF.
Step 78, the base station transmits the user request content to the UE.
It will be appreciated that as shown in fig. 8, after step 754, the CDN connector has obtained the user requested content, and thus step 77 may be performed while step 755 is performed. Step 755 is performed in order to enable the vcn 1 node to obtain a cache of the user requested content so that any user does not need to go back to the source again at the next access.
The embodiment of the invention provides an access device of a content delivery network CDN, as shown in fig. 9, where the access device of the CDN includes a CDN connector 900, and the CDN connector 900 includes a receiving module 901, a determining module 902, a sending module 903, and an obtaining module 904. The receiving module 901 is arranged to receive request information from a user. The determining module 902 is configured to determine a first vcn node among a plurality of vcn nodes. The first vcn node is a vcn node corresponding to the first CDN source station, and the first vcn 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 in the CDN source stations. The sending module 903 is configured to forward the request information to the first vcn node. The obtaining module 904 is configured to obtain content corresponding to the request information from the first vcn node or the first CDN source station. The sending module 903 is further configured to return content corresponding to the request information to the user.
In some embodiments, the request information includes address information of the CDN connector; the address information of the CDN connectors is obtained by the user via a DNS query.
In some embodiments, the determination module 902 is configured to: determining an MEC platform where the CDN connector is located according to the address information of the CDN connector; according to a record of a local DNS on an MEC platform where the CDN connector is located, determining a CDN source station corresponding to the request information and taking the CDN source station as a first CDN source station; and determining a first vCDN node corresponding to the first CDN source station according to the preset corresponding relation between the CDN source station and the vCDN node.
In some embodiments, the receiving module 901 is configured to: receiving request information from a user forwarded by a base station through an edge user plane gateway; the edge user plane gateway is configured with address information of the CDN connector.
In some embodiments, the sending module 903 is configured to: and returning the content corresponding to the request information to the base station through the edge user plane gateway so that the base station forwards the content corresponding to the request information to the user.
In some embodiments, as shown in fig. 10, the CDN connector 900 further includes a determining module 905 configured to: judging whether the content corresponding to the request information is cached in a first vCDN node or not; the acquisition module 904 is configured to: if the determining module 905 determines that the content corresponding to the request information is cached in the first vccdn node, the content corresponding to the request information cached in the first vccdn node is obtained.
In some embodiments, if the determining module 905 determines that the content corresponding to the request information is not cached in the first vcn node, the receiving module 901 is configured to: receiving a source return request from a first vCDN node; the transmitting module 903 is configured to: forwarding a back source request from the first vcn node to the first CDN source station. The obtaining module 904 is configured to obtain content corresponding to the request information from the first CDN source station.
In some embodiments, the sending module 903 is further configured to: and forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.
The specific scheme and the beneficial effects of a communication device provided by the embodiment of the present invention can refer to the related description of a CDN access method provided by the embodiment of the present invention, and are not repeated here.
An embodiment of the present invention provides a computer device, as shown in fig. 11, where the computer device 1100 includes a memory 1101 and a processor 1102, where a computer program is stored in the memory 1101, and when the processor 1102 runs the computer program stored in the memory 1101, the processor 1102 executes the foregoing CDN access method.
The specific scheme and the beneficial effects of a computer device provided by the embodiment of the present invention may refer to the related description of a CDN access method provided by the embodiment of the present invention, which is not described herein again.
Embodiments of the present invention provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the CDN access method described above.
The specific scheme and the beneficial effects of a computer readable storage medium provided by the embodiments of the present invention may refer to the related description of a CDN access method provided by the embodiments of the present invention, which is not described herein again.
It is to be understood that the above embodiments are merely illustrative of the application of the principles of the present invention, but not in limitation thereof. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the invention, and are also considered to be within the scope of the invention.

Claims (11)

1. An access method of a content delivery network CDN, wherein the access method is applied to a CDN connector, the CDN connector being respectively connected to a plurality of CDN source stations and a plurality of virtual content delivery networks vcn nodes, the access method comprising:
receiving request information from a user;
determining a first vcn node among the plurality of vcn nodes; the first vCDN node is a vCDN node corresponding to a first CDN source station, and the first vCDN node is positioned on a mobile edge computing MEC platform where the CDN connector is positioned; the first CDN source station is a CDN source station corresponding to the request information in the CDN source stations;
forwarding the request information to a first vcn node; and
and acquiring the content corresponding to the request information from the first vCDN node or the first CDN source station, and returning the content corresponding to the request information to a user.
2. The CDN access method of claim 1 wherein the request information includes address information of CDN connectors; the address information of the CDN connector is obtained by inquiring a Domain Name System (DNS).
3. The CDN access method of claim 2, wherein determining a first vcn node from the plurality of vcn nodes includes:
determining an MEC platform where the CDN connector is located according to the address information of the CDN connector;
determining a CDN source station corresponding to the request information according to a record of a local DNS on an MEC platform where the CDN connector is located, and taking the CDN source station as the first CDN source station; and
according to a preset corresponding relation between the CDN source station and the vCDN node, determining a first vCDN node corresponding to the first CDN source station.
4. The CDN access method of claim 1 wherein receiving request information from a user comprises:
receiving request information from a user forwarded by a base station through an edge user plane gateway; and the edge user plane gateway is configured with address information of the CDN connector.
5. The CDN access method of claim 1 wherein returning content corresponding to the request information to the user includes:
and returning the content corresponding to the request information to the base station through 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, wherein the acquiring content corresponding to the request information from the first vcn node or the first CDN source station includes:
judging whether the content corresponding to the request information is cached in the first vCDN node or not; if yes, obtaining the content corresponding to the request information cached in the first vCDN node.
7. The CDN access method of claim 6 further comprising: if the content corresponding to the request information is not cached in the first vcn node, receiving a source return request from the first vcn node, and forwarding the source return request 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 of claim 7 further comprising:
and forwarding the content corresponding to the request information from the first CDN source station to the first vCDN node.
9. An access device of a content delivery network CDN, comprising a CDN connector comprising;
a receiving module configured to receive request information from a user;
a determining module configured to determine a first vcn node among the plurality of vcn nodes; the first vCDN node is a vCDN node corresponding to a first CDN source station, and the first vCDN node is positioned on a mobile edge computing MEC platform where the CDN connector is positioned; the first CDN source station is a CDN source station corresponding to the request information in the CDN source stations;
the sending module is configured to forward the request information to a first vcn node;
the acquisition module is configured to acquire content corresponding to the request information from the first vcn node or the first CDN source station;
the sending module is further configured to return content corresponding to the request information to the user.
10. A computer device comprising a memory and a processor, the memory having stored therein a computer program, which when executed by the processor performs the method of accessing a CDN according to any one of claims 1 to 8.
11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, performs the access method of the CDN according to any one of claims 1 to 8.
CN202310652728.1A 2023-06-02 2023-06-02 CDN access method and device, computer equipment and readable storage medium Pending CN116668128A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310652728.1A CN116668128A (en) 2023-06-02 2023-06-02 CDN access method and device, computer equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310652728.1A CN116668128A (en) 2023-06-02 2023-06-02 CDN access method and device, computer equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN116668128A true CN116668128A (en) 2023-08-29

Family

ID=87711485

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310652728.1A Pending CN116668128A (en) 2023-06-02 2023-06-02 CDN access method and device, computer equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN116668128A (en)

Similar Documents

Publication Publication Date Title
CN113596191B (en) Data processing method, network element equipment and readable storage medium
US20230171618A1 (en) Communication method and apparatus
US8756296B2 (en) Method, device and system for distributing file data
AU2009342169A1 (en) Scalable WLAN gateway
CN110896553A (en) Multi-access edge computing method and platform and communication system
US8665849B2 (en) Methods and systems for implementing inter-network roam, querying and attaching network
CN113572835B (en) Data processing method, network element equipment and readable storage medium
CN114270789A (en) Method and device for acquiring information
KR20200130043A (en) Method and apparatus for managing an identifier of a terminal in edge computing service
JP2008522464A (en) Method and system for agent to redirect terminal request
CN113572864B (en) Data processing method, network element equipment and readable storage medium
EP2709337B1 (en) Service data processing method, device and system
CN103825923A (en) Resource download method, business server and mobile phone client-terminal
EP3917083A1 (en) Network device and method for searching for edge service implemented in network device
CN113613314A (en) ICOT private network networking method and system based on converged network splitter
KR102214915B1 (en) Operating method of server load balancing apparatus, local domain name server and content delivery service system
GB2446877A (en) Address translation using an intermediate node and a database of fixed and temporary addresses
CN109788075B (en) Private network system, data acquisition method and edge server
CN113841372A (en) Method and apparatus for obtaining and managing location information of mobile terminal in edge computing system
CN116668128A (en) CDN access method and device, computer equipment and readable storage medium
CN114006915B (en) Resource request method, device, equipment and computer readable storage medium
CN114025023A (en) Source returning method, device, equipment and computer readable storage medium
JP2010113710A (en) Method of transmitting data between peers with network selection according to at least one criterion, and associated management device and communication equipment
CN112994996B (en) Home network sharing method, MEC server, computer device, and medium
CN111147345B (en) Cloud environment network isolation device and method and cloud system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination