Communication connection method and terminal device

Abstract

The present application provides a communication connection method and a terminal device, and belongs to the field of communication of mobile phone devices. The method comprises: when there is a Wi-Fi disconnection event, acquiring a disconnection cause value corresponding to the Wi-Fi disconnection event, the disconnection cause value being used for indicating a cause for the Wi-Fi disconnection, and the Wi-Fi disconnection event being interruption of Wi-Fi connection between a first AP and a terminal device; and, on the basis of the disconnection cause value, re-establishing connection with the first AP. The method can be used for solving the problem of poor experience of users caused by frequent Wi-Fi disconnection.

Description

Communication connection method and terminal equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 25, 2023, with application number 202311249189.3 and application name “A communication connection method, terminal device and chip system in a wifi roaming scenario”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 30, 2024, with application number 202410136080.7 and application name “Communication connection method and terminal device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of mobile device communications, and in particular to a communication connection method and terminal device. Background Art

[0003] There are two main ways for existing terminal devices to access the Internet. One is to connect through a mobile communication network, such as the fifth generation mobile communication technology (5G th generation, 5G), the fourth generation of mobile communication technology (4 th Another method is to connect to the network through a wireless local area network (WLAN), such as a wireless fidelity (Wi-Fi) network.

[0004] With the development of mobile internet, WLAN, especially Wi-Fi, has brought great convenience to our work, study, and daily lives, becoming as important infrastructure as water and electricity. However, due to various reasons such as weak signals and system resets, Wi-Fi networks often experience frequent disconnections, resulting in a poor user experience.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication connection method to solve the poor user experience caused by frequent Wi-Fi disconnections.

[0007] The communication connection method provided in an embodiment of the present application intercepts the disconnection reason value when the Wi-Fi disconnection reason value is a self-healing reason value (or the Wi-Fi disconnection reason is a self-healing reason) so that it is not transmitted to the upper-layer application of the terminal device. The Wi-Fi signal prompt on the terminal device interface continues to be displayed, and the user is unaware of the Wi-Fi disconnection. At the same time, the terminal device performs a self-healing reconnection with the original Wi-Fi AP to quickly restore the Wi-Fi connection. Compared to the complete Wi-Fi connection process, the self-healing reconnection process of the terminal device with the original Wi-Fi AP can omit some steps such as scanning and network selection, thereby speeding up the Wi-Fi reconnection process.

[0008] In addition to determining whether the Wi-Fi disconnection reason value is a self-healing reason value, the terminal device can also determine whether it supports self-healing reconnection with the original Wi-Fi AP based on other conditions, including: Wi-Fi signal strength, whether the supplicant status is completed (if so, it means that the terminal device was previously connected to the Wi-Fi AP), and whether the original Wi-Fi AP is on the blacklist.

[0009] In a first aspect, a communication connection method is provided, which is applied to a terminal device and includes:

[0010] When a Wireless Fidelity (Wi-Fi) disconnection event occurs, obtaining a disconnection reason value corresponding to the Wi-Fi disconnection event, where the disconnection reason value is used to indicate a reason for the Wi-Fi connection being disconnected, where the Wi-Fi disconnection event is a disconnection of the Wi-Fi connection between the first radio access network device AP and the terminal device;

[0011] Reconnect with the first AP according to the disconnection reason value.

[0012] In a possible implementation, the first AP may correspond to a Wi-Fi AP to which the terminal device was originally connected but is currently disconnected. In the embodiment of the present application, the first AP may also be described as the original Wi-Fi AP.

[0013] In a possible implementation, reconnection may also be described in the embodiments below in this application as self-healing reconnection, reconnection, self-healing connection, quick connection, etc. Unlike a complete Wi-Fi connection process (such as the process of a terminal device connecting to an AP for the first time), reconnection may not perform some steps such as scanning and network selection. Therefore, it takes less time to complete the Wi-Fi connection.

[0014] With reference to the first aspect, in certain implementations of the first aspect, reconnecting with the first AP according to the disconnection reason value specifically includes:

[0015] Determining whether the disconnection reason value is the self-healing reason value, and the self-healing reason value supports reconnection between the terminal device and the first AP;

[0016] When the disconnection reason value is the self-healing reason value, reconnect with the first AP.

[0017] According to the communication connection method provided by this implementation, after a terminal device is disconnected from an AP, it is determined whether the disconnection reason value meets the conditions for self-healing reconnection. When the conditions for self-healing reconnection are met, the mobile phone performs a self-healing connection with the current AP, allowing the mobile phone to restore its Wi-Fi connection with the AP, thereby reducing the impact of Wi-Fi disconnection on the user's network experience.

[0018] In combination with the first aspect, in certain implementations of the first aspect, when the disconnection reason value is the self-healing reason value, reconnecting with the first AP further includes:

[0019] When the disconnection reason value is the self-healing reason value, determining whether the Wi-Fi received signal strength RSSI is greater than a preset threshold;

[0020] When the received signal strength RSSI of the Wi-Fi is greater than a preset threshold, reconnecting with the first AP is performed.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:

[0022] Determining whether the first AP is in the blacklist;

[0023] When the first AP is not in the blacklist, reconnecting with the first AP.

[0024] In one possible implementation, if the terminal device enters the self-healing reconnection process with the first AP, the terminal device will add the first AP to the blacklist, so that the terminal device cannot self-heal and reconnect with the first AP again in a short time, saving communication connection resources.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:

[0026] When reconnecting with the first AP, the service set identifier SSID and basic service set identifier BSSID corresponding to the first AP are added to the blacklist.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the blacklist is set with a limit on the number of APs for the SSID, where the limit is a maximum number of first APs under the SSID added to the blacklist. The method further includes:

[0028] Determine whether the SSID corresponding to the first AP is in the blacklist;

[0029] If the SSID corresponding to the first AP is in the blacklist, determining whether the number of SSIDs in the blacklist reaches the limit;

[0030] If the limit is not reached, determining whether the BSSID corresponding to the first AP is in the blacklist;

[0031] If the BSSID is not in the blacklist, reconnecting with the first AP.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:

[0033] While connected to the first AP, the roaming association process with the second AP fails;

[0034] Receive a disconnection indication message sent by the first AP, where the disconnection indication message is used to indicate that the Wi-Fi connection between the first AP and the terminal device is disconnected.

[0035] With reference to the first aspect, in certain implementations of the first aspect, reconnecting with the first AP specifically includes:

[0036] Sending a reconnection request message to the first AP;

[0037] Receive a first response message sent by the first AP in response to the reconnection request message, where the first response message is used to indicate reconnection with the terminal device.

[0038] In combination with the first aspect, in some implementations of the first aspect, the disconnection indication message includes the disconnection reason value.

[0039] In combination with the first aspect, in certain implementations of the first aspect, when a Wireless Fidelity (Wi-Fi) disconnection event occurs, the Wi-Fi signal indicator continues to be displayed.

[0040] When the current AP is found to meet the conditions for self-healing reconnection, or when the mobile phone obtains the current disconnection reason value as the self-healing reason value, the mobile phone can intercept the Wi-Fi disconnection event and no longer transmit it to the UI side. This allows the UI interface to continuously display the Wi-Fi signal indicator, reducing the user's perception of Wi-Fi disconnection and recovery in a short period of time, and improving the user experience.

[0041] In a second aspect, a communication connection method is provided, which is applied to a terminal device and includes:

[0042] While connected to the first AP, the roaming association process with the second AP fails;

[0043] receiving a disconnection indication message sent by the first AP, where the disconnection indication message is used to indicate that a Wi-Fi connection between the first AP and the terminal device is disconnected;

[0044] Sending a reconnection request message to the first AP;

[0045] Receive a first response message sent by the first AP in response to the reconnection request message, where the first response message is used to indicate reconnection with the terminal device.

[0046] With reference to the second aspect, in some implementations of the second aspect, sending the reconnection request message to the first AP specifically includes:

[0047] When the AP1 meets a preset judgment condition, a reconnection request message is sent to the first AP, where the judgment condition is used to determine whether to reconnect with the first AP.

[0048] With reference to the second aspect, in certain implementations of the second aspect, the first AP satisfies the preset judgment condition, including:

[0049] The disconnection indication message sent by the first AP carries a disconnection reason value;

[0050] The disconnection reason value is a self-healing reason value, and the self-healing reason value supports reconnection between the terminal device and the AP.

[0051] With reference to the second aspect, in certain implementations of the second aspect, the first AP satisfies the preset judgment condition, further comprising:

[0052] The first RSSI is greater than a preset threshold.

[0053] With reference to the second aspect, in certain implementations of the second aspect, the first AP satisfies the preset judgment condition, further comprising:

[0054] The first AP is not in the blacklist.

[0055] In a third aspect, a terminal device is provided, including:

[0056] processor;

[0057] Memory;

[0058] The memory stores a computer program, which includes instructions. When the instructions are executed by the processor, the terminal device executes the method described in any one of the implementations of the first aspect or the second aspect.

[0059] In a fourth aspect, a chip system is provided, comprising: a processing circuit, a receiving pin and a transmitting pin; wherein the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method described in any one of the implementation methods of the first aspect or the second aspect above to control the receiving pin to receive signals and control the transmitting pin to send signals.

[0060] In a fifth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable program instructions. When the computer-executable program instructions are executed on a computer, the computer executes the method described in any one of the implementation methods of the first aspect or the second aspect.

[0061] In a sixth aspect, a computer program product is provided, which includes a computer program code. When the computer program code runs on a computer, the computer is caused to execute the method described in any one of the implementation methods of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] FIG1 is a schematic diagram of a Wi-Fi roaming scenario provided in an embodiment of the present application.

