CN114500241B

CN114500241B - Abnormal reset processing method and terminal equipment

Info

Publication number: CN114500241B
Application number: CN202210394333.1A
Authority: CN
Inventors: 张永振
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-04-15
Filing date: 2022-04-15
Publication date: 2022-09-23
Anticipated expiration: 2042-04-15
Also published as: CN114500241A

Abstract

The application provides an abnormal reset processing method and terminal equipment, and belongs to the technical field of terminals. The method comprises the following steps: when a trigger event is detected, carrying out abnormal reset monitoring; when a monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists, switching the current first type of network state, and performing the abnormal reset monitoring again, wherein the types of the network state comprise a working frequency band, a network type and equipment capacity; and if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, repeatedly switching the current second type network state, and carrying out the abnormal reset monitoring until the abnormal reset disappears or a plurality of preset types of the network state are traversed. By switching the preset network state which possibly causes the abnormal reset of the protocol subsystem, the reason of the abnormal reset can be efficiently checked, and the network connection is recovered.

Description

Abnormal reset processing method and terminal equipment

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method for exception reset processing and a terminal device.

Background

When a terminal product such as a mobile phone and a tablet computer carries out a communication protocol related scene service, due to the defects of software, hardware and the like, the phenomena of network loss, card drop, disconnection and the like exist in the scenes such as conversation, video, large-flow downloading, short messages, multimedia messages and application experience, and the protocol subsystem is reset. In the method, the terminal may be frequently reset when the software has a large defect and the hardware has a problem and cannot be recovered through one-time reset. The protocol subsystem is frequently reset, so that the original module cannot be restored to a normal state, the quality index of a product is aggravated, and meanwhile, the user experience is poor.

Therefore, how to solve the problem of the device performance deterioration and the user experience degradation caused by the frequent reset of the protocol subsystem becomes a significant concern.

Disclosure of Invention

The embodiment of the application provides an abnormal reset processing method and terminal equipment, and network states of a working frequency band, a network type, equipment capacity and the like which possibly cause abnormal reset of a protocol subsystem are sequentially switched to other corresponding working frequency bands, network types, equipment capacities and the like for communication, so that network connection can be efficiently recovered.

In a first aspect, a method for exception reset processing is provided, which is applied to a terminal device, and includes:

when a trigger event is detected, carrying out abnormal reset monitoring;

when a monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, switching the current first type of network state, and performing the abnormal reset monitoring again, wherein the types of the network state comprise a working frequency band, a network type and equipment capacity;

and if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, repeatedly switching the current second type of the network state, and carrying out the abnormal reset monitoring until the abnormal reset disappears or a plurality of preset types of the network state are traversed.

With reference to the first aspect, in some implementation manners of the first aspect, after the current network state of the second type is switched, if a monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset still exists, the current network state of the third type is switched, and the abnormal reset monitoring is performed, where the network state of the first type, the network state of the second type, and the state of the third type are different.

With reference to the first aspect, in some implementation manners of the first aspect, when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset, switching the current network state of the first type specifically includes:

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, switching the current network state of the first type according to the processing sequence of the default network state type; alternatively, the first and second electrodes may be,

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, determining the processing sequence of the network state types according to a historical abnormal reset record, wherein the historical abnormal reset record comprises the network state types corresponding to the factors influencing the abnormal reset;

and switching the current first type network state according to the processing sequence of the network state types.

The processing order of the default network status type may be preset, for example, the processing order of the default network status type may include: working frequency band-network system-equipment capability, working frequency band-equipment capability-network system, network system-working frequency band-equipment capability, network system-equipment capability-working frequency band, equipment capability-working frequency band-network system, equipment capability-network system-working frequency band.

With reference to the first aspect, in certain implementations of the first aspect, the terminal device includes a white list, where the white list includes the network status corresponding to the terminal device when the abnormal reset does not occur;

when the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists, switching the current network state of the first type specifically includes:

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list comprises other network states of the first type, switching the current network state of the first type into the other network states of the first type recorded in the white list, wherein the other network states of the first type are different from the current network state of the first type;

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list does not include the network states of the other first types, performing network searching and/or network scanning to acquire the network states of the other first types different from the current network state of the first type;

and switching the current first type network state into the other first type network states recorded in the white list.

and when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list does not comprise the current network state of the first type, switching the current network state of the first type.

With reference to the first aspect, in some implementation manners of the first aspect, when the monitoring result corresponding to the abnormal reset monitoring indicates that an abnormal reset exists, switching the current network state of the first type specifically includes:

and when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, setting the current network state of the first type into a blacklist mode, and residing on other network states of the first type.

With reference to the first aspect, in some implementation manners of the first aspect, the adding the current network state of the first type to a blacklist when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset includes:

when a monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, acquiring the historical times of the current first type network state being set to be in the blacklist mode;

determining the punishment duration of the current first type of network state set as the blacklist mode according to the historical times;

and setting the current first type network state to be the blacklist mode.

With reference to the first aspect, in certain implementation manners of the first aspect, the determining, according to the historical times, that the current network state of the first type is set as a penalty duration of the blacklist mode specifically includes:

obtaining a penalty duration for which the current first type of network status is set to the blacklist mode according to the following formula,

T=n*K

wherein T is the punishment duration, n is the historical frequency, and K is a preset constant.

With reference to the first aspect, in some implementation manners of the first aspect, if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, the repeatedly switching the current network state of the second type, and performing the abnormal reset monitoring until the abnormal reset disappears, or until a plurality of preset types of the network state are traversed specifically includes:

if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, the blacklist mode is removed from the current first type network state;

and repeatedly switching the current second type of the network state, and carrying out the abnormal reset monitoring until the abnormal reset disappears or a plurality of preset types of the network state are traversed.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes:

when the current first type network state is switched and the abnormal reset monitoring is carried out again, if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset disappears, the blacklist mode of the current first type network state is removed after the duration that the current first type network state is in the blacklist mode meets the punishment duration.

With reference to the first aspect, in certain implementations of the first aspect, the exception reset includes at least one of:

a modem subsystem reset, a wireless fidelity Wi-Fi subsystem reset, a bluetooth subsystem reset, a location based services LBS subsystem reset, a near field communication NFC subsystem reset.

In a second aspect, a terminal device is provided, which includes:

one or more processors;

one or more memories;

the memory comprises computer readable program instructions which, when run in the processor, cause the terminal device to perform the method as described in any of the implementations of the first aspect above.

In a third aspect, a computer-readable storage medium is provided, which stores computer-executable program instructions that, when executed by a computer, cause the computer to perform the method according to any of the implementations of the first and second aspects.

In a fourth aspect, a computer program product is provided, comprising computer program code which, when run on a computer, causes the computer to perform the method according to any of the implementations of the first aspect described above.

Drawings

Fig. 1 is a schematic structural diagram of a terminal device 100 according to an embodiment of the present application.

Fig. 2 is a block diagram of a software structure of a terminal device 100 according to an embodiment of the present disclosure.

Fig. 3 is a schematic flowchart of a method for exception reset processing according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of another method for exception reset processing according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of another method for exception reset processing according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a graphical user interface that may be involved in an exception reset processing process according to an embodiment of the present application.

Fig. 7 is a schematic flow chart of another method for exception reset processing according to an embodiment of the present application.

Detailed Description

It is noted that the terminology used in the description of the embodiments of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. In the description of the embodiments of the present application, "/" indicates an alternative meaning, for example, a/B may indicate a or B; "and/or" herein is merely an associative relationship describing an associated obstacle, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two, "at least one", "one or more" means one, two or more than two, unless otherwise specified.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the definition of "first" or "second" feature may explicitly or implicitly include one or more of such features.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

