CN112583952B

CN112583952B - Redirection scheduling processing method, device and system, related equipment and storage medium

Info

Publication number: CN112583952B
Application number: CN202011448229.3A
Authority: CN
Inventors: 刘贵荣
Original assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Current assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Priority date: 2020-12-09
Filing date: 2020-12-09
Publication date: 2023-01-24
Anticipated expiration: 2040-12-09
Also published as: CN112583952A

Abstract

According to the redirection scheduling processing method, the redirection scheduling processing device, the redirection scheduling processing system, the related equipment and the storage medium, aiming at the resource request of a requester, under the condition that the resource request is at least a first version type IP request, the scheduler can realize the redirection of the resource request of a user by acquiring a target redirection domain name which can be at least used for supporting the resolution of a double version type IP address (namely, the redirection domain name can be at least resolved into a first version type IP address and a second version type IP address), and can correspondingly support the requester such as a client to access the resource by using a double-protocol stack mode, so that the first version type IP (such as IPv 6) network environment is poor, the resource request can be switched to a second version type IP (such as IPv 4) network environment for resource acquisition, and when the redirection scheduling technology of the scheme is applied to the support of IPv6 and other networks, the flexibility of the support of IPv6 can be obviously improved, and the service capability of a resource service provider such as CDN and the like is further improved.

Description

Redirection scheduling processing method, device and system, related equipment and storage medium

Technical Field

The present application belongs to the field of communications technologies, and in particular, to a method, an apparatus, a system, related devices, and a storage medium for redirection scheduling processing.

Background

A CDN (Content Delivery Network) is a Content Delivery Network constructed on a Network, and by means of edge servers deployed in various places and through functions of load balancing, content Delivery, scheduling, and the like of a central platform, a user can obtain required Content nearby, network congestion is reduced, and the access response speed of the user is increased.

The CDN scheduling system is configured to schedule an access request of a user to a CDN edge node according to a certain scheduling rule, and generally includes two scheduling manners: domain Name System (DNS) scheduling and Hypertext Transfer Protocol (HTTP) scheduling.

The HTTP scheduling is also called as HTTP302 scheduling or HTTP302 redirection scheduling, has the advantages of high accuracy, good flexibility, quick effect taking, difficult hijacking and the like, and is more suitable for resource scheduling of large files, video files and the like. The HTTP scheduling is mature in an IPv4 (Internet Protocol version 4, fourth edition of Internet communication Protocol) environment, and can well support an IPv4 network, and with the continuous development of IPv6 (Internet Protocol version 6, sixth edition of Internet communication Protocol), the IPv6 network is increasingly mature, and it is necessary to use the HTTP scheduling in the IPv6 environment, and the HTTP scheduling system correspondingly needs to support the IPv6 environment, however, the existing HTTP scheduling technology is not flexible enough to support the IPv6 environment, and affects the service capability of resource servers such as the CDN to the user.

Disclosure of Invention

In view of this, the present application provides a redirection scheduling processing method, apparatus, system, related device, and storage medium, which improve the flexibility of the redirection scheduling technology in supporting IPv6 and improve the service capability of resource service parties such as CDN.

The specific technical scheme is as follows:

a redirection scheduling processing method is applied to a scheduling party;

the method comprises the following steps:

acquiring a resource request of a requester;

determining a target IP address of a target device for providing resource service for the resource request;

under the condition that the resource request is at least a first version type IP request, acquiring a target redirection domain name corresponding to the target IP address;

feeding back response information including the target redirection domain name to a requester;

wherein, the redirection domain name corresponds to: a resolution rule usable at least to resolve the redirected domain name into a first version type IP address and a second version type IP address.

Optionally, the obtaining a target redirection domain name corresponding to the target IP address under the condition that the resource request is at least a first version type IP request includes:

under the condition that the resource request is an IPv6 request, acquiring a target redirection domain name corresponding to the IPv6 address of the target device;

or,

and under the condition that the resource request is an IPv6 request and is a hypertext transfer security protocol (https) request, acquiring a target redirection domain name corresponding to the IPv6 address of the target device.

Optionally, the target redirection domain name is obtained by processing the target IP address and a pre-applied redirection domain name;

the processing procedure for obtaining the target redirection domain name based on the processing of the target IP address and the pre-applied redirection generic domain name comprises the following steps:

converting the IPv6 address of the target device into a domain name prefix;

and assembling the domain name prefix and the redirection domain name to obtain the target redirection domain name corresponding to the IPv6 address of the target equipment.

Optionally, redirecting the resolution rule of the domain name corresponding to the domain name service side includes:

analyzing the redirection domain name into a corresponding IPv6 address according to a first analysis record which is added for the pre-association of the redirection domain name and comprises the IPv6 address;

and resolving the redirection domain name into a corresponding IPv4 address according to a second resolution record which is added for the pre-association of the redirection domain name and comprises the IPv4 address.

Optionally, before the obtaining the target redirection domain name corresponding to the target IP address, the method further includes:

and if the currently used redirection domain name of the dispatcher is unavailable, selecting an available redirection domain name from a plurality of redirection domain names which are applied by the dispatcher in advance, and triggering the step of acquiring the target redirection domain name corresponding to the target IP address, so that the acquired target redirection domain name is obtained by processing the target IP address and the selected redirection domain name.

A redirection scheduling processing method is applied to a domain name service party;

the method comprises the following steps:

acquiring a first analysis request carrying a target redirection domain name of a requester;

analyzing the target redirection domain name according to an analysis rule to obtain a target version type IP address consistent with the request type of the first analysis request; the analysis rule can be at least used for analyzing the redirection domain name into a first version type IP address and a second version type IP address;

and feeding back response information comprising the target version type IP address to a requester.

Optionally, the domain name service side pre-stores, for each redirection domain name in the redirection domain name set, a first resolution record including an IPv6 address and a second resolution record including an IPv4 address, which are added in association with the redirection domain name.

Optionally, the request type of the first parsing request is a type for requesting an IPv6 address;

the analyzing the target redirection domain name according to the analysis rule to obtain a target version type IP address consistent with the request type of the first analysis request comprises the following steps:

and resolving the target redirection domain name into a corresponding IPv6 address according to a first resolution record added for the target redirection domain name in a pre-association manner.

Optionally, after feeding back the response information including the target version type IP address to the requester, the method further includes:

acquiring a second resolution request carrying the target redirection domain name from a requester; and analyzing the target redirection domain name according to the analysis rule to obtain a target version type IP address consistent with the request type of the second analysis request, and feeding back response information including the target version type IP address consistent with the request type of the second analysis request to a requester.

