Scheduling information generation method and device and electronic equipment

Abstract

The invention discloses a scheduling information generation method and device, electronic equipment and a storage medium. The method comprises the following steps: in response to a scheduling query demand, obtaining a to-be-queried service domain name and a query condition; performing domain name resolution on the to-be-queried service domain name to obtain a domain name alias; querying a matched scheduling record in a scheduling system according to the query condition and the domain name alias; wherein the query condition is used for constraining a scheduling range corresponding to the matched scheduling record; and generating corresponding scheduling information according to the matched scheduling record. According to the method and the device, on the basis of the to-be-queried service domain name and the query condition input by the user, the matched scheduling record can be automatically queried in the scheduling system, the corresponding scheduling information is generated, manual intervention is not needed, the accuracy and the speed of obtaining the scheduling information are improved, and the time and resource cost is reduced.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a method, device and electronic device for generating scheduling information. Background Art

[0002] Converged Content Delivery Network (CDN) refers to the integration of multiple CDN service providers to improve content distribution efficiency and network performance. Since each service provider has its own scheduling system, it is difficult for users to directly understand the specific scheduling strategies of each service provider or it is difficult for users' CDN scheduling systems to include detailed scheduling of all regions. Therefore, there are problems such as insufficient transparency of scheduling information and difficulty in directly obtaining scheduling information such as scheduling Internet Protocol (IP) location or regional scheduling.

[0003] In the related art, the dispatch information needs to be queried and obtained through manual communication channels. However, the above solution requires manual intervention, which reduces the accuracy and speed of obtaining the dispatch information and increases the time and resource costs. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a method, device, electronic device and storage medium for generating scheduling information, so as to solve the problem that manual intervention is required in related technologies, which reduces the accuracy and speed of obtaining scheduling information and increases time and resource costs.

[0005] To achieve the above objectives, the present application embodiment adopts the following technical solutions: In a first aspect, an embodiment of the present application provides a method for generating scheduling information, comprising: in response to a scheduling query demand, obtaining a domain name of a service to be queried and a query condition; performing domain name resolution on the domain name of the service to be queried to obtain a domain name alias; querying a matching scheduling record in a scheduling system according to the query condition and the domain name alias; wherein the query condition is used to constrain a scheduling range corresponding to a matching scheduling record; and generating corresponding scheduling information according to the matching scheduling record.

[0006] In a second aspect, an embodiment of the present application provides a device for generating scheduling information, including: an acquisition module, used to obtain a domain name of a service to be queried and a query condition in response to a scheduling query demand; a resolution module, used to perform domain name resolution on the domain name of the service to be queried to obtain a domain name alias; a query module, used to query a matching scheduling record in a scheduling system according to the query condition and the domain name alias; wherein the query condition is used to constrain a scheduling range corresponding to a matching scheduling record; a generation module, used to generate corresponding scheduling information according to the matching scheduling record.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the embodiment of the first aspect of the present application.

[0008] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the embodiment of the first aspect of the present application are implemented.

[0009] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: When generating scheduling information, the embodiment of the present application responds to the scheduling query demand, obtains the domain name of the service to be queried and the query condition, performs domain name resolution on the domain name of the service to be queried, obtains the domain name alias, and queries the matching scheduling record in the scheduling system according to the query condition and the domain name alias. The query condition is used to constrain the scheduling range corresponding to the matching scheduling record, and generates corresponding scheduling information according to the matching scheduling record. Based on the domain name of the service to be queried and the query condition input by the user, the embodiment of the present application can realize automatic query of matching scheduling records in the scheduling system, and generate scheduling information within the scheduling range corresponding to the corresponding query condition, such as the scheduling information of different suppliers within the scheduling range corresponding to the target user IP address, or the scheduling information within the scheduling range corresponding to at least one set regional screening condition, without the need for manual intervention, thereby improving the accuracy and speed of obtaining scheduling information and reducing time and resource costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings: Figure 1 A flowchart of a method for generating scheduling information provided by an embodiment of the present application; Figure 2 A flowchart of a method for generating scheduling information provided in another embodiment of the present application; Figure 3 A schematic diagram of the overall flow of a method for generating scheduling information provided in another embodiment of the present application; Figure 4 A flowchart of a method for generating scheduling information provided in another embodiment of the present application; Figure 5 A schematic diagram of the overall flow of a method for generating scheduling information provided in another embodiment of the present application; Figure 6 A schematic diagram of the structure of a device for generating scheduling information provided by an embodiment of the present application; Figure 7 A schematic diagram of the structure of an electronic device provided for one embodiment of the present application. DETAILED DESCRIPTION

[0011] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0012] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. In addition, the "and / or" in this application represents at least one of the connected objects, and the character " / " generally represents that the front and back associated objects are in an "or" relationship. It should be noted that the data involved in this application are all obtained on the premise of obtaining user authorization.