The protocol subsystem reset in the embodiment of the present application includes a modem (modem) subsystem reset, a wireless fidelity (Wi-Fi) subsystem reset, a bluetooth (bluetooth) subsystem reset, a Location Based Service (LBS) subsystem reset, a Near Field Communication (NFC) subsystem reset, and the like. Different types of subsystem resets often lead to different problems, such as the reset of the cellular modem subsystem is manifested as a lost terminal, a dropped card, no signal, etc.; the short-distance Wi-Fi, Bluetooth, LBS and NFC subsystem reset are represented as follows: disconnection, flow cutoff, positioning failure, access control failure, and the like. The subsystem reset can affect the protocol service, and if the subsystem service occurs in the protocol service scene, a user can strongly perceive the service. Generally, the foregoing subsystem reset may be autonomously recovered in a short time. However, frequent resetting of the subsystem is usually caused by wrong configuration of radio frequency parameters, abnormal codes related to operating systems, wrong configuration of User Equipment (UE) capability, other failures (bugs) of software, and the like. Compared with the reduction of user experience caused by the reset of a subsystem at a single time, the frequent reset can lead the user experience to be worse, which can not only lead the subsystem to recover the normal state, but also aggravate the quality index of the product.

The embodiment of the application provides an abnormal reset processing method and terminal equipment, aiming at the problem of poor user experience caused by frequent resetting of a subsystem. According to the abnormal reset processing method, the network states of the terminal equipment working frequency band, the network system, the equipment capability and the like which possibly cause abnormal reset are respectively added into the blacklist, and other corresponding working frequency bands, network systems, equipment capabilities and the like are selected for communication, so that the reasons causing abnormal reset are checked as much as possible, network connection is recovered, and the network experience of a user under extreme conditions is improved.

The method for processing abnormal reset provided by the embodiment of the application can be applied to various types of terminal devices, such as a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and the like. Exemplary embodiments of the terminal device include, but are not limited to, a portable terminal that mounts an IOS, Android, Microsoft, or hong meng, or other operating system. The terminal device 100 may also be a desktop computer or the like having a touch-sensitive surface (e.g., a touch panel). The embodiment of the present application does not limit the specific type of the terminal device 100.

Exemplarily, as shown in fig. 1, a schematic structural diagram of a terminal device 100 provided in an embodiment of the present application is shown.

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 key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. 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, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. Wherein, the different processing units may be independent devices or may be integrated in one or more processors.

Wherein the controller may be a neural center and a command center of the terminal device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through an I2C bus interface to implement the touch function of the terminal device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, audio module 170 and wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to implement the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture function of terminal device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the terminal device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the terminal device 100, and may also be used to transmit data between the terminal device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other terminals, such as AR devices, etc.

It should be understood that the interface connection relationship between the modules according to the embodiment of the present invention is only an exemplary illustration, and does not limit the structure of the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the terminal device 100. The charging management module 140 may also supply power to the terminal through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the terminal device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied on 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), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred 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 a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the terminal device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

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 (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. 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).

The terminal device 100 implements a display function by the GPU, the display screen 194, and the application processor. The display screen 194 is used to display images, video, and the like.

The terminal device 100 can implement a photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor, etc.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the terminal device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy. Video codecs are used to compress or decompress digital video. The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in the external memory card. The internal memory 121 may be used to store computer-executable program code, which includes instructions.

The terminal device 100 may implement an audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. The gyro sensor 180B may be used to determine the motion attitude of the terminal device 100. The magnetic sensor 180D includes a hall sensor. The terminal device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. The acceleration sensor 180E can detect the magnitude of acceleration of the terminal device 100 in various directions (generally, three axes). The magnitude and direction of gravity can be detected when the terminal device 100 is stationary. The method can also be used for identifying the terminal posture, and is applied to transverse and vertical screen switching, pedometers and other applications. The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal device 100 emits infrared light to the outside through the light emitting diode. The ambient light sensor 180L is used to sense the ambient light level. The terminal device 100 may adaptively adjust the brightness of the display screen 194 according to the perceived ambient light level. The fingerprint sensor 180H is used to collect a fingerprint. The temperature sensor 180J is used to detect temperature. The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation acting thereon or nearby. The bone conduction sensor 180M can acquire a vibration signal.

Further, the terminal device 100 includes an air pressure sensor 180C and a distance sensor 180F. The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 100 calculates an altitude from the barometric pressure measured by the barometric pressure sensor 180C, and assists in positioning and navigation.

A distance sensor 180F for measuring a distance. The terminal device 100 may measure the distance by infrared or laser. In some embodiments, shooting a scene, the terminal device 100 may range using the distance sensor 180F to achieve fast focus.

Illustratively, the software system of the terminal device 100 may employ a hierarchical architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present invention takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the terminal device 100. Fig. 2 is a block diagram of a software configuration of the terminal device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages. As shown in fig. 2, the application packages may include camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, clone applications, and the like.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions. As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide a communication function of the terminal device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the terminal vibrates, an indicator light flashes, and the like.

The Android Runtime comprises a core library and a virtual machine. The Android Runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application layer and the application framework layer as binary files. The virtual machine is used for performing the functions of barrier life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media libraries (media libraries), three-dimensional graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), short-range Wi-Fi modules, and the like.

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

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The short-range Wi-Fi module is used for establishing a hotspot on a Wi-Fi channel, such as a Wi-Fi hotspot on a 2.4G channel or a 5G channel.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Fig. 3 is a schematic flow chart of a method for exception reset processing according to an embodiment of the present application. The method may be executed by a terminal device as a main body, and specifically may include the following steps:

and S301, resetting and monitoring the protocol subsystem.

For example, there may be a plurality of events that trigger the terminal device to perform the protocol subsystem reset monitoring, and the events that trigger different types of protocol subsystem reset monitoring (hereinafter referred to as trigger events) may be different. For example, the triggering events for the cellular Modem subsystem reset monitoring may include: the terminal equipment loses the network for a long time (for example, the duration of the lost network state is greater than a first threshold), loses the card for a long time (for example, the duration of the lost card state is greater than a second threshold), and the like. As another example, triggering events for short-range Wi-Fi subsystem reset monitoring may include: terminal equipment Wi-Fi disconnects, data stream disconnection transmitted through a Wi-Fi network and the like. For another example, the triggering events of the short-range LBS subsystem reset, the NFC subsystem reset, and the bluetooth subsystem reset may include: corresponding traffic failures, corresponding data transfer failures, and the like.

It should be noted that the above-described monitoring of the trigger events corresponding to the resets of different protocol subsystems is only an example, and in practical applications, different monitoring trigger events may also be set for the resets of different protocol subsystems, which is not limited in this embodiment of the present application.

In some embodiments, in response to the occurrence of the trigger event, the terminal device performs a protocol subsystem reset detection procedure corresponding to the trigger event. For example, when detecting that the duration of the network loss state of the terminal device is greater than a first threshold, the terminal device may initiate detection of a reset of the modem subsystem. For another example, when detecting that the Wi-Fi network of the terminal device is disconnected, the terminal device may initiate detection of a Wi-Fi protocol subsystem reset. For another example, when detecting that the bluetooth service of the terminal device fails (e.g., the bluetooth connection is abnormally disconnected), the terminal device may initiate detection of the bluetooth protocol subsystem reset.

S302, judging whether the abnormal protocol subsystem is reset or not.

In some embodiments, whether an abnormal protocol subsystem reset exists is determined according to a monitoring result of the terminal device for the protocol subsystem reset. The abnormal protocol subsystem reset refers to frequent protocol subsystem reset, for example, if the number of times of protocol subsystem reset is greater than a target threshold within a preset time, the protocol subsystem reset is an abnormal subsystem reset.

