WO2018210265A1

WO2018210265A1 - Scheduling control method, apparatus, and system

Info

Publication number: WO2018210265A1
Application number: PCT/CN2018/087074
Authority: WO
Inventors: 廖伟健
Original assignee: 腾讯科技（深圳）有限公司
Priority date: 2017-05-18
Filing date: 2018-05-16
Publication date: 2018-11-22
Also published as: CN107071089B; CN107071089A

Abstract

Provided in the present application are a scheduling control method, an apparatus, and a system. The method comprises: obtaining respective average access delays experienced by terminals with different network properties upon accessing each service node in a service system, wherein the network properties of the terminals represent operators and geographical regions to which the terminals belong; and selecting, for each of the terminals having a network property, and from the service nodes in the service system, a service node suitable for access by the terminal with the network property, and using an IP address of the service node suitable for access by the terminal with the network property as an IP address of a service node matching the network property in a domain name resolution list. The solution of the present application enables a more reasonable configuration of service nodes in a domain name resolution list to be accessed by terminals with different network properties, thus reducing access delay when accessing service nodes in a service system by the terminals, and enhancing access speed.

Description

Scheduling control method, device and system

The present application claims priority to Chinese Patent Application No. PCT Application No. No. No. No. No. No. No. No. No. No. No. No. No.

Technical field

The present application relates to the field of network communication technologies, and in particular, to a scheduling control method, apparatus, and system.

Background technique

Computers in the network are located through Internet Protocol (IP) addresses, and IP addresses are difficult to remember. Therefore, domain names are generally used instead of IP addresses. Correspondingly, after receiving the network address input by the user, the terminal needs to send the domain name included in the network address to the domain name server, and the domain name server converts the domain name into an IP address before accessing the network based on the IP address. Host. The process of converting a domain name into an IP address through a domain name server is commonly known as domain name resolution.

In order to meet business needs or improve business processing efficiency, a service system generally deploys multiple service nodes, so that in order to make access requests to the service system can be directed to different service nodes, the domain name server corresponding to the service service system The domain name of the service service system can be resolved to the IP address of a different service node. For example, the domain name server can store the correspondence between different operators, domain names, and IP addresses. Thus, if the operators to which the terminals belong are different, even if the domain names requested by the terminal are the same, the IP address returned by the domain name server for the terminal will be different. However, when the terminal accesses the service system based on the IP address resolved by the domain name server, the access speed is too slow.

Summary of the invention

The present application provides a scheduling control method, apparatus, and system to improve access speed of a service node in a terminal access service system.

In order to solve the above problem, in a first aspect, the application provides a scheduling control method, including:

The average access delay of each service node in the terminal access service system with different network attributes is obtained, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

For a terminal having each network attribute, a service node suitable for access by a terminal having a network attribute is selected from a plurality of service nodes of the service system, wherein a target service suitable for access by a terminal having a target network attribute is selected. a node, the average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition;

For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute.

In a possible implementation manner of the first aspect, for a target service node that is suitable for access by a terminal having a target network attribute, an average access delay of the terminal having the target network attribute suitable for accessing the target service node is satisfied. The first preset condition includes:

The terminal having the target network attribute has the smallest average access delay for accessing the target service node.

In a possible implementation manner of the first aspect, for a target service node that is suitable for access by a terminal having a target network attribute, the load or capacity of the target service node satisfies a second preset condition.

In a possible implementation manner of the first aspect, the IP address of the service node that the terminal having the network attribute is suitable to access is the IP address of the service node that matches the network attribute in the domain name resolution list, and includes:

Sending, by the authoritative domain name server, the IP address of the service node corresponding to the local domain name server having the network attribute in the domain name resolution list stored by the authoritative domain name server. The IP address of the service node that is configured to be accessible to the terminal with network attributes.

In a possible implementation manner of the first aspect, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node that matches the network attribute in the domain name resolution list, including :

Configuring a domain name resolution list stored in the authoritative domain name server according to the IP address of the target service node that the terminal having the network attribute is suitable for accessing, in the domain name resolution list, the service node corresponding to the local domain name server having the network attribute The IP address is configured as the IP address of the service node to which the terminal having the network attribute is suitable to access.

In a possible implementation manner of the first aspect, the obtaining an average access delay of each service node in a terminal access service system having different network attributes includes:

Acquiring an average access delay of each service node in the terminal access service system having different network attributes from the data server, wherein the data server obtains access delays of different service nodes in the plurality of terminal access service systems, according to the access delay The network attributes of the terminal respectively calculate the average access delay of each terminal accessing each service node with each network attribute.

Acquiring access delays of different service nodes in multiple terminal access service systems, where network attributes of the multiple terminals are different;

Determining, by the network attributes of the multiple terminals, at least one terminal having the same network attribute to form a terminal set, to obtain a plurality of terminal sets that represent different network attributes;

For the terminal set with each network attribute, according to the access delay of each service node in the terminal access service system in the terminal set, the average access delay of the terminal accessing each service node in the terminal set is calculated separately, and the difference is obtained. The endpoint of the network attribute accesses the average access latency of each service node.

In a possible implementation manner of the first aspect, the obtaining an average access delay of each service node in a terminal access service system having different network attributes, respectively, includes:

Obtaining an average access delay of each service node in the mobile terminal access service system having different network attributes, where the mobile terminal accesses the service node in the service system by using a wireless network;

For the terminal having each network attribute, a service node that is suitable for access by the terminal having the network attribute is selected from the plurality of service nodes of the service system, including:

For a mobile terminal having each network attribute, a service node suitable for access by a mobile terminal having a network attribute is selected from a plurality of service nodes of the service system;

For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute, including:

For each network attribute, the IP address of the service node that the mobile terminal having the network attribute is suitable to access is used as the IP address of the service node in the first domain name resolution list that matches the network attribute, in the first domain name resolution list. The IP address of the service node to which the mobile terminal having different network attributes needs to be scheduled is stored.

Obtaining an average access delay of each service node in a wired network terminal access service system having different network attributes, where the wired network terminal accesses a service node in the service system based on a wired network;

For a wired network terminal having each network attribute, a service node suitable for access by a wired network terminal having a network attribute is selected from a plurality of service nodes of the service system;

For each network attribute, the IP address of the service node that the terminal of the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute, including:

For each network attribute, the IP address of the service node that the wired network terminal of the network attribute is suitable to access is used as the IP address of the service node in the second domain name resolution list that matches the network attribute, and the second domain name resolution list is The IP address of the service node to which the wired network terminal having different network attributes needs to be scheduled is stored.

In a second aspect, the embodiment of the present application further provides a scheduling control apparatus, including:

An average delay acquisition unit is configured to respectively obtain an average access delay of each service node in the terminal access service system having different network attributes, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

a service node matching unit, configured to: for a terminal having each network attribute, select, from a plurality of service nodes of the service system, a service node that is suitable for access by a terminal having a network attribute, where, for a target network attribute a target service node that is suitable for access by the terminal, and an average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition;

The matching relationship determining unit is configured to, for each network attribute, an IP address of a service node that is suitable for access by the terminal having the network attribute as an IP address of the service node in the domain name resolution list that matches the network attribute.

In a possible implementation manner of the second aspect, for a target service node that is suitable for access by a terminal having a target network attribute, an average access delay of the terminal having the target network attribute accessing the target service node is the smallest.

In a possible implementation manner of the second aspect, for a target service node that is suitable for access by a terminal having a target network attribute, the load or capacity of the target service node satisfies a second preset condition.

In a possible implementation manner of the second aspect, the matching relationship determining unit includes:

a matching relationship sending unit, configured to send an IP address of a service node that is suitable for access by the terminal having the network attribute to the authoritative domain name server, so that the authoritative domain name server will store the domain name resolution list, and the local domain name server with the network attribute The IP address of the corresponding service node is configured as the IP address of the service node to which the terminal having the network attribute is suitable to access.

a matching relationship configuration unit, configured to configure a domain name resolution list stored in an authoritative domain name server according to an IP address of a target service node that is suitable for a terminal having a network attribute, to configure a local domain name with a network attribute in the domain name resolution list The IP address of the service node corresponding to the server is configured as the IP address of the service node to which the terminal having the network attribute is suitable to access.

In a possible implementation manner of the second aspect, the device further includes:

a relationship configuration unit, configured to: in the matching relationship determining unit, the IP address of the service node that the terminal having the network attribute is suitable to access, as the IP address of the service node matching the network attribute in the domain name resolution list, according to the network The matching relationship between the attribute and the IP address of the service node, and configuring the domain name resolution list stored in the authoritative domain name server.

In a possible implementation manner of the second aspect, the average delay acquisition unit is specifically configured to:

Acquiring an average access delay of each service node in the terminal access service system having different network attributes from the data server, wherein the data server obtains access delays of different service nodes in the plurality of terminal access servers, according to the terminal The network attribute calculates the average access delay of each terminal accessing each service node with each network attribute.

