A method, apparatus, device, and storage medium for handling access point handover anomalies.

Abstract

This invention discloses a method, apparatus, device, and storage medium for handling access point switching anomalies, to solve the problem of connection anomalies when frequently switching wireless access points. The method includes: after a terminal device sends a connection request to a wireless access point, if the terminal device does not receive a response to the connection request, parsing the terminal device's wireless driver log to obtain the abnormal error appearing in the wireless driver log; determining whether the abnormal error is an authentication failure; if so, capturing the data packet sent by the wireless access point to the terminal device; determining whether the data packet is valid; if invalid, intercepting the data packet to handle access point switching anomalies caused by authentication failure due to invalid data packets.

Description

Technical Field

[0001] This invention relates to the field of network technology, and in particular to a method, apparatus, device, and storage medium for handling access point switching anomalies. Background Technology

[0002] With the rapid development of mobile internet, we are using more and more wireless access points in our daily lives. In order to maintain a good and stable wireless signal, there are often multiple wireless access points in the same location, so that when one wireless access point has a poor connection, users can switch to another nearby wireless access point in time.

[0003] However, when users switch between different wireless access points, connection failures occasionally occur. The probability of failure increases when users switch frequently. This often leads to users being unable to choose the most suitable wireless access point based on their own needs due to access point connection problems. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and storage medium for handling access point switching anomalies, in order to solve the problem of connection anomalies when frequently switching wireless access points.

[0005] A method for handling access point handover anomalies, comprising:

[0006] After the terminal device sends a connection request to the wireless access point, if the terminal device does not receive a response to the connection request, the wireless driver log of the terminal device is parsed to obtain the abnormal error that occurred in the wireless driver log.

[0007] Determine whether the abnormal error indicates an authentication failure;

[0008] If so, capture the data packets sent by the wireless access point to the terminal device;

[0009] Determine whether the data packet is valid. If it is invalid, intercept the data packet to handle the access point switching anomaly caused by authentication failure due to the invalid data packet.

[0010] In one possible design, parsing the wireless driver log of the terminal device to determine the abnormal errors appearing in the wireless driver log includes:

[0011] In the wireless driver log, preset abnormal keywords are filtered to obtain the main abnormal keywords that have appeared in the wireless driver log;

[0012] Identify the exception errors corresponding to the main exception keywords.

[0013] In one possible design, determining whether the abnormal error is an authentication failure includes:

[0014] Determine whether the abnormal error includes an authentication timeout;

[0015] If it is included, then determine whether the abnormal error contains a cancellation authorization instruction to confirm whether the abnormal error is an authentication failure.

[0016] In one possible design, before determining whether the abnormal error contains a deauthorization instruction, the method further includes:

[0017] Determine whether the wireless driver log contains keywords indicating completion of authentication password transmission;

[0018] If not included, packet capture logs in the communication channel are obtained to determine whether the wireless access point responded to the connection request sent by the terminal device.

[0019] In one possible design, after the terminal device does not receive a response to the connection request, the method further includes:

[0020] Determine whether the wireless driver log contains the keyword "connection successful";

[0021] If present, the host configuration protocol log of the terminal device is retrieved to determine whether the access point switching anomaly occurred during the host configuration protocol phase.

[0022] In one possible design, before determining whether the wireless driver log contains a connection success keyword, the method further includes:

[0023] The number of requests initiated by the terminal device to the wireless access point within the expected time period is counted.

[0024] Distinguish between the number of successful connections and the number of failed connections in the aforementioned request count;

[0025] Calculate the ratio of the number of failed connections to the number of requests to obtain the failure probability;

[0026] If the failure probability is greater than the expected probability, then the wireless access point is determined to be abnormal due to frequent switching.

[0027] In one possible design, the number of requests initiated by the terminal device to the wireless access point within the expected statistical time period includes:

[0028] In the wireless driver log, the number of times the preset wireless connection point name appears within the expected time period is counted to obtain the number of requests.

[0029] An access point switching anomaly handling device, comprising:

