CDN (Content Delivery Network) intelligent scheduling method for reducing client request network abnormity
Through client reporting error information and server data analysis, intelligent scheduling of mobile network requests is realized, automatic switching of cloud service providers and optimized DNS resolution is solved, and the problem of unstable network quality in mobile network requests is reduced, and link timeout is reduced Error rate, improves network access efficiency and stability.
Patent Information
- Application Number
- CN202410969378.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-18
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-07-18
AI Technical Summary
Mobile network requests frequently encounter problems such as link timeout, read and write timeout and handshake errors. The existing CDN services cannot effectively cover the country's area, resulting in unstable network quality. Users need to switch to cloud service providers themselves to optimize network effects, but this process Complex and inefficient.
By reporting error information on the client, server data analysis and archive, calculate the domain name error rate, if the threshold is exceeded, switch to cloud service providers, push high-quality domain names for domain name switching, optimize DNS resolution, provide multiple domain names corresponding to different cloud service providers, and realize Automatically switch between service providers for manual decision-making to reduce network abnormalities.
Real-time analysis and switching cloud service providers, reduce link timeout error rate, optimize user network quality, ensure network stability and reliability, reduce access problems caused by DNS cache errors, and improve network access efficiency.
Smart Images

Figure CN119030856A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of computer technology, and in particular relates to a CDN intelligent scheduling method for reducing network anomalies of client requests. Background Art
[0002] In the era of mobile Internet explosion, the frequency of use of mobile apps has replaced that of PCs, and network access initiated by mobile devices is also flooding the entire network.
[0003] At present, initiating Internet requests from mobile terminals involves many network problems. Due to the diversity of user networks, HTTP connection and communication are severely tested, such as connection timeout, read and write timeout, handshake error, etc. In order to solve these problems, some cloud service providers usually provide CDN services to solve these network problems. The basic principle is to maintain the principle of nearby access. However, in order to achieve this principled goal of nearby access, a lot of technical support is needed behind it, such as DNS intelligent scheduling. If it is based on the premise that intelligent scheduling is relatively accurate, there is generally no problem. However, the IDC computer room of cloud service providers is limited and cannot cover the whole country, even down to the city, district, and county level. Therefore, the result will be cross-city or even cross-province, which will have a great negative impact on the network of mobile phone users. As a customer using cloud services, the network coverage will also be considered. Multiple cloud service providers will be used at the same time to cover the national network as much as possible to solve the network problems of mobile phone users. However, different service providers have different advantages and disadvantages in different regional network conditions, so we need to switch services by ourselves to achieve the best network usage effect, so it needs to be improved. Summary of the invention
[0004] The purpose of the present invention is to provide a CDN intelligent scheduling method for reducing network anomalies of client requests, so as to solve the problems raised in the above background technology.
[0005] In order to achieve the above object, the present invention provides the following technical solution: a CDN intelligent scheduling method for reducing client request network anomalies, the specific steps are as follows:
[0006] Step 1: Data collection (client reporting)
[0007] When a network error occurs on the client, the error is reported immediately; the server provides a log collection interface;
[0008] Step 2: Data Analysis (Server-side Analysis)
[0009] 1. Collect enough samples, archive them by minute according to the rules, and calculate the error rate of each domain name. If it exceeds the predetermined threshold, try to switch the service provider to improve the network quality;
[0010] Analyze regional characteristics. If the characteristics are obvious, proactively push the resolved DNS address of the nearby area based on the collected client information to improve the current regional network problems.
[0011] Analyze the network quality. When the domain name features are obvious, the server intelligently pushes the client to switch the domain name, which is equivalent to switching the cloud service provider.
[0012] When the network connection is abnormal or there are many read and write anomalies, intelligent decision-making will be made, and when the threshold is triggered, the client of the high-quality domain name (operator) will be pushed for switching;
[0013] Second, a single service will provide multiple domain names, each of which will correspond to a different cloud service provider to ensure that the collected data is comparable;
[0014] Step 3: DNS resolution
[0015] The original DNS resolution will first search the local cache. If it exists, it will be used directly. If it does not exist, it will search localDNS. After optimization, the manufacturer's DNS resolution service will be used first. If it is not resolved, it will return to the original path.
[0016] Step 4: Error warning capability
[0017] If the threshold is still exceeded after the automatic strategy is corrected, an alert will be issued to prompt manual intervention;
[0018] Manual decision-making to select cloud service providers;
[0019] Step 5: Manual Decision Making
[0020] Dashboard data analysis provides a basis for decision making.
[0021] Preferably, the interface data dimensions in step one are defined as including basic device information, IP, region, request time, longitude and latitude, error type, domain name, network type, response time, and status code.
[0022] Preferably, the network error occurring in the client in step 1 comprises a DNS resolution error, which is an error occurring when performing domain name resolution.
[0023] Preferably, in step 1, when the user initiates a request and fails to connect to the server, an error message is reported and interface data is collected.
[0024] Preferably, if the threshold is triggered in step 2, and there are many users using the CDN concentrated on the same service provider, then the feature meets the conditions for switching service providers, and the client will be notified to switch to other cloud service providers.
[0025] Preferably, the large-scale failure of the CDN described in step 2 causes the server to be inaccessible. At the same time, due to problems such as local DNS cache, when the user's access is resolved to these failed servers, the client will retry the address a limited number of times. After failing to access, the resolved IP address will be added to the temporary blacklist and synchronized to the server to ensure that the server tells the user not to use the IP when pushing the switch.
[0026] Preferably, when the user initiates a request, the cloud service provider in step 2 will call the service to obtain the optimal IP address instead of directly accessing with the domain name. However, due to the cache of the interface itself, a small number of invalid IPs will be generated, resulting in network access errors. At this time, the client will enter the fault handling process, temporarily clear the IP, and add it to the temporary blacklist.
[0027] Preferably, the DNS in step three needs to update the cache after the resolution is completed, clear the previously cached domain name resolution result, and re-acquire the latest domain name resolution result.
[0028] Preferably, the data in step five include key indicators such as error rate, response time, and domain name switching frequency.
[0029] The beneficial effects of the present invention are as follows:
[0030] When a user cannot connect to the server, an error message will be reported. After accumulating a certain amount of samples, the server will perform real-time analysis and calculation to analyze the regional distribution of the error type. If the threshold is triggered, it will switch to other cloud service providers to change the user's network situation and reduce the link timeout error rate. If there are too many connection timeout nodes, the client will be notified to remove the DNS node from the local cache to reduce the error rate, thereby solving the network connection timeout problem. It can also analyze and exclude weak network users based on regional distribution, user's own network type and other factors, and optimize the network usage of other users. If a small number of users cross the network, resulting in slow reading and writing or even timeouts, if obvious distribution features can be extracted, the server will push adjustments based on the network situation of the best cloud service provider at the time, and can enter the fault handling process when there are large-scale CDN failures and DNS cache errors, thereby ensuring the user's network quality. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] Figure 1 It is a schematic diagram of the business process diagram of the present invention;
[0032] Figure 2 It is a schematic diagram of the request processing process of the present invention;
[0033] Figure 3 It is a schematic diagram of the DNS resolution process of the present invention. DETAILED DESCRIPTION
[0034] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0035] like Figures 1 to 3 As shown, the embodiment of the present invention provides a CDN intelligent scheduling method for reducing client request network anomalies, and the specific steps are as follows:
[0036] Step 1: Data collection (client reporting)
[0037] When a network error occurs on the client, the error is reported immediately; the server provides a log collection interface;
[0038] Step 2: Data Analysis (Server-side Analysis)
[0039] 1. Collect enough samples, archive them by minute according to the rules, and calculate the error rate of each domain name. If it exceeds the predetermined threshold, try to switch the service provider to improve the network quality;
[0040] Analyze regional characteristics. If the characteristics are obvious, proactively push the resolved DNS address of the nearby area based on the collected client information to improve the current regional network problems.
[0041] Analyze the network quality. When the domain name features are obvious, the server intelligently pushes the client to switch the domain name, which is equivalent to switching the cloud service provider.
[0042] When the network connection is abnormal or there are many read and write anomalies, intelligent decision-making will be made, and when the threshold is triggered, the client of the high-quality domain name (operator) will be pushed for switching;
[0043] Second, a single service will provide multiple domain names, each of which will correspond to a different cloud service provider to ensure that the collected data is comparable;
[0044] Step 3: DNS resolution
[0045] The original DNS resolution will first search the local cache. If it exists, it will be used directly. If it does not exist, it will search localDNS. After optimization, the manufacturer's DNS resolution service will be used first. If it is not resolved, it will return to the original path.
[0046] Step 4: Error warning capability
[0047] If the threshold is still exceeded after the automatic strategy is corrected, an alert will be issued to prompt manual intervention;
[0048] Manual decision-making to select cloud service providers;
[0049] Step 5: Manual Decision Making
[0050] Dashboard data analysis provides a basis for decision making.
[0051] By collecting data on clients where network errors occur, we can automatically switch service providers based on the network error rate to ensure that users have good network quality. When the client network connection is abnormal or there are many read and write exceptions, after the threshold is triggered, the client will be automatically provided with a high-quality domain name to ensure the user's network quality. When the requirements cannot be met after the policy is revised, an early warning will be triggered and manual intervention will be allowed to select a cloud service provider to ensure the stability and reliability of the service.
[0052] Among them, the interface data dimension in step one is defined as including basic device information, IP, region, request time, longitude and latitude, error type, domain name, network type, response time, and status code.
[0053] By collecting data from various aspects, the error rate of each domain name can be calculated more accurately.
[0054] The network error occurring on the client in step 1 includes a DNS resolution error, which is an error occurring during domain name resolution.
[0055] DNS resolution errors are caused by DNS server failures, domain name resolution errors, etc.
[0056] Among them, in step one, when the user initiates a request and cannot connect to the server, an error message will be reported and the interface data will be collected at the same time.
[0057] By collecting interface data, it is possible to automatically switch between multiple cloud service providers to improve the network quality of mobile phone users' APP requests.
[0058] If the threshold is triggered in step 2, and there are many users using the CDN concentrated on the same service provider, then the feature meets the conditions for switching service providers, and the client will be notified to switch to other cloud service providers.
[0059] By notifying the client to switch to other cloud service providers, the user's network situation can be changed to reduce the link timeout error rate.
[0060] Among them, in step 2, a large-scale CDN failure causes the server to be inaccessible. At the same time, due to problems such as local DNS cache, when user access is resolved to these failed servers, the client will retry the address a limited number of times. If it cannot be accessed, the resolved IP address will be added to the temporary blacklist and synchronized to the server to ensure that the server tells the user not to use the IP when pushing the switch.
[0061] The client will retry the blacklist every 5 minutes. If it recovers, it will be removed from the blacklist to ensure that the IP is valid.
[0062] Among them, in step 2, when the user initiates a request, the cloud service provider will call the service to obtain the optimal IP address instead of directly accessing with the domain name. However, due to the cache of the interface itself, a small number of invalid IPs will be generated, resulting in network access errors. At this time, the client will enter the fault handling process, temporarily clear the IP, and add it to the temporary blacklist.
[0063] After being included in the temporary blacklist, the client will periodically retry to remove it, to maximize the guarantee that users are using valid resolution results.
[0064] Among them, in step three, after the DNS resolution is completed, it needs to update the cache, clear the previously cached domain name resolution results, and re-acquire the latest domain name resolution results.
[0065] By giving priority to the manufacturer's DNS resolution service, the advantage is that the accuracy and timeliness of the resolution are guaranteed with a high probability, allowing users to obtain the optimal access path.
[0066] Among them, the data in step five include key indicators such as error rate, response time, and domain name switching frequency.
[0067] By analyzing the data, it provides rich basis for decision-making and also provides data support for future scheduling strategy optimization.
[0068] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.
[0069] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.
Claims
1. A CDN intelligent scheduling method for reducing client request network anomalies, characterized by: The specific steps are as follows: Step 1: Data collection (client reporting) When a network error occurs on the client, the error is reported immediately; The server provides a log collection interface; Step 2: Data Analysis (Server-side Analysis) 1. Collect enough samples, archive them by minute according to the rules, and calculate the error rate of each domain name. If it exceeds the predetermined threshold, try to switch the service provider to improve the network quality; Analyze regional characteristics. If the characteristics are obvious, proactively push the resolved DNS address of the nearby area based on the collected client information to improve the current regional network problems. Analyze the network quality. When the domain name features are obvious, the server intelligently pushes the client to switch the domain name, which is equivalent to switching the cloud service provider. When the network connection is abnormal or there are many read and write anomalies, intelligent decision-making will be made, and when the threshold is triggered, the client of the high-quality domain name (operator) will be pushed for switching; Second, a single service will provide multiple domain names, each of which will correspond to a different cloud service provider to ensure that the collected data is comparable; Step 3: DNS resolution The original DNS resolution will first search the local cache. If it exists, it will be used directly. If it does not exist, it will search localDNS. After optimization, the manufacturer's DNS resolution service will be used first. If it is not resolved, it will return to the original path. Step 4: Error warning capability If the threshold is still exceeded after the automatic strategy is corrected, an alert will be issued to prompt manual intervention; Manual decision-making to select cloud service providers; Step 5: Manual Decision Making Dashboard data analysis provides a basis for decision making.
2. According to claim 1, a CDN intelligent scheduling method for reducing client request network anomalies is characterized by: The interface data dimensions described in step 1 are defined as including basic device information, IP, region, request time, longitude and latitude, error type, domain name, network type, response time, and status code.
3. According to claim 1, a CDN intelligent scheduling method for reducing client request network anomalies is characterized by: The network error on the client described in step 1 includes a DNS resolution error, which is an error that occurs when resolving the domain name.
4. According to claim 1, a CDN intelligent scheduling method for reducing client request network anomalies is characterized in that: As described in step 1, when the user initiates a request and fails to connect to the server, an error message will be reported and the interface data will be collected.
5. According to claim 1, a CDN intelligent scheduling method for reducing client request network anomalies is characterized in that: If the threshold is triggered as described in step 2, and there are many users who use the CDN concentrated on the same service provider, then the feature meets the conditions for switching service providers, and the client will be notified to switch to other cloud service providers.
6. According to claim 1, a CDN intelligent scheduling method for reducing client request network anomalies is characterized by: The large-scale failure of CDN described in step 2 makes the server inaccessible. At the same time, due to problems such as local DNS cache, when user access is resolved to these failed servers, the client will retry the address a limited number of times. If it cannot be accessed, the resolved IP address will be added to the temporary blacklist and synchronized to the server to ensure that the server tells the user not to use the IP when pushing the switch.
7. The CDN intelligent scheduling method for reducing client request network anomalies according to claim 1, characterized in that: When the user initiates a request as described in step 2, the cloud service provider will call the service to obtain the optimal IP address instead of directly accessing it with the domain name. However, due to the cache of the interface itself, a small number of invalid IPs will be generated, resulting in network access errors. At this time, the client will enter the fault handling process, temporarily clear the IP, and add it to the temporary blacklist.
8. The CDN intelligent scheduling method for reducing client request network anomalies according to claim 1, characterized in that: After the DNS resolution is completed in step 3, it is necessary to update the cache, clear the previously cached domain name resolution results, and re-acquire the latest domain name resolution results.
9. The CDN intelligent scheduling method for reducing client request network anomalies according to claim 1, characterized in that: The data described in step five include key indicators such as error rate, response time, and domain name switching frequency.
Citation Information
Patent Citations
Domain name system (DNS) message processing method and network safety equipment
CN102223422A
Domain name resolution system, domain name resolution server and domain name resolution method
CN107071078A
CDN scheduling algorithm and system based on network delay
CN110708385A
Acceleration method for App to access nodes
CN116567085A
Multi-uplink network connectivity detection method and device, and storage medium
CN117478541A
