CN107071089B

CN107071089B - Scheduling control method, device and system

Info

Publication number: CN107071089B
Application number: CN201710353408.0A
Authority: CN
Inventors: 廖伟健
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-05-18
Filing date: 2017-05-18
Publication date: 2020-09-15
Anticipated expiration: 2037-05-18
Also published as: CN107071089A; WO2018210265A1

Abstract

The application provides a scheduling control method, a device and a system, wherein the method comprises the following steps: respectively obtaining the average access time delay of each service node in a terminal access service system with different network attributes, wherein the network attributes of the terminal represent an operator to which the terminal belongs and a geographical area; and selecting a target service node which is suitable for being accessed by the terminal with the network attribute from a plurality of service nodes of the service system aiming at the terminal with each network attribute, and taking the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute as the IP address of the service node matched with the network attribute in the domain name resolution list. According to the scheme, the service nodes which are required to be accessed by the terminals with different network attributes in the domain name resolution list can be configured more reasonably, so that the access delay of the service nodes in the service system accessed by the terminals can be reduced, and the access speed can be improved.

Description

Scheduling control method, device and system

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

Computers on a network are located by Internet Protocol (IP) addresses, which are difficult to remember, and thus, IP addresses are generally replaced by recording domain names. Accordingly, after receiving a network address input by a user, a terminal needs to send a domain name included in the network address to a domain name server, and the domain name server converts the domain name into an IP address, and then can access a host in a network based on the IP address. The process of converting a domain name into an IP address by a domain name server is commonly called domain name resolution.

In order to meet the service requirement or improve the service processing efficiency, a set of service system generally deploys a plurality of service nodes, so that, in order to direct an access request for accessing the service system to different service nodes, a domain name server corresponding to the service system can resolve the domain name of the service system into IP addresses of different service nodes. For example, the domain name server may store the correspondence between different operators and domain names and IP addresses, so that if the operator to which the terminal belongs is different, the IP addresses returned by the domain name server to the terminal are different even if the domain names requested to be resolved by the terminal are the same. However, when the terminal accesses the service system based on the IP address resolved by the domain name server, the access speed may be too slow.

Disclosure of Invention

The application provides a scheduling control method, a device and a system, which are used for improving the access speed of a terminal to a service node in a service system.

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

respectively obtaining the average access time delay of each service node in a terminal access service system with different network attributes, wherein the network attributes of the terminal represent an operator to which the terminal belongs and a geographical area;

for each network attribute terminal, selecting a target service node which is suitable for being accessed by the network attribute terminal from a plurality of service nodes of the service system, wherein the average access time delay which is suitable for being accessed by the network attribute terminal to the target service node meets a first preset condition;

and aiming at each network attribute, taking the IP address of the target service node which is suitable for being accessed by the terminal of the network attribute as the IP address of the service node matched with the network attribute in the domain name resolution list.

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

the system comprises an average time delay obtaining unit, a time delay calculating unit and a time delay calculating unit, wherein the average time delay obtaining unit is used for respectively obtaining the average access time delay of each service node in a terminal access service system with different network attributes, and the network attributes of the terminal represent an operator to which the terminal belongs and a geographical area;

a service node matching unit, configured to select, for each network attribute terminal, a target service node that is suitable for the network attribute terminal to access from multiple service nodes of the service system, where an average access delay of the network attribute terminal to access the target service node meets a first preset condition;

and the matching relation determining unit is used for taking the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute as the IP address of the service node matched with the network attribute in the domain name resolution list aiming at each network attribute.

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

a data server and a configuration server;

the data server is used for acquiring access time delays of different service nodes in a plurality of terminal access service systems; respectively calculating the average access time delay of each service node in all terminal access service systems with the network attribute aiming at the terminal with the network attribute, wherein the network attribute of the terminal represents an operator to which the terminal belongs and a geographical region;

the configuration server is used for selecting a target service node which is suitable for being accessed by a terminal with different network attributes from a plurality of service nodes of the service system according to the average access time delay of each service node in the service system accessed by the terminal with different network attributes, wherein the average access time delay which is suitable for being accessed by the terminal with the network attributes to the target service node meets a first preset condition; and aiming at each network attribute, taking the IP address of the target service node which is suitable for being accessed by the terminal of the network attribute as the IP address of the service node matched with the network attribute in the domain name resolution list.

As can be seen from the above, in the embodiment of the present application, the average access time delay of the terminal with different network attributes (the operator to which the terminal belongs and the geographic area) to different service nodes in the service system is respectively obtained, and for each terminal with network attributes, according to the average access time delay of the terminal with network attributes to different service nodes, it is beneficial to select a target service node better suitable for the terminal with network attributes to access from the service system, so that the access time delay of the terminal with network attributes to access the target service node is relatively small, so that after determining the IP address of the target service node corresponding to the network attributes as the IP address of the service node corresponding to the network attributes in the domain name resolution list, when the terminal with subsequent network attributes accesses the service system, the domain name server can schedule the terminal with network attributes to the target service node with smaller access time delay according to the domain name resolution list, therefore, the access delay of the terminal to access the service system is reduced, and the access speed of the terminal to access the service system is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.

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

FIG. 2 is a diagram illustrating domain name resolution based on domain name resolution relationships;

fig. 3 is a schematic diagram illustrating a possible structure of a domain name configuration system to which the method for configuring domain name resolution of the present application is applied;

fig. 4 is a schematic diagram illustrating a composition structure of an application scenario to which the method for configuring domain name resolution of the present application is applied;

FIG. 5 is a flow diagram illustrating one embodiment of a method for configuring domain name resolution of the present application;

FIG. 6 is a flow chart illustrating a method of configuring domain name resolution according to yet another embodiment of the present application;

FIG. 7 is a schematic diagram illustrating a flow chart of domain name resolution performed by the domain name resolution system after the domain name resolution list is configured by the method for configuring domain name resolution according to the present application;

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

fig. 9 is a schematic diagram illustrating a configuration server according to an embodiment of the present application.

Detailed Description

For the convenience of understanding the scheme of the present application, a description is first given to a domain name resolution scenario. Referring to fig. 1, a schematic diagram of a domain name resolution scenario is shown.

In the scenario of fig. 1, the terminal at least includes 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. The LDNS of different operators are different, and different LDNS may be deployed even in different location ranges by the same operator, so that when the operator to which the terminal belongs and the location range in which the terminal is located are different, the LDNS corresponding to the terminal is also different.

Fig. 1 shows a manner of performing domain name resolution by stepwise recursion, and the LDNS may also be referred to as a recursive domain name resolution server in the scenario of fig. 1.

As shown in fig. 1, in step 101, a domain name resolution request sent by a terminal to a local domain name server of an operator carries a domain name "www.xxx.com.