It should be noted that the abnormality determination condition for determining whether the subsystem reset is abnormal may be preset, for example, a default abnormality determination condition may be set for different types of subsystems, or different abnormality determination conditions may be set for different types of subsystems, for example, the abnormality determination condition may be customized according to a difference between different subsystems. For example, the default abnormality determination condition may be that the number of resets is greater than or equal to 2 times within 1min, and the number of resets is greater than or equal to 6 times within 3 min. For example, taking the modem subsystem as an example, if the terminal device is reset 2 times within 1min and is reset 7 times within 3min, the terminal device is considered to have an abnormal modem subsystem reset at this time.

In some embodiments, after the terminal device detects whether the subsystem reset is abnormal, a corresponding detection result is obtained. When the subsystem reset is determined to be abnormal, for example, "Y" or "yes" may be used to indicate; when it is determined that the subsystem is reset to the normal reset, it may be represented by "N" or "no", for example.

And S303, when the abnormal subsystem is reset, acquiring the current network state of the terminal equipment.

Illustratively, the network status of the terminal device includes: a frequency band corresponding to a terminal device working network (hereinafter referred to as a working frequency band), a network system used by the terminal device, a device capability corresponding to the terminal device, and the like. The network system used by the terminal device may include, for example: a fifth generation mobile communication (5 th generation, 5G) network, a Long Term Evolution (LTE) network, a Wi-Fi network, a cellular mobile network, or a future-evolution communication network (e.g., a 6G network), etc. The device capabilities corresponding to the terminal device may include supported network communication capabilities, bandwidth currently used for communication, and so on. This is not a limitation of the present application.

In some embodiments, when it is determined that there is an abnormal subsystem reset, the terminal device may obtain an operating frequency band, a network type, and a device capability (e.g., a currently used bandwidth) currently used by the terminal device. For example, the terminal device currently operates in an N78 frequency band of a cellular mobile network, and the used network standard is a New Radio (NR) network, a Carrier Aggregation (CA) state, and the like. For another example, the terminal device currently operates in a certain 5G frequency band of short-range Wi-Fi, the used network format is a Wi-Fi 6 mode, and the used bandwidth is 160 MHz.

In some embodiments, when it is determined that there is an abnormal subsystem reset, the terminal device may also obtain all network states supported by the terminal device itself, such as an operating frequency band, a network type, and a device capability of a cellular network and a short-distance network, so that other available network states may be efficiently selected when performing optimization processing on the abnormal subsystem reset in the subsequent process, and efficiency of optimizing device performance is improved.

In some embodiments, after acquiring the current network state of the terminal device, the terminal device may perform optimization processing on the abnormal reset. For example, in the embodiment of the present application, the manner of performing the exception reset processing on the subsystem may include multiple manners, such as: the first method is as follows: performing exception reset processing according to default logic, that is, a default processing mode (which may correspond to the processing mode in step S305 (a)); in the second mode, exception reset processing is performed according to history analysis result logic (which may correspond to the processing mode in step S305 (b)).

S304, the terminal equipment determines the mode of carrying out the abnormal reset processing based on the historical abnormal reset record according to the network state corresponding to the abnormal subsystem reset.

In some embodiments, the terminal device may acquire the subsystem reset exception that may occur with the corresponding type (marked as type a) according to the exception (such as network loss, Wi-Fi disconnection, and the like) monitored in step S301. Then, if it is determined in step S302 that the type a subsystem reset satisfies the abnormality determination condition, it is determined that the type a subsystem reset abnormality occurs. Then, after the current corresponding network state of the terminal device is obtained in step S303, step S304 may be executed, that is, based on the historical abnormal reset record, a mode for processing and optimizing the abnormal reset of the subsystem is determined.

In some embodiments, the terminal device may be pre-provisioned with a historical exception reset database that may include different types of historical exception resets that have occurred, such as a modem subsystem reset type, a Wi-Fi subsystem reset type, a bluetooth subsystem reset type, an NFC subsystem reset type, and so forth. The historical abnormal reset database can also comprise corresponding network states when abnormal resets of different types of subsystems occur, and the network states can be reasons for causing the abnormal resets of the subsystems.

In some embodiments, the historical exception database may further record a processing manner corresponding to different types of exception subsystem resets, for example, a black list is respectively added to the network states corresponding to the exceptions when the exceptions occur according to a certain order.

In some embodiments, after determining the type of exception subsystem reset (e.g., type a), the terminal device may look up from the historical exception database whether there is a history matching the type a subsystem reset exception.

In some embodiments, the terminal device may update the historical exception database, for example, after performing optimization processing on the exception subsystem reset each time, the terminal device may update the data in the historical exception database based on the reason for causing the exception subsystem reset each time. Such as adding some kind of abnormal subsystem reset and its corresponding reason. For another example, the terminal device may also periodically update the historical anomaly database.

Optionally, the terminal device may upload a historical abnormal reset database of itself to the cloud server. The cloud server can synthesize abnormal subsystem resets uploaded by different terminal devices and reasons causing the abnormal resets, and remind other terminal devices which are easy to have similar abnormal resets to perform optimization processing. Optionally, the cloud server may further perform optimization processing according to the abnormal subsystem reset type reported by the terminal device and the reason causing the abnormal reset, so as to avoid similar abnormal reset of other terminal devices. For example, the cloud server may determine that a certain cell base station is abnormal, a certain cell router is interrupted, and a certain segment of a network is interrupted based on historical abnormal reset information reported by the terminal device (or a plurality of terminal devices in a certain cell), and then the cloud server may perform corresponding processing to avoid abnormal reset of more terminal devices in the cell.

In some embodiments, the terminal device may further preset a white list database, where the white list database may record network states, such as a working frequency band, a network type, and a device capability, corresponding to the terminal device when the terminal device protocol subsystem operates normally. The white list database can periodically update the network state of the protocol subsystem during normal operation, including updating the whole network state supported by the terminal equipment or updating the current network state of the terminal equipment. For example, the terminal device may update the white list data every 24 hours, such as updating the operating frequency band, the network type, the device capability, and the like corresponding to the cellular network every 24 hours, where the cellular network may be a network currently used by the terminal device, or a network supported by the terminal device but not currently used.

It should be noted that the network state added in the white list may be a result of periodic self-learning of the terminal device, or a result pushed by the cloud server. For example, the terminal device may obtain data of the network operating state 1 time at regular intervals, and determine the network state in which the terminal device can operate normally (for example, it is determined that the LTE B1 frequency band can be used normally), then when the terminal device sending subsystem is reset frequently, the terminal device may select the LTE B1 frequency band to preferentially camp on under the instruction of the cloud server. For another example, if it is determined through big data analysis that 100% of a certain segment of LTE B1 frequency band can normally work, the terminal device maintenance background can add the segment of LTE B1 frequency band into the white list in a cloud pushing manner, and when the terminal device is abnormally reset by the subsystem, the terminal device can preferentially select the LTE B1 frequency band to reside.

It should be noted that the network status recorded in the white list is continuously used even if it is detected that the abnormal subsystem resets the corresponding network status, and is not processed in the following manner in step S305(a) or step S305(b) (including adding the network status to black, switching to the corresponding other network status, and the like).

In some embodiments, the terminal device may determine what processing manner is adopted for the currently occurring abnormal subsystem reset according to the record in the historical abnormal reset database and the white list, for example, what logic sequence is adopted for the network system, the working frequency band, and the device capability to perform optimization processing respectively.