[0063] FIG2 is a schematic diagram of Layer 2 roaming provided in an embodiment of the present application.

[0064] FIG3 is a schematic diagram of a system architecture 10 applicable to a communication connection method provided in an embodiment of the present application.

[0065] FIG4 is a schematic structural diagram of a terminal device 100 provided in an embodiment of the present application.

[0066] FIG5 is a software structure block diagram of a terminal device 100 provided in an embodiment of the present application.

[0067] 6A and 6B are schematic diagrams of GUIs that may be involved in some communication connection methods provided in embodiments of the present application.

[0068] FIG7 is a schematic flowchart of a communication connection method provided in an embodiment of the present application.

[0069] FIG8 is a schematic flowchart of another communication connection method provided in an embodiment of the present application.

[0070] FIG9 is a schematic diagram of a method for communication connection in a Wi-Fi roaming scenario provided by an embodiment of the present application.

[0071] FIG10 is a schematic diagram of another method for communication connection in a Wi-Fi roaming scenario provided in an embodiment of the present application.

[0072] FIG11 is a schematic flowchart of another communication connection method provided in an embodiment of the present application.

[0073] FIG12 is a schematic flowchart of another communication connection method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] It should be noted that the terms used in the implementation methods section of the embodiments of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a way to describe the association relationship of associated obstacles, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more than two, "at least one" and "one or more" mean one, two or more than two.

[0075] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly specifying the number of the technical features indicated. Therefore, the definition of "first" and "second" features may explicitly or implicitly include one or more of the features.

[0076] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0077] In order to better understand the communication connection method provided in the embodiments of the present application, the following first introduces the concepts or terms that may be involved in the following embodiments.

[0078] 1. Wi-Fi roaming

[0079] Wi-Fi roaming refers to the ability of a terminal device (STA) to move between different wireless access points (APs) within the same extended service set (ESS) while maintaining uninterrupted user services. An ESS includes multiple APs. When a terminal device moves from one AP coverage area to another, Wi-Fi roaming technology enables a smooth transition of services used by the terminal device. For example, in offices, conference halls, libraries, and other places where the coverage of a single AP is limited, multiple APs are typically used to provide Wi-Fi network coverage from multiple angles to ensure uninterrupted user services during mobility.

[0080] The wireless signal of an AP can only cover a limited area. If there is no Wi-Fi roaming, then when the user moves to an area with weak AP signal in the WLAN, the network between the user's terminal device (or STA) and the AP will be disconnected. For services such as audio and video, network disconnection will seriously affect the user experience. The emergence of Wi-Fi roaming is precisely to solve this problem. As shown in Figure 1, a schematic diagram of a Wi-Fi roaming scenario provided in an embodiment of the present application is provided. The Wi-Fi roaming scenario may include multiple APs that can provide the same access network service, taking AP1 and AP2 as an example. AP1 and AP2 provide the same access network service, for example, the service set identifier (SSID) of both is ×××-net. The STA can initially be located in the Wi-Fi network coverage of AP1. When the STA moves to the critical area of ​​the Wi-Fi network coverage of the two APs, the STA associates with the new AP2 and disconnects from the original AP1, and maintains an uninterrupted Wi-Fi network connection during this process. Simply put, just like the mobile call function of a mobile phone, roaming can provide uninterrupted and seamless call capabilities when the mobile phone moves from the coverage area of ​​one base station to the coverage area of ​​another base station.

[0081] The biggest advantage of WLAN networks is that STAs are not affected by the physical medium. They can move around within the WLAN coverage area and maintain uninterrupted services. Wi-Fi roaming improves the user experience of wireless networks and solves the following problems: (1) ensuring that the user's Internet Protocol (IP) address remains unchanged, allowing them to access the network they associated with when they first went online after roaming, and maintaining the same services they can perform; (2) preventing user authentication times from being too long during roaming, which can lead to data packet loss or even service interruption.

[0082] Regarding the working principle of Wi-Fi roaming, generally speaking, the specific process of Wi-Fi roaming usually includes the following stages: (1) Triggering: After the STA senses that the downlink signal is lower than the threshold, it triggers the channel scanning process; (2) Scanning: The STA will use active scanning or passive scanning to discover the available APs at the current location and measure the network information used for network selection. Among them, active scanning mainly includes: the STA periodically sends active scanning frames (probe request), and the AP will respond (probe response) after listening to the scanning frame. After receiving the response message, the STA senses the existence of the AP. Passive scanning mainly includes: the STA senses the existence of the AP by listening to the beacon frames periodically sent by the AP. Which scanning method is used is generally determined by the support of the STA. The wireless network card of a mobile phone or computer generally supports both scanning methods; voice terminals based on IP voice transmission (VoIP) generally use passive scanning. (3) Network selection: Based on the information of each AP scanned, select an AP as the roaming target. (4) Switching: Based on the STA and network capabilities, select a roaming method that matches the network side.

[0083] As shown in Figure 2, roaming can be divided into Layer 2 roaming and Layer 3 roaming depending on whether the STA is in the same subnet. Figure 2 only shows a schematic diagram of Layer 2 roaming. Layer 2 roaming means that the STA remains in the original subnet after roaming, and Layer 3 roaming means that the STA roams between different subnets (roaming within the same virtual local area network pool (VLAN pool) is still Layer 2 roaming). When planning the WLAN network, we can deploy APs on the same floor as Layer 2 roaming and APs between different floors as Layer 3 roaming. As shown in Figure 2, a scenario is shown where a STA roams between different APs under the same wireless controller (Access Controller, AC). The AC here is a network device responsible for managing APs (such as Wi-Fi APs) in a wireless network within a certain area.

[0084] 2. Class 2 frame

[0085] A STA can successfully send Class 2 frames only after successful authentication. If a STA or AP receives a Class 2 frame before successful authentication, it will reply with a frame, pushing the other end back to the unauthenticated and unassociated state.

[0086] 3. Class 3 frame

[0087] If the STA completes authentication and association with the AP and enters the authenticated, associated, and 802.1x unauthenticated state, the STA can transmit data services to the AP. Class 3 frames include all frames other than those in class 1 and class 2.

[0088] As described in the background technology, frequent Wi-Fi disconnections can lead to a poor Internet experience for users. This is especially true in scenarios where users have high network quality requirements, such as gaming, conferencing, and live streaming. Wi-Fi disconnections can significantly impact normal business operations.

