Fault handling method and related apparatus

Abstract

The embodiments of the present application relate to the technical field of terminals. Provided are a fault handling method and a related apparatus. The method comprises: when a network fault of an electronic device is a first fault type, acquiring a first fault recovery action list and a first scenario in which the electronic device is located, wherein the first scenario is differentiated on the basis of one or more of the following parameters: the motion speed of the electronic device, the signal intensity of a network accessed by the electronic device, interface content displayed by the electronic device, a link status between the electronic device and an accessed network device, or a network attachment status of the electronic device; screening the first fault recovery action list to obtain a first target fault recovery action conforming to the first scenario; and executing the first target fault recovery action. Thus, some ineffective or unreasonable fault recovery actions can be eliminated, thereby helping to shorten a fault duration.

Description

Fault handling method and related devices

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on January 10, 2024, with application number 202410046036.7 and application name “Fault Handling Method and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a fault handling method and related devices. Background Art

[0003] Currently, electronic devices using cellular networks are prone to prolonged outages. For example, long pauses can occur during gaming or video playback, or persistent call failures can occur during phone calls. Summary of the Invention

[0004] The embodiments of the present application provide a fault handling method and related devices, which are applied in the field of terminal technology and are helpful in shortening the duration of faults.

[0005] In a first aspect, an embodiment of the present application provides a fault handling method, which is applied to an electronic device, the method comprising: when the network fault of the electronic device is a first fault type and the movement speed of the electronic device is a first speed, the electronic device performs a first fault repair action, wherein the first fault type corresponds to a first fault repair action list, and the first fault repair action includes actions in the first fault repair action list that are not used to trigger network switching; when the network fault of the electronic device is the first fault type and the movement speed of the electronic device is a second speed, the electronic device performs a second fault repair action, wherein the second fault repair action includes actions in the first fault repair action list that are used to trigger network switching, and the second speed is less than the first speed.

[0006] An electronic device may be preset with one or more fault types. Each fault type may correspond to a fault repair action list, which may include one or more fault repair actions. Fault repair actions may also be referred to as self-healing actions, which are not limited in this embodiment of the present application. In this embodiment of the present application, the electronic device may be preset with the corresponding relationships shown in Table 1.

[0007] When the network fault of the electronic device is of the first fault type, a first fault repair action list corresponding to the first fault type can be obtained. The first fault type can be any fault type preset in the electronic device, and this embodiment of the application does not limit this.

[0008] The first fault repair action list may contain invalid or unreasonable fault repair actions, and the invalid or unreasonable fault repair actions can be removed according to different scenarios.

[0009] If the electronic device's movement speed is the first speed, it indicates that the electronic device is in a high-speed scenario. If the first fault repair list includes an action that triggers a network switch, and the probability of the action triggering a network switch repairing the fault is low, the electronic device may not perform the action that triggers a network switch. In this case, the first fault repair action does not include the action that triggers a network switch. If the electronic device's movement speed is the second speed, it indicates that the electronic device is in a non-high-speed scenario. If the first fault repair list includes an action that triggers a network switch, and the probability of the action triggering a network switch repairing the fault is high, the electronic device may perform the action that triggers a network switch. In this case, the first fault repair action may include the action that triggers a network switch.

[0010] In this way, when the electronic device is in a high-speed scenario, invalid or unreasonable fault repair actions in the first fault repair action list are not executed, which is conducive to shortening the fault duration.

[0011] In one possible implementation, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, information reflecting the network rate is also displayed in the electronic device, and the first fault repair action does not include actions that affect the network rate in the first fault repair action list.

[0012] The electronic device displays information reflecting the network rate, indicating that the electronic device is in a rate-sensitive scenario. In some examples, the electronic device displays information reflecting the network rate, which may indicate that the electronic device displays a download rate or displays or runs an application that tests the network rate.

[0013] If the electronic device is in a high-speed scenario and is in a rate-sensitive scenario, the electronic device may not perform actions that affect the network rate in addition to not performing the action of triggering the network switch. In this way, the first fault repair action may not include actions that affect the network rate.

[0014] It is understandable that if the electronic device is in a non-high-speed scenario and is in a rate-sensitive scenario, the electronic device may not perform actions that affect the network rate. In this way, the second fault repair action may not include actions that affect the network rate.

[0015] In this way, when the electronic device is in a high-speed scenario and in a rate-sensitive scenario, no action that affects the network rate is performed, which helps to shorten the fault duration.

[0016] In a possible implementation, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, the signal strength of the network to which the electronic device is connected is greater than or equal to a strength threshold.

[0017] If the network signal strength connected to the electronic device is greater than or equal to the strength threshold, it indicates that the network signal is good and not a weak signal, which is conducive to the implementation of various fault repair actions. The electronic device performs the actions in the first fault repair list, which helps to increase the probability of repairing the fault and shorten the duration of the fault.

[0018] In one possible implementation, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, the electronic device is still in an idle state, and the first fault repair action does not include actions in the first fault repair action list that cannot be performed in the idle state. The idle state is used to indicate that a link between the electronic device and the network device to which it is connected has not been established.

[0019] If there are actions in the first fault action repair list that cannot be performed in the idle state, and at this time, the electronic device is in the idle state, the actions that cannot be performed in the idle state may not be performed. In this way, the first fault repair action does not include the actions in the first fault repair action list that cannot be performed in the idle state, which is beneficial to increase the probability of repairing the fault and shorten the fault duration.

[0020] In a possible implementation, when the network failure of the electronic device is of the first failure type and the movement speed of the electronic device is the first speed, the electronic device is still in a service state, and the service state is used to indicate that the electronic device is successfully stationed on the network.

[0021] The electronic device is in a service state, indicating that the electronic device is successfully connected to the network, which is conducive to the implementation of various fault repair actions. The electronic device performs the actions in the first fault repair list, which is conducive to increasing the probability of repairing the fault and shortening the fault duration.

[0022] In one possible implementation, the first fault repair action includes the first action and the second action in the first fault repair action list; when the movement speed of the electronic device is the first speed, the probability of successfully repairing the fault is less than the first preset probability, or the number of times the fault is repaired is less than the first preset number; when the movement speed of the electronic device is the first speed, the probability of successfully repairing the fault is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number; the electronic device performs the first fault repair action, including: the electronic device performs the second action; if after the second action is completed, the network fault of the electronic device is still the first fault type, the electronic device performs the first action.

[0023] Based on prior information, the probability and number of times the first and second actions successfully repair the fault can be obtained. If the success rate of the second action in repairing the fault is higher than that of the first action, the execution order of the second action is before the first action.

[0024] This will help improve the success rate of fault repair and shorten the duration of the fault.

[0025] In one possible implementation, the first fault repair action does not include the third action in the first fault repair action list, and when the movement speed of the electronic device is the first speed, the third action successfully repairs the fault more than the first preset number of times, and the probability of successfully repairing the fault is less than the second preset probability, and the second preset probability is less than the first preset probability.

[0026] According to prior information, the third action has a low success rate in repairing the fault, so the electronic device may not perform the action. This helps to improve the success rate of repairing the fault and shorten the fault duration.

[0027] In one possible implementation, the first fault repair action includes the fourth action in the first fault repair action list, and when the movement speed of the electronic device is the first speed, the probability of successfully repairing the fault with the fourth action is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number of times, the fourth action is a preset action, the second action is not a preset action, and the impact of the fourth action is greater than the impact of the first action and the second action; the method also includes: after executing the first action, if the network fault of the electronic device is still the first fault type, executing the fourth action.

[0028] The fourth action is a preset action, which means that although the success rate of repairing the fault is higher, the impact of the fourth action is greater, so it cannot be executed first. The second action is not a preset action, which means that the second action can be executed first if the success rate is higher. Therefore, the second action is before the first action, and the fourth action is after the first action.

[0029] This can reduce the impact on users and equipment while shortening the duration of the failure.

[0030] In one possible implementation, the duration between each fault repair action in the first fault repair action and the last execution of each fault repair action is greater than or equal to the first duration corresponding to each fault repair action; the duration between each fault repair action in the second fault repair action and the last execution of each fault repair action is greater than or equal to the second duration corresponding to each fault repair action.

[0031] Each fault repair action has a corresponding duration, which can be called the protection time. During this duration, the fault repair action cannot be repeated to avoid repeated state switching, which affects the success rate of fault repair.

[0032] In one possible implementation, the method includes: when the network fault of the electronic device is a second fault type and the network signal strength to which the electronic device is connected is less than a strength threshold, the electronic device does not perform actions in a second fault repair action list, the second fault type corresponds to the second fault repair list, and the second fault repair list includes actions different from those in the first fault repair list.

[0033] The second fault type is different from the first fault type. If the network signal strength of the electronic device is less than the strength threshold, it indicates a weak signal environment, making it difficult to perform fault repair actions. Therefore, the electronic device may not perform the fault repair actions. If the electronic device's network fault is of the second fault type, which corresponds to the second fault repair list, the electronic device may not perform the actions in the second fault repair action list.

[0034] In an environment with poor network signals, fault repair actions are performed. The probability of successful repair of the fault is low, and it may also cause the inability to use a better network when the network signal is good. Therefore, in an environment with poor network signals, not performing fault repair actions is beneficial to shorten the duration of the fault.

[0035] In one possible implementation, the method includes: when the network fault of the electronic device is a third fault type and the electronic device is still in a connected state, the electronic device executes an action in a third fault repair action list, the third fault type corresponds to the third fault repair list, the third fault repair list includes actions different from those in the first fault repair list, and the connection state is used to indicate that a link is established between the electronic device and the network device to which it is connected.

[0036] The electronic device is in a connected state, which is conducive to the execution of fault repair actions. At this time, the network fault of the sub-device is the third fault type, and the third fault type corresponds to the third fault repair list. The electronic device can execute the actions in the third fault repair action list, which is conducive to shortening the fault duration.

[0037] In one possible implementation, the method includes: when the network failure of the electronic device is a fourth fault type and the electronic device is still in a no-service state, the electronic device does not execute the actions in the fourth fault repair action list, the fourth fault type corresponds to the fourth fault repair list, the no-service state is used to indicate that the electronic device fails to stay on the network, and the fourth fault repair list includes actions different from those in the first fault repair list.

[0038] The electronic device is in a no-service state, indicating that the electronic device has failed to access the network. This is not conducive to the execution of fault repair actions. The network failure of the electronic device is the fourth fault type, which corresponds to the fourth fault repair list. The electronic device may not execute the actions in the fourth fault repair action list, which is conducive to shortening the fault duration.

[0039] In a second aspect, an embodiment of the present application provides a fault handling method, which is applied to an electronic device, and the method includes: when the network fault of the electronic device is of a first fault type, obtaining a first fault repair action list and a first scenario in which the electronic device is located, wherein the first scenario is distinguished based on one or more of the following parameters: the movement speed of the electronic device, the network signal strength to which the electronic device is connected, the interface content displayed by the electronic device, the link status between the electronic device and the network device to which it is connected, or the network status of the electronic device; screening a first target fault repair action that meets the first scenario in the first fault repair action list; and executing the first target fault repair action.

