Domain name configuration method and device, computer equipment and readable storage medium

Abstract

The invention relates to a domain name configuration method and device, computer equipment and a readable storage medium. The method comprises the following steps: acquiring a target domain name configuration template from a template information base according to a domain name configuration request sent by a request end; generating an initial domain name configuration result according to configuration content in the domain name configuration request and the target domain name configuration template; converting the initial domain name configuration result, and generating a target domain name configuration result; the target domain name configuration result meets the configuration requirement of the edge node; and sending the target domain name configuration result to a target edge node. By adopting the method, the domain name configuration efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a domain name configuration method, apparatus, computer equipment, and readable storage medium. Background Art

[0002] The Content Delivery Network (CDN) works by adding a new layer of network architecture to the existing internet, distributing website content to the "edge" of the network closest to users. This allows users to access the content they need locally, alleviates internet congestion, and improves website response times. Due to the advantages of CDNs, an increasing number of domain names are adopting CDN acceleration services to improve response times.

[0003] To use CDN acceleration services, domain name users submit a configuration request for the domain name they want to use CDN acceleration services (referred to as the accelerated domain name) to the domain name management server in the CDN. The domain name management server then configures the accelerated domain name based on the configuration request submitted by the domain name user. This allows the CDN edge nodes to provide CDN acceleration services for each accelerated domain name according to the corresponding configuration. However, the existing domain name configuration process is time-consuming and inefficient. Summary of the Invention

[0004] Based on this, it is necessary to provide a domain name configuration method, apparatus, computer device and readable storage medium that can improve the efficiency of domain name configuration in order to address the above technical problems.

[0005] In a first aspect, the present application provides a domain name configuration method, applied to a content distribution network, wherein the content distribution network includes at least one edge node, the method comprising:

[0006] According to the domain name configuration request sent by the requesting end, the target domain name configuration template is obtained from the template information library;

[0007] Generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template;

[0008] Converting the initial domain name configuration result and generating a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node;

[0009] Send the target domain name configuration result to the target edge node.

[0010] In one embodiment, the domain name configuration request includes at least one to-be-configured item, the configuration content includes at least one sub-configuration content, and each to-be-configured item corresponds to the sub-configuration content in a one-to-one manner; the template information library includes a plurality of domain name configuration templates, each of the domain name configuration templates includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item;

[0011] The step of obtaining a target domain name configuration template from a template information library according to the domain name configuration request sent by the requesting end includes:

[0012] Obtaining similarities between the to-be-configured items in the domain name configuration request and the template configuration items of each of the domain name configuration templates;

[0013] The target domain name configuration template is obtained according to the similarities corresponding to the domain name configuration templates.

[0014] In one embodiment, the template information library further includes a plurality of sub-configuration templates; and obtaining the target domain name configuration template according to the similarity corresponding to each of the domain name configuration templates includes:

[0015] Determine the domain name configuration template with the highest similarity as the candidate domain name configuration template;

[0016] In a case where at least some template configuration items of the candidate domain name configuration template correspond one-to-one to each of the to-be-configured items in the domain name configuration request, determining the candidate domain name configuration template as the target domain name configuration template;

[0017] In a case where at least some of the template configuration items in the candidate domain name configuration template correspond one-to-one to some of the items to be configured in the configuration content, sub-configuration templates corresponding to the remaining items to be configured in the domain name configuration request are screened out from the template information library, and the candidate domain name configuration template is updated according to the screened sub-configuration template to obtain a target domain name configuration template.

[0018] In one embodiment, the domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each of the item to be configured corresponds to the sub-configuration content in a one-to-one manner;

[0019] The target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a storage column of the template configuration item;

[0020] Generating an initial domain name configuration result according to the configuration content in the domain name configuration request and the domain name configuration template includes:

[0021] Determining a target template configuration item corresponding to the to-be-configured item from a sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item;

[0022] The sub-configuration content corresponding to the item to be configured is stored in the storage column corresponding to the target template configuration item to generate an initial domain name configuration result.

[0023] In one embodiment, the domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each of the items to be configured corresponds to the sub-configuration content in a one-to-one manner; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a conversion rule for the template configuration item;

[0024] The converting the initial domain name configuration result and generating a target domain name configuration result includes:

[0025] Determining a target template configuration item corresponding to the to-be-configured item from a sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item;

[0026] The sub-configuration content corresponding to the to-be-configured item is converted according to the conversion rule corresponding to the target template configuration item to generate a target domain name configuration result.

[0027] In one embodiment, before converting the initial domain name configuration result, the method further includes:

[0028] Verifying the initial domain name configuration result according to the verification rules in the target domain name configuration template and generating a verification result;

[0029] If the verification result is passed, the step of converting the initial domain name configuration result is performed.

[0030] In one embodiment, the domain name configuration request includes a domain name to be configured, and the initial domain name configuration result is an initial domain name configuration result of the domain name to be configured; the method further includes:

[0031] Obtaining historical domain name configuration results of the domain name to be configured;

[0032] The historical domain name configuration result is compared with the initial domain name configuration result, and a comparison result of the domain name to be configured is generated.

[0033] In a second aspect, the present application provides a domain name configuration device, which is applied to a content distribution network, wherein the content distribution network includes at least one edge node, and the device includes:

[0034] A first execution module is configured to obtain a target domain name configuration template from a template information library according to a domain name configuration request sent by a requesting end;

[0035] A second execution module is configured to generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template;

[0036] a third execution module, configured to convert the initial domain name configuration result and generate a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node;

[0037] The fourth execution module is configured to send the target domain name configuration result to the target edge node.

[0038] In a third aspect, the present application provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method described in any one of the above embodiments when executing the computer program.

[0039] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method described in any one of the above embodiments when the computer program is executed by a processor.

