WO2020019472A1 - 服务节点的评分方法、域名***dns调度方法及服务器 - Google Patents

服务节点的评分方法、域名***dns调度方法及服务器 Download PDF

Info

Publication number
WO2020019472A1
WO2020019472A1 PCT/CN2018/107474 CN2018107474W WO2020019472A1 WO 2020019472 A1 WO2020019472 A1 WO 2020019472A1 CN 2018107474 W CN2018107474 W CN 2018107474W WO 2020019472 A1 WO2020019472 A1 WO 2020019472A1
Authority
WO
WIPO (PCT)
Prior art keywords
service node
domain name
service
information
preset
Prior art date
Application number
PCT/CN2018/107474
Other languages
English (en)
French (fr)
Inventor
黄志贤
Original Assignee
网宿科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to EP18918414.6A priority Critical patent/EP3629521B1/en
Priority to US16/482,383 priority patent/US20210409298A1/en
Publication of WO2020019472A1 publication Critical patent/WO2020019472A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • H04L43/55—Testing of service level quality, e.g. simulating service usage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3495—Performance evaluation by tracing or monitoring for systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/125—Shortest path evaluation based on throughput or bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • Embodiments of the present invention relate to the field of Internet technologies, and in particular, to a scoring method for a service node, a DNS scheduling method for a domain name system, and a server.
  • Domain Name System DNS (DomainNameSystem, referred to as "DNS") is a distributed database of domain names. It is the core service of the Internet's basic resources. It is mainly used to carry the conversion between IP addresses and Internet domain names, making it easier and faster to access. the Internet.
  • DNS Domain Name System
  • the terminal invokes the resolver to perform a DNS query, the resolver sends the DNS query request to the domain name server, and the domain name server queries its resource records in the domain name space to obtain the corresponding source site
  • the service node returns the address information of the source service node to the parser, and the parser returns the final result to the terminal.
  • CDN Content Delivery Network
  • CDN Content Delivery Network
  • It is a concept proposed relative to a complex network structure. It is a network traffic distribution and scheduling system derived from DNS to improve Internet access speed and quality. . Its main principle is to redirect the user's request to the source station service node closest to the user in real time according to the network traffic, the connection information of each source station service node, the load status, and the user's distance and response time. Open bottlenecks and links on the Internet that may affect the speed and stability of data transmission, making content transmission faster and more stable.
  • the existing CDN scheduling system mainly relies on static policies. Through the pre-deployed nodes throughout the network, a new intelligent virtual network is formed, and a series of DNS mapping data tables are constructed to distinguish the domain name line coverage in different regions. These DNS mapping data tables direct access users to the corresponding nodes to facilitate traffic grooming and speed up processing.
  • the DNS mapping data table is set in advance and is strictly segmented according to the operator's region. Therefore, the data received by each node is a relatively fixed static configuration.
  • the scheduling system cannot determine the availability of each node, and different nodes The resources cannot be prepared for each other, the flexibility is poor, and the reasonable allocation of resources is difficult to achieve. It may happen that the nodes are unavailable or the network traffic is unevenly distributed.
  • hybrid CND scheduling content providers use multiple CDN service vendors to provide services.
  • the hybrid CND scheduling service requires the scheduling system to select, schedule, switch between multiple CDN service vendors, and finally obtain The best resources.
  • This requires that the scheduling system has a relatively complete monitoring and scheduling mechanism that can monitor the status of each CDN in real time. When a CDN service is unavailable or under heavy load, it can switch or add another CDN service. This has a significant impact on technology and resources. The investment is huge.
  • the purpose of the embodiments of the present invention is to provide a scoring method for a service node, a DNS scheduling method for a domain name system, and a server, which are capable of scoring a service node to distinguish a high-quality service node, and provide a basis for achieving a reasonable allocation of resources.
  • an embodiment of the present invention provides a method for scoring a service node, including:
  • Score service nodes based on several performance reference information.
  • An embodiment of the present invention further provides a DNS scheduling method for a domain name system, including:
  • the domain name to be scheduled and the line service information corresponding to the domain name to be scheduled; wherein the line service information includes address information of at least several service nodes;
  • An embodiment of the present invention further provides a server, including:
  • At least one processor At least one processor
  • Memory in communication with at least one processor; wherein:
  • the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the above-mentioned DNS scheduling method of the domain name system.
  • An embodiment of the present invention also provides a computer-readable storage medium storing a computer program, and the computer program, when executed by a processor, implements the foregoing DNS scheduling method for a domain name system.
  • the embodiment of the present invention proposes a method for scoring a service node, and monitors the service node according to the obtained address information of the service node, so as to obtain several performance reference information of the service node. In order to score the service nodes. In this way, the score of the service node can intuitively reflect whether the service node is used, whether the service node is a high-quality service node, and so on, which provides a basis for the reasonable allocation of resources.
  • T is the scoring value
  • t is the resource response time
  • t 0 is the preset resource response time
  • v is the download speed
  • v 0 is the preset download speed.
  • the DNS scheduling method of the domain name system in the embodiment of the present invention generates line scheduling information of the domain name to be scheduled according to the score values of each service node corresponding to the domain name to be scheduled, and distributes the line scheduling information to the
  • the implementation of the designed domain name server provides a basis for real-time ground line tuning and reasonable resource distribution. It is applicable to CDN intranet scheduling and cross-CDN hybrid CDN scheduling, and has a wide range of applications. In addition, there is no need for too many people to intervene in the operation, which saves the human and financial resources of the enterprise and effectively controls the operation and maintenance costs.
  • generating the line scheduling information of the domain name to be scheduled according to the rating value of each service node specifically includes: ranking each service node that meets the line screening condition according to the ranking value; , To generate the line scheduling information of the domain name to be scheduled, so as to realize analysis of line tuning and reasonable distribution of resources.
  • the method further includes: pushing prompt information including the line scheduling information to a preset terminal, so that a technician can timely understand the comparison More effective information.
  • FIG. 1 is a specific flowchart of a scoring method for a service node according to a first embodiment
  • FIG. 2 is a specific flowchart of a DNS scheduling method of a domain name system according to a second embodiment
  • FIG. 3 is a schematic diagram of a server according to a fourth embodiment.
  • the first embodiment of the present invention relates to a method for scoring a service node.
  • the specific process is shown in FIG. 1.
  • the scoring method for the service node in this embodiment is implemented on a server, hereinafter referred to as the resource scoring center.
  • the implementation steps of the scoring method in this embodiment are as follows:
  • Step 101 Obtain address information of a service node.
  • the service node may be a source service node or an acceleration service node.
  • the technician sends the address information of the service node to be scored to the resource scoring center.
  • the address information of the service node may be an IP address or an alias record CNAME address.
  • Step 102 Monitor the service node according to the address information of the service node, obtain several performance reference information of the service node, and score the service node according to the several performance reference information.
  • the resource scoring center can control one or more monitoring machines to perform real-time monitoring and detection on the service node. That is, each monitor can perform several performance monitorings on the service node to obtain several performance reference information of the service node. In this way, the resource scoring center can score the service nodes based on several performance reference information of the service nodes obtained by each monitoring machine.
  • Step 102 includes sub-steps 1021 to 1026, as follows:
  • Sub-step 1021 determining whether the address information of the service node is a CNAME address. If yes, go to step 1022, otherwise go to step 1024.
  • the determination result of sub-step 1021 is YES. If the address information of the service node is an IP address, the determination result of sub-step 1021 is no.
  • Substep 1022 Obtain the resource response time and download speed of the service node.
  • the resource scoring center can control one or more monitoring machines to perform real-time monitoring and detection on the service node.
  • the control and monitoring machine of the resource scoring center performs network diagnosis PING (Packet Internet Internet Groper, "PING") monitoring on the service nodes to obtain the download speed of the service nodes, and performs DNS monitoring on the service nodes to obtain the resource response time of the service nodes .
  • PING Packet Internet Internet Groper
  • a technician can set the detection time frequency of the monitoring machine in the resource scoring center in advance, so that the resource scoring center can control the monitoring machine to obtain more accurate and representative data.
  • the detection time frequency can be 2 minutes / time.
  • Sub-step 1023 Calculate the score of the service node according to the first preset formula.
  • the first preset formula is input by a technician in advance and saved to a resource scoring center.
  • the resource scoring center controls a monitoring machine to perform real-time monitoring and detection on service nodes.
  • the service node's score value is the average value of T.
  • the resource scoring center controls two monitoring machines to perform real-time monitoring and detection on service nodes.
  • One monitoring machine monitors t for 40ms and v is 2500k / s, and the other monitors t for 60ms and v is 2000k / s. ;
  • Sub-step 1024 Determine whether the address information of the service node is an IP address. If yes, go to step 1025, otherwise end this process.
  • Sub-step 1025 Obtain resource response time, bandwidth usage rate, and resource memory load of the service node.
  • the resource scoring center can control one or more monitoring machines to perform real-time monitoring and detection on the service node.
  • the control monitor monitors the service nodes for network diagnostics PING (Packet Internet Internet Groper, "PING" for short) to obtain the download speed of the service nodes, perform port monitoring on the service nodes to obtain the bandwidth usage rate of the service nodes, and The nodes perform server performance monitoring to obtain resource memory load.
  • PING Packet Internet Internet Groper
  • the resource scoring center control and monitoring machine performs server performance monitoring on the service node to obtain the resource memory load.
  • the specific implementation method may be: the resource scoring center control and monitoring machine obtains the CPU usage, memory usage, and disk of the service node. Occupancy, according to the formula Calculate the resource memory load of the service node, where z is the resource memory load, A1 is the CPU usage, A2 is the memory usage, and A3 is the disk usage; a is the preset weight of the CPU usage and b is the memory usage The preset weight of c is the preset weight of disk occupancy.
  • the CPU usage rate of the monitoring node to obtain the service node is 40%
  • the memory usage rate is 40%
  • the disk occupation rate is 40%.
  • the calculation formula of the resource memory load in this embodiment is:
  • technicians can modify the calculation formula of resource memory load, such as .
  • the calculation formula of resource memory load can be transformed into Among them, A1 to An represent specific numerical values of each performance reference information, m represents the number of performance reference information obtained by the resource scoring center, and x represents a preset weight of An performance reference information.
  • Sub-step 1026 Calculate the score of the service node according to the second preset formula.
  • the second preset formula is input by a technician in advance and saved to a resource scoring center.
  • the resource scoring center controls a monitoring machine to perform real-time monitoring and detection on service nodes. The monitoring machine monitors t for 50ms, n for 40%, and z for The preset t 0 is 200ms, n 0 is 80%, and z 0 is 80%, then
  • the service node's score value is an average value of T.
  • the resource scoring center controls two monitoring machines to perform real-time monitoring and detection on the service node.
  • step 102 is only an exemplary description provided for easy understanding. This embodiment does not make specific reference to performance reference information and specific implementation forms for scoring service nodes based on the performance reference information. Any restrictions. In actual application, a technician can set a specific implementation form of performance reference information and a specific implementation form of scoring according to actual needs.
  • the embodiment of the present invention proposes a method for scoring a service node, and monitors the service node according to the obtained address information of the service node, so as to obtain several performance reference information of the service node. To score the service nodes.
  • the scoring of the service node can intuitively reflect whether the service node is used, whether the service node is a high-quality service node, and so on, which provides a basis for the rational allocation of resources.
  • the second embodiment of the present invention relates to a DNS scheduling method of a domain name system, and a specific process is shown in FIG. 2.
  • the second embodiment of the present invention needs to call the scoring method of the service node in the first embodiment in order to generate the line scheduling information of a certain domain name.
  • the DNS scheduling method of the domain name system in this embodiment is implemented on a server, hereinafter referred to as the scheduling decision center.
  • the specific steps of the DNS scheduling method of the domain name system in this embodiment are as follows:
  • Step 201 Obtain a domain name to be scheduled and line service information corresponding to the domain name to be scheduled.
  • the technician sends the domain name to be scheduled and the line service information corresponding to the domain name to be scheduled to the scheduling decision center.
  • the line service information includes at least address information of several service nodes.
  • the service node may be a source station service node.
  • the address information of the service node may be an IP address.
  • the line service information may also include information such as the geographic location of each service node, the Internet service provider, and so on.
  • the to-be-scheduled domain name obtained by the scheduling decision center and the line service information corresponding to the to-schedule domain name may be shown in Example 1 below:
  • Example 1 The domain name to be scheduled is test.example.com; the line service information is shown in Table 1 below:
  • IP Geographical location Address information
  • Step 202 Obtain score values of several service nodes included in the line service information.
  • the dispatch decision center sends the address information of several service nodes included in the line service information to the resource scoring center in the first embodiment, so that the resource scoring center performs the processing on the several service nodes included in the line service information. Score, and return the score value of each service node to the scheduling decision center.
  • Step 203 Generate line scheduling information of the domain name to be scheduled according to the score value of each service node.
  • the scheduling decision center can sort each service node according to the score value, and generate line scheduling information of the domain name to be scheduled according to the ranking result.
  • a technician configures a line screening condition in the scheduling decision center in advance, and the line screening condition may be that the score value of the service node is greater than a preset threshold.
  • the scheduling decision center can filter out certain faulty lines or heavy-loaded lines, thereby generating line scheduling information based on the higher-quality service nodes.
  • the scheduling decision center may sort each service node that meets the line screening condition (scoring value is greater than a preset threshold) according to the level of the scoring value, so as to generate line scheduling information of the scheduling domain name according to the ranking result.
  • the line filter condition can also be a preset type for the type to which the Internet service provider belongs.
  • the preset type is Telecom
  • the service nodes of Fujian Telecom as the Internet service provider meet the line screening conditions.
  • the scheduling decision center can sort each service node of the Internet service provider type telecommunications according to the score value, so as to generate line scheduling information of the scheduling domain name according to the ranking result.
  • step 203 in this embodiment is exemplified below.
  • the content described below is only an exemplary description, and the specific implementation form of step 203 is not limited in this embodiment.
  • the domain name to be scheduled is test.example.com; the line service information is shown in Table 1:
  • the scoring table of each source station service node is as follows:
  • the scheduling decision center can filter the top service nodes from the ranking, so that when a line fails Or when the load is heavy, the selected high-quality service nodes can be replaced and covered to ensure the normal analysis of the line is available.
  • the scheduling decision center needs to remove service nodes other than the preset types first, and then sort.
  • the scheduling decision center can generate line scheduling information of the domain name to be scheduled according to the level level and the ranking result. For example, when the low-level line is faulty, the analytical line can be switched from the low-level line to the upper-level line step by step. For example, when Fujian Telecom 2.1.1.1 fails, the China Telecom line is preferentially switched. When there is no China Telecom line or the IP under the telecommunication line is down, Switch to the default line 1.1.1.1. When all the default lines fail, the top resources will be automatically ranked according to the score value for replacement analysis.
  • the resource scoring center can control the monitoring machine to obtain more accurate and representative data Moreover, the resource scoring center can perform dynamic real-time scoring for each service node, providing a basis for subsequent scheduling decision-making centers to be able to generate more real-time dynamic line scheduling information. In this way, the timeliness and flexibility of the domain name system adjustment are effectively ensured, and the problem of timeliness caused by the optimization of the manual and manual mode in the prior art is effectively avoided.
  • the scheduling decision center when it generates the line scheduling information of the domain name to be scheduled, it can also set the load value for each service node included in the line scheduling information according to the scheduling method preset by the technician.
  • the preset scheduling method is a master-slave scheduling method
  • the service node ranked first may be used as the main scheduling line
  • the service node ranked second may be used as the standby scheduling line.
  • the preset scheduling mode is load balancing
  • each of the service nodes ranked first and the service nodes ranked second is loaded with 50% of the scheduling traffic. In this way, the purposes of dynamic load balancing and multi-level active / standby switching can be achieved.
  • Step 204 Publish the line scheduling information to a preset domain name server.
  • a technician can input and save the address information of one or more domain name servers in the scheduling decision center in advance, so that the scheduling decision center can release the line scheduling information to a preset according to the currently stored name server address information.
  • the domain name server enables the domain name server to perform line scheduling information, which provides a basis for achieving comprehensive coverage of line scheduling information.
  • the dispatch decision center after the dispatch decision center publishes the line dispatch information to each domain name server, it can also push the line dispatch information to the preset terminal, so that the technicians can know more effective information in time .
  • the preset terminal may be a mobile phone, a computer, or a tablet of a technician.
  • the dispatching decision center can push information to the preset terminal through various channels such as email, text message, WeChat, and intra-station letter.
  • the scheduling decision center can also inform users of resource failure, resource switching, and resource recovery.
  • the prompt information including the line scheduling information may exist in the following form.
  • the following examples of the prompt information are only for illustrative purposes.
  • a technician may preset the prompt items included in the prompt information.
  • a technician can also set a switching timing in the scheduling decision center, for example, immediate switching, delayed switching, or manual switching, so that the scheduling decision center determines the time for issuing line scheduling information according to the switching timing.
  • the scheduling decision center in this embodiment is equivalent to a CDN network traffic distribution scheduling system, and generates line scheduling information of the domain name to be scheduled according to the score values of each service node corresponding to the domain name to be scheduled, and It is distributed to the domain name server for execution, realizing the purposes of real-time line tuning and reasonable distribution of resources.
  • technicians only need to set up a simple domain name configuration table (as shown in Table 1), and the scheduling system can realize the pros and cons of each service node, so as to automatically generate better line scheduling information for network-wide coverage, eliminating the need for Too many people intervene in the operation, while effectively guaranteeing the quality of services, it saves corporate manpower and financial resources, and effectively controls operation and maintenance costs.
  • the third embodiment of the present invention relates to a DNS scheduling method for a domain name system.
  • the third embodiment of the present invention is substantially the same as the second embodiment, and the main difference is that the third embodiment of the present invention is applicable to a cross-CDN hybrid CDN scheduling situation, which will be specifically described below:
  • Step 201 Obtain a domain name to be scheduled and line service information corresponding to the domain name to be scheduled.
  • the technician sends the domain name to be scheduled and the line service information corresponding to the domain name to be scheduled to the scheduling decision center.
  • the line service information includes address information of at least several service nodes.
  • the service node may be an accelerated service node.
  • the address information of the service node may be a CNAME address of an alias of a certain CDN.
  • the line service information may also include information such as the geographic location of each service node, the Internet service provider, and so on.
  • the to-be-scheduled domain name and the line service information corresponding to the to-be-scheduled domain name obtained by the scheduling decision center can be shown in Example 2 below:
  • Example 2 The domain name to be scheduled is cdn.example.com; the line service information is shown in Table 2 below:
  • CDN1, CDN2, and CDN3 represent the address information of the network traffic distribution and scheduling systems of the three CDN service providers.
  • Table 2 above indicates that the content provider with the domain name cdn.example.com needs to use CDN1, CDN2, and CDN3 three CDN service providers for hybrid acceleration.
  • Step 202 Obtain score values of several service nodes included in the line service information.
  • this step is the same as that in the second embodiment, that is, the dispatch decision center sends the address information of several service nodes included in the line service information to the resource scoring center in the first embodiment, so that the resource scoring center can route the lines.
  • the dispatch decision center sends the address information of several service nodes included in the line service information to the resource scoring center in the first embodiment, so that the resource scoring center can route the lines.
  • Several service nodes included in the service information are scored, and the score values of each service node are returned to the scheduling decision center.
  • Step 203 Generate line scheduling information of the domain name to be scheduled according to the score value of each service node.
  • the score table of each accelerated service node is as follows:
  • the scheduling decision center can sort the acceleration service nodes according to the level of the resource score value, and the line scheduling information can be set according to the preset number of acceleration service nodes, for example, when the preset number is 1.
  • priority is given to CDN1; for example, when the preset number is 2, in Fujian Telecom, priority is given to CDN1 and CDN2.
  • Step 204 Publish the line scheduling information to a preset domain name server.
  • the scheduling decision center in this embodiment is equivalent to a cross-CDN network traffic distribution scheduling system, which is applicable to the case of hybrid CDN scheduling (that is, cross-CDN scheduling).
  • This scheduling method is based on the scores of each service node corresponding to the domain name to be scheduled. Value to generate line scheduling information for the domain name to be scheduled, and distribute the line scheduling information to the domain name server for execution, achieving the purpose of dynamically optimizing according to the acceleration quality of each CDN, enabling real-time line tuning and reasonable resource distribution.
  • there is no need for too many people to intervene in the operation which greatly saves the human and financial resources of the enterprise and controls the operation and maintenance costs.
  • a fourth embodiment of the present invention relates to a server, as shown in FIG. 3, including: at least one processor 301; and a memory 302 communicatively connected to the at least one processor 301; wherein the memory 302 stores at least one process
  • the instructions executed by the server 301 are executed by at least one processor 301, so that the at least one processor 301 can execute the DNS scheduling method of the domain name system in the foregoing method embodiment.
  • the memory 302 and the processor 301 are connected in a bus manner.
  • the bus may include any number of interconnected buses and bridges.
  • the bus connects one or more processors 301 and various circuits of the memory 302 together.
  • the bus can also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, they will not be described further herein.
  • the bus interface provides an interface between the bus and the transceiver.
  • a transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium.
  • the data processed by the processor 301 is transmitted on a wireless medium through an antenna. Further, the antenna also receives the data and transmits the data to the processor 301.
  • the processor 301 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 302 may be used to store data used by the processor 301 when performing operations.
  • the embodiments of the present invention provide a basis for achieving analytical line tuning and reasonable resource distribution.
  • the domain name system can be dispatched without excessive human intervention, which saves manpower and financial resources of the enterprise and effectively controls operation and maintenance costs.
  • a fifth embodiment of the present invention relates to a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the above method embodiment is implemented.
  • the embodiments of the present invention provide a basis for achieving analytical line tuning and reasonable resource distribution.
  • the domain name system can be dispatched without excessive human intervention, which saves manpower and financial resources of the enterprise and effectively controls operation and maintenance costs.
  • the program is stored in a storage medium and includes several instructions for making a device ( It may be a single-chip microcomputer, a chip, or the like) or a processor that executes all or part of the steps of the method described in each embodiment of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Environmental & Geological Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Mathematical Physics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施方式涉及互联网技术领域，公开了一种服务节点的评分方法、域名***DNS调度方法及服务器。本发明实施方式中，服务节点的评分方法包括：获取服务节点的地址信息；根据服务节点的地址信息，对服务节点进行监测，并获取服务节点的若干个性能参考信息；根据若干个性能参考信息，对服务节点进行评分。本发明实施方式还提供了一种域名***DNS调度方法及服务器。本发明实施方式对服务节点进行评分，以区分出优质服务节点，为实现资源的合理分配提供了基础。