Optionally, the request type of the second resolution request is a type for requesting an IPv4 address;

the analyzing the target redirection domain name according to the analysis rule to obtain a target version type IP address consistent with the request type of the second analysis request comprises:

and resolving the target redirection domain name into a corresponding IPv4 address according to a second resolution record added for the target redirection domain name in a pre-association manner.

A redirection scheduling processing device is applied to a scheduling party;

the device comprises:

a first obtaining unit, configured to obtain a resource request of a requester;

a determining unit, configured to determine a target IP address of a target device for providing a resource service for the resource request;

a second obtaining unit, configured to obtain a target redirection domain name corresponding to the target IP address when the resource request is at least a first version type IP request;

a first feedback unit, configured to feed back response information including the target redirection domain name to a requester;

A redirection scheduling processing device is applied to a domain name service side;

the device comprises:

a third obtaining unit, configured to obtain a first resolution request carrying a target redirection domain name from a requester;

the analysis unit is used for analyzing the target redirection domain name according to an analysis rule to obtain a target version type IP address consistent with the request type of the first analysis request; the analysis rule can be at least used for analyzing the redirection domain name into a first version type IP address and a second version type IP address;

and the second feedback unit is used for feeding back response information comprising the target version type IP address to the requester.

A scheduling apparatus, comprising:

a first memory for storing a first set of computer instructions;

the first processor is used for realizing the redirection scheduling processing method applied to the scheduling party by executing the instruction set stored on the first memory.

A domain name service apparatus, comprising:

a second memory for storing a second set of computer instructions;

and the second processor is used for implementing the redirection scheduling processing method applied to the domain name service party by executing the instruction set stored on the second memory.

A computer readable storage medium having stored therein a first set of computer instructions which, when executed by a processor, implement a redirection scheduling processing method as applied to a scheduler as described in any of the above.

A computer readable storage medium having stored therein a second set of computer instructions which, when executed by a processor, implement a redirection scheduling processing method as applied to a domain name service as claimed in any one of the preceding claims.

A redirection scheduling processing system comprises a request party, a domain name service party and a scheduling party;

wherein:

the requester can be used for initiating a resource request to the dispatcher through the domain name service party;

the dispatcher is used for realizing the redirection of the resource request of the requester by executing the redirection dispatching processing method applied to the dispatcher;

the domain name service side is configured to implement provision of the domain name service for the requesting side by executing the redirection scheduling processing method applied to the domain name service side as described in any one of the above.

According to the redirection scheduling processing method, device, system, related equipment and storage medium disclosed by the embodiment of the application, aiming at the resource request of a requester, under the condition that the resource request is at least a first version type IP request, the scheduler can realize redirection of the resource request of a user by acquiring a target redirection domain name which can be used for supporting at least double version type IP address resolution (namely, the redirection domain name can be at least resolved into a first version type IP address and a second version type IP address) for the requester, and correspondingly, the requester such as a client can be supported to access resources by using a double-protocol stack mode, so that when the network environment of the first version type IP (such as IPv 6) is poor, the resource request can be switched to the network environment based on the second version type IP (such as IPv 4) for resource acquisition, when the redirection scheduling technology of the scheme of the application is applied to support of networks such as IPv6, the flexibility of support of IPv6 can be obviously improved, and the service capability of resource service parties such as CDN (CDN) can be further improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a schematic illustration of HTTP redirection scheduling;

fig. 2 is a schematic flowchart of a redirection scheduling processing method applied to a scheduler according to an embodiment of the present application;

fig. 3 is a system framework diagram of a CDN scheduling system provided in an embodiment of the present application;

fig. 4 is another schematic flowchart of a redirection scheduling processing method applied to a scheduler according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a redirection scheduling processing method applied to a domain name service provider according to an embodiment of the present application;

fig. 6 is a schematic diagram of different domain name information systems corresponding to different domain names according to an embodiment of the present application;

fig. 7 is another schematic flowchart of a redirection scheduling processing method applied to a domain name service provider according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a redirection scheduling processing apparatus applied to a scheduler according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another redirection scheduling processing apparatus applied to a scheduler according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a redirection scheduling processing apparatus applied to a domain name service provider according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a domain name service device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

A CDN scheduling system, that is, a Global Server Load Balance (GSLB) scheduling system of the CDN, is configured to schedule an access request of a client to a CDN edge node according to a certain scheduling rule, and there are two scheduling manners: domain name system DNS scheduling and HTTP scheduling. The HTTP schedule is also referred to as HTTP302 schedule or HTTP302 redirect schedule, and the present application focuses on further improvements to existing HTTP schedule redirection scheduling techniques.

Referring to fig. 1, the principle of HTTP scheduling is that a client first accesses to an HTTP scheduling system through a DNS system, the HTTP scheduling system preferentially selects an edge server in a CDN according to a policy to provide a resource service to the client, assembles an HTTP response header according to an IP address of the selected edge server, such as assembling Location of the HTTP response header according to an IPv4 address (client request is based on an IPv4 environment) or an IPv6 address (client request is based on an IPv6 environment) of the selected server, and returns response information to the client by using a state code 302, thereby redirecting a client request. Then, the client may initiate a link to a corresponding server (i.e., an edge server selected by the scheduling system) for resource acquisition based on the received response information.

The inventor finds that the existing HTTP scheduling technology is not flexible enough to support IPv6, and affects the service capability of resource service parties such as CDN and the like to users. For example, the rule for converting IPv6 address into domain name in the prior art is not flexible enough; only the IPv6 condition is supported, and how to quickly switch to the IPv4 environment to acquire resources when the IPv6 network environment is poor is not considered; no quick solutions are considered if a single domain name is unavailable due to resolution failure or extreme conditions such as being blocked, etc.

In order to at least partially solve the technical defects, the application discloses a redirection scheduling processing method, a redirection scheduling processing device, a redirection scheduling processing system, related equipment and a storage medium, and the service capability of a resource server such as a CDN is further improved by improving the flexibility of the redirection scheduling technology in supporting IPv6.

Referring to fig. 2, a schematic flow chart of a redirection scheduling processing method applied to a scheduling party according to an embodiment of the present application is provided, optionally, the scheduling party may be a scheduling system of a content service provider such as a CDN, and the scheduling system includes at least one server for executing redirection scheduling service, and the method may be specifically applied to one or more servers included in the CDN scheduling system.