[0040] The movement speed of the electronic device is used to distinguish whether it is a high-speed scenario, the network signal strength to which the electronic device is connected is used to distinguish whether it is a weak field environment, the interface content displayed by the electronic device is used to distinguish whether it is a rate-sensitive scenario, the link status between the electronic device and the network device to which it is connected is used to distinguish whether it is in an idle state or a connected state, and the network status of the electronic device is used to distinguish whether there is no service or service.

[0041] In the embodiment of the present application, the method may refer to FIG4 , and these scenarios may refer to user scenarios and link information.

[0042] Different fault repair actions can be applicable to different scenarios. When the network fault of the electronic device is of the first fault type, the first target fault repair action that meets the first scenario is screened in the first fault repair action list; when the first target fault repair action is executed, unreasonable or invalid fault repair actions may not be executed, which is conducive to shortening the fault duration.

[0043] In one possible implementation, if the first scenario is differentiated based on the movement speed of the electronic device, the first target fault repair action that meets the first scenario is screened in the first fault repair action list, including: if the movement speed of the electronic device meets the preset conditions, in the first fault repair action list, deleting the action used to trigger network switching to obtain the first target fault repair action.

[0044] This method can be referred to S508 and S509 in Figure 5. In this way, unreasonable or invalid fault repair actions can be avoided, which is conducive to shortening the fault duration.

[0045] In one possible implementation, if the first scenario is distinguished based on the interface content displayed by the electronic device, the first target fault repair action that meets the first scenario is screened in the first fault repair action list, including: if the electronic device displays information used to reflect the network rate, then in the first fault repair action list, the action that affects the network rate is deleted to obtain the first target fault repair action.

[0046] This method can be referred to S506 and S507 in Figure 5. In this way, unreasonable or invalid fault repair actions can be avoided, which is conducive to shortening the fault duration.

[0047] In one possible implementation, if the first scenario is differentiated based on the signal strength of the network to which the electronic device is connected, then screening the first target fault repair action that matches the first scenario from the first fault repair action list includes: if the signal strength of the network to which the electronic device is connected is less than or equal to a strength threshold, then the first target fault repair action is not included in the first fault repair action list. This method may refer to S504 and S505 in FIG. 5 .

[0048] In one possible implementation, if the first scenario is distinguished based on the link status between the electronic device and the connected network device, the first target fault repair action that meets the first scenario is screened in the first fault repair action list, including: if the electronic device is in an idle state, in the first fault repair action list, delete the action that cannot be performed in the idle state to obtain the first target fault repair action, and the idle state is used to indicate that the link between the electronic device and the connected network device is not established. This method can refer to S705 and S706 in Figure 7, and the action performed in the connected state is used to indicate the action that cannot be performed in the spatial state.

[0049] In one possible implementation, if the first scenario is differentiated based on the network status of the electronic device, then the first target fault repair action that matches the first scenario is screened from the first fault repair action list, including: if the electronic device is in an out-of-service state, then the first target fault repair action is not included in the first fault repair action list, and the out-of-service state is used to indicate that the electronic device has failed to network. This method can be referred to S703 and S704 in Figure 7.

[0050] In one possible implementation, the first fault repair action list includes a first action and a second action, with the first action preceding the second action; screening the first target fault repair action that meets the first scenario in the first fault repair action list includes: adjusting the second action before the first action to obtain the first target fault repair action; wherein, when the network fault of the electronic device is of the first fault type, the probability of successfully repairing the fault is less than a first preset probability, or the number of times the fault is repaired is less than a first preset number; when the network fault of the electronic device is of the first fault type, the probability of successfully repairing the fault is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number. This method can refer to S602 and S603 in Figure 6.

[0051] In one possible implementation, the first target fault repair action does not include the third action in the first fault repair action list, and when the network fault of the electronic device is of the first fault type, the third action successfully repairs the fault more than a first preset number of times, and the probability of successfully repairing the fault is less than a second preset probability, and the second preset probability is less than the first preset probability. This method can be referred to S604 and S605 in FIG6 .

[0052] In one possible implementation, the first fault repair action list also includes a fourth action, and the second action is before the fourth action; the first target fault repair action also includes a fourth action, then in the first target fault repair action, the second action is before the first action, and the first action is before the fourth action; wherein, when the network fault of the electronic device is of the first fault type, the probability of successfully repairing the fault is greater than or equal to the first preset probability, the number of times the fault is repaired is greater than or equal to the first preset number, and the fourth action is a preset action.

[0053] In a possible implementation, a duration between each fault repair action in the first target fault repair action and the last execution of each fault repair action is greater than or equal to a duration corresponding to each fault repair action.

[0054] In one possible implementation, the method includes: when the network fault of the electronic device is of the second fault type, obtaining a second fault repair action list and a second scenario in which the electronic device is located, wherein the second scenario is distinguished based on one or more of the following parameters: the movement speed of the electronic device, the network signal strength to which the electronic device is connected, the interface content displayed by the electronic device, the link status between the electronic device and the network device to which it is connected, or the network status of the electronic device; the second fault repair list includes actions different from those in the first fault repair list; screening a second target fault repair action that meets the second scenario in the second fault repair action list; and executing the second target fault repair action.

[0055] Different fault types can correspond to different fault repair lists, which is conducive to targeted repairs for different fault types, thereby increasing the probability of fault repair and shortening the fault duration.

[0056] In a third aspect, embodiments of the present application provide a fault repair device, which may be an electronic device or a chip or chip system within an electronic device. The fault repair device may include a processing unit. The processing unit implements a fault repair method described in any aspect or any possible implementation of any aspect. When the fault repair device is an electronic device, the processing unit may be a processor. The fault repair device may also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to cause the electronic device to implement a fault repair method described in any aspect or any possible implementation of any aspect. When the fault repair device is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to cause the electronic device to implement a fault repair method described in any aspect or any possible implementation of any aspect. The storage unit may be a storage unit within the chip (e.g., a register, cache, etc.) or a storage unit within the electronic device located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0057] In one possible implementation, the processing unit is configured to, when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is of the first speed, execute a first fault repair action, wherein the first fault type corresponds to a first fault repair action list, and the first fault repair action includes actions in the first fault repair action list that are not used to trigger network switching; and when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is of the second speed, execute a second fault repair action, wherein the second fault repair action includes actions in the first fault repair action list that are used to trigger network switching, and the second speed is less than the first speed.

[0058] In one possible implementation, when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is the first speed, information reflecting the network rate is also displayed in the fault handling device, and the first fault repair action does not include actions that affect the network rate in the first fault repair action list.

[0059] In a possible implementation, when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is the first speed, the signal strength of the network to which the fault handling device is connected is greater than or equal to a strength threshold.

[0060] In one possible implementation, when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is the first speed, the fault handling device is still in an idle state, and the first fault repair action does not include actions in the first fault repair action list that cannot be performed in the idle state. The idle state is used to indicate that the link between the fault handling device and the connected network device has not been established.

[0061] In a possible implementation, when the network fault of the fault handling device is of the first fault type and the movement speed of the fault handling device is the first speed, the fault handling device is still in a service state, and the service state is used to indicate that the fault handling device is successfully stationed on the network.

[0062] In one possible implementation, the first fault repair action includes the first action and the second action in the first fault repair action list; the first action, when the movement speed of the fault handling device is the first speed, the probability of successfully repairing the fault is less than the first preset probability, or the number of times the fault is repaired is less than the first preset number; the second action, when the movement speed of the fault handling device is the first speed, the probability of successfully repairing the fault is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number; the processing unit is also used to: execute the second action; if after the second action is executed, the network fault of the fault handling device is still the first fault type, then execute the first action.

[0063] In one possible implementation, the first fault repair action does not include the third action in the first fault repair action list, and when the movement speed of the fault handling device is the first speed, the third action successfully repairs the fault more than the first preset number of times, and the probability of successfully repairing the fault is less than the second preset probability, and the second preset probability is less than the first preset probability.

[0064] In one possible implementation, the first fault repair action includes the fourth action in the first fault repair action list, and when the movement speed of the fault handling device is the first speed, the probability of successfully repairing the fault with the fourth action is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number of times, the fourth action is a preset action, the second action is not a preset action, and the impact of the fourth action is greater than the impact of the first action and the second action; the processing unit is also used to: after executing the first action, if the network fault of the fault handling device is still the first fault type, execute the fourth action.

[0065] In one possible implementation, the duration between each fault repair action in the first fault repair action and the last execution of each fault repair action is greater than or equal to the first duration corresponding to each fault repair action; the duration between each fault repair action in the second fault repair action and the last execution of each fault repair action is greater than or equal to the second duration corresponding to each fault repair action.

[0066] In one possible implementation, the processing unit is also used to: when the network fault of the fault handling device is a second fault type and the network signal strength to which the fault handling device is connected is less than a strength threshold, not execute the actions in the second fault repair action list, the second fault type corresponds to the second fault repair list, and the second fault repair list includes actions different from those in the first fault repair list.

[0067] In one possible implementation, the processing unit is also used to: when the network fault of the fault handling device is a third fault type and the fault handling device is still in a connected state, execute actions in a third fault repair action list, the third fault type corresponds to a third fault repair list, the third fault repair list includes actions different from those in the first fault repair list, and the connected state is used to indicate that a link is established between the fault handling device and the connected network device.

[0068] In one possible implementation, the processing unit is also used to: when the network fault of the fault handling device is a fourth fault type and the fault handling device is still in an out-of-service state, not execute the actions in the fourth fault repair action list, the fourth fault type corresponds to the fourth fault repair list, the out-of-service state is used to indicate that the fault handling device fails to stay on the network, and the fourth fault repair list includes actions different from those in the first fault repair list.

[0069] In another possible implementation, the processing unit is used to: when the network fault of the fault repair device is of the first fault type, obtain a first fault repair action list and a first scenario in which the fault repair device is located, wherein the first scenario is distinguished based on one or more of the following parameters: the movement speed of the fault repair device, the network signal strength to which the fault repair device is connected, the interface content displayed by the fault repair device, the link status between the fault repair device and the connected network device, or the network status of the fault repair device; filter the first target fault repair action that meets the first scenario in the first fault repair action list; and execute the first target fault repair action.

[0070] In one possible implementation, if the first scenario is differentiated based on the movement speed of the fault repair device, the processing unit is specifically used to: if the movement speed of the fault repair device meets the preset conditions, delete the action used to trigger network switching in the first fault repair action list to obtain the first target fault repair action.

[0071] In one possible implementation, if the first scenario is distinguished based on the interface content displayed by the fault repair device, the processing unit is specifically used to: if the fault repair device displays information used to reflect the network rate, then in the first fault repair action list, delete the action that affects the network rate to obtain the first target fault repair action.

[0072] In one possible implementation, if the first scenario is differentiated based on the network signal strength to which the fault repair device is connected, the processing unit is specifically used to: if the network signal strength to which the fault repair device is connected is less than or equal to the strength threshold, then there is no first target fault repair action in the first fault repair action list.