[0089] In view of this, an embodiment of the present application provides a communication connection method. When Wi-Fi is disconnected, the method determines whether the conditions for self-healing reconnection are met based on the cause of the Wi-Fi disconnection, the network status, the AP status, etc. If so, the Wi-Fi network is self-healed and reconnected, thereby reducing the impact of frequent Wi-Fi disconnections on normal network services.

[0090] 3 , which is a schematic diagram of a system architecture 10 applicable to a communication connection method provided in an embodiment of the present application, can include at least one terminal device 100 and a wireless access point (AP) 200 .

[0091] In some embodiments, the terminal device 100 can be various types of electronic devices, such as: a smart phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA) or a dedicated voice call device, etc. The embodiments of the present application do not impose any restrictions on the specific type of the terminal device 100.

[0092] In some embodiments, the AP 200 may be, for example, an AP (or hotspot). The terminal device 100 and the AP 200 may be connected to a network via Wi-Fi, and the terminal device 100 may access the Internet via the AP 200.

[0093] For example, as shown in FIG4 , there is shown a schematic structural diagram of a terminal device 100 provided in an embodiment of the present application.

[0094] The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0095] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0096] The wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0097] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0098] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0099] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0100] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the terminal device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0101] In some embodiments, the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0102] The terminal device 100 implements a display function through a GPU, a display screen 194 , and an application processor, etc. The display screen 194 is used to display images, videos, etc.

[0103] The terminal device 100 can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0104] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy. The video codec is used to compress or decompress digital video. The NPU is a neural network (NN) computing processor that quickly processes input information by drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, and can also continuously self-learn.

[0105] Exemplarily, the software system of the terminal device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the terminal device 100. Figure 5 is a system architecture diagram of a terminal device 100 suitable for the solution of the present application provided in the embodiment of the present application. The system architecture may include a number of layers into which the Android system software is divided based on roles and division of labor, and these layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into four layers, from top to bottom, namely, an application layer, an application framework layer, an Android runtime (Android runtime), a system library, a kernel layer, a hardware abstraction layer (HAL) and a hardware layer. In addition, the system architecture may also include a Wi-Fi chip (chepset), which may be located in the hardware layer of the terminal device 100.

[0106] The application layer can include a series of application packages. As shown in Figure 5, the application package can include camera, calendar, map, WLAN, music, short message, Bluetooth, video, social, gallery, call and other applications.

[0107] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes predefined functions. As shown in Figure 5, the application framework layer may include a window manager, content provider, telephony manager, resource manager, notification manager, view system, and Wi-Fi management module (supplicant).

[0108] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0109] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0110] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0111] The phone manager is used to provide communication functions of the terminal device 100, such as management of call status (including answering, hanging up, etc.).

[0112] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0113] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. For example, the Notification Manager can be used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating the terminal, or flashing indicator lights.

[0114] The Wi-Fi management module can also be described as middleware, used to relay all messages between the kernel and the user during the operation of the terminal device. The Wi-Fi management module can be a supplicant.

[0115] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0116] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0117] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine is responsible for managing the object lifecycle, stack management, thread management, security and exception management, and garbage collection.

[0118] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0119] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0120] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0121] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0122] A 2D graphics engine is a drawing engine for 2D drawings.

[0123] The kernel layer is the layer between hardware and software. It includes at least the display driver, camera sensor driver, audio driver, sensor driver, and Wi-Fi driver. The Wi-Fi driver is responsible for connecting the Wi-Fi chip to the terminal device's operating system.

[0124] The Wi-Fi chip is located at the hardware layer of the terminal device.

[0125] 6A is a schematic diagram of a scenario in which a communication connection method provided by an embodiment of the present application is applicable. Here, the terminal device 100 is a mobile phone and the AP 200 is an AP.

[0126] In one possible application scenario, when a user has a high demand for Wi-Fi network use (such as gaming, online conferencing, video calling, etc.), if the Wi-Fi between the mobile phone and the AP is disconnected due to some problems, it will seriously affect the user's normal business. At this time, the Wi-Fi signal prompt in the mobile phone interface will also disappear, and the mobile phone interface will change from, for example, as shown in Figure 6A to as shown in Figure 6B. From the disappearance of the Wi-Fi signal prompt (such as 601 in Figure 6A), the user can clearly know that the Wi-Fi network is disconnected.

[0127] In actual applications, there are many factors that affect the Wi-Fi connection status, and some disconnection reasons will only affect the normal Wi-Fi connection for a very short time. Therefore, in the solution of the embodiment of the present application, under the aforementioned disconnection reasons, the mobile phone can perform Wi-Fi self-healing reconnection, thereby quickly restoring its previous network connection with the AP.

[0128] In some embodiments, when the Wi-Fi connection between the phone and the AP is restored, the Wi-Fi signal indicator on the phone's interface can reappear to alert the user that the Wi-Fi network is reconnected. However, if Wi-Fi disconnections are frequent and each disconnection reconnects automatically, the Wi-Fi signal indicator on the phone's interface will frequently disappear and reappear. This may be effective in alerting users to the Wi-Fi connection status in scenarios where users have a high demand for Wi-Fi network usage. However, in scenarios where users have a low demand for Wi-Fi network usage, such as when watching videos on Wi-Fi (video apps typically pre-cache a portion of the content), the frequent disappearance and reappearance of the Wi-Fi signal indicator in a short period of time does not provide much effective information to the user and will only affect the user's viewing experience. In particular, after a short period of frequent disconnection and self-healing, if the Wi-Fi network returns to a normal connection state, the Wi-Fi connection problem during this short period will not have a substantial impact on the user. In this case, if the Wi-Fi signal indicator is still displayed and disappeared according to the actual Wi-Fi connection status, it will only cause confusion to the user.

[0129] In view of the above issues, in some embodiments provided herein, if the cause affecting normal Wi-Fi connection is a self-healing cause, then when Wi-Fi is disconnected, the mobile phone can continue to display the Wi-Fi signal prompt on its interface, making the user unaware of the Wi-Fi connection status. The self-healing cause mentioned here means that the cause only causes the Wi-Fi disconnection for a short period of time, and the Wi-Fi connection between the mobile phone and the AP can be restored through a self-healing connection operation.

[0130] It is understandable that Wi-Fi disconnection caused by self-healing reasons (hereinafter referred to as self-healing reasons) has little impact on users, or will not make users feel a noticeable network disconnection. Therefore, when the mobile phone detects that the cause of the Wi-Fi disconnection is a self-healing reason, it can enter the self-healing reconnection process to quickly restore the Wi-Fi network and avoid the user's experience of frequent Wi-Fi disconnections. In addition, when the disconnection reason is a self-healing reason, the Wi-Fi management module (hereinafter referred to as supplicant) in the mobile phone will intercept these self-healing reasons and not report these reasons to the upper-level application, so that the upper-level application will not be aware of the existence of the cause of the Wi-Fi disconnection, and the user interface (UI) can continue to display the Wi-Fi signal prompt, so that the user is unaware of the Wi-Fi disconnection and self-healing reconnection process, thereby improving the user's experience of using the Wi-Fi network.

[0131] In order to better understand the solution provided by the embodiment of the present application, the following is an introduction to the implementation process of the communication connection method provided by the embodiment of the present application in conjunction with the accompanying drawings. For ease of description, the following description is still based on the example of a mobile phone as the terminal device. For example, as shown in Figure 7, it is a schematic flow chart of a communication connection method provided by the embodiment of the present application. Specifically, it may include the following steps:

[0132] S701: The supplicant obtains a disconnection event. Different disconnection events correspond to different disconnection reason values.

[0133] Among them, supplicant can be an event-driven framework, which can correspond to the Wi-Fi management module mentioned above.