Description

服务节点的评分方法、域名***DNS调度方法及服务器 技术领域
本发明实施方式涉及互联网技术领域，特别涉及服务节点的评分方法、域名***DNS调度方法及服务器。
背景技术
域名***DNS(DomainNameSystem，简称“DNS”)是一个域名分布式的数据库，它是互联网基础资源的核心服务，主要用于承载IP地址和互联网域名之间的转换，令人们能够更方便快捷地访问互联网。当用户在终端的浏览器中发起域名解析请求时，终端调用解析器进行DNS查询，解析器将DNS查询请求发送至域名服务器，域名服务器在域名空间中查询其资源记录，以获取对应的源站服务节点，并将源站服务节点的地址信息返回给解析器，再由解析器将最终结果返给终端。
内容分发网络CDN(Content Delivery Network，简称“CDN”)，它是相对于复杂的网络结构提出的一个概念，是在DNS基础上衍生的网络流量分配调度***，用来提升互联网的访问速度和质量。其主要原理是实时地根据网络流量和各源站服务节点的连接、负载状况以及到用户的距离和响应时间等综合信息将用户的请求重新导向离用户最近的源站服务节点上，尽可能避开互联网上有可能影响数据传输速度和稳定性的瓶颈和环节，使内容传输的更快、更稳定。
但是，本专利申请的发明人在长期研发的过程中发现现有技术中至少存在如下问题：
现有CDN调度***主要是依赖静态策略，通过在网络上各处预先部署的节点，构成一层新的智能虚拟网络，并构建一系列DNS映射数据表来区分不同地区的域名线路覆盖，最终根据这些DNS映射数据表将访问用户引导至对应的节点上，以便于进行流量疏导、加速处理。但是，DNS映射数据表是预先设定，按照运营商地域进行严格切分的，因而各节点所接收到的数据均为相对固定的静态配置，调度***无法去判断各节点的可用性，且不同节点间的资源无法互备，灵活性较差，并难以实现资源的合理分配，并可能会出现调度到不可用的节点，或网络流量分配不均的情况。
并且，现有技术还存在混合CND调度(内容供应商采用多个CDN服务厂商提供服务)的情况，混合CND调度服务要求调度***在多个CDN服务厂商之间进行选择、调度、切换， 最终获取最优质的资源。这就要求调度***拥有比较完善的监控和调度机制，能够实时监控各CDN的状况，在某一CDN服务不可用或者负载过重时，能够切换或增加另一CDN服务，这对技术和资源的投入都是非常巨大的。
发明内容
本发明实施方式的目的在于提供一种服务节点的评分方法、域名***DNS调度方法及服务器，能够对服务节点进行评分，以区分出优质服务节点，为实现资源的合理分配提供了基础。
为解决上述技术问题，本发明的实施方式提供了一种服务节点的评分方法，包括：
获取服务节点的地址信息；
根据服务节点的地址信息，对服务节点进行监测，并获取服务节点的若干个性能参考信息；
根据若干个性能参考信息，对服务节点进行评分。
本发明的实施方式还提供了一种域名***DNS调度方法，包括：
获取待调度域名以及待调度域名对应的线路服务信息；其中，线路服务信息中至少包括若干个服务节点的地址信息；
利用上述的服务节点的评分方法，对若干个服务节点进行评分；
根据各服务节点的评分值，生成待调度域名的线路调度信息；
将线路调度信息发布至预设的域名服务器，以供域名服务器执行线路调度信息。
本发明的实施方式还提供了一种服务器，包括：
至少一个处理器；以及，
与至少一个处理器通信连接的存储器；其中，
存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行上述的域名***DNS调度方法。
本发明的实施方式还提供了一种计算机可读存储介质，存储有计算机程序，该计算机程序被处理器执行时实现上述的域名***DNS调度方法。
本发明实施方式相对于现有技术而言，提出了一种服务节点的评分方法，根据所获取的服务节点的地址信息，对服务节点进行监控，以便于获取服务节点的若干个性能参考信息，从而对服务节点进行评分。这样，服务节点的评分可以直观地反映出该服务节点是否用，该服务节点是否为优质服务节点等信息，为实现资源的合理分配提供了基础。
优选地，服务节点的评分方法中，根据服务节点的地址信息，对服务节点进行监测，获取服务节点的若干个性能参考信息，具体包括：若服务节点的地址信息为别名记录CNAME(Canonical Name，简称“CNAME”)地址，则获取服务节点的资源响应时间以及下载速度；根据若干个性能参考信息，对服务节点进行评分，具体包括：根据公式T＝(t 0/t)*(v/v 0)，计算服务节点的评分值；其中，T为评分值，t为资源响应时间，t 0为预设的资源响应时间，v为下载速度，v 0为预设的下载速度。这样，提供了对服务节点进行监测、评分的一种具体实现形式，增加了本发明实施方式的灵活性，令本发明实施方式具有较为广泛的应用范围。
优选地，服务节点的评分方法中，根据服务节点的地址信息，对服务节点进行监测，并获取服务节点的若干个性能参考信息，具体包括：若服务节点的地址信息为IP地址，则获取服务节点的资源响应时间、带宽使用率以及资源内存负载；根据服务节点的性能参考信息，对服务节点进行评分，具体包括：根据公式：T＝(t 0/t)*(n/n 0)*(z/z 0)，计算服务节点的评分值；其中，T为评分值，t为资源响应时间，t 0为预设的资源响应时间，n为带宽使用率，n 0为预设的带宽使用率；z为资源内存负载；z 0为预设的资源内存负载。这样，提供了对服务节点进行监测、评分的一种具体实现形式，增加了本发明实施方式的灵活性，令本发明实施方式具有较为广泛的应用范围。
本发明实施方式中的域名***DNS调度方法相对于现有技术而言，根据待调度域名对应的各服务节点的评分值，来生成待调度域名的线路调度信息，并将线路调度信息分发至预设的域名服务器进行执行，为实现实时地线路调优和资源合理分布提供了基础，适用于CDN网内调度以及跨CDN的混合CDN调度，应用范围较广。并且，无需过多的人员干预操作，节省了企业人力和财力，有效地控制了运维成本。
优选地，域名***DNS调度方法中，根据各服务节点的评分值，生成待调度域名的线路调度信息，具体包括：对满足线路筛选条件的各服务节点按照评分值的高低进行排序；根据排序结果，生成所待调度域名的线路调度信息，从而能够实现解析线路调优和资源合理分布。
优选地，域名***DNS调度方法中，将线路调度信息发布至预设的域名服务器后，还包括：将包含线路调度信息的提示信息推送至预设终端，从而令技术人员能够及时地了解到较多的有效信息。
附图说明
一个或多个实施方式通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施方式的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有 特别申明，附图中的图不构成比例限制。
图1是根据第一实施方式的服务节点的评分方法的具体流程图；
图2是根据第二实施方式的域名***DNS调度方法的具体流程图；
图3是根据第四实施方式的服务器的示意图。
具体实施方式
为使本发明实施方式的目的、技术方案和优点更加清楚，下面将结合附图对本发明的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本发明各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。
本发明的第一实施方式涉及一种服务节点的评分方法，具体流程如图1所示。本实施方式中服务节点的评分方法在一服务器上进行实施，以下简称该服务器为资源评分中心。本实施方式中评分方法的实现步骤如下：
步骤101，获取服务节点的地址信息。
具体地说，服务节点可以为源站服务节点，也可以为加速服务节点。技术人员将需要评分的服务节点的地址信息发送至资源评分中心。其中，服务节点的地址信息可以为IP地址，也可以为别名记录CNAME地址。
步骤102，根据服务节点的地址信息，对服务节点进行监测，获取服务节点的若干个性能参考信息，并根据若干个性能参考信息，对服务节点进行评分。
具体地说，资源评分中心可以控制一台或多台监控机对服务节点进行实时监控探测。也就是说，每个监控机均可以对服务节点进行若干个性能监测，以获取服务节点的若干个性能参考信息。这样，资源评分中心便可以根据每台监控机获取到的服务节点的若干个性能参考信息，对服务节点进行评分。
以下对本实施方式中步骤102的具体实现方式进行举例说明，步骤102包括子步骤1021至子步骤1026，具体如下：
子步骤1021，判断服务节点的地址信息是否为CNAME地址。若是，则执行步骤1022，否则执行步骤1024。
具体地说，若服务节点的地址信息为一个域名，如某一CDN服务商的域名，则子步骤1021的判断结果为是。若服务节点的地址信息为一个IP地址，则子步骤1021的判断结果为否。
子步骤1022，获取服务节点的资源响应时间及下载速度。
具体地说，资源评分中心可以控制一台或多台监控机对服务节点进行实时监控探测。如，资源评分中心控制监控机对服务节点进行网络诊断PING(Packet Internet Groper，简称“PING”)监控，来获取服务节点的下载速度，对服务节点进行DNS监控，以获取服务节点的资源响应时间。
更具体地说，技术人员可以预先在资源评分中心中设置监控机的探测时间频率，以便于资源评分中心能够控制监控机获取较为准确且具有代表性的数据。如，探测时间频率可以为2分钟/次。
子步骤1023，根据第一预设公式，计算服务节点的评分值。
具体地说，第一预设公式由技术人员预先输入并保存至资源评分中心。本实施方式中，第一预设公式为：T＝(t 0/t)*(v/v 0)；其中，T为评分值，t为资源响应时间，t 0为预设的资源响应时间，v为下载速度，v 0为预设的下载速度。如，资源评分中心控制一台监控机对服务节点进行实时监控探测。该监控机监测到的t为40ms，v为2500k/s，预设的t 0为100ms，v 0为1250k/s，则T＝(100/40)*(2500/1250)＝5。
需要注意的是，若资源评分中心控制多台监控机对服务节点进行实时监控探测，则服务节点的评分值为T的平均值。如，资源评分中心控制两台监控机对服务节点进行实时监控探测，一台监控机监测到的t为40ms，v为2500k/s，另一台监测到的t为60ms，v为2000k/s；预设的t 0为100ms，v 0为1250k/s，则T＝((100/40)*(2500/1250)+(60/40)*(2000/1250))/2＝(5+2.67)/2＝3.84。
子步骤1024，判断服务节点的地址信息是否为IP地址。若是，则执行步骤1025，否则结束本流程。
子步骤1025，获取服务节点的资源响应时间、带宽使用率以及资源内存负载。
具体地说，资源评分中心可以控制一台或多台监控机对服务节点进行实时监控探测。如，控制监控机对服务节点进行网络诊断PING(Packet Internet Groper，简称“PING”)监控，来获取服务节点的下载速度，对服务节点进行端口监控，以获取服务节点的带宽使用率，对服务节点进行服务器性能监控，以获取资源内存负载。
更具体地说，资源评分中心控制监控机对服务节点进行服务器性能监控，以获取资源内存负载的具体实现方式可以为：资源评分中心控制监控机获取服务节点的CPU使用率、内存使用率以及磁盘占用率，根据公式
Figure PCTCN2018107474-appb-000001
计算获取服务节点的资源内存负载，其中，z为资源内存负载，A1为CPU使用率，A2为内存使用率，A3为磁盘占用率；a 为CPU使用率的预设权重，b为内存使用率的预设权重，c为磁盘占用率的预设权重。
如，假设a、b、b均为1，监控机获取服务节点的CPU使用率为40％、内存使用率为40％、磁盘占用率为40％，则
Figure PCTCN2018107474-appb-000002
需要注意的是，本实施方式中资源内存负载的计算公式为
Figure PCTCN2018107474-appb-000003
在实际操作时，资源评分中心获取到的服务节点的若干个性能参考信息不仅限于资源响应时间、带宽使用率以及资源内存负载时，技术人员可以对资源内存负载的计算公式进行一定的变形，如，资源内存负载的计算公式可以变形为
Figure PCTCN2018107474-appb-000004
其中，A1至An表示各性能参考信息的具体数值，m表示资源评分中心所获取的性能参考信息的个数，x表示An性能参考信息的预设权重。
子步骤1026，根据第二预设公式，计算服务节点的评分值。
具体地说，第二预设公式由技术人员预先输入并保存至资源评分中心。本实施方式中，第二预设公式为：T＝(t 0/t)*(n/n 0)*(z/z 0)；其中，T为评分值，t为资源响应时间，t 0为预设的资源响应时间，n为带宽使用率，n 0为预设的带宽使用率；z为资源内存负载；z 0为预设的资源内存负载。如，资源评分中心控制一台监控机对服务节点进行实时监控探测。该监控机监测到的t为50ms，n为40％，z为
Figure PCTCN2018107474-appb-000005
预设的t 0为200ms，n 0为80％，z 0为80％，则
Figure PCTCN2018107474-appb-000006
更具体地说，若资源评分中心控制多台监控机对服务节点进行实时监控探测，则服务节点的评分值为T的平均值。如，资源评分中心控制两台监控机对服务节点进行实时监控探测，一台监控机监测到的t为50ms，n为40％，z为
Figure PCTCN2018107474-appb-000007
另一台监测到的t为60ms，n为60％，z为
Figure PCTCN2018107474-appb-000008
则T＝(16+8.53)/2＝12.27。
需要注意的是，上述对步骤102的阐述，仅为方便理解所提供的一种示例性说明，本实施方式并不对性能参考信息，以及根据性能参考信息，对服务节点进行评分的具体实现形式做任何限定。在实际应用时，技术人员可以根据实际需要设置性能参考信息的具体实现形式，以及评分的具体实现形式。
本发明的实施方式相对于现有技术而言，提出了一种服务节点的评分方法，根据所获取的服务节点的地址信息，对服务节点进行监控，以便于获取服务节点的若干个性能参考信息，从而对服务节点进行评分。这样，服务节点的评分可以直观地反应出该服务节点是否用，该服务节点是否为优质服务节点等信息，为实现资源的合理分配提供了基础。
本发明的第二实施方式涉及一种域名***DNS调度方法，具体流程如图2所示。本发明第二实施方式需要调用第一实施方式中服务节点的评分方法，以便于生成某一域名的线路调度信息。本实施方式中域名***DNS调度方法在一服务器上进行实施，以下简称该服务器为调度决策中心。本实施方式中域名***DNS调度方法的具体步骤如下：
步骤201，获取待调度域名以及待调度域名对应的线路服务信息。
具体地说，技术人员将待调度域名以及待调度域名对应的线路服务信息发送至调度决策中心。其中，线路服务信息中至少包括若干个服务节点的地址信息，服务节点可以为源站服务节点，如，服务节点的地址信息可以为IP地址。
更具体地说，线路服务信息中还可以包括各服务节点的地理位置、互联网服务提供商等信息。如，调度决策中心获取的待调度域名以及待调度域名对应的线路服务信息可以如下文中例一所示：
例一：待调度域名为test.example.com；线路服务信息如下表一：
互联网服务提供商 地理位置 源站服务节点的地址信息(IP)
默认 默认 1.1.1.1
福建电信 福建 2.1.1.1
上海移动 上海 3.1.1.1
北京联通 北京 4.1.1.1
步骤202，获取线路服务信息中包括的若干个服务节点的评分值。
具体地说，调度决策中心将线路服务信息中包括的若干个服务节点的地址信息发送至第一实施方式中的资源评分中心，以便于资源评分中心对线路服务信息中包括的若干个服务节点进行评分，并将各服务节点的评分值返回给调度决策中心。
步骤203，根据各服务节点的评分值，生成待调度域名的线路调度信息。
具体地说，调度决策中心可以对各服务节点按照评分值的高低进行排序，并根据排序结果，生成待调度域名的线路调度信息。如，技术人员预先在调度决策中心中配置有线路筛选条件，该线路筛选条件可以为服务节点的评分值大于预设阈值。这样，调度决策中心可以将某些故障线路或负载较重的线路滤除，从而基于较为优质的各服务节点生成线路调度信息。如，调度决策中心可以对满足线路筛选条件(评分值大于预设阈值)的各服务节点按照评分值的高低进行排序，以便于根据排序结果生成调度域名的线路调度信息。
需要注意的是，线路筛选条件还可以为互联网服务提供商所属的类型为预设类型。如，预设类型为电信，则互联网服务提供商为福建电信的服务节点均满足线路筛选条件。这样， 调度决策中心可以对互联网服务提供商所属类型为电信的各服务节点按照评分值的高低进行排序，以便于根据排序结果生成调度域名的线路调度信息。
为方便理解，以下对本实施方式中步骤203的具体实现形式进行举例说明，然而下文所阐述的内容仅作为示例性说明，本实施方式中并不对步骤203的具体实现形式做任何限定。
待调度域名为test.example.com；线路服务信息如表一：
假设部署2个监控机设备Node1、Node2，对各源站服务节点的探测数据如下：
Figure PCTCN2018107474-appb-000009
若，预设的t 0为200ms，n 0为80％，z 0为80％，CPU使用率的预设权重、内存使用率的预设权重以及磁盘占用率的预设权重均为1，则各源站服务节点的评分表如下：
Figure PCTCN2018107474-appb-000010
若，预设类型包括目前所有的互联网服务提供商所属的类型，即，当前调度允许跨运营商访问，则调度决策中心可从排序中筛选最靠前的服务节点，以便于当某线路故障时或者负载较重时，可以将筛选出的优质服务节点进行替换覆盖，保障该线路的正常解析可用。
若，预设类型包括目前部分互联网服务提供商所属的类型，即，当前调度不允许跨运营商进行访问，则调度决策中心需先去除预设类型外的服务节点，再进行排序。并且，线路服 务信息中包括各服务节点的等级时，调度决策中心可以按照等级高低以及排序结果，生成待调度域名的线路调度信息。如，当低级线路故障，解析线路可由低级线路逐级向上级线路切换，如当福建电信2.1.1.1故障，则优先切换至中国电信线路，没有中国电线路或电信线路下IP全部宕机时，切换至默认线路1.1.1.1。当默认线路全部故障时，自动将按评分值排前资源，进行替换解析。
需要注意的是，由于监控机是按照探测时间频率对各服务节点进行监测的，因而探测时间频率在2分钟/次左右时，资源评分中心能够控制监控机获取较为准确地，具有代表性的数据，而且资源评分中心可以为各服务节点进行较为实时地动态评分，为后续调度决策中心能够生成较为实时的动态线路调度信息提供了基础。这样，有效地保证了域名***调整的及时性以及灵活性，避免了现有技术中人工手动模式的优化所造成的时效性方面置后的问题。
值得一提的是，调度决策中心生成待调度域名的线路调度信息时，还可以依据技术人员预设的调度方式，为线路调度信息中包括的各服务节点设置负载值。如，预设的调度方式为主备调度方式，则可以令排序第一的服务节点作为主调度线路，排序第二的服务节点作为备用调度线路。如，预设的调度方式为负载均衡时，令排序第一以及排序第二的服务节点各负载50％的调度流量。这样，从而可以实现动态负载均衡、多级主备切换的目的。
步骤204，将线路调度信息发布至预设的域名服务器。
具体地说，技术人员可以预先将一个或多个域名服务器的地址信息输入并保存至调度决策中心中，以便于调度决策中心根据当前存储的域名服务器的地址信息，将线路调度信息发布至预设的域名服务器，令域名服务器执行线路调度信息，为实现线路调度信息的全面覆盖提供了基础。
需要注意的是，本实施方式中，调度决策中心将线路调度信息发布至各域名服务器后，还可以将线路调度信息推送至预设终端，从而令技术人员能够及时地了解到较多的有效信息。其中，预设终端可以为技术人员的手机、电脑、平板电脑。调度决策中心可以通过邮件、短信、微信、站内信等各种渠道向预设终端推送信息。并且，调度决策中心还可以向用户告知资源故障、资源切换、资源恢复等信息。
如，包含线路调度信息的提示信息可以以如下形式存在，然而，下文提示信息的举例仅作为示例性的说明，在实际操作时，技术人员可以预设提示信息中所包括的提示项目。
[消息类型]:调度切换
[策略类型]:线路调度
[发生时间]:2017-11-23 11:57:35
[域名]:test.example.com
[线路]:默认线路
[调度信息]:1.1.1.1替代2.1.1.1。
本实施方式中，技术人员还可以在调度决策中心中设置切换时机，如，立即切换、延迟切换或手动切换，以便于调度决策中心根据切换时机，决定发布线路调度信息的时间。
不难看出，本实施方式中的调度决策中心相当于一个CDN网络流量分配调度***，根据待调度域名对应的各服务节点的评分值，来生成待调度域名的线路调度信息，并将线路调度信息分发至域名服务器进行执行，实现了实时线路调优和资源合理分布的目的。这样，技术人员只需建立简单的域名配置表(如表一所示)，调度***就能够实现各服务节点的优劣评判，以便于自动生成较优的线路调度信息进行全网覆盖，从而无需过多的人员干预操作，在有效地保障服务质量的情况下，节省了企业人力和财力，有效地控制了运维成本。
本发明第三实施方式涉及一种域名***DNS调度方法。本发明第三实施方式与第二实施方式大致相同，主要区别之处在于：本发明第三实施方式适用于跨CDN的混合CDN调度情况，以下进行具体说明：
本实施方式中调度方法的具体步骤与第二实施方式相同，主要不同之处在于各步骤的具体实现形式，以下进行具体说明
步骤201，获取待调度域名以及待调度域名对应的线路服务信息。
具体地说，技术人员将待调度域名以及待调度域名对应的线路服务信息发送至调度决策中心。其中，线路服务信息中至少包括若干个服务节点的地址信息，服务节点可以为加速服务节点，如，服务节点的地址信息可以为某一CDN的别名记录CNAME地址。
更具体地说，线路服务信息中还可以包括各服务节点的地理位置、互联网服务提供商等信息。如，调度决策中心获取的待调度域名以及待调度域名对应的线路服务信息可以如下文中例二所示：
例二：待调度域名为cdn.example.com；线路服务信息如下表二：
Figure PCTCN2018107474-appb-000011
其中，CDN1、CDN2以及CDN3表示三家CDN服务商的网络流量分配调度***各自的 地址信息。上述表二表示域名为cdn.example.com的内容商需要用到CDN1、CDN2、CDN3三家CDN服务商进行混合加速。
步骤202，获取线路服务信息中包括的若干个服务节点的评分值。
此步骤的具体实现与第二实施方式相同，即，调度决策中心将线路服务信息中包括的若干个服务节点的地址信息发送至第一实施方式中的资源评分中心，以便于资源评分中心对线路服务信息中包括的若干个服务节点进行评分，并将各服务节点的评分值返回给调度决策中心。
步骤203，根据各服务节点的评分值，生成待调度域名的线路调度信息。
假设部署2个监控机设备Node1、Node2，对各加速服务节点探测数据如下：
Figure PCTCN2018107474-appb-000012
若，预设的t 0为100ms，v 0为1250k/s，则各加速服务节点的评分表如下：
Figure PCTCN2018107474-appb-000013
则，基于上述评分信息，调度决策中心可以按资源评分值的高低对各加速服务节点进行排序，并且，线路调度信息可以根据加速服务节点的预设数量进行设置，如，预设数量为1时，在福建电信中，优先考虑CDN1；如，预设数量为2时，在福建电信中，优先考虑CDN1以及CDN2。
步骤204，将线路调度信息发布至预设的域名服务器。
此步骤的具体实现与第二实施方式相同，为避免重复，在此不再赘述。
不难看出，本实施方式中的调度决策中心相当于跨CDN的网络流量分配调度***，适用 于混合CDN调度(即跨CDN调度)情况，该调度方法根据待调度域名对应的各服务节点的评分值，来生成待调度域名的线路调度信息，并将线路调度信息分发至域名服务器进行执行，实现了动态根据各CDN加速质量进行优选的目的，能够实时地进行线路调优和资源合理分布。并且，无需过多的人员干预操作，大大地节省了企业人力和财力，控制了运维成本。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本发明第四实施方式涉及一种服务器，如图3所示，包括：至少一个处理器301；以及，与至少一个处理器301通信连接的存储器302；其中，存储器302存储有可被至少一个处理器301执行的指令，指令被至少一个处理器301执行，以使至少一个处理器301能够执行上述方法实施方式中的域名***DNS调度方法。
其中，存储器302和处理器301采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器301和存储器302的各种电路连接在一起。总线还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器301处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器301。
处理器301负责管理总线和通常的处理，还可以提供各种功能，包括定时，***接口，电压调节、电源管理以及其他控制功能。而存储器302可以被用于存储处理器301在执行操作时所使用的数据。
本发明的实施方式相对于现有技术而言，为实现解析线路调优和资源合理分布提供了基础。并且，无需过多的人员干预操作，就实现了域名***的调度，节省了企业人力和财力，有效地控制了运维成本。
本发明第五实施方式涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施方式。
本发明的实施方式相对于现有技术而言，为实现解析线路调优和资源合理分布提供了基础。并且，无需过多的人员干预操作，就实现了域名***的调度，节省了企业人力和财力，有效地控制了运维成本。
即，本领域技术人员可以理解，实现上述实施方式方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施方式所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本发明的具体实施方式，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本发明的精神和范围。