In a possible implementation manner of the second aspect, the average delay acquisition unit includes:

a delay acquisition unit, configured to acquire access delays of multiple terminals to different service nodes in the service system, where the plurality of terminals have different network attributes;

a terminal categorizing unit, configured to form, according to network attributes of the multiple terminals, at least one terminal having the same network attribute to form a terminal set, to obtain a plurality of terminal sets that represent different network attributes;

An average delay calculation unit is configured to calculate, according to each network attribute, access delays of each of the service nodes in the terminal set in the terminal set according to the network attribute, and calculate, according to the access delay of each terminal in the terminal set, The average access delay of the service nodes is obtained by the terminal of the network attribute to obtain the average access delay of each service node.

a first time delay acquisition unit, configured to respectively acquire an average access delay of each service node in the mobile terminal access service system having different network attributes, where the mobile terminal accesses the service node in the service system by using a wireless network;

The service node matching unit includes:

a first node matching unit, configured to: for a mobile terminal having each network attribute, select, from among a plurality of service nodes of the service system, a service node that is suitable for access by a mobile terminal with a network attribute;

The matching relationship determining unit includes:

a first relationship determining unit, configured to use, for each network attribute, an IP address of a service node that is suitable for access by the mobile terminal having the network attribute as an IP address of the service node that matches the network attribute in the first domain name resolution list And storing, in the first domain name resolution list, an IP address of a service node that is required to be scheduled by the mobile terminal having different network attributes.

a second time delay acquisition unit, configured to respectively obtain an average access delay of each service node in the wired network terminal access service system for acquiring different network attributes, where the wired network terminal accesses the service node in the service system based on the wired network ;

The service node matching unit includes:

a second node matching unit, configured to: for a wired network terminal having each network attribute, select, from among a plurality of service nodes of the service system, a service node that is suitable for access by a wired network terminal having a network attribute;

The matching relationship determining unit includes:

a second relationship determining unit, configured to, for each network attribute, an IP address of a service node that is suitable for access by the wired network terminal having the network attribute, as an IP address of the service node matching the network attribute in the second domain name resolution list An address, where the second domain name resolution list stores an IP address of a service node that is scheduled to be scheduled by a wired network terminal having a different network attribute.

In a third aspect, the embodiment of the present application further provides a scheduling control system, including:

Data server and configuration server;

The data server is configured to acquire access delays of different service nodes in multiple terminal access service systems; and calculate, for each terminal having each network attribute, each service node in all terminal access service systems having network attributes Average access delay, where the network attribute of the terminal characterizes the operator to which the terminal belongs and the geographic area;

The configuration server is configured to select a terminal having each network attribute from multiple service nodes of the service system according to an average access delay of each service node in the terminal access service system having different network attributes. a service node that is suitable for access, wherein, for a target service node that is suitable for access by a terminal having a target network attribute, an average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition; For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute.

In a possible implementation manner of the third aspect, the data server obtains a delay in accessing different service nodes in a plurality of terminal access service systems, and is specifically configured to acquire different services in multiple mobile terminal access service systems. The access delay of the node and the access delay of different service nodes in the plurality of wired network terminals accessing the service system;

The data server calculates the average access time delay of each service node in the terminal access service system with network attributes for the terminal having each network attribute, specifically for:

Calculating, for a mobile terminal having each network attribute, an average access delay of each service node in the service system having all the network attributes, the mobile terminal accessing the service node in the service system by using a wireless network;

Calculating, for a wired network terminal having each network attribute, an average access delay of each of the service nodes having access to the service system in all of the line network terminals having the network attribute, the wired network terminal accessing the service in the service system based on the wired network node;

The configuration server selects, according to the average access delay of each service node in the terminal access service system having different network attributes, from the plurality of service nodes of the service system, the terminal having each network attribute is suitable. When accessing a service node, it is specifically used to:

Selecting, from the plurality of service nodes of the service system, a service node that is suitable for access by the mobile terminal having each network attribute; or selecting a service node that is suitable for access by the wired network terminal having each network attribute.

In a possible implementation manner of the third aspect, the scheduling control system further includes: a plurality of speed measuring nodes deployed in different equipment rooms in the service system, wherein each service node of the service system is associated with a speed measuring node, and the speed measuring node associated with the service node and the service node are deployed in the same equipment room;

The data server obtains a delay of accessing different service nodes in a plurality of mobile terminal access service systems, and is specifically configured to: obtain access delays of multiple mobile terminals to access different speed measurement nodes;

The data server calculates, for a mobile terminal having each network attribute, an average access time delay of each service node in the service system having all the network attributes, specifically for:

For the mobile terminal with each network attribute, calculate the average access delay of each speed-measuring node in all the mobile terminal access service systems with the network attribute, and determine all the movements with the network attribute according to the association relationship between the speed measuring node and the service node. The average access delay of each service node in the terminal access service system;

The speed measuring node is configured to test an access delay of the target gateway to the speed measuring node according to an IP address of the target gateway returned by the service node associated with the speed measuring node, where the IP address of the target gateway is When the service node associated with the speed measuring node receives the access request of the wired network terminal, the IP address of the gateway to which the wired network terminal belongs is reversely routed, the network attribute of the wired network terminal and the wired network terminal The network attribute of the associated target gateway is the same; the access delay of the target gateway to the speed measuring node is used as the access delay of the wired network terminal to the speed measuring node, and is sent to the data server.

In a fourth aspect, the embodiment of the present application provides a storage medium for storing program code, where the program code is used to execute any one of the scheduling control methods of the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any one of the scheduling control methods of the first aspect.

It can be seen from the above that in the embodiment of the present application, the average access delays of different service nodes in the service system are obtained by the terminals having different network attributes (the carrier and the geographical area to which they belong), and are directed to the terminal having each network attribute. According to the average access delay of the terminal with the network attribute to different service nodes, it is advantageous to select a service node that is more suitable for terminal access with the network attribute from the service system, wherein the terminal is suitable for accessing the terminal with the target network attribute. The target service node, the average access delay of the terminal access target service node having the target network attribute satisfies the first preset condition, so that the access delay of the terminal having the target network attribute accessing the target service node is relatively small. In this way, after the IP address of the service node that the mobile terminal having the network attribute is suitable to access is determined as the IP address of the service node corresponding to the network attribute in the domain name resolution list, when the terminal having the target network attribute subsequently accesses the service system, the authority The domain name server can, according to the domain name resolution list, schedule the terminal of the target network attribute to the target service node with a small access delay, thereby reducing the access delay of the terminal access service system and improving the access of the terminal access service system. speed.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

FIG. 1 is a schematic diagram of a domain name resolution scenario;

FIG. 2 is a schematic diagram of domain name resolution based on a domain name resolution relationship;

FIG. 3 is a schematic diagram showing a possible composition structure of a domain name configuration system to which the method for configuring domain name resolution in the present application is applicable;

FIG. 4 is a schematic structural diagram of a configuration scenario of an application scenario to which the method for configuring domain name resolution in the present application is applied;

FIG. 5 is a schematic flowchart diagram of an embodiment of a method for configuring domain name resolution according to the present application;

FIG. 6 is a schematic flowchart diagram of still another embodiment of a method for configuring domain name resolution according to the present application;

FIG. 7 is a schematic flowchart of the domain name resolution system performing domain name resolution after the domain name resolution list is configured by applying the domain name resolution method in the application of the present application;

FIG. 8 is a schematic structural diagram of an apparatus for configuring domain name resolution according to an embodiment of the present application;

FIG. 9 is a block diagram showing the structure of an embodiment of a configuration server of the present application.

detailed description

In order to facilitate the understanding of the solution of the present application, the scenario of domain name resolution is introduced first. Referring to Figure 1, a schematic diagram of a domain name resolution scenario is shown.

In the scenario of FIG. 1, at least a terminal that initiates a domain name resolution request, a local domain name server (LDNS), a root domain name server, a generic top-level domain name server, and a third-level domain name server are included. The LDNS of different operators is different. Even if the same carrier is deployed in different locations, different LDNSs may be deployed. Therefore, when the operators to which the terminals belong and the location range are different, the LDNS corresponding to the terminals is also different.

FIG. 1 is a manner of performing domain name resolution by recursively. In the scenario of FIG. 1, LDNS may also be referred to as a recursive domain name resolution server.

As shown in Figure 1, in the step 101, the domain name resolution request sent by the terminal to the local domain name server of the operator carries the domain name "WWW.XXX.com." to be resolved.

In step 102, the LDNS initiates a domain name resolution request to the root domain name server.

In step 103, the root domain name server returns the address of the generic top level domain server for the LDNS.

Since the root domain name server cannot determine the IP address corresponding to the domain name "WWW.XXX.com.", but only knows the address of the generic top-level domain name server that needs to be accessed by the generic top-level domain name ".com." in the domain name, The root name server will instruct the LDNS to access the generic top-level domain server.

In step 104, the LDNS initiates a domain name resolution request to the generic top level domain server.