[0134] In some embodiments, there may be multiple reasons for the disconnection event, which may be caused by reasons on the mobile phone side or on the AP side, including, for example: (1) disconnected due to inactivity on the mobile phone side or the AP side, such as the AP sending a data frame or a keep-alive frame to the mobile phone, but failing to receive an ACK frame from the mobile phone for a long time (the disconnection can be determined by combining the presence of an ACK frame from the mobile phone on the air interface); or, a problem with the communication environment or a problem with the communication receiving module Rx on the AP side causes the inability to receive mobile phone information; or, a problem with the communication receiving module Rx on the mobile phone side causes the inability to receive AP information; or, the mobile phone side detects beacon frame loss, etc. (2) The mobile phone or AP receives a class 2 frame (class 2 frame received from nonauthenticated STA) from an unauthenticated peer (AP or mobile phone). For example, the AP receives a request message from the mobile phone, but the mobile phone fails to pass the authentication stage; or, the AP receives a request message from the mobile phone, but the AP does not have any information about the mobile phone; or, the AP receives a request message from the mobile phone, but the mobile phone does not have an authentication stage; or, the mobile phone triggers roaming to connect to another AP (denoted as AP2), but the association process fails for some reason. At this time, the original AP (denoted as AP1) has deleted the mobile phone's media access control address (MAC), and the mobile phone does not reconnect with AP1 by self-healing or the mobile phone sends a disconnect (diassoc) message to the AP; or, the mobile phone's transmit power drops to zero, and the AP initiates a forced switching management message (Bss transition management, BTM). At this time, the mobile phone cannot roam successfully, which will trigger a situation similar to the AP receiving a request message from the mobile phone but finding that the mobile phone has not passed the authentication stage. (3) The mobile phone or AP receives a class 3 frame from a nonassociated peer (AP or mobile phone). (4) A basic service set (BSS) device leaves the BSS. (5) The peer repeatedly sends STA kickout messages, etc.

[0135] In some embodiments, different disconnection events may correspond to different disconnection reason values. Since different disconnection events have different effects on whether the mobile phone and the AP can self-recover and reconnect (that is, in some disconnection events, the mobile phone and the AP can self-recover and reconnect, while in other disconnection events, the mobile phone and the AP cannot self-recover and reconnect), the correspondence between different disconnection reason values ​​and whether self-recover and reconnect can be pre-set. For example, as shown in Table 1 below, an example of the correspondence between the reason value and the disconnection event in a case where self-recovery and reconnection are possible is provided in an embodiment of the present application.

[0136] Table 1

[0137] It should be noted that Table 1 above only introduces the reason values ​​4, 6, 7, 8, 65529 and 65533 as examples, but in actual applications, the reason values ​​for supporting self-healing reconnection are not limited to this. In an embodiment of the present application, the reason value for supporting self-healing reconnection can be described as a self-healing reason value, which can be a reason value that can support self-healing reconnection specified in a standard or protocol (such as reason value 4, reason value 6, reason value 7, reason value 8), or a custom reason value (such as reason value 65529 and reason value 65533).

[0138] S702: Determine whether the disconnection reason value is a self-healing reason value.

[0139] Among them, if the disconnection reason value is the self-healing reason value, that is, the judgment result of this step is "yes", then step S703 can be executed next; if the disconnection reason value is not the self-healing reason value, that is, the judgment result of this step is "no", then step S713 can be executed next, that is, Wi-Fi disconnection.

[0140] In some embodiments, the self-healing reason value can be pre-set and stored locally on the mobile phone. When the mobile phone receives a disconnection event, it can obtain the reason value based on the preset correspondence between the disconnection event and the disconnection reason value. Subsequently, the mobile phone's supplicant obtains the reason value and determines whether the reason value is a self-healing reason value.

[0141] Specifically, the Wi-Fi chip of the mobile phone can determine whether there is a disconnection event based on the current Wi-Fi communication status. For example, when the Wi-Fi chip cannot receive a data frame from the AP side, a disconnection event can be obtained, or when the Wi-Fi chip receives an unauthenticated message sent by the AP, a disconnection event can be determined. Subsequently, the Wi-Fi chip can send a disconnection request message to the Wi-Fi driver, where the disconnection request message may include the disconnection event (for example, a disconnection event indicated by a capability bit combination). After obtaining the disconnection event, the Wi-Fi driver can obtain a disconnection cause value corresponding to the disconnection event and send the disconnection cause value to the supplicant. Alternatively, after obtaining the disconnection event, the Wi-Fi driver can directly send the disconnection event to the supplicant, such as transparently transmitting the disconnection request message to the supplicant. Subsequently, the supplicant can determine whether the obtained cause value is a self-healing cause value, or the supplicant can obtain the disconnection cause value based on the disconnection event and then determine whether the disconnection cause value is a self-healing cause value.

[0142] S703: Determine whether the current supplicant status is COMPLETED.

[0143] It should be noted that supplicant is an event-driven framework, in which, at different stages of interaction, a connection event will be set by supplicant to different states. The state descriptions include: 1. DISCONNECTED; 2. ASSOCIATING; 3. ASSOCIATED; 4. 4WAY_HANDSHAKE; 5. GROUP_HANDSHAKE; 6. COMPLETED. Among them, the COMPLETED state indicates that the Wi-Fi is in a connected state (in this embodiment of the application, COMPLETED can indicate that the mobile phone and the Wi-Fi AP were originally in a connected state). When making a judgment on self-healing reconnection, it is first necessary to ensure that the connection event is from the original connection state to the connecting state (that is, from COMPLETE to ASSOCIATING).

[0144] Among them, if the current supplicant status is completed, that is, the judgment result of this step is "yes", then step S704 can be executed next; if the current supplicant status is unfinished, that is, the judgment result of this step is "no", then step S713 can be executed next, that is, Wi-Fi disconnection.

[0145] S704: Determine whether a received signal strength indication (RSSI) is greater than a preset threshold.

[0146] Among them, if the RSSI is greater than the preset threshold, that is, the judgment result of this step is "yes", then step S705 can be executed next; if the RSSI is less than or equal to the preset threshold, that is, the judgment result of this step is "no", then step S713 can be executed next, that is, Wi-Fi disconnection.

[0147] S705: Determine whether the current AP is in the blacklist.

[0148] It should be noted that the purpose of the judgment operation in steps S702 to S705 is to determine whether the current conditions (including the disconnection reason, signal strength, AP status, etc.) meet the requirements for self-healing reconnection between the mobile phone and the AP. Generally speaking, if the mobile phone and the AP meet these judgment conditions, the mobile phone will initiate a self-healing reconnection with the AP. Once the mobile phone and the AP perform the self-healing reconnection operation, regardless of whether the self-healing reconnection result is successful or unsuccessful, in order to prevent the mobile phone from frequently initiating self-healing reconnections with the same AP in a short period of time, the AP currently in self-healing reconnection with the mobile phone will be added to the blacklist.

[0149] In some embodiments, a first timeout period, such as 2 minutes, may be set for an AP in the blacklist. When the time for which the AP has been added to the blacklist reaches the first timeout period, the AP may be released from the blacklist.

[0150] Specifically, if the mobile phone and the AP meet the judgment conditions for self-healing reconnection and enter the self-healing reconnection process, the SSID and basic service set identifier (BSSID) corresponding to the AP can be added to the blacklist. In some cases, an SSID can include APs with different BSSIDs. For example, SSID1 can include four APs with basic service set identifiers BSSID1, BSSID2, BSSID3, and BSSID4. When setting the blacklist, the corresponding blacklist limit number can be set for different SSIDs. For example, for the service set identifier SSID1, the corresponding blacklist limit number can be set to 3, which means that up to 3 APs of the SSID can be added to the blacklist, and these 3 APs have different BSSIDs. If the number of APs of the SSID in the blacklist has reached the limit, and there are APs of the SSID that need to be added to the blacklist, then all subsequent APs under the SSID (regardless of whether their BSSIDs are already in the blacklist) will not perform self-healing reconnection.

[0151] For example, if two APs with a service identifier of SSID1 have been added to the blacklist, and the basic service set identifiers of these two SSID1 APs are BSSID1 and BSSID2, then when the mobile phone enters the self-healing reconnection process with an AP with a service identifier of SSID1 and a basic service set identifier of BSSID3, the mobile phone (such as a supplicant) will first check whether SSID1 is on the blacklist. If so, it will further check whether BSSID3 is under SSID1 on the blacklist. If the mobile phone does not find SSID3 under SSID1 on the blacklist, and the number of APs added to SSID1 on the blacklist has not reached the limit, the mobile phone can add BSSID3 to the blacklist. At this time, the number of APs corresponding to SSID1 on the blacklist has reached the limit of 3. When the mobile phone subsequently attempts to reconnect to the AP with service identifier SSID1 and basic service set identifier BSSID4, the mobile phone will not reconnect to the AP with BSSID4 under SSID1 because SSID1 is already in the blacklist and the number of APs under SSID1 has reached the limit.

[0152] For example, the AP information added to the blacklist may be:

[0153] {SSID1

[0154] BSSID1, BSSID2, BSSID3, [num3]}

[0155] [num3] indicates that the number of APs under SSID1 is limited to 3, that is, a maximum of three APs with SSID SSID1 can be added to the blacklist.

[0156] In some embodiments, when the number of APs under a blacklisted SSID reaches a limit, this result can be reported to the supplicant in the mobile phone. Based on this result, the supplicant can determine not to perform self-healing reconnection with the APs under that SSID. Specifically, the supplicant can determine not to perform self-healing reconnection with the APs under that SSID while the number of APs under that SSID on the blacklist remains at the limit.

[0157] In some embodiments, when an AP corresponding to a BSSID under a blacklisted SSID reaches a limit and is released from the blacklist after reaching a first timeout period, this result may also be reported to the supplicant in the mobile phone. Based on this result, the supplicant can determine that the number of APs under that SSID on the blacklist is less than the limit. Subsequently, when the supplicant determines whether to perform a self-healing reconnection with other APs under that SSID, it may first query the SSID and then the BSSID under that SSID to determine whether the AP is added to the blacklist. If the number of APs under that SSID on the blacklist is less than the limit, and the BSSID of the AP to be self-healed reconnected is not on the blacklist, the supplicant may determine to self-heal and reconnect with that AP. After entering the self-healing reconnection process, it may add the SSID and BSSID corresponding to that AP to the blacklist.

[0158] In some embodiments, when the supplicant obtains that the current AP meets the conditions for self-healing reconnection (e.g., after executing steps S702 to S705), it can intercept the obtained disconnection event and not report it to the mobile phone UI, so that the UI interface can continue to display the Wi-Fi signal indicator, preventing the user from perceiving a brief Wi-Fi disconnection. Alternatively, when the supplicant obtains that the current disconnection reason value is a self-healing reason value, it can intercept the obtained disconnection reason value and not report it to the mobile phone UI, so that the UI interface can continue to display the Wi-Fi signal indicator, preventing the user from perceiving a brief Wi-Fi disconnection.

[0159] It should be noted that the execution order of each judgment condition in step S702 to step S705 may not be limited to the order in the embodiment of Figure 7, and the embodiment of the present application does not limit the execution order of each judgment condition.

[0160] In this step, if the current AP is not in the blacklist (including the SSID of the current AP is not in the blacklist, or the SSID of the current AP is in the blacklist but the BSSID is not in the blacklist, and the SSID has not reached the limit), that is, the judgment result of this step is "no", then step S706 can be executed next; if the current AP is in the blacklist (including the SSID of the current AP is in the blacklist and its BSSID is also in the blacklist, or the SSID of the current AP is in the blacklist, its BSSID is not in the blacklist, but the SSID has reached the limit), that is, the judgment result of this step is "yes", then step S713 can be executed next, that is, Wi-Fi disconnection.

[0161] S706, enter the self-healing reconnection process.

[0162] When the self-healing reconnection judgment conditions are met, that is, the following conditions are met: (1) the disconnection reason value is the self-healing reason value; (2) the RSSI of the mobile phone is greater than the preset threshold; (3) the supplicant is in the completed state; (4) the current router is not in the blacklist, then the mobile phone can enter the self-healing reconnection process and initiate the reconnection process with the AP.

[0163] It should be noted that the embodiments of the present application only use the judgment conditions for self-healing and reconnection as shown above as examples for illustration. In actual applications, the judgment condition may also be part of these judgment conditions, but not all of them. The embodiments of the present application do not limit this.

[0164] S707: Set the self-healing state.

[0165] In some embodiments, setting the self-healing state may include setting indication information corresponding to a self-healing process to identify the current process as a self-healing reconnection process. The purpose of setting the self-healing state is to distinguish the current self-healing reconnection process from a conventional Wi-Fi connection process (non-self-healing reconnection), thereby causing the mobile phone to execute the process according to the self-healing reconnection path.

[0166] It should be noted that the purpose of setting the self-healing state is to facilitate the subsequent maintainability and logical judgment of the self-healing reconnection plan and to visualize its government benefits.

[0167] S708: Add the current AP to the blacklist.

[0168] In some embodiments, after the mobile phone enters the self-healing reconnection process with the current AP, the SSID and BSSID corresponding to the current AP may be added to a blacklist.

[0169] S709: Register self-healing timeout event.

[0170] In some embodiments, the mobile phone can pre-set a second timeout period corresponding to the self-healing reconnection process, for example, 10 minutes. When the second timeout period is reached and the mobile phone still fails to successfully reconnect to the Wi-Fi self-healing process, it indicates that a self-healing timeout event has occurred.

[0171] It should be noted that registering the self-healing timeout event can prevent the mobile phone from taking too long to reconnect to the AP through self-healing, which would cause the Wi-Fi network to take too long to recover and affect the user experience.

[0172] S710, enter the fast Wi-Fi connection process.

[0173] The fast Wi-Fi connection process here is also the self-healing reconnection process between the mobile phone and the AP.

[0174] It should be noted that the fast Wi-Fi connection between the mobile phone and the AP is also the self-healing connection or self-healing reconnection in the embodiment of this application. Unlike the normal complete connection process (such as the Wi-Fi connection process between the mobile phone and the original AP for the first time), the fast connection in the embodiment of this application can only perform the EAPO1 stage and the DHCP stage. The scanning, network selection, authentication (auth) stage, and association (assoc) stage can be omitted to shorten the time it takes for the mobile phone to reconnect to the original AP Wi-Fi self-healing.

[0175] In some embodiments, after the mobile phone completes each stage of interaction with the AP according to the normal Wi-Fi connection process, the process proceeds to step S711, indicating a successful Wi-Fi connection. If a Wi-Fi connection anomaly occurs between the mobile phone and the current AP, the Wi-Fi connection is not completed within the second timeout period, or other Wi-Fi connection failures are reported (such as authentication (auth) failure, authentication client response (eapol) failure, network protocol (DHCP) failure, etc.), the process proceeds to step S712, indicating a connection anomaly event.

[0176] According to the communication connection method provided in the embodiment of the present application, after the terminal device is disconnected from the AP, it is determined whether the disconnection reason value, signal strength, whether the AP is on the blacklist, etc. meet the conditions for self-healing reconnection. When the conditions for self-healing reconnection are met, the mobile phone executes a self-healing connection with the current AP, so that the mobile phone can restore its Wi-Fi connection with the AP, thereby reducing the impact of Wi-Fi disconnection on the user's network experience. In addition, when it is obtained that the current AP meets the conditions for self-healing reconnection, or when the mobile phone obtains the current disconnection reason value as the self-healing reason value, the mobile phone can intercept the Wi-Fi disconnection event and no longer transmit it to the UI side, so that the UI interface can always display the Wi-Fi signal indicator, reducing the user's perception of Wi-Fi disconnection and recovery in a short period of time, and improving the user's usage experience.

[0177] To more clearly understand the communication connection method provided in the embodiment of the present application, the following is a comparison and distinction between the improved solution and the unimproved solution provided in the present application in conjunction with Figure 8. For example, as shown in Figure 8, it is a schematic flow chart of another communication connection method provided in the embodiment of the present application.

[0178] S801, supplicant program starts.

[0179] The supplicant program may specifically include: a program for monitoring disconnection events and / or disconnection reason values, and a program for determining whether the disconnection reason value is a self-healing reason value. The instruction codes involved may include: supplicant / main.cmain, wpa_supplicant_init_match.

[0180] S802, initialization.

[0181] The initialization here specifically refers to the initialization of the supplicant framework state machine, including the initialization of some variables, configuration file reading, initialization of the loop event list, etc.

[0182] S803, register the global event loop.

[0183] The global event may refer to a Wi-Fi disconnection event, determining whether the Wi-Fi disconnection event meets a self-healing reconnection condition, and performing a self-healing reconnection event when the self-healing reconnection condition is met.

[0184] S804, monitoring a disconnection event.

[0185] In some embodiments, the mobile phone can monitor the disconnection event through the Wi-Fi chip. If there is a disconnection event, the disconnection event is transmitted to the Wi-Fi driver, and the Wi-Fi driver can report the disconnection event or the cause value corresponding to the disconnection event to the supplicant.

[0186] S805: A disconnection event is detected.

[0187] When a disconnection event is detected, some solutions will directly disconnect the Wi-Fi, that is, directly execute step S808; in the solution of this application, when a disconnection event is detected, step S806 can be executed next, that is, self-healing condition determination. The process of determining the self-healing condition can be referred to steps S702 to S705 in the embodiment of Figure 7 above, and will not be described in detail here.

[0188] When the result of the self-healing condition judgment is that the self-healing condition is met, step S807 can be executed next, that is, the mobile phone reconnects to the current AP (also known as self-healing reconnection or quick connection); when the result of the self-healing condition judgment is that the self-healing condition is not met, step S808 is executed again to disconnect the Wi-Fi.

[0189] It is understandable that, unlike the solution of directly disconnecting the Wi-Fi after monitoring a disconnection event, the communication connection method provided in the embodiment of the present application will determine whether the disconnection event (or the cause value corresponding to the disconnection event) meets the conditions for self-healing reconnection, that is, whether self-healing reconnection is supported. If self-healing reconnection is supported, the mobile phone will quickly self-heal and reconnect with the current AP, so that the mobile phone can successfully reconnect to the current AP's Wi-Fi network in a short time, reducing the frequency of Wi-Fi disconnection.

[0190] The communication connection method provided in the embodiments of the present application is applicable to scenarios where Wi-Fi is disconnected. In actual applications, Wi-Fi disconnection may occur in a variety of service scenarios, such as Wi-Fi roaming scenarios. For example, as shown in Figure 9, a schematic diagram of a communication connection method provided in an embodiment of the present application for Wi-Fi roaming scenarios is provided.

[0191] In some scenarios, when a mobile phone is connected to AP1 and its WLAN chip attempts to roam to AP2, during the process of establishing a connection between the mobile phone and AP2, the access controller AC learns that the mobile phone has left AP1 and deletes the mobile phone from AP1's device list (as shown in step S903 in Figure 9). If the association process between the mobile phone and AP2 fails, the mobile phone believes it is still connected to AP1. At this time, if the mobile phone sends a frame to AP1, AP1 will consider the mobile phone to be an unauthenticated device and disconnect with the mobile phone (as shown in step S906A marked in the problem scenario in Figure 9, AP1 sends a message to the mobile phone indicating the disconnection, and the message carries a reason value (which can be called reasoncode) of 6 or 7). The user will perceive the Wi-Fi signal indicator disappearing from the mobile phone interface. The Wi-Fi signal indicator will reappear after about 2-3 seconds when the Wi-Fi is successfully reconnected. During this process, the user will perceive the Wi-Fi disconnection, which affects the user experience. As shown in FIG9 , in one embodiment of the present application, if the roaming link establishment between the mobile phone and AP2 fails, the WLAN chip of the mobile phone can immediately initiate a reassociation process with the original AP (i.e., AP1) (as indicated in step S905B of the first embodiment in FIG9 , specifically, this can include sending a reassociation request, and further can include the mobile phone receiving a first response message from the AP1 in response to the reassociation request), thereby avoiding a disconnection that may be caused by a state asynchrony between the two ends. In this solution, the reconnection process between the mobile phone and the original AP (AP1) can be completed by the Wi-Fi chip firmware, with a time overhead of approximately tens of milliseconds. The Wi-Fi signal indicator on the mobile phone interface can remain unchanged during the entire process (even if the control icon on the software program disappears briefly, the interface display switching also takes a certain amount of time, and the interface may not have time to switch in a very short time, or even if the interface switches, the change in the interface in a very short time will be imperceptible to the user's vision). The user will basically not feel the Wi-Fi disconnection during the entire process.

[0192] The following introduces another communication connection method provided in an embodiment of the present application in conjunction with the embodiment of Figure 9.

[0193] S901, the mobile phone is connected to AP1.

[0194] AP1 is an access network device (such as a router) in a roaming scenario. The roaming scenario also includes AP2. AP1 and AP2 can provide the same access network services. For example, AP1 and AP2 have the same SSID: XXX-net. The Wi-Fi network coverage of AP1 and AP2 partially overlaps (as shown in Figure 1 or Figure 2).

[0195] In some embodiments, the mobile phone may initially be located in the Wi-Fi network coverage area of ​​AP1, and the mobile phone has established a Wi-Fi connection with AP1 and is in a connected state. The process of establishing a Wi-Fi connection between the mobile phone and AP1 can refer to the existing process and will not be repeated here.

[0196] S902: The mobile phone initiates Wi-Fi roaming to AP2.

[0197] In some embodiments, as the mobile phone moves, the mobile phone may gradually move away from AP1 and approach AP2. The moving direction may be, for example, the direction indicated by the arrow in FIG. 1 or FIG. 2 .

[0198] When the mobile phone moves to a certain location (for example, to the critical area of ​​the Wi-Fi coverage of AP1 and AP2), it can initiate Wi-Fi roaming to AP2. The method of initiating roaming by the mobile phone can be referred to the above description and will not be repeated here.

[0199] S903: When the wireless controller AC learns that the mobile phone has left AP1, it deletes or modifies the context of the mobile phone.

[0200] At this time, AP1 does not include the mobile phone information (such as the authentication information of the mobile phone), or the context of the mobile phone information (such as the authentication information of the mobile phone) is changed. For AP1, the mobile phone becomes an unauthenticated device.

[0201] S904: The roaming association process between the mobile phone and AP2 fails.

[0202] It should be understood that when the roaming association process between the mobile phone and AP2 fails, the mobile phone has been disconnected from AP1. For AP1, the mobile phone is regarded as an unauthenticated device.

[0203] For the problem scenario, when the roaming association between the mobile phone and AP2 fails, the mobile phone may interact with AP1 again, including steps S905A and S906A:

[0204] S905A: The mobile phone sends a class 2 frame or a class 3 frame to AP1.

[0205] It should be understood that a mobile phone can only successfully send Class 2 frames to AP1 after successful authentication with AP1; or, alternatively, a mobile phone can only successfully send Class 3 frames to AP1 after successful authentication and association with AP1. Class 2 frames are used for connection management, while Class 3 frames are used for data transmission.

[0206] S906A, AP1 sends a disconnection indication message to the mobile phone.

[0207] The disconnection instruction message is used to instruct AP1 to disconnect the Wi-Fi connection with the mobile phone.

[0208] In some embodiments, after receiving a class 2 frame or a class 3 frame sent by a mobile phone, the AP1 may disconnect from the mobile phone according to the reason value 6 or the reason value 7.

[0209] In the problem scenario, since the mobile phone is an unauthenticated device for AP1, when the mobile phone fails to establish a roaming association with AP2 and interacts with AP1 again, AP1 will return a disconnection instruction to the mobile phone, and the mobile phone's Wi-Fi will be disconnected.

[0210] For the scenario corresponding to the present application solution, when the roaming association between the mobile phone and AP2 fails, the mobile phone interacts with AP1 again, which may include steps S905B and S906B:

[0211] S905B, the mobile phone sends a reassociation request message to AP1.

[0212] The reassociation request message is used to initiate a connection to AP1 (ie, self-healing reconnection).

