WO2021003798A1 - 一种实现域名访问加速的方法和*** - Google Patents

一种实现域名访问加速的方法和*** Download PDF

Info

Publication number
WO2021003798A1
WO2021003798A1 PCT/CN2019/100417 CN2019100417W WO2021003798A1 WO 2021003798 A1 WO2021003798 A1 WO 2021003798A1 CN 2019100417 W CN2019100417 W CN 2019100417W WO 2021003798 A1 WO2021003798 A1 WO 2021003798A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
cdn
target
resolution
identification information
Prior art date
Application number
PCT/CN2019/100417
Other languages
English (en)
French (fr)
Inventor
尤文榜
林更新
刘涛
孙达康
苏志伟
Original Assignee
网宿科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to US17/622,712 priority Critical patent/US20220255894A1/en
Priority to EP19937051.1A priority patent/EP3989508A1/en
Publication of WO2021003798A1 publication Critical patent/WO2021003798A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/457—Network directories; Name-to-address mapping containing identifiers of data entities on a computer, e.g. file names
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to the field of network communication technology, in particular to a method and system for realizing domain name access acceleration.
  • CDN Content Delivery Network
  • the DNS system can direct the received domain name resolution request to the resolution scheduling system of different CDN vendors according to the configuration.
  • the resolution scheduling system of the CDN vendor can determine whether the local CDN cluster provides accelerated access services for the corresponding domain name access traffic. If not, the resolution scheduling system can forward the domain name resolution request to the resolution scheduling system of other CDN vendors to Respond to domain name resolution requests through other CDN clusters.
  • CDN clusters mostly use domain names as the identifier to mark domain name access traffic. If there are domain name access traffic forwarded by other CDN clusters (which can be called switching traffic) and domain name access traffic directly sent by user terminals (which can be called Direct sales traffic), CDN vendors will not be able to effectively distinguish the above two types of domain name access traffic, which is not conducive to traffic settlement and the expansion of CDN business.
  • the embodiments of the present invention provide a method and system for realizing domain name access acceleration.
  • the technical solution is as follows:
  • a method for realizing domain name access acceleration includes:
  • the CDN node receives the domain name access traffic of the target domain name through the locally configured target VIP address, and determines the target CDN vendor corresponding to the target VIP address;
  • the CDN node reads the resource configuration file corresponding to the target CDN vendor and the target domain name, and processes the domain name access traffic to which the identification information is added based on the resource configuration file.
  • the method further includes:
  • the CDN node When receiving the resource prefetch request of the target domain name carrying the identification information of the target CDN vendor, the CDN node obtains the domain name resource file of the target domain name;
  • the CDN node marks the domain name resource file according to the identification information, and stores the marked domain name resource file.
  • the CDN node can mark the domain name resource files with the identification information of different CDN vendors to realize the differentiated storage of domain name resource files corresponding to different CDN vendors.
  • the method further includes:
  • the CDN node When receiving the resource push request of the target domain name carrying the identification information of the target CDN vendor, the CDN node deletes the locally stored domain name resource file of the target domain name marked with the identification information.
  • the CDN node can accurately delete the domain name resource file corresponding to the specified CDN vendor by marking the domain name resource file with the identification information of different CDN vendors.
  • the CDN node adds identification information of the target CDN vendor to the domain name information of the domain name access traffic, including:
  • the CDN node uses the identification information of the target CDN vendor as a suffix and splices it at the end of the domain name information of the domain name access traffic.
  • the identification information of the CDN manufacturer is uniformly added to the end of the domain name information in the form of a suffix, so as to facilitate the identification of the domain name information and identification information.
  • processing the domain name access traffic to which the identification information is added includes:
  • the CDN node deletes the identification information of the target CDN vendor in the domain name information, and sends the deletion of the identifier to the source station The domain name access traffic after the information.
  • a method for realizing domain name access acceleration includes:
  • the CDN resolution scheduling system receives the domain name resolution request of the target domain name, reads the domain name resolution configuration of the target domain name, the domain name resolution configuration records at least one VIP address corresponding to the CDN manufacturer;
  • the CDN resolution scheduling system determines the target VIP address corresponding to the source CDN vendor of the domain name resolution request according to the domain name resolution configuration
  • the CDN resolution scheduling system feeds back the target VIP address to the source end of the domain name resolution request, so that the source end sends domain name access traffic to the target VIP address.
  • the CDN resolution scheduling system determining the target VIP address corresponding to the source CDN vendor of the domain name resolution request according to the domain name resolution configuration includes:
  • the CDN resolution scheduling system determines all available VIP addresses corresponding to the source CDN manufacturer of the domain name resolution request according to the domain name resolution configuration
  • the CDN resolution scheduling system determines the target VIP address among all available VIP addresses according to the network status and geographic status of the source end of the domain name resolution request.
  • the CDN resolution scheduling system receives the domain name resolution request of the target domain name, it further includes:
  • the CDN resolution scheduling system sends the domain name resolution request to another preset CDN resolution scheduling system.
  • the method further includes:
  • the CDN resolution scheduling system receives a service configuration request carrying domain name information of the target domain name and identification information of the target CDN vendor;
  • the CDN resolution scheduling system determines the target VIP address, and sets the domain name resolution configuration of the target domain name based on the target VIP address, the domain name information, and the identification information.
  • a system for realizing domain name access acceleration includes a CDN node and a CDN resolution scheduling system, wherein the CDN node is used to execute the method as described in the first aspect, so The CDN parsing and scheduling system is used to execute the method described in the second aspect.
  • a network device in a fourth aspect, includes a processor and a memory.
  • the memory stores at least one instruction, at least one program, code set, or instruction set.
  • a piece of program, the code set or the instruction set is loaded and executed by the processor to implement the method for realizing domain name access acceleration as described in the first aspect.
  • a computer-readable storage medium stores at least one instruction, at least one program, code set, or instruction set, the at least one instruction, the at least one program, and the code
  • the set or instruction set is loaded and executed by the processor to implement the method for realizing domain name access acceleration as described in the first aspect.
  • the CDN node receives the domain name access traffic of the target domain name through the locally configured target VIP address, and determines the target CDN vendor corresponding to the target VIP address; the CDN node adds the identification information of the target CDN vendor to the domain name information of the domain name access traffic ; The CDN node reads the resource configuration file corresponding to the target CDN manufacturer and the target domain name, and processes the access traffic of the domain name with the identification information based on the resource configuration file.
  • the source of the domain name access traffic is identified by distinguishing the VIP address at the CDN node, and the domain name access traffic from different sources is marked in the CDN cluster by adding the identification information of the CDN vendor Therefore, it is possible to effectively distinguish the domain name access traffic of the same domain name switched from different CDN vendors, which is beneficial to the traffic settlement in the CDN cluster and the expansion of CDN business.
  • FIG. 1 is a schematic diagram of a network architecture for realizing domain name access acceleration according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for realizing domain name access acceleration provided by an embodiment of the present invention
  • FIG. 3 is a schematic diagram of prefetching/pushing a domain name resource file according to an embodiment of the present invention
  • Fig. 4 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • the embodiment of the present invention provides a method for realizing domain name access acceleration.
  • the method can be applied to a CDN cluster and is specifically executed by a CDN resolution scheduling system and a CDN node.
  • the CDN cluster can include at least a CDN resolution scheduling system and a large number of CDN nodes.
  • the CDN resolution scheduling system can be used to receive domain name resolution requests sent by the outside world (which can be a DNS system or other CDN cluster resolution scheduling systems), and follow the schedule.
  • the configured domain name resolution configuration feedbacks different domain name access addresses in the CDN cluster.
  • the CDN node can cache domain name resource files and resource configuration files of a large number of domain names. When receiving domain name access traffic, the CDN node can process the domain name access traffic through the above resource configuration files.
  • the above-mentioned CDN resolution scheduling system can also exchange data with the resolution scheduling systems of other CDN clusters, and forward the received domain name resolution requests to the resolution scheduling systems of other CDN clusters, thereby realizing traffic switching between CDN vendors.
  • the composed network architecture can be shown in Figure 1.
  • the functions of the CDN parsing and scheduling system and the CDN node can be implemented by a single network device, or by a device group composed of multiple network devices.
  • the above-mentioned network equipment may include a processor, a memory, and a transceiver.
  • the processor may be used to perform the processing for implementing domain name access acceleration in the following process.
  • the memory may be used to store the data required and generated during the processing.
  • the transceiver may Used to receive and send relevant data during processing.
  • Step 201 The CDN resolution scheduling system receives the domain name resolution request of the target domain name, and reads the domain name resolution configuration of the target domain name.
  • the domain name resolution configuration records at least one VIP (Virtual IP) address corresponding to the CDN vendor.
  • the CDN resolution scheduling system may be pre-configured with a corresponding domain name resolution configuration for each domain name, and the domain name resolution configuration may record at least one VIP address corresponding to the CDN manufacturer.
  • the domain name resolution configuration can be DNSMap, which is used to map different domain names to different VIP addresses.
  • the CDN resolution scheduling system can read the locally stored domain name resolution configuration of the target domain name. It is worth mentioning that, referring to Figure 1, after the domain name operator of the target domain name has opened the domain name access acceleration service in multiple CDN vendors, the target domain name and the resolution scheduling system of multiple CDN vendors can be added to the DNS system. Mapping relations.
  • the user terminal can send a domain name resolution request for the target domain name to the DNS system.
  • the DNS system can follow the preset resolution rules (that is, the target domain name and the resolution scheduling system of multiple CDN vendors). Mapping relationship)
  • the domain name resolution request is forwarded to the resolution scheduling system of the CDN manufacturer, such as the above-mentioned CDN resolution scheduling system, or other CDN resolution scheduling systems.
  • other CDN resolution scheduling systems can also forward the domain name resolution request to the CDN resolution scheduling system to accelerate the corresponding domain name access traffic through the CDN cluster to which the CDN resolution scheduling system belongs. Therefore, the domain name resolution request received by the CDN resolution scheduling system may be forwarded through the DNS system or through other CDN resolution scheduling systems.
  • the CDN resolution scheduling system can forward the domain name resolution request to other CDN resolution scheduling systems.
  • the following processing can occur after step 201: If the domain name of the target domain name does not exist If the resolution configuration, or the domain name resolution configuration of the target domain name is empty, the CDN resolution scheduling system sends a domain name resolution request to other preset CDN resolution scheduling systems.
  • the CDN resolution scheduling system can Send domain name resolution requests to other preset CDN resolution scheduling systems.
  • the other CDN resolution scheduling systems here can be pre-configured in the CDN resolution scheduling system, which can be configured in units of domain names. For example, domain name A corresponds to CDN resolution scheduling system 1, and domain name B corresponds to CDN resolution. Scheduling system 2. In this way, when the CDN resolution scheduling system sends a domain name resolution request to other CDN resolution scheduling systems, it can select the CDN resolution scheduling system corresponding to the pre-configured target domain name.
  • Step 202 The CDN resolution scheduling system determines the target VIP address corresponding to the source CDN vendor of the domain name resolution request according to the domain name resolution configuration.
  • the CDN resolution scheduling system can first determine the source CDN vendor of the domain name access traffic.
  • the source CDN vendor is the CDN vendor to which the CDN resolution scheduling system belongs. If the domain name access traffic is forwarded to the CDN resolution scheduling system by another CDN resolution scheduling system, the source CDN vendor is the CDN to which the other CDN resolution scheduling system belongs Vendor. After that, the CDN resolution scheduling system can determine the target VIP address corresponding to the source CDN vendor of the domain name resolution request according to the domain name resolution configuration of the target domain name.
  • the process of the CDN resolution scheduling system selecting VIP addresses for the domain name resolution request may be specifically as follows: the CDN resolution scheduling system determines all available VIP addresses corresponding to the source CDN vendor of the domain name resolution request according to the domain name resolution configuration; CDN resolution scheduling The system determines the target VIP address among all available VIP addresses according to the network status and geographic status of the source end of the domain name resolution request.
  • the CDN resolution scheduling system can determine the source CDN vendor of the domain name resolution request, and then obtain all available VIP addresses corresponding to the source CDN vendor in the CDN cluster to which the CDN resolution scheduling system belongs. After that, the CDN resolution scheduling system can determine, among all available VIP addresses, the geographic location closest to the source end and belong to the target VIP address under the same network operator based on the network status and geographic status of the source end of the domain name resolution request.
  • the area where the source end of the domain name resolution request is located can also be determined first, and then all available VIP addresses corresponding to the source CDN manufacturer in the area are obtained.
  • Step 203 The CDN resolution scheduling system feeds back the target VIP address to the source end of the domain name resolution request, so that the source end sends domain name access traffic to the target VIP address.
  • the source end of the domain name resolution request is the user terminal that sends the domain name resolution request.
  • the CDN resolution scheduling system can set the domain name resolution configuration based on the service configuration request, and the corresponding processing can be as follows:
  • the CDN resolution scheduling system receives the service configuration request carrying the domain name information of the target domain name and the identification information of the target CDN vendor;
  • the CDN resolution scheduling system determines the target VIP address, and sets the domain name resolution configuration of the target domain name based on the target VIP address, domain name information and identification information.
  • the resolution scheduling system of the CDN cluster can receive the domain name information carrying the target domain name and the identity of the target CDN manufacturer Information service configuration request. After that, the CDN resolution scheduling system can assign VIP addresses to the target CDN vendors and target domain names. Specifically, the CDN resolution scheduling system can determine the unused target VIP addresses, and then based on the target VIP address, the domain name information of the target domain name, and the target CDN vendor The identification information sets the domain name resolution configuration of the target domain name.
  • Step 204 The CDN node receives the domain name access traffic of the target domain name through the locally configured target VIP address, and determines the target CDN vendor corresponding to the target VIP address.
  • CDN vendors support accelerated services for domain name access traffic forwarded by other CDN vendors, they can plan different VIP addresses for different CDN vendors on CDN nodes in advance.
  • different VIP addresses can be used to receive Domain name access traffic under this domain name of different CDN vendors.
  • VIP address 1 is used to receive domain name access traffic of domain name X forwarded by CDN vendor A
  • VIP address 2 is used to receive domain name access traffic of domain name X forwarded by CDN vendor B Traffic
  • VIP address 3 is used to receive domain name access traffic of domain name X directly sent from the user terminal.
  • one VIP address can be used to receive domain name access traffic from multiple domain names of the same CDN vendor.
  • the CDN node can continuously monitor multiple locally configured VIP addresses.
  • the CDN node can determine the target CDN vendor corresponding to the target VIP address.
  • Step 205 The CDN node adds the identification information of the target CDN vendor to the domain name information of the domain name access traffic.
  • the CDN node after the CDN node determines the target CDN vendor corresponding to the target VIP address, it can extract the domain name information (such as the URL of the domain name access traffic) carried in the domain name access traffic, and then add the target CDN vendor's logo to the domain name information information.
  • the CDN node may use the identification information of the target CDN vendor as the suffix and splice it at the end of the domain name information of the domain name access traffic.
  • the identification information of the target CDN vendor is "AAA” and the domain name information is "www.aa.com” , It will be "www.aa.com.AAA" after splicing.
  • the target CDN vendor is the CDN vendor to which the CDN node belongs, that is, the domain name access traffic is not the traffic forwarded by other CDN vendors to the target CDN vendor, there is no need to add identification information to the domain name information, thereby reducing the addition of identification information
  • the processing capacity of the CDN node saves the processing resources.
  • Step 206 The CDN node reads the resource configuration file corresponding to the target CDN vendor and the target domain name, and processes the domain name access traffic with the identification information added based on the resource configuration file.
  • the CDN node after the CDN node determines the target CDN vendor corresponding to the target VIP address, it can read the locally stored resource configuration file corresponding to the target CDN vendor and the target domain name, and then access the domain name with identification information added according to the resource configuration file Traffic is processed.
  • the processing of domain name access traffic may at least include: 1. Respond to domain name access traffic based on locally stored domain name resource files; 2. Forward the domain name access traffic to the parent node; 3. Return the domain name access traffic to the source deal with.
  • the CDN node may delete the identification information of the CDN vendor in the domain name access traffic. Accordingly, part of the processing in step 206 may be as follows: The source site sends the domain name access traffic, and the CDN node deletes the identification information of the target CDN manufacturer in the domain name information, and sends the domain name access traffic with the deleted identification information to the source site.
  • the CDN node after the CDN node determines that it needs to send domain name access traffic to the source site of the target domain name based on the resource configuration file, it can first read the domain name information in the domain name access traffic, and then delete the target CDN vendor logo in the domain name information After that, the domain name access traffic with the identification information deleted can be sent to the origin site. It can be understood that if the CDN node sends domain name access traffic to the parent node in the CDN cluster, there is no need to delete the identification information of the target CDN vendor in the domain name information.
  • the CDN node can distinguish the domain name resource files corresponding to different CDN vendors by adding the identification information of the CDN vendor during the process of prefetching and storing the domain name resource files.
  • the corresponding processing can be as follows: When the resource prefetching request of the target domain name carrying the identification information of the target CDN manufacturer, the CDN node obtains the domain name resource file of the target domain name; the CDN node marks the domain name resource file according to the identification information, and stores the marked domain name resource file. In this way, the CDN node can mark the domain name resource files with the identification information of different CDN vendors to realize the differentiated storage of domain name resource files corresponding to different CDN vendors.
  • domain name operators can store domain name resource files in CDN nodes in advance through resource prefetching.
  • CDN vendors can also deploy domain names in nodes of other CDN vendors in advance through resource prefetching. resource.
  • the target CDN manufacturer wants to deploy the domain name resource file of the target domain name in the CDN node in advance
  • the target CDN manufacturer can submit a resource prefetch request to the resource prefetch system of the CDN cluster to which the CDN node belongs, and the resource prefetch request can carry There is the target domain name and the identification information of the target CDN vendor.
  • the resource prefetching system may send a resource prefetching request of the target domain name carrying the identification information of the target CDN vendor to the CDN node.
  • the CDN node After receiving the above resource prefetch request, the CDN node can obtain the domain name resource file of the target domain name from the source site of the target domain name, and then mark the domain name resource file according to the identification information of the target CDN vendor, and store the marked domain name resource file. Therefore, the CDN node can respond to the domain name access traffic sent by different CDN vendors based on the stored domain name resource files of different CDN vendors. Refer to Figure 3 for the above processing.
  • the CDN node may delete the domain name resource file of the specified CDN vendor based on the resource push request, and the corresponding processing may be as follows: when receiving the resource push request of the target domain name carrying the identification information of the target CDN vendor, the CDN node deletes the local The stored domain name resource file of the target domain name marked with identification information.
  • the domain name operator can delete the stored domain name resource files in the CDN cluster through resource push.
  • CDN vendors can also delete their pre-deployment in CDN nodes of other CDN vendors through resource push The domain name resource file.
  • the target CDN manufacturer wants to delete the domain name resource file of the target domain name deployed in the CDN node
  • the target CDN manufacturer can submit a resource push request to the resource push system of the CDN cluster to which the CDN node belongs, and the resource push request can carry the target domain name And the identification information of the target CDN vendor.
  • the resource pushing system may send a resource pushing request of the target domain name carrying the identification information of the target CDN vendor to the CDN node.
  • the CDN node may delete the locally stored domain name resource file of the target domain name marked with the identification information of the CDN vendor. Refer to Figure 3 for the above processing.
  • the CDN node receives the domain name access traffic of the target domain name through the locally configured target VIP address, and determines the target CDN vendor corresponding to the target VIP address; the CDN node adds the identification information of the target CDN vendor to the domain name information of the domain name access traffic ; The CDN node reads the resource configuration file corresponding to the target CDN manufacturer and the target domain name, and processes the access traffic of the domain name with the identification information based on the resource configuration file.
  • the source of the domain name access traffic is identified by distinguishing the VIP address at the CDN node, and the domain name access traffic from different sources is marked in the CDN cluster by adding the identification information of the CDN vendor Therefore, it is possible to effectively distinguish the domain name access traffic of the same domain name switched from different CDN vendors, which is beneficial to the traffic settlement in the CDN cluster and the expansion of CDN business.
  • the embodiments of the present invention also provide a system for realizing domain name access acceleration.
  • the system includes a CDN node and a CDN resolution scheduling system, wherein the CDN node is used to execute the CDN node in the above embodiment
  • the CDN parsing and scheduling system is used to execute the processing realized by the CDN parsing and scheduling system in the foregoing embodiment.
  • Fig. 4 is a schematic structural diagram of a network device provided by an embodiment of the present invention.
  • the network device 400 may have relatively large differences due to different configurations or performances, and may include one or more central processing units 422 (for example, one or more processors) and a memory 432, and one or more storage application programs 442 or The storage medium 430 of the data 444 (for example, one or a storage device in a large amount).
  • the memory 432 and the storage medium 430 may be short-term storage or persistent storage.
  • the program stored in the storage medium 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the network device 400.
  • the central processing unit 422 may be configured to communicate with the storage medium 430, and execute a series of instruction operations in the storage medium 430 on the network device 400.
  • the network device 400 may also include one or more power supplies 429, one or more wired or wireless network interfaces 450, one or more input and output interfaces 458, one or more keyboards 456, and/or, one or more operating systems 441, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.
  • the network device 400 may include a memory and one or more programs.
  • One or more programs are stored in the memory and configured to be executed by one or more processors. The above instructions for realizing domain name access acceleration.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种实现域名访问加速的方法和***，属于网络通信技术领域。所述方法包括：CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定目标VIP地址对应的目标CDN厂商（204）；CDN节点在域名访问流量的域名信息中添加目标CDN厂商的标识信息（205）；CDN节点读取目标CDN厂商和目标域名对应的资源配置文件，并基于资源配置文件对添加有标识信息的域名访问流量进行处理（206）。采用本方法可以对不同CDN厂商切换来的域名访问流量进行有效区分，有利于CDN集群中的流量结算以及CDN业务的拓展。

