CN114500460B - CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN - Google Patents
CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN Download PDFInfo
- Publication number
- CN114500460B CN114500460B CN202111617599.XA CN202111617599A CN114500460B CN 114500460 B CN114500460 B CN 114500460B CN 202111617599 A CN202111617599 A CN 202111617599A CN 114500460 B CN114500460 B CN 114500460B
- Authority
- CN
- China
- Prior art keywords
- node
- request
- layer
- domain name
- parent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000012384 transportation and delivery Methods 0.000 title description 3
- 238000013439 planning Methods 0.000 claims abstract description 48
- 238000004891 communication Methods 0.000 claims abstract description 19
- 230000003068 static effect Effects 0.000 claims description 10
- 238000013507 mapping Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an automatic dispatching method for CDN network and node return upper layer request thereof, comprising the following steps: the system comprises a resource planning system, a configuration system, a cache system and a scheduling system, wherein the resource planning system, the configuration system, the scheduling system and the cache system are in communication connection; the resource planning system is used for marking the resources, dividing the resource planning into multiple layers of nodes, and the scheduling system generates DNS configuration and deploys the DNS configuration to the internal DNS server; the configuration system transmits the IP of the recursive DNS software to the cache server and provides domain name and source returning information; and each node of the cache system sequentially initiates a plurality of requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and the scheduling system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP of the parent domain name or obtains a source domain name and a source resource IP.
Description
Technical Field
The invention relates to the field of CDN scheduling, in particular to an automatic scheduling method for CDN network and a node return upper layer request thereof.
Background
CDN nodes are divided into edge nodes and middle layer nodes, the middle layer nodes can be divided into multiple layers, and the current CDN system returns to the middle father layer and the source is write dead IP on the cache configuration. If the father layer node needs to be scheduled to adjust the source station IP, manual adjustment configuration is needed, and the configuration is issued to the cache server. The operation and maintenance operation risks are large, and deployment pressure is large when the number of the issuing machines reaches tens of thousands or even tens of thousands along with the increase of the edge and middle layer cache server nodes. And with the increase of clients, great challenges are brought to the maintenance cost and parent layer planning of the configuration, and huge manpower is required to be input for maintenance and operation.
Disclosure of Invention
Therefore, the technical problem to be solved by the invention is to overcome the defect that the CDN network in the prior art needs to put in huge manpower and cost in the process of deployment, maintenance and scheduling, thereby providing an automatic scheduling method for the CDN network and the node return upper layer request thereof.
In order to achieve the above purpose, the present invention provides the following technical solutions:
In a first aspect, an embodiment of the present invention provides a CDN network, including: the system comprises a resource planning system, a configuration system, a cache system and a scheduling system, wherein the resource planning system, the configuration system, the scheduling system and the cache system are in communication connection; the resource planning system is used for marking the resources and dividing the resource planning into multi-level nodes; the dispatching system generates DNS configuration to be deployed in a DNS server in the dispatching system; the configuration system transmits the IP of the recursive DNS software to the cache server and provides domain name and source returning information; and each node of the cache system sequentially initiates a plurality of requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and the scheduling system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP of the parent domain name or obtains a source domain name and a source resource IP.
In one embodiment, a multi-level node includes: edge node, middle one-layer father node and middle two-layer father node.
In one embodiment, a cache system includes: the system comprises an edge node cache server, a first-layer father node cache server and a second-layer father node cache server which are sequentially connected in a communication way, wherein the edge node cache server is used for sending multiple requests to a dispatching system according to domain names requested by users and returning to an upper-layer node IP according to response information of the dispatching system; the parent node server of one layer is used for sending multiple requests to the dispatching system again according to the upper layer node IP returned by the edge node cache server, and returning to the upper layer node IP according to the response information of the dispatching system; the two-layer father node server is used for sending multiple requests to the dispatching system again according to the last layer node IP returned by the one-layer father node server, and returning to the client source station according to the response information of the dispatching system.
In one embodiment, a scheduling system includes: the system comprises an edge node recursive DNS, a first-layer parent node recursive DNS, a second-layer parent node recursive DNS, a first authority DNS, a second authority DNS and a GSLB scheduling system, wherein the edge node recursive DNS, the first-layer parent node recursive DNS and the second-layer parent node recursive DNS are correspondingly in communication connection with an edge node cache server, a first-layer parent node cache server and a second-layer parent node cache server respectively; the edge node recursive DNS, the first-layer parent node recursive DNS and the second-layer parent node recursive DNS and the GSLB scheduling system are also in communication connection with the resource planning system; the second authoritative DNS is in communication connection with the GSLB scheduling system; the edge node recursive DNS and the first-layer father node recursive DNS and the second-layer father node recursive DNS are respectively used for sending requests to the first authority DNS and the second authority DNS according to multiple requests sent by the edge node cache server, the first-layer father node cache server and the second-layer father node cache server; ; the first authority DNS and the second authority DNS respond to the optimal answer according to the request sent by the recursive DNS, and send the optimal answer to the corresponding cache server through the corresponding recursive DNS.
In one embodiment, a resource planning system includes: the system comprises an RAP resource application planning module and a DCP static coverage planning module, wherein the RAP resource application planning module is respectively in communication connection with the DCP static coverage planning module and a configuration system; the RAP resource application planning module is used for providing information of a parent layer group and hierarchical information; the DCP static coverage planning module generates back source information based on the client source configuration; generating coverage of the corresponding parent layer domain name according to the parent layer group information; the configuration system issues the IP of the recursive DNS software to the caching server based on the hierarchy information.
In a second aspect, an embodiment of the present invention provides an automatic scheduling method for a node return upper layer request of a CDN network, where the scheduling method includes: and each node of the cache system sequentially initiates a plurality of requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and the scheduling system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP of the parent domain name or obtains a source domain name and a source resource IP.
In an embodiment, each node of the cache system sequentially initiates a process of multiple requests to the scheduling system according to a preset rule according to a domain name requested by a user or response information of the scheduling system, including: the edge node server sends an SRV request to the dispatching system according to the domain name of the user request; the scheduling system returns the corresponding parent-returning domain name to the edge node server based on the SRV request; the edge node server sends an A request to the dispatching system again according to the parent domain name; the scheduling system returns the corresponding parent returning resource IP to the edge node server based on the A request; the edge node server returns a corresponding layer of father node based on the father returning resource IP, and the father layer of father node server sends an SRV request to the dispatching system based on the father returning resource IP returned by the edge node server; the scheduling system returns the corresponding parent-returning domain name to a layer of parent node servers based on the SRV request; the parent node server of the one layer sends an A request to the dispatching system again according to the parent domain name; the scheduling system returns the corresponding parent returning resource IP to a layer of parent node servers based on the A request; the first-layer father node returns to the corresponding second-layer father node based on the returned father resource IP, and the second-layer father node server sends an SRV request to the dispatching system based on the returned father resource IP returned by the first-layer father node server; the scheduling system returns the corresponding back source domain name to the two-layer father node server based on the SRV request; the two-layer father node server sends an A request to the dispatching system again according to the source-returning domain name; the scheduling system returns the corresponding back source resource IP to the corresponding client source station based on the a request.
In one embodiment, the process of responding to the SRV request and the A request by the authoritative DNS comprises the following steps: the recursive DNS sends an SRV record request of the domain name to the first authority DNS based on the received SRV request of the domain name; the first authority DNS returns corresponding SRV records to the cache server through the recursive DNS based on the SRV record request, wherein the SRV records comprise a parent domain name or a source resource IP; the recursive DNS sends an A record request of the domain name to the second authority DNS based on the received A request of the domain name; the second authoritative DNS returns corresponding a records to the cache server through recursive DNS based on the a record request, the a records including the back parent resource IP or the back source resource IP.
In one embodiment, an edge node area, a first-layer father node area and a second-layer father node area are planned in advance; configuring an SRV mapping relation of ctup.com of each node; the a records of ctup.com and ctfu.com for each node are configured.
In one embodiment, the SRV request resolution and the a request resolution each include: the request type and the hierarchy to which the carried edns belongs.
The technical scheme of the invention has the following advantages:
1. The CDN provided by the invention comprises the following steps: the system comprises a resource planning system, a configuration system, a cache system and a scheduling system, wherein the resource planning system, the configuration system, the scheduling system and the cache system are in communication connection; the resource planning system is used for marking the resources and dividing the resource planning into multi-level nodes; the dispatching system generates DNS configuration to be deployed in a DNS server in the dispatching system; the configuration system transmits the IP of the recursive DNS software to the cache server and provides domain name and source returning information; and each node of the cache system sequentially initiates a plurality of requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and the scheduling system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP of the parent domain name or obtains a source domain name and a source resource IP.
2. According to the CDN provided by the invention, the CDN architecture increases the request of the back intermediate father layer node, and reduces the back source pressure; and the operation work of manually maintaining back to the upper layer configuration is avoided based on the resource planning of the platform. The GSLB automatic dispatching system identifies node attribution and automatically dispatches to the intermediate father layer node or the return source; the cache server does not need to receive the upper layer configuration (middle layer IP/domain name and source IP/domain name) of the customer domain name, so that the function realization and the operation are simplified; the cache server requests according to the information of the DNS protocol SRV supporting priority, weight, port, upper domain name and the like; authoritative DNS software only needs to receive the GSLB scheduling result, and does not need to be customized and developed; the recursive DNS server is shared with the management server inside the node without adding a server.
3. According to the automatic dispatching method for the node return upper layer request of the CDN, each node of the cache system sequentially initiates multiple requests to the dispatching system according to the domain name requested by the user or the response information of the dispatching system and the preset rule, the dispatching system responds to the cache system optimally based on the request content, and the cache system obtains the return parent resource IP of the return parent domain name or obtains the return source domain name and the return source resource IP.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a composition diagram of a specific example of a CDN network according to an embodiment of the present invention;
FIG. 2 is a configuration flow chart executed by the configuration system according to the embodiment of the present invention;
Fig. 3 is a composition diagram of another specific example of a CDN network according to an embodiment of the present invention;
FIG. 4 is a flowchart of a specific example of a scheduling method according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a cache server return upper layer request method according to an embodiment of the present invention;
FIG. 6 is a flowchart of another specific example of a scheduling method according to an embodiment of the present invention;
FIG. 7 is a flowchart of another specific example of a scheduling method according to an embodiment of the present invention;
Fig. 8 is a flow chart of client request provided in an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made apparent and fully in view of the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the description of the present invention, it should be noted that the directions or positional relationships indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. are based on the directions or positional relationships shown in the drawings, are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be either fixedly connected, detachably connected, or integrally connected, for example; can be mechanically or electrically connected; the two components can be directly connected or indirectly connected through an intermediate medium, or can be communicated inside the two components, or can be connected wirelessly or in a wired way. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
In addition, the technical features of the different embodiments of the present invention described below may be combined with each other as long as they do not collide with each other.
Example 1
An embodiment of the present invention provides a CDN network, including: the system comprises a resource planning system 1, a configuration system 2, a cache system 3 and a scheduling system 4, wherein the resource planning system 1, the configuration system 2, the scheduling system 4 and the cache system 3 are in communication connection.
The resource planning system 1 of the embodiment of the present invention is used for labeling resources, dividing the resource into multiple levels of nodes, generating DNS configuration by the scheduling system 4 and deploying the DNS configuration into an internal DNS server, where the multiple levels of nodes include: the edge nodes, the middle first-layer father nodes and the middle second-layer father nodes are to be noted, and the multi-level nodes in the embodiment of the invention are not limited to three-layer nodes, can be divided according to actual conditions, and are not limited herein.
The configuration system 2 of the embodiment of the invention issues the IP of the recursive DNS software to the cache server and provides domain name and back source information; specifically, as shown in fig. 3, the configuration system includes a global configuration and a domain name channel configuration, where the domain name channel configuration provides domain name and source information, and the global configuration issues IP of the recursive DNS software to the cache server.
Specifically, the scheduling system 4 includes, but is not limited to, a plurality of recursive DNS software, and the cache system 3 includes, but is not limited to, a plurality of cache servers, and one recursive DNS software and one cache server are responsible for transmission of requests initiated by a class of nodes.
Specifically, the embodiment of the invention adds an HTTP interface in the configuration system 2 to provide the mapping relation from the full customer domain name to the back source domain name. As shown in fig. 2, the DCP of the resource planning system 1 newly adds a time task and pulls the data file from the configuration system 2. And if the pulled back source domain name is of the IP type, generating a layer domain name resolution configuration. Examples of the conversion are shown in table 1.
TABLE 1
According to the method and the system, each node of the cache system 3 initiates a plurality of requests to the dispatch system 4 according to the domain name requested by the user or the response information of the dispatch system 4 in sequence according to preset rules, the dispatch system 4 responds to the cache system 3 optimally based on the request content, and the cache system 3 obtains the back father resource IP of the back father domain name or obtains the back source domain name and the back source resource IP.
Specifically, in the embodiment of the invention, upper and lower levels are formed among the multi-layer nodes, and in the process of returning the nodes to the upper layer request, the edge node, the intermediate first-layer father node and the intermediate second-layer father node send requests to the dispatching system 4 in sequence, and the dispatching system 4 outputs corresponding answers based on the request content.
In one embodiment, as shown in FIG. 3, the cache system includes: the edge node cache servers (namely the edge node cache service in fig. 3), the one-layer parent node cache servers (namely the one-layer parent node cache service in fig. 3) and the two-layer parent node cache servers (namely the two-layer parent node cache service in fig. 3) which are connected in sequence in a communication mode.
Specifically, the edge node cache server is used for sending multiple requests to the dispatching system according to the domain name requested by the user, and returning to the upper node IP according to the response information of the dispatching system; the parent node server of one layer is used for sending multiple requests to the dispatching system again according to the upper layer node IP returned by the edge node cache server, and returning to the upper layer node IP according to the response information of the dispatching system; the two-layer father node server is used for sending multiple requests to the dispatching system again according to the last layer node IP returned by the one-layer father node server, and returning to the client source station according to the response information of the dispatching system.
Specifically, an edge node cache server, a first-layer father node cache server and a second-layer father node cache server form an upper level and a lower level, in the process of returning an upper layer request from a node, the edge node cache server, the first-layer father node cache server and the second-layer father node cache server sequentially send SRV requests and A requests to a dispatching system, and the dispatching system outputs corresponding answers based on request contents, wherein for the SRV requests, answer information of the dispatching system comprises a return father domain name or a return source domain name, and for the A requests, answer information of the dispatching system comprises a return father resource IP or a return source resource IP.
Specifically, the caching software of the embodiment of the present invention may be, but not limited to, nmginx+ ats to provide caching services and return upper layer requests.
In one embodiment, as shown in FIG. 3, the scheduling system includes: edge node recursive DNS (i.e., leftmost recursive DNS in fig. 3), one level parent node recursive DNS (i.e., middlemost recursive DNS in fig. 3), two levels of parent node recursive DNS (i.e., rightmost recursive DNS in fig. 3), first authoritative DNS (i.e., recursive DNS in fig. 3 for responding to a first request), second authoritative DNS (i.e., recursive DNS in fig. 3 for responding to a second request), and a GSLB scheduling system.
As shown in fig. 3, the edge node recursive DNS, the first-layer parent node recursive DNS and the second-layer parent node recursive DNS are respectively in corresponding communication connection with the edge node cache server, the first-layer parent node cache server and the second-layer parent node cache server; the edge node recursion DNS, the first-layer father node recursion DNS and the second-layer father node recursion DNS and the GSLB scheduling system are also all in communication connection with a resource planning system (DCP static coverage planning module); the second authoritative DNS is communicatively coupled to the GSLB dispatch system.
Specifically, the edge node recursive DNS, the first layer parent node recursive DNS and the second layer parent node recursive DNS are respectively used for sending requests to the first authoritative DNS and the second authoritative DNS according to multiple requests sent by the edge node cache server, the first layer parent node cache server and the second layer parent node cache server; the first authority DNS and the second authority DNS respond to the optimal answer according to the request sent by the recursive DNS, and send the optimal answer to the corresponding cache server through the corresponding recursive DNS.
Specifically, the first request in fig. 3 is an SRV request, the second request is an a request, and the two authoritative DNS make the best answer based on the received request.
In one embodiment, as shown in FIG. 3, the resource planning system includes: the system comprises a RAP resource application planning module and a DCP static coverage planning module, wherein the RAP resource application planning module is respectively in communication connection with the DCP static coverage planning module and a configuration system.
Specifically, the RAP resource application planning module is used for providing information of a parent layer group and hierarchy information; the DCP static coverage planning module generates back source information based on the client source configuration; generating coverage of the corresponding parent layer domain name according to the parent layer group information; the configuration system issues the IP of the recursive DNS software to the caching server based on the hierarchy information.
Example 2
The embodiment of the invention provides an automatic dispatching method for a node return upper layer request of a CDN (content delivery network), which is based on the CDN of embodiment 1 and comprises the following steps: and each node of the cache system sequentially initiates a plurality of requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and the scheduling system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP of the parent domain name or obtains a source domain name and a source resource IP.
Specifically, upper and lower levels are formed among the multi-layer nodes in the embodiment of the invention, and in the process of returning the nodes to the upper layer request, the edge node, the intermediate first-layer father node and the intermediate second-layer father node send requests to a dispatching system in sequence, and the dispatching system outputs corresponding answers based on request contents.
Specifically, the scheduling method provided by the embodiment of the present invention is based on the CDN network of embodiment 1, where the scheduling system selects and decides an optimal upper node according to the planned resources, generates DNS configuration, and deploys the DNS configuration to DNS software. The configuration system issues the IP of the recursive DNS software to the caching software, the caching software initiates a request to the recursive DNS according to a preset rule and the recursive DNS initiates an authoritative DNS according to a DNS protocol according to the domain name requested by a user. The authoritative DNS responds to the best answer according to the attribution of the visiting cache server. And the lower cache server initiates a request to the upper cache server according to the information such as IP, weight and the like of the DNS response, so that automatic scheduling is realized.
In a specific embodiment, as shown in fig. 4, each node of the cache system sequentially initiates a process of multiple requests to the scheduling system according to a preset rule according to a domain name requested by a user or response information of the scheduling system, including:
Step S11: the edge node server sends an SRV request to the dispatching system according to the domain name of the user request; the scheduling system returns the corresponding parent-returning domain name to the edge node server based on the SRV request; the edge node server sends an A request to the dispatching system again according to the parent domain name; the dispatch system returns the corresponding parent back resource IP to the edge node server based on the a request.
Step S12: the edge node server returns a corresponding layer of father node based on the father returning resource IP, and the father layer of father node server sends an SRV request to the dispatching system based on the father returning resource IP returned by the edge node server; the scheduling system returns the corresponding parent-returning domain name to a layer of parent node servers based on the SRV request; the parent node server of the one layer sends an A request to the dispatching system again according to the parent domain name; the scheduling system returns the corresponding parent return resource IP to a layer of parent node servers based on the a request.
Step S13: the first-layer father node returns to the corresponding second-layer father node based on the returned father resource IP, and the second-layer father node server sends an SRV request to the dispatching system based on the returned father resource IP returned by the first-layer father node server; the scheduling system returns the corresponding back source domain name to the two-layer father node server based on the SRV request; the two-layer father node server sends an A request to the dispatching system again according to the source-returning domain name; the scheduling system returns the corresponding back source resource IP to the corresponding client source station based on the a request.
Specifically, each node in the embodiment of the invention sends two requests to a dispatching system, namely an SRV request and an A request, wherein the authority software judges which SRV record is to be returned specifically based on the SRV request and the carried level to which edns belongs, and the authority software judges which A record is to be returned specifically based on the A request and the carried level to which edns belongs, and the SRV record obtains a parent domain name or a source domain name.
It should be noted that, the embodiment of the present invention sets three layers of nodes: the edge node, the middle first-layer father node and the middle second-layer father node are sequentially sent by the edge node, the middle first-layer father node and the middle second-layer father node, but in order to reduce the dispatching pressure, four layers and more than four layers of nodes can be arranged, but the dispatching method provided by the embodiment of the invention can be used, and the method is not limited.
Specifically, as shown in fig. 5, the return between the hierarchies is www.abc.com.ctup.com in the www.abc.com +ctyun.com embodiment, and as can be seen from fig. 5, the NS analysis is forwarded to NGINX, and the gateway records the return source and parent of the ATS through the SRV record and the a record of the headband. The gateway carries the hierarchy and whether the source-back identification header is passed to the ATS, which uses different configuration logic depending on the hierarchy to which it belongs and whether it is the source-back/parent.
In one embodiment, as shown in fig. 6, the process of responding to the SRV request and the a request by the authoritative DNS includes:
Step S21: the recursive DNS sends an SRV record request of the domain name to the first authority DNS based on the received SRV request of the domain name; the first authoritative DNS returns corresponding SRV records to the cache server via recursive DNS based on the SRV record request, the SRV records including the back parent domain name or the back source resource IP.
Step S22: the recursive DNS sends an A record request of the domain name to the second authority DNS based on the received A request of the domain name; the second authoritative DNS returns corresponding a records to the cache server through recursive DNS based on the a record request, the a records including the back parent resource IP or the back source resource IP.
Specifically, the SRV request implemented by the invention only returns the parent domain name or the source domain name, then the A request is sent again by utilizing the received domain name, and the A request returns the resource IP corresponding to the parent domain name or the source domain name.
In a specific embodiment, as shown in fig. 7, the logic for generating the SRV record and the a record by the authoritative DNS in the embodiment of the present invention includes:
step S31: the edge node area, the first-layer father node area and the second-layer father node area are planned in advance.
As shown in table 2, first, three levels of views of an edge node area, a first parent node area, and a second parent node area are defined for each class of nodes: va, vb, vc.
TABLE 2
Step S32: the SRV mapping relationship of ctup.com of each node is configured.
The SRV mapping of ctup.com for each node is shown in table 3.
TABLE 3 Table 3
Step S33: the SRV mapping relationship of ctup.com of each node is configured.
The SRV mapping of ctup.com for each node is shown in table 4.
TABLE 4 Table 4
In one embodiment, the method comprises the following steps: the SRV request analysis result and the A request analysis result both comprise: the request type and the hierarchy to which the carried edns belongs.
Specifically, when the cache server initiates a DNS request, the edge machine fixed bearer edns is 127.1.0.1, one layer of parent fixed bearer 127.1.0.2, and two layers of parent fixed bearers 127.1.0.3. The DNS server judges which SRV record or A record is to be returned specifically according to the type in the DNS request and the belonged level of edns.
Based on the above method, the embodiment of the present invention provides a client request flow chart as shown in fig. 8.
As can be seen from fig. 8, the client request flow for each layer of nodes is: client accesses Cache domain name test.com/. Ts; the Cache initiates an SRV request of test.com.ctup.com to the layer of recursive DNS; the layer DNS recursions to authoritative DNS; the authority DNS matches the VIEW according to the IP of the request, matches the VIEW and the request domain name to a corresponding upper domain name (father or source station), and returns SRV records comprising priority, weight, port, upper domain name and the like; after the Cache acquires the SRV record, initiating a record inquiry to the local recursion DNS again according to the returned upper domain name; the authority DNS responds to the A request, returns a resource IP, and the Cache acquires the returned IP and initiates a request to the father or source station.
When the SRV record is a parent domain name, the local recursive DNS is directly recursive into the GSLB; when the SRV record is a back source domain name, the local recursive DNS recursion is to the DNS request of the client source.
If the source station provides IP, the GSLB needs to virtually develop a back source domain name (the back source domain name is still a zone of ctup.com), which configures the IP provided by the source station.
It is apparent that the above examples are given by way of illustration only and are not limiting of the embodiments. Other variations or modifications of the above teachings will be apparent to those of ordinary skill in the art. It is not necessary here nor is it exhaustive of all embodiments. And obvious variations or modifications thereof are contemplated as falling within the scope of the present invention.
Claims (10)
1. A CDN network comprising: a resource planning system, a configuration system, a cache system and a scheduling system, wherein,
The resource planning system, the configuration system, the scheduling system and the cache system are in communication connection;
The resource planning system is used for marking the resources and dividing the resource planning into multi-level nodes;
The dispatching system generates DNS configuration to be deployed in a DNS server in the dispatching system;
the configuration system issues the IP address of the node where the recursive DNS software is located to a cache server and provides domain name and source returning information;
Each node of the cache system initiates a plurality of requests to the dispatch system according to a domain name requested by a user or response information of the dispatch system in sequence and a preset rule, the dispatch system responds to the cache system based on the request content to obtain a parent resource IP of a parent domain name or a source domain name and a source resource IP.
2. The CDN network of claim 1, wherein the multi-tier node comprises: edge node, middle one-layer father node and middle two-layer father node.
3. The CDN network of claim 2 wherein the caching system comprises: an edge node cache server, a first layer father node cache server and a second layer father node cache server which are connected in sequence in a communication way, wherein,
The edge node cache server is used for sending multiple requests to the dispatching system according to the domain name requested by the user, and returning to the upper node IP according to the response information of the dispatching system;
the parent node cache server is used for sending multiple requests to the dispatching system again according to the upper node IP returned by the edge node cache server, and returning to the upper node IP according to the response information of the dispatching system;
and the two-layer father node cache server is used for sending multiple requests to the dispatching system again according to the last layer node IP returned by the one-layer father node cache server and returning to the client source station according to the response information of the dispatching system.
4. The CDN network of claim 3 wherein the scheduling system comprises: an edge node recursive DNS, a layer one parent node recursive DNS, a layer two parent node recursive DNS, a first authoritative DNS, a second authoritative DNS, and a GSLB scheduling system, wherein,
The edge node recursive DNS, the first-layer parent node recursive DNS and the second-layer parent node recursive DNS are respectively in corresponding communication connection with the edge node cache server, the first-layer parent node cache server and the second-layer parent node cache server; the edge node recursive DNS, the first-layer parent node recursive DNS, the second-layer parent node recursive DNS and the GSLB scheduling system are also in communication connection with the resource planning system; the second authoritative DNS is in communication connection with the GSLB scheduling system;
The edge node recursive DNS, the first-layer father node recursive DNS and the second-layer father node recursive DNS are respectively used for sending requests to a first authoritative DNS and a second authoritative DNS according to multiple requests sent by the edge node cache server, the first-layer father node cache server and the second-layer father node cache server;
And the first authoritative DNS and the second authoritative DNS respond to the optimal answer according to the request sent by the recursive DNS and send the optimal answer to the corresponding cache server through the corresponding recursive DNS.
5. The CDN network of claim 4, wherein the resource planning system comprises: a RAP resource application planning module and a DCP static coverage planning module, wherein,
The RAP resource application planning module is respectively in communication connection with the DCP static coverage planning module and the configuration system;
The RAP resource application planning module is used for providing information of a parent layer group and hierarchical information;
the DCP static coverage planning module generates back source information based on client source configuration; generating coverage of the corresponding parent layer domain name according to the parent layer group information;
The configuration system issues the IP of the recursive DNS software to the cache server based on the hierarchical information.
6. An automatic scheduling method for a node return upper layer request of a CDN network, wherein the scheduling method comprises, based on the CDN network of claim 5:
And each node of the cache system sequentially initiates a plurality of requests to the dispatch system according to a domain name requested by a user or response information of the dispatch system and a preset rule, the dispatch system responds to the cache system optimally based on the request content, and the cache system obtains a parent resource IP returned from a parent domain name or obtains a source domain name and a source resource IP returned.
7. The automatic scheduling method for node back upper layer requests of CDN network of claim 6, wherein each node of the cache system sequentially initiates a process of multiple requests to the scheduling system according to a domain name requested by a user or response information of the scheduling system and a preset rule, including:
The edge node server sends an SRV request to the dispatching system according to the domain name of the user request; the dispatching system returns the corresponding back parent domain name to the edge node server based on the SRV request; the edge node server sends an A request to the dispatching system again according to the parent domain name; the scheduling system returns the corresponding parent return resource IP to the edge node server based on the A request;
The edge node server returns a corresponding layer of father node based on the father returning resource IP, and the layer of father node server sends an SRV request to the dispatching system based on the father returning resource IP returned by the edge node server; the scheduling system returns the corresponding back parent domain name to a layer of parent node server based on the SRV request; a layer of father node server sends an A request to the dispatching system again according to the father domain name; the scheduling system returns the corresponding parent returning resource IP to the layer of parent node servers based on the A request;
The first-layer father node returns a corresponding second-layer father node based on the returned father resource IP, and the second-layer father node server sends an SRV request to the dispatching system based on the returned father resource IP returned by the first-layer father node server; the scheduling system returns the corresponding back source domain name to the two-layer father node server based on the SRV request; the two-layer father node server sends an A request to the dispatching system again according to the source-returning domain name; the scheduling system returns the corresponding source return resource IP to the corresponding client source station based on the A request;
The SRV request is a first request, and the first request is used for requesting the dispatching system to feed back the parent domain name or the source domain name;
The request A is a second request, and the second request is used for requesting the scheduling system to feed back to the parent resource IP or the source resource IP.
8. The method for automatically scheduling a node back to upper layer request in a CDN network of claim 7 wherein the process of responding to the SRV request and the a request by the authoritative DNS comprises:
The recursive DNS sends an SRV record request of the domain name to the first authority DNS based on the received SRV request of the domain name; the first authority DNS returns corresponding SRV records to a cache server through the recursive DNS based on the SRV record request, wherein the SRV records comprise a parent return domain name or a source return resource IP name;
The recursive DNS sends an A record request of the domain name to the second authority DNS based on the received A request of the domain name; and the second authority DNS returns corresponding A records to the cache server through the recursive DNS based on the A record request, wherein the A records comprise a parent resource IP or a source resource IP.
9. The method for automatically scheduling a node back to an upper layer request in a CDN network of claim 8 further comprising:
Pre-planning an edge node area, a first-layer father node area and a second-layer father node area;
Configuring an SRV mapping relation of ctup.com of each node;
The a records of ctup.com and ctfu.com for each node are configured.
10. The method for automatically scheduling a node back to an upper layer request of a CDN network of claim 9, comprising:
The SRV request analysis result and the A request analysis result comprise: the request type and the hierarchy to which the carried edns belongs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111617599.XA CN114500460B (en) | 2021-12-27 | 2021-12-27 | CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111617599.XA CN114500460B (en) | 2021-12-27 | 2021-12-27 | CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114500460A CN114500460A (en) | 2022-05-13 |
| CN114500460B true CN114500460B (en) | 2024-04-26 |
Family
ID=81496788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111617599.XA Active CN114500460B (en) | 2021-12-27 | 2021-12-27 | CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114500460B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225490A (en) * | 2022-07-20 | 2022-10-21 | 天翼云科技有限公司 | Gateway configuration method and device and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102843426A (en) * | 2012-08-09 | 2012-12-26 | 网宿科技股份有限公司 | Method and system for sharing Web cached resource based on intelligent father node |
| CN105681491A (en) * | 2016-04-08 | 2016-06-15 | 网宿科技股份有限公司 | DNS (Domain Name Resolution) acceleration method, system and device |
| CN108234685A (en) * | 2017-12-20 | 2018-06-29 | 中国移动通信集团江苏有限公司 | Method, apparatus, equipment and the medium of user terminal gateway equipment DNS scheduling |
| CN108574744A (en) * | 2017-07-28 | 2018-09-25 | 北京金山云网络技术有限公司 | A kind of domain name analytic method, device, electronic equipment and readable storage medium storing program for executing |
| US10193853B1 (en) * | 2016-10-31 | 2019-01-29 | Workday, Inc. | Web browser or web service based detection of internet facing DNS server |
| CN109951543A (en) * | 2019-03-14 | 2019-06-28 | 网宿科技股份有限公司 | A kind of data search method of CDN node, device and the network equipment |
| CN110708368A (en) * | 2019-09-25 | 2020-01-17 | 北京计算机技术及应用研究所 | Micro front-end system and method based on routing distribution |
| CN112738288A (en) * | 2020-12-24 | 2021-04-30 | 上海牙木通讯技术有限公司 | DNS domain name resolution method, DNS server, GSLB system and domain name resolution system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7412535B2 (en) * | 2001-12-19 | 2008-08-12 | International Business Machines Corporation | Method and system for caching fragments while avoiding parsing of pages that do not contain fragments |
| CN102857363B (en) * | 2012-05-04 | 2016-04-20 | 运软网络科技(上海)有限公司 | A kind of autonomous management system and method for virtual network |
-
2021
- 2021-12-27 CN CN202111617599.XA patent/CN114500460B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102843426A (en) * | 2012-08-09 | 2012-12-26 | 网宿科技股份有限公司 | Method and system for sharing Web cached resource based on intelligent father node |
| CN105681491A (en) * | 2016-04-08 | 2016-06-15 | 网宿科技股份有限公司 | DNS (Domain Name Resolution) acceleration method, system and device |
| US10193853B1 (en) * | 2016-10-31 | 2019-01-29 | Workday, Inc. | Web browser or web service based detection of internet facing DNS server |
| CN108574744A (en) * | 2017-07-28 | 2018-09-25 | 北京金山云网络技术有限公司 | A kind of domain name analytic method, device, electronic equipment and readable storage medium storing program for executing |
| CN108234685A (en) * | 2017-12-20 | 2018-06-29 | 中国移动通信集团江苏有限公司 | Method, apparatus, equipment and the medium of user terminal gateway equipment DNS scheduling |
| CN109951543A (en) * | 2019-03-14 | 2019-06-28 | 网宿科技股份有限公司 | A kind of data search method of CDN node, device and the network equipment |
| CN110708368A (en) * | 2019-09-25 | 2020-01-17 | 北京计算机技术及应用研究所 | Micro front-end system and method based on routing distribution |
| CN112738288A (en) * | 2020-12-24 | 2021-04-30 | 上海牙木通讯技术有限公司 | DNS domain name resolution method, DNS server, GSLB system and domain name resolution system |
Non-Patent Citations (1)
| Title |
|---|
| 基于EDNS优化的CDN精准调度方案探讨;黄润怀;广东通信技术;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114500460A (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101453399B (en) | Virtual network configuration method and apparatus | |
| CN103262503B (en) | Node selecting method and equipment in packet core network | |
| US20080008091A1 (en) | Qos CONTROL SYSTEM | |
| CN1859437B (en) | Method for obtaining cut-in position information for user terminal and user terminal and relative device | |
| CN101141420A (en) | Method and system for performing data communication between private network and public network | |
| CN101729591A (en) | User guide device, system and method | |
| CN110326345A (en) | A kind of methods, devices and systems of Configuration network slice | |
| CN103329506B (en) | Identify privately owned device in the public network | |
| CN101282248B (en) | Method for measuring network application performance supporting internet high bandwidth real time video application | |
| WO2018196843A1 (en) | Resource request method and device | |
| CN114500460B (en) | CDN (content delivery network) and automatic scheduling method for node return upper layer requests of CDN | |
| US20090024761A1 (en) | Method, system and application for service addressing | |
| JP2010534994A (en) | Method and system for providing RACF configuration information | |
| CN101282249B (en) | Automatic log-on and management method for distributed internet measurement server | |
| JP2001016255A (en) | Inter-network communication method and system | |
| CN109194914B (en) | Method and device for processing equipment information | |
| US20080247379A1 (en) | Method and Network for Managing an Interface for Session-Based Synchronization | |
| CN1997036A (en) | Access multiplexer | |
| CN101453396B (en) | Method and system for multiple service provider device management | |
| CN113315704B (en) | Message forwarding method, SDN controller, switch and system | |
| EP2019535A1 (en) | Requester-aware domain name system | |
| CN108632173B (en) | Resource access system and resource access method based on local area network | |
| EP1598982B1 (en) | Architecture for configuration and management of cross-domain services | |
| CN101374068A (en) | Method, apparatus and system for implementing packet transmission of multicast business | |
| CN100373879C (en) | Wideband access net with three layer access point and its IP address distributing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |