Business processing method and apparatus, device, computer readable storage medium

Abstract

Embodiments of the present application disclose a service processing method and device, equipment and computer readable storage medium. The service processing method in the embodiments receives a service request sent by a service requester, detects whether a service type corresponding to the service request is a domain name service type, and obtains a detection result. If the detection result indicates that the service type is the domain name service type, a domain name result corresponding to the service request is obtained from a cached domain name result, that is, the cached domain name result corresponding to the service request is directly obtained, so that the obtained domain name result is more accurate, and the service processing flow is reduced, so that the service processing process is faster. Finally, based on the obtaining condition of the domain name result corresponding to the service request, a return strategy of the domain name result corresponding to the service request is determined, and the domain name result is returned to the service requester based on the return strategy, so that the result corresponding to the service request can be quickly and accurately returned.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a service processing method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] With the rapid development of internet services, the number of business requests sent by application terminals is increasing daily. These requests include various business types, such as domain name services and others. Therefore, a business processing method is urgently needed to identify the requested business based on the request, reduce processing steps, and quickly and accurately return the corresponding results. Summary of the Invention

[0003] To address the aforementioned technical problems, embodiments of this application provide a business processing method and apparatus, an electronic device, and a computer-readable storage medium, respectively, to identify the business type corresponding to a business request and quickly and accurately return the result corresponding to the business request.

[0004] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0005] According to one aspect of the embodiments of this application, a business processing method is provided, comprising: receiving a business request sent by a business requester, and detecting whether the business type corresponding to the business request is a domain name business type, and obtaining a detection result; if the detection result indicates that the business type is the domain name business type, then obtaining the domain name result corresponding to the business request from a cached domain name result; wherein the cached domain name result is obtained by caching after the business of the domain name business type is executed; determining a return strategy for the domain name result corresponding to the business request based on the acquisition status of the domain name result corresponding to the business request, and returning the domain name result to the business requester based on the return strategy.

[0006] According to one aspect of the embodiments of this application, a business processing apparatus is provided, comprising: a receiving and detection module configured to receive a business request sent by a business requester, and detect whether the business type corresponding to the business request is a domain name business type, and obtain a detection result; if the detection result indicates that the business type is the domain name business type, then obtaining the domain name result corresponding to the business request from a cached domain name result; wherein the cached domain name result is obtained by caching after the business of the domain name business type is executed; and a returning module configured to determine a returning strategy for the domain name result corresponding to the business request based on the acquisition status of the domain name result corresponding to the business request, and return the domain name result to the business requester based on the returning strategy.

[0007] In another embodiment, the return module is configured to, if the acquisition status indicates that no domain name result corresponding to the business request has been obtained, determine to execute the business corresponding to the business request through a recursive service return strategy to obtain the domain name result corresponding to the business request, and return the obtained domain name result to the business requester; if the acquisition status indicates that a domain name result corresponding to the business request has been obtained, determine to return the obtained domain name result to the business requester through a cache service return strategy.

[0008] In another embodiment, the business processing device further includes a matching storage module, configured to match the caching conditions of the domain name result corresponding to the business request with preset domain name result caching conditions to obtain a matching result; if the matching result indicates a successful match, the domain name result corresponding to the business request is cached to update the cached domain name result.

[0009] In another embodiment, the service processing device further includes a quantity first detection module, configured to detect the quantity of data requested by the service request; if the quantity of data requested by the service request is greater than a preset quantity threshold, then detect whether the service type corresponding to the service request is the domain name service type.

[0010] In another embodiment, the detection module further includes a second detection module, configured to execute the business corresponding to the business request through a recursive service return strategy if the number of data requested by the business request is less than or equal to the preset number threshold, so as to obtain the domain name result corresponding to the business request, and return the obtained domain name result to the business requester.

[0011] In another embodiment, the business processing device further includes a cache update module, configured to count the number of times each domain name result contained in the cached domain name results is retrieved within a preset time period; to take the domain name results whose number of retrievals is less than a preset threshold as target domain name results; and to delete the target domain name results from the cached domain name results.

[0012] In another embodiment, the receiving detection module further includes a recursive service processing unit, configured to execute the service corresponding to the service request through a recursive service return strategy if the detection result indicates that the service type is not the domain name service type, so as to obtain the domain name result corresponding to the service request, and return the obtained domain name result to the service requester.