[0030] The parsing module is used to parse the wireless driver log of the terminal device after the terminal device sends a connection request to the wireless access point, and if the terminal device does not receive a response to the connection request, then the module can deduce the abnormal errors that occur in the wireless driver log.

[0031] The judgment module is used to determine whether the abnormal error is an authentication failure;

[0032] A capture module, configured to capture data packets sent by the wireless access point to the terminal device if the condition is met;

[0033] The interception module is used to determine whether the data packet is valid. If it is invalid, the data packet is intercepted to handle the access point handover anomaly caused by the invalid data packet.

[0034] An apparatus includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the above-described access point switching exception handling method.

[0035] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described access point switching exception handling method.

[0036] The aforementioned method, apparatus, device, and storage medium for handling access point switching anomalies, after a terminal device sends a connection request to a wireless access point, if the terminal device does not receive a response to the connection request, it parses the terminal device's wireless driver log to identify any abnormal errors appearing in the wireless driver log; it determines whether the abnormal error is an authentication failure; if so, it captures the data packets sent by the wireless access point to the terminal device; it determines whether the data packets are valid; if invalid, it intercepts the data packets to handle access point switching anomalies caused by authentication failure due to invalid data packets. This method accurately and efficiently confirms the cause of wireless access point anomalies by parsing the driver log, and then judges the validity of data packets for abnormal errors and intercepts invalid data packets, preventing the program from being abnormally disconnected due to invalid data packets. This efficiently and accurately solves the problem of users frequently switching wireless access points and encountering anomalies that prevent them from connecting to the wireless access point. Attached Figure Description

[0037] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram of an application environment for a method for handling access point switching anomalies according to an embodiment of the present invention;

[0039] Figure 2 This is a flowchart illustrating a method for handling access point switching anomalies in one embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of a device for handling access point switching anomalies in one embodiment of the present invention;

[0041] Figure 4 This is a schematic diagram of a device in one embodiment of the present invention. Detailed Implementation

[0042] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0043] The access point handover anomaly handling method provided in this embodiment of the invention can be applied to, for example... Figure 1 The application environment shown is illustrated. Specifically, this access point handover exception handling method is applied in a wireless network system, which includes, for example, [example of such system]. Figure 1 The diagram illustrates a wireless access point and terminal device. The terminal device communicates with the wireless access point via a network to troubleshoot and resolve frequent anomalies of the wireless access point, thereby restoring the wireless network connection. The terminal device includes, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices—any device capable of connecting to a wireless access point. A wireless access point (AP) is a device in a computer network that connects a wireless network to a wired network; it is also known as a wireless base station. It is typically a standalone device connected to a router via a wired network, or it can be integrated with a router.

[0044] In one embodiment, such as Figure 2 As shown, a method for handling access point handover anomalies is provided, which is applied to... Figure 1 Taking a wireless network system as an example, the following steps are included:

[0045] S10: After the terminal device sends a connection request to the wireless access point, if the terminal device does not receive a response to the connection request, the terminal device's wireless driver log is parsed to determine the abnormal error that occurred in the wireless driver log.

[0046] The connection request of a terminal device to a wireless access point refers to all the request steps before connecting to the wireless access point, including but not limited to probe request, probe request response, association request, association request response, four-way handshake access authentication, etc.

[0047] If the terminal device does not receive a response to the connection request—that is, after sending a connection request to the wireless access point, the terminal device does not receive a response from the wireless access point—it cannot establish a wireless network connection. In this case, the terminal device cannot determine whether the connection request was sent successfully. Therefore, it is necessary to analyze the terminal device's wireless driver logs to deduce possible causes of the wireless network failure from the abnormal errors appearing in the wireless driver logs. These abnormal errors include, but are not limited to, exception messages, exception keywords, and exception status codes appearing in the wireless driver logs.

[0048] S20: Determine whether the abnormal error is an authentication failure.