As shown in fig. 2, the redirection scheduling processing method applied to the scheduler in this embodiment may include:

step 201, obtaining a resource request of a requester.

The requesting party may be a client on a smartphone, a tablet Computer, a Personal PC (Personal Computer), or the like, such as a web browser, a mail client, various installed applications, and the like on the above-described devices.

When a requester needs to acquire resources from a network, the requester firstly accesses a scheduling system of a scheduler through a DNS system, and the scheduler correspondingly acquires a resource request of the requester. Optionally, the resource request of the requester may specifically be a content request facing the CDN, and carries information such as an IP address of the requester, a request type (such as http, https), and a resource identifier of the requested resource, in implementation, the resource request of the requester may carry the request type and the resource identifier of the requested resource based on a URL (uniform resource locator) address of the requested resource, and the scheduler obtains the information by performing an analysis operation on the resource request.

Referring to the architecture diagram of the scheduling system shown in fig. 3, the scheduling system of the scheduling party may be implemented in the form of a central controller (central Master) and multiple edge nodes (edge servers), where the central controller is used for configuring, updating, and storing scheduling rules, and providing an API (Application Programming Interface) facing each edge node/edge server, and each edge node/edge server performs rule synchronization from the central controller based on the API Interface, and responds to a resource request of a requesting party according to the rules, so as to implement redirection of a resource request of the requesting party.

It should be noted that, an edge node (edge server) in the scheduling system is different from an edge node (edge server) in the CDN network, the former is used to provide a redirection scheduling service for a resource request of a requester in the scheduling system, so as to redirect the resource request to a corresponding edge server in the CDN, and the latter is used to provide a content service for the resource request of the requester, and the scheduling edge node/edge server and the CDN edge node/edge server are used to distinguish between them.

The scheduling rules may include, but are not limited to:

determining which CDN edge server should be employed to provide the content service based on a scheduling policy;

which generic domain name should be used for the determination of the redirect domain name (as to the generic domain name, it will be set forth below).

Further, the scheduling policy may include, but is not limited to, scheduling the resource request of the requester to the corresponding CDN edge server based on any one or more of a nearby scheduling principle, a quality-first principle (preferably using CDN edge nodes/edge servers with high quality of service), a cost-first principle (preferably using CDN edge nodes/edge servers with low cost of service), and the like.

The method comprises the steps that a requester accesses a certain scheduling edge server in a scheduling system through a DNS (domain name system), optionally, the DNS can also access the requester to a certain scheduling edge server in the scheduling system based on any one or more of a nearby scheduling principle, a quality priority principle (a scheduling edge node/edge server with high service quality is preferentially adopted), a cost priority principle (a scheduling edge node/edge server with low service cost is preferentially adopted), and the like, on the basis, the requester directly interacts with the accessed scheduling edge server, the scheduling edge server correspondingly receives a resource request of the requester and analyzes the resource request to obtain information such as an IP (such as an IPv4 or IPv6 address), a request type (such as http and https) of the requester, a resource identifier of a requested resource, and the like.

Step 202, determining a target IP address of a target device for providing resource service for the resource request.

Thereafter, the scheduler further determines a target IP address of a target device for providing resource services for the resource request of the requester based on the scheduling rule.

For the system architecture of the scheduling party shown in fig. 3, specifically, the scheduling edge server that receives the resource request of the requesting party further selects, based on the scheduling rule of the central synchronization, a corresponding CDN edge server from the CDN network as a target device for providing resource service to the requesting party, and correspondingly obtains a corresponding IP address as a target IP address, where the target IP address is consistent with the version type of the internet communication protocol IP on which the resource request of the requesting party is based.

In the embodiment of the present application, for each unit (e.g., one CDN edge server or a plurality of CDN edge servers sharing an IP address) corresponding to one IP address in the CDN edge node, at least two version-type IP addresses are configured in advance for the unit, illustratively, at least one IPv4 address and one IPv6 address are configured for the unit.

On this basis, if the IP address of the requester is an IPv6 protocol version type, the scheduler correspondingly obtains the IPv6 address of a target device (such as a CDN edge server) as a target IP address after determining the target device that is used to provide resource service for the resource request; similarly, if the IP address of the requester is the IPv4 protocol version type, the dispatcher correspondingly obtains the IPv4 address of the target device as the target IP address.

Step 203, under the condition that the resource request is at least a first version type IP request, acquiring a target redirection domain name corresponding to the target IP address.

The application focuses on further improvements in the support of IPv6 with respect to the existing HTTP redirection scheduling technology. By designing a conversion rule between the IPv6 address and the domain name, and adding a first analysis record comprising the IPv6 address and a second analysis record comprising the IPv4 address for domain name association, a requester is supported to access resources in a dual-protocol stack mode, and the resource acquisition can be flexibly switched to an IPv4 environment when the IPv6 network environment is poor.

In view of this, in this embodiment, preferably, the first version type IP is IPv6.

When the resource request of the requester is at least an IPv6 request (i.e., a request initiated based on an IPv6 network environment), the dispatcher acquires a target redirection domain name corresponding to the determined target IP address, and responds (302 response) to the requester in the form of a domain name for redirection of the resource request of the requester.

In an optional implementation manner, when the resource request of the requester is an IPv6 request, the scheduler acquires a domain name corresponding to an IPv6 address of a target device for providing a resource service to the requester, and uses the domain name as a target redirection domain name.

Typically, the HTTPs request relates to a problem of a domain name certificate (a requestor needs to verify whether a domain name of a dispatcher is legal according to a domain name certificate of the dispatcher), and therefore, the HTTP302 redirects the dispatch, and when responding to a requestor initiating the HTTPs request, a response in a domain name form must be returned, and in view of this, in implementation, a response (302 response) in a domain name form may be adopted in combination with a need to pertinently only to the HTTPs request in an IPv6 environment, and therefore, in another optional implementation, the dispatcher acquires, as a target redirection domain name, a domain name corresponding to an IPv6 address of a target device for providing a resource service to the requestor in a case where a resource request of the requestor is an IPv6 request and is an HTTPs request.

Aiming at the domain name form response requirement of an IPv6 request or an https request under an IPv6 environment, the embodiment of the application pre-formulates a conversion rule between an IPv6 address and a domain name, so that the domain name form response information can be successfully assembled according to the determined IPv6 address of target equipment (such as a certain CDN edge server).

The core idea of the conversion rule is that an IP address is converted into a unique domain name prefix according to the uniqueness of the IPv6 address, and the mapping from the IPv6 address to a domain name (redirection domain name) is realized by performing domain name assembly according to the domain name prefix obtained by conversion.