Description

一种实现域名访问加速的方法和*** 技术领域
本发明涉及网络通信技术领域，特别涉及一种实现域名访问加速的方法和***。
背景技术
随着互联网技术的不断进步，CDN(内容分发网络，Content Delivery Network)服务也随之快速发展，域名运营方往往会在多个CDN厂商处同时开通同一域名的加速访问服务。由于服务成本、资源分布等因素，不同CDN厂商间会存在流量切换的需求，即将各自的域名访问流量切换至其它CDN厂商处进行加速。
具体来讲，域名运营方在不同CDN厂商处开通了同一域名的加速访问服务后，可以先在DNS***对域名的解析规则进行配置。从而DNS***可以根据该配置将接收到的域名解析请求引导至不同CDN厂商的解析调度***。之后，CDN厂商的解析调度***可以判断本地CDN集群是否为相应的域名访问流量提供加速访问服务，如果不提供，解析调度***则可以将该域名解析请求转发至其它CDN厂商的解析调度***，以通过其它CDN集群对域名解析请求进行响应。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：
当前CDN集群大多以域名为标识对域名访问流量进行标记，如果CDN集群中同时存在其它CDN集群转发来的域名访问流量(可称为切换流量)和用户终端直接发送的域名访问流量(可称为直销流量)，CDN厂商将无法对上述两类域名访问流量进行有效区分，进而不利于流量结算以及CDN业务的拓展。
发明内容
为了解决现有技术的问题，本发明实施例提供了一种实现域名访问加速的方法和***。所述技术方案如下：
第一方面，提供了一种实现域名访问加速的方法，所述方法包括：
CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定所述目标VIP地址对应的目标CDN厂商；
所述CDN节点在所述域名访问流量的域名信息中添加所述目标CDN厂商的标识信息；
所述CDN节点读取所述目标CDN厂商和所述目标域名对应的资源配置文件，并基于所述资源配置文件对添加有所述标识信息的域名访问流量进行处理。
可选的，所述方法还包括：
当接收到携带有目标CDN厂商的标识信息的目标域名的资源预取请求时，所述CDN节点获取所述目标域名的域名资源文件；
所述CDN节点根据所述标识信息对所述域名资源文件进行标记，并存储标记后的所述域名资源文件。
这样，CDN节点可以通过对域名资源文件标记不同CDN厂商的标识信息，实现对不同CDN厂商对应的域名资源文件的区别存储。
可选的，所述方法还包括：
当接收到携带有目标CDN厂商的标识信息的目标域名的资源推送请求时，所述CDN节点删除本地存储的、标记有所述标识信息的所述目标域名的域名资源文件。
这样，CDN节点可以通过对域名资源文件标记不同CDN厂商的标识信息，实现对指定CDN厂商对应的域名资源文件的精确删除。
可选的，所述CDN节点在所述域名访问流量的域名信息中添加所述目标CDN厂商的标识信息，包括：
所述CDN节点将所述目标CDN厂商的标识信息作为后缀，拼接在所述域名访问流量的域名信息的尾部。
这样，统一将CDN厂商的标识信息以后缀的形式添加在域名信息的尾部，从而便于识别域名信息和标识信息。
可选的，所述对添加有所述标识信息的域名访问流量进行处理，包括：
如果确定需要向所述目标域名的源站发送所述域名访问流量，所述CDN节点则删除所述域名信息中的所述目标CDN厂商的标识信息，并向所述源站发送删除所述标识信息后的域名访问流量。
这样，在回源前删除域名信息中的CDN厂商的标识信息，可以有效保证回 源处理的正常执行。
第二方面，提供了一种实现域名访问加速的方法，所述方法包括：
CDN解析调度***接收目标域名的域名解析请求，读取所述目标域名的域名解析配置，所述域名解析配置中记录有至少一个CDN厂商对应的VIP地址；
所述CDN解析调度***根据所述域名解析配置确定所述域名解析请求的源CDN厂商对应的目标VIP地址；
所述CDN解析调度***向所述域名解析请求的源端反馈所述目标VIP地址，以使所述源端向所述目标VIP地址发送域名访问流量。
可选的，所述CDN解析调度***根据所述域名解析配置确定所述域名解析请求的源CDN厂商对应的目标VIP地址，包括：
所述CDN解析调度***根据所述域名解析配置确定域名解析请求的源CDN厂商对应的所有可用VIP地址；
所述CDN解析调度***根据所述域名解析请求的源端的网络状态和地理状态，在所述所有可用VIP地址中确定目标VIP地址。
可选的，所述CDN解析调度***接收目标域名的域名解析请求之后，还包括：
如果不存在所述目标域名的域名解析配置，或者所述目标域名的域名解析配置为空，所述CDN解析调度***则向预设的其它CDN解析调度***发送所述域名解析请求。
可选的，所述方法还包括：
所述CDN解析调度***接收携带有目标域名的域名信息和目标CDN厂商的标识信息的服务配置请求；
所述CDN解析调度***确定目标VIP地址，并基于所述目标VIP地址、所述域名信息和所述标识信息设置所述目标域名的域名解析配置。
第三方面，提供了一种实现域名访问加速的***，其特征在于，所述***包括CDN节点和CDN解析调度***，其中，所述CDN节点用于执行如第一方面所述的方法，所述CDN解析调度***用于执行如第二方面所述的方法。
第四方面，提供了一种网络设备，所述网络设备包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如第一方面所述的实现域名访问加速的方法。
第五方面，提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如第一方面所述的实现域名访问加速的方法。
本发明实施例提供的技术方案带来的有益效果是：
本发明实施例中，CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定目标VIP地址对应的目标CDN厂商；CDN节点在域名访问流量的域名信息中添加目标CDN厂商的标识信息；CDN节点读取目标CDN厂商和目标域名对应的资源配置文件，并基于资源配置文件对添加有标识信息的域名访问流量进行处理。这样，对于同一域名的域名访问流量，以在CDN节点处区分VIP地址的方式对域名访问流量的来源进行识别，并在CDN集群内部以添加CDN厂商的标识信息的方式标记不同来源的域名访问流量，从而可以对不同CDN厂商切换来的同一域名的域名访问流量进行有效区分，有利于CDN集群中的流量结算以及CDN业务的拓展。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种实现域名访问加速的网络架构示意图；
图2是本发明实施例提供的一种实现域名访问加速的方法流程图；
图3是本发明实施例提供的一种域名资源文件的预取/推送示意图；
图4是本发明实施例提供的一种网络设备的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
本发明实施例提供了一种实现域名访问加速的方法，该方法可以应用于CDN集群，并具体由CDN解析调度***和CDN节点执行。其中，CDN集群可以至少包括CDN解析调度***和大量的CDN节点，CDN解析调度***可以用于接收外界(可以是DNS***也可以其它CDN集群的解析调度***)发送的域名解析请求，并按照预设的域名解析配置反馈CDN集群中不同的域名访问地址。CDN节点上可以缓存有大量域名的域名资源文件以及资源配置文件，当接收到域名访问流量时，CDN节点可以通过上述资源配置文件对域名访问流量进行处理。上述CDN解析调度***还可以与其它CDN集群的解析调度***进行数据交互，即将接收到的域名解析请求转发至其它CDN集群的解析调度***，从而实现CDN厂商间的流量切换，上述多个CDN厂商组成的网络架构可以如图1所示。CDN解析调度***和CDN节点的功能可以由单个网络设备实现，也可以由多个网络设备构成的设备组实现。上述网络设备可以包括处理器、存储器、收发器，处理器可以用于进行下述流程中执行实现域名访问加速的处理，存储器可以用于存储处理过程中需要的数据以及产生的数据，收发器可以用于接收和发送处理过程中的相关数据。
下面将结合具体实施方式，对图2所示的处理流程进行详细的说明，内容可以如下：
步骤201，CDN解析调度***接收目标域名的域名解析请求，读取目标域名的域名解析配置。
其中，域名解析配置中记录有至少一个CDN厂商对应的VIP(虚拟IP，Virtual IP)地址。
在实施中，CDN解析调度***中可以预先针对每个域名设置有对应的域名解析配置，该域名解析配置中可以记录有至少一个CDN厂商对应的VIP地址。具体来讲，域名解析配置可以为DNSMap，用于将不同域名映射到不同的VIP地址。这样，在接收到目标域名的域名解析请求之后，CDN解析调度***可以读取本地存储的目标域名的域名解析配置。值得一提的是，参照图1所示，目 标域名的域名运营方在多个CDN厂商中开通了域名访问加速服务之后，可以在DNS***中添加目标域名和多个CDN厂商的解析调度***的映射关系。这样，当用户想要访问目标域名时，用户终端可以向DNS***发送目标域名的域名解析请求，之后，DNS***可以按照预设解析规则(即上述目标域名和多个CDN厂商的解析调度***的映射关系)将该域名解析请求转发至CDN厂商的解析调度***，如可以是上述CDN解析调度***，也可以是其它CDN解析调度***。而其它CDN解析调度***在接收到上述域名解析请求后，也可以再将域名解析请求转发至CDN解析调度***，以通过CDN解析调度***所属的CDN集群实现对相应的域名访问流量的加速。故而，CDN解析调度***接收到的域名解析请求可以是经DNS***转发的，也可以是经其它CDN解析调度***转发的。
可选的，当无法对域名解析请求进行有效响应时，CDN解析调度***可以将域名解析请求转发至其它CDN解析调度***，相应的，步骤201后可以存在如下处理：如果不存在目标域名的域名解析配置，或者目标域名的域名解析配置为空，CDN解析调度***则向预设的其它CDN解析调度***发送域名解析请求。
在实施中，CDN解析调度***接收到目标域名的域名解析请求后，如果无法读取到目标域名的域名解析配置，或者读取到的目标域名的域名解析配置为空，CDN解析调度***则可以向预设的其它CDN解析调度***发送域名解析请求。值得一提的是，此处的其它CDN解析调度***可以是预先配置在CDN解析调度***内的，具体可以以域名为单位进行配置，如域名A对应CDN解析调度***1，域名B对应CDN解析调度***2，这样，CDN解析调度***在向其它CDN解析调度***发送域名解析请求时，可以选取预先配置的目标域名对应的CDN解析调度***。
步骤202，CDN解析调度***根据域名解析配置确定域名解析请求的源CDN厂商对应的目标VIP地址。
在实施中，CDN解析调度***在读取了目标域名的域名解析配置之后，可以先确定域名访问流量的源CDN厂商，此处，基于步骤201的说明，若域名访问流量为用户终端直接发送至CDN解析调度***，则源CDN厂商为CDN解析调度***所属的CDN厂商，如果域名访问流量为其它CDN解析调度***转发至CDN解析调度***的，则源CDN厂商为其它CDN解析调度***所属的CDN 厂商。之后，CDN解析调度***可以根据目标域名的域名解析配置，确定出域名解析请求的源CDN厂商对应的目标VIP地址。
可选的，步骤202中CDN解析调度***为域名解析请求选取VIP地址的处理具体可以如下：CDN解析调度***根据域名解析配置确定域名解析请求的源CDN厂商对应的所有可用VIP地址；CDN解析调度***根据域名解析请求的源端的网络状态和地理状态，在所有可用VIP地址中确定目标VIP地址。
在实施中，CDN解析调度***接收到域名解析请求后，可以确定域名解析请求的源CDN厂商，然后获取CDN解析调度***所属CDN集群中源CDN厂商对应的所有可用VIP地址。之后，CDN解析调度***可以根据域名解析请求的源端的网络状态和地理状态，在所有可用VIP地址中确定与源端地理位置最近，且属于同一网络运营商下的目标VIP地址。当然，获取源CDN厂商对应的所有可用VIP地址时，也可以先确定域名解析请求的源端所处的区域，再获取该区域内源CDN厂商对应的所有可用VIP地址。
步骤203，CDN解析调度***向域名解析请求的源端反馈目标VIP地址，以使源端向目标VIP地址发送域名访问流量。
其中，域名解析请求的源端即为发送域名解析请求的用户终端。
可选的，CDN解析调度***可以基于服务配置请求对域名解析配置进行设置，相应的处理可以如下：CDN解析调度***接收携带有目标域名的域名信息和目标CDN厂商的标识信息的服务配置请求；CDN解析调度***确定目标VIP地址，并基于目标VIP地址、域名信息和标识信息设置目标域名的域名解析配置。
在实施中，在CDN集群中开通对于目标CDN厂商的目标域名的域名访问流量的加速服务的过程中，该CDN集群的解析调度***可以接收到携带有目标域名的域名信息和目标CDN厂商的标识信息的服务配置请求。之后，CDN解析调度***可以为目标CDN厂商及目标域名分配VIP地址，具体的，CDN解析调度***可以确定未被使用的目标VIP地址，然后基于目标VIP地址、目标域名的域名信息和目标CDN厂商的标识信息设置目标域名的域名解析配置。
步骤204，CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定目标VIP地址对应的目标CDN厂商。
在实施中，CDN厂商如果支持对其他CDN厂商转发的域名访问流量的加 速服务，则可以预先在CDN节点上针对不同CDN厂商规划不同的VIP地址，对于同一域名，不同的VIP地址可以用于接收不同CDN厂商的该域名下的域名访问流量，例如，VIP地址1用于接收CDN厂商A转发来的域名X的域名访问流量，VIP地址2用于接收CDN厂商B转发来的域名X的域名访问流量，VIP地址3用于接收用户终端直接发送来的域名X的域名访问流量。可以理解，一个VIP地址可以用于接收同一CDN厂商的多个域名的域名访问流量。这样，CDN节点可以持续监听本地配置的多个VIP地址，当通过本地配置的目标VIP地址接收到目标域名的域名访问流量时，CDN节点可以确定目标VIP地址对应的目标CDN厂商。
步骤205，CDN节点在域名访问流量的域名信息中添加目标CDN厂商的标识信息。
在实施中，CDN节点在确定了目标VIP地址对应的目标CDN厂商后，可以提取域名访问流量携带的域名信息(如域名访问流量的URL)，然后可以在该域名信息中添加目标CDN厂商的标识信息。具体的，CDN节点可以将目标CDN厂商的标识信息最为后缀，拼接在域名访问流量的域名信息的尾部，例如，目标CDN厂商的标识信息为“AAA”，域名信息为“www.aaa.com”，则拼接后即为“www.aaa.com.AAA”。需要说明的是，如果目标CDN厂商为CDN节点所属的CDN厂商，即域名访问流量不是其他CDN厂商转发到目标CDN厂商的流量，则可以无需在域名信息中添加标识信息，从而可以减少添加标识信息的处理量，节省CDN节点的处理资源。
步骤206，CDN节点读取目标CDN厂商和目标域名对应的资源配置文件，并基于资源配置文件对添加有标识信息的域名访问流量进行处理。
在实施中，CDN节点在确定目标VIP地址对应的目标CDN厂商之后，可以读取本地存储的目标CDN厂商和目标域名对应的资源配置文件，然后根据该资源配置文件对添加有标识信息的域名访问流量进行处理。此处，对域名访问流量的处理至少可以包括：1.基于本地存储的域名资源文件对域名访问流量进行响应；2.向父节点转发该域名访问流量；3.对该域名访问流量进行回源处理。
可选的，在对域名访问流量进行回源处理时，CDN节点可以将域名访问流量中的CDN厂商的标识信息删除，相应的，步骤206中的部分处理可以如下：如果确定需要向目标域名的源站发送域名访问流量，CDN节点则删除域名信息 中的目标CDN厂商的标识信息，并向源站发送删除标识信息后的域名访问流量。
在实施中，CDN节点在基于资源配置文件确定出需要向目标域名的源站发送域名访问流量后，可以先读取该域名访问流量中的域名信息，然后删除域名信息中的目标CDN厂商的标识信息，之后则可以向源站发送删除了标识信息后的域名访问流量。可以理解，如果CDN节点将域名访问流量发往CDN集群中的上级父节点，则无需删除域名信息中的目标CDN厂商的标识信息。
可选的，CDN节点可以在对域名资源文件进行预取和存储的过程中，通过添加CDN厂商的标识信息的方式对不同CDN厂商对应的域名资源文件进行区分，相应的处理可以如下：当接收到携带有目标CDN厂商的标识信息的目标域名的资源预取请求时，CDN节点获取目标域名的域名资源文件；CDN节点根据标识信息对域名资源文件进行标记，并存储标记后的域名资源文件。这样，CDN节点可以通过对域名资源文件标记不同CDN厂商的标识信息，实现对不同CDN厂商对应的域名资源文件的区别存储。
在实施中，域名运营方可以通过资源预取的方式，提前将域名资源文件存储到CDN节点中，同理，CDN厂商也可以通过资源预取的方式，提前在其它CDN厂商的节点中部署域名资源文件。这样，目标CDN厂商想要提前在CDN节点中部署目标域名的域名资源文件时，目标CDN厂商可以向CDN节点所属CDN集群的资源预取***提交资源预取请求，该资源预取请求中可以携带有目标域名和目标CDN厂商的标识信息。之后，资源预取***可以向CDN节点发送携带有目标CDN厂商的标识信息的目标域名的资源预取请求。CDN节点在接收到上述资源预取请求后，可以从目标域名的源站获取目标域名的域名资源文件，然后可以根据目标CDN厂商的标识信息对域名资源文件进行标记，并存储标记后的域名资源文件。从而CDN节点可以基于存储的不同CDN厂商的域名资源文件对不同CDN厂商发来的域名访问流量进行响应。上述处理可以参考图3所示。
可选的，CDN节点可以基于资源推送请求删除指定CDN厂商的域名资源文件，相应的处理可以如下：当接收到携带有目标CDN厂商的标识信息的目标域名的资源推送请求时，CDN节点删除本地存储的、标记有标识信息的目标域名的域名资源文件。
在实施中，域名运营方可以通过资源推送的方式，删除CDN集群中已存储 的域名资源文件，同理，CDN厂商也可以通过资源推送的方式，删除其在其它CDN厂商的CDN节点中预先部署的域名资源文件。这样，目标CDN厂商想要删除在CDN节点中部署目标域名的域名资源文件时，目标CDN厂商可以向CDN节点所属CDN集群的资源推送***提交资源推送请求，该资源推送请求中可以携带有目标域名和目标CDN厂商的标识信息。之后，资源推送***可以向CDN节点发送携带有目标CDN厂商的标识信息的目标域名的资源推送请求。CDN节点在接收到上述资源推送请求后，可以删除本地存储的、标记有CDN厂商的标识信息的目标域名的域名资源文件。上述处理可以参考图3所示。
本发明实施例中，CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定目标VIP地址对应的目标CDN厂商；CDN节点在域名访问流量的域名信息中添加目标CDN厂商的标识信息；CDN节点读取目标CDN厂商和目标域名对应的资源配置文件，并基于资源配置文件对添加有标识信息的域名访问流量进行处理。这样，对于同一域名的域名访问流量，以在CDN节点处区分VIP地址的方式对域名访问流量的来源进行识别，并在CDN集群内部以添加CDN厂商的标识信息的方式标记不同来源的域名访问流量，从而可以对不同CDN厂商切换来的同一域名的域名访问流量进行有效区分，有利于CDN集群中的流量结算以及CDN业务的拓展。
基于相同的技术构思，本发明实施例还提供了一种实现域名访问加速的***，所述***包括CDN节点和CDN解析调度***，其中，所述CDN节点用于执行如上述实施例中CDN节点所实现的处理，所述CDN解析调度***用于执行如上述实施例中CDN解析调度***所实现的处理。
图4是本发明实施例提供的网络设备的结构示意图。该网络设备400可因配置或性能不同而产生比较大的差异，可以包括一个或一个以***处理器422(例如，一个或一个以上处理器)和存储器432，一个或一个以上存储应用程序442或数据444的存储介质430(例如一个或一个以上海量存储设备)。其中，存储器432和存储介质430可以是短暂存储或持久存储。存储在存储介质430的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对网络设备400中的一系列指令操作。更进一步地，中央处理器422可以设置为与存 储介质430通信，在网络设备400上执行存储介质430中的一系列指令操作。
网络设备400还可以包括一个或一个以上电源429，一个或一个以上有线或无线网络接口450，一个或一个以上输入输出接口458，一个或一个以上键盘456，和/或，一个或一个以上操作***441，例如Windows Server，Mac OS X，Unix，Linux，FreeBSD等等。
网络设备400可以包括有存储器，以及一个或者一个以上的程序，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行所述一个或者一个以上程序包含用于进行上述实现域名访问加速的指令。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (12)

  1. 一种实现域名访问加速的方法，其特征在于，所述方法包括：
    CDN节点通过本地配置的目标VIP地址接收目标域名的域名访问流量，确定所述目标VIP地址对应的目标CDN厂商；
    所述CDN节点在所述域名访问流量的域名信息中添加所述目标CDN厂商的标识信息；
    所述CDN节点读取所述目标CDN厂商和所述目标域名对应的资源配置文件，并基于所述资源配置文件对添加有所述标识信息的域名访问流量进行处理。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当接收到携带有目标CDN厂商的标识信息的目标域名的资源预取请求时，所述CDN节点获取所述目标域名的域名资源文件；
    所述CDN节点根据所述标识信息对所述域名资源文件进行标记，并存储标记后的所述域名资源文件。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当接收到携带有目标CDN厂商的标识信息的目标域名的资源推送请求时，所述CDN节点删除本地存储的、标记有所述标识信息的所述目标域名的域名资源文件。
  4. 根据权利要求1所述的方法，其特征在于，所述CDN节点在所述域名访问流量的域名信息中添加所述目标CDN厂商的标识信息，包括：
    所述CDN节点将所述目标CDN厂商的标识信息作为后缀，拼接在所述域名访问流量的域名信息的尾部。
  5. 根据权利要求1所述的方法，其特征在于，所述对添加有所述标识信息的域名访问流量进行处理，包括：
    如果确定需要向所述目标域名的源站发送所述域名访问流量，所述CDN节点则删除所述域名信息中的所述目标CDN厂商的标识信息，并向所述源站发送 删除所述标识信息后的域名访问流量。
  6. 一种实现域名访问加速的方法，其特征在于，所述方法包括：
    CDN解析调度***接收目标域名的域名解析请求，读取所述目标域名的域名解析配置，所述域名解析配置中记录有至少一个CDN厂商对应的VIP地址；
    所述CDN解析调度***根据所述域名解析配置确定所述域名解析请求的源CDN厂商对应的目标VIP地址；
    所述CDN解析调度***向所述域名解析请求的源端反馈所述目标VIP地址，以使所述源端向所述目标VIP地址发送域名访问流量。
  7. 根据权利要求6所述的方法，其特征在于，所述CDN解析调度***根据所述域名解析配置确定所述域名解析请求的源CDN厂商对应的目标VIP地址，包括：
    所述CDN解析调度***根据所述域名解析配置确定域名解析请求的源CDN厂商对应的所有可用VIP地址；
    所述CDN解析调度***根据所述域名解析请求的源端的网络状态和地理状态，在所述所有可用VIP地址中确定目标VIP地址。
  8. 根据权利要求6所述的方法，其特征在于，所述CDN解析调度***接收目标域名的域名解析请求之后，还包括：
    如果不存在所述目标域名的域名解析配置，或者所述目标域名的域名解析配置为空，所述CDN解析调度***则向预设的其它CDN解析调度***发送所述域名解析请求。
  9. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述CDN解析调度***接收携带有目标域名的域名信息和目标CDN厂商的标识信息的服务配置请求；
    所述CDN解析调度***确定目标VIP地址，并基于所述目标VIP地址、所述域名信息和所述标识信息设置所述目标域名的域名解析配置。
  10. 一种实现域名访问加速的***，其特征在于，所述***包括CDN节点和CDN解析调度***，其中，所述CDN节点用于执行如权利要求1至5任一项所述的方法，所述CDN解析调度***用于执行如权利要求6至9任一项所述的方法。
  11. 一种网络设备，其特征在于，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至6任一所述的方法中的处理。
  12. 一种计算机可读存储介质，存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至6中任一所述的方法中的处理。