[0049] Since possible causes of abnormal wireless network handover include, but are not limited to, authentication failure, password transmission failure, and data packet decryption failure, this embodiment, after executing step S10 multiple times, confirms that the abnormal error usually occurs as authentication failure in this scenario. Therefore, in step S20, that is, after obtaining the abnormal error in the wireless driver log, it is first determined whether the abnormal error is authentication failure.

[0050] S30: If so, capture the data packets sent by the wireless access point to the terminal device.

[0051] When determining whether an abnormal error is an authentication failure, all data packets sent from the wireless access point to the terminal device are captured in the path where the abnormal error is an authentication failure, so that subsequent steps can judge and process the data packets.

[0052] S40: Determine whether the data packet is valid. If it is invalid, intercept the data packet to handle the access point switching anomaly caused by authentication failure due to the invalid data packet.

[0053] The system determines whether all data packets captured in step S30 are valid. If any are invalid, they are intercepted. This ensures that subsequent procedures can continue even when other valid data packets are received, preventing authentication failures caused by invalid data packets and thus avoiding access point switching anomalies. Specifically, the validity of received data packets is determined according to the 80211 protocol stack definition. After receiving a data packet, it is decrypted using the password negotiated during the previous four-way handshake protocol. If decryption is successful, the data packet is considered valid; otherwise, it is considered invalid.

[0054] In traditional solutions, if an invalid data packet is captured, the wireless network is immediately disconnected. This causes abnormal wireless access point switching, which is the main reason for connection failures after frequent switching. Therefore, step S40 employs an alternative method: intercepting invalid data packets. Because invalid data packets are intercepted, valid data packets will continue to be processed, and the wireless network connection will be maintained. The method for intercepting data packets can be to destroy invalid data packets or to establish a dual-channel execution, with one channel receiving valid data packets and the other receiving invalid data packets; this is not limited here.

[0055] It should be noted that this method for handling wireless access point switching anomalies accurately and efficiently identifies the cause of the anomaly by parsing the driver logs. Then, it judges the legality of the data packets for the anomaly and blocks invalid data packets, preventing the program from being affected by invalid data packets and disconnecting abnormally. This efficiently and accurately solves the problem of users frequently switching wireless access points and encountering anomalies that prevent them from connecting to the wireless access point.

[0056] In one embodiment, step S10, namely parsing the wireless driver log of the terminal device to obtain the abnormal errors that occur in the wireless driver log, specifically includes the following steps:

[0057] S11: In the wireless driver log, filter preset abnormal keywords to obtain the main abnormal keywords that have appeared in the wireless driver log.

[0058] S12: Determine the exception error corresponding to the main exception keyword.

[0059] In this embodiment, preset abnormal keywords are used, and then the wireless driver log is filtered to determine whether these keywords appear, thereby identifying the main abnormal keywords that have appeared in the log. The preset abnormal keywords refer to abnormal keywords set according to expected abnormal issues, including but not limited to error message keywords, error reason prompts, abnormal status codes, and frequently recurring abnormal keywords in the wireless driver log. The main abnormal keywords refer to all or some of the abnormal keywords filtered from the wireless driver log; the keyword filtering conditions can be set according to actual conditions.

[0060] Next, by identifying the abnormal errors corresponding to the main abnormal keywords, the cause of the wireless access point handover abnormality was determined.

[0061] For example, the wireless driver log can be filtered for preset exception keywords "auth timeout" and "issue_deauth reason". Based on the filtering results, it can be determined whether the above exception keywords appear in the log. If the filtering results show "auth timeout", the main exception keyword is authentication timeout. If the filtering results show "issue_deauth reason", the main exception keyword is that the terminal device driver judges that the data packet received from the wireless access point is invalid, and the terminal device actively initiates disconnection.

[0062] In one embodiment, in step S11, the filtered abnormal keywords can be further filtered according to a preset threshold or condition to select the main abnormal keywords. If, in the above example, the filtering results contain both the abnormal keywords "auth timeout" and "issue_deauth reason", then the most prominent of the two abnormal keywords is selected as the main abnormal keyword using a preset threshold.