[0073] In one possible implementation, if the first scenario is distinguished based on the link status between the fault repair device and the connected network device, the processing unit is specifically used to: if the fault repair device is in an idle state, in the first fault repair action list, delete the actions that cannot be executed in the idle state to obtain the first target fault repair action, and the idle state is used to indicate that the link between the fault repair device and the connected network device has not been established.

[0074] In one possible implementation, if the first scenario is distinguished based on the network status of the fault repair device, the processing unit is specifically used to: if the fault repair device is in an out-of-service state, there is no first target fault repair action in the first fault repair action list, and the out-of-service state is used to indicate that the fault repair device has failed to stay on the network.

[0075] In one possible implementation, the first fault repair action list includes a first action and a second action, and the first action is before the second action; the processing unit is specifically used to: adjust the second action before the first action to obtain a first target fault repair action; wherein, when the network fault of the fault repair device is of the first fault type, the probability of successfully repairing the fault is less than a first preset probability, or the number of times the fault is repaired is less than the first preset number; when the network fault of the fault repair device is of the first fault type, the probability of successfully repairing the fault for the second action is greater than or equal to the first preset probability, and the number of times the fault is repaired is greater than or equal to the first preset number.

[0076] In one possible implementation, the first target fault repair action does not include the third action in the first fault repair action list. When the network fault of the fault repair device is of the first fault type, the number of successful fault repairs of the third action is greater than the first preset number, and the probability of successfully repairing the fault is less than the second preset probability, and the second preset probability is less than the first preset probability.

[0077] In one possible implementation, the first fault repair action list also includes a fourth action, and the second action is before the fourth action; the first target fault repair action also includes a fourth action, then in the first target fault repair action, the second action is before the first action, and the first action is before the fourth action; wherein, when the network fault of the fault repair device is of the first fault type, the probability of successfully repairing the fault is greater than or equal to the first preset probability, the number of times the fault is repaired is greater than or equal to the first preset number, and the fourth action is a preset action.

[0078] In a possible implementation, a duration between each fault repair action in the first target fault repair action and the last execution of each fault repair action is greater than or equal to a duration corresponding to each fault repair action.

[0079] In one possible implementation, the processing unit is also used to: when the network fault of the fault repair device is of the second fault type, obtain a second fault repair action list and a second scenario in which the fault repair device is located, wherein the second scenario is distinguished based on one or more of the following parameters: the movement speed of the fault repair device, the network signal strength to which the fault repair device is connected, the interface content displayed by the fault repair device, the link status between the fault repair device and the connected network device, or the network status of the fault repair device; the second fault repair list includes actions different from those in the first fault repair list; the second target fault repair action that meets the second scenario is screened in the second fault repair action list; and the second target fault repair action is executed.

[0080] In a fourth aspect, an embodiment of the present application provides an electronic device comprising one or more processors and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code comprising computer instructions, and the one or more processors calling the computer instructions to enable the electronic device to execute the method described in any aspect or any possible implementation of any aspect.

[0081] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is run on an electronic device, the electronic device executes the method described in any aspect or any possible implementation of any aspect.

[0082] In a sixth aspect, an embodiment of the present application provides a computer program product, which includes a computer program code. When the computer program code runs on an electronic device, the electronic device executes the method described in any aspect or any possible implementation of any aspect.

[0083] In the seventh aspect, an embodiment of the present application provides a chip or a chip system, which is applied to an electronic device, and the chip or chip system includes at least one or more processors, and the one or more processors are used to call computer instructions to execute the method described in any aspect or any possible implementation of any aspect.

[0084] In one possible implementation, the chip or chip system described above in the embodiments of the present application further includes at least one memory, in which instructions are stored. The memory may be a storage unit within the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).

[0085] It should be understood that the third to seventh aspects of the embodiments of the present application correspond to the technical solutions of any aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] FIG1 is a schematic flow chart of a multi-stage self-healing process for an electronic device;

[0087] FIG2 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0088] FIG3 is a schematic diagram of a software architecture of an electronic device provided in an embodiment of the present application;

[0089] FIG4 is a schematic flowchart of a fault handling method provided in an embodiment of the present application;

[0090] FIG5 is a schematic flowchart of another fault handling method provided in an embodiment of the present application;

[0091] FIG6 is a schematic flowchart of another fault handling method provided in an embodiment of the present application;

[0092] FIG7 is a schematic flowchart of another fault handling method provided in an embodiment of the present application;

[0093] FIG8 is a schematic block diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] To facilitate a clear description of the technical solutions of the embodiments of the present application, some of the terms and technologies involved in the embodiments of the present application are briefly introduced below:

[0095] 1. Switching cells

[0096] Switching cells may refer to a process in which a communication link between an electronic device and a current network device is transferred to another network device.

[0097] The current location of the electronic device can be covered by multiple cells at the same time. When the electronic device needs to perform wireless communication, it can select one of the multiple cells to reside in to achieve access to the cellular network (such as the long term evolution (LTE) network or the new radio (NR) network). When the electronic device encounters a cellular network failure in the resident cell, it can switch from the resident cell to another cell to obtain better signal quality and faster network speed, which is conducive to repairing the fault.

[0098] In some examples, the switching cell can be implemented by adding a black cell or specifying a registered cell. The switching cell may also be called a bar cell or a black cell, which is not limited in the embodiments of the present application.

[0099] 2. Suppress stand alone (SA) networking

[0100] Suppressing SA may also be referred to as shutting down SA, downgrading the wireless NR, or changing the domain, which is not limited in the embodiments of the present application.

[0101] Suppressing SA is used to indicate that the electronic device turns off a network that uses an independent networking mode. After the electronic device turns off SA, it can use a network that uses a non-standalone (NSA) networking mode. For example, the fifth-generation mobile communication technology (5G) network is a network that uses an independent networking mode, and the fourth-generation mobile communication technology (4G) network is a network that uses a non-standalone networking mode. After the electronic device turns off the 5G network, it can use the 4G network for communication.

[0102] In this way, when an electronic device fails due to the use of a 5G network, the electronic device can repair the failure by suppressing SA.

[0103] It can be understood that the embodiment of the present application uses suppressed SA to indicate the change of mobile communication technology, for example, from the sixth-generation mobile communication technology (6G) to 5G, from 5G to 4G, etc. The embodiment of the present application does not limit the name.

[0104] 3. Re-registration

[0105] Reregistration, also known as re-registration, refers to the process of re-registering an electronic device with a network device to enable communication with the network device. Reregistration typically occurs when communication between the electronic device and the network device is interrupted or unstable. Through reregistration, the electronic device can re-establish a connection with the network device and regain access to the network device.

[0106] For example, when an electronic device fails to use a cellular network due to interruption or instability of communication between the electronic device and a network device, the electronic device can repair the failure by re-registering.

[0107] 4. Switch data switch

[0108] The data switch is used to indicate turning the data switch off and then on again. Turning the data switch off indicates that the electronic device's ability to use a cellular data network is disabled. Turning the data switch on indicates that the electronic device's ability to use a cellular data network is enabled. Cellular data network indicates using a cellular network for data services.

[0109] 5. Restart radio

[0110] Restarting the radio function can be used to re-enable the communication function of an electronic device to restore normal operation. Radio devices may experience malfunctions or unstable connections after extended use or when they encounter a malfunction. Restarting the radio can clear possible software or hardware faults, reinitialize device parameters, and restore normal operation.

[0111] Restarting the radio function may include turning off the radio device, waiting for a period of time (e.g., a few seconds), and then restarting the device. This process can be performed manually, or the electronic device can be set to automatically restart at a specific time. In some examples, restarting the radio function can also be referred to as turning on or off airplane mode.

[0112] For example, when an electronic device freezes when using a cellular network due to prolonged use or a malfunction of the radio device, the electronic device can restart the radio function by turning on airplane mode, waiting a few seconds, and then turning off airplane mode, which helps to repair the freeze.

[0113] 6. Restart your modem

[0114] Restarting a modem may mean turning off the modem, waiting for a period of time, and then turning it back on. An electronic device includes a modem, which provides cellular communication capabilities for the electronic device. When a cellular network failure occurs in the electronic device, the electronic device can recover from the failure by restarting the modem.

[0115] 7. Stationed

[0116] Being on the network means that electronic devices are connected to the operator's network equipment through the Internet.

[0117] 8. Other terms

[0118] In the embodiments of this application, terms such as "first" and "second" are used to distinguish between identical or similar items with substantially the same function or effect. For example, the first fault type and the second fault type are merely used to distinguish between different fault types and do not define their order. Those skilled in the art will understand that terms such as "first" and "second" do not define the quantity or execution order, and do not necessarily define differences between them.

[0119] It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0120] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, c can be single or multiple.

[0121] 9. Electronic devices

[0122] The electronic devices of the embodiments of the present application may include handheld devices, vehicle-mounted devices, etc. with cellular communication functions. For example, some electronic devices include: mobile phones, tablet computers, PDAs, laptop computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks. The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0123] In addition, in the embodiments of the present application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0124] The electronic devices in the embodiments of the present application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0125] 10. Network equipment

[0126] The network device may be an access network (AN) device, or may be referred to as a radio access network (RAN) device. The RAN device may provide access functions for electronic devices and be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side. The RAN device may include 5G, such as a gNB in ​​an NR system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network node constituting a gNB, a transmission and reception point (TRP or transmission point, TP), or a transmission measurement function (TMF), such as a baseband unit (BBU), a centralized unit (CU) or a distributed unit (DU), an RSU with base station functions, or a wired access gateway, or a 5G core network element. Alternatively, the RAN device may also include an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, etc. Alternatively, the RAN device may also include a next-generation mobile communication system, such as 6G access network equipment, such as a 6G base station, or in the next-generation mobile communication system, the network equipment may also have other naming methods, all of which are included in the protection scope of the embodiments of this application, and this application does not impose any limitations on this.

[0127] Currently, electronic devices using cellular networks are prone to prolonged outages. For example, long pauses can occur during gaming or video playback, or persistent call failures can occur during phone calls.

[0128] Electronic devices are pre-programmed with a series of self-healing actions to perform when a fault occurs. When a cellular network failure occurs, the electronic device can recover from the fault through this series of self-healing actions. These actions are triggered in a step-by-step manner based on the impact of the self-healing action. The impact level indicates the impact on the user and / or the ability to recover from the fault. Self-healing actions can include one or more of switching cells, suppressing SA, re-registration, turning data on and off, restarting the radio function, or restarting the modem.

[0129] For example, FIG1 shows a schematic flow chart of a multi-stage self-healing method for an electronic device. As shown in FIG1 , the method may include the following steps:

[0130] S101. When a cellular network failure occurs, the electronic device reads a default self-healing action.

[0131] The default self-healing action may include one or more self-healing actions, which is not limited in the present embodiment. When the default self-healing action includes multiple self-healing actions, these multiple self-healing actions have a preset order, which is based on the degree of impact of the self-healing action.

[0132] S102: The electronic device may perform a self-healing action.