[0040] The above-mentioned domain name configuration method, device, computer equipment and readable storage medium, before receiving the domain name configuration request sent by the requesting end, first builds a template information library, and the template information library can include multiple domain name configuration templates. When the domain name configuration request sent by the requesting end is received, the target domain name configuration template can be directly obtained from the template information according to the domain name configuration request, and the initial domain name configuration result is directly generated according to the configuration content in the domain name configuration request and the target domain name configuration template. The initial domain name configuration result is then converted into a target domain name configuration result that can be parsed by the edge node, and the target domain name configuration result is then sent to the target edge node to complete the configuration of the domain name. The present application performs domain name configuration through a domain name configuration template, which not only unifies the standard for domain name configuration, but also can flexibly and quickly respond to the accelerated configuration requirements of various domain names, thereby improving the efficiency of domain name configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0042] Figure 1 A flowchart of a domain name configuration method according to an embodiment;

[0043] Figure 2 Schematic diagram of the process of step S101 in one embodiment;

[0044] Figure 3 Schematic diagram of the process of step S202 in one embodiment;

[0045] Figure 4 Schematic diagram of the process of step S102 in one embodiment;

[0046] Figure 5 Schematic diagram of the process of step S104 in one embodiment;

[0047] Figure 6 A flowchart of a domain name configuration method according to another embodiment;

[0048] Figure 7 A flowchart of a domain name configuration method according to another embodiment;

[0049] Figure 8 A system architecture diagram of a requesting end, a domain name configuration end, and a target edge node in one embodiment;

[0050] Figure 9 Schematic diagram of a flow chart of a domain name configuration method in another embodiment;

[0051] Figure 10 A structural block diagram of a domain name configuration device according to an embodiment;

[0052] Figure 11 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0054] As mentioned in the background technology section, with the development of information technology, network speed also determines user stickiness to a certain extent. Users' demands for website access efficiency are also getting higher and higher. In order to retain customers, website operators urgently need to accelerate domain names, which has given rise to diverse domain name acceleration needs in the CDN field. Traditional domain name configuration has no template concept. All domain names use similar configuration modes. CDN domain name configuration is actually differentiated by business type. Different business types have different configuration requirements, but there may also be common requirements. For example, the configuration requirements of static acceleration domain names, full-site acceleration domain names, security acceleration, and live broadcast are consistent, while some are personalized. Therefore, the traditional CDN domain name configuration process has the problem of low efficiency.

[0055] To solve the above technical problems, in an exemplary embodiment, please refer to Figure 1 The present application provides a domain name configuration method applied to a content distribution network, wherein the content distribution network includes at least one edge node. The domain name configuration method includes steps S101 to S104. The following description will be given using an example of the method being applied to a domain name configuration end in a content distribution network.

[0056] S101: According to the domain name configuration request sent by the requesting end, a target domain name configuration template is obtained from a template information library.

[0057] It can be understood that before receiving the domain name configuration request sent by the requesting end, the domain name configuration end can first build multiple domain name configuration templates. Specifically, the basic configuration item template can be defined first. The basic configuration item template can include the name, type, maximum and minimum values ​​of the configuration item, whether it supports customer self-service configuration, field mapping for external self-service, parent node information, configuration verification rules (which can be regular), configuration display model, linkage configuration items, configuration examples, configuration delivery level, delivery content, and dynamic monitoring events. Afterwards, for each configuration item, a corresponding sub-configuration template is generated according to the basic configuration item template. In an example, the basic configuration item template can be shown in Table 1 below:

[0058] Table 1 Basic configuration item template

[0059]

[0060] As can be seen, the basic configuration item template can include the configuration item name, configuration item identifier id, configuration item type type, configuration item storage column col, configuration item external self-service field api_field, whether self-service is supported is_api, parent node identifier pid, verification rule rule, conversion rule deploy_data, prompt information hint, dynamic event listening, and some other extended fields. After obtaining the basic configuration item template, corresponding sub-configuration templates can be generated for each configuration item based on the basic configuration item template. For example, for the cache time configuration item, a sub-configuration template corresponding to the cache time can be generated based on the basic configuration item template. The sub-configuration template corresponding to the cache time can be shown in Table 2.

[0061] Table 2 Cache time sub-configuration template

[0062]

[0063] In the application, for common configuration items, you can quickly generate corresponding sub-configuration templates based on the basic configuration item template. For some personalized configuration items, the basic configuration item template also provides some extended fields, which can be used to generate corresponding sub-configuration templates based on the basic configuration item template.

[0064] After obtaining each sub-configuration template, these sub-configuration item templates can be stored in the template information library. Since CDN domain name configuration is differentiated by business type, different business types have different configuration requirements, but there may also be common requirements, such as static acceleration domain names, full-site acceleration domain names, security acceleration, and live broadcast configuration requirements. There are consistent and personalized requirements. Therefore, according to the business type, its common configuration items can be selected, and according to the sub-configuration templates corresponding to these common configuration items, the corresponding domain name configuration templates for each business type can be generated and stored in the template information library. When the domain name configuration request sent by the requesting end is subsequently received, the appropriate domain name configuration template can be directly obtained from the template information according to the domain name configuration request, so that the various configuration requirements of customers can be quickly responded to, while improving development efficiency, reducing operation and maintenance costs, and unifying overall configuration specifications.

[0065] S102: Generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template.

[0066] In an application, the domain name configuration request sent by the requesting end can include the domain name to be configured and the configuration content of the domain name to be configured. After obtaining the target domain name configuration template, the configuration content of the domain name to be configured in the domain name configuration request can be entered into the storage column corresponding to the target domain name configuration template to generate the initial domain name configuration result. In an example, please refer to Table 2. Assume that the domain name configuration request includes the configuration content {"cache_time":2}, where cache_time is the external self-service field for the cache time configuration item and 2 is the value the user wishes to configure for the cache time. Then, the configuration value 2 corresponding to the cache time can be entered into the configuration item storage column N1 corresponding to the cache time to obtain the initial domain name configuration result.

[0067] S103: Convert the initial domain name configuration result and generate a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node.

[0068] To convert the initial domain name configuration result into data the gateway can understand, it must be converted. For example, the conversion rules in the sub-configuration template can be used to convert the configuration content into data the gateway can understand, namely the target domain name configuration result. For an example, referring to Table 2, the domain name configuration request still includes the configuration content {"cache_time":2}. The initial domain name configuration result can be converted to the target domain name configuration result ["set_cache_time", {"cache_time":"2"}].

[0069] S104: Send the target domain name configuration result to the target edge node.

[0070] After converting the initial domain name configuration result into a target domain name configuration result that the gateway can understand, the target domain name configuration result can be sent to the target edge node corresponding to the domain name to be configured in the content distribution network, so that the target edge node can accelerate the processing of the domain name to be configured according to the target domain name configuration result.

[0071] The above-mentioned domain name configuration method, before receiving the domain name configuration request sent by the requesting end, first builds a template information library, and the template information library may include multiple domain name configuration templates. When the domain name configuration request sent by the requesting end is received, the target domain name configuration template can be directly obtained from the template information according to the domain name configuration request, and the initial domain name configuration result is directly generated according to the configuration content in the domain name configuration request and the target domain name configuration template. The initial domain name configuration result is then converted into a target domain name configuration result that can be parsed by the edge node, and the target domain name configuration result is then sent to the target edge node to complete the configuration of the domain name. The present application performs domain name configuration through a domain name configuration template, which not only unifies the standard for domain name configuration, but also can flexibly and quickly respond to the accelerated configuration requirements of various domain names, thereby improving the efficiency of domain name configuration.

[0072] In an exemplary embodiment, a domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds to a sub-configuration content; the template information library includes multiple domain name configuration templates, each domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item; please refer to Figure 2 , step S101, according to the domain name configuration request sent by the requesting end, obtain the target domain name configuration template from the template information library, including step S201 and step S202.

[0073] S201: Obtain similarities between the to-be-configured items in the domain name configuration request and the template configuration items of each domain name configuration template.

[0074] It can be understood that since the template information library includes multiple domain name configuration templates, in order to filter out the target domain name configuration template suitable for the current domain name configuration from the template information library, the to-be-configured items in the domain name configuration request can be compared with the template configuration items of each domain name configuration template to obtain the similarity between the to-be-configured items in the domain name configuration request and the template configuration items of each domain name configuration template. The template configuration items can be the names of the configuration items in the sub-configuration template. In one example, assuming that the to-be-configured items in the domain name configuration request include source station information, back-to-source timeout, and anti-hotlinking, the template information library includes domain name configuration template 1, which includes a sub-configuration template for source station information, a sub-configuration template for back-to-source timeout, and a sub-configuration template for anti-hotlinking, that is, the template configuration items in domain name configuration template 1 include source station information, back-to-source timeout, and anti-hotlinking. Since the template configuration items included in domain name configuration template 1 can correspond one-to-one to the to-be-configured items in the domain name configuration request, the similarity between the to-be-configured items in the domain name configuration request and the template configuration items in domain name configuration template 1 is 100%. In another example, assume that the items to be configured in the domain name configuration request include source site information, back-to-source timeout, anti-hotlinking and IP blacklist, and the template information library includes domain name configuration template 1. Domain name configuration template 1 includes a sub-configuration template for source site information, a sub-configuration template for back-to-source timeout and a sub-configuration template for anti-hotlinking, that is, the template configuration items in domain name configuration template 1 include source site information, back-to-source timeout and anti-hotlinking. Since the template configuration items in domain name configuration template 1 do not include IP blacklist, the similarity between the items to be configured in the domain name configuration request and the template configuration items of domain name configuration template 1 is 75%.

[0075] S202: Obtain a target domain name configuration template according to the similarity corresponding to each domain name configuration template.

[0076] In this embodiment, each sub-configuration template included in the target domain name configuration template can correspond one-to-one to each to-be-configured item in the domain name configuration request. For example, assuming that the to-be-configured items in the domain name configuration request include source site information, back-to-source timeout period, and anti-hotlinking, the template information library includes domain name configuration template 1, and domain name configuration template 1 includes a sub-configuration template for source site information, a sub-configuration template for back-to-source timeout period, and a sub-configuration template for anti-hotlinking. Since each sub-configuration template included in domain name configuration template 1 can correspond one-to-one to each to-be-configured item in the domain name configuration request, domain name configuration template 1 can be used as the target domain name configuration template for this domain name configuration.

[0077] In another example, the domain name configuration request sent by the requesting end may also include a specified configuration template identifier, and each domain name configuration template in the template information library may have a unique identifier. In the case where the domain name configuration request sent by the requesting end includes a specified configuration template identifier, the domain name configuration end may directly obtain the domain name configuration template corresponding to the specified configuration template identifier from the template information library based on the specified configuration template identifier, and use it as the specified domain name configuration template. If at least some of the template configuration items in the specified domain name configuration template correspond one-to-one with each of the items to be configured in the domain name configuration request, the specified domain name configuration template may be determined as the target domain name configuration template, and an initial domain name configuration result may be generated based on the configuration content in the domain name configuration request and the target domain name configuration template. If at least some of the template configuration items in the specified domain name configuration template correspond one-to-one with some of the items to be configured in the domain name configuration request, the sub-configuration template corresponding to the remaining items to be configured in the domain name configuration request is filtered out from the template information library, and the specified domain name configuration template is updated based on the filtered sub-configuration template to obtain the target domain name configuration template.

[0078] Exemplarily, the template information library contains N domain name configuration templates, each with a unique identifier, such as Template 1, Template 2, ..., Template i, ..., Template N, where 1 < i ≤ N. A domain name configuration request sent by a requesting end to a domain name configuration end includes items to be configured and a designated configuration template identifier. The items to be configured include source site information, a return-to-source timeout, anti-hotlinking, and an IP blacklist. The designated configuration template identifier is "Template 4." Upon receiving the domain name configuration request, the domain name configuration end first retrieves the domain name configuration template corresponding to the designated configuration template identifier "Template 4" from the template information library as the designated domain name configuration template. If the designated domain name configuration template includes a sub-configuration template for source site information, a sub-configuration template for return-to-source timeout, and a sub-configuration template for anti-hotlinking, and the template configuration items of the designated domain name configuration template include source site information, return-to-source timeout, and anti-hotlinking, and since the template configuration items included in the designated domain name configuration template correspond one-to-one to the items to be configured in the domain name configuration request, the designated domain name configuration template can be directly used as the target domain name configuration template for the current domain name configuration. If the specified domain name configuration template includes a sub-configuration template for origin site information, a sub-configuration template for back-to-origin timeout, and a sub-configuration template for anti-hotlinking, that is, the template configuration items of the specified domain name configuration template include origin site information, back-to-origin timeout, and anti-hotlinking, and since the template configuration items of the specified domain name configuration template do not include the IP blacklist, you can obtain the IP blacklist sub-configuration template from the template information library, add the IP blacklist sub-configuration template to the specified domain name configuration template, and obtain a new domain name configuration template. Then, determine this new domain name configuration template as the target domain name configuration template.

[0079] In an exemplary embodiment, the template information library also includes multiple sub-configuration templates; see Figure 3 , step S202, obtaining the target domain name configuration template according to the similarity corresponding to each domain name configuration template, including steps S301 to S303.

[0080] S301: Determine the domain name configuration template with the highest similarity as a candidate domain name configuration template.

[0081] It can be understood that the higher the similarity between the to-be-configured item in the domain name configuration request and the domain name configuration template 1, the more closely the to-be-configured item in the domain name configuration request matches the domain name configuration template 1. Therefore, the domain name configuration template with the highest similarity can be determined as the candidate domain name configuration template.

[0082] S302: When at least some template configuration items of the candidate domain name configuration template correspond one-to-one to each to-be-configured item in the domain name configuration request, determine the candidate domain name configuration template as the target domain name configuration template.

[0083] For example, assuming that the items to be configured in the domain name configuration request include source site information, back-to-source timeout period and anti-hotlinking, the candidate domain name configuration template includes a sub-configuration template for source site information, a sub-configuration template for back-to-source timeout period and a sub-configuration template for anti-hotlinking, that is, the template configuration items of the candidate domain name configuration template include source site information, back-to-source timeout period and anti-hotlinking. Since the template configuration items included in the candidate domain name configuration template can correspond one-to-one to the items to be configured in the domain name configuration request, the candidate domain name configuration template can be directly used as the target domain name configuration template for this domain name configuration.

[0084] S303: When at least some of the template configuration items in the candidate domain name configuration template correspond one-to-one with some of the items to be configured in the configuration content, sub-configuration templates corresponding to the remaining items to be configured in the domain name configuration request are filtered out from the template information library, and the candidate domain name configuration template is updated according to the filtered sub-configuration template to obtain the target domain name configuration template.

[0085] In the application, when the candidate domain name configuration template only includes sub-configuration templates corresponding to some of the items to be configured in the domain name configuration request, the template configuration items missing from the candidate domain name configuration template corresponding to the domain name configuration request can be filtered out based on the template configuration items in the candidate domain name configuration template and the items to be configured in the domain name configuration request, and then the sub-configuration templates corresponding to these template configuration items are obtained from the template information library. The candidate domain name configuration template is updated according to the filtered sub-configuration templates to obtain the target domain name configuration template. In one example, the items to be configured in the domain name configuration request include source site information, back-to-source timeout, anti-hotlinking, and IP blacklist. The candidate domain name configuration template includes a sub-configuration template for source site information, a sub-configuration template for back-to-source timeout, and a sub-configuration template for anti-hotlinking. That is, the template configuration items of the candidate domain name configuration template include source site information, back-to-source timeout, and anti-hotlinking. Since the template configuration items of the candidate domain name configuration template do not include an IP blacklist, the sub-configuration template for the IP blacklist can be obtained from the template information library, and the sub-configuration template for the IP blacklist can be added to the domain name configuration template 1 to obtain a new domain name configuration template, which is then determined as the target domain name configuration template. In the application, the new domain name configuration template can also be stored in the template information library so that it can be directly retrieved and called from the template information library during subsequent domain name configuration.

[0086] In an exemplary embodiment, the domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds to the sub-configuration content; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a storage column of the template configuration item; please refer to Figure 4 , step S102, generating an initial domain name configuration result according to the configuration content in the domain name configuration request and the domain name configuration template, also includes steps S401 and S402.

[0087] S401: Determine a target template configuration item corresponding to a to-be-configured item from a sub-configuration template of a target domain name configuration template; the to-be-configured item is the same as the target template configuration item.

[0088] As described in the above embodiment, the target domain name configuration template includes multiple template configuration items corresponding to each to-be-configured item in the domain name configuration request. Therefore, for each to-be-configured item in the domain name configuration request, the target template configuration item corresponding to each to-be-configured item is determined from the target domain name configuration template.

[0089] S402: Store the sub-configuration content corresponding to the item to be configured into the storage column corresponding to the target template configuration item to generate an initial domain name configuration result.

[0090] In the application, the domain name configuration end also includes a configuration information library. The sub-configuration template of each configuration item includes the location where the value of each configuration item is stored in the configuration information library, that is, the configuration item storage column col. Therefore, the sub-configuration content corresponding to each to-be-configured item can be stored in the corresponding configuration item storage column col in the configuration information library according to the configuration item storage column col corresponding to its corresponding target template configuration item to generate the initial domain name configuration result.

[0091] In an exemplary embodiment, the domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds to the sub-configuration content; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a conversion rule for the template configuration item; please refer to Figure 5 , step S104, converting the initial domain name configuration result and generating a target domain name configuration result, including step S501 and step S502.

[0092] S501: Determine a target template configuration item corresponding to a to-be-configured item from a sub-configuration template of a target domain name configuration template; the to-be-configured item is the same as the target template configuration item.

[0093] As described in the above embodiment, the target domain name configuration template includes multiple sub-configuration templates corresponding to the items to be configured in the domain name configuration request, and each sub-configuration template includes template configuration items. Therefore, for each item to be configured in the domain name configuration request, the target template configuration items corresponding to each item to be configured are determined from the sub-configuration templates of the target domain name configuration template.

[0094] S502: Convert the sub-configuration content corresponding to the target configuration item according to the conversion rule corresponding to the target template configuration item to generate a target domain name configuration result.

[0095] As shown in Tables 1 and 2 above, the sub-configuration templates of each configuration item include the data format that needs to be converted when the value of each configuration item is sent to the edge node, that is, the conversion rule deploy_data. Therefore, the sub-configuration content corresponding to each to-be-configured item can be converted according to the conversion rule deploy_data corresponding to its corresponding target template configuration item to generate the target domain name configuration result.

[0096] In an exemplary embodiment, see Figure 6 , step S103, before converting the initial domain name configuration result, the method further includes steps S601 and S602.

[0097] S601: Verify the initial domain name configuration result according to the verification rules in the target domain name configuration template and generate a verification result.

[0098] In the application, after obtaining the initial domain name configuration result, in order to ensure the accuracy of the data sent to the edge node, it is also necessary to verify the sub-configuration content corresponding to each sub-configuration template according to the verification rules in each sub-configuration template in the target domain name configuration template. In one example, for a configuration item of a numerical type, the corresponding verification rule may include the maximum and minimum values ​​of the numerical value. In another example, for a configuration item of an enumeration type, the corresponding verification rule may be to verify whether the input value is within the enumeration value. It should be understood that the above verification rules are only examples. In the application, for the same type of configuration items, the corresponding verification rules may be the same or different. The verification rules corresponding to each configuration item can be determined by relevant technical personnel according to specific needs.

[0099] S602: If the verification result is passed, the step of converting the initial domain name configuration result is executed.

[0100] When the configuration content is verified, some sub-configuration contents in the configuration content can also be processed, and then the processed initial domain name configuration result can be converted. In one example, when the unit of the value of the sub-configuration content corresponding to the cache time in the domain name configuration request is hours, the value of the sub-configuration content corresponding to the cache time can be processed, and the value of the sub-configuration item corresponding to the cache time can be converted to seconds; in another example, the domain name configuration request includes "cache switch" and "cache time". When the cache switch is turned off, it means that all files do not need to be cached. At this time, the cache time configuration is invalid, so the sub-configuration content of "cache time" can be removed.

[0101] When the configuration content verification fails, a prompt message may be generated, which may include the configuration item that failed the verification, and the prompt message may be returned to the requesting end to prompt the user to re-initiate the domain name configuration request.

[0102] In an exemplary embodiment, the domain name configuration request includes the domain name to be configured, and the initial domain name configuration result is the initial domain name configuration result of the domain name to be configured; see Figure 7 , the method also includes step S701 and step S702.

[0103] S701: Obtain the historical domain name configuration result of the domain name to be configured.

[0104] In this embodiment, during the domain name configuration process, the present application can also track the configuration history of the domain name to be configured and obtain the historical domain name configuration results of the domain name to be configured. The historical domain name configuration results may include the configuration history information of the domain name to be configured and the configuration history of a single configuration item in the domain name to be configured.

[0105] S702: Compare the historical domain name configuration result with the initial domain name configuration result, and generate a comparison result of the domain name to be configured.

[0106] Since each domain name configuration is performed by obtaining the target domain name configuration template from the template information library, when the target domain name configuration template used before and after the domain name to be configured is the same, the configuration items can be quickly compared. If the target domain name configuration template used before and after the domain name to be configured is different, the same configuration items can be merged and compared when generating the configuration comparison results, which allows for quick and clear identification of the differences between the previous and next configurations.

[0107] In the application, some configuration items of the domain name to be configured can also be calibrated according to the historical domain name configuration results of the domain name to be configured. In an example, assuming that the configuration items in the domain name configuration request include an IP blacklist, the sub-configuration content corresponding to the IP blacklist in the domain name configuration request is {"1.1.1.1", "1.1.1.2"}, and the historical domain name configuration result of the domain name to be configured records the historical sub-configuration contents corresponding to the IP blacklist of the domain name to be configured, which are all {"1.1.1.1", "1.1.1.2", "1.1.1.3"}. Therefore, the domain name configuration end can modify the current sub-configuration content of the IP blacklist in the domain name to be configured based on the historical sub-configuration content of the IP blacklist in the domain name to be configured. Among them, the domain name configuration end can directly modify the current sub-configuration content of the IP blacklist in the domain name to be configured according to the historical sub-configuration content of the IP blacklist, or generate a correction prompt information, which includes the comparison difference results of the historical sub-configuration contents corresponding to the IP blacklist and the current sub-configuration content of the IP blacklist in the configured domain name, so as to prompt the user of the difference between the current domain name configuration and the historical domain name configuration, and determine whether to modify the current sub-configuration content of the IP blacklist in the domain name to be configured according to the historical sub-configuration content of the IP blacklist based on the correction instruction returned by the user through the request end.

[0108] For a detailed example, see Figure 8In the domain name configuration process of the present application, the interaction between the requesting end, the domain name configuration end and the target edge node is involved. The requesting end is used to send a domain name configuration request to the domain name configuration end. The domain name configuration end includes a basic configuration item maintenance module, a template customization module, a domain name configuration module and a template parsing engine. The basic configuration item maintenance module is used to maintain the basic configuration item template, and to construct corresponding sub-configuration templates and parent configuration templates for each configuration item required for the domain name configuration. The template customization module is used to generate a domain name configuration template based on the constructed sub-configuration template and parent configuration template. The domain name configuration module is used to generate an initial domain name configuration result according to the domain name configuration request and the target domain name configuration template. The template parsing engine is used to perform verification and conversion on the domain name configuration result, generate a target domain name configuration result and send the target domain name configuration result to the target edge node.

[0109] Specifically, the configuration items required for domain name configuration include sub-configuration items and parent configuration items. A parent configuration item may include multiple sub-configuration items with common attributes. Before receiving the domain name configuration request sent by the requesting end, the domain name configuration end may first construct corresponding sub-configuration templates and parent configuration templates for each configuration item required for domain name configuration based on the basic configuration item template. Afterwards, based on these sub-configuration templates and parent configuration templates, multiple domain name configuration templates may be customized according to the business type of CDN domain name configuration, and stored in the template information library so that they can be directly retrieved and called when the domain name is subsequently configured. At the same time, domain name configuration templates can be added to the template information library. For newly added domain name configuration templates, the existing domain name configuration templates in the template information library can be inherited, eliminating the repetitive operation of adding sub-configuration templates and parent configuration templates one by one. In the application, the parent configuration template is only for classification and does not require specific storage values. Therefore, the domain name configuration template may not include the parent configuration template, but only the sub-configuration template.

[0110] In an example, please refer to Tables 3, 4 and 5. Tables 3 and 4 are the parent configuration templates corresponding to the configuration items "cache configuration" and "access control" constructed based on the above Table 1, and Table 5 is the child configuration template corresponding to the configuration item "IP blacklist" constructed based on the above Table 1.

[0111] Table 3 Parent configuration template for cache configuration

[0112]

[0113] Table 4 Access control parent configuration template

[0114]

[0115] Table 5 IP blacklist sub-configuration template

[0116]

[0117] Some values ​​in Table 3 and Table 4 are left blank because the parent configuration items are only used for classification and do not need to store specific values.

[0118] In an example, the structure of a domain name configuration template constructed based on a child configuration template and a parent configuration template may be as shown in Table 6 below.

[0119] Table 6 Example of domain name configuration template structure

[0120]

[0121] In this example, the i-th domain name configuration template in the template information library includes the parent configuration template of the parent configuration item "Back-to-origin configuration", the parent configuration template of the parent configuration item "Cache configuration", the parent configuration template of the parent configuration item "Access control", the child configuration template of the child configuration item "Origin site information", the child configuration template of the child configuration item "Back-to-origin timeout", the child configuration template of the child configuration item "Cache time", the child configuration template of the child configuration item "Cache parameters", the child configuration template of the child configuration item "IP blacklist", the child configuration template of the child configuration item "IP whitelist", and the child configuration template of the child configuration item "Anti-hotlinking". Among them, "Origin site information" and "Back-to-origin timeout" are both child configuration items of the parent configuration item "Back-to-origin configuration", "Cache time" and "Cache parameters" are both child configuration items of the parent configuration item "Cache configuration", and "IP blacklist", "IP whitelist", and "Anti-hotlinking" are all child configuration items of the parent configuration item "Access control".

[0122] After building your template repository, see Figure 9When a domain name configuration request is received from the requesting end, the target domain name configuration template is obtained from the template information library, and the domain name to be configured is configured according to the target domain name configuration template and the domain name configuration request. The domain name configuration request can carry the domain name to be configured and the configuration content of the domain name to be configured. For example, the domain name configuration request can be {"domain":www.a.com,"cache_time":"2","ip_black_list":"1.1.1.1"}, where "www.a.com" is the domain name to be configured, "2" and "1.1.1.1" are the configuration content. Specifically, "2" is the sub-configuration content corresponding to the "cache time" to be configured, and "1.1.1.1" is the sub-configuration content corresponding to the "ip blacklist" to be configured. After receiving the domain name configuration request, the domain name configuration end will find the target domain name configuration template corresponding to the domain name configuration request from the template information according to the configuration items to be configured in the domain name configuration request, and fill each sub-configuration content into the corresponding configuration item storage column col in the configuration information library according to the configuration item storage column col in the corresponding sub-configuration template in the target domain name configuration template to generate the initial domain name configuration result. At the same time, the domain name configuration end can also obtain the historical domain name configuration results of the domain name to be configured, and compare the historical domain name configuration results with the initial domain name configuration results.

[0123] After determining the target domain name configuration template corresponding to the domain name configuration request, the domain name configuration terminal can also generate a template parsing engine for the current domain name based on the target domain name configuration template. The template parsing engine receives the initial domain name configuration result, verifies, processes, and converts the initial domain name configuration result, and saves the result of each domain name configuration. The template parsing engine has a common parsing module and a personalized parsing module for each domain name configuration template. The personalized parsing engine module solves each domain name configuration template with personalized configuration and personalized processing. Configuration information that cannot be processed by sub-configuration templates, i.e., special configurations, can be processed by the personalized parsing module. Specifically, the template parsing engine includes a configuration verifier, a configuration processor, and a configuration generator. The configuration verifier is used to verify the initial domain name configuration result according to the verification rules in each sub-configuration template. For example, for the cache time in the above example, it verifies whether the type of the input sub-configuration content "2" is correct and whether the data value size is an integer. Similarly, for the IP blacklist, it verifies whether the input sub-configuration content "1.1.1.1" is legal. After all sub-configurations have been verified, the configuration processor further processes them, converting them into a final result and passing it to the configuration generator. For example, if the cache time sub-configuration is entered in hours, the configuration processor can convert the cache time sub-configuration value into seconds. Finally, the configuration generator converts the initial domain name configuration result into data that the gateway can understand, namely the target domain name configuration result, based on the deploy_data conversion rule in the sub-configuration template corresponding to each configuration item in the target domain name configuration template. For example, after converting the cache time and IP blacklist sub-configurations, the target domain name configuration result is [["set_cache_time", {"cache_time": "2"}], ["set_ip_black_list", {"match_list": ["1.1.1.1"], "action": "deny", "forbidden_code": 403}]], and then sends the target domain name configuration result to the target edge node corresponding to the domain to be configured. In the application, after obtaining the target domain name configuration result, the configuration result can also be stored. The storage structure of the configuration result can include domain name, customer ID, domain name configuration template ID, configuration content, target domain name configuration result, version number and configuration time.

[0124] The domain name configuration method of the present application, based on the traditional overlay function configuration, formulates a unified configuration standard and standardizes the general configuration by maintaining a set of standardized basic configuration item templates. And according to the different business classifications of CDN, the various configuration items are combined into custom templates. On the basis of adapting to various acceleration configuration requirements of CDN, the CDN acceleration configuration can be classified and managed and configuration tracked. Since CDN configuration is also personalized, different customer domain names have various personalized configuration requirements. In response to such personalized requirements, personalized domain name configuration templates can also be formulated, and template parsing engines can be specified for processing, so as to achieve rapid response to various domain name configuration requirements of customers and reduce customer business response time. Due to the standardization of configuration standards, different business configurations are converted from traditional multi-platforms to a unified standard platform. While improving development efficiency, it also effectively reduces the complexity and learning cost of business operation and maintenance, and also reduces the risk of business failures to a certain extent.

[0125] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0126] Based on the same inventive concept, embodiments of the present application also provide a domain name configuration device for implementing the aforementioned domain name configuration method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more domain name configuration device embodiments provided below can be found in the aforementioned limitations of the domain name configuration method and will not be further elaborated here.

[0127] In an exemplary embodiment, Figure 10 As shown, the present application provides a domain name configuration device, which is applied to a content distribution network, the content distribution network includes at least one edge node, and the domain name configuration device includes a first execution module 1001, a second execution module 1002, a third execution module 1003 and a fourth execution module 1004.

[0128] The first execution module 1001 is configured to obtain a target domain name configuration template from a template information library according to a domain name configuration request sent by a requesting end.

[0129] The second execution module 1002 is configured to generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template.

[0130] The third execution module 1003 is used to convert the initial domain name configuration result and generate a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node.

[0131] The fourth execution module 1004 is configured to send the target domain name configuration result to the target edge node.

[0132] In an exemplary embodiment, a domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds one-to-one to the sub-configuration content; the template information library includes multiple domain name configuration templates, each domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item; wherein, the first execution module 1001 includes a first execution sub-module and a second execution sub-module.

[0133] The first execution submodule is used to obtain similarities between the to-be-configured items in the domain name configuration request and the template configuration items of each domain name configuration template.

[0134] The second execution submodule is used to obtain the target domain name configuration template according to the similarity corresponding to each domain name configuration template.

[0135] In an exemplary embodiment, the template information library further includes a plurality of sub-configuration templates; and the second execution submodule includes a first execution unit, a second execution unit, and a third execution unit.

[0136] The first execution unit is configured to determine the domain name configuration template with the highest similarity as a candidate domain name configuration template.

[0137] The second execution unit is configured to determine the candidate domain name configuration template as the target domain name configuration template when at least some template configuration items of the candidate domain name configuration template correspond one-to-one to each to-be-configured item in the domain name configuration request.

[0138] The third execution unit is used to filter out sub-configuration templates corresponding to the remaining items to be configured in the domain name configuration request from the template information library when at least some of the template configuration items in the candidate domain name configuration template correspond one-to-one to some of the items to be configured in the configuration content, and update the candidate domain name configuration template according to the filtered sub-configuration template to obtain the target domain name configuration template.

[0139] In an exemplary embodiment, a domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds to the sub-configuration content one-to-one; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a storage column of the template configuration item; the second execution module includes a third execution sub-module and a fourth execution sub-module.

[0140] The third execution submodule is used to determine the target template configuration item corresponding to the to-be-configured item from the sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item.

[0141] The fourth execution submodule is used to store the sub-configuration content corresponding to the to-be-configured item into the storage column corresponding to the target template configuration item to generate an initial domain name configuration result.

[0142] In an exemplary embodiment, the domain name configuration request includes at least one item to be configured, the configuration content includes at least one sub-configuration content, and each item to be configured corresponds to the sub-configuration content one-to-one; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a conversion rule for the template configuration item; the third execution module includes a fifth execution sub-module and a sixth execution sub-module.

[0143] The fifth execution submodule is used to determine the target template configuration item corresponding to the to-be-configured item from the sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item.

[0144] The sixth execution submodule is used to convert the sub-configuration content corresponding to the target configuration item according to the conversion rule corresponding to the target template configuration item to generate a target domain name configuration result.

[0145] In an exemplary embodiment, the domain name configuration apparatus further includes a fifth execution module and a sixth execution module.