In step 105, the generic top-level domain name server returns the address of the third-level domain name server that the domain name "WWW.XXX.com." needs to access for the LDNS.

Since the generic top-level domain name server cannot resolve the IP address corresponding to the "WWW.XXX.com.", the generic top-level domain name server can determine the third access required to resolve the domain name "***.XXX.com." The domain name server, therefore, the generic top-level domain server sends the address of the third-level domain name server to the LDNS.

In step 106, the LDNS sends a domain name resolution request to the third level domain name server.

In step 107, after the third-level domain name server queries the IP address corresponding to the domain name "WWW.XXX.com.", the queried IP address is returned to the LDNS.

In step 108, the LDNS returns the IP address corresponding to the domain name "WWW.XXX.com." to the terminal.

It can be seen from the above that the LDNS needs to start the first-level recursion from the root domain name server, and finally finds the third-level domain name server, and the third-level domain name server resolves the domain name into an IP address. It can be understood that FIG. 1 is only an example of a domain name resolution system including three levels of recursion. In this case, the lowest level domain name server is a third level domain name server, but in actual application, LDNS may be After more levels of recursion, you can finally locate the lowest-level domain name server, and the domain name server resolves the domain name to an IP address.

The bottom-level domain name server is also referred to as an authoritative domain name server. The domain name and the IP address are configured in the authoritative domain name server, such as a domain name resolution list. It can be seen that only the LDNS locates the authoritative domain name server, and the operation of resolving the domain name into an IP address can be completed through the authoritative domain name server.

Of course, FIG. 1 is only a domain name resolution process described in order to understand the domain name resolution process. In actual applications, the process of domain name resolution may have other possibilities, which is not limited in this application.

The inventor of the present application has conducted research on the process of domain name resolution. It is found that the LDNS corresponding to the terminal can represent the operator to which the terminal belongs and the geographical area in which the terminal belongs. Currently, LDNS is generally configured in the authoritative domain name server. The correspondence between the identifier, domain name, and IP address. At present, when a domain name of a service system corresponds to an IP address of a plurality of service nodes, the proximity access is generally adopted according to the operator and the geographical area to which the LDNS belongs, and the location of the plurality of service nodes in the service system. In principle, the IP address of the service node that is closer to the LDNS is selected from the plurality of IP addresses, and the correspondence between the selected IP address and the LDNS and the domain name is established.

Referring to Figure 2, taking two different LDNSs as an example, assume that one LDNS is the LDNS of the telecom operator in Guangzhou, and one LDNS is the LDNS of the Unicom operator in Shanghai. At the same time, it is assumed that the service system is in Guangzhou with the telecom operator. The IP address of the nearest service node of LDNS is: 119.***.15.13, and the IP address of the service node closest to the LDNS of China Unicom's operator in Shanghai is: 123.***.119.147, then the authoritative domain name server The following two correspondences can be stored:

Domain name: www.a*b.com, Guangzhou - Telecom operator, IP address: 119.***.15.13;

Domain name: www.a*b.com, Shanghai-China Unicom operator, IP address: 123.***.119.147.

Correspondingly, as can be seen from Figure 2, when the terminal of the Guangzhou-telecom operator and the terminal of the Shanghai-China Unicom operator initiate a resolution request for www.a*b.com, the authoritative domain name server will return according to the above correspondence. Different IP addresses.

However, the above correspondence is established for the authoritative domain name server according to the nearest access principle, but the access delay (or network delay) of the terminal accessing different service nodes is not considered. The access delay may be considered as the time required for the packet sent from the terminal to reach the serving node. Although the location of the service node is close to the location of the LDNS corresponding to the terminal, the access delay of the terminal accessing the service node may be large, so that the access speed of the terminal accessing the service system is slow, which affects Access the access experience of the service system.

In order to solve the above problem, the embodiment of the present application provides a scheduling control method, in which a terminal having different network attributes (for example, information indicating a terminal or a device to which a device belongs and a geographical area) is separately required. Counting the average access delay of each service node in the terminal access service system with each network attribute; selecting the average access delay for the different service nodes of the service system for each terminal having each network attribute, respectively, from the service system a service node that is suitable for access by a terminal having a network attribute, for a target service node that is suitable for access by a terminal having a target network attribute, and an average access delay of the terminal having the target network attribute accessing the target service node satisfies a first pre- Set conditions. And the IP address of the service node that the terminal having the network attribute is suitable to access is the IP address of the service node that matches the network attribute in the domain name resolution list. It can be seen that, when the solution of the present application determines the IP address of the service node that needs to be matched by different network attributes in the domain name resolution table, the average access delay of each service node in the terminal access service system with different network attributes is comprehensively considered, thereby It is possible to reasonably determine the service nodes that need to be scheduled by different terminals, thereby reducing the access delay of the terminal access service system and improving the access speed of the terminal access service system.

In order to facilitate the understanding of the solution of the present application, a scheduling control system used in the method for configuring domain name resolution information of the present application is first introduced, as shown in FIG. 3.

As can be seen from FIG. 3, the dispatch control system can include:

Data server 301 and configuration server 302;

The data server 301 is configured to obtain access delays of different service nodes in the plurality of terminal access service systems, where network attributes of the multiple terminals are not identical; for the terminals having each network attribute, respectively, the network is calculated. All the terminals of the attribute access the average access delay of each service node, wherein the network attribute of the terminal can represent the operator to which the terminal belongs and the geographical area. Of course, the network attribute may also include other network attributes of the terminal, and Limit it.

Correspondingly, the configuration server 302 is configured to obtain, from the data server 301, an average access delay of each service node in the terminal access service system having different network attributes; for the terminal having each network attribute, multiple from the service system In the service node, a service node that is suitable for access by a terminal having a network attribute is selected, and an IP address of a service node that is suitable for access by a terminal having a network attribute is used as a service node that matches a network attribute in a domain name resolution list. IP address. The average access delay of the terminal having the target network attribute accessing the target service node meets the first preset condition, for the terminal having the target network attribute being suitable for accessing the target service node. For example, the first preset condition may be that the average access delay of the terminal having the target network attribute accessing the target service node is smaller than the access of the service access node other than the target service node in the terminal access service system having the target network attribute. Delay.

Optionally, the configuration server 302 is further configured to configure, according to the service node that matches the different operators and the geographic area, the correspondence between the different operators and the geographical area and the service node in the domain name resolution list of the authoritative domain name server. . It can be understood that the above is an example in which the data server 301 calculates the average access delay of all the terminals having the network attributes to the service nodes in the service system, but in actual applications, the calculation average can also be completed by the configuration server. The operation of accessing the delay is not limited here.

Of course, in the actual application, the configuration server 302 and the data server 301 may be separately set as shown in FIG. 3, or may be combined into one server. For example, the configuration server 302 may be integrated into the data server 301. A functional module for accessing latency data.

For ease of understanding, an application scenario to which a scheduling control method in the embodiment of the present application is applied is introduced below. FIG. 4 is a schematic diagram showing the structure of an application scenario used in the embodiment of the present application.

As shown in FIG. 4, the application scenario includes: a service system 40, a domain name resolution system 41, and a scheduling control system 42.

The service system 40 includes a plurality of service nodes 401 deployed at different locations.

The domain name resolution system 41 includes at least an authoritative domain name server 411 and a plurality of local domain name servers LDNS 412.

The network attribute of each LDNS 412 is different, and the network attribute of the LDNS can also be the operator and the geographical area to which the LDNS belongs. For example, the multiple LDNSs may include at least: a first LDNS that is deployed in the first geographic area and belongs to the first operator; a second LDNS that is deployed in the second geographic area and belongs to the first carrier; a third LDNS that is located in a geographic area and belongs to the second operator; a fourth LDNS that is deployed in the second geographic area and belongs to the second operator, where the first geographic area is different from the second geographical area, and the first An operator is different from the second carrier.

The domain name resolution list is stored in the authoritative domain name server 411, and the domain name resolution list may include: a correspondence between a domain name of the service system, a network attribute, and an IP address of the service node in the service system. Considering that the network attributes of different LDNSs are different, the domain name resolution list may specifically store the correspondence between the domain name of the service system, the identifier of the LDNS, and the IP address of the service node in the service system.

The dispatch control system 42 includes a data server 421 and a configuration server 422.

The specific functions of the data server 421 and the configuration server 422 can be referred to the related introduction.

Correspondingly, the configuration server 422 can also be connected to the authoritative domain name server 411 via the network, so that the configuration server 422 can send information of the service node suitable for the terminal having each network attribute to the authoritative domain name server 411, or the authority The domain name resolution list in the domain name server 411 is configured.

In this application scenario, the terminal 43 belonging to different LDNSs (only one terminal is shown in FIG. 4) may be further included, wherein the network attributes of the terminals 43 belonging to different LDNSs are different. For example, if the terminal 1 belongs to the LDNS set by the operator A at the city M, the operator of the terminal 1 is the operator A, and the terminal 1 is the terminal of the user of the operator A in the range of the city M.