For example, if a currently occurring a type a abnormal subsystem reset is assumed, if the abnormal subsystem reset database records that the type a abnormal subsystem reset is caused by a radio frequency parameter configuration error and is affected by a working frequency band, and a white list does not include a current corresponding network state of the terminal device, the method in step S305(b) may be subsequently adopted to autonomously determine a logical sequence of the working frequency band, a network type, and a device capability optimization (for example, to perform optimization on the working frequency band first) to perform optimization on the abnormal subsystem reset, that is, to perform the abnormal reset according to a historical molecular result logic.

For another example, assuming that a type B abnormal subsystem reset occurs currently, if the historical abnormal subsystem library does not record the optimization processing mode corresponding to the type B abnormal subsystem reset, the mode in step S305(a) may be subsequently adopted to perform optimization processing on the abnormal subsystem reset, and the abnormal subsystem reset is performed according to the preset optimization processing sequence of the working frequency band, the network system, and the device capability, that is, the abnormal reset is processed according to the default logic.

For another example, if a reset of the C-type abnormal subsystem occurs currently, if the network state corresponding to the reset is recorded in the white list, even if the reset of the C-type abnormal subsystem occurs currently, the terminal device may not process and optimize the network state corresponding to the reset of the C-type abnormal subsystem, and the terminal device may still continue to use the current network state to run various services.

S305(a) performs an exception reset process according to default logic.

For example, the default way to handle exception resetting may include: according to a preset sequence, each preset network state (working frequency band, network standard, equipment capability and the like) is added into a blacklist, the punishment duration of the call is kept in the blacklist, and meanwhile, other corresponding network states (working frequency band, network standard and equipment capability) are switched to replace the preset network states until the abnormal reset disappears, or the processing process adopting the default mode is carried out until all the network states are traversed.

The preset network state optimization processing sequence may be flexibly set, for example, the working frequency band-network system-device capability is used as a default sequence of the network state optimization processing, or the network system-working frequency band-device capability is used as a default sequence of the network state optimization processing, and the like, which is not limited in the embodiment of the present application.

And S305(b) performing exception reset processing according to the history analysis result logic.

For example, the processing of the exception reset according to the history analysis result logic may include: and after determining the type of the abnormal reset (such as modem subsystem reset, Wi-Fi subsystem reset, Bluetooth subsystem reset and the like), determining the sequence of the network state optimization processing according to the reason corresponding to the type of the abnormal reset recorded in the historical abnormal reset database.

The reset database records a network state which has a large influence on abnormal reset, or records a network state which causes a certain type of abnormal reset. After determining the type of the reset exception, the terminal device may obtain a specific network state that affects or causes the type of the reset exception from the historical exception reset database, and then, when performing optimization processing on the network state, may first process the specific network state recorded by the historical exception reset database, specifically, may add the specific network state into a blacklist, and switch to another corresponding network state, without performing optimization processing on the preset network state according to a fixed sequence.

For example, in the history optimization processing process, the abnormal reset of the type a is determined to be caused by a radio frequency parameter configuration error and caused by an X operating frequency band, then according to the record of the history abnormal reset database, when the type of the abnormal reset is determined to be the type a, the currently used operating frequency band may be added to the blacklist and switched to another operating frequency band, if the abnormal reset still exists after the operating frequency band is switched, then the abnormal reset is optimized by adding the network system or the device capability to the blacklist.

According to the method for processing the abnormal reset, provided by the embodiment of the application, the network states of the working frequency band, the network system, the equipment capability and the like which possibly cause the abnormal reset of the protocol subsystem are sequentially switched to other corresponding working frequency bands, network systems, equipment capabilities and the like for communication, so that the reasons causing the abnormal reset are checked as much as possible, the network connection is recovered, and the network experience of a user under extreme conditions is improved.

The following describes a procedure for performing exception reset processing optimization using default logic, with reference to the accompanying drawings. For convenience of understanding, in the embodiment of the present application, a default logic is described by taking a network state processing sequence of an operating frequency band, a network system, and a device capability as an example, but in an actual application, a processing sequence of a network state corresponding to the default logic may also be other multiple types, and the embodiment of the present application does not limit this.

Illustratively, as shown in fig. 4, a schematic flow chart of another method for exception reset handling provided by the embodiment of the present application is shown. The process may be executed by the terminal device as a main body, and specifically may include the following steps:

s401, adding a first working frequency band used by the terminal equipment into a blacklist, and acquiring the historical times M of adding the first working frequency band into the blacklist.

In some embodiments, when it is determined that the abnormal reset occurs and it is determined that the default logic is adopted to perform optimization processing on the abnormal reset, the terminal device may obtain the current network state of the terminal device (e.g., in step S303 above), and determine that the currently used operating frequency band is the first operating frequency band.

In some embodiments, the terminal device may add the first operating frequency band to a blacklist, where adding the first operating frequency band to the blacklist means that network camping or connection is no longer performed for the first operating frequency band. For example, if the abnormal reset is the abnormal reset of the modem subsystem, and the currently used operating frequency band is NR N41, the NR N41 operating frequency band may be added to the blacklist. For another example, if the abnormal reset is an abnormal reset of the Wi-Fi subsystem, and the currently used operating frequency band is 5G CH36, the 5G CH36 operating frequency band may be added to a blacklist.

In some embodiments, after the terminal device obtains the currently used operating frequency band as the first operating frequency band, the historical number M of times that the first operating frequency band is added to the blacklist within a preset historical duration may be obtained. The preset historical duration can be flexibly set according to needs, and the preset historical duration is not limited in the embodiment of the application.

The historical number of times M that the first operating frequency band is added to the blacklist may be initially set to 0, and the historical number of times M is increased by 1 every time the first operating frequency band is added to the blacklist within a preset historical time period, so as to indicate the total number of times that the first operating frequency band is added to the blacklist within the preset historical time period.

S402, determining the time length T1 for the first working frequency band to be added into the blacklist according to the historical times M for the first working frequency band to be added into the blacklist.

In some embodiments, the terminal device may calculate the blacklisting duration T1 for the first operating frequency band by using the following formula (1-1):

T1=M*X （1-1）

wherein, T1 is the punishment duration of the first working frequency band added into the blacklist; m is the number of times that the first working frequency band is currently added into the blacklist; x is a constant, for example X may be set to 10.

For example, it is assumed that the first operating frequency band is currently added to the blacklist 2 times, if X is 10, the penalty duration T1=2 × 10=20min for adding the first operating frequency band to the blacklist this time, that is, 20min is continuously left without camping on the first operating frequency band and performing network connection.

It should be understood that by calculating the blacklist punishment duration for the working frequency band in the manner, the more times the working frequency band is added into the blacklist, the longer the obtained punishment duration added into the blacklist at present is, the probability that the working frequency band with frequent problems is used can be reduced, the terminal device can work on the working frequency band with low problem rate more easily, and the device performance and the user experience are improved.

In some embodiments, the counting period of M may be a preset duration, and when the preset duration is met, M starts timing from the initial value 0 again; optionally, the counting period of M may also be an application period of one software version on the terminal device, that is, when the software is upgraded to the next software version, M will be counted again from the initial value 0.

And S403, adopting a second working frequency band for reconnection, wherein the first working frequency band is other working frequency bands except the first working frequency band.

In some embodiments, after the first operating frequency band is added to the blacklist, the terminal device may skip the first operating frequency band and does not search, scan, connect, etc. the first operating frequency band when performing network searching, reconnection, etc.

In some embodiments, the terminal device may select other operating frequency bands (denoted as second operating frequency bands) other than the first operating frequency band to perform network camping, connection, and the like. The selection manner of the second operating frequency band may include, for example: (1) preferentially selecting the working frequency band recorded in the white list, namely preferentially selecting the working frequency band in the white list to reside; (2) and if the working frequency band recorded by the white list is empty, selecting other working frequency bands to reside according to the results of actual network searching, scanning and the like.

