WO2011116726A2

WO2011116726A2 - Method and system for network caching, domain name system redirection sub-system thereof

Info

Publication number: WO2011116726A2
Application number: PCT/CN2011/073566
Authority: WO
Inventors: 杨长盛
Original assignee: 华为技术有限公司
Priority date: 2011-04-29
Filing date: 2011-04-29
Publication date: 2011-09-29
Also published as: CN102301682B; CN102301682A; WO2011116726A3

Abstract

The present invention provides a method and a system for network caching, a Domain Name System (DNS) redirection sub-system thereof. The method includes: receiving a DNS resolution request sent from a client, parsing out a domain name carried by the DNS resolution request, and determining that the domain name is in a white list; obtaining the Internet Protocol (IP) address of the cache sub-system corresponding to the domain name, and sending the IP address of the cache sub-system to the client to enable the client to request data from the cache sub-system according to the IP address of the cache sub-system. The embodiments of the present invention can avoid the problem of network caching based on the policy route.

Description

Network caching method and system and DNS redirection subsystem

Technical field

The present invention relates to network communication technologies, and in particular, to a network cache method and system, and a Domain Name System (DNS) redirection subsystem. Background technique

With the development of the Internet, Internet users will become more and more critical about the quality of their visits. On the one hand, they hope that the content provided by the website will become more and more abundant. On the other hand, they hope to access the website faster and faster. Since the network architecture of the network (Web) server is a point-to-multipoint transmission, the network transmission contains a large amount of duplicate content, and more than 80% of users frequently access 20% of the content, so the cache is the best solution to the above problem. Program. The Cache scheme caches the content frequently accessed by users on the cache server. The cache server provides services for users. It does not need to occupy the processing power of the source server and the egress bandwidth of the backbone, which can save resources and speed up access.

The existing caching scheme mainly includes a WebCache solution based on policy routing. The policy-based routing WebCache solution is to configure policy routing on the router to forward the HyperText Transfer Protocol (HTTP) request from the user to the Cache subsystem. In this solution, complex configuration changes need to be made to the router, which is difficult to maintain, and it is easy to generate a single point of failure at the router, and the reliability is low. Summary of the invention

The embodiments of the present invention provide a network caching method and system, and a DNS redirection subsystem, which are used to solve the problem of the prior art policy-based network caching scheme.

An embodiment of the present invention provides a network caching method, including: receiving a domain name system DNS resolution request sent by a client, parsing a domain name carried by the DNS resolution request, and determining that the domain name is in a white list; Obtaining an Internet Protocol IP address of the cache subsystem corresponding to the domain name, and sending the IP address of the cache subsystem to the client, so that the client sends the cache to the cache according to the IP address of the cache subsystem. The system requests data.

The embodiment of the invention provides a network cache system, which includes:

The domain name system DNS redirection subsystem is configured to receive a domain name system DNS resolution request sent by the client, parse the domain name carried by the DNS resolution request, determine that the domain name is in the white list, and obtain a cache subsystem corresponding to the domain name. An internet protocol IP address, and sending the IP address of the cache subsystem to the client, so that the client requests data from the cache subsystem according to the IP address of the cache subsystem; Receiving a data request message sent by the client according to an IP address of the cache subsystem, and sending data corresponding to the data request message to the client.

The embodiment of the present invention provides a DNS redirection subsystem, including: a deep packet parsing device, configured to receive a domain name system DNS resolution request sent by a client, parse the domain name carried by the DNS resolution request, and determine the domain name. In the white list;

a DNS server, configured to obtain an internet protocol IP address of a cache subsystem corresponding to the domain name, and send an IP address of the cache subsystem to the client, so that the client is configured according to the IP address of the cache subsystem Request data from the cache subsystem.

According to the foregoing technical solution, the network cache is implemented by the DNS redirection subsystem, which avoids the problem of network caching based on policy routing. The configuration is simple, difficult to maintain, and does not cause single point failure at the router. Sex is higher. DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, a brief description of the drawings to be used in the description of the embodiments will be briefly made. It is obvious that the drawings in the following description are the present invention. For some embodiments of the present invention, other drawings may be obtained from those skilled in the art without any inventive labor.

1 is a schematic flow chart of a method according to a first embodiment of the present invention;