In step 102, the LDNS may initiate 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 name 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 general top level domain name server to be accessed to resolve the general top level domain name "com." in the domain name, the root domain name server instructs the LDNS to access the general top level domain name server.

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

In step 105, the generic top level domain name server returns the address of the third level domain name server for the LDNS to resolve the domain name "www.xxx.com.

Since the general top-level domain name server cannot resolve the IP address corresponding to the "www.xxx.com." either, the general top-level domain name server may determine the third-level domain name server to be accessed to resolve the "www.xxx.com." and therefore, the general top-level domain name 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 tertiary 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.

As can be seen from the above, the LDNS needs to start a first-level recursion from the root domain name server, and finally find the third-level domain name server, and the third-level domain name server resolves the domain name into an IP address. It should be understood that fig. 1 is only described by way of example of a domain name resolution system including three levels of recursion, in which case the bottom level domain name server is the third level domain name server, but in practical applications the LDNS may go through more levels of recursion to finally locate the bottom level domain name server and resolve the domain name into an IP address by the bottom level domain name server.

The bottom-level dns is also referred to as an authoritative dns, and a corresponding relationship between a domain name and an IP address, such as a domain name resolution list, is configured in the authoritative dns. Therefore, as long as the LDNS locates the authoritative domain name server, the operation of resolving the domain name into the IP address can be completed through the authoritative domain name server.

Of course, fig. 1 is only one domain name resolution process described for understanding the domain name resolution process, and in practical applications, the domain name resolution process may also have other possibilities, which is not limited in this application.

The inventor of the present application finds, through research on a domain name resolution process: because the LDNS corresponding to the terminal can represent the operator to which the terminal belongs and the geographical area in which the terminal is located, currently, the identity of the LDNS, and the correspondence between the domain name and the IP address are generally configured in the authoritative domain name server. At present, under the condition that a domain name of a service system corresponds to IP addresses of a plurality of service nodes, a near access principle is generally adopted according to an operator and a geographical area to which an LDNS belongs and positions to which the plurality of service nodes in the service system belong, an IP address of a service node closer to the LDNS is selected from the plurality of IP addresses, and a corresponding relationship between the selected IP address and the LDNS and the domain name is established.

For example, referring to fig. 2, taking two different LDNS as an example, assume that one LDNS is an LDNS of a telecommunications carrier in guangzhou and one LDNS is an LDNS of a unicom carrier in shanghai, and meanwhile, assume that in the service system, the IP address of the service node closest to the LDNS of the telecommunications carrier in guangzhou is: 15.13, and the IP address of the service node closest to the LDNS in shanghai with the unicom operator is: 119.147, the authoritative domain name server may store the following two correspondences:

domain name: com, guangzhou-telecom operator, IP address: 119. x.15.13;

domain name: com, shanghai-unicom operator, IP address: 123.***.119.147.

Accordingly, as can be seen from fig. 2, when the terminal of the cantonese-telecom operator and the terminal of the shanghai-unicom operator both initiate a resolution request of www.a × b.com, the authoritative domain name server returns different IP addresses according to the above correspondence.

However, the above correspondence relationship is established for the authoritative dns according to the near access principle, but the access delay (or network delay) of the terminal accessing different service nodes is not considered. The access delay can be considered as the time required for the message sent from the terminal to reach the service node. Although the location of the service node is closer to the location of the LDNS corresponding to the terminal, the access delay of the terminal accessing the service node may be larger, which may result in a slow access speed of the terminal accessing the service system, and affect the access experience of accessing the service system.

In order to solve the above problem, an embodiment of the present application provides a scheduling control method, in this scheme, it is required to count an average access delay of each service node in a terminal access service system of each network attribute for terminals with different network attributes (for example, information representing an operator to which a terminal or a device belongs, a geographic area, and the like); and respectively aiming at the average access time delay of each network attribute terminal to different service nodes of the service system, selecting a target service node which is suitable for the terminal with the network attribute to access from the service system, and taking the IP address of the target service node which is suitable for the terminal with the network attribute to access as the IP address of the service node matched with the network attribute in the domain name resolution list. Therefore, when the IP addresses of the service nodes required to be matched with different network attributes in the domain name resolution table are determined, the average access time delay of each service node in the terminal access service system with different network attributes is comprehensively considered, so that the service nodes required to be scheduled by different terminals can be reasonably determined, the access delay of the terminal access service system is favorably reduced, and the access speed of the terminal access service system is improved.

To facilitate understanding of the solution of the present application, a scheduling control system used in a method for configuring domain name resolution information of the present application is first described below, as shown in fig. 3.

As can be seen from fig. 3, the schedule control system may include:

a data server 301 and a configuration server 302;

the data server 301 is configured to obtain access delays of multiple terminals accessing different service nodes in a service system, where network attributes of the multiple terminals are not completely the same; for each network attribute terminal, calculating an average access delay of all the terminals with the network attribute accessing each service node, where the network attribute of the terminal may represent an operator and a geographic area to which the terminal belongs, and of course, the network attribute may also include other network attributes of the terminal, which is not limited herein.

Correspondingly, the configuration server is used for acquiring the average access time delay of each service node in the terminal access service system with different network attributes from the data server; and aiming at each network attribute terminal, selecting a target service node which is suitable for being accessed by the network attribute terminal from a plurality of service nodes of the service system, and taking the IP address of the target service node which is suitable for being accessed by the network attribute terminal as the IP address of the service node matched with the network attribute in the domain name resolution list. And the average access time delay suitable for accessing the target service node by the terminal with each network attribute meets a preset condition. For example, the preset condition may be that the average access delay of the terminal with the network attribute accessing the target service node is smaller than the access delay of other service nodes except the target service node in the terminal access service system with the network attribute.

Optionally, the configuration server 302 may also be configured to configure, according to the target service node matched with different operators and geographic areas, a corresponding relationship between the target service node and the different operators and geographic areas in the domain name resolution list of the authoritative domain name server. It should be understood that the above is described by taking an example that the data server calculates the average access delay of all terminals of each network attribute to the service node in the service system, but in practical applications, the operation of calculating the average access delay may also be performed by the configuration server, and is not limited herein.

Of course, in practical applications, the configuration server and the data server may be separately provided as shown in fig. 3, or may be combined into one server, for example, the configuration server may integrate the function of the data server to obtain the access delay data.

For convenience of understanding, the following description is provided with reference to an application scenario to which a scheduling control method according to an embodiment of the present application is applied. Fig. 4 is a schematic diagram illustrating a composition structure of an application scenario used in the embodiment of the present application.

As can be seen from fig. 4, the application scenario includes: a service system 40, a domain name resolution system 41 and a scheduling control system 42.