[0013] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0014] Figure 1 A flowchart of a method for generating scheduling information provided by an embodiment of the present application is shown below. Figure 1 As shown, the method for generating scheduling information in the embodiment of the present application may specifically include the following steps: S101, in response to a scheduling query demand, obtaining a domain name of a service to be queried and a query condition.

[0015] In the embodiment of the present application, the execution subject of the method for generating scheduling information in the embodiment of the present application is a scheduling information generation device, which can be set in an electronic device. The electronic device can be a terminal device or a server. Among them, the terminal device can be a mobile phone, a tablet computer, a desktop computer, a portable notebook, a vehicle-mounted device, etc.; the server can be an independent server or a server cluster composed of multiple servers.

[0016] The user initiates a scheduling query demand, which includes the service domain name to be queried and the query conditions entered by the user.

[0017] The business domain name to be queried is the business domain name to be queried input by the user, such as a.com. The query condition is the scheduling content to be queried input by the user, which is used to constrain the scheduling range corresponding to the matching scheduling record, and may specifically include but is not limited to the target user Internet Protocol IP address (such as 1.1.1.1) or at least one set regional screening condition, at least one regional screening condition includes positive selection area and / or negative selection area (for example, if you want to query the scheduling situation of Beijing, Shanghai and Guangzhou in China + all overseas regions, then the positive selection is: Beijing, Shanghai and Guangzhou in China, and the negative selection is: China, that is, you need to select Beijing, Shanghai and Guangzhou in China, and then exclude other regions in China, then the remaining regions are Beijing, Shanghai and Guangzhou in China + all overseas regions), etc.

[0018] In some embodiments, the user may input the domain name of the service to be queried and the query conditions in text format through an input device such as a mouse or a keyboard.

[0019] In other embodiments, the user may input the business domain name and query conditions to be queried in voice format by voice. Specifically: the scheduling information generation device collects the business domain name and query conditions to be queried input by the user through a sound collection device such as a microphone, and converts the business domain name and query conditions to be queried in voice format into the business domain name and query conditions to be queried in text format.

[0020] In addition, the embodiments of the present application can support users to select the scheduling type of CDN, such as Domain Name System (DNS) type and Hypertext Transfer Protocol DNS, HTTPDNS type, etc. The default is DNS type. The subsequent scheduling process is executed according to the scheduling type of CDN selected by the user. The following scheduling process is described using DNS as an example. The HTTPDNS type is similar to the DNS type and will not be repeated here.

[0021] S102, performing domain name resolution on the service domain name to be queried to obtain a domain name alias.

[0022] In the embodiment of the present application, the user can perform domain name resolution on the service domain name to be queried obtained in step S101 through the dig command to obtain the alias (Canonical Name, CNAME for short) of the resolved domain name corresponding to the service domain name to be queried, that is, the domain name alias.

[0023] A domain name alias may include at least one level, i.e., one level or multiple levels, and multiple levels of domain name aliases may include one level to N level domain name aliases, where N is equal to or greater than 2. For example, by performing domain name resolution on a service domain name a.com to be queried through the dig command, a first level domain name alias b.com, a second level domain name alias c.com, and the like may be obtained.

[0024] S103, searching for matching scheduling records in the scheduling system according to the query condition and the domain name alias, wherein the query condition is used to constrain the scheduling range corresponding to the matching scheduling record.

[0025] In the embodiment of the present application, according to the query condition obtained in step S101 and the domain name alias obtained in step S102, the converged CDN scheduling system is searched for scheduling records that fully comply with the query condition and the domain name alias.

[0026] S104, generating corresponding scheduling information according to the matched scheduling records.

[0027] In an embodiment of the present application, there are generally multiple matching scheduling records queried in step S103, and corresponding multiple scheduling information are generated based on the multiple scheduling records. The specific generation process corresponds to different processes depending on the query conditions. For details, please see the relevant description in the subsequent embodiments.

[0028] Among them, different query conditions correspond to scheduling information within different scheduling ranges. For example, when the query condition is the target user IP address, the scheduling information is the scheduling information of different suppliers within the scheduling range corresponding to the target user IP address; when the query condition is at least one set regional filtering condition, the scheduling information is the scheduling information of different suppliers within the scheduling range corresponding to the at least one set regional filtering condition.

[0029] It should be noted here that the embodiment of the present application supports the user to choose whether to cache the query results, that is, the correspondence between the service domain name to be queried and the query conditions and scheduling information. The query results need to be cached by default; if you choose to cache, the query results can be retrieved from the cache very quickly the next time you want to use them, and the entire query process will no longer be executed; if you choose not to cache, each query will not obtain data from the cache, but the entire query process will be executed directly.