[0013] According to one aspect of the embodiments of this application, an electronic device is provided, including: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the above-described business processing method.

[0014] According to one aspect of the embodiments of this application, a computer-readable storage medium is also provided, on which computer-readable instructions are stored, which, when executed by a computer's processor, cause the computer to perform the above-described business processing method.

[0015] According to one aspect of the embodiments of this application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned business processing method.

[0016] In the technical solution provided by the embodiments of this application, a business request is received from the business requester, and the business type corresponding to the business request is detected as a domain name business type to obtain a detection result. If the detection result indicates that the business type is a domain name business type, the domain name result corresponding to the business request is obtained from the cached domain name result. The cached domain name result is obtained after the business execution of the domain name business type is completed, that is, the cached domain name result corresponding to the business request is directly obtained, which makes the obtained domain name result more accurate and reduces the business processing steps, making the business processing faster. Finally, based on the acquisition of the domain name result corresponding to the business request, the return strategy of the domain name result corresponding to the business request is determined, and the domain name result is returned to the business requester based on the return strategy, which can quickly and accurately return the result corresponding to the business request.

[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0019] Figure 1 This is a flowchart illustrating a business processing method according to an exemplary embodiment of this application;

[0020] Figure 2 Based on Figure 1 The illustrated embodiment shows a flowchart of another business processing method;

[0021] Figure 3 Based on Figure 2The illustrated embodiment shows a flowchart of another business processing method;

[0022] Figure 4 Based on Figure 1 The illustrated embodiment shows a flowchart of another business processing method;

[0023] Figure 5 Based on Figure 4 The illustrated embodiment shows a flowchart of another business processing method;

[0024] Figure 6 This is a flowchart illustrating the service processing procedure of a Type 65 service request, as shown in another exemplary embodiment of this application.

[0025] Figure 7 This is a schematic diagram of the Local DNS device for business processing in this application;

[0026] Figure 8 This is a schematic diagram of the structure of a service processing apparatus shown in an exemplary embodiment of this application;

[0027] Figure 9 This is a schematic diagram of one implementation environment involved in this application;

[0028] Figure 10 This is a schematic diagram of another implementation environment involved in this application;

[0029] Figure 11 This is a schematic diagram of the structure of a computer system for an electronic device, as illustrated in an exemplary embodiment of this application. Detailed Implementation

[0030] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0031] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0032] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0033] In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0034] Figure 1 This is a flowchart illustrating a business processing method according to an exemplary embodiment of this application. The method includes at least steps S110 to S130, which are described in detail below:

[0035] S110: Receive the business request sent by the business requester, and detect whether the business type corresponding to the business request is a domain name business type, and obtain the detection result.

[0036] The service request sender includes terminals with signal transmission capabilities such as mobile phones, computers, etc. In this embodiment, the service request is a request sent by the user to the operator through the service request sending terminal to activate the relevant service.

[0037] The business type includes various types, such as domain name business type. Specifically, type 65, Apple's iOS terminals, including mobile phones, iPads and PCs, generate a DNS request with a request type (Type) of "HTTPS (HTTPS specific service Endpoints)(65)" in order to prevent DNS hijacking. It is not a regular "A (Host Address)" type request.

[0038] S110 is illustrated by an example. The domain name service type is type65. The system detects whether the service type corresponding to the service request is type65. The detection result represents two cases: the case that is type65 and the case that is not type65.

[0039] S120: If the detection result indicates that the business type is a domain name business type, then obtain the domain name result corresponding to the business request from the cached domain name result; wherein, the cached domain name result is obtained by caching after the business of the domain name business type is executed.

[0040] Specifically, if the domain name business type is type65, and the business type corresponding to the detection business request is type65, then the domain name result corresponding to the type65 business request is obtained from the cached domain name results.

[0041] S130: Based on the acquisition status of the domain name result corresponding to the business request, determine the return strategy for the domain name result corresponding to the business request, and return the domain name result to the business requester based on the return strategy.

[0042] The acquisition status includes two scenarios: successful acquisition and failed acquisition. There are different return strategies for the domain name results for the two scenarios, and the domain name results are returned to the business requester according to their respective return strategies.