Claims (10)

  1. [根据细则91更正 01.04.2019]
    一种服务节点的评分方法，其特征在于，包括：
    获取服务节点的地址信息；
    根据所述服务节点的地址信息，对所述服务节点进行监测，并获取所述服务节点的若干个性能参考信息；
    根据所述若干个性能参考信息，对所述服务节点进行评分。
  2. 根据权利要求1所述的服务节点的评分方法，其特征在于，所述根据所述服务节点的地址信息，对所述服务节点进行监测，并获取所述服务节点的若干个性能参考信息，具体包括：
    若所述服务节点的地址信息为别名记录CNAME地址，则获取所述服务节点的资源响应时间以及下载速度；
    所述根据所述若干个性能参考信息，对所述服务节点进行评分，具体包括：
    根据公式T＝(t 0/t)*(v/v 0)，计算所述服务节点的评分值；
    其中，T为所述评分值，t为所述资源响应时间，t 0为预设的资源响应时间，v为所述下载速度，v 0为预设的下载速度。
  3. 根据权利要求1所述的服务节点的评分方法，其特征在于，所述根据所述服务节点的地址信息，对所述服务节点进行监测，并获取所述服务节点的若干个性能参考信息，具体包括：
    若所述服务节点的地址信息为IP地址，则获取所述服务节点的资源响应时间、带宽使用率以及资源内存负载；
    所述根据所述服务节点的性能参考信息，对所述服务节点进行评分，具体包括：
    根据公式：T＝(t 0/t)*(n/n 0)*(z/z 0)，计算所述服务节点的评分值；
    其中，T为所述评分值，t为所述资源响应时间，t 0为预设的资源响应时间，n为所述带宽使用率，n 0为预设的带宽使用率；z为所述资源内存负载；z 0为预设的资源内存负载。
  4. 根据权利要求3所述的服务节点的评分方法，其特征在于，获取所述服务节点的资源内存负载，具体包括：
    获取所述服务节点的CPU使用率、内存使用率以及磁盘占用率；
    根据公式
    Figure PCTCN2018107474-appb-100001
    计算获取所述服务节点的资源内存负载；
    其中，z为所述资源内存负载，A 1为所述CPU使用率，A 2为所述内存使用率，A 3为所述磁盘占用率；a为所述CPU使用率的预设权重，b为所述内存使用率的预设权重，c为所述磁盘占用率的预设权重。
  5. 一种域名***DNS调度方法，其特征在于，包括：
    获取待调度域名以及所述待调度域名对应的线路服务信息；其中，所述线路服务信息中至少包括若干个服务节点的地址信息；
    利用如权利要求1至4中任意一项所述的服务节点的评分方法，对若干个所述服务节点进行评分；
    根据各所述服务节点的评分值，生成所述待调度域名的线路调度信息；
    将所述线路调度信息发布至预设的域名服务器，以供所述域名服务器执行所述线路调度信息。
  6. 根据权利要求5所述的域名***DNS调度方法，其特征在于，所述根据各所述服务节点的评分值，生成所述待调度域名的线路调度信息，具体包括：
    对满足所述线路筛选条件的各所述服务节点按照评分值的高低进行排序；
    根据所述排序结果，生成所待调度域名的线路调度信息。
  7. 根据权利要求6所述的域名***DNS调度方法，其特征在于，所述线路筛选条件为以下条件的其中之一或任意组合：
    服务节点的评分值大于预设阈值、服务节点的互联网服务提供商所属的类型为预设类型。
  8. 根据权利要求5所述的域名***DNS调度方法，其特征在于，所述将所述线路调度信息发布至预设的域名服务器后，还包括：
    将包含所述线路调度信息的提示信息推送至预设终端。
  9. 一种服务器，其特征在于，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求5至8中任一所述的域名***DNS调度方法。
  10. 一种计算机可读存储介质，存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求5至8中任一所述的域名***DNS调度方法。