Under the core idea, the process of converting the IPv6 address into the domain name based on the conversion rule is as follows:

1) Converting the IPv6 address into a domain name prefix;

the IPv6 address has the length of 128 bits (bit), and the standard format is that the 128-bit is divided into one segment according to 16 bits, each segment is converted into hexadecimal numbers, and the hexadecimal numbers are used for separating the segments by colons. A double colon compression, a formal compression format, may be employed for consecutive digital 0 s between different colons.

For example, the compression format IPv6 address 1234.

Wherein, for IPv6 address with standard format, it can be directly converted into domain name prefix. For the IPv6 address in the compressed format, for convenience of management, the IPv6 address may be first expanded into the standard format, and then converted into the domain name prefix according to the standard format, but the present invention is not limited thereto, and the domain name prefix may also be directly converted according to the compressed format.

For IPv6 in standard or compressed format, the present embodiment provides the following two alternatives to implement the conversion between IP address and domain name prefix:

a. replacing colon numbers in the IPv6 addresses with characters supported by domain names but excluding characters supported by IPv6 addresses to generate domain name prefixes:

considering that the domain name specification requires that no colon exists in the domain name, in this embodiment, the characters supported by the domain name are used to replace the colon in the IPv6 address, in order to avoid confusion between new characters after the colon is replaced and original characters in the IPv6 address, which results in unrecognizable IPv6 address or low recognition degree, when the characters supported by the domain name are used to replace the colon in the IPv6 address, a character set obtained after removing the characters supported by the IPv6 address from the characters supported by the domain name is specifically used as a selection space for replacing the characters of the colon in the IPv6 address, and the characters supported by the IPv6 address include numbers 0 to 9 and letters a to f, so the selection space specifically may be: the set of characters resulting from removing the numbers 0 to 9 and the letters a to f from the characters supported by the domain name, such as the characters g to z, and the character "-", may be included.

By way of example:

for an IPv6 address 1234. In implementation, the characters of the IPv6 address 1234.

For another example, a middle horizontal line is used to replace a colon therein, so that a domain name prefix 1234-5678-90 ab-0-0-0-cdef can be obtained, and for the IPv6 address in a compressed format, a middle horizontal line is used to replace a colon, so that 1234-5678-90 ab-cdef can be correspondingly obtained. The middle transverse line is used for replacing the information, and the information can be hidden to a certain degree by replacing the middle transverse line with other letters.

b. Converting the IPv6 address by adopting a Hash algorithm to obtain a domain name prefix;

specifically, a hash Algorithm, such as MD5 (Message Digest Algorithm 5) or the like, may be used to convert the IPv6 address expanded into the standard format to generate a domain name prefix, and the prefix 55ec44c73c13d7b5345b34bb 736452 is specifically generated after MD5 operation, taking the following ratio of 1234. In implementation, the hash process may be directly performed on the IPv6 address in the compressed format, which is not limited in this embodiment.

2) And assembling the domain name prefix and the pre-generated redirected extensive domain name to obtain the domain name.

Com, and at the same time, the CDN content provider may also apply for a generic domain name https certificate in advance, so as to support domain name verification in https service.

The domain name prefix in the xxx.com can be replaced by a domain name prefix obtained by converting any IPv6 address in the CDN, the domain name prefix is replaced by the domain name prefix in the extensive domain name, the assembly of the domain name prefix and the redirection extensive domain name is realized, and the domain name (domain name prefix + redirection extensive domain name) corresponding to the IPv6 address is obtained and serves as the redirection domain name in the redirection scheduling.

For example, the domain name prefix 1234g5678g90abg0g0g0g0 gcref is assembled with the domain name xxx.com to obtain the domain name 1234g5678g90abg0g0g0g0g0g0gcdef.xxx.com.

By using the conversion rule, the IPv6 address can be quickly converted into the unique domain name, and the redirection scheduling technology can uniquely position the requester to the IPv6 address of the corresponding edge server through the domain name (redirection domain name) correspondingly based on the conversion rule.

In order to improve the flexibility of the IPv6 support by the redirection scheduling technology, in addition to the above conversion rule, in the embodiment of the present application, on the basis of obtaining a domain name corresponding to each IPv6 address in the CDN based on the conversion rule, a first resolution record carrying an IPv6 address and a second resolution record carrying an IPv4 address are further added in association for each domain name corresponding to each IPv6 address in the CDN, and a domain name resolution rule matching the domain name information structure is designed.

The IPv6 address carried in the first analysis record added for a certain domain name association is an IPv6 address used when the domain name is generated based on the conversion rule, and the IPv4 address carried in the second analysis record added for the domain name association is an IPv4 address actually corresponding to a device (e.g., an edge server) to which the IPv6 address used when the domain name is generated points.

In practical application, an AAAA record and an a record may be specifically added to each domain name, where the AAAA record carries an IPv6 address corresponding to the domain name, the a record carries an IPv4 address corresponding to the domain name, and the IPv6 address carried in the AAAA record may be in a standard format or a compressed format.

For example, assuming that a CDN edge server N1 has an IPv4 address of 1.1.1.1, an IPv6 address of 1234 5678: 1234g5678g90abg0g0g0g0gcdef.xxx.com aaaa1234;

the added a records may be: 1234g5678g90abg0g0g0g0g0gcdef. Xxx. Com A1.1.1.1.

In the implementation, the domain name generated based on the IPv6 address and the first and second resolution records added for each domain name can be stored in a DNS system, such as a DNS system of a CDN provider, and a domain name resolution rule for the stored information is configured in the DNS system, so that based on the stored information, a redirection domain name fed back to a requester by a dispatcher can be resolved into an IPv6 address and an IPv4 address, a client is supported to access resources in a dual-protocol (IPv 4, IPv 6) stack manner, and the client is supported to perform flexible switching between different protocol stacks according to requirements, accordingly, the flexibility of supporting IPv6 by the redirection scheduling technology can be improved, and when the quality of an IPv6 environment is poor, the client can be flexibly switched to the IPv4 environment to perform resource acquisition.

The above processing correspondingly enables the redirection domain name to correspond to a resolution rule at least capable of resolving the redirection domain name into a first version type IP address (such as an IPv6 address) and a second version type IP address (such as an IPv4 address) on the domain name service side. The parsing rule may specifically include:

It should be noted that the above two kinds of resolution records added for the domain name association corresponding to each IPv6 address in the CDN, and the design of the domain name resolution rule based on this are merely exemplary and non-limiting illustrations of the embodiment of the present application, and other variant implementation manners may also be used in practical applications, for example, for the domain name corresponding to each IPv6 address in the CDN, only one resolution record (e.g., a record) carrying an IPv4 address is added for each domain name association, and when a domain name is resolved, the domain name can be resolved into the corresponding IPv4 address according to the record added in association, and in addition, since the domain name is obtained by converting the IPv6 address using the conversion rule, when domain name resolution is performed, the IPv6 address corresponding to the domain name can also be obtained based on a matched inverse conversion process, and it can also be supported that the domain name is resolved into IP addresses of different versions, so that the purpose of improving the flexibility supported by the redirection scheduling technology for IPv6 is also achieved.

In this step 203, when acquiring the target redirection domain name corresponding to the target IP address (i.e., the IP address of the target device for providing the content service for the requester), optionally, a conversion operation may be temporarily performed based on the above-mentioned conversion rule to convert the target IP address (IPv 6 address) into the domain name. Or, optionally, each IPv6 address in the CDN network may be converted into a domain name form in advance, and on this basis, after the scheduler determines, based on the scheduling rule, the IPv6 address of the target device for providing the content service to the requester, the domain name corresponding to the IPv6 address may be obtained directly by a query means and used as the target redirection domain name.

And step 204, feeding back response information comprising the target redirection domain name to the requester.

Then, the dispatcher further assembles the Location of the HTTP response head according to the target redirection domain name to obtain response information carrying the target redirection domain name, such as HTTPs:// 1234g5678g90abg0g0g0g0gcdef.yy.com/abc.user.com/aa.jpg, and returns the response information to the requester, and then the requester can realize redirection of the resource request according to the redirection domain name in the obtained response information, initiate connection to the redirected CDN edge server, and obtain the resource.

Because the DNS system stores a first analysis record carrying the IPv6 address and a second analysis record carrying the IPv4 address in association with the domain name, and supports dual-protocol stack domain name analysis, when the IPv6 network condition is poor and the service quality is poor, a requester can flexibly switch to the IPv4 network to initiate connection to a corresponding CDN edge server based on the IPv4 address obtained by DNS analysis, so as to acquire resources.

It is easily understood that the IPv6 address and the IPv4 address are only exemplary illustrations of at least two version types of IP addresses in the embodiments of the present application, and as the internet communication protocol evolves, other version types of IP addresses are not excluded, and the present application is also applicable to the technical idea of the solution of the present application to achieve similar purposes, which is within the protection scope of the present application. In addition, in practical application, the purpose of flexibly switching between IPv4 and IPv6 networks can also be achieved by designing a conversion rule between the IPv4 address and the domain name and adding two analysis records carrying the IPv4 address and the IPv6 address for the domain name, which is not limited in this embodiment.

According to the redirection scheduling processing method, device and system, the related equipment and the storage medium disclosed by the embodiment of the application, aiming at the resource request of a requester, under the condition that the resource request is at least a first version type IP request, the scheduler can realize the redirection of the resource request of a user by acquiring a target redirection domain name which can be used for supporting the resolution of a double version type IP address (namely, the redirection domain name can be at least resolved into the first version type IP address and a second version type IP address), and correspondingly can support the requester such as a client to access the resource by using a double-protocol stack mode, so that the resource request can be switched to a network environment based on a second version type IP (such as IPv 4) to acquire the resource when the network environment of the first version type IP (such as IPv 6) is poor, and when the redirection scheduling technology of the scheme of the application is applied to the support of networks such as IPv6, the flexibility of the support of IPv6 can be obviously improved, and the service capability of resource service parties such as CDN (CDN) and the like is further improved.

In practical application, there may be an extreme case where a domain name is blocked (for example, there are violations and illegal contents in the domain name), or a global resolution fault occurs, which may result in that the domain name is not available, and for this case, in order to avoid that a domain name resolution failure has an influence on a content service of a user, see a flowchart of the redirection scheduling processing method provided in fig. 4, the redirection scheduling processing method applied to the scheduling party may further include, before step 203:

step 203', if the currently used redirection domain name of the dispatcher is unavailable, selecting an available redirection domain name from a plurality of redirection domain names applied by the dispatcher in advance, and triggering the step of acquiring the target redirection domain name corresponding to the target IP address, so that the acquired target redirection domain name is obtained by processing the target IP address and the selected redirection domain name.

In view of the above situation, in order to provide a fast and effective solution, in this embodiment, N (N > = 2) redirected domain names, such as xxx.com, yyy.com, zz.com, etc., are applied to the CDN network in advance, and a corresponding https domain name certificate is applied to each domain name, respectively, so as to support domain name verification in the https service.

On the basis, a prefix domain name obtained by converting each IPv6 address in the CDN is assembled with different domain names in advance to obtain different domain names of which each IPv6 address corresponds to different domain names, and the prefix domain name and the different domain names are combined into a first analysis record (AAAA record) and a second analysis record (A record) which are added to the domain name under each domain name to form different domain name information systems of which the IPv6 address set of the CDN corresponds to the different domain names respectively.

In each specific moment, only one generic domain is enabled, the domain information system corresponding to the generic domain is correspondingly enabled, and other generic domains and the domain information systems corresponding to the generic domains are used as spares.

The method and the device effectively solve the problem of rapid recovery of CDN service when extreme conditions such as domain name is forbidden (e.g. violation, illegal content and the like exist in the domain name) or global resolution failure and the like occur, and can avoid influence on the service capability of the CDN caused by unavailability of the currently used domain name.

Matching with the redirection scheduling processing method applied to the scheduler, the embodiment of the present application further discloses a redirection scheduling processing method applied to a domain name service, where the domain name service scheduler may be a DNS system, specifically, a DNS system of a CDN provider.

Referring to the flowchart of the redirection scheduling processing method provided in fig. 5, the redirection scheduling processing method applied to the domain name service provider may include:

step 501, a first resolution request carrying a target redirection domain name of a requester is obtained.

After receiving the response information fed back by the scheduling party, the requesting party generates a first resolution request based on the target redirection domain name and the self resolution requirement (if an IPv6 address or an IPv4 address needs to be resolved) carried in the response information, and sends the first resolution request to a domain name service party, such as a DNS system.

After obtaining the first resolution request, the domain name service side resolves to obtain a target redirection domain name and request type information corresponding to resolution requirements of the request side, where the request type information may be, for example, AAAA, indicating that an IPv6 address corresponding to the target redirection domain name needs to be resolved, or may also be, a, indicating that an IPv4 address corresponding to the target redirection domain name needs to be resolved.