It can be understood that there are many ways to obtain the access delay of the terminal to access different service nodes. For example, when the terminal accesses the service node, the service system 40 may instruct the terminal to send a test data packet to different service nodes; the time when the terminal transmits the test data packet, and the time of the response data packet of the test data packet returned by the service node. To determine the access delay of the terminal to access the service node; correspondingly, the terminal may send an access delay to test access to different service nodes to the data server.

Optionally, because the service nodes need to process different services at different times, in order to avoid the test of the access delay caused by the service node processing the service, and to avoid the test access delay, the service processing of the service node is affected. In the application scenario of FIG. 4, the method further includes: a speed measuring node 402 associated with the service node 401, each service node 401 is associated with at least one speed measuring node 402, and the speed measuring node 402 is at the same position as its associated service node 401, specific The speed measuring node 402 associated with the service node 401 and the service node 401 can be deployed in the same equipment room.

Since the speed measuring node 402 associated with the service node 401 and the service node 401 are deployed at the same location (eg, in the same equipment room), the same terminal accesses the access delay of the speed measuring node 402, and the terminal accesses the speed measuring node 402. The access delay of the associated service node 401 is the same.

The access delay of the speed measurement node 402 is accessed by the test terminal, and the tested access delay is used as the access delay of the service node 401 associated with the speed measurement node 402, so that the terminal can access the service node 401 more realistically. The network state makes the access latency closer to the real network latency.

Correspondingly, in the scenario of FIG. 4, the data server 421 can be connected to the speed measuring node 402 through a network, so that the data server 421 can obtain the access delay of different terminals reported by the speed measuring node 402, and report the speed measuring node 402. The access delays of different terminals are used as access delays of the service nodes 401 corresponding to the speed measurement nodes 402 by different terminals.

Of course, there may be a case where the terminal calculates the access delay of the terminal and the speed measuring node. In this case, the data server 421 may also be connected to the terminal through the network, so as to obtain the access of the terminal to the different speed measuring nodes 402. The delay is used, and the access delay of the terminal accessing the different speed measuring nodes 402 is used as the access delay of the different service nodes 401 corresponding to the different speed measuring nodes 402.

It can be understood that, in the embodiment of the present application, the terminal may be a mobile terminal, a tablet computer, or the like, based on a mobile Internet access service system; the terminal may also be a desktop computer or the like based on a wired network (commonly known as a fixed network) access service system. Terminal, referred to as wired network terminal.

Optionally, considering the different network environments, the access delay of the terminal access service node may also be different. If the terminal configuration in the different network environments adopts the same domain name resolution configuration relationship, the mobile terminal and the cable may not be considered. The access experience of the network terminal. Therefore, in the embodiment of the present application, the mobile terminal having each network attribute and the access delay of the wired network terminal accessing different service nodes may be separately tested, and the mobile terminal is determined to be suitable for mobile mobile having each network attribute. The service node, and for the wired network terminal, determine the service node to which the wired network terminal of each network attribute is suitable to access.

For ease of understanding, the following describes the scheduling control method of the present application for terminals in two different types of network environments, namely, a mobile terminal and a wired network terminal.

Referring to FIG. 4, FIG. 5 is a schematic flowchart diagram of an embodiment of a scheduling control method in the present application. The method in this embodiment may include:

S501. After initiating an access request to the serving node in the serving system, the mobile terminal determines an IP address of the at least one speed measuring node to be tested.

In a possible case, determining the IP address of the at least one speed measuring node may be: after the serving node receives the access request of the mobile terminal, the serving node feeds back to the mobile terminal one or more speed measuring nodes of the required test IP address. It can be understood that when the terminal is a mobile terminal, the network protocol used by the mobile terminal to access the service node is different from the network protocol used by the wired network terminal. Therefore, the service node can identify according to the network protocol adopted by the terminal. The terminal is a mobile terminal, and further instructs the mobile terminal to access at least one speed measuring node to be tested.

In another possible case, determining the IP address of the at least one speed measuring node may be: presetting a plurality of IP addresses of the speed measuring nodes required to be tested in a client of the service system installed by the mobile terminal, such that When the terminal detects that an access request is initiated to the service system, the IP address of the preset at least one speed measuring node may be acquired.

It can be understood that, in order to enable a plurality of mobile terminals belonging to the same LDNS to separately access the speed measuring nodes associated with different service nodes, each mobile terminal may use all the speed measuring nodes as the speed measuring nodes to be tested; In order to reduce the data processing capacity of the mobile terminal, the speed measurement nodes to be tested corresponding to different mobile terminals may be different. For example, for the mobile terminal A and the mobile terminal B belonging to the same LDNS, the speed measuring nodes to be tested of the mobile terminal A are the speed measuring node A, the speed measuring node B and the speed measuring node C, and the speed measuring node of the mobile terminal B to be tested may It is the speed measuring node A and the speed measuring node D.

It should be noted that the condition that the mobile terminal triggers the access delay of the test accessing the different speed measurement nodes is not limited to the mobile terminal initiating an access request to the service system. In actual applications, other trigger conditions may also be triggered to trigger the mobile terminal to determine the speed measurement node. The IP address, for example, the mobile terminal can also periodically determine the IP address of the speed measurement node to be tested according to a preset test period.

S502. The mobile terminal sends the speed measurement data packet to the speed measurement node according to the IP address of the speed measurement node.

S503. After receiving the speed measurement data packet, the speed measurement node returns a response data packet for the speed measurement data packet to the mobile terminal.

S504: The mobile terminal determines, according to the sending time of the speed measuring data packet to the speed measuring node, and the receiving time of the response data packet returned by the speed measuring node, the access delay of the mobile terminal to access the speed measuring node.

For example, the access delay may be half of the time difference between the reception time and the transmission time.

S505. The mobile terminal sends the IP address of the mobile terminal, the identifier of the speed measuring node, and the access delay to the data server.

For example, the mobile terminal sends an access delay to the data server, and may carry the IP address of the mobile terminal and the identifier of the speed measuring node, and the mobile terminal may identify the mobile terminal that sends the access delay by using the IP address of the mobile terminal, and pass the The IP address can analyze network attributes such as the operator to which the mobile terminal belongs and the geographic area. Correspondingly, the identifier of the speed measuring node may indicate that the access delay is a network delay that exists when the mobile terminal accesses the speed measuring node.

For example, if the access delay of the mobile terminal A accessing the speed measuring node M is 15 ms, the mobile terminal may delay the sending of the access, carrying the IP address of the mobile terminal A and the identifier of the speed measuring node M.

The identifier of the speed measuring node may be an IP address of the speed measuring node or other identifier capable of uniquely indicating the speed measuring node.

It can be understood that the foregoing steps S501 to S505 are only one implementation manner of obtaining the access delay of the mobile terminal accessing the service node, and the method for obtaining the access delay of the mobile terminal accessing the service node by using other methods in the actual application is also The same applies to the embodiments of the present application.

In addition, the above steps S501 and S505 only describe the process of testing the access delay of the mobile terminal to a speed measuring node from the perspective of the mobile terminal, but it can be understood that the mobile terminal accesses other speed measuring nodes and other mobiles. The process of accessing any one of the speed measurement nodes in the service system is similar to the above process, and will not be described here.

The above steps S501 to S505 can be repeatedly performed to update the access delays of different mobile operators and different mobile nodes in different geographical locations in real time to reflect the network delay of different mobile terminals.

S506. The data server stores the IP address of the mobile terminal, the identifier of the speed measuring node, and the access delay transmitted by the mobile terminal.

Optionally, each access delay corresponds to an IP address of the mobile terminal and an identifier of the speed measuring node. To facilitate data storage and subsequent data transmission, the data server may move the access delay and the access delay. The IP address of the terminal and the identifier of the speed measuring node are stored as an access delay array. Thus, each access delay data includes: an IP address of the mobile terminal, an identifier of the speed measuring node, and an access delay.

It can be understood that, because the access delay data reported by the mobile terminal may be different at different times, the data server may update the stored access delay data at regular intervals.

It should be noted that the above steps S501 to S506 are only for explaining the process of obtaining the access delay of the mobile terminal to the serving node, which is only for preparing the subsequent configuration of the domain name resolution information.

Optionally, in the case that the data server stores the access delay data in the form of an access delay array, the configuration server may obtain multiple access delay arrays, where each access delay array includes: the IP address of the mobile terminal, the speed measurement node Identification and access delay.

S507. The data server determines an operator and a geographic area to which the mobile terminal belongs according to the IP address of the mobile terminal.

For ease of understanding, the embodiment of the present application introduces the network attribute of the mobile terminal to the operator and the geographical area to which the terminal belongs, but when the network attribute includes other attribute information, the process is similar.

S508. The data server combines at least one mobile terminal belonging to the same operator and the geographical area to form a mobile terminal set according to the operator and the geographical area to which the plurality of mobile terminals that report the access delay respectively belong to obtain a plurality of different operators. And a collection of mobile terminals in a geographic area.