For example, if the cellular modem subprotocol is reset abnormally, and the currently used NR N41 operating frequency band is added to the black list, if the white list records the N78 frequency band at this time, the N78 will reside preferentially; if the working frequency bands recorded in the white list at this time are empty, the user can perform residing according to the sequence of the actually searched frequency bands (such as N1, N3, N78, N79, etc.), or randomly select one of the actually searched frequency bands to perform residing.

S404, judging whether the abnormal reset still exists.

In some embodiments, after the terminal device selects to reside, connect, and the like on the second operating frequency band, it may be determined whether there is an abnormal reset on the second operating frequency band subsequently.

If the above steps S401 to S404 are passed, the abnormal reset disappears, and then the following steps S405 and S406 may be performed. If the abnormal reset still exists through the above steps S401 to S404, the following step S407 may be performed thereafter.

S405, carrying out blacklist punishment on the first working frequency band for the time length of T1.

S406, the blacklist mode is released.

For the case of no abnormal reset, a blacklist penalty of T1 duration may be imposed on the first operating frequency band. And after the punishment duration is met, subsequently removing the blacklist limitation on the first working frequency band.

S407, the blacklist mode of the first working frequency band is released.

In some embodiments, after switching the operating frequency band currently used by the terminal device, there may still be an abnormal reset. For example, when the cellular Modem subsystem is abnormally reset, if the NR N41 operating frequency band is added to the blacklist, the problem of frequent Modem crash still exists after the N1 preferentially resides according to the sequence of the searched N1, N3, N78, N79 and other frequency bands. For another example, when the Wi-Fi subsystem is abnormally reset, if the 5G CH36 is added to the blacklist, the frequent Wi-Fi shock still exists after reconnection according to the CH40 negotiated by the air interface.

For the situation that the same protocol subsystem is frequently reset after the blacklist working frequency band is forbidden, it indicates that the abnormal reset is not affected by the first working frequency band, and then when the next network state is selected for optimization, the first working frequency band in the blacklist can be removed first. For example, the NR N41 operating band in the above example is removed from the black list; as another example, 5G CH36 in the above example is removed from the blacklist. At this time, the blacklist limit of the first working frequency band is removed, and the terminal equipment can be prevented from being used normally for the first working frequency band subsequently.

S408, adding the first network system currently used by the terminal equipment into the blacklist, and acquiring the historical times N of adding the first network system into the blacklist.

In some embodiments, the terminal device may obtain the working format (denoted as the first network format) in the network status information through step S303.

In some embodiments, the terminal device adds the first network system to the blacklist means that network residence or connection is no longer performed for the first working system. For example, when the abnormal reset is the reset of the cellular Modem subsystem, the currently used 5G NR operating system may be added to the blacklist. For another example, when the abnormal reset is a Wi-Fi subsystem reset, the currently used 5G may be added to a blacklist.

S409, determining the time length T2 for the first network system to be added into the blacklist according to the historical times N for the first network system to be added into the blacklist.

In some embodiments, the terminal device may calculate the blacklisting duration T2 for the first network system through the following formula (1-2):

T2=N*Y （1-2）

wherein, T2 is a penalty duration for adding the first network type to the blacklist; n is the number of times that the first network system is currently added into the blacklist; y is a constant, for example Y may be set to 10.

For example, it is assumed that the first network system is currently added to the blacklist at 2 nd time, if Y is 10, the penalty duration T2=2 × 10=20min for adding the first network system to the blacklist this time, that is, 20min is continuously absent from the first network system for camping on a network and performing network connection, and the like.

It should be understood that by calculating the blacklist punishment duration for the network system in the above manner, the more times the network system is added to the blacklist, the longer the obtained punishment duration currently added to the blacklist is, at this time, the probability that the network system with frequent problems is used can be reduced, the terminal device can more easily work on the network system with low problem rate, and the device performance and the user experience can be improved.

In some embodiments, the counting period of N may be a preset duration, and when the preset duration is met, N starts timing from the initial value 0 again; optionally, the counting period of N may also be an application period of one software version on the terminal device, that is, when the software is upgraded to the next software version, N will be counted again from the initial value of 0.

S410, adopting a second network system to reconnect, wherein the second network system is other network systems except the first network system.

In some embodiments, after the first network type is added to the blacklist, the terminal device may skip the first network type and does not search, scan, connect, and the like for the first network type when performing network searching, reconnection, and the like.

In some embodiments, the terminal device may select other network standards (denoted as a second network standard) than the first network standard to perform network residence, connection, and the like. The selection manner of the second network system may include, for example: (1) preferentially selecting the network system recorded in the white list, namely preferentially selecting the network system in the white list to reside; (2) and if the network system recorded by the white list is empty, selecting other network systems to reside according to the results of actual network searching, scanning and the like.

For example, if the cellular modem subprotocol is abnormal in reset and the currently used 5G NR network type is added to the blacklist, if the white list records the LTE type at this time, LTE will preferentially reside; if the working frequency band recorded in the white list is empty, the user can reside according to the actually searched network systems (such as LTE, WCDMA, GSM, CDMA and the like) according to a preset priority order (such as high system priority), or randomly select one of the network systems according to the actually searched network systems for residing.

And S411, judging whether the abnormal reset still exists or not.

In some embodiments, after the terminal device selects to reside, connect, and the like on the second network system, it may be determined whether there is an abnormal reset on the second network system subsequently.

In some embodiments, after the network system currently used by the terminal device is switched, there may still be an abnormal reset. For example, when the cellular Modem subsystem is abnormally reset, if the 5G NR network system is added to the blacklist, the problem of frequent Modem crash still exists after the system is resident according to the searched LTE, WCDMA, GSM, CDMA and other systems according to the principle of high system priority. For another example, when the Wi-Fi subsystem is abnormally reset, if the 5G standard is added to the blacklist, the 2.4G standard is negotiated according to the air interface, and the frequent Wi-Fi burst problem still exists after reconnection.

Here, if it is determined that the abnormal reset disappears after the above steps S408 to S411, the following steps S412 and S406 may be performed thereafter. If the abnormal reset still exists through the above steps S408 to S411, then the following step S413 may be performed.

S412, carrying out blacklist punishment on the first network system for the duration of T3.

For the case of no abnormal reset, the first network type is subjected to blacklist penalty of T3 duration. After the penalty duration is satisfied, step S406 may be executed subsequently, that is, the blacklist restriction is released for the first network type.

S413, the blacklist mode of the first network system is released.

For the condition that the same protocol subsystem is frequently reset after the blacklist network system is forbidden, the abnormal reset is not influenced by the first network system, and then the first network system in the blacklist can be removed when the next network state is selected for optimization processing. For example, the 5G NR network type in the above example is removed from the blacklist; as another example, the Wi-Fi 5G format in the above example is removed from the blacklist. At this time, the blacklist limit of the first network system is removed, and the subsequent normal use of the first network system by the terminal equipment can be avoided.

And S414, adding the first device capability currently used by the terminal device into the blacklist, and acquiring the historical times P of adding the first device capability into the blacklist.

In some embodiments, the terminal device may obtain the device capability (denoted as the first device capability) in the network status information in step S303. Wherein the device capabilities may include: supported bandwidth, negotiation capabilities (e.g., 64QAM, 256QAM, single CC, 2CC, 3CC, etc.), etc.