Wherein the service system 40 comprises 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 attributes of each LDNS412 are different, and the network attributes of the LDNS may also be the operator to which the LDNS belongs and the geographic area. For example, the plurality of LDNS may include at least: a first LDNS deployed within a first geographic area and belonging to a first operator; a second LDNS deployed in a second geographic region and belonging to the first operator; a third LDNS deployed within the first geographic area and owned by the second operator; and a fourth LDNS deployed in the second geographic area and belonging to the second operator, wherein the first geographic area is different from the second geographic area, and the first operator is different from the second operator.

A domain name resolution list is stored in the authoritative domain name server 411, and includes: and the corresponding relation between the domain name and the network attribute of the service system and the IP address of the service node in the service system. Considering that the network attributes of different LDNS are different, the domain name resolution list may specifically store a corresponding relationship between the domain name of the service system, the identity of the LDNS, and the IP address of the service node in the service system.

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

The specific functions of the data server and the configuration server may be as described above.

Correspondingly, the configuration server can be connected with the authoritative domain name server through a network, so that the configuration server can send the information of the target service node suitable for the terminal with each network attribute to the authoritative domain name server, or configure the domain name resolution list in the authoritative domain name server.

In this application scenario, the method may further include: a plurality of terminals 43 (only one terminal is shown in fig. 4) belonging to different LDNS, wherein the network attributes of the terminals belonging to different LDNS are different. If the terminal 1 belongs to the LDNS where the operator a is located in the city M, it indicates that the operator of the terminal 1 is the operator a and is the terminal of the user whose operator a is 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 a service node, the service system may instruct the terminal to send a test packet to a different service node; the terminal determines the access time delay of the terminal for accessing the service node according to the time of sending the test data packet and the time of the response data packet of the test data packet returned by the service node; accordingly, the terminal may send the access delays for testing access to different service nodes to the data server.

Optionally, because the service nodes need different processing traffic at different times, to avoid that the service node processes the traffic to affect the test of the access delay and to avoid that the test of the access delay affects the service processing of the service node, in the application scenario of fig. 4, the method further includes: each service node is associated with at least one speed measurement node, and the speed measurement node is located at the same position as the associated service node, and specifically, the speed measurement node associated with the service node and the service node are deployed in the same machine room.

Since the speed measurement node associated with the service node is deployed at the same position (e.g., in the same machine room) as the service node, the access delay of the same terminal accessing the speed measurement node is the same as the access delay of the terminal accessing the service node associated with the speed measurement node.

By testing the access delay of the terminal for accessing the speed measuring node and taking the tested access delay as the access delay of the terminal for accessing the service node associated with the speed measuring node, the network state of the terminal for accessing the service node can be reflected more truly, and the access delay can be closer to the real network delay.

Correspondingly, in the scenario of fig. 4, the data server may be connected to the speed measurement node through a network, so that the data server may obtain access delays of different terminals reported by the speed measurement node, and use the access delays of the different terminals reported by the speed measurement node as access delays of the different terminals accessing the service node corresponding to the speed measurement node.

Of course, there may be a case where the terminal calculates the access delay between the terminal and the speed measurement node, and in this case, the data server may also be connected to the terminal through a network, so as to obtain the access delay when the terminal accesses different speed measurement nodes, and use the access delay when the terminal accesses different speed measurement nodes as the access delay when the terminal accesses different service nodes corresponding to different speed measurement nodes.

It can be understood that, in the embodiment of the present application, the terminal may be a mobile terminal based on a mobile internet access service system, such as a mobile phone and a tablet computer; the terminal can also be a terminal of a desktop computer and the like accessing a service system based on a wired network (commonly called fixed network), which is called a wired network terminal for short.

Optionally, in consideration of differences in access delay of the terminal accessing the service node under different network environments, if the same domain name resolution configuration relationship is adopted for the terminals under different network environments, access experience of the mobile terminal and the wired network terminal may not be considered at the same time. Therefore, in the embodiment of the present application, the mobile terminal of each network attribute and the access delay of the wired network terminal accessing different service nodes may be respectively tested, and a target service node suitable for being accessed by the mobile terminal of each network attribute and a target service node suitable for being accessed by the wired network terminal of each network attribute may be respectively determined for the mobile terminal and the wired network terminal.

For convenience of understanding, the scheduling control method of the present application is introduced below for terminals in two different types of network environments, namely, a mobile terminal and a wired network terminal.

Referring to fig. 5 in conjunction with fig. 4, which shows a schematic flowchart of an embodiment of a scheduling control method in the present application, the method of the present embodiment may include:

s501, after initiating an access request to a service node in a service system, the mobile terminal determines an IP address of at least one speed measuring node to be tested.

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

In yet another possible case, the determining the IP address of at least one speed measuring node may be: the IP addresses of a plurality of speed measuring nodes needing to be tested are preset in a client side of the service system installed on the mobile terminal, so that when the mobile terminal detects that an access request to the service system is initiated, the preset IP address of at least one speed measuring node can be obtained.

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

It should be noted that the condition for the mobile terminal to trigger and test the access delay for accessing different speed measurement nodes is not limited to that the mobile terminal initiates an access request to the service system, and in practical applications, other trigger conditions may also be used to trigger the mobile terminal to determine the IP address of the speed measurement node, for example, the mobile terminal may 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 a 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;

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

For example, the access delay may be half the time difference between the receive time and the transmit time.

And 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 may send the access delay to the data server, where the access delay may be carried with an IP address of the mobile terminal and an identifier of the velocity measurement node, the mobile terminal that sends the access delay may be identified by the IP address of the mobile terminal, and network attributes such as an operator to which the mobile terminal belongs, a geographic area, and the like may be analyzed by the IP address. Correspondingly, the identifier of the velocity measurement node may indicate that the access delay is the network delay existing when the mobile terminal accesses which velocity measurement node.

For example, if the access delay of the mobile terminal a to access the velocity measurement node M is 15ms, the mobile terminal may send the access delay to carry the IP address of the mobile terminal a and the identifier of the velocity measurement node M.

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

It can be understood that the above steps S501 to S505 are only one implementation manner of obtaining the access delay of the mobile terminal to the service node, and in practical applications, a manner of obtaining the access delay of the mobile terminal to the service node by other manners is also applicable to the embodiment of the present application.

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

The steps S501 to S505 may be repeated continuously, so as to update the access delay situations of different service nodes for multiple mobile terminals in different operators and geographic areas in real time, so as to truly reflect the network delays of different mobile terminals.

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

Optionally, each access delay corresponds to an IP address of a mobile terminal and an identifier of a speed measurement node, and in order to facilitate data storage and subsequent data transmission, the data server may store the access delay and the IP address of the mobile terminal and the identifier of the speed measurement node corresponding to the access delay as an access delay array, so that each access delay data includes: the IP address of the mobile terminal, the identification of the speed measuring node and the access time delay.