[0063] For example, in another possible scenario, if the filter results contain the abnormal keyword "issue_deauth reason", the preset conditions can be used to filter out the preset keyword "tw_cfg80211_indicate_disconnect(wlan0),reason=1". Based on the above two keywords, the current network disconnection is caused by the terminal device's wireless driver actively disconnecting.

[0064] It should be noted that since the keywords of the wireless network connection at different stages will correspond to different abnormal errors, in the scenario of frequently switching wireless access points, based on the possible abnormal errors, the abnormal keywords are preset, and then the cause of the abnormality of the wireless access point is determined by filtering whether the relevant keywords appear in the wireless driver log. This improves the efficiency of determining the cause of the abnormality caused by frequent switching of wireless access points, and makes the subsequent handling of wireless access point abnormalities more efficient and simple.

[0065] In one embodiment, step S20, which determines whether the abnormal error is an authentication failure, specifically includes the following steps:

[0066] S21: Determine whether the abnormal error includes authentication timeout.

[0067] S22: If it is included, determine whether the abnormal error contains a cancellation authorization instruction to confirm whether the abnormal error is an authentication failure.

[0068] Since authentication failure can be caused by various factors such as authentication timeout, receiving a cancellation instruction, and data packet reception failure, in this embodiment, considering the scenario of frequent wireless access point switching, the most likely causes are authentication timeout and receiving a cancellation instruction. Furthermore, because a cancellation instruction may affect the determination of authentication success or failure, it is essential to ensure that no cancellation instruction has been received when confirming the cause of authentication failure. Therefore, in steps S21-S22, it is first determined whether an authentication timeout has occurred, and then whether a cancellation instruction is included. If an authentication timeout has occurred but no cancellation instruction has been received, it can be confirmed that the cause of the current anomaly due to frequent wireless access point switching is authentication timeout.

[0069] It should be noted that while authentication timeout is the main cause of authentication failure, the cancellation of authorization command will affect the determination of this main cause. Therefore, after determining whether the authentication failure-related keywords are included, it is also necessary to determine whether the cancellation of authorization command-related keywords are included in order to accurately determine the cause of the wireless access point's anomaly and ensure that subsequent handling of the anomaly cause is efficient and accurate.

[0070] In one embodiment, before step S22, i.e. before determining whether the abnormal error contains a revocation instruction, the method for handling access point switching abnormalities further includes the following steps:

[0071] S51: Determine whether the wireless driver log contains keywords indicating the completion of authentication password transmission.

[0072] S52: If not included, obtain packet capture logs in the communication channel to determine whether the wireless access point responded to the connection request sent by the terminal device.

[0073] Before determining whether the abnormal error contains a deauthorization instruction, in one embodiment, another possibility of an abnormal error is also ruled out: failure to complete the password transmission during the four-way handshake phase of network transmission.

[0074] Because network transmission involves not only authentication and association but also password transmission, when a terminal device sends a connection request frame to a wireless access point, this frame contains the terminal device's MAC address (Media Access Control Address) and the MAC address of the wireless access point to which it wants to connect. Next, upon receiving the connection request frame, the wireless access point sends a connection response frame to the terminal device as an acknowledgment. This frame contains a session identifier, which will be used for subsequent communication, as well as some other connection parameters. Then, upon receiving the connection response frame, the terminal device sends an association request frame to the wireless access point. This frame contains the terminal device's authentication information, including but not limited to the SSID (Service Set Identifier), security keys, and the previously obtained session identifier. Finally, upon receiving the association request frame, the wireless access point sends an association response frame to the terminal device. This frame contains the result of the terminal device's authentication and other association parameters. At this point, the wireless network connection has been established, and the terminal device and the wireless access point can communicate. At this point, the wireless driver log will list keywords including, but not limited to, "1 / 4EAPOL key", "2 / 4EAPOL key", "3 / 4EAPOL key", and "4 / 4EAPOL key", which are the keywords for completing the authentication password transmission in step S51. Filtering these keywords in the wireless driver log can determine whether the password transmission was successful.