[0213] S906B, the mobile phone and AP1 are successfully associated.

[0214] In some embodiments, after receiving the reassociation request message, AP1 can respond to the message and re-establish a Wi-Fi connection with the mobile phone. The manner in which the mobile phone and AP1 re-establish a Wi-Fi connection can refer to the existing process and will not be described in detail here.

[0215] In the scenario corresponding to this application solution, when the mobile phone fails to establish a roaming association with AP2, the mobile phone will initiate a reconnection to AP1 and interact with AP1 for business data after successful re-authentication, rather than directly sending class2 frames or class3 frames to AP1, which are information that unauthenticated devices cannot directly interact with successfully. During the process of the mobile phone being disconnected from AP1 until it is successfully reconnected to AP1, the mobile phone interface can continue to display the Wi-Fi signal indicator, so that the user is unaware of the short-term Wi-Fi disconnection.

[0216] In other embodiments of the present application, when the roaming failure between the mobile phone and AP2 causes the mobile phone to be disconnected from AP1, and the disconnection triggers the WALIN chip (also known as the Wi-Fi chip) to report the reason value of the Wi-Fi disconnection between the mobile phone and AP1 to the upper layer of the mobile phone (such as the application processor of the mobile phone), the mobile phone adopts different processing methods for a part of the reason value that can be self-recovered by fast reconnection (which can be referred to as the first part of the reason value or the self-healing reason value, and the first part of the reason value can include at least one of 4, 6, 7, 8, 65529, and 65533) and another part of the reason value that the mobile phone cannot self-recover through fast reconnection (which can be referred to as the second part of the reason value or the non-self-healing reason value, and the second part of the reason value can be a reason value other than the first part of the reason value).

[0217] Exemplarily, as shown in FIG10 , the mobile phone can also determine whether the current disconnection reason value is a reason value that can be self-healed. If not, the normal disconnection process is executed to disconnect; if so (assuming that the current reason value is the first reason value that can be self-healed, that is, it can be one of the reason values ​​in the first part), the judgment is continued, such as: determining whether the self-healing threshold is reached (the self-healing threshold can be whether the signal strength of the AP exceeds the preset threshold, and can further include whether other parameters meet the preset conditions). If the self-healing threshold is not reached, a fast reconnection will not be performed but a normal disconnection process will be performed; otherwise, a fast reconnection will be performed to self-heal (for example, if the current signal strength of AP1 exceeds the preset threshold, the terminal's wlan chip can quickly reconnect to AP1 to quickly restore the connection between the two).

[0218] For example, as shown in FIG10 , a schematic flow chart of another communication connection method provided in an embodiment of the present application is provided. Specifically, the following steps may be included:

[0219] S1001, disconnection trigger.

[0220] In some embodiments, the disconnection trigger may be, for example, the mobile phone obtaining a disconnection event, or the supplicant obtaining a disconnection event and / or a disconnection reason value.

[0221] S1002: Determine whether the disconnection reason value is a self-healing reason value.

[0222] In the embodiment of the present application, the self-healing cause value may also be described as a first part cause value.

[0223] If the disconnection reason value is a self-healing reason value, that is, the judgment result of this step is "yes", then step S1003 can be executed next; if the disconnection reason value is not a self-healing reason value, that is, the judgment result of this step is "no", then step S1006 can be executed next, that is, Wi-Fi disconnection is performed through the normal process.

[0224] S1003: Determine whether a self-healing reconnection trigger threshold is reached.

[0225] The triggering threshold for self-healing reconnection may include, for example, whether the Wi-Fi signal of the current AP received by the mobile phone is greater than a preset threshold, whether the current AP is in the blacklist, etc.

[0226] If the trigger threshold for self-healing reconnection is reached, that is, the judgment result of this step is "yes", then step S1004 can be executed next; if the trigger threshold for self-healing reconnection is not reached, that is, the judgment result of this step is "no", then step S1006 can be executed next, that is, Wi-Fi disconnection is performed through the normal process.

[0227] S1004: Quickly reconnect to the current AP.

[0228] The fast reconnection process here can refer to the existing reconnection process. In some embodiments, the process of self-healing reconnection between the mobile phone and the current AP may not include operations such as scanning and channel selection, thereby saving time for the mobile phone to reconnect to the AP.

[0229] S1005: Determine whether the self-healing reconnection is successful.

[0230] If the self-healing reconnection is successful, that is, the judgment result of this step is "yes", the process ends; if the self-healing reconnection is unsuccessful, that is, the judgment result of this step is "no", then step S1001 can be continued to monitor the disconnection event or disconnection reason value, and repeat steps S1002 to S1005.

[0231] According to the communication connection method provided in the embodiment of the present application, after the terminal device is disconnected from the AP, it is determined whether the disconnection reason value, signal strength, whether the AP is on the blacklist, etc. meet the conditions for self-healing reconnection. When the conditions for self-healing reconnection are met, the mobile phone executes a self-healing connection with the current AP, so that the mobile phone can restore its Wi-Fi connection with the AP, thereby reducing the impact of Wi-Fi disconnection on the user's network experience. In addition, when it is obtained that the current AP meets the conditions for self-healing reconnection, or when the mobile phone obtains the current disconnection reason value as the self-healing reason value, the mobile phone can intercept the Wi-Fi disconnection event and no longer transmit it to the UI side, so that the UI interface can always display the Wi-Fi signal indicator, reducing the user's perception of Wi-Fi disconnection and recovery in a short period of time, and improving the user's usage experience.

[0232] For example, as shown in FIG11 , a schematic flow chart of another communication connection method provided in an embodiment of the present application is provided. The flow chart is applied to a terminal device and may specifically include the following steps:

[0233] S1101: When a Wi-Fi disconnection event occurs, obtain a disconnection reason value corresponding to the Wi-Fi disconnection event, where the disconnection reason value is used to indicate a reason for disconnection of the Wi-Fi connection. The Wi-Fi disconnection event is a disconnection of the Wi-Fi connection between the first AP and the terminal device.

[0234] S1102: Reconnect with the first AP according to the disconnection reason value.

[0235] In some embodiments, reconnecting with the AP based on the disconnection reason value specifically includes: determining whether the disconnection reason value is the self-healing reason value, and the self-healing reason value supports the reconnection of the terminal device with the AP; when the disconnection reason value is the self-healing reason value, reconnecting with the first AP.

[0236] In some embodiments, when the disconnection reason value is the self-healing reason value, reconnecting with the first AP further includes: when the disconnection reason value is the self-healing reason value, determining whether the Wi-Fi received signal strength RSSI is greater than a preset threshold; and when the Wi-Fi received signal strength RSSI is greater than the preset threshold, reconnecting with the first AP.

[0237] In some embodiments, the method further includes: determining whether the first AP is in a blacklist; and reconnecting with the first AP when the first AP is not in the blacklist.

[0238] In some embodiments, the method further includes: when reconnecting with the first AP, adding the service set identifier SSID and basic service set identifier BSSID corresponding to the first AP to a blacklist.

[0239] In some embodiments, the blacklist sets a limit number for the SSID, and the limit number is the maximum number of first APs under the SSID added to the blacklist. The method also includes: determining whether the SSID corresponding to the first AP is in the blacklist; if the SSID corresponding to the first AP is in the blacklist, determining whether the SSID in the blacklist reaches the limit number; if the limit number is not reached, determining whether the BSSID corresponding to the first AP is in the blacklist; if the BSSID is not in the blacklist, reconnecting with the first AP.

[0240] In some embodiments, the method further includes: when connected to the first AP, a roaming association process with a second AP fails; and receiving a disconnection indication message sent by the first AP, the disconnection indication message being used to indicate that the Wi-Fi connection between the first AP and the terminal device is disconnected.

[0241] In some embodiments, the reconnection with the first AP specifically includes: sending a reconnection request message to the first AP; receiving a first response message sent by the first AP in response to the reconnection request message, the first response message being used to indicate reconnection with the terminal device.

[0242] In some embodiments, the disconnection indication message includes the disconnection cause value.

[0243] According to the communication connection method provided in the embodiment of the present application, after the terminal device is disconnected from the AP, it is determined whether the disconnection reason value, signal strength, whether the AP is on the blacklist, etc. meet the conditions for self-healing reconnection. When the conditions for self-healing reconnection are met, the mobile phone executes a self-healing connection with the current AP, so that the mobile phone can restore its Wi-Fi connection with the AP, thereby reducing the impact of Wi-Fi disconnection on the user's network experience. In addition, when it is obtained that the current AP meets the conditions for self-healing reconnection, or when the mobile phone obtains the current disconnection reason value as the self-healing reason value, the mobile phone can intercept the Wi-Fi disconnection event and no longer transmit it to the UI side, so that the UI interface can always display the Wi-Fi signal indicator, reducing the user's perception of Wi-Fi disconnection and recovery in a short period of time, and improving the user's usage experience.

[0244] For example, as shown in FIG12 , a schematic flow chart of another communication connection method provided in an embodiment of the present application is provided. The flow chart is applied to a terminal device and may specifically include the following steps:

[0245] S1201: When connected to a first AP, a roaming association process with a second AP fails.

[0246] S1202: Receive a disconnection indication message sent by the first AP, where the disconnection indication message is used to indicate that the Wi-Fi connection between the first AP and the terminal device is disconnected.

[0247] S1203: Send a reconnection request message to the first AP.

[0248] S1204: Receive a first response message sent by the first AP in response to the reconnection request message, where the first response message is used to indicate reconnection with the terminal device.

[0249] In some embodiments, sending a reconnection request message to the first AP specifically includes: sending a reconnection request message to the first AP when the AP1 meets a preset judgment condition, and the judgment condition is used to determine whether to reconnect with the first AP.

[0250] In some embodiments, the first AP satisfies the preset judgment condition, including: the disconnection indication message sent by the first AP carries a disconnection reason value; the disconnection reason value is a self-healing reason value, and the self-healing reason value supports the terminal device to reconnect with the AP.

[0251] In some embodiments, the first AP satisfies the preset judgment condition, further comprising: the first RSSI is greater than a preset threshold.

[0252] In some embodiments, the first AP satisfies the preset judgment condition, further comprising: the first AP is not in the blacklist.

[0253] According to the communication connection method provided in the embodiment of the present application, in a Wi-Fi roaming scenario, after the terminal device is disconnected from the AP, it is determined whether the disconnection reason value, signal strength, whether the AP is on the blacklist, etc. meet the conditions for self-healing reconnection. When the conditions for self-healing reconnection are met, the mobile phone executes a self-healing connection with the current AP, so that the mobile phone restores its Wi-Fi connection with the AP, thereby reducing the impact of the Wi-Fi disconnection on the user's network usage experience.

[0254] Based on the same technical concept, an embodiment of the present application also provides a terminal device, including a processor; a memory; the memory stores a computer program, and the computer program includes instructions. When the instructions are executed by the processor, the terminal device executes one or more steps of any of the above methods.

[0255] Based on the same technical concept, an embodiment of the present application also provides a chip system, which includes: a processing circuit, a receiving pin and a transmitting pin; wherein, the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes one or more steps of any of the above methods to control the receiving pin to receive signals and control the transmitting pin to send signals.

[0256] Based on the same technical concept, an embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable program instructions. When the computer-executable program instructions are executed on a computer, the computer or processor executes one or more steps in any of the above methods.

[0257] Based on the same technical concept, an embodiment of the present application also provides a computer program product containing instructions, wherein the computer program product includes computer program code. When the computer program code is run on a computer, the computer or processor executes one or more steps in any of the above methods.

[0258] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0259] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0260] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A communication connection method, characterized in that: Applied to terminal equipment, including: When there is a wireless fidelity Wi-Fi disconnection event, obtaining a disconnection reason value corresponding to the Wi-Fi disconnection event, where the disconnection reason value is used to indicate a reason for the Wi-Fi connection being disconnected, and the Wi-Fi disconnection event is a disconnection of the Wi-Fi connection between the first wireless access network device AP and the terminal device; Reconnect with the first AP according to the disconnection reason value.