It can be understood that, because the access delay data reported by the mobile terminal at different times are different, 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 service node, and only prepare for subsequently configuring the domain name resolution information.

Optionally, in a case that the data server stores the access delay data in an access delay array form, the configuration server may obtain a plurality of access delay arrays, where each access delay array includes: the IP address of the mobile terminal, the identification of the speed measuring node and the access time delay.

S507, the data server determines the operator and the geographical area to which the mobile terminal belongs according to the IP address of the mobile terminal.

For convenience of understanding, the embodiments of the present application take the network attribute of the mobile terminal as an operator to which the terminal belongs and a geographic area as examples, but when the network attribute includes other attribute information, the process is similar.

And S508, the data server forms at least one mobile terminal belonging to the same operator and the same geographic area into a mobile terminal set according to the operator and the geographic area to which the mobile terminals respectively belong, and the mobile terminal sets representing different operators and geographic areas are obtained.

As can be seen from the foregoing processes in step 501 to step 505, the data server may store access delay data reported by a plurality of different mobile terminals, and the IP addresses of the plurality of mobile terminals are different, so as to obtain access delays of the plurality of mobile terminals belonging to a plurality of different network attributes. For each network attribute, the data server may store access latencies of the multiple mobile terminals with the network attribute to different service nodes, and in order to subsequently calculate an average access latency of the multiple terminals with each network attribute to the same service node, it is necessary to determine the mobile terminals with the same network attribute first.

And S509, for each mobile terminal set, the data server respectively determines the average access time delay of each speed measuring node in all mobile terminal access service systems in the mobile terminal set.

For example, the access delay of the mobile terminal a belonging to the first operator in china-guangzhou to access the speed measuring node 1, the speed measuring node 2, and the speed measuring node 3 may be respectively expressed as:

china-guangzhou-first operator to speed measurement node 1, IP address: 1.1.1.1, delay 30 ms;

china-guangzhou-first operator to speed measurement node 2, IP address: 2.2.2.2, delay 100 ms;

china-guangzhou-first operator to speed measurement node 3, IP address: 3.3.3.3, delay 50 ms; meanwhile, it is assumed that access delays of the mobile terminal B belonging to the first operator in china-guangzhou to access the speed measurement node 2, the speed measurement node 3, and the speed measurement node 4 may be respectively expressed as:

china-guangzhou-first operator to speed measurement node 2, IP address: 2.2.2.2, delay 70 ms;

china-guangzhou-first operator to speed measurement node 3, IP address: 3.3.3.3, delay 10 ms;

china-guangzhou-first operator to speed measurement node 4, IP address: 4.4.4.4, delay 40 ms;

then, the average access time delay of the mobile terminal accessing the speed measuring node 1 under the first operator in china-guangzhou can be counted to be 30 ms; and the average access delay of accessing the node 2 is (100ms +70ms)/2 is 85ms, and the average access delay for other nodes is similar.

Optionally, before calculating an average access delay of all mobile terminals in the mobile terminal set accessing a certain speed measuring node for a mobile terminal set, the maximum value and the minimum value of multiple access delays of multiple mobile terminals in the mobile terminal set accessing the speed measuring node may be removed first, and then the average access delay of the terminals in the mobile terminal set accessing the speed measuring node is calculated by using the remaining multiple access delays.

Further, since the network states may also differ at different times, after the average access delay is calculated, the calculation time of the average access delay may also be recorded, so that the domain name resolution list may be configured by using the latest calculated average access delay in the following.

It is understood that the steps S507 to S509 may be executed once every preset time, instead of triggering each time there is the mobile terminal reporting the access delay data.

It should be noted that steps S507 to S509 are only for ease of understanding, and the description is given by taking an example in which mobile terminals with the same network attribute form a mobile terminal set, and an average access delay to a service node is calculated for all mobile terminals in the mobile terminal set formed by terminals with the network attribute. 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 of the network attribute to a service node in the service system, and details are not described herein again.

Alternatively, the wireless network used by the mobile terminal may have various forms, such as a wireless network using the 3rd Generation mobile communication technology (3G), a wireless network using the 4th Generation mobile communication technology (4G), a WiFi network, and so on. In the embodiment of the application, in order to more accurately reflect the access delay conditions of the mobile terminal to different service nodes in different network environments, the mobile terminal may further send the type of the wireless network used by the mobile terminal to the data server together with the IP address of the mobile terminal, the identifier of the speed measurement node, and the access delay corresponding to the speed measurement node. Correspondingly, the data server can respectively count the average access time delay of each service node when the mobile terminal with each network attribute adopts different wireless networks.

And S510, aiming at each mobile terminal, the data server respectively determines the average access delay of the mobile terminal in the mobile terminal set to each service node according to the average access delay of the mobile terminal in the mobile terminal set to different speed measuring nodes and by combining the incidence relation between the different speed measuring nodes and the service nodes.

Since different mobile terminal sets represent different network attributes, the average access delay of the mobile terminals in the mobile terminal set to the service node is as follows: and the average access delay of the mobile terminal with the network attribute represented by the mobile terminal set to the service node.

It can be understood that the data server may store an association relationship between the speed measurement node and the service node, so that after the average access delay of the mobile terminal in the mobile terminal set to the speed measurement node is determined, the service node associated with the speed measurement node is determined, and the average access delay of the mobile terminal in the mobile terminal set to the service node is actually obtained.

Optionally, in order to distinguish average access time delays of terminals with different network attributes accessing different service nodes, the data server may store a correspondence between the network attributes, the identifiers of the speed measurement nodes, and the average access time delays, for example, the following form may be used for storage:

china-guangzhou-first operator to speed measurement node 1, IP address: 1.1.1.1, average access delay 40 ms;

as indicated by the above correspondence, the average access delay of the mobile terminal of the first operator in Guangzhou, China to access the speed measuring node 1(IP address: 1.1.1.1) is 40 ms.

It can be understood that, in practical applications, for each network attribute of the mobile terminal, calculating the average access delay of the terminal with the network attribute to different service nodes in the service system may also be performed by the configuration server, that is, how steps S507 to S510 may be performed by the configuration server, in which case, the configuration server only needs to obtain data of access delays reported by a plurality of different mobile terminals from the data server.

S511, the configuration server obtains the average access time delay of each service node in the service system respectively accessed by the mobile terminals with different network attributes from the data server;

for example, the configuration server may obtain multiple sets of corresponding relationships stored in the data server, where each set of corresponding relationships includes a corresponding relationship between a network attribute, an identifier of a service node, and an average access delay, and each set of corresponding relationships represents an average access delay of a terminal with one network attribute to one service node.