[0030] Furthermore, since the domain name alias obtained in step S102 may include multiple levels, the matching scheduling record is searched in order according to the level of the domain name alias until a matching scheduling record is found. Figure 2 As shown, the above step S103 may specifically include the following steps: S201, querying whether there is a matching scheduling record in the scheduling system according to the query condition and the current-level domain name alias, wherein the initial value of the current-level domain name alias is the first-level domain name alias.

[0031] In an embodiment of the present application, the first-level domain name alias is used as the initial value of the current-level domain name alias. According to the query condition and the first-level domain name alias obtained in step S101, a query is made in the first-level scheduling record of the integrated CDN scheduling system to see whether there is a scheduling record matching the query condition and the first-level domain name alias.

[0032] S202: If it exists, execute the step of generating corresponding scheduling information according to the matching scheduling record.

[0033] In the embodiment of the present application, if there is a scheduling record that matches the query condition and the first-level domain name alias, the scheduling record query is terminated and the subsequent step S104 is executed.

[0034] S203: If it does not exist, update the next-level domain name alias to the current-level domain name alias, and return to step S201.

[0035] In an embodiment of the present application, if there is no scheduling record that matches the query condition and the first-level domain name alias, the next-level domain name alias, that is, the second-level domain name alias, is used as the new current-level domain name alias, and the process returns to step S201. According to the query condition and the second-level domain name alias obtained in step S101, the second-level scheduling record of the integrated CDN scheduling system is queried to see whether there is a scheduling record that matches the query condition and the second-level domain name alias. If there is a scheduling record that matches the query condition and the second-level domain name alias, the scheduling record query is terminated, and the subsequent step S104 is executed. If there is no scheduling record that matches the query condition and the second-level domain name alias, the next-level domain name alias, that is, the third-level domain name alias, is used as the new current-level domain name alias, and the process returns to step S201... and so on, until a matching scheduling record is found, the scheduling record query is terminated, and the subsequent step S104 is executed.

[0036] It should be noted here that the multi-level domain name aliases can be fully resolved before the scheduling record query, or the first-level domain name aliases can be resolved first, and the next-level domain name aliases can be resolved in sequence as needed during the scheduling record query process.

[0037] The following describes in detail the method for generating scheduling information in an embodiment of the present application by taking the query conditions including the target user IP address and the query conditions including at least one set region screening condition as examples.

[0038] 1) When the query condition includes the target user IP address, the above step S103 "querying matching scheduling records in the scheduling system according to the query condition and the domain name alias" may specifically include the following steps: determining the corresponding target user IP address according to the target user IP address; and querying the scheduling system for scheduling records corresponding to the domain name alias within the scheduling range that matches the target user IP address according to the target user IP address and the domain name alias.

[0039] In the embodiment of the present application, the IP attribution of the target user is the attribution of the IP address of the target user. For example, according to the IP address 1.1.1.1 of the target user, by querying the IP address database, it can be obtained that the attribution of the IP address 1.1.1.1 is: China-Telecom-Guangdong. According to the IP attribution of the target user: China-Telecom-Guangdong and the domain name alias, the dispatching record corresponding to the domain name alias within the dispatching range matching China-Telecom-Guangdong is queried in the dispatching system.

[0040] Each matching scheduling record includes at least a scheduling record type corresponding to the scheduling record and a scheduling weight corresponding to the scheduling record. The scheduling record type may include A type, AAAA type, and domain name alias (CNAME) type. The sum of the scheduling weights in all matching scheduling records is 100%.

[0041] A-type dispatch records are the most common and widely used type of DNS records in DNS resolution. They are used to point domain names to corresponding IP address spaces. Adding A-type dispatch records is equivalent to telling the DNS system that when users enter domain names, they should be directed to the server IP address set by the A record. For example, if you need to point the domain name www.example.com to the IP address 1.1.1.1, you need to add an A-type dispatch record to complete the binding relationship between the domain name and the IP address. It should be noted that A-type dispatch records are only applicable to Internet Protocol version 4 (IPv4) address resolution, and IPv6 addresses require AAAA-type dispatch records.

[0042] The CNAME type dispatch record is another common record type in DNS resolution. It is different from the A type dispatch record in that it represents the mapping of hostname to hostname. When you need to point a domain name to another domain name instead of an IP address, you need to add a CNAME type dispatch record. For example, when you need to point the domain name www.example.com to another domain name test.example.com, you need to add a CNAME type dispatch record instead of an A type dispatch record.

[0043] A common application scenario for CNAME type dispatch records is that a company has multiple domain names pointing to an IP address. If the IP address changes, the A type dispatch record needs to be modified for each domain name, which is not only inefficient but also prone to errors. In this case, you can use one of the domain names or create a new domain name separately, add an A type dispatch record to this domain name pointing to the IP address, and then add CNAME type dispatch records to other domain names pointing to this domain name. When the IP address changes, you only need to modify the domain name pointed to by the CNAME type dispatch record, without having to make changes to each domain name, which greatly improves work efficiency and reduces the risk of operational errors. In addition, CNAME type dispatch records are also often used in CDN, corporate mailbox, and global traffic management scenarios.