It can be seen from the foregoing steps 501 to S505 that the data server can store the access delay data reported by a plurality of different mobile terminals, and the IP addresses of the multiple mobile terminals are different, thereby obtaining a plurality of different network attributes. The access delay of mobile terminals. For each network attribute, the data server can store the access delays of the plurality of mobile terminals having the network attribute for different service nodes, so that multiple terminals having each network attribute can be calculated for the same service. The average access delay of a node needs to first determine the mobile terminal with the same network attribute.

S509. For each mobile terminal set, the data server respectively determines an average access delay of each mobile terminal in the mobile terminal set accessing each speed measuring node in the service system.

For example, the access delays of the mobile terminal A accessing the speed measuring node 1, the speed measuring node 2, and the speed measuring node 3 belonging to the China-Guangzhou-first operator can be expressed as:

China-Guangzhou-first operator to speed node 1, IP address: 1.1.1.1, delay 30ms;

China-Guangzhou-first operator to speed node 2, IP address: 2.2.2.2, delay 100ms;

China-Guangzhou-first operator to speed node 3, IP address: 3.3.3.3, delay 50ms;

Meanwhile, it is assumed that the access delays of the mobile terminal B accessing the speed measuring node 2, the speed measuring node 3, and the speed measuring node 4 belonging to the China-Guangzhou-first operator can be expressed as:

China-Guangzhou-first operator to speed node 2, IP address: 2.2.2.2, delay 70ms;

China-Guangzhou-first operator to speed node 3, IP address: 3.3.3.3, delay 10ms;

China-Guangzhou-first operator to speed node 4, IP address: 4.4.4.4, delay 40ms;

Then, it can be counted that the average access delay of the mobile terminal accessing the speed measurement node 1 under the China-Guangzhou-first operator is 30 ms; and the average access delay of the access speed measurement node 2 is (100 ms+70 ms)/2=85 ms, The average access latency for other speed measuring nodes is similar.

Optionally, before calculating, for a mobile terminal set, an average access time delay of all the mobile terminals in the mobile terminal set to access a certain speed measurement node, the mobile terminal may be removed from the mobile terminal set to access the speed measurement node. The highest value and the lowest value of the plurality of access delays are then used to calculate the average access delay of the terminal in the mobile terminal set to access the speed measuring node by using the remaining multiple access delays.

Further, the network status may be different at different times. After calculating the average access delay, the calculation time of the average access delay may also be recorded, so that the domain name resolution may be configured by using the latest calculated average access delay. List.

It can be understood that the steps S507 to S509 can be performed every preset time, instead of triggering execution every time the mobile terminal reports the access delay data.

It should be noted that steps S507 to S509 are only for convenience of understanding, that the mobile terminals of the same network attribute are grouped into one mobile terminal set, and all mobile terminal pairs in the mobile terminal set formed by the terminal that calculates the network attribute are The average access latency of a service node is described as an example. However, it can be understood that, for a network attribute, there may be other manners for calculating the average access delay of the mobile terminal having the network attribute for a service node in the service system, and details are not described herein again.

Optionally, the wireless network used by the mobile terminal may also be in various forms, for example, a wireless network using the 3rd Generation mobile communication technology (3G), using a fourth generation mobile communication technology ( The 4th Generation mobile communication technology, 4G) wireless network, WiFi network and so on. In the embodiment of the present application, in order to more accurately reflect the access delay of the mobile terminal in different network environments and different service nodes, the mobile terminal may also use the type of the wireless network used by the mobile terminal. The IP address of the mobile terminal, the identifier of the speed measuring node, and the access delay corresponding to the speed measuring node are sent to the data server. Correspondingly, the data server can separately count the average access delay of each mobile node when the mobile terminal having each network attribute uses different wireless networks.

S510. For each mobile terminal, the data server determines, according to the average access delay of the mobile terminal in the mobile terminal set to different speed measuring nodes, and combines the relationship between the different speed measuring nodes and the service node, respectively, to determine the mobility in the mobile terminal set. The average access delay of the terminal to each service node.

Wherein, because different mobile terminal sets represent different network attributes, the average access delay of the mobile terminal in the mobile terminal set to the service node is: the mobile terminal having the network attribute represented by the mobile terminal set to the service node Average access latency.

It can be understood that the association relationship between the speed measuring node and the service node may be stored in the data server, so that after determining the average access delay of the mobile terminal in the mobile terminal set for the speed measuring node, determining the speed node association The service node actually obtains the average access delay of the mobile terminal in the mobile terminal set to the service node.

Optionally, in order to distinguish the average access delay of the terminal accessing different service nodes by different network attributes, the data server may store the correspondence between the network attribute, the identifier of the speed measuring node, and the average access delay, for example, may be stored in the following form:

China-Guangzhou-first operator to speed node 1, IP address: 1.1.1.1, average access delay 40ms;

The above correspondence indicates that the average access delay of the mobile terminal of the first operator in Guangzhou, China, accessing the speed measuring node 1 (IP address: 1.1.1.1) is 40 ms.

It can be understood that, in practical applications, for a mobile terminal having each network attribute, calculating an average access delay of a terminal having a network attribute to different service nodes in the service system may also be performed by a configuration server, that is, a step. S507 to S510 may be completed by the configuration server. In this case, the configuration server only needs to acquire data of the access delay reported by a plurality of different mobile terminals having network attributes from the data server.

S511. The configuration server acquires, from the data server, the average access delay of each mobile node in the service system by the mobile terminal having different network attributes.

For example, the configuration server may obtain multiple sets of correspondences stored by the data server, and each set of correspondences includes: network attributes, service node identifiers, and average access delay correspondences, and each set of correspondences represents a network attribute terminal for one The average access latency of the service node.

S512. For a mobile terminal having each network attribute, the configuration server selects, from among a plurality of service nodes of the service system, a service node that is suitable for access by the mobile terminal having the network attribute.

Wherein, for the target service node that is suitable for the terminal with the target network attribute, the average access delay of the mobile terminal having the target network attribute accessing the target service node satisfies the first preset condition, and the first preset condition may have A variety of possibilities. For example, for a terminal having a target network attribute, the first preset condition may be that an average access delay of a mobile terminal having a target network attribute accessing the target service node is smaller than an average access delay of the mobile terminal accessing another service node. For example, the first preset condition may be that the average access delay is less than the preset value; for example, the first preset condition may be in the order of the average access delay corresponding to the service node from small to large, for multiple After the service node sorts, it sorts any service node that is in the previous specified position.

It can be understood that, when determining the service node that the mobile terminal having the network attribute is suitable to access, in addition to the delay access delay corresponding to the service node, multiple factors such as the load and capacity of the service node can be comprehensively considered. Correspondingly, for the target service node that is suitable for the terminal with the target network attribute, the load or capacity of the target service node needs to meet the second preset condition, the load is less than the preset value, or the capacity is greater than the preset threshold. and many more. For example, for a mobile terminal having a target network attribute, the target service node may be a service node in the service system whose load is less than a preset value, and the mobile terminal has the smallest average access delay.

Optionally, the priority order of the average access delay, load, and capacity may be preset, such as optimal load, optimal capacity, etc., so that the highest priority factor may be selected from multiple service nodes. The at least one service node of the second preset condition selects, from the at least one service node, a target service node whose other factors also satisfy the corresponding preset condition.

S513. For each network attribute, configure an IP address of a service node that is suitable for access by the mobile terminal of the network attribute as an IP address of the service node that matches the network attribute in the first domain name resolution list of the authoritative domain name server.

In order to distinguish the domain name resolution list corresponding to the wired network terminal, the domain name resolution list for the mobile terminal is referred to as a first domain name resolution list, and the subsequent domain name resolution list for the wired network terminal is referred to as a second domain name resolution list.

For the target network attribute, if the IP address of the service node corresponding to the target network attribute in the first domain name resolution list is the IP address of the target service node, the IP address of the corresponding service node may be maintained. Otherwise, the IP address of the service node corresponding to the target network attribute can be updated to the IP address of the target service node.

Because different operators and LDNSs deployed in the geographic area are different, different network attributes can be characterized by the LDNS identifier in the first domain name resolution list. In this case, the mobile network with the target network attribute is actually The IP address of the target service node that the terminal is suitable to access is configured as the IP address of the service node that matches the identifier of the LDNS with the target network attribute in the first domain name resolution list.

It can be understood that, in the embodiment of the present application, the mobile terminal having the same network attribute and the service node to be directed to the wired network terminal may have different differences. Therefore, the authoritative domain name server may be configured differently for the mobile terminal and the wired network terminal respectively. List of domain name resolutions. Certainly, in order to directly distinguish the network type used by the terminal in the domain name resolution list, the identifier information used to identify the network type used by the terminal may be added in each domain name resolution relationship of the domain name resolution list.