[0146] The fifth execution module is used to verify the initial domain name configuration result according to the verification rules in the target domain name configuration template and generate a verification result.

[0147] The sixth execution module is used to execute the step of converting the initial domain name configuration result when the verification result is passed.

[0148] In an exemplary embodiment, the domain name configuration request includes the domain name to be configured, and the initial domain name configuration result is the initial domain name configuration result of the domain name to be configured; the domain name configuration device further includes a seventh execution module and an eighth execution module.

[0149] The seventh execution module is used to obtain the historical domain name configuration result of the domain name to be configured.

[0150] The eighth execution module is used to compare the historical domain name configuration result with the initial domain name configuration result, and generate a comparison result of the domain name to be configured.

[0151] Each module in the domain name configuration device described above may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0152] In an exemplary embodiment, the present application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method in any of the above embodiments when executing the computer program.

[0153] The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 11 As shown. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via wired or wireless means, and the wireless means can be implemented via Wi-Fi, a mobile cellular network, near-field communication (NFC), or other technologies. When executed by the processor, the computer program implements a domain name configuration method. The display unit of the computer device is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0154] Those skilled in the art will understand that Figure 11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0155] In one embodiment, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in any one of the above embodiments are implemented.

[0156] In one embodiment, a computer program product is provided, comprising a computer program, which implements the steps of the method described in any one of the above embodiments when executed by a processor.

[0157] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0158] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0159] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0160] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A domain name configuration method, characterized in that: Applied to a content distribution network, the content distribution network includes at least one edge node, and the method includes: According to the domain name configuration request sent by the requesting end, the target domain name configuration template is obtained from the template information library; Generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template; Converting the initial domain name configuration result and generating a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node; Send the target domain name configuration result to the target edge node.

2. The domain name configuration method according to claim 1, characterized in that: The domain name configuration request includes at least one to-be-configured item, the configuration content includes at least one sub-configuration content, and each to-be-configured item corresponds to the sub-configuration content in a one-to-one manner; the template information library includes a plurality of domain name configuration templates, each of the domain name configuration templates includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item; The step of obtaining a target domain name configuration template from a template information library according to the domain name configuration request sent by the requesting end includes: Obtaining similarities between the to-be-configured items in the domain name configuration request and the template configuration items of each of the domain name configuration templates; The target domain name configuration template is obtained according to the similarities corresponding to the domain name configuration templates.

3. The domain name configuration method according to claim 2, characterized in that: The template information library further includes a plurality of sub-configuration templates; and obtaining the target domain name configuration template according to the similarity corresponding to each of the domain name configuration templates includes: Determine the domain name configuration template with the highest similarity as the candidate domain name configuration template; In a case where at least some template configuration items of the candidate domain name configuration template correspond one-to-one to each of the to-be-configured items in the domain name configuration request, determining the candidate domain name configuration template as the target domain name configuration template; In a case where at least some of the template configuration items in the candidate domain name configuration template correspond one-to-one to some of the items to be configured in the configuration content, sub-configuration templates corresponding to the remaining items to be configured in the domain name configuration request are screened out from the template information library, and the candidate domain name configuration template is updated according to the screened sub-configuration template to obtain a target domain name configuration template.

4. The domain name configuration method according to any one of claims 1 to 3, characterized in that: The domain name configuration request includes at least one to-be-configured item, the configuration content includes at least one sub-configuration content, and each of the to-be-configured items corresponds to the sub-configuration content in a one-to-one manner; The target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a storage column of the template configuration item; Generating an initial domain name configuration result according to the configuration content in the domain name configuration request and the domain name configuration template includes: Determining a target template configuration item corresponding to the to-be-configured item from a sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item; The sub-configuration content corresponding to the item to be configured is stored in the storage column corresponding to the target template configuration item to generate an initial domain name configuration result.

5. The domain name configuration method according to any one of claims 1 to 3, characterized in that: The domain name configuration request includes at least one to-be-configured item, the configuration content includes at least one sub-configuration content, and each to-be-configured item corresponds to the sub-configuration content in a one-to-one manner; the target domain name configuration template includes at least one sub-configuration template, and the sub-configuration template includes at least a template configuration item and a conversion rule for the template configuration item; The converting the initial domain name configuration result and generating a target domain name configuration result includes: Determining a target template configuration item corresponding to the to-be-configured item from a sub-configuration template of the target domain name configuration template; the to-be-configured item is the same as the target template configuration item; The sub-configuration content corresponding to the to-be-configured item is converted according to the conversion rule corresponding to the target template configuration item to generate a target domain name configuration result.

6. The domain name configuration method according to any one of claims 1 to 3, characterized in that: Before converting the initial domain name configuration result, the method further includes: Verifying the initial domain name configuration result according to the verification rules in the target domain name configuration template and generating a verification result; If the verification result is passed, the step of converting the initial domain name configuration result is performed.

7. The domain name configuration method according to any one of claims 1 to 3, characterized in that: The domain name configuration request includes the domain name to be configured, and the initial domain name configuration result is the initial domain name configuration result of the domain name to be configured; the method further includes: Obtaining historical domain name configuration results of the domain name to be configured; The historical domain name configuration result is compared with the initial domain name configuration result, and a comparison result of the domain name to be configured is generated.

8. A domain name configuration device, characterized in that: Applied to a content distribution network, the content distribution network includes at least one edge node, and the device includes: A first execution module is configured to obtain a target domain name configuration template from a template information library according to a domain name configuration request sent by a requesting end; A second execution module is configured to generate an initial domain name configuration result according to the configuration content in the domain name configuration request and the target domain name configuration template; a third execution module, configured to convert the initial domain name configuration result and generate a target domain name configuration result; the target domain name configuration result meets the configuration requirements of the edge node; The fourth execution module is configured to send the target domain name configuration result to the target edge node.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images