In some embodiments, the terminal device adding the first device capability to the blacklist means that the network is no longer resident or connected for the first device capability. For example, when the exception reset is the cellular Modem subsystem reset, the currently used negotiation capabilities of 256QAM, 2CC, 3CC, etc. may be added to the blacklist. As another example, when the exception reset is a Wi-Fi subsystem reset, the currently used Wi-Fi 6 can be blacklisted.

S415, determining the duration T3 for the first device capability to be added into the blacklist according to the historical times P for the first device capability to be added into the blacklist.

In some embodiments, the terminal device may calculate the blacklisting duration T3 for the first device capability by the following equation (1-3):

T3=P*Z （1-3）

wherein, T3 is a penalty duration for adding the first device capability to the blacklist; p is the number of times that the first network system is currently added into the blacklist; z is a constant, for example Z may be set to 10.

For example, assuming that the first device capability is currently added to the blacklist 2 times, if Z is 10, the penalty duration T3=2 × 10=20min for adding the first device capability to the blacklist this time, that is, 20min is not in the first device capability for camping on the network and performing network connection, and the like continuously.

It should be understood that by calculating the penalty duration of the blacklist for the device capability in the above manner, the more times the device capability is added to the blacklist, the longer the obtained penalty duration of the current blacklist addition is, at this time, the probability that the device capability with frequent problems is used can be reduced, the terminal device can more easily work on the device capability with low problem rate, and the device performance and the user experience can be improved.

In some embodiments, the counting period of P may be a preset duration, and when the preset duration is met, P starts to count again from the initial value of 0; optionally, the counting period of P may also be an application period of one software version on the terminal device, that is, when the software is upgraded to the next software version, P will be counted again from the initial value 0.

S416, reconnecting with a second device capability, the second device capability being other than the first device capability.

In some embodiments, after the first device capability is added to the blacklist, the terminal device may skip the first device capability and not search, scan, connect, etc. the first device capability when performing network searching, reconnection, etc.

In some embodiments, the terminal device may select other device capabilities (denoted as second device capabilities) than the first device capability for hosting, connecting, and the like. The selection manner of the second device capability may include, for example: (1) preferentially selecting the equipment capacity recorded in the white list, namely preferentially selecting the equipment capacity in the white list to reside; (2) and if the white list recorded device capability is empty, selecting other device capability to reside according to the results of actual searching, scanning and the like.

For example, if the cellular modem subprotocol is reset abnormally, and the currently used negotiation capability of 256QAM, 2CC, and 3CC devices is added to the blacklist, if the whitelist records the negotiation capability of 64QAM and single CC devices at this time, then a 64QAM cell and a single CC cell will preferentially reside; and if the negotiation capability of the device recorded in the white list at the moment is empty, residing is performed according to the actually searched cells and the negotiation capability, or one of the cells is randomly selected to reside according to the actually searched cells.

For another example, if the Wi-Fi subprotocol is abnormally reset, after the currently used Wi-Fi 6 is added into the blacklist, reconnection is performed according to the priority principle of the scanned Wi-Fi5, Wi-Fi4 and the like.

S417, it is determined whether there is an abnormal reset.

If the above steps S414 to S417 are passed, it is determined that the abnormal reset disappears, and then the following steps S418 and S406 may be performed. If the abnormal reset still exists through the above-described steps S414 to S417, the following step S419 may be performed thereafter.

S418, carrying out blacklist punishment on the first device capacity for the duration of T3.

For the case where there is no abnormal reset, the first device capability is penalized for blacklisting for a duration of T3. After the penalty duration is satisfied, step S406 may be performed subsequently, i.e., the blacklist restriction is released for the first device capability.

And S419, prompting that the current network quality is poor.

In some embodiments, the terminal device may prompt that the current network quality is poor in various manners, for example, taking a mobile phone as an example, a first prompt message may be displayed on an interface, where the first prompt message is, for example, "the current network quality is poor" (as shown in fig. 6), and for example, the terminal device may also prompt that the current network quality is poor in a manner of voice, an indicator light, or the like.

In some embodiments, after the first device capability is added to the blacklist, if there is still an abnormal reset, the blacklist display of the first device capability may be released, and then the optimization processing flow of the reset abnormality is ended.

The following describes a process of performing exception reset processing optimization by using history analysis result logic with reference to the accompanying drawings.

It should be noted that, in the embodiment of the present application, an implementation order of an actual optimization scheme of a history analysis result logic (that is, an order of optimizing a working frequency band, a network system, an equipment capability, and the like) may be obtained based on records of a history abnormal database and a white list. For example, when the actual optimization scheme is obtained according to the historical abnormal reset database, if it is determined that the reason for the abnormal reset is caused by a known abnormal setting of a frequency band parameter, the system may determine the network state optimization sequence of the working frequency band-network system-device capability or the working frequency band-device capability-network system. For another example, when the reason for causing the abnormal reset is obtained according to the historical abnormal reset database is that the terminal negotiation capability is high, the system may give a sequence of network optimization of device capability-operating frequency band-network type or device capability-network type-operating frequency band.

Therefore, if the abnormal reset is optimized according to the history analysis result logic, a total of 6 (3 × 2) specific network state optimization sequences can be obtained from the overall actual scheme, which are respectively: working frequency band-network system-equipment capability, working frequency band-equipment capability-network system, network system-working frequency band-equipment capability, network system-equipment capability-working frequency band, equipment capability-working frequency band-network system, equipment capability-network system-working frequency band.

When performing the abnormal reset optimization processing according to the history analysis result logic, the main difference between the abnormal reset optimization processing and the default branch is as follows: the historical analysis result logic branch has certain basic analysis, and the problem of abnormal resetting of the terminal can be solved through the first round of optimization processing (one-time optimization processing is carried out on one network state).

For convenience of understanding, the following describes a process of optimally processing the exception reset according to the historical analysis result, taking a network state processing sequence according to the device capability, the operating frequency band and the network type as an example.

Illustratively, as shown in fig. 5, a schematic flow chart of another method for exception reset handling provided by the embodiments of the present application is shown. The process may be executed by the terminal device as a main body, and specifically may include the following steps:

s501 (a), adding the first device capability currently used by the terminal device into a blacklist, and acquiring the historical times P of accessing the first device capability into the blacklist.

In some embodiments, the terminal device blacklisting the first device capability means that the first device capability is no longer on-premise or connected. For example, when the exception reset is the cellular Modem subsystem reset, the currently used negotiation capabilities of 256QAM, 2CC, 3CC, etc. may be added to the blacklist. As another example, when the exception reset is a Wi-Fi subsystem reset, the currently used Wi-Fi 6 can be blacklisted.

S502 (a), determining the duration T3 for the first device capability to be added into the blacklist according to the historical times P for the first device capability to be added into the list.

In some embodiments, the terminal device may calculate the blacklisting duration T3 for the first device capability by the following equation (1-4):

T3=P*Z （1-4）

For example, assuming that the first device capability is currently added to the blacklist 2 nd time, if Z takes 10, the penalty duration T3=2 × 10=20min for adding the first device capability to the blacklist this time, that is, 20min is continuously left from the first device capability, network connection is performed, and the like.

In some embodiments, the counting period of P may be a preset duration, and when the preset duration is met, P will start timing from the initial value 0 again; optionally, the counting period of P may also be an application period of one software version on the terminal device, that is, when the software is upgraded to the next software version, P will be counted again from the initial value of 0.

S503 (a), reconnecting with a second device capability, which is a capability of a device other than the first device capability.

In some embodiments, after the first device capability is blacklisted, the terminal device may skip the first device capability and not search, scan, connect, etc. the first device capability when performing network searching, reconnection, etc.