2 is a schematic structural diagram of a system according to a second embodiment of the present invention;

3 is a schematic flow chart of a method according to a second embodiment of the present invention;

4 is a schematic structural diagram of a DNS redirection subsystem according to a second embodiment of the present invention; FIG. 5 is a schematic flowchart of a method for acquiring data from a source server by a cache subsystem according to an embodiment of the present invention; FIG. 6 is a flowchart of a third embodiment of the present invention. Schematic diagram of the process;

7 is a schematic flow chart of a method according to a fourth embodiment of the present invention;

8 is a schematic flow chart of a method according to a fifth embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a network cache system according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a DNS redirection subsystem according to an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

1 is a schematic flowchart of a method according to a first embodiment of the present invention, including: Step 11: A DNS redirection subsystem receives a DNS resolution request sent by a client, parses a domain name carried by the DNS resolution request, and determines that the domain name is white. In the list, the DNS redirection subsystem may receive the Internet access request, and the Internet access request may be a DNS resolution request. Because the DNS redirection subsystem processes the DNS resolution request, the DNS redirection subsystem parses the Internet access. After the request is resolved by the DNS, the subsequent processing is performed. Step 12: The DNS redirection subsystem acquires an IP address of the cache subsystem corresponding to the domain name, and sends an IP address of the cache subsystem to the client, so that the client can perform IP according to the cache subsystem. The address requests data from the cache subsystem.

In this embodiment, the network cache is implemented by the DNS redirection system, which can avoid network cache based on policy routing, and has high reliability, network delay time period, does not affect other service performance, and does not cause existing network topology. Under the condition of impact, it can save export bandwidth, reduce inter-network settlement, improve network utilization efficiency, reduce network operation cost, and enhance user experience. The embodiment shown in FIG. 1 is taken as an example in which the client obtains data from the cache subsystem. In a specific embodiment, the client may also obtain data from the source server instead of the cache subsystem. To this end, the present invention provides a Specific embodiment.

2 is a schematic structural diagram of a system according to a second embodiment of the present invention. Referring to FIG. 2, a client 21, a Domain Name System (DNS) redirection subsystem 22, a cache (Cache) subsystem 23, and an external network 24 including a source server are included. And the splitter (or router image) 25. The cache subsystem includes a load balancer and a network cache (WebCache) server, wherein, to improve reliability, the load balancer includes a primary load balancer and a backup load balancer. In addition, some routers and switches are included in the system.

Referring to the system architecture shown in Figure 2, the process of this embodiment can be as shown in Figure 3:

FIG. 3 is a schematic flowchart of a method according to a second embodiment of the present invention, including:

Step 31: The client sends an online request, and the online request includes the domain name requested by the client. Step 32: The optical splitter receives the above-mentioned online request, and sends the online request to the domain name system (DNS) redirection subsystem and the external network respectively.

The external network may include an external network DNS server and a source server, and the Internet request is parsed by the external network DNS server, and the IP address of the source server may be obtained, so that the client obtains the requirement from the source server according to the IP address of the source server. The data.

Step 33: The DNS redirection subsystem performs deep packet parsing on the online request (Deep

Packet Inspection, DPI), the Internet request can resolve the DNS for DNS resolution request Parsing the request and obtaining the domain name corresponding to the DNS resolution request. If the domain name is whitelisted in the DNS redirection subsystem, the IP address of the cache subsystem is obtained according to the domain name corresponding to the DNS resolution request, and the cache subsystem is The IP address is carried in the DNS response and returned to the client. If the domain name is not in the whitelist in the DNS redirection subsystem, the DNS resolution request is discarded.