[0043] This embodiment receives a business request from the requester and detects whether the business type corresponding to the request is a domain name business type, obtaining a detection result. If the detection result indicates that the business type is a domain name business type, the domain name result corresponding to the business request is obtained from the cached domain name result. The cached domain name result is obtained after the business of the domain name business type is executed, that is, the cached domain name result corresponding to the business request is directly obtained, making the obtained domain name result more accurate and reducing the business processing steps, making the business processing faster. Finally, based on the acquisition of the domain name result corresponding to the business request, the return strategy of the domain name result corresponding to the business request is determined, and the domain name result is returned to the requester based on the return strategy, which can quickly and accurately return the result corresponding to the business request.

[0044] Existing technologies employ the same return strategy to return domain name results to the business requester for various acquisition scenarios. To address different acquisition scenarios, another exemplary embodiment of this application further illustrates how to return domain name results to the business requester, specifically... Figure 2 Based on Figure 1 The illustrated embodiment presents a flowchart of another business processing method. S130 further includes at least S210 to S220, which are detailed below:

[0045] S210: If the status indicator does not show that the domain name result corresponding to the business request is obtained, then the business corresponding to the business request is executed through the recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result is returned to the business requester.

[0046] The recursive service return strategy refers to recursively processing a business request and then returning the processing result to the corresponding business requester.

[0047] If the domain name result corresponding to the business request is not obtained, it means that the cached domain name result does not store the domain name result corresponding to the business request. For example, if the domain name result corresponding to business request a is A, but the cached domain name results only contain B and C, then A is not present in the cached domain name results. In this case, the business corresponding to business request a is executed through a general recursive service return strategy to obtain the domain name result A corresponding to business request a, and the obtained domain name result A is returned to the business requester.

[0048] S220: If the retrieval status indicates that the domain name result corresponding to the business request has been obtained, then the retrieved domain name result will be returned to the business requester through the caching service return strategy.

[0049] The caching service return strategy refers to directly retrieving the domain name result corresponding to the business request from the cached domain name results, and then returning the retrieved domain name result to the corresponding business requester.

[0050] If a domain name result corresponding to the business request is obtained, it means that the cached domain name result contains a domain name result corresponding to the business request. The domain name result corresponding to the business request is directly obtained and sent to the corresponding domain name result for the business request, and then the obtained domain name result is returned to the corresponding business requester.

[0051] This embodiment further illustrates the different return strategies corresponding to different acquisition scenarios. If the domain name result corresponding to the business request is not obtained, the business request needs to be processed recursively, and the domain name result obtained from the recursive processing is returned to the corresponding business requester. If the domain name result corresponding to the business request is obtained, there is no need to parse the business request; the domain name result can be directly sent to the corresponding business requester, reducing the amount of business processing and thus speeding up the business processing process.

[0052] In general business processing, the obtained domain name result is directly returned to the business requester. To fully utilize the obtained domain name result, in another exemplary embodiment of this application, the domain name result is cached. Please refer to [link to relevant documentation] for details. Figure 3 , Figure 3 Based on Figure 2 The illustrated embodiment presents a flowchart of another business processing method. Following S220, the method further includes at least S310 to S320, detailed below:

[0053] S310: Match the caching conditions of the domain name result corresponding to the business request with the preset domain name result caching conditions to obtain the matching result.

[0054] Caching conditions refer to the storage conditions of domain name results. Only when the caching conditions match the preset caching conditions for domain name results can the domain name results be cached.

[0055] S320: If the matching result indicates a successful match, the domain name result corresponding to the business request will be cached to update the cached domain name result.

[0056] For example, if the caching condition for a domain result is A, and the default caching condition for a domain result is also A, then the two conditions match successfully, and the domain result can be cached. If the caching condition for a domain result is A, and the default caching condition for a domain result is B, then the caching condition for the domain result cannot match the default caching condition, indicating that the domain result cannot be cached.

[0057] This embodiment further illustrates the process of caching domain name results. After determining that the obtained domain name results are returned to the business requester through the caching service return strategy, if the caching conditions of the domain name results corresponding to the business request match the preset domain name result caching conditions, in order to make full use of the obtained domain name results and facilitate the subsequent acquisition of the corresponding cached domain name results for new business requests, the domain name results corresponding to the business request are cached, thereby updating the cached domain name results in a timely manner and making subsequent business processing faster.