[0133] If the default self-healing action includes one self-healing action, the electronic device may perform this self-healing action. If the default self-healing action includes multiple self-healing actions, and these multiple self-healing actions have a preset order, the electronic device may perform the first self-healing action among the multiple self-healing actions according to the preset order, where the first self-healing action is the self-healing action with the least impact among the multiple self-healing actions.

[0134] S103: After executing the self-healing action, the electronic device starts evaluation.

[0135] After the electronic device performs this self-healing action, it evaluates whether the fault still exists.

[0136] S104: The electronic device determines whether self-healing is successful.

[0137] If the electronic device still has a fault, it means that the self-healing is unsuccessful. The electronic device may determine whether to perform the next level of self-healing action, that is, execute S106.

[0138] If the electronic device does not have a fault, it indicates that the self-healing is successful, and the electronic device may return a self-healing success message, ie, execute S105 .

[0139] S105: If the self-healing is successful, the electronic device returns a message indicating that the self-healing is successful.

[0140] Returning a self-healing success may indicate that the electronic device outputs a self-healing success.

[0141] In one example, if the self-healing is successful, the electronic device may output SUCCESS, which indicates that the self-healing is successful.

[0142] S106: If the self-healing is unsuccessful, the electronic device determines whether to execute the next level of self-healing action.

[0143] Determines whether to execute the next level of self-healing action, which is used to determine whether there are other self-healing actions.

[0144] If the default self-healing action includes one self-healing action, it indicates that no other self-healing actions can be performed, and the electronic device may not perform the next level of self-healing actions. If the default self-healing action includes multiple self-healing actions, it indicates that other self-healing actions can be performed, and the electronic device may perform the second self-healing action among the multiple self-healing actions. The second self-healing action can be considered the next level of action of the first self-healing action. The impact of the second self-healing action is greater than that of the first self-healing action, but less than that of the other self-healing actions in the multiple self-healing actions.

[0145] S107: If the next level of self-healing action is not executed, the electronic device returns to self-healing failure.

[0146] Returning that the self-healing is unsuccessful may indicate that the electronic device outputs that the self-healing is successful.

[0147] In one example, if the next level of self-healing action is not executed, the electronic device may output FALL or reject, where FALL or reject indicates that the self-healing is unsuccessful.

[0148] S108: If the next level of self-healing action is to be executed, the electronic device executes the next level of self-healing action.

[0149] If the next level of self-healing action is executed, after the electronic device executes this self-healing action, it is evaluated whether the fault still exists, that is, the above S103 is executed.

[0150] In order to better understand the method shown in FIG1 , a specific example is provided below for explanation.

[0151] For example, when an electronic device encounters a fault while using a cellular network, the self-healing process that can be executed includes: 1) suppressing SA; 2) turning on and off the data switch; 3) restarting the radio function; and 4) restarting the modem.

[0152] That is, when an electronic device fails, it first executes SA suppression; after executing SA suppression, if the data failure still exists, it executes data switch on / off; after executing data switch on / off, if the failure still exists, it executes radio function restart; after executing radio function restart, if the failure still exists, it executes modem restart.

[0153] This implementation can result in extended fault durations because the default self-healing actions may be unreasonable or ineffective, preventing timely repairs and resulting in extended fault durations. Furthermore, the default self-healing actions are fixed and don't adjust based on actual conditions, resulting in limited flexibility.

[0154] In view of this, an embodiment of the present application provides a fault handling method and related devices, which determine the corresponding self-healing actions based on the fault type, and can adjust the execution order of these self-healing actions, or delete invalid self-healing actions, which is beneficial to increase the probability of successful self-healing actions, and further help reduce the probability of a long fault duration.

[0155] The method provided in the embodiment of the present application can be executed by an electronic device. To facilitate understanding, the hardware structure of the electronic device provided in the embodiment of the present application is first introduced.

[0156] For example, FIG2 shows a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. As shown in FIG2, the electronic device 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, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195, etc.

[0157] Optionally, the above-mentioned sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0158] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0159] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem, 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). The different processing units may be independent devices or integrated into one or more processors. A modem may provide cellular communication capabilities, and electronic devices may use the modem to implement a series of cellular communication functions, such as sending and receiving text messages, 5G-related functions, making and receiving calls, etc.

[0160] The SIM card interface 195 is used to insert a SIM card. The SIM card described in the embodiments of the present application can be understood as a module that provides user information in a cellular network or uses a mobile cellular network. For example, a terminal device equipped with a SIM card slot and a card reader can register for a mobile cellular network by inserting a SIM card. The SIM card can be a physical card (or hard card) or a virtual SIM card (or soft card), such as an eSIM. The specific form of the SIM card is not limited in the embodiments of the present application.

[0161] When the electronic device is equipped with a SIM card, the processor 110 can use the SIM card to establish a network connection. After successful establishment, the cellular network can be used. In the event of a cellular network failure, the processor 110 can obtain the corresponding self-healing actions based on the failure type and adjust the execution order of these self-healing actions, or delete invalid self-healing actions to obtain the required self-healing actions, and then execute the corresponding self-healing actions to repair the failure.

[0162] The software system of the electronic device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a microservice architecture, or a cloud architecture. The layered architecture can adopt the Android system, the Apple (IOS) system, or other operating systems, and the embodiments of the present application are not limited to this. The following uses the Android system with a layered architecture as an example to illustrate the software architecture of the electronic device provided in the embodiments of the present application.

[0163] Figure 3 shows a schematic diagram of the software architecture of an electronic device provided in an embodiment of the present application. As shown in Figure 3, the layered architecture divides the software architecture of the electronic device into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into multiple layers, from top to bottom, including the application layer (applications), the application framework layer (application framework), the hardware abstraction layer (HAL), the kernel layer (kernel), and the modem.

[0164] The application layer can include a series of application packages, which run applications by calling the application programming interface (API) provided by the application framework layer. As shown in Figure 3, the application package can include applications such as browsers, phones, games, and videos.

[0165] The application framework layer provides an API and a programming framework for the applications of the application layer. The application framework layer includes some predefined functions. As shown in Figure 3, the application framework layer may include a view system, a content provider, and a fault handling module, etc. Among them, the fault handling module can determine the type of fault when a fault occurs when the electronic device uses a cellular network, and determine the self-healing action list corresponding to the fault type based on the fault type, and adjust the order of the self-healing actions in the self-healing action list according to the rules provided in the embodiments of the present application, and / or delete the self-healing actions in the self-healing action list to obtain an updated self-healing action list.

[0166] The electronic device can execute the self-healing action with the least impact in the updated self-healing action list. After executing the self-healing action, if a fault still exists, the fault type is the same as the fault type before executing the self-healing action, and the self-healing action has a next-level self-healing action, then the next-level self-healing action of the self-healing action is executed.

[0167] After executing the self-healing action, if a fault still exists, the fault type is the same as the fault type before executing the self-healing action, and the self-healing action has no next-level self-healing action, then the self-healing action ends.

[0168] After executing the self-healing action, if a fault still exists and the fault type is different from the fault type before executing the self-healing action, a self-healing action list corresponding to the fault type is determined based on the current fault type, and the above steps are repeated.

[0169] It should be noted that the fault handling module being located in the application framework layer is merely an example. The fault handling module may also be located in other layers or other chips, and this embodiment of the present application does not limit this.

[0170] The purpose of the HAL layer is to abstract the hardware. It can provide a unified interface for querying hardware devices for upper-layer applications, or it can also provide data storage services for upper-layer applications. As shown in Figure 3, the HAL layer can include a display driver module and sensor hardware abstraction.

[0171] The kernel layer is the layer between hardware and software. The kernel layer is used to drive the hardware to make it work. As shown in Figure 3, the kernel layer can include one or more of the following: display driver and sensor driver.

[0172] The modem can provide cellular communication functions and perform some related self-healing actions.

[0173] It should be understood that in some embodiments, layers that implement the same function may be referred to by other names, or a layer that can implement the functions of multiple layers may be considered as one layer, or a layer that can implement the functions of multiple layers may be divided into multiple layers. This embodiment of the present application does not limit this.

[0174] The software and hardware structures of the electronic device in the embodiment of the present application are introduced above in conjunction with FIG. 2 and FIG. 3 . The method applied to the electronic device is described below.

[0175] For example, FIG4 shows a schematic flow chart of a fault handling method provided in an embodiment of the present application. As shown in FIG4 , the method 400 may include the following steps:

[0176] S401: When a cellular network failure occurs in an electronic device, a default self-healing action is read based on the type of failure.

[0177] The electronic device has a preset correspondence between fault types and self-healing actions. When a fault occurs, the self-healing action corresponding to the fault type can be obtained based on the fault type. The default self-healing action may include one or more self-healing actions, which are not limited in the embodiments of the present application. When the default self-healing action includes multiple self-healing actions, these multiple self-healing actions have a preset order, which is sorted by the degree of impact of the self-healing action.

[0178] For example, Table 1 shows a schematic diagram of the correspondence between fault types and self-healing actions.

[0179] Table 1

[0180] As shown in Table 1, fault types can include call signaling anomalies, data freezes, weak signals, and data activation failures. An electronic device can identify a call signaling anomaly as a fault type in the following scenario: In response to a call request, the electronic device sends a request message to a network device, but the network device rejects the request message for some reason, causing the call to fail. When the fault type is call signaling anomaly, the self-healing actions that the electronic device can perform include switching cells and suppressing SA.

[0181] If an electronic device experiences lag while executing a cellular data service, the fault type can be determined to be data lag. Cellular data services can be understood as using a cellular network to open a webpage, play a video or music, or download an application. When the fault type is data lag, the self-healing actions that the electronic device can perform include switching cells, suppressing SA, reregistering, and restarting the radio function.

[0182] When the electronic device uses a 5G cellular network and detects a weak 5G signal, it can be determined that the fault type is a weak signal. When the fault type is a weak signal, the self-healing action that the electronic device can perform may include suppressing SA.

[0183] When an electronic device switches from an idle state (i.e., not executing data services) to a service state (i.e., executing data services), it may first activate the link with the network device before executing cellular data services. If activation fails, the electronic device may determine that the failure type is a data activation failure. When the failure type is a data activation failure, the electronic device may perform self-healing actions including suppressing SA, re-registering, and restarting the radio function.

[0184] In the example shown in Table 1, when an electronic device experiences a cellular network failure, the fault type is determined, and a default self-healing action is obtained based on the corresponding relationship between the fault type and Table 1. The default self-healing action may also be referred to as a default self-healing action list or a self-healing action list, which is not limited in the present embodiment.

[0185] S402: The electronic device filters the default self-healing action based on the user scenario, the prior information, and one or more pieces of information in the link information to obtain an updated self-healing action.

[0186] In order to reduce the probability that the default self-healing actions include unreasonable or invalid self-healing actions, the electronic device can filter the default self-healing actions based on one or more information in the user scenario, prior information, and link information to delete unreasonable or invalid self-healing actions, and can adjust the execution order of the self-healing actions, which is conducive to shortening the time to repair the fault.

[0187] 1) User Scenario