Optionally, when the network used by the terminal is different, the domain name used by the terminal to request access to the same service system may be different. For example, the mobile terminal accessing the service system may adopt the first domain name of the service system, and the wired network terminal The service system can be accessed using the second domain name of the service system. Specifically, the network type identifier indicating the network type used by the terminal may be included in the domain name requested by the terminal, and the network type identifier in the first domain name and the second domain name are different. For example, the domain name that the mobile terminal can use to access a certain service system may be mobile.a*b.com, and the domain name used by the wired network terminal to access the service system may be: static.a*b.com, where "mobile" in the domain name "mobile.a*b.com" indicates that the terminal that initiated the domain name resolution request is a mobile terminal that uses the wireless network; and the "static" in the domain name "static.a*b.com" indicates that the domain name resolution request is initiated. The terminal is a wired network terminal using a wired network.

Correspondingly, in the embodiment of the present application, after determining the service node corresponding to each network attribute, the configuration server may configure the identifier of the LDNS with the network attribute and the service system in the domain name resolution list of the authoritative domain name server. The domain name resolution relationship between a domain name and the IP address of the service node.

It can be understood that the embodiment of the present application is an example in which the configuration server configures the domain name resolution list in the authoritative domain name server as an example, but it can be understood that the configuration server determines that the mobile terminal having different network attributes is suitable for parsing. After the service node, the service node that is suitable for the terminal having the network attribute is only used as the service node corresponding to the network attribute in the domain name resolution list, and the matching relationship between the service node and the network attribute that the terminal having the network attribute is suitable for is stored, and subsequently The configuration relationship update request may be initiated by the authoritative domain name server, or the configuration server may send the matching relationship to the authoritative domain name server, so that the authoritative domain name server completes the configuration of the domain name resolution list according to the matching relationship.

It can be seen that, in this embodiment, for the operator and the geographic area represented by the same network attribute, the average access delay of each service node in the service system is accessed by the mobile terminal having the network attribute, thereby facilitating the service system from the service system. Among the plurality of service nodes, the service node having the average access delay of the mobile terminal having the network attribute is selected, so that the IP address of the service node corresponding to the LDNS having the network attribute in the domain name resolution list is determined to have After the IP address of the service node that the terminal of the network attribute is suitable for access, when the subsequent mobile terminal accesses the service system through the LDNS, the mobile terminal can be directed to the service node that the terminal having the network attribute is suitable for access, which is beneficial to reducing the access of the mobile terminal. The access delay of the service system improves the access speed of the mobile terminal access service system.

Referring to FIG. 4, FIG. 6 is a schematic flowchart of a scheduling control method of the present application in a case where the terminal is a wired network terminal, and the method in this embodiment may include:

S601. The wired network terminal sends an access request to a service node in the service system.

S602. After receiving the access request, the serving node tracks the target gateway to which the wired network terminal belongs by using a reverse route.

The reverse route traceroute technology can track the gateway through which the access request passes, and the gateway through which the access request passes is the target gateway to which the wired network terminal belongs.

S603. The serving node transmits the IP address of the target gateway to which the wired network terminal belongs to the speed measuring node associated with the serving node.

S604. The speed measurement node sends the speed measurement data packet to the target gateway according to the IP address of the target gateway to which the wired network terminal belongs.

S605. The target gateway returns a response data packet for the speed measurement data packet to the speed measurement node in response to the received speed measurement data packet.

S606. The speed measurement node calculates an access delay of the target gateway to the speed measurement node according to a sending time of the speed data packet and a receiving time of receiving the response data packet.

The access delay of the target gateway to the speed measuring node can be regarded as the access delay of the mobile terminal belonging to the target gateway to access the speed measuring node.

Of course, steps S602 to S606 are one way of testing the access delay of the gateway to the speed measuring node, but the manner of testing the access delay of the gateway to the speed measuring node is also applicable to the embodiment. In addition, the embodiment of the present application introduces the access delay of the gateway to the speed measuring node as an access delay of the wired network terminal to the speed measuring node, but it can be understood that the wired network terminal is tested to the speed measuring node by other means. The manner of access delay is also applicable to the embodiments of the present application.

S607. The speed measurement node sends the IP address of the target gateway, the identifier of the service node, and the access delay to the data server.

S608. The data server stores the IP address of the target gateway, the identifier of the speed measuring node, and the access delay.

It can be understood that, in order to distinguish the access delay data of the mobile terminal and the wired network terminal, different data servers may be separately set for the mobile terminal and the wired network terminal respectively. For example, the first data server may store the access reported by the mobile terminal. Relevant data such as delay; the second data server can obtain related data such as the access delay of the wired network terminal reported by the speed measuring node.

When a data server is used to store the access delay data related to the wired network terminal and the mobile terminal, the data server can distinguish the access delay corresponding to the access delay according to the device that reports the access delay, such as After receiving the access delay sent by the speed measurement node, the data server may determine that the access delay is an access delay of the target gateway to the speed measurement node to which the wired network terminal belongs. Of course, in order to be able to more clearly determine the access delay for the access delay of the terminal with which network attribute, the speed measurement node and the mobile terminal can also report the access delay, and carry the network representing the terminal corresponding to the access delay. The identifier of the attribute, for example, the delay when the mobile terminal reports the access, may carry the identifier 1 indicating that the access delay is the access delay of the mobile terminal to the speed measuring node or the serving node; and the speed measuring node reports the access of the target gateway to the serving node. The time delay may carry an identifier 2 that may indicate that the access delay is a access delay of the wired network terminal to the serving node. Correspondingly, after receiving the access delay corresponding to different terminals, the data server may uniformly store all access delays in one data table, or may store the corresponding access of the mobile terminal and the wired network terminal through two data tables respectively. Delay data.

S609. The data server determines, according to the IP address of the target gateway, the operator and the geographic area to which the target gateway belongs.

For ease of understanding, the embodiment of the present application introduces the network attribute of the target gateway to the operator and the geographical area to which the target gateway belongs, but when the network attribute includes other attribute information, the process is similar.

S610: The data server forms a set of gateways belonging to the same operator and at least one wired network terminal of the geographic area, and obtains a plurality of gateway sets that represent different operators and geographic regions.

S611. For each gateway set, the data server determines an average access delay of each target gateway in the gateway set to each speed measuring node in the service system.

Steps S609 to S611 are similar to the processes of steps S507 to S509 in the embodiment of FIG. 5. Therefore, the average access delay of all target gateways to the speed measuring nodes in each gateway set can be obtained by referring to the foregoing calculation of all terminal pairs in the mobile terminal set. The process of the average access delay of the speed measuring node will not be described here.

S612. For each gateway set, the data server determines the target access gateway in the gateway set to different service nodes according to the average access delay of the target gateway to the different speed measuring nodes in the gateway set, and the association relationship between the different speed measuring nodes and the serving node. Average access latency.

Wherein, because different gateway sets represent different network attributes, the average access delay of the target gateway to the service node in the gateway set is: the average of the wired network terminal having the network attribute represented by the set of gateways to the service node Access delay.

It can be understood that the data server can store the association relationship between the speed measurement node and the service node, so that after determining the average access delay of the target gateway in the gateway set for the speed measurement node, the gateway is actually obtained. The average access latency of the target node in the set to the service node associated with the speed node.

S613. The configuration server acquires, from the data server, a wired network terminal having different network attributes to respectively access an average access delay of each service node in the service system.

S614. For a wired network terminal of each network attribute, the configuration server selects, from among a plurality of service nodes of the service system, a service node that is suitable for access by the wired network terminal having the network attribute.

The average access delay of the target service node that is suitable for the network network terminal of each network attribute meets the first preset condition. The first preset condition may be similar to the previous embodiment, and details are not described herein again.

Correspondingly, when determining the service node that the wired network terminal with the network attribute is suitable for access, in addition to the delay access delay corresponding to the service node, multiple factors such as the load and capacity of the service node can be comprehensively considered. Correspondingly, for the target service node that is suitable for the terminal with the target network attribute, the load or capacity of the target service node needs to meet the second preset condition, the load is less than the preset value, or the capacity is greater than the preset threshold. and many more. For the second preset condition, refer to the related description of the previous embodiment, and details are not described herein again.

S615. For each network attribute, configure an IP address of a service node that is suitable for access by the wired network terminal of the network attribute as an IP address of the service node that matches the network attribute in the second domain name resolution list of the authoritative domain name server.

For example, for the target network attribute, after determining the target service node that the wired network terminal having the target network attribute is suitable to access, the identifier and the service system of the LDNS having the target network attribute may be configured in the domain name resolution list of the authoritative domain name server. The domain name resolution relationship between the second domain name and the IP address of the target service node.

Certainly, the specific operation process of step S615 can be similar to the process of step S513 in the foregoing embodiment of FIG. 5, and details are not described herein again.

In this embodiment, the IP address of the service node corresponding to the LDNS in the domain name resolution list may be configured as an IP address of a service node that is suitable for access by the wired network terminal of the LDNS, and the wired network terminal belonging to the LDNS is suitable. The accessed service node is a service node whose average access delay is delayed by the wired network terminal belonging to the LDNS, so that the wired network terminal is directed to the service node suitable for access by the wired network terminal belonging to the LDNS according to the domain name resolution list. It is beneficial to reduce the access delay of the wired network terminal access service system and improve the access speed of the wired network terminal access service system.