2. The method according to claim 1, characterized in that The reconnecting with the first AP according to the disconnection reason value specifically includes: Determine whether the disconnection reason value is the self-healing reason value, and the self-healing reason value supports the terminal device to reconnect with the first AP; When the disconnection reason value is the self-healing reason value, reconnecting with the first AP.

3. The method according to claim 1 or 2, characterized in that: When the disconnection reason value is the self-healing reason value, reconnecting with the first AP further includes: When the disconnection reason value is the self-healing reason value, determining whether the Wi-Fi received signal strength RSSI is greater than a preset threshold; When the received signal strength RSSI of the Wi-Fi is greater than a preset threshold, reconnecting with the first AP is performed.

4. The method according to claim 2 or 3, characterized in that: The method further comprises: Determine whether the first AP is in the blacklist; When the first AP is not in the blacklist, reconnecting with the first AP.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: When reconnecting with the first AP, the service set identifier SSID and the basic service set identifier BSSID corresponding to the first AP are added to the blacklist.

6. The method according to claim 5, characterized in that The blacklist is set with a limit number for the SSID, and the limit number is the maximum number of first APs under the SSID added to the blacklist, and the method further includes: Determine whether the SSID corresponding to the first AP is in the blacklist; If the SSID corresponding to the first AP is in the blacklist, determining whether the SSIDs in the blacklist have reached the limit number; If the limit number is not reached, determining whether the BSSID corresponding to the first AP is in the blacklist; If the BSSID is not in the blacklist, reconnecting with the first AP.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: In a state of being connected to the first AP, a roaming association process with the second AP fails; A disconnection indication message sent by the first AP is received, where the disconnection indication message is used to indicate that a Wi-Fi connection between the first AP and the terminal device is disconnected.

8. The method according to any one of claims 1 to 7, characterized in that The reconnecting with the first AP specifically includes: Sending a reconnection request message to the first AP; Receive a first response message sent by the first AP in response to the reconnection request message, where the first response message is used to indicate reconnection with the terminal device.

9. The method according to claim 7, characterized in that: The disconnection indication message includes the disconnection reason value.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: When there is a Wireless Fidelity Wi-Fi disconnection event, the Wi-Fi signal indicator continues to be displayed.

11. A communication connection method, characterized in that: Applied to terminal equipment, including: When connected to the first AP, the roaming association process with the second AP fails; receiving a disconnection indication message sent by the first AP, where the disconnection indication message is used to indicate that a Wi-Fi connection between the first AP and the terminal device is disconnected; Sending a reconnection request message to the first AP; Receive a first response message sent by the first AP in response to the reconnection request message, where the first response message is used to indicate reconnection with the terminal device.

12. The method according to claim 11, characterized in that The sending a reconnection request message to the first AP specifically includes: When the AP1 meets a preset judgment condition, a reconnection request message is sent to the first AP, where the judgment condition is used to determine whether to reconnect with the first AP.

13. The method according to claim 12, characterized in that The first AP meets the preset judgment condition, including: The disconnection indication message sent by the first AP carries a disconnection reason value; The disconnection reason value is a self-healing reason value, and the self-healing reason value supports the terminal device to reconnect with the AP.

14. The method according to claim 13, characterized in that The first AP meets the preset judgment condition, further comprising: The first RSSI is greater than a preset threshold.

15. The method according to claim 12 or 13, characterized in that The first AP meets the preset judgment condition, further comprising: The first AP is not in the blacklist.

16. A terminal device, characterized in that: include: processor; Memory; The memory stores a computer program, which includes instructions. When the instructions are executed by the processor, the terminal device executes the method according to any one of claims 1 to 10 or 11 to 15.

17. A chip system, characterized in that: The chip system includes a processing circuit, a receiving pin and a transmitting pin; wherein the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method described in any one of claims 1 to 10 or 11 to 15 to control the receiving pin to receive a signal and control the transmitting pin to send a signal.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable program instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 10 or 11 to 15.

Images