In the case that the requesting terminal supports IPv4 and IPv6 dual stack, it is usually default to prefer IPv6 environment for network communication and resource acquisition, and in view of this, the request type information carried in the first analysis request is preferably AAAA.

Step 502, resolving the target redirection domain name according to the resolution rule to obtain a target version type IP address consistent with the request type of the first resolution request; wherein the resolution rules are at least operable to resolve the redirected domain name into a first version type IP address and a second version type IP address.

Optionally, the domain name server stores a series of domain names, and a first analysis record including an IPv6 address and a second analysis record including an IPv4 address, which are respectively added to each domain name. More specifically, as shown in fig. 6, in order to support rapid CDN service recovery under the condition that a domain name is blocked or a global resolution fault is unavailable, the domain name server may store different domain name information systems respectively corresponding to multiple domain names, where the different domain name information systems respectively maintain a set of domain name sets corresponding to different domain names, and a first resolution record and a second resolution record respectively added to each domain name in the set.

Meanwhile, the domain name service side maintains a domain name resolution rule based on the information structure, and the resolution rule comprises the following steps:

At each specific moment, the domain name service side performs domain name resolution based on the enabled generic domain name and its domain name information system.

After a first resolution request carrying a target redirection domain name of a requester is obtained, a domain name server extracts an IP address from a corresponding resolution record corresponding to the target redirection domain name according to a request type, for example, according to a request type AAAA, extracts a corresponding IPv6 address from an AAAA record corresponding to the target redirection domain name, and the like.

In addition, optionally, in the domain name information system of the domain name service side, each domain name may be associated with only one resolution record (e.g., a record) carrying the IPv4 address. After a first parsing request carrying a target redirection domain name of a requester is obtained, if the request type is a type for indicating obtaining of an IPv4 address, if the request type is a, directly extracting a corresponding IPv4 address from an a record corresponding to the target redirection domain name, if the request type is a type for indicating obtaining of an IPv6 address, such as AAAA, performing an inverse conversion process matching the above conversion rule on the target redirection domain name, and converting the target redirection domain name into an IPv6 address, for example, for a domain name 1234g5678g90abg0g0g0g0g0g0g0gcdef.xxx.com, removing a generic domain name xxx.com therein to obtain a1234 g5678g abg0g0g0g0 gcef, and then further replacing g therein with a colon mark, to obtain a1234 g5678 ab in terms of IPv6 address.

Step 503, feeding back response information including the target version type IP address to the requester.

And then, the domain name server assembles the analysis result into response information and returns the response information to the requester, wherein the response information comprises an IP address corresponding to the request type of the requester, and the IP address specifically corresponds to the target redirection domain name fed back by the dispatcher.

For the case of supporting IPv4 and IPv6 dual protocol stacks, the requesting party will preferably send an IPv6 type resolution request to the DNS system, and correspondingly, the domain name service party returns a response message including an IPv6 address.

Subsequently, the requester locates a target device for providing resource service, such as a certain CDN edge server in the CDN network, according to the IPv6 address in the response information, and initiates a link to the target device to obtain the resource.

In this embodiment, the resource server stores the first analysis record including the IPv6 address and the second analysis record including the IPv4 address for each domain name, so that it is possible to support dual-protocol IP address analysis on the redirection domain name, and accordingly, the flexibility of the redirection scheduling technology in supporting IPv6 is improved, and the service capabilities of the resource servers such as the CDN are improved.

When the IPv6 network environment is not good and the service quality is not good, based on the redirection scheduling technique in the embodiment of the present application, it can support the requester to quickly switch to using the IPv4 network environment for network information access, and thus, referring to fig. 7, the redirection scheduling processing method applied to the domain name service side in the present application may further include, after step 503:

step 504, a second resolution request carrying the target redirection domain name of the requester is obtained.

When a requester acquires resources through an IPv6 network according to an IPv6 address fed back by a DNS system, if the IPv6 network environment is not good, conditions such as response timeout or response failure are easily caused, at this time, a requester terminal can continuously initiate a second analysis request to the DNS system according to a pre-established network switching strategy, wherein the second analysis request carries a target redirection domain name and an IPv4 request type (for example, specific portable request type information: A).

And 505, analyzing the target redirection domain name according to the analysis rule to obtain a target version type IP address consistent with the request type of the second analysis request.

The DNS system receives a second resolution request of the requester, extracts a corresponding IPv4 address from a second resolution record (such as an A record) corresponding to the target redirection domain name according to a resolution rule, and realizes the domain name resolution of the type required by the second resolution request.

Step 506, returning response information including the target version type IP address consistent with the request type of the second resolution request to the requester.

And then, the DNS assembles the IPv4 address obtained by analysis into response information and feeds the response information back to the requester.

The requester locates a certain CDN edge server in the CDN network based on the IPv4 network according to the obtained IPv4 address, and obtains resources for the CDN edge server, so that the resource is easy to understand, after network switching is carried out, the CDN edge server located based on the IPv4 address is consistent with the CDN edge server located by the IPv6 address before switching, and the difference is that the resource service based on location and location is realized based on different IP protocol stacks and different networks.

Based on the domain name information structure of the domain name service side, the IP address resolution of the required protocol version is carried out on the same redirection domain name according to the requirement, the purposes of resource acquisition and information access by flexibly switching to another network when one network environment is poor are achieved, in terms of IPv6, the flexibility of the redirection scheduling technology for supporting IPv6 is improved, the service capability of the CDN network is improved, and meanwhile, the capability of a requester terminal for accessing resources is also improved.

Corresponding to the redirection scheduling processing method applied to the scheduler, an embodiment of the present application further provides a redirection scheduling processing apparatus applied to the scheduler, and as shown in fig. 8, the structural schematic diagram of the apparatus may include:

a first obtaining unit 801, configured to obtain a resource request of a requester;

a determining unit 802, configured to determine a target IP address of a target device for providing a resource service for the resource request;

a second obtaining unit 803, configured to obtain a target redirection domain name corresponding to the target IP address when the resource request is at least a first version type IP request;

a first feedback unit 804, configured to feed back response information including the target redirection domain name to the requester;

In an optional implementation manner of the embodiment of the present application, the second obtaining unit 803 is specifically configured to:

under the condition that the resource request is an IPv6 request, acquiring a target redirection domain name corresponding to the IPv6 address of the target equipment;

or,

In an optional implementation manner of the embodiment of the present application, the target redirection domain name is obtained by processing the target IP address and a pre-applied redirection domain name;

converting the IPv6 address of the target device into a domain name prefix;

In an optional implementation manner of the embodiment of the present application, redirecting the resolution rule of the domain name corresponding to the domain name service side includes:

resolving the redirection domain name into a corresponding IPv6 address according to a first resolution record which is added for the pre-association of the redirection domain name and comprises the IPv6 address;

In an optional implementation manner of the embodiment of the present application, referring to fig. 9, the apparatus may further include:

a selecting unit 805 configured to: if the currently used redirection domain name of the dispatcher is unavailable, selecting an available redirection domain name from a plurality of redirection domain names previously applied by the dispatcher, and triggering the second obtaining unit 803 to obtain a target redirection domain name corresponding to the target IP address, so that the obtained target redirection domain name is obtained by processing the target IP address and the selected redirection domain name.

As for the redirection scheduling processing apparatus applied to the scheduler disclosed in the embodiment of the present application, since it corresponds to the redirection scheduling processing method applied to the scheduler disclosed in the above method embodiments, the description is relatively simple, and for relevant similar points, please refer to the description of the above corresponding method embodiments, and detailed description is omitted here.

Corresponding to the above redirection scheduling processing method applied to the domain name service provider, an embodiment of the present application further provides a redirection scheduling processing apparatus applied to the domain name service provider, and as shown in a schematic structural diagram of the apparatus shown in fig. 10, the redirection scheduling processing apparatus may include:

a third obtaining unit 1001, configured to obtain a first resolution request carrying a target redirection domain name from a requestor;

an analyzing unit 1002, configured to analyze the target redirection domain name according to an analysis rule, to obtain a target version type IP address that is consistent with the request type of the first analysis request; the resolution rule at least can be used for resolving the redirection domain name into a first version type IP address and a second version type IP address;

a second feedback unit 1003, configured to feed back response information including the target version type IP address to the requester.

In an optional implementation manner of the embodiment of the present application, the domain name service entity pre-stores, for each redirection domain name in the set of redirection domain names, a first resolution record including an IPv6 address and a second resolution record including an IPv4 address, which are added in association with the redirection domain name.

In an optional implementation manner of the embodiment of the present application, a request type of the first resolution request is a type for requesting an IPv6 address;

the parsing unit 1002, when parsing the target redirection domain name according to the parsing rule to obtain a target version type IP address consistent with the request type of the first parsing request, is specifically configured to: and resolving the target redirection domain name into a corresponding IPv6 address according to a first resolution record added for the target redirection domain name in a pre-association manner.

In an optional implementation manner of the embodiment of the present application, the third obtaining unit 1001 is further configured to: acquiring a second resolution request carrying the target redirection domain name from a requester; the analyzing unit 1002 is further configured to analyze the target redirection domain name according to the analysis rule, so as to obtain a target version type IP address consistent with the request type of the second analysis request; the second feedback unit 1003 is further configured to: and feeding back response information including a target version type IP address consistent with the request type of the second resolution request to a requester.

In an optional implementation manner of the embodiment of the present application, the request type of the second resolution request is a type for requesting an IPv4 address;

the parsing unit 1002, when parsing the target redirection domain name according to the parsing rule to obtain a target version type IP address consistent with the request type of the second parsing request, is specifically configured to: and resolving the target redirection domain name into a corresponding IPv4 address according to a second resolution record added for the target redirection domain name pre-association.

As for the redirection scheduling processing apparatus applied to the domain name service side disclosed in the embodiment of the present application, since it corresponds to the redirection scheduling processing method applied to the domain name service side disclosed in the above method embodiments, the description is relatively simple, and for the relevant similar points, please refer to the description of the above corresponding method embodiments, and detailed description is omitted here.

The embodiment of the present application further discloses a scheduling device, where the scheduling device may be, but is not limited to, a certain scheduling server in a CDN scheduling system, and a schematic structural diagram of the scheduling device shown in fig. 11 at least includes:

a first memory 1101 for storing a first set of computer instructions;

the set of computer instructions may be embodied in the form of a computer program.

The first memory 1101 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The first processor 1102 is configured to implement the redirection scheduling processing method applied to the scheduler according to any of the above method embodiments by executing the instruction set stored in the first memory.