S512, aiming at the mobile terminal with each network attribute, the configuration server selects a target service node which is suitable for being accessed by the mobile terminal with the network attribute from a plurality of service nodes of the service system.

The average access delay suitable for the mobile terminal with each network attribute to access the target service node meets a first preset condition, and the first preset condition can be various. For example, for a terminal with a network attribute, the preset condition may be that an average access delay of the mobile terminal with the network attribute for accessing the target service node is smaller than an average access delay of the mobile terminal for accessing other service nodes; for another example, the preset condition may be that the average access delay is smaller than a preset value; for another example, the preset condition may be that after the plurality of service nodes are sorted according to the sequence from small to large of the average access delay corresponding to the service node, any service node at the front designated position is sorted.

It can be understood that, when determining the target service node, besides the delay access delay corresponding to the service node, multiple factors such as load and capacity of the service node may be considered comprehensively. Correspondingly, the load or the capacity of the target service node may also be set to meet a second preset condition, where the load is smaller than a preset value, or the capacity is larger than a preset threshold, and the like. For example, for a mobile terminal with one network attribute, the target serving node may be a serving node with the smallest average access delay of the mobile terminal among serving nodes with loads smaller than a preset value in the serving system.

Optionally, the priority order of the factors such as the average access delay, the load, and the capacity may be preset, such as the optimal load and the optimal capacity, so that at least one service node with the highest priority satisfying the preset condition may be selected from the multiple service nodes, and then the target service node with other factors also satisfying the corresponding preset condition may be selected from the at least one service node.

S513, for each network attribute, configuring the IP address of the target service node that the mobile terminal with the network attribute is suitable to access as the IP address of the service node matched with the network attribute in the first domain name resolution list of the authoritative domain name server.

In order to distinguish from 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 a network attribute, if the IP address of the service node corresponding to the 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 unchanged; otherwise, the IP address of the service node corresponding to the network attribute may be updated to the IP address of the target service node.

Since the LDNS deployed in different operators and geographic regions are different, different network attributes may be characterized by the identity of the LDNS in the first domain name resolution list, in which case the IP address of the target service node to which the mobile terminal with such network attribute is adapted to access is actually configured as the IP address of the service node in the first domain name resolution list whose identity of the LDNS with such network attribute matches.

It can be understood that, in the embodiment of the present application, service nodes to which the mobile terminal and the wired network terminal having the same attribute need to be directed may differ, and therefore, the authoritative domain name server may configure different domain name resolution lists for the mobile terminal and the wired network terminal, respectively. Of course, in order to directly distinguish the network type adopted by the terminal in the domain name resolution list, identification information for identifying the network type adopted by the terminal may be added in each domain name resolution relationship in the domain name resolution list.

Optionally, when the networks used by the terminals are different, the domain names used by the terminals to request access to the same service system may be different, for example, the mobile terminal may use a first domain name of the service system to access the service system, and the wired network terminal may use a second domain name of the service system to access the service system. Specifically, the domain name requested to be resolved by the terminal may include a network type identifier indicating a network type used by the terminal, and the network type identifier in the first domain name is different from the network type identifier in the second domain name. For example, the domain name that can be used for the mobile terminal to access a certain service system may be mobile.a × b.com, and the domain name that can be used for the wired network terminal to access the service system may be: static.a.b.com, wherein "mobile" in the domain name "mobile.a.b.com" indicates that the terminal initiating the domain name resolution request is a mobile terminal adopting a wireless network; and "static" in the domain name "static.a × b.com" indicates that the terminal that initiated the domain name resolution request is a wired network terminal that employs a wired network.

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

It can be understood that, in the embodiment of the present application, a domain name resolution list in an authoritative domain name server is configured by a configuration server as an example, but it can be understood that, after determining a target service node that a mobile terminal with different network attributes is suitable for resolving, the configuration server only uses the target service node as a service node corresponding to the network attribute in the domain name resolution list, stores a matching relationship between the target service node and the network attribute, and may subsequently initiate a configuration relationship update request at the authoritative domain name server, or the configuration server actively sends the matching relationship to the authoritative domain name server, so that the authoritative domain name server completes configuration of the domain name resolution list according to the matching relationship.

It can be seen that, in this embodiment, for an operator and a geographic area represented by the same network attribute, by obtaining an average access delay of each service node in the mobile terminal having the network attribute accessing the service system, it is beneficial to select a target service node having a relatively small average access delay of the mobile terminal having the network attribute from a plurality of service nodes of the service system, so that after determining an IP address of the service node corresponding to the LDNS having the network attribute in the domain name resolution list as an IP address of the target service node, when a subsequent mobile terminal accesses the service system through the LDNS, the mobile terminal can be directed to the target service node having a relatively small access delay, which is beneficial to reducing an access delay of the mobile terminal accessing the service system, and improving an access speed of the mobile terminal accessing the service system.

Referring to fig. 6 in conjunction with fig. 4, which shows a flowchart of the scheduling control method of the present application in a case where the terminal is a wired network terminal, the method of 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 service node tracks the target gateway to which the wired network terminal belongs through a reverse route.

The gateway through which the access request passes, that is, the target gateway to which the wired network terminal belongs, can be tracked through a reverse routing technology.

S603, the service node transmits the IP address of the target gateway to which the wired network terminal belongs to a speed measuring node associated with the service node;

s604, the speed measuring node sends a speed measuring data packet to a target gateway according to the IP address of the target gateway to which the wired network terminal belongs;

and 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 the access time delay from the target gateway to the speed measurement node according to the sending time of the speed measurement data packet and the receiving time of the response data packet;

the access delay from the target gateway to the velocity measurement node can be regarded as the access delay of the mobile terminal belonging to the target gateway to the velocity measurement node.

Of course, steps S602 to S606 are a way to test the access delay from the gateway to the node, but other ways to test the access delay from the gateway to the node are also applicable to this embodiment. In addition, in the embodiment of the present application, the access delay from the gateway to the speed measurement node is taken as an example of the access delay from the wired network terminal to the speed measurement node, but it can be understood that a mode of testing the access delay from the wired network terminal to the speed measurement node by other modes is also applicable to the embodiment of the present application.

And S607, the speed measuring node sends the IP address of the target gateway, the identification of the service node and the access delay to the data server.

And S608, the data server correspondingly 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 respective 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, for example, the first data server may store relevant data such as access delay reported by the mobile terminal; the second data server can obtain the access delay and other related data of the wired network terminal reported by the speed measuring node.