PCT/CN2019/100417 2019-07-05 2019-08-13 一种实现域名访问加速的方法和*** WO2021003798A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/622,712 US20220255894A1 (en) 2019-07-05 2019-08-13 Method and system for implementing domain name access acceleration
EP19937051.1A EP3989508A1 (en) 2019-07-05 2019-08-13 Method and system for implementing domain name access accelration

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910605508.7A CN110445886B (zh) 2019-07-05 2019-07-05 一种实现域名访问加速的方法和***
CN201910605508.7 2019-07-05

Publications (1)

Publication Number Publication Date
WO2021003798A1 true WO2021003798A1 (zh) 2021-01-14

Family

ID=68429442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/100417 WO2021003798A1 (zh) 2019-07-05 2019-08-13 一种实现域名访问加速的方法和***

Country Status (4)

Country Link
US (1) US20220255894A1 (zh)
EP (1) EP3989508A1 (zh)
CN (1) CN110445886B (zh)
WO (1) WO2021003798A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111625359B (zh) * 2020-05-25 2023-04-18 北京金山云网络技术有限公司 用户的cdn用量的确定方法、装置和终端设备
CN112104605B (zh) * 2020-08-10 2023-02-03 深信服科技股份有限公司 网络管理方法、设备及存储介质
CN112291343B (zh) * 2020-10-28 2022-11-22 成都知道创宇信息技术有限公司 信息获取方法、装置及电子设备
CN114827158A (zh) * 2021-01-18 2022-07-29 网宿科技股份有限公司 一种配置信息的加载方法、***及服务器
CN114448809A (zh) * 2021-12-22 2022-05-06 网宿科技股份有限公司 Cdn加速资源的规划方法、装置、设备及存储介质
CN115442331B (zh) * 2022-08-29 2023-11-03 天翼云科技有限公司 一种域名访问方法、装置、网络设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103391254A (zh) * 2012-05-09 2013-11-13 百度在线网络技术（北京）有限公司 用于分布式cdn的流量管理方法及装置
CN104660677A (zh) * 2015-01-16 2015-05-27 北京邮电大学 基于网格结构的树型cdn-p2p融合网络构架及方法
US20170331701A1 (en) * 2013-08-08 2017-11-16 Level 3 Communications, Llc Content delivery methods and systems

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030079027A1 (en) * 2001-10-18 2003-04-24 Michael Slocombe Content request routing and load balancing for content distribution networks
US7660296B2 (en) * 2005-12-30 2010-02-09 Akamai Technologies, Inc. Reliable, high-throughput, high-performance transport and routing mechanism for arbitrary data flows
CN101764747B (zh) * 2009-12-24 2012-05-02 北京云快线软件服务有限公司 内容分发网络流量智能调度方法、装置及***
US9282097B2 (en) * 2010-05-07 2016-03-08 Citrix Systems, Inc. Systems and methods for providing single sign on access to enterprise SAAS and cloud hosted applications
US9461996B2 (en) * 2010-05-07 2016-10-04 Citrix Systems, Inc. Systems and methods for providing a single click access to enterprise, SAAS and cloud hosted application
US9037712B2 (en) * 2010-09-08 2015-05-19 Citrix Systems, Inc. Systems and methods for self-loading balancing access gateways
WO2012064235A1 (en) * 2010-11-08 2012-05-18 Telefonaktiebolaget L M Ericsson (Publ) Traffic acceleration in mobile network
CN102668518B (zh) * 2011-12-02 2013-10-02 华为技术有限公司 一种内容分发网络路由方法、***和用户终端
CN105190557B (zh) * 2012-10-16 2018-09-14 思杰***有限公司 用于通过多级api集成在公共与私有云之间进行桥接的***和方法
US9160809B2 (en) * 2012-11-26 2015-10-13 Go Daddy Operating Company, LLC DNS overriding-based methods of accelerating content delivery
US9596299B2 (en) * 2013-04-06 2017-03-14 Citrix Systems, Inc. Systems and methods for dynamically expanding load balancing pool
US9577892B2 (en) * 2013-04-06 2017-02-21 Citrix Systems, Inc. Systems and methods for providing monitoring in a cluster system
CN104104610A (zh) * 2013-04-09 2014-10-15 江苏天联信息科技发展有限公司 基于域名***的流量调度方法、装置及域名***
US9396330B2 (en) * 2013-05-15 2016-07-19 Citrix Systems, Inc. Systems and methods for reducing denial of service attacks against dynamically generated next secure records
US9749148B2 (en) * 2013-07-31 2017-08-29 Citrix Systems, Inc. Systems and methods for load balancing non-IP devices
US9241044B2 (en) * 2013-08-28 2016-01-19 Hola Networks, Ltd. System and method for improving internet communication by using intermediate nodes
US9813343B2 (en) * 2013-12-03 2017-11-07 Akamai Technologies, Inc. Virtual private network (VPN)-as-a-service with load-balanced tunnel endpoints
CN103825975B (zh) * 2014-02-26 2018-03-13 北京六间房科技有限公司 Cdn节点分配服务器及***
US9621509B2 (en) * 2014-05-06 2017-04-11 Citrix Systems, Inc. Systems and methods for achieving multiple tenancy using virtual media access control (VMAC) addresses
CN104363313B (zh) * 2014-12-02 2018-09-18 网宿科技股份有限公司 使用内容分发网络的网站的资源使用率保障方法和***
US10129239B2 (en) * 2015-05-08 2018-11-13 Citrix Systems, Inc. Systems and methods for performing targeted scanning of a target range of IP addresses to verify security certificates
US10101981B2 (en) * 2015-05-08 2018-10-16 Citrix Systems, Inc. Auto discovery and configuration of services in a load balancing appliance
CN111831392A (zh) * 2015-05-19 2020-10-27 华为技术有限公司 一种硬件加速方法以及相关设备
CN105897822B (zh) * 2015-11-11 2019-07-26 法法汽车(中国)有限公司 一种内容分发网络cdn节点选择方法及其装置
CN106936856B (zh) * 2015-12-29 2019-10-22 中国电信股份有限公司 内容加速方法和延伸加速节点
US20170195237A1 (en) * 2015-12-30 2017-07-06 Akamai Technologies, Inc. Distributed quality-of-service (QoS) mechanism in an overlay network having edge regions
US10601703B2 (en) * 2015-12-30 2020-03-24 Akamai Technologies, Inc. Distributed quality-of-service (QoS) in an overlay network using capacity enforcement
US11025477B2 (en) * 2015-12-31 2021-06-01 Akamai Technologies, Inc. Overlay network ingress edge region selection
US10079877B2 (en) * 2016-02-04 2018-09-18 Citrix Systems, Inc. System and method for cloud aware application delivery controller
BR112018071151A2 (pt) * 2016-04-15 2019-02-05 Qualcomm Inc técnicas para gerenciar transmissões de conteúdo seguras em uma rede de entrega de conteúdo
US10484336B2 (en) * 2016-05-13 2019-11-19 Citrix Systems, Inc. Systems and methods for a unique mechanism of providing ‘clientless SSLVPN’ access to a variety of web-applications through a SSLVPN gateway
CN106230782A (zh) * 2016-07-20 2016-12-14 腾讯科技（深圳）有限公司 一种基于内容分发网络的信息处理方法及装置
US20180139230A1 (en) * 2016-11-15 2018-05-17 Level 3 Communications, Llc Identification and mitigation of attacks in a content delivery network (cdn)
US10728206B2 (en) * 2017-03-22 2020-07-28 Citrix Systems, Inc. Method for DNS response reordering based on path quality and connection priority for better QOS
US10778684B2 (en) * 2017-04-07 2020-09-15 Citrix Systems, Inc. Systems and methods for securely and transparently proxying SAAS applications through a cloud-hosted or on-premise network gateway for enhanced security and visibility
US10673805B2 (en) * 2017-09-29 2020-06-02 Level 3 Communications, Llc Dynamic binding and load determination in a content delivery network (CDN)
CN109660578B (zh) * 2017-10-11 2022-01-21 阿里巴巴集团控股有限公司 Cdn的回源处理方法及装置、***
CN109672698B (zh) * 2017-10-13 2021-02-09 华为技术有限公司 内容分发方法、设备及***
US11290765B2 (en) * 2018-02-06 2022-03-29 Akamai Technologies, Inc. Securing an overlay network against attack
US11418352B2 (en) * 2018-02-21 2022-08-16 Akamai Technologies, Inc. Certificate authority (CA) security model in an overlay network supporting a branch appliance
CN109286691B (zh) * 2018-09-30 2021-11-05 网宿科技股份有限公司 信息引流、请求发送、通信加速方法、引流及节点服务器
CN110198363B (zh) * 2019-05-10 2021-05-18 深圳市腾讯计算机***有限公司 一种移动边缘计算节点的选择方法、装置及***
CN110198307B (zh) * 2019-05-10 2021-05-18 深圳市腾讯计算机***有限公司 一种移动边缘计算节点的选择方法、装置及***
US11343185B2 (en) * 2019-05-20 2022-05-24 Citrix Systems, Inc. Network traffic steering with programmatically generated proxy auto-configuration files

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103391254A (zh) * 2012-05-09 2013-11-13 百度在线网络技术（北京）有限公司 用于分布式cdn的流量管理方法及装置
US20170331701A1 (en) * 2013-08-08 2017-11-16 Level 3 Communications, Llc Content delivery methods and systems
CN104660677A (zh) * 2015-01-16 2015-05-27 北京邮电大学 基于网格结构的树型cdn-p2p融合网络构架及方法