[0058] When the amount of data requested by a business request is small, a general recursive service return strategy can accurately and effectively return the domain name result to the business requester. However, if the business request is processed according to the business processing methods in the above embodiments, it will waste processing resources and generate unnecessary processing flows. Therefore, in another exemplary embodiment of this application, the amount of data requested by the business request is detected, and an appropriate business processing method is selected based on the quantity detection result. For details, please refer to [link to relevant documentation]. Figure 4 , Figure 4 Based on Figure 1 The illustrated embodiment presents a flowchart of another business processing method. This method further includes steps S410 to S420 in step S110, which are detailed below:

[0059] S410: Detect the amount of data requested by the service request.

[0060] A business request includes at least one request data, which is closely related to the business request. The request data can be data A, data B, data C, etc., and this embodiment does not impose specific limitations.

[0061] S420: If the number of data requested by a business request is greater than a preset threshold, then check whether the business type corresponding to the business request is a domain name business type.

[0062] For example, the requested data includes 3 A data, 2 B data and 1 C data, and the number of requested data is 3+2+1=6. The preset quantity threshold is 5. Obviously, the number of requested data is greater than the preset quantity threshold. Then, it is checked whether the business type corresponding to the business request is a domain name business type.

[0063] This embodiment further refines the business processing process based on the comparison result between the number of data requested by the business request and the preset quantity threshold. By introducing the preset quantity threshold for comparison with the number of data requested by the business request, if it is detected that the number of data requested by the business request is greater than the preset quantity threshold, it is then detected whether the business type corresponding to the business request is a domain name business type. That is, only when the number of requested data exceeds a certain threshold is it detected whether the business type corresponding to the business request is a domain name business type.

[0064] In another exemplary embodiment of this application, the case where the amount of data requested by the business request is less than or equal to a preset quantity threshold is illustrated. Please refer to [link / reference needed] for details. Figure 5 , Figure 5 Based on Figure 4 The illustrated embodiment presents a flowchart of another business processing method. This method further includes S510 after S410, which is detailed below:

[0065] S510: If the number of data requested by the business request is less than or equal to the preset number threshold, the business corresponding to the business request is executed through the recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result is returned to the business requester.

[0066] For example, if the number of data requested by the business request is 4 and the preset data volume threshold is 5, it is clear that the number of data requested by the business request is less than the preset volume threshold. Therefore, the business corresponding to the business request is recursively processed, and the domain name result obtained from the processing is returned to the business requester.

[0067] As the number of cached domain names continues to increase, but the space they occupy is limited, how to optimize the resources of cached domain name results while ensuring normal business processing is an urgent technical problem to be solved. Therefore, another exemplary embodiment of this application is based on the above... Figures 1 to 5 The illustrated embodiment demonstrates another business processing method, which further includes:

[0068] Step (a): Count the number of times each domain name result contained in the cached domain name results is retrieved within the preset time period.

[0069] The preset time period is a time length value, such as 08:00 to 09:00, one day, one month, one year, etc.

[0070] For example, the preset time period is from 08:00 to 09:00, and the domain name results include A, B and C. The number of times A is retrieved, the number of times B is retrieved and the number of times C is retrieved are counted respectively within the period from 08:00 to 09:00.

[0071] Step (b): Domains whose domain results are retrieved less than a preset threshold number of times are selected as target domain results.

[0072] For example, the preset threshold for the number of times is 8, the preset time period is from 08:00 to 10:00, and the domain name results include A, B, and C. Between 08:00 and 10:00, A is retrieved 11 times, B is retrieved 6 times, and C is retrieved 5 times. Since the number of times B and C are retrieved exceeds the preset threshold, B and C are selected as the target domain name results.

[0073] Step (c): Remove the target domain name result from the cached domain name results.

[0074] If the number of times a target domain name result is retrieved within a preset time period is less than a preset threshold, it indicates that it has a low retrieval frequency and is used infrequently. Therefore, cached domain name results with a low retrieval frequency will be deleted, thus leaving sufficient cache space for cached domain name results with a high retrieval frequency.

[0075] This embodiment introduces a preset threshold to evaluate the frequency of retrieval of cached domain name results, and deletes cached domain name results with low retrieval frequency to ensure storage space for cached domain name results with high retrieval frequency.

[0076] In another exemplary embodiment of this application, it is further explained how to perform traffic splitting processing based on the service type corresponding to different service requests. Specifically, based on the above... Figures 1 to 5 The illustrated embodiment demonstrates another business processing method, which further includes:

[0077] Step (d): If the detection result indicates that the business type is not the domain name business type, then execute the business corresponding to the business request through the recursive service return strategy to obtain the domain name result corresponding to the business request, and return the obtained domain name result to the business requester.

[0078] For example, if the business type corresponding to the business request is A and the domain name business type is B, then the business type corresponding to the business request is not the domain name business type. In this case, after recursively processing the business request, the obtained domain name result will be returned to the corresponding business requester.

[0079] This embodiment clarifies the business processing flow when the business type corresponding to the business request is not the domain name business type. That is, after recursively processing the business request, the obtained domain name result is returned to the corresponding business requester, thereby diverting the business processing and making the business processing process more targeted.

[0080] With the rapid development of internet services, Local DNS (Local Domain Name System) is facing a variety of diverse and personalized business requests. In recent years, to prevent DNS (Domain Name System) hijacking, iOS devices, iPads, and PCs have generated DNS requests with a type of HTTPS (HTTPS-specific service endpoints) (65), which is not a regular A (Host Address) request. When processing these types of requests, the Local DNS system often cannot obtain cached domain name results and can only forward the DNS Type 65 request to a recursive service. As the volume of DNS Type 65 requests continues to increase, it poses a significant challenge to the service capacity and stability of the recursive server. Furthermore, the recursive service process for DNS Type 65 requests prolongs DNS request response time and degrades the user experience. Therefore, this application provides another embodiment that utilizes the business processing methods described in the above embodiments to process Type 65 requests. For details, please refer to [link to specific embodiments]. Figure 6 , Figure 6 This is a flowchart illustrating the service processing procedure of a Type 65 service request, as shown in another exemplary embodiment of this application.

[0081] S610: Receives service requests sent by the service requester.

[0082] Please refer to the explanation in S110 above for details.

[0083] S620: Determine whether the business type corresponding to the business request is Type65, and obtain the type determination result.

[0084] Figure 7 This is a schematic diagram of the Local DNS device for business processing in this application, as shown below. Figure 7 As shown, the Local DNS device includes a DNS caching system and a DNS recursive system. The DNS caching system receives DNS service requests sent by the service requester; the DNS recursive system includes a Type 65 detection module, a Type 65 management module, and a Type 65 domain name caching module.

[0085] The Type 65 detection module executes S620. Specifically, this module can perform traffic splitting on DNS service requests, transferring non-Type 65 DNS service requests to the recursive module for service processing. The recursive module then returns the processed domain name results to the DNS caching system, and finally the DNS caching system returns the domain name results to the service requester.

[0086] S630a: If the type determination result indicates that the business type corresponding to the business request is Type65, then the domain name result corresponding to the business request is obtained from the cached domain name result, and it is determined whether the cached domain name result has been obtained.

[0087] If the DNS service request corresponds to the service type Type65, the domain name result corresponding to the DNS service request will be obtained from the cached domain name result. However, not all cached domain name results can be obtained. Therefore, it is necessary to further determine whether the cached domain name result has been successfully obtained.

[0088] Specifically, such as Figure 7 As shown, the Type 65 management module includes a record management unit, a cache management unit, and a policy management unit. The cache management unit can cache domain name results to the Type 65 cache module.

[0089] S630b: If the type determination result indicates that the business type corresponding to the business request is not Type65, then the recursive service return strategy will be executed.

[0090] If the service type corresponding to the DNS service request is not Type65, the service corresponding to the DNS service request will be executed through the recursive service return strategy to obtain the domain name result corresponding to the DNS service request, and the obtained domain name result will be returned to the service requester.

[0091] Specifically, such as Figure 7 As shown, after executing S620, the policy management unit will determine the return policy based on parameters such as the type65 request volume and request density, that is, determine whether to execute the recursive service return policy or the cache service return policy.

[0092] S640a: If a domain name result corresponding to the business request is obtained, the obtained domain name result is returned to the business requester through the caching service return strategy.

[0093] Specifically, if from Figure 7 Once the cache management unit obtains the cached domain name result, the policy management unit will determine the return policy to be executed as the cache service return policy.

[0094] S640b: If the domain name result corresponding to the business request is not obtained, the business corresponding to the business request is executed through the recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result is returned to the business requester.

[0095] If no domain name result corresponding to the DNS service request is obtained, the DNS service request is temporarily transferred and then processed through a normal recursive process. That is, the business corresponding to the DNS service request is executed through the recursive service return strategy to obtain the domain name result corresponding to the DNS service request, and the obtained domain name result is returned to the service requester.

[0096] Specifically, if not from Figure 7 Once the cache management unit obtains the cached domain name result, the policy management unit will determine the return policy to be the recursive service return policy, and transfer the DNS business request to the recursive module for business processing. The recursive module will then return the processed domain name result to the DNS cache system, and finally the DNS cache system will return the domain name result to the business requester.

[0097] S650: Match the caching conditions of the domain name result corresponding to the business request with the preset domain name result caching conditions to obtain the matching result.

[0098] Figure 7 The cache management unit also stores preset domain name result cache conditions. When matching the cache conditions of the domain name result corresponding to the DNS service request with the preset domain name result cache conditions, the preset domain name result cache conditions in the cache management unit are called for matching processing.

[0099] S660: If the matching result indicates a successful match, the domain name result corresponding to the business request will be cached to update the cached domain name result, and the obtained domain name result will be returned to the business requester.

[0100] Specifically, if the caching conditions for the domain name result corresponding to the DNS service request match the preset domain name result caching conditions, the domain name result corresponding to the DNS service request will be cached in [the specified location]. Figure 7 The cache management unit in the system updates the cached domain name results.

[0101] This embodiment applies the various business processing methods in the above embodiments to the Type 65 business processing process, performing traffic splitting detection and cache learning for DNS Type 65 business requests. Specifically, a Type 65 detection module, a Type 65 caching module, and a Type 65 management module are added to the Local DNS recursive system. For short-term repeated Type 65 domain name requests, if the conditions are met, the domain name result can be returned to the business requester immediately, without the need for a step-by-step iterative process, thus reducing the business pressure on the recursive module.

[0102] In addition, this embodiment can also detect the amount of data requested by DNS type65 service requests. When the amount of requested data exceeds a preset threshold, the DNS type65 service requests are diverted, and service processing such as service detection, record management, retrieval of cached domain name results, and caching of domain name results for Type65 services is enabled.

[0103] Another aspect of this application provides a business processing apparatus, such as Figure 8 As shown, Figure 8 This is a schematic diagram illustrating the structure of a service processing apparatus according to an exemplary embodiment of this application. The service processing apparatus includes:

[0104] The receiving and detection module 810 is configured to receive business requests sent by the business requester, detect whether the business type corresponding to the business request is a domain name business type, and obtain the detection result; if the detection result indicates that the business type is a domain name business type, then the domain name result corresponding to the business request is obtained from the cached domain name result; wherein, the cached domain name result is obtained by caching after the business of the domain name business type is executed.

[0105] The return module 830 is configured to determine the return strategy for the domain name result corresponding to the business request based on the acquisition status of the domain name result corresponding to the business request, and return the domain name result to the business requester based on the return strategy.

[0106] In another embodiment, the return module 830 is configured to, if the acquisition status indicates that no domain name result corresponding to the business request has been obtained, determine to execute the business corresponding to the business request through a recursive service return strategy to obtain the domain name result corresponding to the business request, and return the obtained domain name result to the business requester; if the acquisition status indicates that a domain name result corresponding to the business request has been obtained, determine to return the obtained domain name result to the business requester through a cache service return strategy.

[0107] In another embodiment, the service processing apparatus further includes:

[0108] The matching storage module is configured to match the caching conditions of the domain name result corresponding to the business request with the preset domain name result caching conditions to obtain the matching result; if the matching result indicates a successful match, the domain name result corresponding to the business request is cached to update the cached domain name result.

[0109] In another embodiment, the service processing apparatus further includes:

[0110] The quantity detection module is configured to detect the amount of data requested by a business request; if the amount of data requested by a business request is greater than a preset quantity threshold, it will detect whether the business type corresponding to the business request is a domain name business type.

[0111] In another embodiment, the detection module further includes:

[0112] The second detection module is configured to execute the business corresponding to the business request through a recursive service return strategy if the number of data requested by the business request is less than or equal to a preset number threshold, so as to obtain the domain name result corresponding to the business request and return the obtained domain name result to the business requester.

[0113] In another embodiment, the service processing apparatus further includes:

[0114] The cache update module is configured to count the number of times each domain name result in the cached domain name results is retrieved within a preset time period; select domain name results whose number of retrievals is less than a preset threshold as target domain name results; and delete target domain name results from the cached domain name results.

[0115] In another embodiment, the receiving and detection module 810 further includes:

[0116] The recursive service processing unit is configured to execute the business corresponding to the business request through the recursive service return strategy if the detection result indicates that the business type is not the domain name business type, so as to obtain the domain name result corresponding to the business request and return the obtained domain name result to the business requester.

[0117] It should be noted that the business processing apparatus provided in the above embodiments and the business processing method provided in the foregoing embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here.

[0118] Please see Figure 9 , Figure 9 This is a schematic diagram of an implementation environment involved in this application. The implementation environment includes a service requester 100 and a server 200, which communicate with each other via a wired or wireless network.

[0119] The service requester 100 includes, but is not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, in-vehicle terminals, etc. It can be any electronic device capable of sending service requests, such as smartphones, tablets, laptops, computers, etc. There are no restrictions here.

[0120] Server 200 receives a business request from the requesting party and checks whether the business type corresponding to the request is a domain name business type, obtaining the detection result. If the detection result indicates that the business type is a domain name business type, it retrieves the domain name result corresponding to the business request from the cached domain name results. The cached domain name results are obtained after the business of the domain name business type is executed. Based on the retrieval status of the domain name result corresponding to the business request, it determines the return strategy for the domain name result corresponding to the business request and returns the domain name result to the requesting party 100 based on the return strategy. Server 200 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. Multiple servers can form a blockchain, and the server is a node on the blockchain. Server 200 can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. This is not a limitation.

[0121] Figure 10 This is a schematic diagram of another implementation environment involved in this application. Specifically, the service requester 100 sends a service request to the LDNS (Local DNS) caching system in the server 200. The server 200 includes an LDNS caching system, a detection module, a management module, a caching module, and a recursive module.

[0122] The detection module detects the number of business requests and the type of business requests. When the number of business requests exceeds a preset threshold, the above-mentioned business processing methods are activated. If the detection result indicates that the business type is a domain name business type, the domain name result corresponding to the business request is obtained from the cached domain name result, that is, the cached domain name result is obtained from the cache module. If the detection module obtains the cached domain name result corresponding to the business request, the cached domain name result can be temporarily stored in the management module. The management module performs operations such as recording and returns it to the detection module. The detection module then returns the cached domain name result to the LDNS caching system, and finally the LDNS caching system returns it to the business requester 100. If the detection module fails to obtain the cached domain name result corresponding to the business request, it forwards the business request to the recursive module. The recursive module sends the received business request to the root and other levels of domain name services for resolution processing to obtain the domain name result. The recursive module then returns the obtained domain name result to the management module. The management module performs operations such as recording the domain name result and determines whether the caching conditions of the domain name result match the preset domain name result caching conditions. If the match is successful, the domain name result is cached in the caching module and returned to the detection module. The detection module then returns the cached domain name result to the LDNS caching system, and finally the LDNS caching system returns it to the business requester 100.

[0123] Another aspect of this application provides an electronic device, including: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the business processing methods described in the various embodiments above.

[0124] Please see Figure 11 , Figure 11 This is a schematic diagram of the structure of a computer system for an electronic device, illustrating an exemplary embodiment of this application. It shows a schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application.

[0125] It should be noted that, Figure 11 The computer system 1100 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0126] like Figure 11As shown, the computer system 1100 includes a Central Processing Unit (CPU) 1101, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 1102 or programs loaded from storage portion 1108 into Random Access Memory (RAM) 1103. The RAM 1103 also stores various programs and data required for system operation. The CPU 1101, ROM 1102, and RAM 1103 are interconnected via a bus 1104. An Input / Output (I / O) interface 1105 is also connected to the bus 1104.

[0127] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed.