It should be noted that, in order to facilitate the description of determining the access delay of the mobile terminal and the wired network terminal to the service node, the scheduling control process of the present application is introduced for the case of the mobile terminal and the wired network terminal respectively by using the embodiments of FIG. 5 and FIG. 6 respectively. However, it can be understood that the average access delay data acquired by the configuration server may include: an average access delay of the mobile terminal with different network nodes for each network attribute, and a wired network terminal pair with each network attribute. The average access delay of different service nodes, the configuration server only needs to allocate the configuration relationship of determining the domain name resolution list to the mobile terminal and the wired network terminal respectively.

In order to facilitate the understanding of the beneficial effects of the embodiments of the present application, the process of requesting domain name resolution by the terminal after the domain name resolution list in the authoritative domain name server is configured by the method in the embodiment of the present application is described below.

FIG. 7 is a schematic flowchart diagram of an embodiment of a domain name resolution method according to the present application. The method in this embodiment may include:

S701. The mobile terminal sends a domain name resolution request to the LDNS to which the mobile terminal belongs, where the domain name resolution request carries the first domain name of the service system.

The first domain name includes a first network type identifier indicating that the network type used by the terminal is a wireless network, and can be used as a target network attribute. For example, in FIG. 7, the first domain name is "mobile.a*b.com" as an example.

In addition, in FIG. 7, the LDNS is the LDNS of China-Guangzhou-operator 1 as an example.

S702. The LDNS determines an authoritative domain name server for parsing the first domain name, and forwards the first domain name to the authoritative domain name server.

For the process of determining the authoritative domain name server for the first domain name, refer to the process shown in FIG. 1 above, and details are not described herein again.

S703. The authoritative domain name server queries, from the first domain name resolution list, an IP address of the first target service node that matches the first domain name and the identifier of the LDNS.

The first domain name resolution table stores a correspondence between the first domain name requested by the mobile terminal, the identifier of the LDNS, and the IP address of the first target service node.

As shown in FIG. 7 , the first domain name is “mobile.a*b.com”. For the first domain name, the first domain name resolution table of the authoritative server stores the following domain name resolution relationship:

Mobile.a*b.com, China-Guangzhou-operator 2, IDC1: 1.1.1.1;

Mobile.a*b.com, China-Xi'an - Carrier 1, IDC 2: 2.2.2.2;

Mobile.a*b.com, China-Guangzhou-operator 1, IDC3: 3.3.3.3.

The IDC indicates the service node. According to the first domain name and the identifier corresponding to the LDNS, that is, China-Guangzhou-operator 1, the resolved IP address can be determined as the IP address of the service node IDC3: 3.3.3.3.

S704. The authoritative domain name server sends the IP address of the first target service node to the mobile terminal via the LDNS server.

S705: The wired network terminal sends a domain name resolution request to the LDNS to which the wired network terminal belongs, where the domain name resolution request carries the second domain name of the service system.

The second domain name includes a second network type identifier indicating that the network type adopted by the terminal is a wired network. For example, in FIG. 7, the second domain name is "static.a*b.com" as an example.

In addition, in FIG. 7, the LDNS to which the wired network terminal belongs is also the LDNS of China-Guangzhou-operator 1 as an example.

S706. The LDNS determines an authoritative domain name server for parsing the second domain name, and forwards the second domain name to the authoritative domain name server.

S707. The authoritative domain name server queries, from the second domain name resolution list, an IP address of the second target service node that matches the second domain name and the identifier of the LDNS.

The second domain name resolution table stores a correspondence between the second domain name requested by the wired network terminal, the identifier of the LDNS, and the IP address of the second target service node.

As shown in FIG. 7, the second domain name is assumed to be "static.a*b.com". For the second domain name, the second domain name resolution table of the authoritative server stores the following domain name resolution relationship:

Static.a*b.com, China-Guangzhou-operator 3, IDC2: 2.2.2.2;

Static.a*b.com, China-Xi'an - Carrier 1, IDC4: 4.4.4.4;

Static.a*b.com, China-Guangzhou-operator 1, IDC1: 1.1.1.1.

According to the second domain name and the identifier corresponding to the LDNS, that is, China-Guangzhou-operator 1, it can be determined that the parsed IP address is the IP address of the service node IDC1: 1.1.1.1, visible, although the wired network terminal and the mobile terminal The LDNSs that belong to the same are the same, but when the networks used by the terminals are different, the service nodes with the least access delay of the terminal will be different due to the difference in network status, so that the IP addresses returned by the authoritative domain name servers are different. The terminals of different networks can access the service nodes with relatively small delay.

S708. The authoritative domain name server sends the IP address of the second target service node to the wired network terminal via the LDNS server.

On the other hand, the embodiment of the present application further provides a scheduling control apparatus. FIG. 8 is a schematic structural diagram of an embodiment of a scheduling control apparatus according to the present application. The apparatus of this embodiment may include:

The average time delay obtaining unit 801 is configured to respectively obtain an average access delay of each service node in the terminal access service system having different network attributes, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

The service node matching unit 802 is configured to: for a terminal having each network attribute, select, from among a plurality of service nodes of the service system, a service node that is suitable for access by a terminal having a network attribute, where The target service node to which the terminal is suitable to access, the average access delay of the terminal having the target network attribute accessing the target service node satisfies the first preset condition;

The matching relationship determining unit 803 is configured to, for each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access, as the IP address of the service node in the domain name resolution list that matches the network attribute.

Optionally, for a target service node that is suitable for access by a terminal having a target network attribute, a terminal having the target network attribute has a minimum average access delay for accessing the target service node.

Optionally, for a target service node that is suitable for access by a terminal having a target network attribute, the load or capacity of the target service node satisfies a second preset condition.

In an implementation manner, the matching relationship determining unit includes:

In still another implementation, the matching relationship determining unit includes:

Optionally, the device further includes:

Optionally, the average delay acquisition unit is specifically configured to:

Optionally, the average delay acquisition unit includes:

In a possible implementation, the average delay acquisition unit includes:

The service node matching unit includes:

The matching relationship determining unit includes:

In a further possible implementation, the average delay acquisition unit includes:

The service node matching unit includes:

The matching relationship determining unit includes:

On the other hand, the embodiment of the present application further provides a configuration server, which may include a scheduling control device as described above.

9 is a block diagram showing the hardware structure of the server. Referring to FIG. 9, the server 900 may include: a processor 901, a communication interface 902, a memory 903, and a communication bus 904;

The processor 901, the communication interface 902, and the memory 903 complete communication with each other through the communication bus 904.

Optionally, the communication interface 902 can be an interface of the communication module, such as an interface of the GSM module;

a processor 901, configured to execute a program;

a memory 903, configured to store a program;

The program can include program code, the program code including computer operating instructions.

The processor 901 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

The memory 903 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.

Among them, the program can be specifically used to:

Acquiring an average access delay of each service node in the terminal access service system with different network attributes, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

For a terminal having each network attribute, a service node suitable for access by a terminal having a network attribute is selected from a plurality of service nodes of the service system, wherein a target service node suitable for access by a terminal having a target network attribute is selected. The average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition;

Based on the foregoing embodiment, the embodiment provides a storage medium for storing program code, and the program code is used to execute the scheduling control method according to any one of the foregoing embodiments corresponding to FIG. 3-7.

Based on the foregoing embodiments, the present embodiment provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the scheduling control methods of the embodiments corresponding to the foregoing Figures 3-7.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of both, in order to clearly illustrate the hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not intended to be limited to the embodiments shown herein.

Claims

A scheduling control method, comprising:

The average access delay of each service node in the terminal access service system with different network attributes is obtained, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

For a terminal having each network attribute, a service node suitable for access by a terminal having a network attribute is selected from a plurality of service nodes of the service system, wherein a target service suitable for access by a terminal having a target network attribute is selected. a node, the average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition;

For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute.
The scheduling control method according to claim 1, wherein for a target service node that is suitable for access by a terminal having a target network attribute, an average access time of the terminal having the target network attribute is suitable for accessing the target service node Delay to meet the first preset conditions, including:

The terminal having the target network attribute has the smallest average access delay for accessing the target service node.
The scheduling control method according to claim 1 or 2, wherein the load or capacity of the target service node satisfies a second preset condition for a target service node that is suitable for access by a terminal having a target network attribute.
The scheduling control method according to claim 1, wherein the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node matching the network attribute in the domain name resolution list. include:

Sending, by the authoritative domain name server, the IP address of the service node corresponding to the local domain name server having the network attribute in the domain name resolution list stored by the authoritative domain name server. The IP address of the service node that is configured to be accessible to the terminal with network attributes.
The scheduling control method according to claim 1, wherein the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node matching the network attribute in the domain name resolution list. ,include:

Configuring a domain name resolution list stored in the authoritative domain name server according to the IP address of the target service node that the terminal having the network attribute is suitable for accessing, in the domain name resolution list, the service node corresponding to the local domain name server having the network attribute The IP address is configured as the IP address of the service node to which the terminal having the network attribute is suitable to access.
The scheduling control method according to claim 1, 2, 4 or 5, wherein the obtaining an average access delay of each service node in the terminal access service system having different network attributes comprises:

Acquiring an average access delay of each service node in the terminal access service system having different network attributes from the data server, wherein the data server obtains access delays of different service nodes in the plurality of terminal access service systems, according to the access delay The network attributes of the terminal respectively calculate the average access delay of each terminal accessing each service node with each network attribute.
The scheduling control method according to claim 1, 2, 4 or 5, wherein the obtaining an average access delay of each service node in the terminal access service system having different network attributes comprises:

Acquiring access delays of different service nodes in multiple terminal access service systems, where network attributes of the multiple terminals are different;

Determining, by the network attributes of the multiple terminals, at least one terminal having the same network attribute to form a terminal set, to obtain a plurality of terminal sets that represent different network attributes;

For the terminal set with each network attribute, according to the access delay of each service node in the terminal access service system in the terminal set, the average access delay of the terminal accessing each service node in the terminal set is calculated separately, and the difference is obtained. The endpoint of the network attribute accesses the average access latency of each service node.
The scheduling control method according to claim 1, wherein the obtaining an average access delay of each service node in the terminal access service system having different network attributes, respectively:

Obtaining an average access delay of each service node in the mobile terminal access service system having different network attributes, where the mobile terminal accesses the service node in the service system by using a wireless network;

For the terminal having each network attribute, a service node that is suitable for access by the terminal having the network attribute is selected from the plurality of service nodes of the service system, including:

For a mobile terminal having each network attribute, a service node suitable for access by a mobile terminal having a network attribute is selected from a plurality of service nodes of the service system;

For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute, including:

For each network attribute, the IP address of the service node that the mobile terminal having the network attribute is suitable to access is used as the IP address of the service node in the first domain name resolution list that matches the network attribute, in the first domain name resolution list. The IP address of the service node to which the mobile terminal having different network attributes needs to be scheduled is stored.
The scheduling control method according to claim 1, wherein the obtaining an average access delay of each service node in the terminal access service system having different network attributes, respectively:

Obtaining an average access delay of each service node in a wired network terminal access service system having different network attributes, where the wired network terminal accesses a service node in the service system based on a wired network;

For the terminal having each network attribute, a service node that is suitable for access by the terminal having the network attribute is selected from the plurality of service nodes of the service system, including:

For a wired network terminal having each network attribute, a service node suitable for access by a wired network terminal having a network attribute is selected from a plurality of service nodes of the service system;

For each network attribute, the IP address of the service node that the terminal of the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute, including:

For each network attribute, the IP address of the service node that the wired network terminal of the network attribute is suitable to access is used as the IP address of the service node in the second domain name resolution list that matches the network attribute, and the second domain name resolution list is The IP address of the service node to which the wired network terminal having different network attributes needs to be scheduled is stored.
A scheduling control device, comprising:

An average delay acquisition unit is configured to respectively obtain an average access delay of each service node in the terminal access service system having different network attributes, where the network attribute of the terminal represents the operator and the geographical area to which the terminal belongs;

a service node matching unit, configured to: for a terminal having each network attribute, select, from a plurality of service nodes of the service system, a service node that is suitable for access by a terminal having a network attribute, where, for a target network attribute a target service node that is suitable for access by the terminal, and an average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition;

The matching relationship determining unit is configured to, for each network attribute, an IP address of a service node that is suitable for access by the terminal having the network attribute as an IP address of the service node in the domain name resolution list that matches the network attribute.
The scheduling control apparatus according to claim 10, wherein the average delay acquisition unit comprises:

a first time delay acquisition unit, configured to respectively acquire an average access delay of each service node in the mobile terminal access service system having different network attributes, where the mobile terminal accesses the service node in the service system by using a wireless network;

The service node matching unit includes:

a first node matching unit, configured to: for a mobile terminal having each network attribute, select, from a plurality of service nodes of the service system, a service node that is suitable for access by a mobile terminal having a network attribute;

The matching relationship determining unit includes:

a first relationship determining unit, configured to use, for each network attribute, an IP address of a service node that is suitable for the mobile terminal of the network attribute to access, as an IP address of the service node that matches the network attribute in the first domain name resolution list, The IP address of the service node scheduled to be scheduled by the mobile terminal having different network attributes is stored in the first domain name resolution list.
The scheduling control apparatus according to claim 10, wherein the average delay acquisition unit comprises:

a second time delay acquisition unit, configured to respectively acquire an average access delay of each service node in the wired network terminal access service system having different network attributes, where the wired network terminal accesses the service node in the service system based on the wired network ;

The service node matching unit includes:

a second node matching unit, configured to: for a wired network terminal having each network attribute, select, from among a plurality of service nodes of the service system, a service node that is suitable for access by a wired network terminal having a network attribute;

The matching relationship determining unit includes:

a second relationship determining unit, configured to, for each network attribute, an IP address of a service node that is suitable for access by the wired network terminal of the network attribute, as an IP address of a service node that matches the network attribute in the second domain name resolution list, The second domain name resolution list stores an IP address of a service node that is scheduled to be scheduled by a wired network terminal having different network attributes.
A dispatch control system, comprising:

Data server and configuration server;

The data server is configured to acquire access delays of different service nodes in multiple terminal access service systems; and calculate, for each terminal having each network attribute, each service node in all terminal access service systems having network attributes Average access delay, where the network attribute of the terminal characterizes the operator to which the terminal belongs and the geographic area;

The configuration server is configured to select a terminal having each network attribute from multiple service nodes of the service system according to an average access delay of each service node in the terminal access service system having different network attributes. a service node that is suitable for access, wherein, for a target service node that is suitable for access by a terminal having a target network attribute, an average access delay of the terminal having the target network attribute accessing the target service node satisfies a first preset condition; For each network attribute, the IP address of the service node that the terminal having the network attribute is suitable to access is used as the IP address of the service node in the domain name resolution list that matches the network attribute.
The scheduling control system according to claim 13, wherein the data server obtains a delay in accessing different service nodes in the plurality of terminal access service systems, and is specifically configured to acquire a plurality of mobile terminal access service systems. Access delays of different service nodes, and access delays of different service nodes in a plurality of wired network terminals accessing the service system;

The data server calculates the average access time delay of each service node in the terminal access service system with network attributes for the terminal having each network attribute, specifically for:

Calculating, for a mobile terminal having each network attribute, an average access delay of each service node in the service system having all the network attributes, the mobile terminal accessing the service node in the service system by using a wireless network;

Calculating, for a wired network terminal having each network attribute, an average access delay of each of the service nodes having access to the service system in all of the line network terminals having the network attribute, the wired network terminal accessing the service in the service system based on the wired network node;

The configuration server selects, according to the average access delay of each service node in the terminal access service system having different network attributes, from the plurality of service nodes of the service system, the terminal having each network attribute is suitable. When accessing a service node, it is specifically used to:

Selecting, from the plurality of service nodes of the service system, a service node that is suitable for access by the mobile terminal having each network attribute; or selecting a service node that is suitable for access by the wired network terminal having each network attribute.
The scheduling control system according to claim 14, wherein the scheduling control system further comprises: a plurality of speed measuring nodes deployed in different equipment rooms in the service system, wherein each service node of the service system The association has a speed measuring node, and the speed measuring node associated with the service node and the service node are deployed in the same equipment room;

The data server obtains a delay of accessing different service nodes in a plurality of mobile terminal access service systems, and is specifically configured to: obtain access delays of multiple mobile terminals to access different speed measurement nodes;

The data server calculates, for a mobile terminal having each network attribute, an average access time delay of each service node in the service system having all the network attributes, specifically for:

For the mobile terminal with each network attribute, calculate the average access delay of each speed-measuring node in all the mobile terminal access service systems with the network attribute, and determine all the movements with the network attribute according to the association relationship between the speed measuring node and the service node. The average access delay of each service node in the terminal access service system;

The speed measuring node is configured to test an access delay of the target gateway to the speed measuring node according to an IP address of the target gateway returned by the service node associated with the speed measuring node, where the IP address of the target gateway is When the service node associated with the speed measuring node receives the access request of the wired network terminal, the IP address of the gateway to which the wired network terminal belongs is reversely routed, the network attribute of the wired network terminal and the wired network terminal The network attribute of the associated target gateway is the same; the access delay of the target gateway to the speed measuring node is used as the access delay of the wired network terminal to the speed measuring node, and is sent to the data server.
A storage medium for storing program code for performing a scheduling control method according to any one of claims 1-9.
A computer program product comprising instructions which, when run on a computer, cause the computer to perform a scheduling control method according to any of claims 1-9.