In some embodiments, the terminal device may select other device capabilities (denoted as second device capabilities) than the first device capability to perform network hosting, connection, and the like. The selection manner of the second device capability may include, for example: (1) preferentially selecting the equipment capacity recorded in the white list, namely preferentially selecting the equipment capacity in the white list to reside; (2) and if the white list recorded device capability is empty, selecting other device capability to reside according to the results of actual searching, scanning and the like.

For example, if the cellular modem subprotocol is reset abnormally, and after the currently used negotiation capability of 256QAM, 2CC, and 3CC devices is added to the blacklist, if the white list records the negotiation capability of 64QAM and single CC devices at this time, a 64QAM and single CC cell will preferentially reside; and if the negotiation capability of the device recorded in the white list at the moment is empty, residing is performed according to the actually searched cells and the negotiation capability, or one of the cells is randomly selected to reside according to the actually searched cells.

For another example, if the Wi-Fi subprotocol is abnormally reset, after the currently used Wi-Fi 6 is added into the blacklist, the connection is reconnected according to the priority principle of the scanned Wi-Fi5, Wi-Fi4 and the like.

S504, whether abnormal resetting still exists is judged.

If there is still abnormal reset, step S507 is executed to determine whether the logic flow of the historical analysis result is finished. If the flow is not completed, step S501 (b) is executed. If there is no abnormal reset, step S505 (a) is executed to perform a blacklist penalty of T1 duration for the first device capability. After blacklisting the first device capability for a duration of T2, step S506 may be performed, the blacklist mode is released, and then the history analysis result flow ends.

And S501 (b), adding the first network system currently used by the terminal equipment into a blacklist, and acquiring the historical times N of the first network system accessing the blacklist.

S502 (b), determining the time length T2 for the first network system to be added into the blacklist according to the historical times N for the first network system to be added into the list.

In some embodiments, the terminal device may calculate the blacklisting duration T2 for the first network system through the following formula (1-5):

T2=N*Y （1-5）

wherein, T2 is a punishment duration for the first network type to join the blacklist; n is the number of times that the first network system is currently added into the blacklist; y is a constant, for example Y may be set to 10.

It should be understood that by calculating the penalty duration for the blacklist of the network system in the above manner, the more times the network system is added to the blacklist, the longer the obtained penalty duration for adding to the blacklist currently is, at this time, the probability that the network system with frequent problems is used can be reduced, the terminal device can work on the network system with low problem rate more easily, and the device performance and the user experience are improved.

In some embodiments, the counting period of N may be a preset duration, and when the preset duration is met, N starts timing from the initial value 0 again; optionally, the counting period of N may also be an application period of one software version on the terminal device, that is, when the software is upgraded to the next software version, N will be counted again from the initial value 0.

And S503 (b), reconnecting by adopting a second network standard, wherein the second network standard is other network standards except the first network standard.

S504, whether abnormal resetting still exists is judged.

If there is still abnormal reset, step S507 is executed to determine whether the logic flow of the historical analysis result is finished. If the flow is not completed, step S501 (c) is executed. If there is no abnormal reset, step S505 (b) is executed to perform a blacklist penalty of T1 duration for the first network type. After the blacklist restriction for the duration of T2 is performed on the first network type, step S506 may be executed, the blacklist mode is released, and then the history analysis result flow ends.

And S501 (c), adding the first working frequency band currently used by the terminal equipment into a blacklist, and acquiring the historical times M of adding the first working frequency band into the blacklist.

In some embodiments, the terminal device may add the first operating frequency band to a blacklist, where adding the first operating frequency band to the blacklist means that network camping or connection is no longer performed for the first operating frequency band. For example, if the exception reset is a modem subsystem exception reset and the currently used operating frequency band is NR N41, the NR N41 operating frequency band may be blacklisted. For another example, if the abnormal reset is an abnormal reset of the Wi-Fi subsystem, and the currently used operating frequency band is 5G CH36, the 5G CH36 operating frequency band may be added to a blacklist.

In some embodiments, after the terminal device obtains the currently used operating frequency band as the first operating frequency band, the historical number M of times that the first operating frequency band is added to the blacklist within a preset historical duration may be obtained. The preset history duration can be flexibly set according to needs, and the embodiment of the application does not limit the preset history duration.

S502 (c), determining the duration T1 of adding the first working frequency band into the blacklist according to the historical times M of adding the first working frequency band into the blacklist.

In some embodiments, the terminal device may calculate the blacklisting duration T1 for the first operating frequency band by the following formula (1-6):

T1=M*X （1-6）

wherein, T1 is a punishment duration for adding the first operating frequency band to the blacklist; m is the number of times that the first working frequency band is currently added into the blacklist; x is a constant, for example X may be set to 10.

S503 (a), re-connecting by using a second operating frequency band, where the second operating frequency band is another operating frequency band except the first operating frequency band.

For example, if the cellular modem subprotocol is reset abnormally, and after the currently used NR N41 operating frequency band is added to the black list, if the white list records the N78 frequency band at this time, the N78 will be preferentially resided; if the working frequency bands recorded in the white list are empty, the frequency bands are resided according to the sequence of the actually searched frequency bands (such as N1, N3, N78, N79, etc.), or one of the actually searched frequency bands is randomly selected for residence.

S504, whether abnormal resetting still exists is judged.

In some embodiments, after the terminal device selects to camp on, connect to, etc. the second operating frequency band, it may be determined whether there is an abnormal reset in the second operating frequency band subsequently.

If there is still abnormal reset, step S507 is executed to determine whether the logic flow of the historical analysis result is finished. If the flow is not completed, the following step S501 (b) is executed. If there is no abnormal reset, step S505 (a) is executed to perform a blacklist penalty of T1 duration on the first operating frequency band. After the blacklist restriction for the duration of T1 is performed on the first operating frequency band, step S506 may be executed, the blacklist mode is released, and then the history analysis result flow ends.

And S508, prompting that the current network quality is poor.

Illustratively, as shown in fig. 7, a schematic flowchart of yet another method for resetting exception handling according to the embodiment of the present application is provided. The process may be executed by the terminal device as a main body, and specifically may include the following steps:

and S701, when the trigger event is detected, carrying out abnormal reset monitoring.

The abnormal reset comprises a modulation and demodulation subsystem reset, a wireless fidelity Wi-Fi subsystem reset, a Bluetooth subsystem reset, a location-based service LBS subsystem reset and a near field communication NFC subsystem reset. The triggering events may include, for example, a network drop, a card drop, no network signal, a network disconnect, a location-based service failure, an NFC service failure, and so on. Different types of reset exceptions may correspond to different trigger events.

S702, when the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists, switching the current first type network state, and carrying out the abnormal reset monitoring again, wherein the type of the network state comprises a working frequency band, a network type and equipment capability.

In some embodiments, when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset, the current network state of the first type is switched, and the process may specifically include: when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, switching the current first type of network state according to the processing sequence of the default network state type; or when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, determining the processing sequence of the network state types according to a historical abnormal reset record, wherein the historical abnormal reset record comprises the network state types corresponding to the factors influencing the abnormal reset; and switching the current first type network state according to the processing sequence of the network state types.

Switching the current first type of network state according to the processing sequence of the default network state type may correspond to the above optimization processing of performing the abnormal reset according to the default logic. Determining a processing sequence of the network state types according to the historical abnormal reset records, and then switching the current first type network state according to the processing sequence of the network state types can be corresponding to the above optimized processing of abnormal reset according to the historical analysis result logic.

In some embodiments, the terminal device may include a white list including the network status corresponding to the terminal device when the abnormal reset has not occurred. When the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists, switching the current network state of the first type may specifically include: when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list comprises other network states of the first type, switching the current network state of the first type into the other network states of the first type recorded in the white list, wherein the other network states of the first type are different from the current network state of the first type; when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list does not include the network states of the other first types, performing network searching and/or network scanning to acquire the network states of the other first types different from the current network state of the first type; and switching the current first type network state into the other first type network states recorded in the white list.