Under the condition that a data server is adopted to store access delay data related to a wired network terminal and a mobile terminal, the data server can distinguish which kind of access delay corresponds to the access delay according to a device reporting the access delay, and if the data server receives the access delay sent by a speed measuring node, the data server can determine that the access delay is the access delay from a target gateway to the speed measuring node to which the wired network terminal belongs. Certainly, in order to make it more clear which network type terminal the access delay is for, the identifier representing the network type of the terminal corresponding to the access delay may be carried in the access delay reported by the velocity measurement node and the mobile terminal, for example, the identifier 1 representing the access delay as the access delay of the mobile terminal to the velocity measurement node or the service node may be carried in the access delay reported by the mobile terminal; and the speed measuring node reports the access delay of the target gateway to the service node, and can carry an identifier 2 which can indicate that the access delay is the access delay of the wired network terminal to the service node. Correspondingly, after receiving the access delays corresponding to different terminals, the data server may store all the access delays in one data table collectively, or may store the access delay data corresponding to the mobile terminal and the wired network terminal through two data tables, respectively.

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

For convenience of understanding, the embodiments of the present application take the network attribute of the target gateway as an operator to which the target gateway belongs and a geographic area as examples, but when the network attribute includes other attribute information, the process is similar.

S610, the data server combines at least one mobile terminal belonging to the same operator and the same geographic area into a gateway set, and a plurality of gateway sets representing different operators and geographic areas are obtained.

S611, for each gateway set, the data server determines an average access delay from all target gateways in the gateway set to each speed measurement 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, so that obtaining the average access delay of the gateway to the velocity measurement node in each gateway set can refer to the process of calculating the average access delay of all terminals in the mobile terminal set to the velocity measurement node, which is not described herein again.

And S612, aiming at each gateway set, the data server determines the average access delay of the target gateway in the gateway set to different service nodes according to the average access delay of the target gateway in the gateway set to different speed measurement nodes and by combining the incidence relation between the different speed measurement nodes and the service nodes.

Because different gateway sets represent different network attributes, the average access delay of the target gateway in the gateway set to the service node is: and average access delay of the wired network terminal with the network attribute represented by the gateway set to the service node.

It can be understood that the data server may store an association relationship between the speed measurement node and the service node, so that after the average access delay of the target gateway in the gateway set to the speed measurement node is determined, the average access delay of the mobile terminal in the mobile terminal set to the service node associated with the speed measurement node is actually obtained.

S613, the configuration server obtains the average access delay of each service node in the service system respectively accessed by the wired network terminals with different network attributes from the data server.

S614, aiming at the mobile terminal with each network attribute, the configuration server selects a target service node which is suitable for the wired network terminal with the network attribute to access from a plurality of service nodes of the service system.

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

Correspondingly, when the target service node is determined, besides the time delay access time delay corresponding to the service node, a plurality of factors such as load, capacity and the like of the service node can be comprehensively considered. Correspondingly, the load or the capacity of the target service node may also be set to meet a second preset condition, where the load is smaller than a preset value, or the capacity is larger than a preset threshold, and the like. For the second preset condition, reference may also be made to the related description of the foregoing embodiment, which is not described herein again.

S615, aiming at each network attribute, the IP address of the target service node which is suitable for the access of the wired network terminal with the network attribute is configured to be the IP address of the service node matched with the network attribute in the second domain name resolution list of the authoritative domain name server.

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

Of course, the specific operation process of step S615 may be similar to the process of step S513 in the embodiment of fig. 5, and is 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 target service node suitable for the access of the wired network terminal belonging to the LDNS, and the target service node is a service node having a relatively small average access delay to the wired network terminal belonging to the LDNS, so that the wired network terminal is directed to the target service node according to the domain name resolution list, which is beneficial to reducing the access delay of the wired network terminal to access the service system, and improving the access speed of the wired network terminal to access the service system.

It should be noted that, for convenience of description, to determine access delay of a mobile terminal and a wired network terminal to a service node, the scheduling control process of the present application is introduced in the embodiments of fig. 5 and fig. 6 for the situations of the mobile terminal and the wired network terminal, respectively, but it may be understood that average access delay data acquired by a configuration server may include: the configuration server only needs to allocate and determine the configuration relation of the domain name resolution list aiming at the mobile terminal and the wired network terminal respectively.

In order to facilitate understanding of the beneficial effects of the embodiments of the present application, in combination with the above commonalities, a process of requesting domain name resolution by a terminal after configuring a domain name resolution list in an authoritative domain name server by the method of the embodiments of the present application is described below.

As shown in fig. 7, which shows a schematic flow chart of an embodiment of a domain name resolution method according to the present application, the method of the embodiment may include:

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

The first domain name comprises a first network type identifier which indicates that the network type adopted by the terminal is a wireless network. For example, in fig. 7, the first domain name is "mobile.

In fig. 7, the LDNS is described as an example of the LDNS of china-guangzhou-carrier 1.

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

The process of determining the authoritative dns for resolving the first domain name by the LDNS may refer to the flow shown in fig. 1, which is not described herein again.

S703, the authoritative domain name server inquires the IP address of the first target service node matched with the first domain name and the LDNS identifier from the first domain name resolution list;

the first domain name resolution table stores the corresponding relation among the first domain name requested by the mobile terminal, the identification of the LDNS and the IP address of the service node.

As shown in fig. 7, assuming that the first domain name is "mobile.a × b.com", the first domain name resolution table of the authoritative server stores the following domain name resolution relations for the first domain name:

com, china-guangzhou-carrier 2, IDC 1: 1.1.1.1;

com, china-sienna-carrier 1, IDC 2: 2.2.2.2;

com, china-guangzhou-carrier 1, IDC 3: 3.3.3.3.

wherein, IDC represents a service node, and then, according to the first domain name and the identifier corresponding to the LDNS, that is, china-guangzhou-operator 1, the resolved IP address may be determined to be the IP address of the service node IDC 3: 3.3.3.3.

s704, the authoritative dns server sends the IP address of the first target serving node to the mobile terminal through 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 a 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".

In fig. 7, an example will be described in which the LDNS to which the wired network terminal belongs is the same LDNS of china-guangzhou-carrier 1.

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

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

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

As shown in fig. 7, assuming that the second domain name is "static.a × b.com", the second domain name resolution table of the authoritative server stores the following domain name resolution relationship for the second domain name:

static.a × b.com, china-guangzhou-operator 3, IDC 2: 2.2.2.2;

static.a × b.com, china-sienna-carrier 1, IDC 4: 4.4.4.4;

static.a × b.com, china-guangzhou-carrier 1, IDC 1: 1.1.1.1.

according to the second domain name and the identifier corresponding to the LDNS, i.e., china-guangzhou-operator 1, it may be determined that the resolved IP address is the IP address of the service node IDC 1: 1.1.1.1, it can be seen that, although the LDNS to which the wired network terminal and the mobile terminal belong are the same, when the networks used by the terminals are different, the service node with the minimum access delay of the terminal will be different due to the difference in network states, so that the IP addresses returned by the authoritative domain name server for the terminal will be different, and thus the terminals of different networks can access the service node with relatively small delay.