[0188] The user scenario is used to represent the environment or state that the electronic device is in. In the embodiment of the present application, the user scenario may include one or more of a weak field environment, a speed-sensitive scenario, or a high-speed scenario.

[0189] A weak field environment indicates that the electronic device is located in a location with a poor network signal, such as a 5G or 4G signal. In a weak field environment, electronic device failures are caused by the environment, and the probability of the self-healing actions performed by the electronic device repairing the failure is low. Some self-healing actions may even cause slow internet access when the electronic device is in a non-weak field environment, resulting in increased negative returns. Therefore, when an electronic device is in a weak field environment, all self-healing actions are blocked, that is, the default self-healing actions are deleted.

[0190] Applications used to represent electronic device operation in rate-sensitive scenarios include applications that reflect operating speed. These applications include applications used to test the operating speed of electronic devices and applications that display operating speed. For example, applications that test the configuration and performance of electronic devices can test the operating speed of electronic devices. Applications used to download applications can display the download speed. In rate-sensitive scenarios, the default self-healing actions may include some self-healing actions that affect the operating speed. To reduce the impact on the operating speed, the electronic device can delete the self-healing actions that affect the operating speed from the default self-healing actions.

[0191] For example, if an electronic device experiences a cellular network failure while downloading a game application, the device displays a download rate. If the default self-healing action includes suppressing SA, switching from 5G to 4G may reduce the download rate. The electronic device will display the reduced download rate, affecting the user experience. In this scenario, the electronic device can delete the suppressing SA in the default self-healing action.

[0192] High-speed scenarios are used when an electronic device is in a high-speed mobile state. For example, the device is on a high-speed train or bus. In high-speed scenarios, network fluctuations are severe, making some self-healing actions ineffective. The device can delete any ineffective self-healing actions from the default set of self-healing actions.

[0193] For example, if the electronic device moves, the cell where it is located changes, rendering the self-healing action useless. If the electronic device moves, the location where it is located loses 4G signal, rendering the self-healing action useless. Therefore, if the default self-healing action includes cell switching or SA suppression, the electronic device can delete the cell switching or SA suppression.

[0194] 2) Prior Information

[0195] Prior information is used to represent the historical execution status of the self-healing action, such as the cell in which the electronic device is located when the self-healing action is executed, the operating status of the electronic device when the self-healing action is executed, whether the self-healing action is successful, the impact of the self-healing action, and the last execution time, etc.

[0196] The electronic device may adjust the execution order of self-healing actions according to one or more of the following rules:

[0197] If the number of self-healing times reaches T in the same cell and under the same motion state, and the success rate is greater than the S1 threshold, the self-healing action is advanced;

[0198] If the number of self-healing times in the same cell and the same motion state reaches T and the success rate is less than the S2 threshold, the self-healing action will be deleted, where S2 is less than S1;

[0199] For self-healing actions with a relatively large impact, such as restarting the radio function and restarting the modem, the order of the self-healing actions is not adjusted; or,

[0200] Each self-healing action is assigned a protection time. After a self-healing action is executed, it cannot be executed again within the corresponding protection time. For example, the suppression of SA function is set to a protection time of 5 minutes. The re-registration function is set to a protection time of 15 minutes. The restart radio function is set to a protection time of 30 minutes.

[0201] The protection time can be fixed or adjustable, which is not limited in the present embodiment. If the protection time is adjustable, the protection time can be changed according to the environment in which the electronic device is located, which is more flexible.

[0202] In some examples, the protection time of the self-healing action may be positively correlated with the impact degree of the self-healing action, that is, the greater the impact degree of the self-healing action, the longer the protection time of the self-healing action.

[0203] It is understandable that the electronic device can start a timer when each self-healing action is executed, and record the cell in which the electronic device is located and the operating status of the electronic device, and can calculate the success rate of the self-healing action based on whether the self-healing action is successful.

[0204] 3) Link information

[0205] Link information is used to indicate the link status between an electronic device and a network device. For example, link information may include "no service," "current service status," "cell is idle," "cell is connected," and network status. "No service" indicates that the electronic device failed to establish network access. "Current service status" indicates that the electronic device successfully established network access. "Idle" indicates that the communication link between the electronic device and the network device was not successfully established. "Connected" indicates that the communication link between the electronic device and the network device was successfully established. Network status indicates the type of network signal in the cell where the electronic device is located.

[0206] The electronic device can determine the connection status between the electronic device and the network device based on the link information, and can delete invalid self-healing actions included in some default actions.

[0207] For example, when an electronic device encounters a cellular network failure, the cell where the electronic device is located is in an idle state, and switching cells can only be supported in a connected state. Therefore, if the default self-healing action includes switching cells, the electronic device can delete the switching cell in the default self-healing action.

[0208] For example, when the electronic device is out of service, self-healing actions such as switching cells, suppressing SA, and re-registration cannot take effect, so the electronic device can intercept self-healing actions such as switching cells, suppressing SA, and re-registration in the default self-healing actions.

[0209] For example, the network signal type of the cell where the electronic device is located is 4G, and suppressing SA cannot take effect, so the electronic device can intercept suppressing SA in the default self-healing action.

[0210] S403: The electronic device may perform a self-healing action.

[0211] If the updated self-healing action includes one self-healing action, the electronic device may execute the self-healing action. If the updated self-healing action includes multiple self-healing actions, and the multiple self-healing actions are ordered, the electronic device may execute the first self-healing action among the multiple self-healing actions.

[0212] S404: After executing the self-healing action, the electronic device starts evaluation.

[0213] After the electronic device performs this self-healing action, it evaluates whether the fault still exists.

[0214] S405: The electronic device determines whether self-healing is successful.

[0215] If the electronic device still has a fault, it indicates that self-healing was unsuccessful. The electronic device can then determine whether the fault type is the same as the fault type before the self-healing action was executed. If the fault type is the same as the fault type before the self-healing action was executed, the electronic device can determine whether to execute the next level of self-healing action, that is, execute S409. If the fault type is different from the fault type before the self-healing action was executed, the electronic device can determine the corresponding self-healing action based on the current fault type and execute S402 above.

[0216] If the electronic device does not have a fault, it indicates that the self-healing is successful, and the electronic device may return a self-healing success message, ie, execute S406 .

[0217] S406: If the self-healing is successful, the electronic device returns a self-healing success message.

[0218] S407: If the self-healing is unsuccessful, the electronic device determines whether to execute the next level of self-healing action.

[0219] S408: If the next level of self-healing action is not executed, the electronic device returns to self-healing failure.

[0220] S409: If the next level of self-healing action is to be executed, the electronic device executes the next level of self-healing action.

[0221] S406 to S409 can refer to the above S105 to S108 and will not be repeated here.

[0222] The fault handling method provided in the embodiments of the present application includes different default self-healing actions for different fault types. Using corresponding self-healing actions for different faults helps increase the probability of successful self-healing, thereby shortening the duration of the fault. Furthermore, based on one or more pieces of information including user scenarios, prior information, and link information, self-healing actions are screened to remove unreasonable or invalid self-healing actions, and the execution order of self-healing actions can be adjusted, thereby increasing the probability of successful self-healing and shortening the duration of fault repair.

[0223] The above-mentioned S402, the electronic device screening the self-healing action based on one or more information of the user scenario, the prior information, and the link information to obtain an updated self-healing action, may include: the electronic device screening the self-healing action based on the user scenario to obtain an updated self-healing action. The user scenario includes a weak field environment, a speed-sensitive scenario, a high-speed scenario, and a general scenario. The general scenario may be a scenario other than a weak field environment, a speed-sensitive scenario, and a high-speed scenario.

[0224] Electronic devices use different filtering rules in different scenarios. For example, Table 2 shows a correspondence between a user scenario and filtering rules. The filtering rules can also be referred to as self-healing action management, which is not limited in this embodiment of the present application.

[0225] Table 2

[0226] As shown in Table 2, if the user scenario is a general scenario, it means that the network is stable and the electronic device does not need to filter the self-healing action. The updated self-healing action is the same as the default self-healing action.

[0227] If the user scenario is in a weak field environment, it means that the network signal is weak and the environment is unstable. In this case, the self-healing action cannot repair the fault. The electronic device can intercept all self-healing actions. In this way, the updated self-healing action does not include any self-healing actions. In this case, when the user scenario is in a non-weak field environment, the fault of the electronic device is repaired.

[0228] If the user scenario is rate-sensitive, it means that the user desires to reside on a high-standard network. In this case, suppressing SA is an unreasonable self-healing action. The electronic device can intercept and suppress SA. In this way, the updated self-healing action does not include suppressing SA.

[0229] If the user scenario is a high-speed scenario, it means that the network fluctuates violently. At this time, the self-healing action of actively triggering network switching (such as switching cells and suppressing SA) cannot take effect. The electronic device can actively trigger the self-healing action of network switching. In this way, the updated self-healing action does not include the self-healing action of actively triggering network switching.

[0230] To better understand this method, it is described below with reference to FIG5 .

[0231] FIG5 shows a schematic flow chart of a fault handling method provided by an embodiment of the present application. As shown in FIG5 , the method may include the following steps:

[0232] S501: The electronic device receives a self-healing request, where the self-healing request is used to request execution of a self-healing action.

[0233] When a cellular network failure occurs, the electronic device may receive a self-healing request. In some implementations, the self-healing request may include the type of failure.

[0234] S502: The electronic device reads a default self-healing action in a configuration file.

[0235] Based on the self-healing request, the electronic device can obtain the default self-healing action from the configuration file. The configuration file can include various self-healing actions, and these self-healing actions are sorted by impact.

[0236] In some examples, the configuration file stores the corresponding relationship shown in Table 1. Based on the fault type in the self-healing request, the electronic device can obtain the self-healing action corresponding to the fault type from the configuration file.

[0237] S503: The electronic device reads the user scenario.

[0238] The electronic device may detect the user scenario in real time or periodically, and may store the user scenario in a memory or storage, and the electronic device may read the user scenario from the memory or storage.

[0239] The user scenario includes one or more of a weak field environment, a rate-sensitive scenario, or a high-speed scenario. In addition to the weak field environment, the rate-sensitive scenario, and the high-speed scenario, the user scenario may also include a general scenario.

[0240] The electronic device may detect the user scenario in the following manner:

[0241] 1) Electronic devices can identify whether they are in a weak field environment by determining network signal strength. Network signal strength can include one or more of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), or signal-to-noise ratio (SNR).

[0242] For example, an electronic device can determine whether it is in a weak field environment based on the strength of RSRP. If the RSRP strength is greater than or equal to a threshold value S, the electronic device is in a non-weak field environment. If the RSRP strength is less than the threshold value S, the electronic device is in a weak field environment. In some examples, S can be -115 or -110, which is not limited in the present embodiment.

[0243] Exemplarily, the electronic device may determine whether the electronic device is in a weak field environment based on the strength of RSRP, the strength of RSRQ, and the strength of SNR.

[0244] The threshold values ​​corresponding to the RSRP strength, RSRQ strength, and SNR strength may be shown in Table 3.