PCT/CN2018/107474 2018-07-24 2018-09-26 服务节点的评分方法、域名***dns调度方法及服务器 WO2020019472A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18918414.6A EP3629521B1 (en) 2018-07-24 2018-09-26 Rating method for service node, domain name system (dns) scheduling method and server
US16/482,383 US20210409298A1 (en) 2018-07-24 2018-09-26 Method for scoring a service node, and method and server for scheduling a domain name system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810816718.6A CN109167674B (zh) 2018-07-24 2018-07-24 服务节点的评分方法、域名***dns调度方法及服务器
CN201810816718.6 2018-07-24

Publications (1)

Publication Number Publication Date
WO2020019472A1 true WO2020019472A1 (zh) 2020-01-30

Family

ID=64898233

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107474 WO2020019472A1 (zh) 2018-07-24 2018-09-26 服务节点的评分方法、域名***dns调度方法及服务器

Country Status (4)

Country Link
US (1) US20210409298A1 (zh)
EP (1) EP3629521B1 (zh)
CN (1) CN109167674B (zh)
WO (1) WO2020019472A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430402A (zh) * 2020-10-15 2022-05-03 ***通信集团浙江有限公司 网络域名流量调度方法、装置及计算设备
WO2022100318A1 (zh) * 2020-11-12 2022-05-19 腾讯科技（深圳）有限公司 雾节点调度方法、装置、计算机设备和存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109901927A (zh) * 2019-02-21 2019-06-18 国泰君安证券股份有限公司 智能化任务动态调度***及其方法
CN110677307B (zh) * 2019-10-30 2022-11-25 北京博睿宏远数据科技股份有限公司 一种服务监测方法、装置、设备和存储介质
CN110944061A (zh) * 2019-12-06 2020-03-31 北京博睿宏远数据科技股份有限公司 内容分发网络调度方法、装置、计算机设备及存储介质
CN111371916B (zh) * 2020-02-26 2021-03-19 腾讯科技（深圳）有限公司 一种数据处理方法及相关设备
CN111582628B (zh) * 2020-03-24 2024-04-09 网宿科技股份有限公司 质量评估方法及装置
CN111479137B (zh) * 2020-04-16 2022-02-18 广州酷狗计算机科技有限公司 线路地址的提供方法、装置、服务器及存储介质
CN112714100B (zh) * 2020-11-30 2023-01-10 互联网域名***北京市工程研究中心有限公司 域名解析服务安全的预测方法和***
CN112965795B (zh) * 2021-02-23 2024-06-07 卓望数码技术（深圳）有限公司 集群调度方法、电子设备及存储介质
CN114448990B (zh) * 2021-12-23 2023-06-23 天翼云科技有限公司 一种基于融合cdn的资源调度方法、装置及设备
CN114826908B (zh) * 2022-05-09 2024-03-26 新华智云科技有限公司 kubernetes集群服务保障方法、组件、***

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945198A (zh) * 2014-05-13 2014-07-23 高新兴科技集团股份有限公司 一种控制视频监控***流媒体路由的***和方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7590739B2 (en) * 1999-11-22 2009-09-15 Akamai Technologies, Inc. Distributed on-demand computing system
US20100088405A1 (en) * 2008-10-08 2010-04-08 Microsoft Corporation Determining Network Delay and CDN Deployment
CA2741895C (en) * 2008-11-17 2015-01-20 Amazon Technologies, Inc. Request routing and updating routing information utilizing client location information
CN102868935A (zh) * 2012-08-24 2013-01-09 乐视网信息技术（北京）股份有限公司 在内容分发网络中响应多源的调度方法
CN104427005B (zh) * 2013-08-20 2018-01-02 阿里巴巴集团控股有限公司 在cdn上实现请求精确调度的方法及***
CN104168341B (zh) * 2014-08-15 2018-01-19 北京百度网讯科技有限公司 Ip地址的定位方法和cdn调度方法以及装置
CN104994123B (zh) * 2015-05-12 2018-10-02 段利平 一种cdn云平台及cdn云平台的流量调度方法
CN105897822B (zh) * 2015-11-11 2019-07-26 法法汽车(中国)有限公司 一种内容分发网络cdn节点选择方法及其装置
CN105516391B (zh) * 2015-12-25 2018-12-21 互联网域名***北京市工程研究中心有限公司 一种基于cname的dns域名解析方法
CN105847353A (zh) * 2016-03-22 2016-08-10 中国科学院信息工程研究所 一种面向移动通信网络的移动cdn内容调度方法与***
CN107645525A (zh) * 2016-07-21 2018-01-30 阿里巴巴集团控股有限公司 内容分发网络的探测处理、调度方法及相应装置、节点
CN106301966B (zh) * 2016-10-25 2019-08-06 北京云端智度科技有限公司 一种基于域名的按比例分配流量的方法
CN106992938B (zh) * 2017-05-15 2020-03-31 网宿科技股份有限公司 一种网络流量动态调度分配方法及***
CN107342913B (zh) * 2017-05-24 2020-02-07 恒安嘉新（北京）科技股份公司 一种cdn节点的探测方法和装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103945198A (zh) * 2014-05-13 2014-07-23 高新兴科技集团股份有限公司 一种控制视频监控***流媒体路由的***和方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430402A (zh) * 2020-10-15 2022-05-03 ***通信集团浙江有限公司 网络域名流量调度方法、装置及计算设备
CN114430402B (zh) * 2020-10-15 2023-11-10 ***通信集团浙江有限公司 网络域名流量调度方法、装置及计算设备
WO2022100318A1 (zh) * 2020-11-12 2022-05-19 腾讯科技（深圳）有限公司 雾节点调度方法、装置、计算机设备和存储介质
US11838387B2 (en) 2020-11-12 2023-12-05 Tencent Technology (Shenzhen) Company Limited Fog node scheduling method and apparatus, computer device, and storage medium