S708, the authoritative dns server sends the IP address of the second target service node to the wired network terminal through the LDNS server.

On the other hand, the embodiment of the application also provides a scheduling control device. Referring to fig. 8, which shows a schematic structural diagram of an embodiment of a scheduling control apparatus according to the present application, the apparatus of the embodiment may include:

an average delay obtaining unit 801, configured to obtain average access delays of each service node in a terminal access service system with different network attributes, respectively, where the network attributes of the terminal represent an operator and a geographic area to which the terminal belongs;

a service node matching unit 802, configured to select, for each network attribute terminal, a target service node that is suitable for the network attribute terminal to access from multiple service nodes of the service system, where an average access delay of the network attribute terminal to access the target service node meets a first preset condition;

a matching relationship determining unit 803, configured to, for each network attribute, use the IP address of the target service node to which the terminal of the network attribute is suitable for accessing as the IP address of the service node matching the network attribute in the domain name resolution list.

Optionally, the average access time delay of the terminal with the network attribute accessing the target service node meets a first preset condition, and includes:

and the average access delay of the terminal with the network attribute for accessing the target service node is minimum.

Optionally, the load or capacity of the target service node meets a second preset condition.

In one implementation, the matching relationship determining unit includes:

a matching relationship sending unit, configured to send the IP address of the target service node that the terminal with the network attribute is suitable for accessing to the authoritative domain name server, so that the authoritative domain name server configures, in the stored domain name resolution list, the IP address of the service node corresponding to the local domain name server with the network attribute as the IP address of the target service node.

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

and the matching relationship configuration unit is used for configuring the domain name resolution list stored in an authoritative domain name server according to the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute, so as to configure the IP address of the service node corresponding to the local domain name server with the network attribute in the domain name resolution list as the IP address of the target service node.

Optionally, the apparatus further comprises:

and the relation configuration unit is used for configuring the domain name resolution list stored in the authoritative domain name server according to the matching relation between the network attribute and the IP address of the service node after the matching relation determines that the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute is used as the IP address of the service node matched with the network attribute in the domain name resolution list.

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

the method comprises the steps of obtaining average access time delay of each service node in a terminal access service system with different network attributes from a data server, wherein after the data server obtains the access time delay of different service nodes in a plurality of terminal access servers, the average access time delay of each service node accessed by the terminal with each network attribute is respectively calculated according to the network attributes of the terminal.

Optionally, the average delay obtaining unit includes:

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

the terminal classifying unit is used for grouping at least one terminal with the same network attribute into a terminal set according to the network attributes of the terminals to obtain a plurality of terminal sets representing different network attributes;

and the average time delay calculating unit is used for calculating the average access time delay of all the terminals in the terminal set respectively accessing each service node according to the access time delay of all the terminals in the terminal set representing the network attribute accessing each service node in the service system aiming at each network attribute, so as to obtain the average access time delay of the terminals with the network attribute respectively accessing each service node.

In a possible implementation manner, the average delay obtaining unit includes:

the mobile terminal comprises a first time delay obtaining unit, a second time delay obtaining unit and a third time delay obtaining unit, wherein the first time delay obtaining unit is used for respectively obtaining the average access time delay of each service node in a mobile terminal access service system with different network attributes, and the mobile terminal accesses the service nodes in the service system by adopting a wireless network;

the service node matching unit includes:

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

the matching relationship determination unit includes:

a first relation determining unit, configured to, for each network attribute, use an IP address of a target service node to which a mobile terminal with the network attribute is suitable for accessing as an IP address of a service node matched with the network attribute in a first domain name resolution list, where IP addresses of service nodes to which mobile terminals with different network attributes need to be scheduled are stored in the first domain name resolution list.

In another possible implementation manner, the average delay obtaining unit includes:

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

the service node matching unit includes:

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

the matching relationship determination unit includes:

and a second relation determining unit, configured to, for each network attribute, use an IP address of a target service node to which the wired network terminal of the network attribute is suitable for accessing as an IP address of a service node matched with the network attribute in a second domain name resolution list, where the IP address of the service node to which the wired network terminal of different network attributes needs to be scheduled is stored in the second domain name resolution list.

On the other hand, an embodiment of the present application further provides a configuration server, where the configuration server may include the above-mentioned scheduling control device.

Fig. 9 is a block diagram showing a hardware configuration of a server, and 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 are communicated with each other through a communication bus 904;

optionally, the communication interface 902 may be an interface of a communication module, such as an interface of a GSM module;

a processor 901 for executing programs;

a memory 903 for storing programs;

the program may include 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 embodiments of the present invention.

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

Among them, the procedure can be specifically used for:

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A scheduling control method, comprising:

respectively acquiring average access time delay of each service node in a terminal access service system with different network attributes from a data server, wherein when the terminal accesses different service nodes in the service system, the terminal sends a test data packet to the corresponding service node and sends the tested access time delay to the data server; after acquiring the access time delay of different service nodes in a plurality of terminal access service systems, the data server respectively calculates the average access time delay of each service node accessed by the terminal with each network attribute according to the network attribute of the terminal; the network attribute of the terminal represents an operator to which the terminal belongs and a geographical area;

2. The scheduling control method according to claim 1, wherein an average access delay of the terminal with the network attribute accessing the target serving node satisfies a first preset condition, and the method comprises:

3. The scheduling control method according to claim 1 or 2, wherein the load or capacity of the target serving node satisfies a second preset condition.

4. The scheduling control method according to claim 1, wherein the using the IP address of the target service node to which the terminal with the network attribute is adapted to access as the IP address of the service node matching the network attribute in the domain name resolution list comprises:

and sending the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute to an authoritative domain name server so that the authoritative domain name server configures the IP address of the service node corresponding to the local domain name server with the network attribute as the IP address of the target service node in a stored domain name resolution list.

5. The scheduling control method according to claim 1, wherein the using the IP address of the target service node to which the terminal with the network attribute is adapted to access as the IP address of the service node matching the network attribute in the domain name resolution list comprises:

and configuring a domain name resolution list stored in an authoritative domain name server according to the IP address of the target service node which is suitable for being accessed by the terminal with the network attribute, so as to configure the IP address of the service node corresponding to the local domain name server with the network attribute in the domain name resolution list as the IP address of the target service node.

6. The scheduling control method according to claim 1, 2, 4 or 5, wherein the obtaining the average access delay of each service node in the terminal access service system with different network attributes comprises:

acquiring access time delays of different service nodes in a plurality of terminals accessing a service system, wherein the network attributes of the terminals are different;