Specifically, the whitelist may be configured in the DNS redirection subsystem, where the domain name of the hotspot network or the domain name of the contracted network is saved, and the domain name saved in the whitelist indicates that the content corresponding to the domain name is cached in the cache subsystem. The client can directly obtain the corresponding data in the cache subsystem. The whitelist can be manually configured in advance. The domain name saved in the whitelist can be the domain name of the hotspot network and/or the subscription network. The hotspot network is Refers to a network that has reached a certain number of times in a certain period of time (this specific time and a specific number of times can be set according to time). The contracted network refers to a network that has a service relationship with the DNS redirection subsystem, for example, a prior agreement of the A network. The data is cached, and the A network is a contracted network. If the domain name corresponding to the DNS resolution request is in the white list, the IP address of the cache subsystem corresponding to the domain name is searched. If the domain name corresponds to the unique cache subsystem, the IP address of the cache subsystem may be used. The bearer is returned to the client in the DNS response; if the domain name corresponds to multiple cache subsystems, the DNS redirection subsystem selects an IP address of a cache subsystem corresponding to the domain name according to the IP address selection algorithm, and returns to carry The DNS response of the IP address of the cache subsystem, for example, algorithms that can be selected according to priority include: Round-Trip Time (RTT) algorithm, Topology algorithm, and Global Availability algorithm . For example: The DNS server can select the RTT algorithm as the preferred algorithm for selecting the IP address of the cache subsystem corresponding to the domain name, that is, all DNS resolution requests are calculated by the DNS server to ensure the optimization of most user access, such as When there are multiple available cache subsystems corresponding to one DNS resolution request, the cache subsystem closest to the user who sent the DNS resolution request is selected as the corresponding cache subsystem as the cache subsystem accessed by the user. The Topology algorithm is used as a supplementary algorithm for RTT dynamic calculation. When there is no result in the RTT calculation mode, the cache subsystem on the local area network to which the user belongs is selected as the cache subsystem for user access. Global Availability algorithm as a system The default algorithm, which selects all DNS resolution requests that cannot be calculated and is not in the scope of Topology, selects the default cache subsystem of the DNS redirection subsystem as the cache subsystem for user access. If the domain name corresponding to the DNS resolution request does not exist in the whitelist, the DNS redirection subsystem does not process, discards the DNS resolution request, and does not return a DNS response to the client.

In addition, referring to FIG. 4, the DNS redirection subsystem may specifically include the DPI device 41 and the DNS server 42, and may also include some general-purpose devices, such as switches, and the DNS server may adopt an active/standby mode, for example, including a primary DNS. The server (DNS server - primary in Figure 4) and the alternate DNS server (DNS server in Figure 4 - standby). The DPI device is configured to perform DPI parsing on the received uplink request to obtain whether the Internet access request is a DNS resolution request. If it is a DNS resolution request, the DNS resolution request is parsed to obtain the carried domain name, and the domain name is sent to the DNS server. The DNS server can save the above-mentioned whitelist. If the domain name carried by the received DNS resolution request belongs to the whitelist, the IP address of the cache subsystem corresponding to the domain name carried in the DNS resolution request is determined. The cache subsystem IP address is then carried back to the client in the DNS response. Of course, if the domain name corresponding to the DNS resolution request is not in the whitelist, the DNS server may discard the DNS resolution request.

Further, the DNS server in the above DNS redirection subsystem can use the (Global Server Load Balance, GSLB) load balancing global server. The GSLB can be configured with a whitelist and a mapping table between the domain name and the IP address of the cache subsystem. If the domain name corresponding to the DNS resolution request is included in the whitelist, the domain name and the IP address of the cache subsystem are used. The correspondence table can obtain the IP address of the cache subsystem corresponding to the domain name. Of course, if the domain name corresponding to the DNS resolution request is not in the whitelist, the GSLB may discard the DNS resolution request.

Step 34: The external network responds to the online request, and carries the IP address of the source server in the DNS response and returns it to the client. The IP address of the source server may be parsed by the DNS server in the external network, and the IP address of the source server is found, and then the IP address of the source server is carried in the DNS response and returned to the client. Step 35: The client processes the received DNS response and discards the received DNS response. In general, the DNS redirection subsystem is closer to the user than the DNS server of the external network. Therefore, the DNS response returned by the DNS redirection subsystem reaches the client first, so the client will process the DNS response returned by the DNS redirection subsystem. That is, the DNS response returned by the DNS redirection subsystem takes effect. Since the DNS response of the DNS redirection subsystem takes effect, the client obtains the IP address of the cache subsystem. After that, the client can obtain data from the cache subsystem according to the IP address of the cache subsystem.

Of course, if the client may also receive the DNS response of the external network first, or only receive the DNS response of the external network, the client directly accesses the IP address of the source server included in the DNS response of the external network. The source server, and get data from the source server.