[0044] From the above, we can see that although both type A scheduling records and type CNAME scheduling records are ultimately used to achieve a mapping relationship between a domain name and a server IP address, type A scheduling records directly resolve a domain name to an IP address, while type CNAME scheduling records require resolving a domain name to another domain name, and then resolving the other domain name to an IP address.

[0045] When the dispatch record type is type A or type AAAA, the matched dispatch record may also include a dispatch IP address, and the dispatch IP attribution corresponding to the dispatch IP address in the matched dispatch record is consistent with the target user IP attribution. For the matched dispatch record whose dispatch record type is type A or type AAAA, the above step S104 "generating corresponding dispatch information according to the matched dispatch record" may specifically include the following steps: generating corresponding dispatch information according to the dispatch IP address and dispatch weight in the matched dispatch record, and the dispatch IP attribution corresponding to the dispatch IP address, the dispatch information including the dispatch IP address, the dispatch IP attribution and the dispatch ratio, and the dispatch ratio is equal to the dispatch weight.

[0046] For example, for the scheduling record of type A: A type + IP1 (scheduling IP address) + 30% (scheduling weight), the scheduling IP ownership is determined according to the scheduling IP address IP1: China-Guangdong-Mobile-Guangzhou. According to the above scheduling record: A type + IP1 (scheduling IP address) + 30% (scheduling weight) and scheduling IP ownership: China-Guangdong-Mobile-Guangzhou, the corresponding scheduling information generated is: China-Guangdong-Mobile-Guangzhou + IP1 + 30% (scheduling ratio).

[0047] When the scheduling record type is CNAME type, the matching scheduling record may also include a supplier CNAME, and the supplier CNAME in the matching scheduling record is consistent with a CNAME in at least one of the first-level CNAMEs obtained by resolving the service domain name to be queried, and is the CNAME of a third-party supplier pointed to by the pre-given service domain name to be queried, proving that it is the CNAME of other integrated suppliers. Among them, the service domain name to be queried and the first-level CNAME in at least one of the first-level CNAMEs resolved by the service domain name to be queried must be its own CNAME, and the second-level and subsequent CNAMEs can be the CNAMEs of third-party suppliers. For a matching scheduling record whose scheduling record type is a CNAME type, the above-mentioned step S104 "generating corresponding scheduling information according to the matching scheduling record" may specifically include the following steps: resolving the provider domain name alias in the matching scheduling record multiple times through the target user IP address, and statistically calculating the statistical weight corresponding to at least one scheduling IP address resolved; generating corresponding scheduling information according to the scheduling weight in the matching scheduling record, the statistical weight corresponding to at least one scheduling IP address resolved, and the scheduling IP attribution, the scheduling information including at least one scheduling IP address, the scheduling IP attribution corresponding to at least one scheduling IP address, and the scheduling ratio, the scheduling ratio corresponding to the scheduling IP address being equal to the product of the scheduling weight in the matching scheduling record and the statistical weight corresponding to the scheduling IP address.

[0048] For example, for a CNAME type dispatch record: CNAME type + aa.com (provider CNAME) + 50% (dispatching weight), the dig command is used to parse and count the provider CNAMEaa.com in the dispatch record 100 times, and the number of occurrences of IP2 (dispatching IP address) is 40 times, and the corresponding statistical weight is 40 / 100=40%. The number of occurrences of IP3 (dispatching IP address) is 60 times, and the corresponding statistical weight is 60 / 100=60%. According to IP2, the corresponding dispatch IP ownership is determined to be: China-Guangdong-Mobile-Guangzhou, and the corresponding dispatch is determined according to IP3. The IP ownership is: China-Guangdong-Mobile-Dongguan. According to the above scheduling records: CNAME type + aa.com (provider CNAME) + 50% (scheduling weight), IP2 + statistical weight 40%, IP3 + statistical weight 60% and IP2 + scheduling IP ownership: China-Guangdong-Mobile-Guangzhou, IP3 + scheduling IP ownership: China-Guangdong-Mobile-Dongguan, the corresponding two scheduling information are generated: China-Guangdong-Mobile-Guangzhou + IP2 + 50% * 40% = 20% (scheduling proportion), China-Guangdong-Mobile-Dongguan + IP3 + 50% * 60% = 30% (scheduling proportion).

[0049] It should be noted here that each scheduling information may also include a scheduling type previously selected by the user, such as DNS type, HTTPDNS, etc.

[0050] Here are some examples: Scenario 1: The matching dispatch records include type A dispatch records: IP1 + dispatch weight 30%, type AAAA dispatch records: IP2 + dispatch weight 70%. By searching the IP database, it is found that IP1 belongs to: China-Guangdong-Mobile-Guangzhou, and IP2 belongs to: China-Guangdong-Mobile-Dongguan. The multiple dispatch information finally generated can be: DNS China-Guangdong-Mobile-Guangzhou 30%IP1 DNS China-Guangdong-Mobile-Dongguan 70%IP2 Scenario 2: The matching scheduling records only include scheduling records of type A: IP1 + scheduling weight 100%. By searching the IP database, the attribution of IP1 is: China-Guangdong-Mobile-Guangzhou. The scheduling information finally generated can be: DNS China-Guangdong-Mobile-Guangzhou 100%IP1 It should be noted here that the situation where the matched dispatch records only include AAAA type dispatch records is the same as scenario 2, and will not be repeated here.

[0051] Scenario 3: The matching dispatch records include A-type dispatch records: IP1 + dispatch weight 50%, CNAME-type dispatch records: aa.com + dispatch weight 50%. By querying the IP database, the attribution of IP1 is: China-Guangdong-Mobile-Guangzhou. After parsing and counting aa.com 100 times, we get: China-Guangdong-Mobile-Guangzhou IP2 40 times, the corresponding statistical weight is 40%, China-Guangdong-Mobile-Dongguan IP3 60 times, the corresponding statistical weight is 60%, then the final dispatch information generated can be: DNS China-Guangdong-Mobile-Guangzhou 50%IP1 DNS China-Guangdong-Mobile-Guangzhou 40% * 50% = 20% IP2 DNS China-Guangdong-Mobile-Dongguan 60% * 50% = 30% IP3 It should be noted here that the situation where the matched scheduling records only include scheduling records of the AAAA record type and scheduling records of the CNAME type is the same as scenario three, and will not be repeated here.

[0052] Scenario 4: The dispatch record only includes CNAME type dispatch records: aa.com + dispatch weight 100%. After parsing and counting aa.com 100 times, we get: China-Guangdong-Mobile-Guangzhou IP1 40 times, the corresponding statistical weight is 40%, China-Guangdong-Mobile-Dongguan IP3 60 times, the corresponding statistical weight is 60%, then the final dispatch information generated can be: DNS China-Guangdong-Mobile-Guangzhou 40% IP1 DNS China-Guangdong-Mobile-Dongguan 60% IP2 To clearly illustrate the method for generating scheduling information in the embodiment of the present application, the following is combined with Figure 3 The overall process of the method for generating scheduling information in the embodiment of the present application is described in detail. Figure 3 The method for generating scheduling information in the embodiment of the present application may specifically include the following steps: S301, in response to a scheduling query demand, obtaining a domain name of a service to be queried and an IP address of a target user.

[0053] S302, performing domain name resolution on the service domain name to be queried to obtain domain name aliases: a first-level domain name alias and a second-level domain name alias.

[0054] S303: Determine the corresponding target user IP address according to the target user IP address.

[0055] S304: According to the target user IP address and the first-level domain name alias, check whether there is a matching scheduling record in the first-level scheduling record of the integrated CDN scheduling system. If yes, execute step S306. If no, execute step S305.

[0056] S305: According to the target user's IP address and the secondary domain name alias, a matching scheduling record is searched in the secondary scheduling record of the integrated CDN scheduling system.

[0057] S306, determine whether the type of the matching scheduling record is type A or type AAAA. If yes, execute step S307. If no, that is, the type of the matching scheduling record is type CNAME, execute steps S308-S309.

[0058] S307, generating and outputting corresponding scheduling information according to the scheduling IP address and scheduling weight in the matched scheduling record, and the scheduling IP attribution corresponding to the scheduling IP address.

[0059] S308, performing multiple resolutions on the provider domain name alias in the matching scheduling record through the target user IP address, and counting the weights corresponding to the at least one scheduling IP address resolved.

[0060] S309: Generate corresponding scheduling information according to the scheduling weight in the matched scheduling record, the statistical weight corresponding to each of the at least one scheduling IP address parsed out, and the scheduling IP attribution.

[0061] 2) When the query condition includes the target user IP address, the above step S103 "querying matching scheduling records in the scheduling system according to the query condition and the domain name alias" may specifically include the following steps: according to the set at least one regional filtering condition and domain name alias, querying the scheduling system for scheduling records within the scheduling range and corresponding to the domain name alias that matches at least one regional filtering condition.

[0062] In the embodiments of the present application, Each matching dispatch record includes at least the dispatch area, dispatch IP address and dispatch weight corresponding to the dispatch record. For regions in China, the dispatch area can be at the province level, such as China-Beijing, China-Shanghai, China-Guangdong, etc. For overseas regions, the dispatch area can be at the country level, such as the United States, the United Kingdom, etc.

[0063] For at least one matching dispatch record in the same dispatch area, such as Figure 4 As shown, the above step S104 "generating corresponding scheduling information according to the matched scheduling record" may specifically include the following steps: S401, when the sum of the dispatch weights is 100%, the dispatch information corresponding to the dispatch area is generated according to the dispatch records corresponding to the dispatch area. The dispatch information includes the dispatch area, the dispatch IP address corresponding to each dispatch record and the dispatch ratio of the dispatch IP address. The dispatch ratio is equal to the dispatch weight.

[0064] For example, for the dispatch area: China-Beijing, there are two matching dispatch records: China-Beijing+IP1+30% and China-Beijing+IP2+70%. Then the dispatch information corresponding to the dispatch area: China-Beijing is: China-Beijing+IP1-30%+IP2-70%.

[0065] S402, when the sum of the dispatching weights is less than 100%, the dispatching weight of the default dispatching area is determined to be the difference between 100% and the sum of the dispatching weights, and the dispatching information corresponding to the dispatching area is generated according to the dispatching records corresponding to the dispatching area and the dispatching weight of the default dispatching area. The dispatching information includes the dispatching area, the dispatching IP address corresponding to each dispatching record and the dispatching ratio of the dispatching IP address, the default dispatching area and the dispatching ratio of the default dispatching area. The dispatching ratio of the dispatching IP address is equal to the dispatching weight of the dispatching IP address, and the dispatching ratio of the default dispatching area is equal to the dispatching weight of the default dispatching area.

[0066] For example, for the dispatch region: United States, there are two matching dispatch records: United States + IP1 + 30%, United States + IP2 + 50%, then the dispatch weight of the default dispatch region is determined to be 100% - (30% + 50%) = 20%, and the dispatch information corresponding to the dispatch region: United States is generated as: United States + IP1-30% + IP2-50% default dispatch region - 20%. The default dispatch region is a region that does not exist in the dispatch record of the dispatch system.

[0067] It should be noted here that each scheduling information may also include a scheduling type previously selected by the user, such as DNS type, HTTPDNS, etc.

[0068] To clearly illustrate the method for generating scheduling information in the embodiment of the present application, the following is combined with Figure 5 The overall process of the method for generating scheduling information in the embodiment of the present application is described in detail. Figure 5 The method for generating scheduling information in the embodiment of the present application may specifically include the following steps: S501, in response to a scheduling query requirement, obtaining a domain name of a service to be queried and at least one set region screening condition.

[0069] S502, performing domain name resolution on the service domain name to be queried to obtain domain name aliases: a primary domain name alias and a secondary domain name alias.

[0070] S503: According to the set at least one region screening condition and the first-level domain name alias, query whether there is a matching scheduling record in the first-level scheduling record of the integrated CDN scheduling system. If yes, execute step S505. If no, execute step S504.

[0071] S504: According to the set at least one region screening condition and the secondary domain name alias, a matching scheduling record is searched in the secondary scheduling record of the converged CDN scheduling system.

[0072] S505, determine whether the sum of the dispatch weights in the matching dispatch records in the same dispatch area is 100%. If so, execute step S506. If not, execute steps S507-S508.

[0073] S506: Generate scheduling information corresponding to the scheduling area according to each scheduling record corresponding to the scheduling area.

[0074] S507, determining that the dispatch weight of the default dispatch area is the difference between 100% and the sum of the dispatch weights.

[0075] S508: Generate scheduling information corresponding to the scheduling area according to each scheduling record corresponding to the scheduling area and the scheduling weight of the default scheduling area.

[0076] In summary, in the method for generating scheduling information according to the embodiments of the present application, when generating scheduling information, in response to a scheduling query requirement, the business domain name to be queried and the query condition are obtained, the business domain name to be queried is resolved to obtain a domain name alias, and according to the query condition and the domain name alias, matching scheduling records are queried in the scheduling system, where the query condition is used to constrain the scheduling range corresponding to the matching scheduling records, and corresponding scheduling information is generated according to the matching scheduling records. Based on the business domain name to be queried and the query condition input by the user, the embodiments of the present application can automatically query matching scheduling records in the scheduling system and generate corresponding scheduling information, such as scheduling information of different suppliers within the scheduling range corresponding to the target user's IP address, or scheduling information within the scheduling range corresponding to at least one region filtering condition set, without manual intervention, improving the accuracy and speed of obtaining scheduling information and reducing time and resource costs.

[0077] Figure 6 FIG. is a schematic structural diagram of a device for generating scheduling information provided by an embodiment of the present application. As Figure 6 shown, the device 600 for generating scheduling information according to the embodiments of the present application may specifically include: an obtaining module 601, a parsing module 602, a query module 603, and a generating module 604. Among them: The obtaining module 601 is configured to obtain the business domain name to be queried and the query condition in response to a scheduling query requirement.

[0078] The parsing module 602 is configured to resolve the business domain name to be queried to obtain a domain name alias.

[0079] The query module 603 is configured to query matching scheduling records in the scheduling system according to the query condition and the domain name alias; where the query condition is used to constrain the scheduling range corresponding to the matching scheduling records.

[0080] The generating module 604 is configured to generate corresponding scheduling information according to the matching scheduling records.

[0081] In the embodiments of the present application, for the specific processes of each module and unit in the device for generating scheduling information according to the embodiments of the present application to implement their functions, reference may be made to the relevant descriptions in the embodiments of the method for generating scheduling information above, and details are not described herein again.

[0082] In summary, the device for generating scheduling information in the embodiment of the present application, when generating scheduling information, responds to the scheduling query demand, obtains the domain name of the service to be queried and the query condition, performs domain name resolution on the domain name of the service to be queried, obtains the domain name alias, and queries the matching scheduling record in the scheduling system according to the query condition and the domain name alias. The query condition is used to constrain the scheduling range corresponding to the matching scheduling record, and generates corresponding scheduling information according to the matching scheduling record. Based on the domain name of the service to be queried and the query condition input by the user, the embodiment of the present application can realize automatic query of matching scheduling records in the scheduling system, and generate scheduling information within the scheduling range corresponding to the corresponding query condition, such as the scheduling information of different suppliers within the scheduling range corresponding to the target user IP address, or the scheduling information within the scheduling range corresponding to at least one set regional screening condition, without the need for manual intervention, thereby improving the accuracy and speed of obtaining scheduling information and reducing time and resource costs.

[0083] The present application also provides an electronic device. Figure 7 As shown, the electronic device 700 includes: a processor 701, a memory 702, and a program or instruction stored in the memory 702 and executable on the processor 701. When the program or instruction is executed by the processor 701, the steps of the method for generating scheduling information in any of the above embodiments are implemented.

[0084] The electronic device of the embodiment of the present application, when generating scheduling information, responds to the scheduling query demand, obtains the domain name of the service to be queried and the query condition, performs domain name resolution on the domain name of the service to be queried, obtains the domain name alias, and queries the matching scheduling record in the scheduling system according to the query condition and the domain name alias. The query condition is used to constrain the scheduling range corresponding to the matching scheduling record, and generates corresponding scheduling information according to the matching scheduling record. Based on the domain name of the service to be queried and the query condition input by the user, the embodiment of the present application can realize automatic query of matching scheduling records in the scheduling system, and generate scheduling information within the scheduling range corresponding to the corresponding query condition, such as the scheduling information of different suppliers within the scheduling range corresponding to the target user IP address, or the scheduling information within the scheduling range corresponding to at least one set regional screening condition, without the need for manual intervention, thereby improving the accuracy and speed of obtaining scheduling information and reducing time and resource costs.

[0085] An embodiment of the present application also proposes a readable storage medium, on which one or more computer programs are stored. The one or more computer programs include instructions. When the program or instructions are executed by a processor in an electronic device that includes multiple applications, the processor in the electronic device can execute the various steps of the above-mentioned scheduling information generation method embodiment.

[0086] The readable storage medium of the embodiment of the present application, when generating scheduling information, responds to the scheduling query demand, obtains the domain name of the service to be queried and the query condition, performs domain name resolution on the domain name of the service to be queried, obtains the domain name alias, and queries the matching scheduling record in the scheduling system according to the query condition and the domain name alias. The query condition is used to constrain the scheduling range corresponding to the matching scheduling record, and generates corresponding scheduling information according to the matching scheduling record. Based on the domain name of the service to be queried and the query condition input by the user, the embodiment of the present application can realize automatic query of matching scheduling records in the scheduling system, and generate scheduling information within the scheduling range corresponding to the corresponding query condition, such as the scheduling information of different suppliers within the scheduling range corresponding to the target user IP address, or the scheduling information within the scheduling range corresponding to at least one set regional screening condition, without the need for manual intervention, thereby improving the accuracy and speed of obtaining scheduling information and reducing time and resource costs.

[0087] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0088] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0089] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0090] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0091] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0092] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0093] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0094] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0095] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0096] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0097] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0098] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0099] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for generating scheduling information, characterized in that: include: In response to the scheduling query demand, obtain the service domain name to be queried and the query condition; Performing domain name resolution on the service domain name to be queried to obtain a domain name alias; According to the query condition and the domain name alias, query the matching scheduling record in the scheduling system; wherein the query condition is used to constrain the scheduling range corresponding to the matching scheduling record; Generate corresponding scheduling information according to the matched scheduling record.

2. The method according to claim 1, characterized in that The domain name alias includes at least one primary domain name alias, and searching for matching scheduling records in the scheduling system according to the query condition and the domain name alias includes: According to the query condition and the current-level domain name alias, querying in the scheduling system whether there is a matching scheduling record, wherein the initial value of the current-level domain name alias is the first-level domain name alias; If so, executing the step of generating corresponding scheduling information according to the matching scheduling record; If it does not exist, the next-level domain name alias is updated to the current-level domain name alias, and the process returns to the step of querying whether there is a matching scheduling record in the scheduling system according to the query condition and the current-level domain name alias.