The first processor 1102 may be a Central Processing Unit (CPU), an application-specific integrated circuit (ASIC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an application-specific programmable gate array (FPGA), or other programmable logic devices.

Besides, the scheduling device may further include a communication interface, a communication bus, and the like. The memory, the processor and the communication interface communicate with each other via a communication bus.

The communication interface is used for communication between the scheduling device and other devices (such as a central control device in the CDN scheduling system). The communication bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like, and may be classified as an address bus, a data bus, a control bus, or the like.

In this embodiment, a first processor in a scheduling device executes a first computer instruction set stored in a first memory, and when a resource request of a requester is a resource request of at least a first version type IP request, the scheduler obtains a target redirection domain name that can be used for at least supporting resolution of a dual version type IP address (i.e., the redirection domain name can be resolved into the first version type IP address and a second version type IP address) for the requester, so as to redirect the resource request of a user, and accordingly, the requester, such as a client, can be supported to access a resource in a dual protocol stack manner, so that when a first version type IP (e.g., IPv 6) network environment is poor, the resource request can be switched to a second version type IP (e.g., IPv 4) network environment for resource acquisition, and when the redirection scheduling technology of the present application is applied to support of networks such as IPv6, the flexibility of support of IPv6 can be obviously improved, and the service capability of a resource service provider, such as CDN, can be further improved.

The embodiment of the present application further discloses a domain name service device, which may specifically be a DNS server in a DNS system, and as shown in a schematic structural diagram of the domain name service device shown in fig. 12, the domain name service device at least includes:

a second memory 1201 for storing a second set of computer instructions;

the second processor 1202 is configured to implement the redirection scheduling processing method applied to the domain name service device according to any of the above method embodiments by executing the instruction set stored in the second memory.

The second memory 1201 and the second processor 1202 are similar to the first memory 1101 and the second processor 1102 of the scheduling apparatus, and thus, it can be understood that the detailed description is omitted.

The second processor in the domain name service device implements the matched processing with the scheduling device by executing the second computer instruction set stored in the second memory, and performs the IP address resolution of the required protocol version on the same redirection domain name according to the requirement based on the stored domain name information structure, thereby achieving the purpose of flexibly switching to another network for resource acquisition and information access when one network environment is poor, and in terms of IPv6, the flexibility of the redirection scheduling technology for supporting IPv6 is improved, the service capability of the CDN network is improved, and the capability of the requester terminal for accessing resources is also improved.

In addition, the embodiment of the present application also discloses a computer readable storage medium, in which a first computer instruction set is stored, and when being executed by a processor, the first computer instruction set implements the redirection scheduling processing method applied to the scheduler as disclosed in any method embodiment above.

Specifically, when the first computer instruction set in the computer-readable storage medium of this embodiment is executed by the processor, for a resource request of a requester, in a case that the resource request is at least a first version-type IP request, the scheduler implements redirection of the resource request to the user by obtaining, for the resource request, a target redirection domain name that can be used for at least supporting resolution of a dual version-type IP address (i.e., at least resolving the redirection domain name into a first version-type IP address and a second version-type IP address), and accordingly can support the requester, such as a client, to access a resource in a dual-protocol stack manner, so that when a network environment of the first version-type IP (e.g., IPv 6) is poor, the requester can be switched to a network environment based on a second version-type IP (e.g., IPv 4) to obtain the resource, and when the redirection scheduling technology of the present application scheme is applied to support of networks, such as IPv6, it is obvious that flexibility of support of IPv6 can be improved, and service capability of a resource service provider, such as CDN, is further improved.

The embodiment of the present application further discloses another computer-readable storage medium, which stores a second set of computer instructions, and the second set of computer instructions, when executed by a processor, implement the redirection scheduling processing method applied to the domain name service party as disclosed in any of the above method embodiments.

When the second computer instruction set stored in the other computer readable storage medium is executed by the processor, based on the domain name information structure stored by the domain name service side, the purpose of flexibly switching to another network for resource acquisition and information access when one network environment is poor is achieved by performing IP address resolution of a required protocol version on the same redirection domain name according to requirements, and for IPv6, the flexibility of the redirection scheduling technology for supporting IPv6 is improved, the service capability of the CDN network is improved, and the capability of a requester terminal for accessing resources is also improved.

In addition, the embodiment of the application also discloses a redirection scheduling processing system, which comprises a request party, a domain name service party and a scheduling party;

wherein:

the dispatcher is used for realizing the redirection of the resource request of the requester by executing the redirection dispatching processing method applied to the dispatcher disclosed by any method embodiment;

the domain name service side is used for providing the domain name service for the requesting side by executing the redirection scheduling processing method applied to the domain name service side as disclosed by any method embodiment.

It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.

For convenience of description, the above system or apparatus is described as being divided into various modules or units by function, respectively. Of course, the functionality of the various elements may be implemented in the same one or more pieces of software and/or hardware in the practice of the present application.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.

Finally, it should also be noted that, in this document, relational terms such as first, second, third, fourth, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. A redirection scheduling processing method is characterized in that the method is applied to a scheduling party;

the method comprises the following steps:

acquiring a resource request of a requester;

under the condition that the resource request is at least a first version type IP request, if the currently used redirection domain name of the scheduling party is unavailable, selecting an available redirection domain name from a plurality of redirection domain names which are applied by the scheduling party in advance;

acquiring a target redirection domain name corresponding to the target IP address based on the selected generic domain name;

feeding back response information comprising the target redirection domain name to a requester;

2. The method according to claim 1, wherein, in the case that the resource request is at least a first version type IP request, acquiring a target redirection domain name corresponding to the target IP address includes:

or,

3. The method according to claim 2, wherein the target redirection domain name is obtained based on processing the target IP address and a pre-applied redirection domain name;

converting the IPv6 address of the target device into a domain name prefix;

4. The method of claim 1, wherein redirecting the resolution rule for the domain name at the domain name server comprises:

5. A redirection scheduling processing method, which is applied to a domain name service side corresponding to the scheduling side in any one of claims 1 to 4;

the method comprises the following steps:

analyzing the target redirection domain name according to an analysis rule to obtain a target version type IP address consistent with the request type of the first analysis request; the resolution rule at least can be used for resolving the redirection domain name into a first version type IP address and a second version type IP address;

6. The method of claim 5, wherein the domain name service pre-stores a first resolution record comprising an IPv6 address and a second resolution record comprising an IPv4 address for each redirection domain name in the set of redirection domain names added in association with the redirection domain name.

7. The method of claim 6, wherein the request type of the first resolution request is a type for requesting an IPv6 address;

8. The method of claim 7, wherein after the feeding back response information including the target version type IP address to the requestor, further comprising:

9. The method of claim 8, wherein the request type of the second resolution request is a type for requesting an IPv4 address;

10. A redirection scheduling processing device is characterized by being applied to a scheduling party;

the device comprises:

a first obtaining unit, configured to obtain a resource request of a requester;

a second obtaining unit, configured to, if the resource request is at least a first-version IP request, select an available redirection domain name from a plurality of redirection domain names that are applied by the scheduler in advance if the redirection domain name currently used by the scheduler is unavailable, and obtain a target redirection domain name corresponding to the target IP address based on the selected domain name;

11. A redirection scheduling processing apparatus, which is applied to a domain name server corresponding to the scheduler in claim 10;

the device comprises:

the resolving unit is used for resolving the target redirection domain name according to a resolving rule to obtain a target version type IP address consistent with the request type of the first resolving request; the analysis rule can be at least used for analyzing the redirection domain name into a first version type IP address and a second version type IP address;

12. A scheduling apparatus, comprising:

a first memory for storing a first set of computer instructions;

a first processor for implementing the redirection scheduling processing method according to any of claims 1 to 4 by executing a set of instructions stored on the first memory.

13. A domain name service apparatus, comprising:

a second memory for storing a second set of computer instructions;

a second processor for implementing the redirection scheduling processing method according to any of claims 5 to 9 by executing a set of instructions stored on the second memory.

14. A computer-readable storage medium having stored therein a first set of computer instructions which, when executed by a processor, implement the redirection scheduling processing method of any of claims 1-4.

15. A computer-readable storage medium having stored therein a second set of computer instructions which, when executed by a processor, implement the redirection scheduling processing method of any of claims 5-9.

16. A redirection scheduling processing system is characterized by comprising a request party, a domain name service party and a scheduling party;

wherein:

the dispatcher, configured to implement redirection of the resource request of the requester by performing the method according to any one of claims 1 to 4;

the domain name service party, configured to provide the domain name service for the requesting party by performing the method according to any one of claims 5 to 9.