After receiving the IP address of the cache subsystem, the client sends a data query request to the cache subsystem, and the data query request may be a web request. If the data corresponding to the data query request is saved in the cache subsystem, the data is returned to the client.

In addition, the DNS redirection subsystem can also be used to provide resource scheduling. The resource scheduling function can implement whitelist update. For example, the DPI device can perform in-depth analysis on the DNS resolution request, and periodically generate a hotspot ranking table for the user to access the website domain name, for example, a hotspot website ranking that is generated by a user who generates an excel or a text format every week. table. In the system, the analysis results of DPI devices can be obtained periodically, and the analysis results of each DPI device are summarized, and the white list of the global load balancing server configuration is refreshed according to the analysis result, so as to improve the user's hit rate and speed up the user's access speed. Improve users' online experience and save Internet settlement.

In addition, the client side may further include a local DNS (Local DNS) server, where the mapping relationship between the domain name and the IP address of the cache subsystem may be recorded, so as to quickly determine the IP address of the cache subsystem corresponding to the DNS resolution request. .

In the foregoing step 31, when the client sends the Internet access request, the Internet access request is first sent to the local DNS server, and if the Local DNS server saves the correspondence table between the domain name and the cache subsystem IP address, and the relationship table is still valid, The local DNS server resolves the internet request Corresponding domain name, and looking up the IP address of the cache subsystem corresponding to the domain name. If the IP address of the cache subsystem corresponding to the domain name is unique, return the IP address of the cache subsystem to the client, and step 32- If the IP address of the cache subsystem corresponding to the domain name is multiple, the IP address of a cache subsystem corresponding to the domain name is selected according to the algorithm selected according to the priority, and is returned to the client. With the IP address of the cache subsystem, and steps 32-35 are skipped, no execution is required. If the local DNS server does not record the correspondence table of the domain name and the cache subsystem IP address or the record has expired, then go to step 32.

If the data corresponding to the data query request is not saved in the cache subsystem, the cache subsystem may obtain the data from the source server and then return the data to the client.

The data stored in the cache subsystem may be obtained from the source server. For example, the cache subsystem may obtain initial data from the source server, and then periodically obtain data from the source server for update. The flow of the cache subsystem to obtain data from the source server can be seen in the embodiment shown in FIG.

FIG. 5 is a schematic flowchart of a process for a cache subsystem to obtain data from a source server according to an embodiment of the present invention, including:

Step 51: The cache subsystem sends a data request message to the source server.

It may be that the cache subsystem periodically sends the data request message to the source server at a preset time point. Alternatively, the cache subsystem sends the data request message to the source server when receiving the request data sent by the client.

In addition, since there may be a router, an L3 switch, a load balancing device, etc. in the network cache system, the data request message may be sent by the cache subsystem to the source server via the L3 switch, the load balancing device, and the router.

Step 52: The source server sends the data corresponding to the data request message to the cache subsystem. Similarly, if there are routers, L3 switches, load balancing devices, etc. in the network cache system, the data can be sent by the source server to the source server via the router, load balancing device, and L3 switch.

Of course, depending on the composition of the network cache system, the devices through which the above paths pass may also be different. of.

In addition, a plurality of cache servers may be included in the cache subsystem for storing data of different source servers separately. The management platform can be used to determine the cache server corresponding to the source server. For example, the management platform includes a resource scheduling module, the resource scheduling module implements monitoring and management of the network node resources, and can also access the website, the hotspot area, or the hotspot period for the entire network. The analysis and statistics can also dynamically adjust and optimize the network resources for the hotspot analysis results, so that the cache server that is close to the source server of the hotspot access area caches the data accessed by the hotspot, and the physical distance is shortened, which can improve the user's Internet access. The experience also saves internet settlement costs.

At this point, the cache subsystem will store the data, and then the corresponding data can be returned according to the client's request. Of course, the data requested by the client may be saved in the cache subsystem, and may not be saved. The following two scenarios are respectively described in FIG. 6 and FIG. 7 below.

FIG. 6 is a schematic flowchart of a method according to a third embodiment of the present invention. In this embodiment, the data requested by the client in the cache subsystem is saved as an example. Referring to FIG. 8, the embodiment includes:

Step 61: The client sends a DNS resolution request to the DNS redirection subsystem.

Step 62: The DNS redirection subsystem carries the IP address of the cache subsystem in the DNS response and sends it to the client.

For the specific DNS redirection subsystem processing procedure, refer to the corresponding embodiment in FIG. 3.

Step 63: The client sends a data query request to the cache subsystem according to the IP address of the cache subsystem.

Step 64: If the data corresponding to the data query request is saved in the cache subsystem, the data is returned to the client.

Similarly, if the network cache system includes a router, an L3 switch, etc., the client may send a data query request to the cache subsystem via the router and the L3 switch; accordingly, the cache subsystem sends the data to the L3 switch and the router. Client.

In addition, the load balancing device and the cache server may be included in the cache subsystem, and the load balancing device is configured to manage each cache server, and can learn the load status of each cache server. After that, when After receiving the data query request sent by the client, the load balancing device may send the received data query request to the cache server with a light load according to the load condition of each cache server, and the cache server processes the data and returns the data to the client. end.

FIG. 7 is a schematic flowchart of a method according to a fourth embodiment of the present invention. In this embodiment, the data in the cache subsystem that does not save the client request is used as an example. Referring to FIG. 7, this embodiment includes:

Step 71: The client sends a DNS resolution request to the DNS redirection subsystem.

Step 72: The DNS redirection subsystem carries the IP address of the cache subsystem in the DNS response and sends it to the client.

For the specific DNS redirection subsystem processing procedure, refer to the above embodiment.

Step 73: The client sends a data query request to the cache subsystem according to the IP address of the cache subsystem.

Step 74: If the data corresponding to the data query request is not saved in the cache subsystem, the data query request is forwarded to the source server.

Step 75: The source server returns data corresponding to the data query request to the cache subsystem.

Step 76: The cache subsystem sends the data returned by the source server to the client.

In addition, after the cache subsystem obtains data from the source server, it can save the acquired data itself, so that the corresponding data can be provided when the client requests the next time.

Similarly, if the system includes a router, an L3 switch, etc., the client may send a data query request to the cache subsystem via the router and the L3 switch; accordingly, the cache subsystem sends the data to the client via the L3 switch and the router. .

In addition, the load balancing device and the cache server may be included in the cache subsystem, and the load balancing device is configured to manage each cache server, and can learn the load status of each cache server. Then, after receiving the data query request sent by the client, the load balancing device may send the received data query request to the cache server with a light load according to the load condition of each cache server, and the cache server processes the data.

In the embodiment shown in Figures 6 and 7, the DNS redirection subsystem is capable of returning to the cache subsystem. For example, the IP address of the DNS redirection subsystem stores the domain name corresponding to the DNS resolution request. If the domain name corresponding to the DNS resolution request is not saved in the whitelist, the embodiment shown in Figure 8 can be performed. deal with.

FIG. 8 is a schematic flowchart of a method according to a fifth embodiment of the present invention. In this embodiment, a domain name corresponding to a DNS resolution request is not stored in the DNS redirection subsystem. For example, as shown in FIG. 8, the embodiment includes: Step 81: Client to The DNS redirection subsystem and the external network DNS server send DNS resolution requests.

Referring to the foregoing embodiment, after the client sends the DNS resolution request, the DNS resolution request is split into two paths through the optical splitter, and is sent to the DNS redirection subsystem and the other to the external network DNS server.

Step 82: The DNS redirection subsystem discards the received DNS resolution request.

The whitelist is saved in the DNS redirection subsystem. If the domain name corresponding to the received DNS resolution request is not in the whitelist, the DNS redirection subsystem cannot provide the IP address of the cache subsystem. In this case, the DNS redirector The system discards the DNS resolution request.

Step 83: The external network DNS server carries the IP address of the source server in the DNS response and returns it to the client.

The external network DNS server stores the mapping between the domain name and the IP address of the source server. According to the domain name corresponding to the DNS resolution request, the IP address of the source server can be obtained. Then, the IP address of the source server is carried in the DNS response. To the client.

Step 84: The client sends a data query request to the source server according to the IP address of the source server. Step 85: The source server sends the data corresponding to the data query request to the client.

Of course, if the system includes a router, the client may send a data query request to the source server via the router, and then the source server sends data to the client via the router.

In the above embodiment, by setting the DNS redirection subsystem separately, transparent deployment and zero impact on the live network can be achieved. DPI device bypass deployment, no single point of failure. There is no need to handshake with the source server three times, no network delay, and no impact on other service performance. In addition, key modules can be fully redundant For example, GSLB and switch adopt 1+1 backup mode, load balancing module can also adopt 1+1 backup mode, and network cache server (WebCache) can use homogeneous node dynamic backup technology to ensure high availability of the entire solution. . Resource scheduling can be used to dynamically divide user traffic to ensure that the Web Cache system is not overloaded. The association between the GSLB and the load balancing device in the cache subsystem can be configured, so that the GSLB can receive the number of healthy network cache devices reported by the load balancing device in the cache subsystem, so that when the cache subsystem fails or the processing capability is insufficient. The GSLB first guarantees the DNS resolution request of the high-level website, and the DNS resolution request of the low-priority website is no longer processed, and the traffic is dynamically offloaded. FIG. 9 is a schematic structural diagram of a network cache system according to an embodiment of the present invention, including a DNS redirection subsystem 901 and a cache subsystem 902. The DNS redirection subsystem 901 is configured to receive a domain name system DNS resolution request sent by a client, and parse the Defining the domain name carried in the DNS resolution request, determining that the domain name is in the white list; obtaining an internet protocol IP address of the cache subsystem corresponding to the domain name, and sending the IP address of the cache subsystem to the client, so that The client requests data from the cache subsystem according to the IP address of the cache subsystem; the cache subsystem 902 is configured to receive a data request message sent by the client according to the IP address of the cache subsystem, and The client sends data corresponding to the data request message.

The cache subsystem 902 is specifically configured to receive a data request message sent by the client; if the cache subsystem has data corresponding to the data request message, the cache subsystem caches the data The data corresponding to the request message is sent to the client; if the data corresponding to the data request message is not cached in the cache subsystem, the cache subsystem sends a data request message for querying data to the source server. The cache subsystem receives data corresponding to the data request message of the query data returned by the source server, and the cache subsystem saves the data locally and sends the data to the client.

The cache subsystem 902 is further configured to: the cache subsystem acquires data from the source server according to a refresh policy, and updates the cached data. The system may further include: a splitter or a router, configured to divide the Internet access request sent by the client into two paths, send the same to the DNS redirection subsystem, and send the other path to the external network. In this embodiment, the network cache is implemented by the DNS redirection system, which can avoid network caching based on policy routing, and has high reliability, no network delay, does not affect other service performance, and does not affect the existing network topology. Under the condition, it can save export bandwidth, reduce inter-network settlement, improve network utilization efficiency, reduce network operation cost, and enhance user experience. FIG. 10 is a schematic structural diagram of a DNS redirection subsystem according to an embodiment of the present invention, including a DPI device 1001 and a DNS server 1002. The DPI device 1001 is configured to receive a domain name system DNS resolution request sent by a client, and parse the DNS resolution request to carry The domain name is determined to be in the whitelist; the DNS server 1002 is configured to obtain an internet protocol IP address of the cache subsystem corresponding to the domain name, and send the IP address of the cache subsystem to the client, so as to The client requests data from the cache subsystem according to the IP address of the cache subsystem. The DPI device 1001 may be further configured to perform in-depth analysis on the received DNS resolution request to generate a hotspot website for updating the whitelist.

The DNS server 1002 may be specifically configured to acquire an IP address of the unique cache subsystem if the domain name corresponds to an IP address of a unique cache subsystem; and if the domain name corresponds to an IP address of two or more cache subsystems, according to the IP address The address selection algorithm selects an IP address of the adapted cache subsystem as the Internet Protocol IP address of the cache subsystem corresponding to the domain name. The DNS server 1002 can be a GSLB.

In this embodiment, the network cache is implemented by the DNS redirection system, which can avoid network caching based on policy routing, and has high reliability, no network delay, does not affect other service performance, and does not affect the existing network topology. Under the condition, it can save export bandwidth, reduce inter-network settlement, improve network utilization efficiency, reduce network operation cost, and enhance user experience.