Also Published As

Publication number Publication date
EP3629521B1 (en) 2021-05-12
CN109167674A (zh) 2019-01-08
CN109167674B (zh) 2021-05-18
US20210409298A1 (en) 2021-12-30
EP3629521A4 (en) 2020-04-29
EP3629521A1 (en) 2020-04-01

Similar Documents

Publication Publication Date Title
WO2020019472A1 (zh) 服务节点的评分方法、域名***dns调度方法及服务器
WO2020253266A1 (zh) 一种提供边缘服务的方法、装置和设备
CN108712464A (zh) 一种面向集群微服务高可用的实现方法
CN107635015B (zh) 移动终端与服务器端链接的最优路径选择***及方法
WO2011000199A1 (zh) 集群服务器智能调度的方法及***
CN109660466A (zh) 一种面向云数据中心租户的多活负载均衡实现方法
CN108174397A (zh) 一种任务驱动的多网关协同方法
CN109756474B (zh) 一种电力调度自动化***的服务跨区域调用方法及装置
US11985049B2 (en) Method and system for guaranteeing service application experience
US20170366441A1 (en) Transmitting test traffic on a communication link
CN113301079B (zh) 一种数据的获取方法、***、计算设备及存储介质
WO2019149166A1 (zh) 网络访问方法、客户端、网络交互方法及调度、网络***
EP3857978A1 (en) Network slice redirection management
WO2021083196A1 (zh) 网络流量的迁移方法及装置
US20190306228A1 (en) Data prioritization and scheduling system
CN110380981B (zh) 一种流量分发方法及设备
US10715608B2 (en) Automatic server cluster discovery
CN110213778B (zh) 一种网元主备智能配对的方法及装置
US10834181B2 (en) Load balancing and data prioritization system
JP2022503762A (ja) セルラ電気通信ネットワーク
US20170005889A1 (en) Self-localizing data distribution network
CN107566475B (zh) 一种会话故障转移方法及装置
WO2012175140A1 (en) Gateway selection for load balancing
CN115665263A (zh) 一种流量调拨方法、装置、服务器及存储介质
GB2577526A (en) Network slice management

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018918414

Country of ref document: EP

Effective date: 20191122

NENP Non-entry into the national phase

Ref country code: DE