[0075] For example, the preset abnormal keywords "2 / 4EAPOL key" and "1 / 4EAPOL key" can be filtered in the wireless driver log to determine whether the authentication password has been successfully transmitted.

[0076] If no relevant keywords are found, in step S52, the packet capture log (snifferlog) in the communication channel is obtained, and a preset keyword search is performed in the packet capture log to determine whether the wireless access point responded to the connection request sent by the terminal device. For example, the packet capture log before the wireless access point encountered an anomaly is searched to see if the keyword "__cfg80211_connect_result" appears. If it appears, it means that the wireless access point responded to the connection request sent by the terminal device; if it does not appear, it means that it did not respond.

[0077] It should be noted that, since password transmission failure is usually one of the reasons for anomalies in wireless access points, it is necessary to rule out this cause to ensure the accuracy of the final cause of the anomaly, so that subsequent handling of the anomaly can be efficient and accurate.

[0078] In one embodiment, step S10, i.e., after the terminal device does not receive a response to the connection request, the method for handling the access point handover exception further includes the following steps:

[0079] S51: Determine whether the wireless driver log contains the keyword "connection successful".

[0080] S52: If it exists, retrieve the host configuration protocol log to determine whether the access point switching anomaly occurred during the host configuration protocol phase.

[0081] In this embodiment, after the terminal device does not receive a response to the connection request, that is, after the terminal device cannot confirm whether the wireless access point has received the connection request, step S51 determines whether the wireless driver log contains a connection success keyword in order to confirm whether the connection request was sent successfully. For example, the preset connection success keyword is "set group key". If this keyword is included, it means that the wireless driver connection is successful, and the wireless network connection will then enter the DHCP (Dynamic Host Configuration Protocol) stage.

[0082] Therefore, in step S52, the DHCP log, i.e. the host configuration protocol log, is obtained to determine whether the wireless access point contains preset keywords before the abnormality occurs.

[0083] Upon entering the DHCP phase, the terminal device broadcasts a DHCP Discovery packet, inquiring which DHCP servers can provide an IP address and other network parameters. Next, the DHCP server, upon receiving the DHCP Discover packet, replies with a DHCP Offer packet, containing a set of IP addresses and other network parameters that the terminal device can use, such as subnet mask, gateway, and DNS server. Then, the terminal device, upon receiving the DHCP Offer packet, selects an IP address and sends a DHCP Request packet to the DHCP server providing that address, requesting that address be assigned. At this point, other DHCP servers will stop the terminal device from requesting the address. Finally, the DHCP server, upon receiving the DHCP Request packet, replies with a DHCP Acknowledge packet, confirming that the IP address has been assigned to the terminal device and providing the other network parameters. After receiving the DHCP Acknowledge packet, the terminal device configures its network interface using the provided IP address and other network parameters. Therefore, by analyzing the different keywords appearing in the DHCP logs at different stages, it is possible to determine at which stage the DHCP network anomaly occurred.

[0084] It should be noted that since the wireless driver log excludes wireless access point anomalies caused by wireless driver malfunctions, in addition to determining the wireless driver's anomaly, it is necessary to ensure that the wireless driver itself has received the connection request to prevent incorrect anomaly determination due to the wireless driver not receiving the connection request. On the other hand, it is also necessary to track the subsequent network connection steps after the wireless driver completes the connection, i.e., the network connection status during the DHCP phase, to ensure the accuracy of the finally determined cause of the wireless access point anomaly, so as to handle the cause of the anomaly efficiently and accurately in subsequent steps.

[0085] In one embodiment, before step S51, i.e. before determining whether the wireless driver log contains a connection success keyword, the method for handling access point switching anomalies further includes the following steps:

[0086] S61: Count the number of requests initiated by the terminal device to the wireless access point within the expected time period.

[0087] S62: Distinguish between the number of successful connections and the number of failed connections in the number of requests.

[0088] S63: Calculate the ratio of the number of failed connections to the number of requests to obtain the failure probability.

[0089] S64: If the failure probability is greater than the expected probability, then it is determined that the wireless access point is abnormal due to frequent switching.