[0245] Table 3

[0246] As shown in Table III, the range of RSRP is (-157, 30) decibel milliwatts (dBm), the range of RSRQ is (-43.5, 20) dB, and the range of SNR is (-23.5, 40) dB.

[0247] If the communication technology between the electronic device and the network device uses microwave (mmWave) technology, the network signal RSRP < -115, the network signal RSRQ < -16, and the network signal SNR < 5, the electronic device can determine that the electronic device is in a weak field environment. If these conditions are not met, the electronic device can determine that the electronic device is in a non-weak field environment.

[0248] If the communication technology between the electronic device and the network device uses Sub 6 GHz technology, the RSRP of the network signal is less than -115, the RSRQ of the network signal is less than -16, and the SNR of the network signal is less than 5, the electronic device can determine that the electronic device is in a weak field environment. If these conditions are not met, the electronic device can determine that the electronic device is in a non-weak field environment.

[0249] If the communication technology between the electronic device and the network device uses Sub 1 GHz technology, the RSRP of the network signal is less than -115, the RSRQ of the network signal is less than -16, and the SNR of the network signal is less than 5, the electronic device can determine that the electronic device is in a weak field environment. If these conditions are not met, the electronic device can determine that the electronic device is in a non-weak field environment.

[0250] It should be noted that in the above Table 3, the thresholds corresponding to different communication technologies are the same, which is only an example. The thresholds corresponding to different communication technologies may also be different, and the embodiments of the present application do not limit this.

[0251] 2) The electronic device can identify whether it is in a rate-sensitive scenario by determining whether the application running on the electronic device is in the whitelist.

[0252] The electronic device may be preset with a whitelist, which may include one or more applications. The applications in the whitelist may be applications for testing the operating speed of the electronic device, or applications for displaying the operating speed of the electronic device.

[0253] The whitelist may include one or more of an application identifier, name, or application package name, which is not limited in the embodiments of the present application. If the application running on the electronic device can be found in the whitelist, the electronic device can determine that the electronic device is in a rate-sensitive scenario. If the application running on the electronic device is not found in the whitelist, the electronic device can determine that the electronic device is in a non-rate-sensitive scenario.

[0254] For example, the electronic device can obtain the application package names of the applications running on the electronic device and determine whether there are any application package names included in the whitelist that are the same as these application package names. If so, it means that the application running on the electronic device can be found in the whitelist, and the electronic device can determine that the electronic device is in a rate-sensitive scenario. If not, it means that the application running on the electronic device is not found in the whitelist, and the electronic device can determine that the electronic device is in a non-rate-sensitive scenario.

[0255] 3) Electronic devices can identify whether they are in a high-speed scenario by determining whether sensor data meets a threshold.

[0256] In some implementations, the sensor data may include acceleration data and / or velocity data. The electronic device may be preset with a threshold. When the acceleration data and / or velocity data meet the threshold, the electronic device determines that the electronic device is in a high-speed scenario. When the acceleration data and / or velocity data do not meet the threshold, the electronic device determines that the electronic device is in a non-high-speed scenario.

[0257] It should be noted that identifying whether a high-speed scene is in progress by judging whether the sensor data meets the threshold is merely an example, and the embodiments of the present application do not limit the specific method of identifying a high-speed scene.

[0258] S504: The electronic device determines whether the user scenario includes a weak field environment.

[0259] S505: If the user scenario includes a weak field environment, the electronic device intercepts a default self-healing action.

[0260] As shown in Table 2 above, if the user scenario includes a weak field environment, and the screening rule corresponding to the weak field environment is to intercept all self-healing actions, the electronic device can intercept the default self-healing action, that is, not perform the self-healing action.

[0261] For example, if an electronic device experiences persistent freezing while playing a video and detects data freezing as the fault type, in the example shown in Table 1 above, the electronic device may obtain a default self-healing action, which may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the RSRP strength is less than a threshold value S and the user scenario includes a weak field environment, the electronic device intercepts the default self-healing action, i.e., does not perform cell switching, suppressing SA, re-registering, or restarting the radio function.

[0262] S506: If the user scenario does not include a weak field environment, the electronic device determines whether the user scenario includes a rate-sensitive scenario.

[0263] S507: If the user scenario includes a rate-sensitive scenario, the electronic device intercepts a self-healing action that affects the rate.

[0264] As shown in Table 2 above, if the user scenario includes a rate-sensitive scenario, and the screening rule corresponding to the rate-sensitive scenario is to intercept self-healing actions that affect the rate, then the electronic device can intercept self-healing actions that affect the rate, for example, the electronic device can intercept and suppress SA.

[0265] For example, if an electronic device experiences a persistent freeze while playing a video and detects data freeze as the fault type, in the example shown in Table 1 above, the electronic device may obtain a default self-healing action that may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the applications running on the electronic device include an app store for downloading applications, and the app store is downloading a game application, the user scenario includes a rate-sensitive scenario, and the electronic device intercepts the self-healing action of suppressing SA. In this way, the updated self-healing action includes switching cells -> re-registering -> restarting the radio function.

[0266] S508: If the user scenario does not include a rate-sensitive scenario, or after intercepting a self-healing action that affects the rate, the electronic device determines whether it is a high-speed scenario.

[0267] S509: If the user scenario includes a high-speed scenario, intercept the self-healing action that actively triggers network switching.

[0268] As shown in Table 2 above, if the user scenario includes a high-speed scenario, and the screening rule corresponding to the high-speed scenario is to intercept the self-healing action that actively triggers the network switching, then the electronic device can intercept the self-healing action that actively triggers the network switching. For example, the electronic device can intercept the switching cell and suppress SA.

[0269] For example, after intercepting a rate-impacting self-healing action, the updated self-healing action includes cell switching -> re-registration -> radio restart. If the user scenario includes a high-speed scenario, the electronic device may intercept the cell switching and suppress SA. In this case, the updated self-healing action includes re-registration -> radio restart.

[0270] S510: If the user scenario does not include a high-speed scenario, or after intercepting the self-healing action that actively triggers network switching, the electronic device performs the next step of screening.

[0271] In some examples, if the user scenario does not include a high-speed scenario, the user scenario may be a general scenario, and the screening rule corresponding to the general scenario is the default self-healing action, that is, no action in the default self-healing action is intercepted, and the next step of screening can be performed. The next step of screening can be the electronic device screening the default self-healing action based on prior information and / or link information.

[0272] In other examples, after intercepting the self-healing action that actively triggers network switching, the electronic device can proceed to the next step of screening.

[0273] If the user scenario does not include a high-speed scenario, or after intercepting the self-healing action that actively triggers a network switch, the electronic device performs the next step of screening. This is only an example. In other examples, if the user scenario does not include a high-speed scenario, or after intercepting the self-healing action that actively triggers a network switch, the electronic device may perform the above steps S403 to S409.

[0274] The fault handling method provided in the embodiment of the present application filters the default self-healing actions based on the user scenario to delete unreasonable or invalid self-healing actions, which is beneficial to improving the probability of successful self-healing and further beneficial to shortening the time to repair the fault.

[0275] The above-mentioned S402, the electronic device filters the default self-healing action based on the user scenario, prior information and one or more information in the link information to obtain the updated self-healing action, may include: the electronic device filters the default self-healing action based on the prior information to obtain the updated self-healing action.

[0276] The electronic device can adjust the order of self-healing actions based on prior information to obtain updated self-healing actions.

[0277] To better understand this method, it is described below with reference to FIG6 .

[0278] For example, FIG6 shows a schematic flow chart of a fault handling method provided in an embodiment of the present application. As shown in FIG6 , the method may include the following steps:

[0279] S601: The electronic device reads a default self-healing action.

[0280] When the electronic device screens the self-healing actions based on the prior information, the default self-healing actions may be traversed, and each of the default self-healing actions may be read in sequence.

[0281] A self-healing action in the default self-healing actions is read, wherein the self-healing action may be any self-healing action in the default self-healing actions, which is not limited in the embodiment of the present application.

[0282] S602: The electronic device determines whether the number of self-healing actions reaches T times and whether the success rate is greater than S1.

[0283] The electronic device may determine whether the number of self-healing actions in the same cell and the same motion state reaches T times, and whether the success rate is greater than the S1 threshold. If the conditions are met, the electronic device may execute S603. If the conditions are not met, the electronic device may execute S604.

[0284] S603: If the number of self-healing actions reaches T and the success rate is greater than S1, the electronic device adjusts the sequence and advances the self-healing action.

[0285] If the number of self-healing attempts reaches T in the same cell and under the same motion state, and the success rate is greater than S1, it indicates that the self-healing action has a high probability of repairing the fault, and the execution order of the self-healing action can be advanced. If the self-healing action is the first self-healing action that meets the conditions, the electronic device can adjust the self-healing action to the first self-healing action in the default self-healing action. If the self-healing action is not the first self-healing action that meets the conditions, the electronic device can adjust it to after the last self-healing action that meets the conditions.

[0286] Exemplarily, T is 5, and S1 is 90%. If the electronic device continues to freeze when playing a video and a fault occurs, the electronic device detects that the fault type is data freeze. In the example shown in Table 1 above, the electronic device can obtain the default self-healing action which may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the self-healing action read by the electronic device is to suppress SA, and the number of self-healing times of suppressing SA in the same cell and the same motion state reaches 5 times, and the success rate is greater than 90%, the electronic device will adjust the suppression SA to before switching the cell, and the updated self-healing action is: suppress SA -> switching cells -> re-registering -> restarting the radio function.

[0287] Optionally, if the number of self-healing actions reaches T and the success rate is greater than S1, the electronic device adjusts the order and advances the self-healing action. This may include: if the number of self-healing actions reaches T and the success rate is greater than S1, the electronic device determines whether the self-healing action is a preset self-healing action, and if not, advances the self-healing action. A preset self-healing action is a self-healing action with a relatively large impact. If it is a preset self-healing action, the electronic device does not advance the self-healing action.

[0288] In some examples, the preset self-healing action is restarting the radio function and / or restarting the modem. If the number of times SA self-healing is suppressed reaches T times, and the success rate is greater than S1, the electronic device determines whether suppressing SA is a preset self-healing action. If suppressing SA is not a preset self-healing action, suppressing SA is brought forward. If the number of times radio self-healing is restarted reaches T times, and the success rate is greater than S1, the electronic device determines whether restarting the radio function is a preset self-healing action. If restarting the radio function is a preset self-healing action, suppressing restarting the radio function is not brought forward. In other words, the execution order of restarting the radio function remains unchanged.

[0289] In this way, the impact on users can be considered while improving the ability to repair faults.

[0290] S604: If the number of self-healing actions has not reached T times, or the success rate is not greater than S1, the electronic device may determine whether the number of self-healing actions has reached T times, and whether the success rate is greater than S2.

[0291] If the number of self-healing times in the same cell and the same motion state does not reach T times, and the success rate is not greater than S1, the electronic device can determine whether the number of self-healing times in the same cell and the same motion state reaches T times, and whether the success rate is less than S2.

