CN113301074A - Data request load scheduling method and device, electronic equipment and readable storage medium - Google Patents
Data request load scheduling method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113301074A CN113301074A CN202010340864.3A CN202010340864A CN113301074A CN 113301074 A CN113301074 A CN 113301074A CN 202010340864 A CN202010340864 A CN 202010340864A CN 113301074 A CN113301074 A CN 113301074A
- Authority
- CN
- China
- Prior art keywords
- network server
- data
- data request
- scheduling
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 7
- 238000004590 computer program Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the disclosure discloses a data request load scheduling method, a data request load scheduling device, an electronic device and a readable storage medium, wherein the method comprises the following steps: receiving data requests sent by a local DNS server, wherein the number of the data requests is one or more, and the data requests carry domain name information of target requests; acquiring a network server address corresponding to the target request domain name information according to the data request; and acquiring the scheduling parameters of the network server, generating a feedback message based on the address of the network server and the scheduling parameters of the network server, and sending the feedback message to the local DNS server so that the local DNS server schedules the data request according to the scheduling parameters of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of data processing, in particular to a data request load scheduling method and device, electronic equipment and a readable storage medium.
Background
With the development of data technology, in order to enable a user to obtain data to be accessed more quickly and accurately, a CDN (Content Delivery Network) is in the process of generating, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed on the CDN. Currently, CDN scheduling mainly implements traffic load balancing based on DNS server data, but because a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by a Local DNS server, and user-based scheduling cannot be implemented, so that the CDN scheduling lacks a certain fineness.
Disclosure of Invention
The embodiment of the disclosure provides a data request load scheduling method and device, electronic equipment and a readable storage medium.
In a first aspect, an embodiment of the present disclosure provides a data request load scheduling method.
Specifically, the data request load scheduling method includes:
receiving data requests sent by a local DNS server, wherein the number of the data requests is one or more, and the data requests carry domain name information of target requests;
acquiring a network server address corresponding to the target request domain name information according to the data request;
and acquiring scheduling parameters of the network server, generating a feedback message based on the address of the network server and the scheduling parameters of the network server, and sending the feedback message to the local DNS server so that the local DNS server schedules the data request according to the scheduling parameters of the network server.
With reference to the first aspect, in a first implementation manner of the first aspect, the data request and the feedback packet are sent based on a preset command.
With reference to the first aspect and the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the network server address is a content distribution network node IP address.
With reference to the first aspect, the first implementation manner of the first aspect, and the second implementation manner of the first aspect, in a third implementation manner of the first aspect, before generating a feedback packet based on the address of the network server and the scheduling parameter of the network server and sending the feedback packet to the local DNS server, the embodiment of the present disclosure further includes:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
With reference to the first aspect, the first implementation manner of the first aspect, the second implementation manner of the first aspect, and the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the embodiment of the present disclosure is configured to determine the scheduling parameter as a load weight.
In a second aspect, a method for scheduling data request load is provided in the embodiments of the present disclosure.
Specifically, the data request load scheduling method includes:
receiving data requests sent by a data request party, wherein the number of the data requests is one or more, and the data requests carry domain name information of target requests;
sending the data request to an authoritative DNS server based on a preset command so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
and receiving and analyzing a feedback message sent by the authoritative DNS server, and scheduling the data request of the data request party according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server.
With reference to the second aspect, in a first implementation manner of the second aspect, the scheduling the data request of the data requester according to the feedback packet is implemented as:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
With reference to the second aspect and the first implementation manner of the second aspect, in a second implementation manner of the second aspect, the feedback message further includes the number of network server addresses.
With reference to the second aspect, the first implementation manner of the second aspect, and the second implementation manner of the second aspect, in a third implementation manner of the second aspect, before scheduling the data request of the data requester according to the feedback packet, the method further includes:
and analyzing the feedback message according to the number of the network server addresses.
With reference to the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, and the third implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the present disclosure further includes:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
With reference to the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, and the fourth implementation manner of the second aspect, in a fifth implementation manner of the second aspect of the present disclosure, the network server address is a content distribution network node IP address.
With reference to the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, the fourth implementation manner of the second aspect, and the fifth implementation manner of the second aspect, in a sixth implementation manner of the second aspect, the scheduling parameter is a load weight.
In a third aspect, an embodiment of the present disclosure provides a data request load scheduling method.
Specifically, the data request load scheduling method includes:
the local DNS server receives a data request sent by a data requester and sends the data request to an authoritative DNS server based on a preset command so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, wherein the number of the data requests is one or more, and the data request carries the target request domain name information;
the authoritative DNS server receives a data request sent by the local DNS server, acquires a network server address corresponding to the target request domain name information according to the data request, acquires a scheduling parameter of the network server, generates a feedback message based on the network server address and the scheduling parameter of the network server, and sends the feedback message to the local DNS server so that the local DNS server schedules the data request according to the scheduling parameter of the network server;
and the local DNS server receives and analyzes a feedback message sent by the authoritative DNS server, and schedules the data request of the data requester according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server.
With reference to the third aspect, in a first implementation manner of the third aspect, before the generating, by the authoritative DNS server, a feedback packet based on the address of the network server and the scheduling parameter of the network server, and sending the feedback packet to the local DNS server, the embodiment of the present disclosure further includes:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
With reference to the third aspect and the first implementation manner of the third aspect, in a second implementation manner of the third aspect, the embodiment of the present disclosure further includes, before the local DNS server schedules the data request of the data requester according to the feedback packet, that:
and analyzing the feedback message according to the number of the network server addresses.
With reference to the third aspect, the first implementation manner of the third aspect, and the second implementation manner of the third aspect, in a third implementation manner of the third aspect, the scheduling, by the local DNS server, the data request of the data requester according to the feedback packet is implemented as:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
With reference to the third aspect, the first implementation manner of the third aspect, the second implementation manner of the third aspect, and the third implementation manner of the third aspect, in a fourth implementation manner of the third aspect, the present disclosure further includes:
and the local DNS server caches the data request and the feedback message, and sends a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
With reference to the third aspect, the first implementation manner of the third aspect, the second implementation manner of the third aspect, the third implementation manner of the third aspect, and the fourth implementation manner of the third aspect, in a fifth implementation manner of the third aspect, the network server address is a content distribution network node IP address.
With reference to the third aspect, the first implementation manner of the third aspect, the second implementation manner of the third aspect, the third implementation manner of the third aspect, the fourth implementation manner of the third aspect, and the fifth implementation manner of the third aspect, in a sixth implementation manner of the third aspect, the present disclosure provides that the scheduling parameter is a load weight.
In a fourth aspect, an embodiment of the present disclosure provides a data request load scheduling apparatus.
Specifically, the data request load scheduling apparatus includes:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is configured to receive data requests sent by a local DNS server, the number of the data requests is one or more, and the data requests carry domain name information of target requests;
the acquisition module is configured to acquire a network server address corresponding to the target request domain name information according to the data request;
and the generating module is configured to acquire the scheduling parameter of the network server, generate a feedback message based on the address of the network server and the scheduling parameter of the network server, and send the feedback message to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
With reference to the fourth aspect, in a first implementation manner of the fourth aspect, in the embodiment of the present disclosure, the data request and the feedback packet are sent based on a preset command.
With reference to the fourth aspect and the first implementation manner of the fourth aspect, in a second implementation manner of the fourth aspect, the network server address is a content distribution network node IP address.
With reference to the fourth aspect, the first implementation manner of the fourth aspect, and the second implementation manner of the fourth aspect, in a third implementation manner of the fourth aspect, the generating module is further configured to, before generating a feedback packet based on the address of the network server and the scheduling parameter of the network server, generate a feedback packet and send the feedback packet to the local DNS server:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
With reference to the fourth aspect, the first implementation manner of the fourth aspect, the second implementation manner of the fourth aspect, and the third implementation manner of the fourth aspect, in a fourth implementation manner of the fourth aspect, the scheduling parameter is a load weight.
In a fifth aspect, an embodiment of the present disclosure provides a data request load scheduling apparatus.
Specifically, the data request load scheduling apparatus includes:
the second receiving module is configured to receive one or more data requests sent by a data requesting party, wherein the data requests carry domain name information of a target request;
the sending module is configured to send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
and the scheduling module is configured to receive and analyze a feedback message sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and a scheduling parameter of the network server.
With reference to the fifth aspect, in a first implementation manner of the fifth aspect, a part of the scheduling module that schedules the data request of the data requestor according to the feedback packet is configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
With reference to the fifth aspect and the first implementation manner of the fifth aspect, in a second implementation manner of the fifth aspect, an embodiment of the present disclosure further includes, in the feedback message, the number of network server addresses.
With reference to the fifth aspect, the first implementation manner of the fifth aspect, and the second implementation manner of the fifth aspect, in a third implementation manner of the fifth aspect, the scheduling module is further configured to, before scheduling the data request of the data requester according to the feedback packet:
and analyzing the feedback message according to the number of the network server addresses.
With reference to the fifth aspect, the first implementation manner of the fifth aspect, the second implementation manner of the fifth aspect, and the third implementation manner of the fifth aspect, in a fourth implementation manner of the fifth aspect, the present disclosure further includes:
and the caching module is configured to cache the data request and the feedback message, and send a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
With reference to the fifth aspect, the first implementation manner of the fifth aspect, the second implementation manner of the fifth aspect, the third implementation manner of the fifth aspect, and the fourth implementation manner of the fifth aspect, in a fifth implementation manner of the fifth aspect of the present disclosure, the network server address is a content distribution network node IP address.
With reference to the fifth aspect, the first implementation manner of the fifth aspect, the second implementation manner of the fifth aspect, the third implementation manner of the fifth aspect, the fourth implementation manner of the fifth aspect, and the fifth implementation manner of the fifth aspect, in a sixth implementation manner of the fifth aspect, the present disclosure provides that the scheduling parameter is a load weight.
In a sixth aspect, an embodiment of the present disclosure provides a data request load scheduling apparatus.
Specifically, the data request load scheduling apparatus includes:
the local DNS server is configured to receive a data request sent by a data requester, send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, receive and analyze a feedback message sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback message, wherein the number of the data requests is one or more, the data request carries the target request domain name information, and the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server;
and the authoritative DNS server is configured to receive the data request sent by the local DNS server, acquire a network server address corresponding to the domain name information of the target request according to the data request, acquire a scheduling parameter of the network server, generate a feedback message based on the network server address and the scheduling parameter of the network server, and send the feedback message to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
With reference to the sixth aspect, in a first implementation manner of the sixth aspect, before the authoritative DNS server generates a feedback packet based on the network server address and the scheduling parameter of the network server, the method further includes:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
With reference to the sixth aspect and the first implementation manner of the sixth aspect, in a second implementation manner of the sixth aspect, before the local DNS server schedules the data request of the data requestor according to the feedback packet, the embodiment of the present disclosure is further configured to:
and analyzing the feedback message according to the number of the network server addresses.
With reference to the sixth aspect, the first implementation manner of the sixth aspect, and the second implementation manner of the sixth aspect, in a third implementation manner of the sixth aspect, the scheduling, by the local DNS server, of the data request of the data requestor according to the feedback packet is configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
With reference to the sixth aspect, the first implementation manner of the sixth aspect, the second implementation manner of the sixth aspect, and the third implementation manner of the sixth aspect, in a fourth implementation manner of the sixth aspect, the local DNS server is further configured to:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
With reference to the sixth aspect, the first implementation manner of the sixth aspect, the second implementation manner of the sixth aspect, the third implementation manner of the sixth aspect, and the fourth implementation manner of the sixth aspect, in a fifth implementation manner of the sixth aspect of the present disclosure, the network server address is a content distribution network node IP address.
With reference to the sixth aspect, the first implementation manner of the sixth aspect, the second implementation manner of the sixth aspect, the third implementation manner of the sixth aspect, the fourth implementation manner of the sixth aspect, and the fifth implementation manner of the sixth aspect, in a sixth implementation manner of the sixth aspect, the present disclosure provides that the scheduling parameter is a load weight.
In a seventh aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, where the memory is used to store one or more computer instructions for supporting a data request load scheduling apparatus to execute the data request load scheduling method, and the processor is configured to execute the computer instructions stored in the memory. The data request load scheduling device may further comprise a communication interface for the data request load scheduling device to communicate with other devices or a communication network.
In an eighth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing computer instructions for a data request load scheduling apparatus, which includes computer instructions for executing the data request load scheduling method to the data request load scheduling apparatus.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
according to the technical scheme, the obtained network server address corresponding to the domain name information of the target request in the data request forwarded by the local DNS server and the scheduling parameter of the network server are sent to the local DNS server together, so that the local DNS server can schedule the received data request according to the scheduling parameter of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the disclosure.
Drawings
Other features, objects, and advantages of embodiments of the disclosure will become more apparent from the following detailed description of non-limiting embodiments when taken in conjunction with the accompanying drawings. In the drawings:
fig. 1 shows a flow chart of a data request load scheduling method according to an embodiment of the present disclosure;
FIG. 2 shows a flow diagram of a data request load scheduling method according to another embodiment of the present disclosure;
FIG. 3 illustrates a flow chart of a data request load scheduling method according to yet another embodiment of the present disclosure;
fig. 4 is a schematic application diagram of a data request load scheduling method according to an embodiment of the present disclosure;
fig. 5 shows a block diagram of a data request load scheduling apparatus according to an embodiment of the present disclosure;
fig. 6 shows a block diagram of a data request load scheduling apparatus according to another embodiment of the present disclosure;
fig. 7 is a block diagram illustrating a structure of a data request load scheduling apparatus according to still another embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a computer system suitable for implementing a data request load scheduling method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, exemplary embodiments of the disclosed embodiments will be described in detail with reference to the accompanying drawings so that they can be easily implemented by those skilled in the art. Also, for the sake of clarity, parts not relevant to the description of the exemplary embodiments are omitted in the drawings.
In the disclosed embodiments, it is to be understood that terms such as "including" or "having," etc., are intended to indicate the presence of the disclosed features, numbers, steps, behaviors, components, parts, or combinations thereof, and are not intended to preclude the possibility that one or more other features, numbers, steps, behaviors, components, parts, or combinations thereof may be present or added.
It should be further noted that the embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict. The embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
According to the technical scheme provided by the embodiment of the disclosure, the obtained network server address corresponding to the domain name information of the target request in the data request forwarded by the local DNS server and the scheduling parameter of the network server are sent to the local DNS server together, so that the local DNS server can schedule the received data request according to the scheduling parameter of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
Fig. 1 shows a flowchart of a data request load scheduling method according to an embodiment of the present disclosure, as shown in fig. 1, the data request load scheduling method includes the following steps S101 to S103:
in step S101, receiving data requests sent by a local DNS server, where the number of the data requests is one or more, and the data requests carry domain name information of a target request;
in step S102, acquiring a network server address corresponding to the target request domain name information according to the data request;
in step S103, a scheduling parameter of the network server is obtained, and a feedback packet is generated based on the address of the network server and the scheduling parameter of the network server and sent to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to obtain data to be accessed more quickly and accurately, a CDN (Content Delivery Network) has come up, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed on the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling method is provided, which sends an address of a network server, which corresponds to domain name information of a target request in a data request forwarded by a local DNS server, and a scheduling parameter of the network server to the local DNS server, so that the local DNS server can schedule the received data request according to the scheduling parameter of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling method is suitable for an authoritative DNS server or other servers that can communicate with a local DNS server and can acquire a network server address corresponding to a target request domain name. For convenience of description, the following explanation and explanation take the authoritative DNS server as an example.
In an embodiment of the present disclosure, the data request refers to a domain name data request that is sent by a data requestor in a Domain Name System (DNS), at least carries domain name information of a target request that the data requestor wants to access, and wants to acquire an address of a network server corresponding to the domain name information of the target request. The number of the data requests may be one or more. In an embodiment of the present disclosure, the network server address may be, for example, a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the data requestor may also be called a domain name data requestor, which refers to a party that issues the domain name data request, for example, the data requestor may be a computer, a handheld device such as a mobile phone, or another device that can issue the domain name data request.
In an embodiment of the present disclosure, the local DNS server is used in a domain name system to communicate with the domain name data requester, receive a domain name data request sent by the domain name data requester, communicate with a higher level DNS server, that is, an authorized authoritative DNS server, and forward the domain name data request sent by the domain name data requester to a server of the authoritative DNS server, where the domain name data request at least carries a domain name information domain name data request of a target request that the domain name data requester wants to access.
In an embodiment of the present disclosure, the authoritative DNS server refers to an authorized DNS server in a domain name system, which is used for communicating with the local DNS server, and processes a domain name data request sent by the local DNS server, converts the domain name data request into a network server address corresponding to the target request domain name information, returns the network server address obtained by the conversion to the local DNS server, and returns the network server address obtained by the conversion to the domain name data requester through the local DNS server, so that the domain name data requester can directly access the network server corresponding to the IP address based on an HTTP protocol according to the received network server address to obtain the desired data. Since the authoritative DNS server is an authorized DNS server, the authoritative DNS server has stored or is capable of obtaining the mapping between different domain names and corresponding network server addresses, for example, by communicating with a network server.
In an embodiment of the present disclosure, the scheduling parameter is a load weight, and the load weight is used to indicate how many data connections the network server can bear, for example, if the load weight of the network server is 100, this means that the network server can bear at most 100 data connections and data transmissions, that is, can establish data connections and transmit data with at most 100 data requesters. In an embodiment of the present disclosure, the scheduling parameter of the network server may be stored in the authoritative DNS server in advance.
In an embodiment of the present disclosure, after obtaining a network server address corresponding to target request domain name information in a data request according to a received data request, a scheduling parameter of the network server may be obtained, and a feedback packet is generated and sent to the local DNS server according to a rule of a preset communication protocol based on the network server address and the scheduling parameter of the network server, so that the local DNS server schedules a data request of the data requester according to the scheduling parameter of the network server. The predefined communication protocol may be, for example, an EDNS (enhanced DNS) protocol, which may support the addition of extension fields, so that more useful information can be sent. Therefore, the local DNS server can realize smooth scheduling based on users, so that the scheduling fineness of a CDN (Content Delivery Network) can be effectively enhanced, and the system stability is enhanced.
In an embodiment of the present disclosure, the EDNS protocol can also increase the number of IP addresses that the authoritative DNS server can return at a single time by means of the custom coding scheme it supports. For example, in the prior art, due to the limitation of the size of the DNS packet, an authoritative DNS server can return only 16 IP addresses to the local DNS server at a time, whereas in the present embodiment, by means of a custom code that can be supported by the EDNS protocol, the number of IP addresses that the authoritative DNS server can return at a time is the number of network servers — the number of IP addresses corresponding to each network server, and assuming that the number of network servers is still 16 and the number of IP addresses corresponding to each network server is 2, the number of IP addresses that the authoritative DNS server can return at a time is 16 — 2 — 32.
In an embodiment of the present disclosure, the data request and the feedback packet are both sent based on a preset command, where the preset command may be a dig command, and the scheduling parameter can be carried in the feedback packet based on an EDNS protocol by using the dig command.
In an embodiment of the present disclosure, before the step of generating a feedback packet based on the address of the network server and the scheduling parameter of the network server and sending the feedback packet to the local DNS server in step S103, the method further includes:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
In order to help the local DNS server to correctly resolve the feedback packet to obtain correct and all network server addresses and avoid situations such as loss of address information of the network server obtained by the resolving, loss of quantity, and the like, the authoritative DNS server determines the quantity of the network server addresses after obtaining the network server addresses corresponding to the domain name information of the target request in the data request, and generates the feedback packet together with the network server addresses and the scheduling parameters of the network server and sends the feedback packet to the local DNS server. The feedback message is obtained according to the specification of the preset communication protocol and has a preset message format.
Fig. 2 shows a flowchart of a data request load scheduling method according to another embodiment of the present disclosure, and as shown in fig. 2, the data request load scheduling method includes the following steps S201 to S203:
in step S201, receiving data requests sent by a data requester, where the number of the data requests is one or more, and the data requests carry domain name information of a target request;
in step S202, sending the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
in step S203, a feedback packet sent by the authoritative DNS server is received and analyzed, and the data request of the data requester is scheduled according to the feedback packet, where the feedback packet includes a network server address corresponding to the target request domain name information and a scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to acquire data to be accessed more quickly and accurately, a CDN has come up with, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed for the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling method is proposed, which schedules a data request according to a network server address received corresponding to target request domain name information in the data request sent by a data requester and a scheduling parameter of a network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling method is suitable for a local DNS server or other servers that can communicate with an authoritative DNS server to obtain, by means of the authoritative DNS server, a network server address corresponding to a target request domain name. For convenience of description, the local DNS server is explained and illustrated below as an example.
In the embodiment, the local DNS server forwards the received data request sent by the data requester to the authoritative DNS server, enabling the authoritative DNS server to obtain the network server address corresponding to the target request domain name information according to the data request, and sending a feedback message generated based on the address of the network server and the scheduling parameter of the network server to the local DNS server, the local DNS server receiving the feedback message and then analyzing the feedback message, and carries out scheduling and network server address allocation for the data request of the data requester according to the scheduling parameter of the network server and the network server address obtained by analysis, and the data request party can access the corresponding network server according to the distributed network server address based on the HTTP protocol to acquire the data required by the data request party.
In an embodiment of the present disclosure, the network server address may be a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the scheduling parameter is a load weight.
In this embodiment, the step of scheduling the data request of the data requester according to the feedback packet in step S203 may be implemented as:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
In this embodiment, in order to perform accurate and refined scheduling on the data requester, first determining a first distribution network server that is first allocated to the data requester and a first scheduling parameter of the first distribution network server, then determining whether data connection of the first distribution network server reaches a full load, if not, allocating an address of the first distribution network server to the data requester until the first distribution network server reaches the full load, then determining a second distribution network server according to the above process, acquiring a second scheduling parameter of the second distribution network server, and allocating the address of the second distribution network server to the data requester according to the second scheduling parameter until the network server carried in the feedback message is allocated. In this way, by means of the load weight, a user-based fine and smooth scheduling of the data request load can be achieved, while also contributing to an enhanced system stability.
For example, if the feedback message includes two network servers, i.e., a network server a and a network server B, where the IP addresses of the network server a are IP _ a1 and IP _ a2, the load weight is 100, the IP addresses of the network server B are IP _ B1 and IP _ B2, and the load weight is 10, the local DNS server may allocate the IP addresses IP _ a1 and IP _ a2 of the network server a to the first 100 data requesters, and allocate the IP addresses IP _ B1 and IP _ B2 of the network server B to the subsequent data requesters, until the full load of the network server B is reached.
In an embodiment of the present disclosure, the allocation order of the network servers may be set according to the needs of practical applications, for example, the allocation order may be set as the generation order of the data requests, that is, the network servers are allocated according to the sequence of the data requests, and of course, other orders may also be adopted, which is not specifically limited by the present disclosure.
In an embodiment of the present disclosure, the feedback message further includes the number of the network server addresses.
In this embodiment, before the step of scheduling the data request of the data requester according to the feedback packet in step S203, the method further includes:
and analyzing the feedback message according to the number of the network server addresses.
In order to correctly analyze the feedback message to obtain correct and all network server addresses and avoid the situations of loss, quantity loss and the like of network server address information obtained by analysis, the authoritative DNS server also adds the quantity of the network server addresses, the network server addresses and the scheduling parameters of the network servers into the feedback message, that is, the feedback message includes the quantity of the network server addresses in addition to the network server addresses corresponding to the target request domain name information and the scheduling parameters of the network servers. Therefore, after receiving the feedback message sent by the authoritative DNS server, the local DNS server can extract the number of the network server addresses according to the regulation of a preset communication protocol and a preset message format, and further continuously analyze the feedback message according to the number of the network server addresses to finally obtain all the network server addresses and the scheduling parameters of the network server.
In an embodiment of the present disclosure, the method further includes:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
In this embodiment, the local DNS server has a data caching capability and can cache the received data request and feedback packet, so that when a data request having the same destination request domain name information as the cached data request is received from the data requestor within the effective caching time of the data request and feedback packet, the network server address corresponding to the destination request domain name information of the cached data request can be directly sent to the data requestor without being requested from the authoritative DNS server.
Technical terms and technical features related to the embodiment shown in fig. 2 are the same as or similar to those mentioned in the embodiment shown in fig. 1, and for the corresponding technical terms and technical features, reference may be made to the above explanation and description of the embodiment shown in fig. 1, and the detailed description of the disclosure is omitted here.
Fig. 3 shows a flowchart of a data request load scheduling method according to still another embodiment of the present disclosure, and as shown in fig. 3, the data request load scheduling method includes the following steps S301 to S303:
in step S301, a local DNS server receives a data request sent by a data requester, and sends the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, where the number of the data requests is one or more, and the data request carries the target request domain name information;
in step S302, the authoritative DNS server receives the data request sent by the local DNS server, obtains a network server address corresponding to the target request domain name information according to the data request, obtains a scheduling parameter of the network server, and generates a feedback packet based on the network server address and the scheduling parameter of the network server, and sends the feedback packet to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server;
in step S303, the local DNS server receives and analyzes a feedback packet sent by the authoritative DNS server, and schedules the data request of the data requestor according to the feedback packet, where the feedback packet includes a network server address corresponding to the target request domain name information and a scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to acquire data to be accessed more quickly and accurately, a CDN has come up with, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed for the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling method is provided, in which an authoritative DNS server sends, to a local DNS server, an obtained network server address corresponding to target request domain name information in a data request forwarded by the local DNS server, and scheduling parameters of the network server, so that the local DNS server can schedule the received data request according to the scheduling parameters of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling method is applicable to a data request load scheduling system including a local DNS server and an authoritative DNS server.
In an embodiment of the present disclosure, before the authoritative DNS server generates a feedback packet based on the address of the network server and the scheduling parameter of the network server, and sends the feedback packet to the local DNS server, the method further includes:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
In an embodiment of the present disclosure, before scheduling, by the local DNS server, the data request of the data requestor according to the feedback packet, the method further includes:
and analyzing the feedback message according to the number of the network server addresses.
In an embodiment of the present disclosure, the network server address may be a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the scheduling parameter is a load weight.
In this embodiment, the local DNS server schedules the data request of the data requestor according to the feedback packet, and is implemented as:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
In an embodiment of the present disclosure, the method further includes:
and the local DNS server caches the data request and the feedback message, and sends a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
Technical terms and technical features related to the embodiment shown in fig. 3 are the same as or similar to those mentioned in the embodiment shown in fig. 1-2, and for the corresponding technical terms and technical features, reference may be made to the above explanation and description of the embodiment shown in fig. 1-2, and the detailed description of the disclosure is omitted here.
Fig. 4 is a schematic application diagram of a data request load scheduling method according to an embodiment of the present disclosure, and as shown in fig. 4, a data requester 1 and a data requester 2 respectively send DNS data requests to local DNS servers, and the local DNS servers forward the received DNS data requests to authoritative DNS servers, where the DNS data requests carry domain name information of target requests; the authoritative DNS server acquires an IP address of a CDN node corresponding to the target request domain name information according to the received DNS data request, acquires a load weight of the CDN node, generates a feedback message based on the IP address of the CDN node and the load weight of the CDN node, and sends the feedback message to the local DNS server by means of DNS response; and the local DNS server receives and analyzes the feedback message sent by the authoritative DNS server, and schedules the DNS data request of the data requester according to the feedback message. And then, the data requester can access the CDN node corresponding to the IP address based on an HTTP protocol according to the distributed IP address of the CDN node and acquire data by means of HTTP response.
The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods.
Fig. 5 shows a block diagram of a data request load scheduling apparatus according to an embodiment of the present disclosure, which may be implemented as part or all of an electronic device through software, hardware, or a combination of the two. As shown in fig. 5, the data request load scheduling apparatus includes:
a first receiving module 501, configured to receive data requests sent by a local DNS server, where the number of the data requests is one or more, and the data requests carry domain name information of a target request;
an obtaining module 502 configured to obtain, according to the data request, a network server address corresponding to the target request domain name information;
a generating module 503, configured to obtain the scheduling parameter of the network server, and generate a feedback packet based on the address of the network server and the scheduling parameter of the network server, and send the feedback packet to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to obtain data to be accessed more quickly and accurately, a CDN (Content Delivery Network) has come up, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed on the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling apparatus is proposed, which sends the acquired network server address corresponding to the domain name information of the target request in the data request forwarded by the local DNS server, and the scheduling parameter of the network server to the local DNS server, so that the local DNS server can schedule the received data request according to the scheduling parameter of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling device may be implemented as an authoritative DNS server or other server capable of communicating with a local DNS server and acquiring the address of the network server corresponding to the domain name of the target request. For convenience of description, the following explanation and explanation take the authoritative DNS server as an example.
In an embodiment of the present disclosure, the data request refers to a domain name data request that is sent by a data requestor in a Domain Name System (DNS), at least carries domain name information of a target request that the data requestor wants to access, and wants to acquire an address of a network server corresponding to the domain name information of the target request. The number of the data requests may be one or more. In an embodiment of the present disclosure, the network server address may be, for example, a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the data requestor may also be called a domain name data requestor, which refers to a party that issues the domain name data request, for example, the data requestor may be a computer, a handheld device such as a mobile phone, or another device that can issue the domain name data request.
In an embodiment of the present disclosure, the local DNS server is used in a domain name system to communicate with the domain name data requester, receive a domain name data request sent by the domain name data requester, communicate with a higher level DNS server, that is, an authorized authoritative DNS server, and forward the domain name data request sent by the domain name data requester to a server of the authoritative DNS server, where the domain name data request at least carries a domain name information domain name data request of a target request that the domain name data requester wants to access.
In an embodiment of the present disclosure, the authoritative DNS server refers to an authorized DNS server in a domain name system, which is used for communicating with the local DNS server, and processes a domain name data request sent by the local DNS server, converts the domain name data request into a network server address corresponding to the target request domain name information, returns the network server address obtained by the conversion to the local DNS server, and returns the network server address obtained by the conversion to the domain name data requester through the local DNS server, so that the domain name data requester can directly access the network server corresponding to the IP address based on an HTTP protocol according to the received network server address to obtain the desired data. Since the authoritative DNS server is an authorized DNS server, the authoritative DNS server has stored or is capable of obtaining the mapping between different domain names and corresponding network server addresses, for example, by communicating with a network server.
In an embodiment of the present disclosure, the scheduling parameter is a load weight, and the load weight is used to indicate how many data connections the network server can bear, for example, if the load weight of the network server is 100, this means that the network server can bear at most 100 data connections and data transmissions, that is, can establish data connections and transmit data with at most 100 data requesters. In an embodiment of the present disclosure, the scheduling parameter of the network server may be stored in the authoritative DNS server in advance.
In an embodiment of the present disclosure, after obtaining a network server address corresponding to target request domain name information in a data request according to a received data request, a scheduling parameter of the network server may be obtained, and a feedback packet is generated and sent to the local DNS server according to a rule of a preset communication protocol based on the network server address and the scheduling parameter of the network server, so that the local DNS server schedules a data request of the data requester according to the scheduling parameter of the network server. The predefined communication protocol may be, for example, an EDNS (enhanced DNS) protocol, which may support the addition of extension fields, so that more useful information can be sent. Therefore, the local DNS server can realize smooth scheduling based on users, so that the scheduling fineness of a CDN (Content Delivery Network) can be effectively enhanced, and the system stability is enhanced.
In an embodiment of the present disclosure, the EDNS protocol can also increase the number of IP addresses that the authoritative DNS server can return at a single time by means of the custom coding scheme it supports. For example, in the prior art, due to the limitation of the size of the DNS packet, an authoritative DNS server can return only 16 IP addresses to the local DNS server at a time, whereas in the present embodiment, by means of a custom code that can be supported by the EDNS protocol, the number of IP addresses that the authoritative DNS server can return at a time is the number of network servers — the number of IP addresses corresponding to each network server, and assuming that the number of network servers is still 16 and the number of IP addresses corresponding to each network server is 2, the number of IP addresses that the authoritative DNS server can return at a time is 16 — 2 — 32.
In an embodiment of the present disclosure, the data request and the feedback packet are both sent based on a preset command, where the preset command may be a dig command, and the scheduling parameter can be carried in the feedback packet based on an EDNS protocol by using the dig command.
In an embodiment of the present disclosure, before the generating module 503 generates a feedback packet based on the address of the network server and the scheduling parameter of the network server, and sends the feedback packet to the local DNS server, the generating module is further configured to:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
In order to help the local DNS server to correctly resolve the feedback packet to obtain correct and all network server addresses and avoid situations such as loss of address information of the network server obtained by the resolving, loss of quantity, and the like, the authoritative DNS server determines the quantity of the network server addresses after obtaining the network server addresses corresponding to the domain name information of the target request in the data request, and generates the feedback packet together with the network server addresses and the scheduling parameters of the network server and sends the feedback packet to the local DNS server. The feedback message is obtained according to the specification of the preset communication protocol and has a preset message format.
Fig. 6 shows a block diagram of a data request load scheduling apparatus according to another embodiment of the present disclosure, which may be implemented as part or all of an electronic device by software, hardware, or a combination of the two. As shown in fig. 6, the data request load scheduling apparatus includes:
a second receiving module 601, configured to receive data requests sent by a data requesting party, where the number of the data requests is one or more, and the data requests carry domain name information of a target request;
a sending module 602, configured to send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
the scheduling module 603 is configured to receive and analyze a feedback packet sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback packet, where the feedback packet includes a network server address corresponding to the target request domain name information and a scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to acquire data to be accessed more quickly and accurately, a CDN has come up with, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed for the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling apparatus is proposed, which schedules a data request according to a network server address received corresponding to target request domain name information in the data request sent by a data requester and a scheduling parameter of a network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling device may be implemented as a local DNS server or other server that can communicate with an authoritative DNS server to obtain, by means of the authoritative DNS server, the network server address corresponding to the target request domain name. For convenience of description, the local DNS server is explained and illustrated below as an example.
In the embodiment, the local DNS server forwards the received data request sent by the data requester to the authoritative DNS server, enabling the authoritative DNS server to obtain the network server address corresponding to the target request domain name information according to the data request, and sending a feedback message generated based on the address of the network server and the scheduling parameter of the network server to the local DNS server, the local DNS server receiving the feedback message and then analyzing the feedback message, and carries out scheduling and network server IP address allocation for the data request of the data request party according to the scheduling parameter of the network server and the network server address obtained by analysis, and the data request party can access the corresponding network server according to the IP address of the distributed network server based on the HTTP protocol to acquire the data required by the data request party.
In an embodiment of the present disclosure, the network server address may be a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the scheduling parameter is a load weight.
In this embodiment, the scheduling module 603, configured to schedule the data request of the data requester according to the feedback packet, may be configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
In this embodiment, in order to perform accurate and refined scheduling on the data requester, first determining a first distribution network server that is first allocated to the data requester and a first scheduling parameter of the first distribution network server, then determining whether data connection of the first distribution network server reaches a full load, if not, allocating an address of the first distribution network server to the data requester until the first distribution network server reaches the full load, then determining a second distribution network server according to the above process, acquiring a second scheduling parameter of the second distribution network server, and allocating the address of the second distribution network server to the data requester according to the second scheduling parameter until the network server carried in the feedback message is allocated. In this way, by means of the load weight, a user-based fine and smooth scheduling of the data request load can be achieved, while also contributing to an enhanced system stability.
For example, if the feedback message includes two network servers, i.e., a network server a and a network server B, where the IP addresses of the network server a are IP _ a1 and IP _ a2, the load weight is 100, the IP addresses of the network server B are IP _ B1 and IP _ B2, and the load weight is 10, the local DNS server may allocate the IP addresses IP _ a1 and IP _ a2 of the network server a to the first 100 data requesters, and allocate the IP addresses IP _ B1 and IP _ B2 of the network server B to the subsequent data requesters, until the full load of the network server B is reached.
In an embodiment of the present disclosure, the allocation order of the network servers may be set according to the needs of practical applications, for example, the allocation order may be set as the generation order of the data requests, that is, the network servers are allocated according to the sequence of the data requests, and of course, other orders may also be adopted, which is not specifically limited by the present disclosure.
In an embodiment of the present disclosure, the feedback message further includes the number of the network server addresses.
In this embodiment, before the scheduling module 603 schedules the data request of the data requester according to the feedback packet, the scheduling module is further configured to:
and analyzing the feedback message according to the number of the network server addresses.
In order to correctly analyze the feedback message to obtain correct and all network server addresses and avoid the situations of loss, quantity loss and the like of network server address information obtained by analysis, the authoritative DNS server also adds the quantity of the network server addresses, the network server addresses and the scheduling parameters of the network servers into the feedback message, that is, the feedback message includes the quantity of the network server addresses in addition to the network server addresses corresponding to the target request domain name information and the scheduling parameters of the network servers. Therefore, after receiving the feedback message sent by the authoritative DNS server, the local DNS server can extract the number of the network server addresses according to the regulation of a preset communication protocol and a preset message format, and further continuously analyze the feedback message according to the number of the network server addresses to finally obtain all the network server addresses and the scheduling parameters of the network server.
In an embodiment of the present disclosure, the apparatus further includes:
and the caching module is configured to cache the data request and the feedback message, and send a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
In this embodiment, the local DNS server has a data caching capability and can cache the received data request and feedback packet, so that when a data request having the same destination request domain name information as the cached data request is received from the data requestor within the effective caching time of the data request and feedback packet, the network server address corresponding to the destination request domain name information of the cached data request can be directly sent to the data requestor without being requested from the authoritative DNS server.
Technical terms and technical features related to the embodiment shown in fig. 6 are the same as or similar to those mentioned in the embodiment shown in fig. 5, and for the corresponding technical terms and technical features, reference may be made to the above explanation and description of the embodiment shown in fig. 6, and the detailed description of the disclosure is omitted here.
Fig. 7 shows a block diagram of a data request load scheduling apparatus according to still another embodiment of the present disclosure, which may be implemented as part or all of an electronic device by software, hardware, or a combination of the two. As shown in fig. 7, the data request load scheduling apparatus includes:
the local DNS server 701 is configured to receive a data request sent by a data requester, send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, receive and analyze a feedback packet sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback packet, where the number of the data requests is one or more, the data request carries the target request domain name information, and the feedback packet includes a network server address corresponding to the target request domain name information and a scheduling parameter of the network server;
an authoritative DNS server 702 configured to receive the data request sent by the local DNS server, obtain a network server address corresponding to the target request domain name information according to the data request, obtain a scheduling parameter of the network server, generate a feedback packet based on the network server address and the scheduling parameter of the network server, and send the feedback packet to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
As mentioned above, with the development of data technology, in order to enable a user to acquire data to be accessed more quickly and accurately, a CDN has come up with, and in order to balance data traffic and load of CDN nodes, scheduling needs to be performed for the CDN. Currently, CDN scheduling is mainly based on DNS server data to achieve traffic load balancing, but since a data request of a user needs to be transmitted to an authoritative server through a Local DNS server, scheduling can only be performed based on a data request generated by the Local DNS server, and user-based scheduling cannot be achieved, so that the CDN scheduling lacks a certain fineness.
In view of the above problem, in this embodiment, a data request load scheduling apparatus is provided, in which an authoritative DNS server sends, to a local DNS server, an obtained network server address corresponding to target request domain name information in a data request forwarded by the local DNS server, and scheduling parameters of the network server, so that the local DNS server can schedule the received data request according to the scheduling parameters of the network server. According to the technical scheme, the scheduling based on the user at the local DNS server is realized by means of the sending of the network server scheduling parameters, so that the scheduling fineness of the CDN can be effectively enhanced, and the efficiency and quality of data request load scheduling are improved.
In this embodiment, the data request load scheduling apparatus may be implemented as a data request load scheduling system including a local DNS server and an authoritative DNS server.
In an embodiment of the present disclosure, before the authoritative DNS server generates a feedback packet based on the address of the network server and the scheduling parameter of the network server, and sends the feedback packet to the local DNS server, the authoritative DNS server is further configured to:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
In an embodiment of the present disclosure, before scheduling the data request of the data requester according to the feedback packet, the local DNS server is further configured to:
and analyzing the feedback message according to the number of the network server addresses.
In an embodiment of the present disclosure, the network server address may be a network server IP address such as a content distribution network node IP address, and the server may include a physical server, or a virtual server based on a virtual machine, a container, or the like, and may further include a server cluster.
In an embodiment of the present disclosure, the scheduling parameter is a load weight.
In this embodiment, the part of the local DNS server that schedules the data request of the data requestor according to the feedback packet is configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
In an embodiment of the present disclosure, the local DNS server is further configured to:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
Technical terms and technical features related to the embodiment shown in fig. 7 are the same as or similar to those mentioned in the embodiment shown in fig. 5 to 6, and for the corresponding technical terms and technical features, reference may be made to the above explanation and description of the embodiment shown in fig. 5 to 6, and the detailed description of the disclosure is omitted here.
The embodiment of the present disclosure also discloses an electronic device, which includes a memory and a processor; wherein,
the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to perform any of the method steps described above.
Fig. 8 is a schematic structural diagram of a computer system suitable for implementing a data request load scheduling method according to an embodiment of the present disclosure.
As shown in fig. 8, the computer system 800 includes a processing unit 801 which can execute various processes in the above-described embodiments according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the system 800 are also stored. The processing unit 801, the ROM802, and the RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary. The processing unit 801 may be implemented as a CPU, a GPU, a TPU, an FPGA, an NPU, or other processing units.
In particular, the above described methods may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a medium readable thereby, the computer program comprising program code for performing the data request load scheduling method. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809 and/or installed from the removable medium 811.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, a program segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present disclosure may be implemented by software or hardware. The units or modules described may also be provided in a processor, and the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.
As another aspect, the disclosed embodiment also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus in the foregoing embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer readable storage medium stores one or more programs for use by one or more processors in performing the methods described in the embodiments of the present disclosure.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept. For example, the above features and (but not limited to) the features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.
Claims (40)
1. A data request load scheduling method comprises the following steps:
receiving data requests sent by a local DNS server, wherein the number of the data requests is one or more, and the data requests carry domain name information of target requests;
acquiring a network server address corresponding to the target request domain name information according to the data request;
and acquiring scheduling parameters of the network server, generating a feedback message based on the address of the network server and the scheduling parameters of the network server, and sending the feedback message to the local DNS server so that the local DNS server schedules the data request according to the scheduling parameters of the network server.
2. The method of claim 1, wherein the data request and feedback messages are sent based on a predetermined command.
3. The method of claim 1, the network server address being a content distribution network node IP address.
4. The method of claim 1, before generating the feedback packet based on the network server address and the scheduling parameter of the network server and sending the feedback packet to the local DNS server, further comprising:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
5. The method of any of claims 1-4, the scheduling parameter is a load weight.
6. A data request load scheduling method comprises the following steps:
receiving data requests sent by a data request party, wherein the number of the data requests is one or more, and the data requests carry domain name information of target requests;
sending the data request to an authoritative DNS server based on a preset command so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
and receiving and analyzing a feedback message sent by the authoritative DNS server, and scheduling the data request of the data request party according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server.
7. The method of claim 6, the scheduling the data request of the data requestor according to the feedback message, implemented as:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
8. The method of claim 6, further comprising a number of the network server addresses in the feedback message.
9. The method of claim 8, before scheduling the data request of the data requestor according to the feedback packet, further comprising:
and analyzing the feedback message according to the number of the network server addresses.
10. The method of claim 6, further comprising:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
11. The method according to any of claims 6-10, wherein the network server address is a content distribution network node IP address.
12. The method according to any of claims 6-10, wherein the scheduling parameter is a load weight.
13. A data request load scheduling method comprises the following steps:
the local DNS server receives a data request sent by a data requester and sends the data request to an authoritative DNS server based on a preset command so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, wherein the number of the data requests is one or more, and the data request carries the target request domain name information;
the authoritative DNS server receives a data request sent by the local DNS server, acquires a network server address corresponding to the target request domain name information according to the data request, acquires a scheduling parameter of the network server, generates a feedback message based on the network server address and the scheduling parameter of the network server, and sends the feedback message to the local DNS server so that the local DNS server schedules the data request according to the scheduling parameter of the network server;
and the local DNS server receives and analyzes a feedback message sent by the authoritative DNS server, and schedules the data request of the data requester according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server.
14. The method of claim 13, wherein before the authoritative DNS server generates a feedback packet based on the network server address and the scheduling parameter of the network server and sends the feedback packet to the local DNS server, the method further comprises:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
15. The method of claim 14, wherein the local DNS server, prior to scheduling the data request of the data requestor according to the feedback packet, further comprises:
and analyzing the feedback message according to the number of the network server addresses.
16. The method of claim 13, wherein the local DNS server schedules the data request of the data requestor according to the feedback packet, and is implemented to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
17. The method of claim 13, further comprising:
and the local DNS server caches the data request and the feedback message, and sends a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
18. The method according to any of claims 13-17, wherein the network server address is a content distribution network node IP address.
19. The method according to any of claims 13-17, wherein the scheduling parameter is a load weight.
20. A data request load scheduling apparatus, comprising:
the system comprises a first receiving module, a second receiving module and a third receiving module, wherein the first receiving module is configured to receive data requests sent by a local DNS server, the number of the data requests is one or more, and the data requests carry domain name information of target requests;
the acquisition module is configured to acquire a network server address corresponding to the target request domain name information according to the data request;
and the generating module is configured to acquire the scheduling parameter of the network server, generate a feedback message based on the address of the network server and the scheduling parameter of the network server, and send the feedback message to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
21. The apparatus of claim 20, wherein the data request and feedback messages are sent based on a predetermined command.
22. The apparatus of claim 20, the network server address is a content distribution network node IP address.
23. The apparatus of claim 20, the generation module, prior to generating a feedback message to send to the local DNS server based on the network server address and the scheduling parameter of the network server, is further configured to:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
24. The apparatus of any of claims 20-23, the scheduling parameter is a load weight.
25. A data request load scheduling apparatus, comprising:
the second receiving module is configured to receive one or more data requests sent by a data requesting party, wherein the data requests carry domain name information of a target request;
the sending module is configured to send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request;
and the scheduling module is configured to receive and analyze a feedback message sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback message, wherein the feedback message comprises a network server address corresponding to the target request domain name information and a scheduling parameter of the network server.
26. The apparatus of claim 25, the portion of the scheduling module that schedules the data request of the data requestor according to the feedback packet configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
27. The apparatus of claim 25, the feedback message further comprising a number of the network server addresses.
28. The apparatus of claim 27, the scheduling module, prior to scheduling the data request of the data requestor according to the feedback message, is further configured to:
and analyzing the feedback message according to the number of the network server addresses.
29. The apparatus of claim 25, further comprising:
and the caching module is configured to cache the data request and the feedback message, and send a cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
30. The apparatus according to any of claims 25-29, wherein the network server address is a content distribution network node IP address.
31. The apparatus of any of claims 25-29, the scheduling parameter is a load weight.
32. A data request load scheduling apparatus, comprising:
the local DNS server is configured to receive a data request sent by a data requester, send the data request to an authoritative DNS server based on a preset command, so that the authoritative DNS server obtains a network server address corresponding to the target request domain name information according to the data request, receive and analyze a feedback message sent by the authoritative DNS server, and schedule the data request of the data requester according to the feedback message, wherein the number of the data requests is one or more, the data request carries the target request domain name information, and the feedback message comprises a network server address corresponding to the target request domain name information and scheduling parameters of the network server;
and the authoritative DNS server is configured to receive the data request sent by the local DNS server, acquire a network server address corresponding to the domain name information of the target request according to the data request, acquire a scheduling parameter of the network server, generate a feedback message based on the network server address and the scheduling parameter of the network server, and send the feedback message to the local DNS server, so that the local DNS server schedules the data request according to the scheduling parameter of the network server.
33. The apparatus of claim 32, before the authoritative DNS server generating a feedback message based on the network server address and the network server's scheduling parameters to send to the local DNS server, further configured to:
determining the number of the obtained network server addresses;
the generating of the feedback message based on the network server address and the scheduling parameter of the network server to the local DNS server is implemented as:
and generating feedback messages based on the network server addresses, the scheduling parameters of the network servers and the number of the network server addresses, and sending the feedback messages to the local DNS server so that the local DNS server analyzes the feedback messages according to the number of the network server addresses.
34. The apparatus of claim 33, the local DNS server, prior to scheduling the data request of the data requestor according to the feedback message, is further configured to:
and analyzing the feedback message according to the number of the network server addresses.
35. The apparatus of claim 32, the portion of the local DNS server that schedules data requests of the data requestor according to the feedback packet configured to:
determining a first distribution network server, and acquiring a first scheduling parameter of the first distribution network server;
allocating the first distribution network server address to the data requestor according to the first scheduling parameter;
when the first distribution network server reaches full load, determining a second distribution network server, and acquiring a second scheduling parameter of the second distribution network server;
and allocating the address of the second allocated network server to the data request party according to the second scheduling parameter until the network server in the feedback message is allocated.
36. The apparatus of claim 32, the local DNS server further configured to:
and caching the data request and the feedback message, and sending the cached network server address corresponding to the target request domain name information of the cached data request to the data requester when receiving the data request which is sent by the data requester and has the same target request domain name information as the cached data request within the effective caching time.
37. The apparatus of any of claims 32-36, wherein the network server address is a content distribution network node IP address.
38. The apparatus of any of claims 32-36, the scheduling parameter is a load weight.
39. An electronic device comprising a memory and a processor; wherein,
the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps of any of claims 1-19.
40. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the method steps of any of claims 1-19.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010340864.3A CN113301074A (en) | 2020-04-26 | 2020-04-26 | Data request load scheduling method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010340864.3A CN113301074A (en) | 2020-04-26 | 2020-04-26 | Data request load scheduling method and device, electronic equipment and readable storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN113301074A true CN113301074A (en) | 2021-08-24 |
Family
ID=77317973
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010340864.3A Pending CN113301074A (en) | 2020-04-26 | 2020-04-26 | Data request load scheduling method and device, electronic equipment and readable storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113301074A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023087820A1 (en) * | 2021-11-18 | 2023-05-25 | 中兴通讯股份有限公司 | Load balancing method and device, and computer-readable storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104954401A (en) * | 2014-03-27 | 2015-09-30 | 阿里巴巴集团控股有限公司 | Flow scheduling method and apparatus |
US20150358276A1 (en) * | 2014-05-28 | 2015-12-10 | International Business Machines Corporation | Method, apparatus and system for resolving domain names in network |
CN108011994A (en) * | 2017-12-15 | 2018-05-08 | 网宿科技股份有限公司 | A kind of method and system of inquiry DNS records |
CN109391703A (en) * | 2017-08-10 | 2019-02-26 | 阿里巴巴集团控股有限公司 | Domain name analytic method, device, equipment and computer storage medium |
CN109547517A (en) * | 2017-09-22 | 2019-03-29 | 贵州白山云科技股份有限公司 | A kind of bandwidth scheduling method and apparatus |
-
2020
- 2020-04-26 CN CN202010340864.3A patent/CN113301074A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104954401A (en) * | 2014-03-27 | 2015-09-30 | 阿里巴巴集团控股有限公司 | Flow scheduling method and apparatus |
US20150358276A1 (en) * | 2014-05-28 | 2015-12-10 | International Business Machines Corporation | Method, apparatus and system for resolving domain names in network |
CN109391703A (en) * | 2017-08-10 | 2019-02-26 | 阿里巴巴集团控股有限公司 | Domain name analytic method, device, equipment and computer storage medium |
CN109547517A (en) * | 2017-09-22 | 2019-03-29 | 贵州白山云科技股份有限公司 | A kind of bandwidth scheduling method and apparatus |
CN108011994A (en) * | 2017-12-15 | 2018-05-08 | 网宿科技股份有限公司 | A kind of method and system of inquiry DNS records |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023087820A1 (en) * | 2021-11-18 | 2023-05-25 | 中兴通讯股份有限公司 | Load balancing method and device, and computer-readable storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11811657B2 (en) | Updating routing information based on client location | |
EP3567881B1 (en) | Request routing and updating routing information utilizing client location information | |
US9608957B2 (en) | Request routing using network computing components | |
JP4753052B2 (en) | Content delivery method and system | |
AU2011307319B2 (en) | Request routing in a networked environment | |
US8458733B2 (en) | Global API deployment and routing | |
CN110430274A (en) | A kind of document down loading method and system based on cloud storage | |
CN102047243A (en) | Request routing based on class | |
CN102067094A (en) | Cache optimzation | |
RU2012118601A (en) | SYSTEM AND METHOD FOR PROVIDING MORE FAST AND MORE EFFECTIVE DATA TRANSFER | |
CN109067936A (en) | A kind of method and device of domain name mapping | |
EP3419249A1 (en) | Methods of optimizing traffic in an isp network | |
CN110401731B (en) | Method and apparatus for distributing content distribution nodes | |
CN111541799A (en) | Domain name resolution method, system, terminal and storage medium | |
CN109471713B (en) | Method and device for inquiring information | |
CN113301074A (en) | Data request load scheduling method and device, electronic equipment and readable storage medium | |
CN110602264B (en) | Method, apparatus, device and medium for transferring domain name resolution address weight information | |
CN110995827B (en) | Communication processing method and device, computer readable medium and electronic equipment | |
EP3304865B1 (en) | Systems and methods for server failover and load balancing | |
CN116248632B (en) | File acquisition method, device, system and equipment, medium and product | |
CN109302505B (en) | Data transmission method, system, device and storage medium | |
CN115086425B (en) | Message transmission method, device, program product, medium and electronic equipment | |
CN110913027B (en) | Domain name resolution method and device | |
CN116112467A (en) | Message processing system, method, device and equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40059169 Country of ref document: HK |
|
RJ01 | Rejection of invention patent application after publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210824 |