[0090] In one embodiment, before determining whether the wireless driver log contains a connection success keyword, it is necessary to first count the number of requests made by the wireless access point within the expected time period, distinguish between successful and failed connections within the request count, and calculate the ratio of the number of failed connections to the cumulative number of requests to determine the probability of connection failure. If the failure probability is greater than the probability of failure, it is determined that the wireless access point is malfunctioning due to frequent handovers.

[0091] It should be noted that since the problem scenario handled in this embodiment is an anomaly caused by the terminal device frequently switching wireless access points, it is necessary to determine that the current anomaly is caused by frequent switching of wireless access points during the anomaly confirmation process. Therefore, this embodiment ensures that the current anomaly is caused by frequent switching of wireless access points by counting the number of requests sent by the terminal device to the wireless access point, thereby ensuring the accuracy of the anomaly cause and enabling accurate and efficient anomaly handling in the future.

[0092] In one embodiment, step S61, which involves counting the number of requests initiated by the terminal device to the wireless access point within a specified time period, specifically includes the following steps:

[0093] S611: In the wireless driver log, count the number of times the preset wireless connection point name appears within the expected time period to obtain the number of requests.

[0094] When counting the number of requests within a given time period, you can count the number of times the wireless access point name appears in the wireless driver log within that time period and use that number of appearances as the request count to determine whether multiple requests were initiated in a short period of time.

[0095] For example, if the wireless access point name is "new candidate", then the keyword "new candidate" is preset, and all occurrences of this keyword are filtered in the wireless driver log, and the number of times this keyword appears is counted as the number of requests.

[0096] It should be noted that since the wireless driver log records the name of the wireless access point for each connection and the connection time, this feature can be used to count the wireless access points connected within the expected time. This ensures that the current cause of the anomaly is due to frequent switching of wireless access points, thus ensuring the accuracy of the anomaly cause finding and enabling accurate and efficient anomaly handling in the future.

[0097] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0098] In one embodiment, an access point handover anomaly handling device is provided, which corresponds one-to-one with the access point handover anomaly handling method in the above embodiments. For example... Figure 3 As shown, the access point switching anomaly handling device includes a parsing module 10, a judgment module 20, a capture module 30, and an interception module 40. Detailed descriptions of each functional module are as follows:

[0099] The parsing module 10 is used to parse the wireless driver log of the terminal device and obtain the abnormal error that occurred in the wireless driver log if the terminal device does not receive a response to the connection request after the terminal device sends a connection request to the wireless access point.

[0100] The judgment module 20 is used to determine whether the abnormal error is an authentication failure;

[0101] The capture module 30 is configured to capture, if yes, the data packets sent by the wireless access point to the terminal device;

[0102] The interception module 40 is used to determine whether the data packet is valid. If it is invalid, the data packet is intercepted to handle the access point switching anomaly caused by the invalid data packet.

[0103] Specific limitations regarding the access point handover anomaly handling device can be found in the limitations of the access point handover anomaly handling method described above, and will not be repeated here. Each module in the aforementioned access point handover anomaly handling device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the operations corresponding to each module.

[0104] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 4 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores temporary and final data generated during the execution of the computer programs, such as preset exception keywords and expected times. The network interface is used to communicate with external terminals via a network connection. When executed by the processor, the computer program implements a method for handling access point switching exceptions.

[0105] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0106] After the terminal device sends a connection request to the wireless access point, if the terminal device does not receive a response to the connection request, the wireless driver log of the terminal device is parsed to obtain the abnormal error that occurred in the wireless driver log.

[0107] Determine whether the abnormal error indicates an authentication failure;

[0108] If so, capture the data packets sent by the wireless access point to the terminal device;

[0109] Determine whether the data packet is valid. If it is invalid, intercept the data packet to handle the access point switching anomaly caused by authentication failure due to the invalid data packet.

[0110] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0111] After the terminal device sends a connection request to the wireless access point, if the terminal device does not receive a response to the connection request, the wireless driver log of the terminal device is parsed to obtain the abnormal error that occurred in the wireless driver log.