[0292] S605: If the number of self-healing times reaches T and the success rate is less than S2, the electronic device deletes the self-healing action.

[0293] If the number of self-healing actions reaches T and the success rate is less than S2, it means that the probability that the self-healing action can repair the fault is low, and the self-healing action can be deleted.

[0294] Exemplarily, T is 5, S1 is 90%, and S2 is 5%. If the electronic device continues to freeze when playing a video and a fault occurs, the electronic device detects that the fault type is data freeze. In the example shown in Table 1 above, the electronic device can obtain the default self-healing action which may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the self-healing action read by the electronic device is switching cells, and the success rate of switching cells in the same cell and the same motion state is not greater than 90%, and at the same time, the number of self-healing actions of switching cells in the same cell and the same motion state reaches T times, and the success rate is less than 5%, then the electronic device will delete the switching cell, and the updated self-healing action is: suppressing SA -> re-registering -> restarting the radio function.

[0295] S606: If the number of self-healing times of the self-healing action does not reach T times and the success rate is not less than S2, the electronic device may determine whether the self-healing action is within its corresponding protection time.

[0296] Each self-healing action corresponds to a protection time, during which the self-healing action will not be repeated. Therefore, the electronic device can determine whether the self-healing action is within its corresponding protection time to decide whether to execute the self-healing action.

[0297] S607: If the self-healing action is not within its corresponding protection time, read the next self-healing action in the default self-healing action.

[0298] If the self-healing action is not within its corresponding protection time, the self-healing action will not be adjusted, and the next self-healing action in the default self-healing action can be read. The above steps S602 to S607 are repeated for the next self-healing action until all self-healing actions in the default self-healing action are read.

[0299] If the self-healing action is within its corresponding protection time, the electronic device may delete the self-healing action, ie, execute S605.

[0300] For example, if an electronic device experiences a persistent freeze while playing a video and detects data freeze as the fault type, in the example shown in Table 1 above, the electronic device may obtain a default self-healing action that may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the self-healing action read by the electronic device is suppressing SA, and the suppression SA is within its corresponding protection time of 5 minutes, the electronic device may delete the suppression SA and obtain the switching cells -> re-registering -> restarting the radio function.

[0301] The fault handling method provided in the embodiment of the present application can sort the default self-healing actions based on prior information, so that the self-healing actions that have a higher probability of repairing the fault are executed first, which is conducive to shortening the time to repair the fault.

[0302] The method shown in FIG6 above describes how to filter the default self-healing action based on prior information to obtain an updated self-healing action. In another example, the electronic device can also filter the default self-healing action based on user scenarios and prior information to obtain an updated self-healing action.

[0303] In one implementation, the electronic device may filter the self-healing action obtained based on the method shown in FIG. 5 based on prior information to obtain an updated self-healing action.

[0304] In another implementation, the electronic device may filter the self-healing actions obtained based on the method shown in FIG. 6 based on the user scenario to obtain updated self-healing actions.

[0305] This will help shorten the time it takes to repair the problem.

[0306] The above-mentioned S402, the electronic device filters the default self-healing action based on the user scenario, prior information and one or more information in the link information to obtain the updated self-healing action, may include: the electronic device filters the default self-healing action based on the link information to obtain the updated self-healing action.

[0307] The electronic device can delete invalid actions based on the link information and obtain updated self-healing actions. The link information may include no service, current service status, idle cell status, connected cell status, and network status.

[0308] To better understand this method, it is described below with reference to FIG7 .

[0309] For example, Figure 7 shows a schematic flow chart of a fault handling method provided in an embodiment of the present application. As shown in Figure 7, the method may include the following steps:

[0310] S701: The electronic device reads a default self-healing action in a configuration file.

[0311] This step may refer to the above-mentioned S502 and will not be described in detail here.

[0312] S702: The electronic device reads the current link status.

[0313] The electronic device can monitor the link status between the electronic device and the network device and store the monitored link status in a memory or storage. After reading the default self-healing action, the electronic device can read the current link status to filter the default self-healing action based on the current link status.

[0314] S703: The electronic device determines whether the current link status is no service.

[0315] S704: If the current link status is no service, the electronic device may intercept a default self-healing action.

[0316] If the current link status is No Service, it means that the electronic device has not successfully logged on to the network. At this time, the probability that all self-healing actions can repair the fault is small. Therefore, the electronic device can intercept the default self-healing action. In this way, the electronic device does not need to perform self-healing actions.

[0317] S705: If the current link status is not no service, the electronic device may determine whether the cell where the electronic device is located is in an idle state.

[0318] If the current link status is not "No Service," it indicates successful network access. The electronic device can then determine whether the cell it is in is idle, i.e., whether the communication link between the electronic device and the network device has not been successfully established. A communication link must be established before service data can be transmitted.

[0319] S706: If the cell where the electronic device is located is in an idle state, the electronic device intercepts a self-healing action executed in a connected state.

[0320] If the cell where the electronic device is located is in an idle state, it means that the communication link between the electronic device and the network device has not been successfully established. At this time, the self-healing action that can be performed in the connected state is invalid, and self-healing cannot be successfully achieved even if it is performed. Therefore, the electronic device intercepts the self-healing action performed in the connected state.

[0321] Exemplarily, the self-healing action performed in the connected state may include switching cells. If an electronic device continues to freeze while playing a video and a fault occurs, and the electronic device detects that the fault type is data freeze, in the example shown in Table 1 above, the electronic device may obtain a default self-healing action that may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the cell where the electronic device is located is in an idle state, the electronic device intercepts the switching cell, that is, deletes the switching cell, and obtains an updated self-healing action of: suppressing SA -> re-registering -> restarting the radio function.

[0322] S707. If the cell where the electronic device is located is not in an idle state, the electronic device determines whether the network signal type of the cell where the electronic device is located is a 5G signal.

[0323] If the cell where the electronic device is located is not in an idle state, it means that the cell where the electronic device is located is in a connected state, and the communication link between the electronic device and the network device is successfully established. The electronic device can determine whether the network signal type of the cell is a 5G signal.

[0324] It should be noted that the electronic device determining whether the network signal type of the cell where the electronic device is located is a 5G signal is only an example. In other examples, the electronic device can determine whether the network signal type of the cell where the electronic device is located is a 6G signal or a 4G signal. The embodiments of the present application do not limit this.

[0325] S708. If the network signal type of the cell where the electronic device is located is not a 5G signal, the electronic device intercepts a self-healing action related to the 5G signal.

[0326] If the network signal type of the cell where the electronic device is located is not a 5G signal, the self-healing action related to the 5G signal is invalid and cannot be successfully self-healed even if executed. Therefore, the electronic device intercepts the self-healing action related to the 5G signal. For example, the electronic device can intercept and suppress SA.

[0327] If the network signal type of the cell where the electronic device is located is a 5G signal, or after intercepting the self-healing action related to the 5G signal, the electronic device can proceed to the next step of screening. The next step of screening can be for the electronic device to screen the default self-healing action based on prior information and / or user scenarios.

[0328] If the network signal type of the cell where the electronic device is located is a 5G signal, or after the self-healing action related to the interception of the 5G signal is performed, the electronic device can proceed to the next step of screening. This is just an example. In other examples, if the network signal type of the cell where the electronic device is located is a 5G signal, or after the self-healing action related to the interception of the 5G signal is performed, the electronic device can perform the above S403 to S409.

[0329] The fault handling method provided in the embodiment of the present application filters the default self-healing actions based on link information to delete unreasonable or invalid self-healing actions, which is beneficial to improving the probability of successful self-healing and further beneficial to shortening the time to repair the fault.

[0330] The above describes the method provided in the embodiment of the present application from the perspective of specific implementation of an electronic device. The following describes the method provided in the embodiment of the present application in combination with application scenarios.

[0331] Exemplarily, the fault handling method provided by an embodiment of the present application may include: when the network fault of the electronic device is a first fault type and the movement speed of the electronic device is a first speed, the electronic device performs a first fault repair action, wherein the first fault type corresponds to a first fault repair action list, and the first fault repair action includes an action in the first fault repair action list that is not used to trigger network switching; when the network fault of the electronic device is a first fault type and the movement speed of the electronic device is a second speed, the electronic device performs a second fault repair action, wherein the second fault repair action includes an action in the first fault repair action list that is used to trigger network switching, and the second speed is less than the first speed.

[0332] In this way, when the electronic device is in a high-speed scenario, invalid or unreasonable fault repair actions in the first fault repair action list are not executed, which is conducive to shortening the fault duration.

[0333] Optionally, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, information reflecting the network rate is also displayed in the electronic device, and the first fault repair action does not include actions in the first fault repair action list that affect the network rate.

[0334] In this way, when the electronic device is in a high-speed scenario and in a rate-sensitive scenario, no action that affects the network rate is performed, which helps to shorten the fault duration.

[0335] Optionally, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, the signal strength of the network to which the electronic device is connected is greater than or equal to a strength threshold.

[0336] Optionally, when the network fault of the electronic device is of the first fault type and the movement speed of the electronic device is the first speed, the electronic device is still in an idle state, and the first fault repair action does not include actions in the first fault repair action list that cannot be performed in the idle state. The idle state is used to indicate that the link between the electronic device and the network device to which it is connected has not been established.

[0337] Optionally, when the network failure of the electronic device is of the first failure type and the movement speed of the electronic device is the first speed, the electronic device is still in a service state, and the service state is used to indicate that the electronic device is successfully stationed on the network.

[0338] It should be noted that the module names involved in the embodiments of the present application can be defined as other names as long as the functions of each module can be achieved, and there is no specific restriction on the names of the modules.

[0339] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0340] The fault handling method of the embodiment of the present application has been described above. The following describes the apparatus for performing the above method provided in the embodiment of the present application. Those skilled in the art will appreciate that the method and apparatus can be combined and referenced with each other, and the relevant apparatus provided in the embodiment of the present application can perform the steps in the above fault handling method.

[0341] FIG8 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. As shown in FIG8 , the chip 80 includes one or more (including two) processors 801 , a communication circuit 802 , a communication interface 803 and a memory 804 .

[0342] In some implementations, the memory 804 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

[0343] The method for processing network jams described in the above embodiments of the present application can be applied to the processor 801, or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method for processing network jams can be completed by an integrated logic circuit of hardware in the processor 801 or instructions in the form of software. The above processor 801 can be a general-purpose processor (for example, a microprocessor or a conventional processor), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates, transistor logic devices or discrete hardware components. The processor 801 can implement or execute the methods, steps and logic block diagrams related to each processing disclosed in the embodiments of the present application.

[0344] The steps of the method for processing network freezes disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. Among them, the software module can be located in a mature storage medium in the art such as a random access memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable read only memory (EEPROM). The storage medium is located in the memory 804, and the processor 801 reads the information in the memory 804 and completes the steps of the above method in combination with its hardware.

[0345] The processor 801 , the memory 804 , and the communication interface 803 may communicate with each other via a communication line 802 .

[0346] In the above embodiment, the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product, wherein the computer program product may be pre-written in the memory or downloaded and installed in the memory in the form of software.