In some embodiments, when the current first-type network state device is recorded in the white list, the first-type network state is not switched even if an abnormal reset occurs. At this time, when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset, switching the current first type network state may specifically include: and when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list does not comprise the current network state of the first type, switching the current network state of the first type.

In some embodiments, when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset, switching the current first type of network state may specifically include: and when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, setting the current network state of the first type into a blacklist mode, and residing on other network states of the first type.

In some embodiments, when the monitoring result corresponding to the abnormal reset monitoring indicates that there is an abnormal reset, adding the current first type of network state to a blacklist specifically includes: when a monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, acquiring the historical times that the current first type network state is set to be the blacklist mode; determining the punishment duration of the current first type of network state set as the blacklist mode according to the historical times; and setting the current first type network state as the blacklist mode.

Determining, according to the historical times, that the current network state of the first type is set to the penalty duration of the blacklist mode may specifically include: obtaining a penalty duration for which the current first type of network status is set to the blacklist mode according to the following equations (1-7),

T=n*K

and T is the punishment duration, n is the historical frequency, and K is a preset constant.

And S703, if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, repeatedly switching the current second type network state, and performing the abnormal reset monitoring until the abnormal reset disappears or until a plurality of preset types of the network state are traversed.

In some embodiments, if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, the switching of the current second type of the network state is repeated, and the abnormal reset monitoring is performed until the abnormal reset disappears, or until a plurality of preset types of the network state are traversed, specifically including: if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, the blacklist mode is removed from the current first type network state; and repeatedly switching the current second type of the network state, and carrying out the abnormal reset monitoring until the abnormal reset disappears or the multiple types of the network state are traversed.

In some embodiments, after switching the current network state of the second type, if a monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset still exists, switching the current network state of the third type, and performing the abnormal reset monitoring, where the network state of the first type, the network state of the second type, and the state of the third type are different.

The first type of network state may be one of an operating frequency band, a network standard and a device capability, the second type of network state may be another one of the operating frequency band, the network standard and the device capability, and the second type of network state may be another one of the operating frequency band, the network standard and the device capability. The three types of network states are different and can be set by default. Illustratively, three types of network states may be: the first type of network state may be, for example, an operating frequency band, the second type of network state may be, for example, a network type, and the third type of network state may be, for example, a device capability.

In some embodiments, when the current network state of the first type is switched and the abnormal reset monitoring is performed again, if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset disappears, the blacklist mode of the current network state of the first type is removed when a duration that the current network state of the first type is in the blacklist mode satisfies the penalty duration.

Based on the same technical concept, the embodiment of the present application further provides a terminal device, which includes one or more processors and one or more memories, where the memories include computer-readable program instructions, and when the computer-readable program instructions are executed in the processors, the terminal device is caused to perform one or more steps of any one of the methods described above.

Based on the same technical concept, the embodiments also provide a computer-readable storage medium, in which computer-executable program instructions are stored, and when the computer-executable program instructions are executed by a computer, the computer or a processor is caused to execute one or more steps of any one of the methods.

Based on the same technical concept, the present application also provides a computer program product containing instructions, the computer program product including computer program code, which when run on a computer, causes the computer or a processor to execute one or more steps of any of the above methods.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optics, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the embodiments of the present application should be covered within the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for processing abnormal reset is characterized in that the method is applied to terminal equipment and comprises the following steps:

when a trigger event is detected, determining a target type protocol subsystem corresponding to the type of the trigger event;

carrying out abnormal reset monitoring on the target type protocol subsystem;

when the monitoring result corresponding to the abnormal reset monitoring indicates that the target type protocol subsystem has abnormal reset, inquiring whether the reason information causing the historical abnormal reset of the target type protocol subsystem exists according to a preset historical abnormal reset database; wherein the content of the first and second substances,

if the historical abnormal resetting database stores reason information causing the historical abnormal resetting of the target type protocol subsystem, and the reason information belongs to a first type of network state, determining that the processing sequence of the network state is to process the first type of network state firstly, wherein the type of the network state comprises a working frequency band, a network type and equipment capacity;

switching a current first type network state, setting the current first type network state as a blacklist mode, setting the punishment duration of the first type network state as the blacklist mode to be in direct proportion to the historical times of the first type network state as the blacklist mode, and carrying out the abnormal reset monitoring again;

if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, switching the current second type network state, setting the current second type network state as the blacklist mode, setting the punishment duration of the second type network state as the blacklist mode to be in direct proportion to the historical times of the second type network state as the blacklist mode, and continuing to perform the abnormal reset monitoring;

after switching the current network state of the second type, if a monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset still exists, switching the current network state of the third type, setting the current network state of the third type as the blacklist mode, setting a penalty duration of the network state of the third type as the blacklist mode to be in direct proportion to a historical number of times that the network state of the third type is set as the blacklist mode, and continuing to perform the abnormal reset monitoring, wherein the network state of the first type, the network state of the second type and the network state of the third type are different.

2. The method of claim 1, further comprising:

and if the historical abnormal resetting database does not have reason information causing the historical abnormal resetting of the target type protocol subsystem, switching the current first type network state according to the processing sequence of the default network state type.

3. The method according to claim 1 or 2, wherein the terminal device comprises a white list, and the white list comprises the corresponding network status when the abnormal reset does not occur in the terminal device;

the switching the current network state of the first type specifically includes:

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list comprises other first type network states, switching the current first type network state into the other first type network states recorded in the white list, wherein the other first type network states are different from the current first type network state;

when the monitoring result corresponding to the abnormal reset monitoring indicates that abnormal reset exists, if the white list does not include other first type network states, network searching and/or network scanning are/is carried out, other first type network states different from the current first type network state are obtained, and the current first type network state is switched to the other first type network states obtained after network searching and/or network scanning.

4. The method according to claim 1 or 2, wherein the terminal device comprises a white list, and the white list comprises the corresponding network status when the abnormal reset does not occur to the terminal device;

5. The method according to claim 1 or 2, wherein the setting the current first type of network state to the blacklist mode specifically comprises:

acquiring the historical times of the current first type of network state set as the blacklist mode;

determining the punishment duration that the current first type network state is set to be the blacklist mode according to the historical times;

and setting the current first type network state as the blacklist mode.

6. The method according to claim 5, wherein the determining that the current network status of the first type is set as the penalty duration of the blacklist mode according to the historical number of times specifically includes:

obtaining the penalty duration for which the current first type of network status is set to the blacklist mode according to the following formula,

T=n*K

7. The method according to claim 1 or 2, characterized in that the method further comprises:

if the current first type network state is switched, the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again, and the blacklist mode is removed from the current first type network state; alternatively, the first and second electrodes may be,

and if the monitoring result corresponding to the abnormal reset monitoring indicates that the abnormal reset exists again after the current second type network state is switched, the blacklist mode is released for the current second type network state.

8. The method according to claim 1 or 2, characterized in that the method further comprises:

9. The method of claim 1 or 2, wherein the abnormal reset comprises at least one of:

10. The method of claim 1 or 2, wherein the triggering event comprises at least one of:

network loss, card drop, no network signal, network connection disconnection, location-based service failure, and NFC service failure.

11. A terminal device, comprising:

one or more processors;

one or more memories;

the memory includes computer-readable program instructions that, when executed in the processor, cause the terminal device to perform the method of any one of claims 1-10.

12. A computer-readable storage medium storing computer-executable program instructions which, when executed by a computer, cause the computer to perform the method of any one of claims 1-10.