[0112] Determine whether the abnormal error indicates an authentication failure;

[0113] If so, capture the data packets sent by the wireless access point to the terminal device;

[0114] Determine whether the data packet is valid. If it is invalid, intercept the data packet to handle the access point switching anomaly caused by authentication failure due to the invalid data packet.

[0115] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0116] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0117] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for handling access point handover anomalies, characterized in that, include: After the terminal device sends a connection request to the wireless access point, if the terminal device does not receive a response to the connection request, the wireless driver log of the terminal device is parsed to obtain the abnormal error that occurred in the wireless driver log. Determine whether the abnormal error indicates an authentication failure; If so, capture the data packets sent by the wireless access point to the terminal device; The system determines whether the data packet is valid. If it is invalid, the data packet is intercepted to handle access point switching anomalies caused by authentication failure due to invalid data packets. The determination of whether the abnormal error is an authentication failure includes: Determine whether the abnormal error includes an authentication timeout; If it is included, then determine whether the abnormal error contains a revocation instruction to confirm whether the abnormal error is an authentication failure; Before determining whether the abnormal error contains a revocation instruction, the method further includes: Determine whether the wireless driver log contains keywords indicating completion of authentication password transmission; If not included, packet capture logs in the communication channel are obtained to determine whether the wireless access point responded to the connection request sent by the terminal device.

2. The method for handling access point handover anomalies as described in claim 1, characterized in that, The step of parsing the wireless driver log of the terminal device to identify abnormal errors appearing in the wireless driver log includes: In the wireless driver log, preset abnormal keywords are filtered to obtain the main abnormal keywords that have appeared in the wireless driver log; Identify the exception errors corresponding to the main exception keywords.

3. The method for handling access point handover anomalies as described in claim 1, characterized in that, After the terminal device does not receive a response to the connection request, the method further includes: Determine whether the wireless driver log contains the keyword "connection successful"; If present, the host configuration protocol log of the terminal device is retrieved to determine whether the access point switching anomaly occurred during the host configuration protocol phase.

4. The method for handling access point handover anomalies as described in claim 3, characterized in that, Before determining whether the wireless driver log contains a connection success keyword, the method further includes: The number of requests initiated by the terminal device to the wireless access point within the expected time period is counted. Distinguish between the number of successful connections and the number of failed connections in the aforementioned request count; Calculate the ratio of the number of failed connections to the number of requests to obtain the failure probability; If the failure probability is greater than the expected probability, then the wireless access point is determined to be abnormal due to frequent switching.

5. The method for handling access point handover anomalies as described in claim 4, characterized in that, The number of requests initiated by the terminal device to the wireless access point within the expected statistical timeframe includes: In the wireless driver log, the number of times the preset wireless connection point name appears within the expected time period is counted to obtain the number of requests.

6. A device for handling access point switching anomalies, characterized in that, include: The parsing module is used to parse the wireless driver log of the terminal device after the terminal device sends a connection request to the wireless access point, and if the terminal device does not receive a response to the connection request, then the module can deduce the abnormal errors that occur in the wireless driver log. The judgment module is used to determine whether the abnormal error is an authentication failure; A capture module, configured to capture data packets sent by the wireless access point to the terminal device if the condition is met; The interception module is used to determine whether the data packet is valid. If it is invalid, the data packet is intercepted to handle the access point handover anomaly caused by the invalid data packet. The determination of whether the abnormal error is an authentication failure includes: Determine whether the abnormal error includes an authentication timeout; If it is included, then determine whether the abnormal error contains a revocation instruction to confirm whether the abnormal error is an authentication failure; Before determining whether the abnormal error contains a revocation instruction, the method further includes: Determine whether the wireless driver log contains keywords indicating completion of authentication password transmission; If not included, packet capture logs in the communication channel are obtained to determine whether the wireless access point responded to the connection request sent by the terminal device.

7. An apparatus comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the access point switching exception handling method as described in any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the access point switching exception handling method as described in any one of claims 1 to 5.

Images