[0347] The fault handling method provided in the embodiment of the present application can be applied to electronic devices with communication functions. The electronic devices include terminal devices. The specific device form of the terminal device can refer to the above related descriptions and will not be repeated here.

[0348] An embodiment of the present application provides a terminal device, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the terminal device to execute the above-mentioned fault handling method.

[0349] The present application provides a chip or chip system. The chip or chip system is applied to an electronic device and includes at least one or more processors configured to invoke computer instructions to execute the fault handling method described in the above embodiment. The implementation principles and technical effects are similar to those of the above-described related embodiments and are not further elaborated here.

[0350] The embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed by an electronic device, the above-mentioned fault handling method is implemented. The fault handling method described in the above embodiment can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

[0351] In one possible implementation, computer-readable media may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium designed to carry or store the desired program code in the form of instructions or data structures and accessible by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave are used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and optical disk as used herein include optical disk, laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk, where disks generally reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0352] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program code runs on an electronic device, the electronic device executes the above-mentioned fault handling method.

[0353] The present application embodiment is described with reference to the flow chart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present application.It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processing unit of general-purpose computer, special-purpose computer, embedded processing machine or other programmable device to produce a machine, so that the instruction executed by the processing unit of computer or other programmable data processing device produces the device for realizing the function specified in one flow chart flow or multiple flows and / or one block or multiple blocks of block diagram.

[0354] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present invention should be included in the scope of protection of the present invention.

Claims

1. A fault handling method, characterized in that, Applied to an electronic device, the method includes: When the network failure of the electronic device is of the first failure type and the movement speed of the electronic device is the first speed, the electronic device performs a first fault repair action, where the first failure type corresponds to a first fault repair action list, and the first fault repair action includes actions in the first fault repair action list that are not used to trigger network switching; When the network failure of the electronic device is the first failure type and the movement speed of the electronic device is the second speed, the electronic device performs a second fault repair action, where the second fault repair action includes actions in the first fault repair action list that are used to trigger network switching, and the second speed is less than the first speed.

2. The method according to claim 1, wherein When the network failure of the electronic device is the first failure type and the movement speed of the electronic device is the first speed, information for reflecting the network rate is also displayed in the electronic device, and the first fault repair action does not include actions in the first fault repair action list that affect the network rate.

3. The method according to claim 1 or 2, characterized in that, When the network failure of the electronic device is the first failure type and the movement speed of the electronic device is the first speed, the network signal strength accessed by the electronic device is greater than or equal to the strength threshold.

4. The method according to claim 1, wherein When the network failure of the electronic device is the first failure type and the movement speed of the electronic device is the first speed, the electronic device is also in an idle state, and the first fault repair action does not include actions in the first fault repair action list that cannot be executed in the idle state. The idle state is used to indicate that the link between the electronic device and the accessed network device is not established.

5. The method according to any one of claims 1 to 4, characterized in that When the network failure of the electronic device is the first failure type and the movement speed of the electronic device is the first speed, the electronic device is also in a service state, and the service state is used to indicate that the electronic device has successfully camped on the network.

6. The method according to any one of claims 1 to 5, characterized in that The first fault repair action includes a first action and a second action in the first fault repair action list; the first action has a probability of successfully repairing the fault less than a first preset probability or the number of times of repairing the fault is less than a first preset number of times when the movement speed of the electronic device is the first speed; The second action has a probability of successfully repairing the fault greater than or equal to the first preset probability and the number of times of repairing the fault is greater than or equal to the first preset number of times when the movement speed of the electronic device is the first speed; The electronic device performing the first fault repair action includes: The electronic device performs the second action; If after the second action is completed, the network failure of the electronic device is still the first failure type, then the electronic device performs the first action.

7. The method according to claim 6, wherein The third action in the first fault repair action list is not included in the first fault repair action. When the moving speed of the electronic device is the first speed, the number of times the third action successfully repairs the fault is greater than the first preset number, and the probability of successfully repairing the fault is less than the second preset probability, and the second preset probability is less than the first preset probability.

8. The method according to claim 6 or 7, characterized in that, The first fault repair action includes the fourth action in the first fault repair action list. When the moving speed of the electronic device is the first speed, the probability of the fourth action successfully repairing the fault is greater than or equal to the first preset probability, and the number of times of repairing the fault is greater than or equal to the first preset number. The fourth action is a preset action, the second action is not the preset action, and the influence degree of the fourth action is greater than the influence degrees of the first action and the second action. The method further includes: After the first action is executed, if the network fault of the electronic device is still the first fault type, the fourth action is executed.

9. The method according to any one of claims 1 to 8, characterized in that, The time duration between each fault repair action in the first fault repair action and the last execution of each fault repair action is greater than or equal to the first time duration corresponding to each fault repair action. The time duration between each fault repair action in the second fault repair action and the last execution of each fault repair action is greater than or equal to the second time duration corresponding to each fault repair action.

10. The method according to any one of claims 1 to 9, characterized in that, The method includes: When the network fault of the electronic device is the second fault type and the network signal strength accessed by the electronic device is less than the strength threshold, the electronic device does not execute the actions in the second fault repair action list. The second fault type corresponds to the second fault repair list, and the second fault repair list includes actions different from those in the first fault repair list.

11. The method according to any one of claims 1 to 10, characterized in that, The method includes: When the network fault of the electronic device is the third fault type and the electronic device is still in the connected state, the electronic device executes the actions in the third fault repair action list. The third fault type corresponds to the third fault repair list, and the third fault repair list includes actions different from those in the first fault repair list. The connected state is used to indicate that a link is established between the electronic device and the accessed network device.

12. The method according to any one of claims 1 to 11, characterized in that, The method includes: When the network fault of the electronic device is the fourth fault type and the electronic device is still in the no-service state, the electronic device does not execute the actions in the fourth fault repair action list. The fourth fault type corresponds to the fourth fault repair list, and the no-service state is used to indicate that the electronic device fails to camp on the network. The fourth fault repair list includes actions different from those in the first fault repair list.

13. A fault handling method, characterized in that, Applied to an electronic device, the method includes: When the network fault of the electronic device is of the first fault type, obtain a first fault repair action list and a first scenario in which the electronic device is located, where the first scenario is distinguished according to one or more of the following parameters: the movement speed of the electronic device, the network signal strength accessed by the electronic device, the interface content displayed by the electronic device, the link state between the electronic device and the network device accessed, or the network registration state of the electronic device; Screen for a first target fault repair action in the first fault repair action list that conforms to the first scenario; Execute the first target fault repair action.

14. The method according to claim 13, characterized in that, If the first scenario is distinguished according to the movement speed of the electronic device, then screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: If the movement speed of the electronic device meets a preset condition, in the first fault repair action list, delete the action for triggering network switching to obtain the first target fault repair action.

15. The method according to claim 13 or 14, characterized in that, If the first scenario is distinguished according to the interface content displayed by the electronic device, then screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: If the electronic device displays information for reflecting network rate, in the first fault repair action list, delete the actions that affect the network rate to obtain the first target fault repair action.

16. The method according to any one of claims 13 to 15, characterized in that, If the first scenario is distinguished according to the network signal strength accessed by the electronic device, then screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: If the network signal strength accessed by the electronic device is less than or equal to the strength threshold, there is no first target fault repair action in the first fault repair action list.

17. The method according to any one of claims 13 to 16, characterized in that If the first scenario is distinguished according to the link state between the electronic device and the network device accessed, then screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: If the electronic device is in an idle state, in the first fault repair action list, delete the actions that cannot be executed in the idle state to obtain the first target fault repair action, where the idle state is used to indicate that the link between the electronic device and the network device accessed is not established.

18. The method according to any one of claims 13 to 17, characterized in that If the first scenario is distinguished according to the network registration state of the electronic device, then screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: If the electronic device is in a no-service state, there is no first target fault repair action in the first fault repair action list, where the no-service state is used to indicate that the network registration of the electronic device fails.

19. The method according to any one of claims 13 to 18, characterized in that, The first fault repair action list includes a first action and a second action, and the first action is before the second action; Screening for a first target fault repair action in the first fault repair action list that conforms to the first scenario includes: Adjust the second action before the first action to obtain the first target fault repair action; wherein, when the network fault of the electronic device is the first fault type, the probability of successfully repairing the fault of the first action is less than the first preset probability, or the number of times of repairing the fault is less than the first preset number of times; when the network fault of the electronic device is the first fault type, the probability of successfully repairing the fault of the second action is greater than or equal to the first preset probability, and the number of times of repairing the fault is greater than or equal to the first preset number of times.

20. The method according to claim 19, wherein The first target fault repair action does not include the third action in the first fault repair action list. When the network fault of the electronic device is the first fault type, the number of times of successfully repairing the fault of the third action is greater than the first preset number of times, and the probability of successfully repairing the fault is less than the second preset probability, and the second preset probability is less than the first preset probability.

21. The method according to claim 19 or 20, characterized in that, The first fault repair action list further includes a fourth action, and the second action is before the fourth action; If the first target fault repair action further includes the fourth action, then in the first target fault repair action, the second action is before the first action, and the first action is before the fourth action; Wherein, when the network fault of the electronic device is the first fault type, the probability of successfully repairing the fault of the fourth action is greater than or equal to the first preset probability, the number of times of repairing the fault is greater than or equal to the first preset number of times, and the fourth action is a preset action.

22. The method according to any one of claims 13 to 21, characterized in that, The time duration between each fault repair action in the first target fault repair action and the last execution of each fault repair action is greater than or equal to the time duration corresponding to each fault repair action.

23. The method according to any one of claims 13 to 22, characterized in that, The method includes: When the network fault of the electronic device is the second fault type, obtain a second fault repair action list and the second scenario where the electronic device is located, wherein the second scenario is distinguished according to one or more of the following parameters: the movement speed of the electronic device, the network signal strength accessed by the electronic device, the interface content displayed by the electronic device, the link state between the electronic device and the network device accessed, or the network registration state of the electronic device; the second fault repair list includes actions different from those in the first fault repair list; Screen the second target fault repair action that meets the second scenario from the second fault repair action list; Execute the second target fault repair action.

24. An electronic device, characterized in that, The electronic device includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method according to any one of claims 1 to 12, or enable the electronic device to execute the method according to any one of claims 13 to 23.

25. A chip system, characterized in that, The chip system is applied to an electronic device. The chip system includes one or more processors, and the one or more processors are configured to invoke computer instructions to cause the electronic device to execute the method according to any one of claims 1 to 12, or to cause the electronic device to execute the method according to any one of claims 13 to 23.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions, and when the computer instructions run on an electronic device, they cause the electronic device to execute the method according to any one of claims 1 to 12, or to cause the electronic device to execute the method according to any one of claims 13 to 23.

27. A computer program product, characterized in that, The computer program product includes computer program code, and when the computer program code runs on an electronic device, it causes the electronic device to execute the method according to any one of claims 1 to 12, or to cause the electronic device to execute the method according to any one of claims 13 to 23.

Images