3. The method according to claim 1, characterized in that The query condition includes the target user's Internet Protocol IP address, or at least one set regional screening condition.

4. The method according to claim 3, characterized in that In the case where the query condition is the target user IP address, querying the matching scheduling record in the scheduling system according to the query condition and the domain name alias includes: According to the target user IP address, determine the corresponding target user IP ownership; According to the target user IP attribution and the domain name alias, the dispatch system is queried for a dispatch record corresponding to the domain name alias within a dispatch range that matches the target user IP attribution.

5. The method according to claim 4, characterized in that The matched scheduling record includes a scheduling record type and a scheduling weight. When the scheduling record type is type A or type AAAA, the matched scheduling record also includes a scheduling IP address. The scheduling IP attribution corresponding to the scheduling IP address in the matched scheduling record is consistent with the IP attribution of the target user. The generating corresponding scheduling information according to the matched scheduling record includes: When the scheduling record type in the matching scheduling record is type A or type AAAA, corresponding scheduling information is generated based on the scheduling IP address and scheduling weight in the matching scheduling record, and the scheduling IP attribution corresponding to the scheduling IP address. The scheduling information includes the scheduling IP address, the scheduling IP attribution and the scheduling ratio, and the scheduling ratio is equal to the scheduling weight.

6. The method according to claim 4, characterized in that The matched scheduling record includes a scheduling record type and a scheduling weight. When the scheduling record type is a domain name alias type, the matched scheduling record also includes a supplier domain name alias. The supplier domain name alias in the matched scheduling record is consistent with a domain name alias in at least one first-level domain name alias obtained by resolving the domain name of the service to be queried; The generating corresponding scheduling information according to the matched scheduling record includes: In the case where the scheduling record type in the matched scheduling record is a domain name alias type, the provider domain name alias in the matched scheduling record is parsed multiple times by the target user IP address, and the statistical weight corresponding to each of the at least one scheduling IP address parsed is counted; According to the scheduling weight in the matched scheduling record, the statistical weight corresponding to each of the at least one scheduling IP address parsed out, and the scheduling IP attribution, the corresponding scheduling information is generated, wherein the scheduling information includes the at least one scheduling IP address, the scheduling IP attribution corresponding to each of the at least one scheduling IP address, and the scheduling ratio, and the scheduling ratio corresponding to the scheduling IP address is equal to the product of the scheduling weight in the matched scheduling record and the statistical weight corresponding to the scheduling IP address.

7. The method according to claim 3, characterized in that The query condition includes at least one set regional screening condition, and searching the scheduling system for matching scheduling records according to the query condition and the domain name alias includes: According to the at least one regional screening condition and the domain name alias, a scheduling record corresponding to the domain name alias within a scheduling range matching the at least one regional screening condition is queried in the scheduling system, wherein the at least one regional screening condition includes a positively selected region and / or a negatively selected region.

8. The method according to claim 7, characterized in that The matched scheduling record includes a scheduling region, a scheduling IP address and a scheduling weight; and the generating corresponding scheduling information according to the matched scheduling record includes: For each dispatch record corresponding to the same dispatch area, when the sum of the dispatch weights is 100%, dispatch information corresponding to the dispatch area is generated according to each dispatch record corresponding to the dispatch area, and the dispatch information includes the dispatch area, the dispatch IP address corresponding to each dispatch record, and the dispatch ratio of the dispatch IP address, and the dispatch ratio of the dispatch IP address is equal to the dispatch weight of the dispatch IP address; When the sum of the scheduling weights is less than 100%, the scheduling weight of the default scheduling area is determined to be the difference between 100% and the sum of the scheduling weights, and the scheduling information corresponding to the scheduling area is generated according to the scheduling records corresponding to the scheduling area and the scheduling weight of the default scheduling area. The scheduling information includes the scheduling area, the scheduling IP address corresponding to each scheduling record and the scheduling ratio of the scheduling IP address, the default scheduling area and the scheduling ratio of the default scheduling area. The scheduling ratio of the scheduling IP address is equal to the scheduling weight of the scheduling IP address, and the scheduling ratio of the default scheduling area is equal to the scheduling weight of the default scheduling area.

9. A device for generating scheduling information, characterized in that: include: An acquisition module, used to respond to the scheduling query demand and obtain the service domain name to be queried and the query condition; A resolution module, used to perform domain name resolution on the service domain name to be queried to obtain a domain name alias; A query module, used to query the matching scheduling record in the scheduling system according to the query condition and the domain name alias; wherein the query condition is used to constrain the scheduling range corresponding to the matching scheduling record; A generation module is used to generate corresponding scheduling information according to the matching scheduling record.

10. An electronic device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 8.

Images