It can be understood that related features in the above methods and devices can be referred to each other. In addition, the "first", "second", and the like in the above embodiments are used to distinguish the embodiments, and do not represent the actual The advantages and disadvantages of the example.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A network caching method, comprising: receiving a domain name system DNS resolution request sent by a client, parsing a domain name carried in the DNS resolution request, determining that the domain name is in a white list; and obtaining the domain name corresponding The internet protocol IP address of the cache subsystem, and the IP address of the cache subsystem is sent to the client, so that the client requests data from the cache subsystem according to the IP address of the cache subsystem.

The method of claim 1, wherein the obtaining the Internet Protocol IP address of the cache subsystem corresponding to the domain name further includes:

If the domain name corresponds to the IP address of the unique cache subsystem, obtain the IP address of the unique cache subsystem;

If the domain name corresponds to the IP addresses of the two or more cache subsystems, according to the IP address selection algorithm, an IP address of the adapted cache subsystem is selected as the Internet Protocol IP address of the cache subsystem corresponding to the domain name.

The method according to any one of claims 1 and 2, wherein the method further comprises: discarding the DNS resolution request if it is determined that the domain name carried by the DNS resolution request is not in the whitelist.

The method according to any one of claims 1 to 3, wherein the method further comprises: the client sending a DNS resolution request, where the DNS resolution carries a domain name;

The DNS resolution request is sent to the external network and the DNS redirection subsystem via a splitter or router;

The client receives a DNS response returned by the external network and the DNS redirection subsystem, and the DNS response returned by the external network carries the source server IP address corresponding to the domain name, and the DNS redirection subsystem returns The DNS response carries the IP address of the cache subsystem, and the client processes the DNS response received first, and then receives the DNS response drop.

The method according to any one of claims 1 to 4, wherein the method further comprises: performing an in-depth analysis on the received DNS resolution request to generate a hotspot website for updating the whitelist.

A domain name system DNS redirection subsystem, comprising: a deep packet parsing device, configured to receive a domain name system DNS resolution request sent by a client, parse the domain name carried by the DNS resolution request, determine a location The domain name is in the white list;

The DNS redirection subsystem of the domain name system according to claim 6, wherein the deep packet parsing device is further configured to perform in-depth analysis on the received DNS resolution request to generate a hotspot website for updating the whitelist. .

The DNS redirection subsystem of the domain name system according to claim 6 or 7, wherein the DNS server is specifically configured to acquire the unique cache if the domain name corresponds to an IP address of a unique cache subsystem. The IP address of the system; if the domain name corresponds to the IP address of more than two cache subsystems, according to the IP address selection algorithm, an IP address of the adapted cache subsystem is selected as the Internet Protocol IP of the cache subsystem corresponding to the domain name. address.

A network cache system, comprising: a domain name system DNS redirection subsystem, configured to receive a domain name system DNS resolution request sent by a client, parse a domain name carried by the DNS resolution request, and determine the domain name In the whitelist, obtaining an internet protocol IP address of the cache subsystem corresponding to the domain name, and sending the IP address of the cache subsystem to the client, so that the client is configured according to the IP address of the cache subsystem. Requesting data from the cache subsystem; a cache subsystem, configured to receive a data request message sent by the client according to an IP address of the cache subsystem, and send, to the client, a data request message corresponding to the data request message data.

The network cache system according to claim 9, wherein the cache subsystem is specifically configured to receive a data request message sent by the client; if the cache subsystem has a cache and the data request The data corresponding to the message, the cache subsystem sends the cached data corresponding to the data request message to the client; if the data corresponding to the data request message is not cached in the cache subsystem, The cache subsystem sends a data request message for querying data to the source server, and the cache subsystem receives data corresponding to the data request message of the query data returned by the source server, where the cache subsystem is locally saved. The data is then sent to the client.

The system according to claim 9 or 10, wherein the cache subsystem is further configured to acquire data from the source server according to the refresh policy, and update the cached data.

The system according to any one of claims 9 to 11, further comprising: a splitter or a router, configured to divide the DNS resolution request sent by the client into two paths, and send the method to the The DNS redirects the subsystem and sends another route to the external network.