Also Published As

Publication number Publication date
US20220255894A1 (en) 2022-08-11
EP3989508A1 (en) 2022-04-27
CN110445886B (zh) 2020-11-06
CN110445886A (zh) 2019-11-12

Similar Documents

Publication Publication Date Title
WO2021003798A1 (zh) 一种实现域名访问加速的方法和***
CN110138606B (zh) 容器网络配置方法及***
US7587471B2 (en) System and method for virtualizing network storages into a single file system view
US8255420B2 (en) Distributed storage
JP5288334B2 (ja) 仮想アプライアンス配備システム
US8423581B2 (en) Proxy support for special subtree entries in a directory information tree using attribute rules
US10848468B1 (en) In-flight data encryption/decryption for a distributed storage platform
US8412901B2 (en) Making automated use of data volume copy service targets
CN111212134A (zh) 一种请求报文处理方法、装置、边缘计算***和电子设备
CN105745867A (zh) 用于在无线通信***中管理特定资源的方法和设备
CN109857723B (zh) 基于可扩容数据库集群的动态数据迁移方法及相关设备
WO2007134918A1 (en) Distributed storage
US9390156B2 (en) Distributed directory environment using clustered LDAP servers
CN113268308B (zh) 信息处理方法、装置以及存储介质
TW201724001A (zh) 全域資訊獲取、處理及更新方法、裝置和系統
JP2009296128A (ja) 情報処理装置、情報処理装置の制御方法及びコンピュータプログラム
US20100332592A1 (en) Data processing device and data retriever
JP3290801B2 (ja) 資源所在位置検出方式
CN113746641B (zh) 一种基于分布式存储的odx协议处理方法
CN114584545A (zh) 数据管理方法、装置、***、存储介质及电子设备
WO2011117921A1 (en) Method for concurrency control in a file versioning system
JP2001092641A (ja) ソフトウェアインストールシステム
JP2004151888A (ja) 端末装置の制御方法
US10621148B1 (en) Maintaining multiple object stores in a distributed file system
US7418488B1 (en) Network address assignment server with configuration updating capability

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19937051

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019937051

Country of ref document: EP

Effective date: 20220124