[0128] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit (CPU) 1101, it performs various functions defined in the system of this application.

[0129] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0130] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0131] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0132] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the aforementioned business processing method. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0133] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the business processing methods provided in the various embodiments described above.

[0134] According to one aspect of the embodiments of this application, a computer system is also provided, including a Central Processing Unit (CPU), which can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) or a program loaded from storage into random access memory (RAM), such as performing the methods described above. Various programs and data required for system operation are also stored in the RAM. The CPU, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0135] The following components are connected to the I / O interface: input components including keyboards, mice, etc.; output components including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage components including hard drives; and communication components including network interface cards such as LAN (Local Area Network) cards and modems. The communication components perform communication processing via networks such as the Internet. Drives are also connected to the I / O interface as needed. Removable media, such as disks, optical discs, magneto-optical discs, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage components as required.

[0136] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A business processing method, characterized in that, include: Receive a service request sent by the service requester and detect the amount of data requested by the service request; If the number of data requested by the business request is greater than a preset threshold, then it is detected whether the business type corresponding to the business request is a domain name business type, and the detection result is obtained. If the detection result indicates that the business type is the domain name business type, then the domain name result corresponding to the business request is obtained from the cached domain name result; wherein, the cached domain name result is obtained by caching after the business of the domain name business type is executed; Based on the acquisition status of the domain name result corresponding to the business request, a return strategy for the domain name result corresponding to the business request is determined, and the domain name result is returned to the business requester based on the return strategy. The acquisition status includes successful acquisition and acquisition failure. If the number of data requested by the service request is less than or equal to the preset number threshold, the service corresponding to the service request is executed through a recursive service return strategy to obtain the domain name result corresponding to the service request, and the obtained domain name result is returned to the service requester.

2. The method according to claim 1, characterized in that, The step of determining a return strategy for the domain name result of the business corresponding to the business request based on the acquisition status of the domain name result, and returning the domain name result to the business requester based on the return strategy, includes: If the acquisition status indicates that no domain name result corresponding to the business request is obtained, then it is determined that the business corresponding to the business request will be executed through a recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result will be returned to the business requester. If the acquisition status indicates that a domain name result corresponding to the business request has been obtained, then it is determined that the obtained domain name result will be returned to the business requester through the caching service return strategy.

3. The method according to claim 2, characterized in that, After determining that the obtained domain name result should be returned to the business requester through the caching service return strategy, the method further includes: The caching conditions for the domain name result corresponding to the business request are matched with the preset domain name result caching conditions to obtain the matching result; If the matching result indicates a successful match, the domain name result corresponding to the business request is cached to update the cached domain name result.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The number of times each domain name result contained in the cached domain name results is retrieved within a preset time period is counted; Domains whose domain results are retrieved less than a preset threshold number of times are used as target domain results; Delete the target domain name result from the cached domain name results.

5. The method according to any one of claims 1-3, characterized in that, The method further includes: If the detection result indicates that the business type is not the domain name business type, then the business corresponding to the business request is executed through a recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result is returned to the business requester.

6. A business processing apparatus, characterized in that, include: The receiving and detection module is configured to receive a service request sent by the service requester and detect the amount of data requested by the service request. If the number of data requested by the business request is greater than a preset threshold, then it is detected whether the business type corresponding to the business request is a domain name business type, and the detection result is obtained. If the detection result indicates that the business type is the domain name business type, then the domain name result corresponding to the business request is obtained from the cached domain name result; wherein, the cached domain name result is obtained by caching after the business of the domain name business type is executed; The return module is configured to determine the return strategy for the domain name result corresponding to the business request based on the acquisition status of the domain name result corresponding to the business request, and return the domain name result to the business requester based on the return strategy. The acquisition status includes successful acquisition and acquisition failure. If it is detected that the amount of data requested by the business request is less than or equal to the preset quantity threshold, the business corresponding to the business request is executed through the recursive service return strategy to obtain the domain name result corresponding to the business request, and the obtained domain name result is returned to the business requester.

7. An electronic device, characterized in that, include: Controller; A memory for storing one or more programs, which, when executed by the controller, cause the controller to implement the business processing method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, It stores computer-readable instructions, which, when executed by the computer's processor, cause the computer to perform the business processing method according to any one of claims 1 to 5.

Images