combining at least one terminal with the same network attribute into a terminal set according to the network attributes of the terminals to obtain a plurality of terminal sets representing different network attributes;

and aiming at the terminal set of each network attribute, respectively calculating the average access time delay of the terminal in the terminal set for accessing each service node according to the access time delay of all the terminals in the terminal set for accessing each service node in the service system, and obtaining the average access time delay of the terminals with different network attributes for accessing each service node.

7. The scheduling control method of claim 1, wherein the obtaining the average access delay of each service node in the terminal access service system with different network attributes respectively comprises:

respectively obtaining the average access time delay of each service node in a mobile terminal access service system with different network attributes, wherein the mobile terminal accesses the service nodes in the service system by adopting a wireless network;

the selecting, by the terminal for each network attribute, a target service node to which the terminal for the network attribute is suitable to access from a plurality of service nodes of the service system includes:

aiming at each mobile terminal with network attribute, selecting a target service node which is suitable for being accessed by the mobile terminal with the network attribute from a plurality of service nodes of the service system;

the step of regarding the IP address of the target service node to which the terminal with the network attribute is suitable to access as the IP address of the service node matched with the network attribute in the domain name resolution list for each network attribute includes:

and aiming at each network attribute, taking the IP address of a target service node which is suitable for being accessed by the mobile terminal with the network attribute as the IP address of the service node matched with the network attribute in a first domain name resolution list, wherein the IP addresses of the service nodes to which the mobile terminals with different network attributes need to be dispatched are stored in the first domain name resolution list.

8. The scheduling control method of claim 1, wherein the obtaining the average access delay of each service node in the terminal access service system with different network attributes respectively comprises:

respectively obtaining the average access time delay of each service node in a wired network terminal access service system with different network attributes, wherein the wired network terminal accesses the service nodes in the service system based on a wired network;

for each wired network terminal with network attribute, selecting a target service node which is suitable for being accessed by the wired network terminal with the network attribute from a plurality of service nodes of the service system;

and aiming at each network attribute, taking the IP address of a target service node which is suitable for being accessed by the wired network terminal of the network attribute as the IP address of the service node matched with the network attribute in a second domain name resolution list, wherein the IP addresses of the service nodes required to be dispatched by the wired network terminals with different network attributes are stored in the second domain name resolution list.

9. A scheduling control apparatus, comprising:

the system comprises an average time delay obtaining unit, a data server and a data processing unit, wherein the average time delay obtaining unit is used for obtaining the average access time delay of each service node in a terminal access service system with different network attributes from the data server respectively, and when the terminal accesses different service nodes in the service system, the terminal sends a test data packet to the corresponding service node and sends the tested access time delay to the data server; after acquiring the access time delay of different service nodes in a plurality of terminal access service systems, the data server respectively calculates the average access time delay of each service node accessed by the terminal with each network attribute according to the network attribute of the terminal; the network attribute of the terminal represents an operator to which the terminal belongs and a geographical area;

10. The apparatus according to claim 9, wherein the average delay obtaining unit includes:

the service node matching unit includes:

the matching relationship determination unit includes:

11. The apparatus according to claim 9, wherein the average delay obtaining unit includes:

the service node matching unit includes:

the matching relationship determination unit includes:

12. A dispatch control system, comprising:

a data server and a configuration server;

the data server is used for acquiring access time delays of different service nodes in a plurality of terminal access service systems; respectively calculating the average access time delay of each service node in all the terminal access service systems with the network attributes aiming at each network attribute terminal, wherein when the terminal accesses different service nodes in the service systems, the terminal sends a test data packet to the corresponding service node and sends the tested access time delay to the data server; the network attribute of the terminal represents an operator to which the terminal belongs and a geographical area;

13. The scheduling control system of claim 12 wherein the data server is configured to obtain access delays of the plurality of terminals for accessing different service nodes in the service system, and in particular, to obtain access delays of the plurality of mobile terminals for accessing different service nodes in the service system and access delays of the plurality of wired network terminals for accessing different service nodes in the service system;

the data server calculates, for each network attribute of the terminal, an average access delay of each service node in all terminal access service systems having the network attribute, and is specifically configured to:

aiming at the mobile terminal with each network attribute, calculating the average access time delay of all the mobile terminals with the network attribute for accessing each service node in a service system, wherein the mobile terminals access the service nodes in the service system by adopting a wireless network;

aiming at the wired network terminal with each network attribute, calculating the average access time delay of all the wired network terminals with the network attribute for accessing each service node in a service system, wherein the wired network terminals access the service nodes in the service system based on a wired network;

when the configuration server selects a target service node suitable for being accessed by a terminal with each network attribute from a plurality of service nodes of the service system according to the average access delay of each service node in the service system accessed by the terminal with different network attributes, the configuration server is specifically configured to:

selecting a target service node which is suitable for being accessed by the mobile terminal with each network attribute from a plurality of service nodes of the service system respectively; and selecting a target service node which is suitable for being accessed by the wired network terminal of each network attribute.

14. The dispatch control system of claim 13, further comprising: the system comprises a plurality of speed measuring nodes deployed in different machine rooms in the service system, wherein each service node of the service system is associated with one speed measuring node, and the speed measuring node associated with the service node and the service node are deployed in the same machine room;

the data server is specifically configured to, when obtaining access delays of different service nodes in a plurality of mobile terminals accessing the service system: acquiring access time delay of a plurality of mobile terminals for accessing different speed measuring nodes;

the data server calculates, for each network attribute of the mobile terminal, an average access delay of each service node in the service system accessed by all the mobile terminals having the network attribute, and is specifically configured to:

aiming at the mobile terminal with each network attribute, calculating the average access time delay of each speed measuring node in all the mobile terminals with the network attribute accessing the service system, and determining the average access time delay of each service node in all the mobile terminals with the network attribute accessing the service system according to the incidence relation between the speed measuring node and the service node;

the speed measurement node is used for testing the access time delay from the target gateway to the speed measurement node according to the IP address of the target gateway returned by the service node associated with the speed measurement node, the IP address of the target gateway is the IP address of the gateway to which the wired network terminal belongs, which is reversely routed when the service node associated with the speed measurement node receives the access request of the wired network terminal, and the network attribute of the wired network terminal is the same as the network attribute of the target gateway to which the wired network terminal belongs; and taking the access delay from the target gateway to the speed measuring node as the access delay from the wired network terminal to the speed measuring node, and sending the access delay to the data server.

15. A configuration server comprising a memory and a processor;

the memory is used for storing programs;

the processor is configured to execute the program to implement the steps of the scheduling control method according to any one of claims 1 to 8.

16. A computer-readable storage medium, comprising a computer program which, when executed, is adapted to implement the steps of the scheduling control method according to any of claims 1 to 8.