Fault processing method and related device

Abstract

The embodiment of the invention provides a fault processing method and a related device, and relates to the technical field of terminals. The method comprises the following steps: under the condition that a network fault of the electronic equipment is of a first fault type, acquiring a first fault repair action list and a first scene in which the electronic equipment is located, the first scene is distinguished according to one or more of the following parameters: the movement speed of the electronic equipment, the signal strength of a network accessed by the electronic equipment, the interface content displayed by the electronic equipment, the link state between the electronic equipment and the accessed network equipment, or the resident network state of the electronic equipment; screening a first target fault repair action conforming to the first scene from the first fault repair action list; and executing the first target fault repair action. In this way, some invalid or unreasonable fault repairing actions can be removed, and the fault duration can be shortened.

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular, to a fault handling method and related device. Background Art

[0002] Currently, when an electronic device uses a cellular network, a phenomenon of a relatively long fault duration is likely to occur. For example, during a game or video playback, a phenomenon of a relatively long freeze may occur. In a call scenario, a phenomenon of continuous call failure may occur. Summary of the Invention

[0003] Embodiments of this application provide a fault handling method and related device, which are applied to the technical field of terminals and are beneficial to shortening the fault duration.

[0004] In a first aspect, embodiments of this application provide a fault handling method, which is applied to an electronic device. The method includes: 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, where 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 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, 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.

[0005] The electronic device may preset one or more fault types, and each fault type may correspond to a fault repair action list, and the fault repair action list may include one or more fault repair actions. The fault repair action may also be referred to as a self-healing action, and embodiments of this application do not make any limitations in this regard. In embodiments of this application, the electronic device may preset the corresponding relationship shown in Table 1.

[0006] When the network fault of the electronic device is a first fault type, a first fault repair action list corresponding to the first fault type may be obtained. The first fault type may be any preset fault type in the electronic device, and embodiments of this application do not make any limitations in this regard.

[0007] There may be invalid or unreasonable fault repair actions in the first fault repair action list, and the invalid or unreasonable fault repair actions may be removed according to different scenarios.

[0008] The moving speed of the electronic device is the first speed, indicating that the electronic device is in a high-speed scenario. If the first fault repair list includes an action to trigger network switching, and the probability of the action to trigger network switching to repair the fault is small, the electronic device may not perform the action to trigger network switching. In this way, the first fault repair action does not include the action to trigger network switching. The moving speed of the electronic device is the second speed, indicating that the electronic device is in a non-high-speed scenario. If the first fault repair list includes an action to trigger network switching, and the probability of the action to trigger network switching to repair the fault is high, the electronic device may perform the action to trigger network switching. In this way, the first fault repair action may include the action to trigger network switching.

[0009] In this way, when the electronic device is in a high-speed scenario, not performing the ineffective or unreasonable fault repair actions in the first fault repair action list is beneficial to shortening the fault duration.

[0010] In a possible implementation manner, when the network fault of the electronic device is the first fault type and the moving 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 the actions in the first fault repair action list that affect the network rate.

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

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

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

[0014] In this way, when the electronic device is in a high-speed scenario and in a rate-sensitive scenario, not performing the actions that affect the network rate is beneficial to shortening the fault duration.

[0015] In a possible implementation manner, when the network fault of the electronic device is the first fault type and the moving 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.

[0016] When the network signal strength accessed by the electronic device is greater than or equal to the strength threshold, it indicates that the network signal is good, which is a non-weak field handover and is conducive to the implementation of various fault repair actions. The electronic device executes the actions in the first fault repair list, which is conducive to increasing the probability of fault repair and shortening the fault duration.

[0017] In a possible implementation, when the network fault of the electronic device is the first fault type and the movement speed of the electronic device is the first speed, the electronic device is still in the idle state, and the first fault repair actions do not include the 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 has not been established.

[0018] If there are actions in the first fault action repair list that cannot be executed in the idle state, and at this time, the electronic device is in the idle state, then the actions that cannot be executed in the idle state can be not executed. In this way, the first fault repair actions do not include the actions in the first fault repair action list that cannot be executed in the idle state, which is conducive to increasing the probability of fault repair and shortening the fault duration.

[0019] In a possible implementation, when the network fault of the electronic device is the first fault type and the movement speed of the electronic device is the first speed, the electronic device is still in the service state. The service state is used to indicate that the electronic device has successfully camped on the network.

[0020] The electronic device being in the service state indicates that the electronic device has successfully camped on the network, which is conducive to the implementation of various fault repair actions. The electronic device executes the actions in the first fault repair list, which is conducive to increasing the probability of fault repair and shortening the fault duration.

[0021] In a possible implementation, the first fault repair actions include the first action and the second action in the first fault repair action list; 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 movement speed of the electronic device is the first speed; 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 when the movement speed of the electronic device is the first speed; the electronic device executing the first fault repair actions includes: the electronic device executes the second action; if after executing the second action, the network fault of the electronic device is still the first fault type, then the electronic device executes the first action.

[0022] According to the prior information, the probabilities of successfully repairing the fault and the number of times of repairing the fault of the first action and the second action can be obtained. If the success rate of the second action in repairing the fault is greater than that of the first action, the execution order of the second action is before the first action.

[0023] In this way, it is beneficial to improve the success rate of fault repair and shorten the fault duration.

[0024] In a possible implementation, the third action in the first fault repair action list is not included in the first fault repair action. When the movement 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, where the second preset probability is less than the first preset probability.

[0025] According to the prior information, the success rate of the third action in repairing the fault is relatively low, and the electronic device may not execute it. In this way, it is beneficial to improve the success rate of fault repair and shorten the fault duration.

[0026] In a possible implementation, the first fault repair action includes the fourth action in the first fault repair action list. When the movement 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 a preset action, and the influence degree of the fourth action is greater than that 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, then execute the fourth action.

[0027] The fourth action being a preset action indicates that although the success rate of repairing the fault is relatively high, the influence degree of the fourth action is relatively large, so it cannot be executed first. The second action not being a preset action indicates that the second action can be executed first when the success rate is relatively high. Therefore, the second action is before the first action, and the fourth action is after the first action.

[0028] In this way, it is possible to reduce the influence degree on the user and the device while shortening the fault duration.

[0029] In a possible implementation, the time interval 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 interval corresponding to each fault repair action; the time interval 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 interval corresponding to each fault repair action.

[0030] Each fault repair action corresponds to a time interval, which can be called the protection time. Within this time interval, the fault repair action cannot be executed repeatedly to avoid repeated state switching and affecting the success rate of fault repair.

[0031] In a possible implementation, the method includes: when the network failure of the electronic device is of the second failure 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 failure repair action list. The second failure type corresponds to the second failure repair list, and the second failure repair list includes actions different from those in the first failure repair list.

[0032] The second failure type is different from the first failure type. The fact that the network signal strength accessed by the electronic device is less than the strength threshold indicates that the electronic device is in a weak field environment with poor network signals, which is not conducive to the execution of failure repair actions. The electronic device may not execute the failure repair actions. When the network failure of the electronic device is of the second failure type and the second failure type corresponds to the second failure repair list, the electronic device may not execute the actions in the second failure repair action list.

[0033] In an environment with poor network signals, when executing failure repair actions, the probability of successfully repairing the failure by the failure repair actions is relatively 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 executing the failure repair actions is beneficial to shortening the failure duration.

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

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

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

[0037] When the electronic device is in a no-service state, it indicates that the electronic device fails to camp on the network. At this time, it is not conducive to the execution of fault repair actions. The network fault of the electronic device is the fourth fault type, and the fourth fault type corresponds to the fourth fault repair list. The electronic device can not execute the actions in the fourth fault repair action list, which helps to shorten the fault duration.

[0038] In a second aspect, an embodiment of the present application provides a fault handling method applied to an electronic device. The method includes: when the network fault of the electronic device is the first fault type, obtaining a first fault repair action list and a first scenario where the electronic device is located, where 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 accessed by the electronic device, the interface content displayed by the electronic device, the link state between the electronic device and the accessed network device, or the network camping state of the electronic device; screening the first target fault repair actions that meet the first scenario from the first fault repair action list; and executing the first target fault repair actions.

[0039] The movement speed of the electronic device is used to distinguish whether it is a high-speed scenario, the network signal strength accessed by the electronic device 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 state between the electronic device and the accessed network device is used to distinguish whether it is in an idle state or a connected state, and the network camping state of the electronic device is used to distinguish whether it is in a no-service or a service state.

[0040] In the embodiment of the present application, the method can refer to Figure 4 , and these scenarios can refer to user scenarios and link information.

[0041] Different fault repair actions can be applicable to different scenarios. When the network fault of the electronic device is the first fault type, screening the first target fault repair actions that meet the first scenario from the first fault repair action list; and executing the first target fault repair actions can avoid executing unreasonable or ineffective fault repair actions, which helps to shorten the fault duration.

[0042] In a possible implementation manner, if the first scenario is distinguished based on the movement speed of the electronic device, screening the first target fault repair actions that meet the first scenario from the first fault repair action list includes: if the movement speed of the electronic device meets a preset condition, deleting the actions for triggering network switching in the first fault repair action list to obtain the first target fault repair actions.

[0043] The method can refer to Figure 5 S508 and S509 in. In this way, unreasonable or ineffective fault repair actions can be avoided, which helps to shorten the fault duration.

[0044] In a possible implementation, if the first scenario is distinguished according to the interface content displayed on the electronic device, screening the first target fault repair actions that meet the first scenario in the first fault repair action list includes: if the electronic device displays information reflecting the network rate, then in the first fault repair action list, delete the actions that affect the network rate to obtain the first target fault repair actions.

[0045] This method can refer to Figure 5 S506 and S507 in [reference document]. In this way, unreasonable or ineffective fault repair actions can be avoided, which helps to shorten the fault duration.

[0046] In a possible implementation, if the first scenario is distinguished according to the network signal strength accessed by the electronic device, screening the first target fault repair actions that meet the first scenario in the first fault repair action list includes: if the network signal strength accessed by the electronic device is less than or equal to the strength threshold, there are no first target fault repair actions in the first fault repair action list. This method can refer to Figure 5 S504 and S505 in [reference document].

[0047] In a possible implementation, if the first scenario is distinguished according to the link state between the electronic device and the accessed network device, screening the first target fault repair actions that meet the first scenario in the first fault repair action list includes: if the electronic device is in the 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 actions. The idle state is used to indicate that the link between the electronic device and the accessed network device is not established. This method can refer to Figure 7 S705 and S706 in [reference document]. The actions executed in the connected state are used to indicate the actions that cannot be executed in the idle state.

[0048] In a possible implementation, if the first scenario is distinguished according to the network registration state of the electronic device, screening the first target fault repair actions that meet the first scenario in the first fault repair action list includes: if the electronic device is in the no-service state, there are no first target fault repair actions in the first fault repair action list. The no-service state is used to indicate that the electronic device fails to register on the network. This method can refer to Figure 7 S703 and S704 in [reference document].

[0049] In a 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 actions that meet the first scenario from the first fault repair action list includes: adjusting the second action to be before the first action to obtain the first target fault repair actions; where the probability of successfully repairing the fault when the network fault of the electronic device is of the first fault type for 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; the probability of successfully repairing the fault when the network fault of the electronic device is of the first fault type for 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. This method can refer to Figure 6 S602 and S603 in

[0050] In a possible implementation, the first target fault repair actions do not include a third action in the first fault repair action list. When the network fault of the electronic device is of the first fault type, the number of times of successfully repairing the fault for 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, where the second preset probability is less than the first preset probability. This method can refer to Figure 6 S604 and S605 in

[0051] In a possible implementation, the first fault repair action list further includes a fourth action, with the second action preceding the fourth action; if the first target fault repair actions further include the fourth action, then in the first target fault repair actions, the second action is before the first action, and the first action is before the fourth action; where the probability of successfully repairing the fault when the network fault of the electronic device is of the first fault type for 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.

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

[0053] In a possible implementation, the method includes: when the network failure of the electronic device is of the second failure type, obtaining a second fault repair action list and a second scenario in which the electronic device is located, where the second scenario is differentiated 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; screening a second target fault repair action that conforms to the second scenario from the second fault repair action list; and executing the second target fault repair action.

[0054] Different fault types can correspond to different fault repair lists, which is beneficial to targeted repair for different fault types, improving the probability of fault repair and shortening the fault duration.

[0055] In a third aspect, an embodiment of the present application provides a fault repair device, which may be an electronic device, or a chip or a chip system within the 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 further 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 enable 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 a chip system within the electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to enable 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., register, cache, etc.), or a storage unit outside the chip within the electronic device (e.g., read-only memory, random access memory, etc.).

[0056] In a possible implementation, a processing unit is configured to perform a first fault repair action when the network fault of the fault handling device is of a first fault type and the moving speed of the fault handling device is a first speed. 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 fault handling device is of the first fault type and the moving speed of the fault handling device is a second speed, perform 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.

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

[0058] In a possible implementation, when the network fault of the fault handling device is of the first fault type and the moving speed of the fault handling device is the first speed, the network signal strength accessed by the fault handling device is greater than or equal to the strength threshold.

[0059] In a possible implementation, when the network fault of the fault handling device is of the first fault type and the moving speed of the fault handling device is the first speed, the fault handling device is also in an idle state. 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 fault handling device and the accessed network device is not established.

[0060] In a possible implementation, when the network fault of the fault handling device is of the first fault type and the moving speed of the fault handling device is the first speed, the fault handling device is also in a service state. The service state is used to indicate that the fault handling device has successfully camped on the network.

[0061] In a possible implementation, the first fault repair action includes a first action and a second action in the first fault repair action list; 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 moving speed of the fault handling device is the first speed; 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 when the moving speed of the fault handling device is the first speed; the processing unit is further configured to: execute the second action; if the network fault of the fault handling device is still the first fault type after the execution of the second action is completed, execute the first action.

[0062] In a possible implementation, there is no third action in the first fault repair action list in the first fault repair action. 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 when the moving speed of the fault handling device is the first speed, and the second preset probability is less than the first preset probability.

[0063] In a possible implementation, the first fault repair action includes a fourth action in the first fault repair action list. The probability of successfully repairing the fault of the fourth 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 when the moving speed of the fault handling device is the first speed. The fourth action is a preset action, the second action is not a 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 processing unit is further configured to: if the network fault of the fault handling device is still the first fault type after the execution of the first action is completed, execute the fourth action.

[0064] In a possible implementation, the time duration between each execution of each fault repair action in the first fault repair action is greater than or equal to the first time duration corresponding to each fault repair action; the time duration between each execution of each fault repair action in the second fault repair action is greater than or equal to the second time duration corresponding to each fault repair action.

[0065] In a possible implementation, the processing unit is further configured to: when the network fault of the fault handling device is the second fault type and the network signal strength accessed by the fault handling device is less than the strength threshold, do 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.

[0066] In a possible implementation, the processing unit is further configured to: when the network fault of the fault handling device is of a third fault type and the fault handling device is still in a connected state, execute the actions in the third fault repair action list, where the third fault type corresponds to a third fault repair list, and 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 network device it accesses.

[0067] In a possible implementation, the processing unit is further configured to: when the network fault of the fault handling device is of a fourth fault type and the fault handling device is still in a no-service state, not execute the actions in the fourth fault repair action list, where the fourth fault type corresponds to a fourth fault repair list, and the no-service state is used to indicate that the fault handling device fails to camp on the network, and the fourth fault repair list includes actions different from those in the first fault repair list.

[0068] In another possible implementation, the processing unit is configured to: when the network fault of the fault repair device is of a first fault type, obtain a first fault repair action list and a first scenario in which the fault repair device is located, where 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 accessed by the fault repair device, the interface content displayed by the fault repair device, the link state between the fault repair device and the network device it accesses, or the network camping state of the fault repair device; screen a first target fault repair action that conforms to the first scenario from the first fault repair action list; and execute the first target fault repair action.

[0069] In a possible implementation, if the first scenario is distinguished based on the movement speed of the fault repair device, the processing unit is specifically configured to: if the movement speed of the fault repair device meets a preset condition, delete the action for triggering network switching in the first fault repair action list to obtain the first target fault repair action.

[0070] In a possible implementation, if the first scenario is distinguished based on the interface content displayed by the fault repair device, the processing unit is specifically configured to: if the fault repair device displays information for reflecting the network rate, delete the actions that affect the network rate in the first fault repair action list to obtain the first target fault repair action.

[0071] In a possible implementation, if the first scenario is distinguished based on the network signal strength accessed by the fault repair device, the processing unit is specifically configured to: if the network signal strength accessed by the fault repair 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.

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

[0073] In a possible implementation, if the first scenario is distinguished based on the network resident state of the fault repair device, the processing unit is specifically configured to: if the fault repair 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 fault repair device fails to reside in the network.

[0074] In a 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 configured to: adjust the second action before the first action to obtain the first target fault repair action; where, when the network fault of the fault repair device is of the first fault type, the probability of successfully repairing the fault for 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 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 of repairing the fault is greater than or equal to the first preset number of times.

[0075] In a possible implementation, the first target fault repair action does not include a 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 times of successfully repairing the fault for 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, where the second preset probability is less than the first preset probability.

[0076] In a possible implementation, the first fault repair action list further includes a fourth action, and the second action is before the fourth action; 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; where, when the network fault of the fault repair device is of the first fault type, the probability of successfully repairing the fault for 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.

[0077] In a possible implementation, 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.

[0078] In a possible implementation, the processing unit is further configured 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, where the second scenario is distinguished according to one or more of the following parameters: the moving speed of the fault repair device, the network signal strength accessed by the fault repair device, the content of the interface displayed by the fault repair device, the link state between the fault repair device and the network device it accesses, or the network resident state of the fault repair device; the second fault repair list includes actions different from those in the first fault repair list; screen a second target fault repair action that conforms to the second scenario from the second fault repair action list; and execute the second target fault repair action.

[0079] Fourthly, an embodiment of the present application provides an electronic device, including one or more processors and a memory; the memory is coupled to the one or more processors, and 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 methods described in any aspect or any possible implementation manner of any aspect.

[0080] Fifthly, an embodiment of the present application provides a computer-readable storage medium, in which computer programs or instructions are stored. When the computer programs or instructions run on an electronic device, the electronic device is enabled to execute the methods described in any aspect or any possible implementation manner of any aspect.

[0081] Sixthly, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on an electronic device, the electronic device is enabled to execute the methods described in any aspect or any possible implementation manner of any aspect.

[0082] Seventhly, an embodiment of the present application provides a chip or a chip system. The chip or the chip system is applied to an electronic device, and the chip or the chip system includes at least one or more processors, and the one or more processors are used to call computer instructions to execute the methods described in any aspect or any possible implementation manner of any aspect.

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

[0084] 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 obtained by each aspect and the corresponding feasible implementation manners are similar, so they will not be elaborated herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 is a schematic flowchart of a multi-level self-healing process of an electronic device;

[0086] Figure 2 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application;

[0087] Figure 3 is a schematic diagram of the software architecture of an electronic device provided by an embodiment of the present application;

[0088] Figure 4 is a schematic flowchart of a fault handling method provided by an embodiment of the present application;

[0089] Figure 5 is a schematic flowchart of another fault handling method provided by an embodiment of the present application;

[0090] Figure 6 is a schematic flowchart of yet another fault handling method provided by an embodiment of the present application;

[0091] Figure 7 is a schematic flowchart of another fault handling method provided by an embodiment of the present application;

[0092] Figure 8 is a schematic block diagram of a chip provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0093] To facilitate a clear description of the technical solutions of the embodiments of the present application, the following briefly introduces some terms and technologies involved in the embodiments of the present application:

[0094] 1. Cell handover

[0095] Cell handover may refer to the process of migrating the communication link between an electronic device and the current network device to another network device.

[0096] The current location of the electronic device can be covered by multiple cells simultaneously. When the electronic device needs to perform wireless communication, it can select one of the multiple cells to camp on to achieve access to a cellular network (such as a Long-Term Evolution (LTE) network or a New Radio (NR) network). When a fault occurs in the cellular network used by the electronic device in the camped cell, the electronic device can switch from the camped cell to other cells to obtain better signal quality and faster network speed, which is beneficial to fault repair.

[0097] In some examples, switching cells can be achieved by adding a black cell or specifying a registered cell. Switching cells can also be referred to as a bar cell or a black cell, and the embodiments of this application do not limit this.

[0098] 2. Suppressing Standalone (SA)

[0099] Suppressing SA can also be referred to as turning off SA, downgrading to New Radio (NR), or switching domains, and the embodiments of this application do not limit this.

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

[0101] In this way, when a fault occurs in the electronic device due to using the 5G network, the electronic device can repair the fault by suppressing SA.

[0102] It can be understood that the embodiments of this application use suppressing SA to indicate replacing the mobile communication technology. For example, replacing from the sixth-generation mobile communication technology (6G) to 5G, from 5G to 4G, etc. The embodiments of this application do not limit the name.

[0103] 3. Re-registration

[0104] Re-registration, which can also be called re - enrollment, can be used to represent the process of an electronic device re - registering on a network device to enable communication with the network device. Re - registration usually occurs when the communication between the electronic device and the network device is interrupted or unstable. By re - registering, the electronic device can re - establish a connection with the network device and regain access to the network device.

[0105] For example, when the electronic device experiences a cellular network failure due to an interruption or instability in the communication between the electronic device and the network device, the electronic device can repair the failure through re - registration.

[0106] 4. Switch the data switch

[0107] The data switch is used to indicate that after closing the data switch, the data switch is then opened. Among them, closing the data switch means that the ability of the electronic device to use the cellular data network is turned off. Opening the data switch means that the ability of the electronic device to use the cellular data network is turned on. Among them, the cellular data network is used to represent the implementation of data services using the cellular network.

[0108] 5. Restart the radio function (restart radio)

[0109] Restarting the radio function can be used to represent that the electronic device re - enables its communication function to restore the normal operating state of the electronic device. When the radio device is used for a long time or encounters a fault, it may experience abnormal operation or unstable connection. At this time, restarting the radio device can clear possible software or hardware faults, re - initialize device parameters, and make it return to the normal operating state.

[0110] Restarting the radio function can include turning off the radio device, waiting for a period of time (such as 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 called switching the flight mode.

[0111] For example, when the electronic device experiences cellular network lag due to long - term use or a fault in the radio device, the electronic device can repair the lag by turning on the flight mode, waiting for a few seconds, and then turning off the flight mode to achieve the restart of the radio function.

[0112] 6. Restart the modem

[0113] Restarting the modem can mean turning off the modem, waiting for a period of time, and then turning it on again. The electronic device includes a modem, and the modem can provide cellular communication capabilities for the electronic device. When the electronic device experiences a fault in using the cellular network, the electronic device can recover from the fault by restarting the modem.

[0114] 7. Network attachment

[0115] Network attachment means that an electronic device is connected to the network equipment of an operator through a network.

[0116] 8. Other terms

[0117] In the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. For example, the first failure type and the second failure type are only used to distinguish different failure types, and do not limit their sequence. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different.

[0118] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.

[0119] In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (s) or multiple items (s). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0120] 9. Electronic device

[0121] The electronic devices in the embodiments of the present application may include handheld devices with cellular communication functions, vehicle-mounted devices, etc. For example, some electronic devices are: mobile phones, tablet computers, handheld computers, 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, wireless terminals in remote medical surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminal devices in a 5G network, or terminal devices in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0122] In addition, in the embodiments of the present application, the electronic device may also be a terminal device in an internet of things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect items to the network through communication technology, so as to realize an intelligent network of human-machine interconnection and thing-thing interconnection.

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

[0124] 10. Network device

[0125] 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 can provide an access function for the electronic device and is 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 the gNB in the NR system, or one or a group (including multiple antenna panels) of antenna panels of a base station in 5G, or may also be a network node constituting the gNB, transmission and reception point (TRP) or transmission point (TP), or transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or a distributed unit (DU), an RSU with base station functions, or a wired access gateway, or a core network element of 5G. 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 called small stations), relay stations, access points, wearable devices, in-vehicle devices, and so on. Alternatively, the RAN device may also include an access network device of a next-generation mobile communication system, such as a 6G base station, or in the next-generation mobile communication system, the network device may have other naming methods, all of which are covered by the protection scope of the embodiments of this application, and this application makes no limitation thereto.

[0126] Currently, when an electronic device uses a cellular network, a phenomenon of a relatively long fault duration is likely to occur. For example, during a game or video playback, there may be a phenomenon of a relatively long freezing time. In a call scenario, there may be a phenomenon that the call always fails.

[0127] The electronic device is preset with a series of self-healing actions to be executed when a fault occurs. When the electronic device has a fault while using the cellular network, the electronic device can recover the fault through this series of self-healing actions. Among them, this series of actions is triggered step by step according to the impact degree of the self-healing actions. The impact degree is used to represent the impact degree on the user and / or the fault recovery ability. The self-healing actions may include switching cells, suppressing SA, re-registering, turning on / off the data switch, restarting the radio function, or restarting one or more of the modems.

[0128] Exemplarily, Figure 1 a schematic flowchart showing a multi-level self-healing process of an electronic device is illustrated. As Figure 1 shown, the method may include the following steps:

[0129] S101. When a failure occurs in the electronic device using the cellular network, read the default self-healing actions.

[0130] The default self-healing actions may include one or more self-healing actions, which are not limited in the embodiments of the present application. When the default self-healing actions include multiple self-healing actions, there is a preset sorting for these multiple self-healing actions, and the sorting is based on the impact degree of the self-healing actions.

[0131] S102. The electronic device may execute the self-healing actions.

[0132] If the default self-healing actions include one self-healing action, the electronic device may execute this self-healing action. If the default self-healing actions include multiple self-healing actions and there is a preset sorting for these multiple self-healing actions, the electronic device may execute the first self-healing action among the multiple self-healing actions according to the preset sorting, and the first self-healing action is the self-healing action with the least impact degree among these multiple self-healing actions.

[0133] S103. After executing the self-healing actions, the electronic device starts to evaluate.

[0134] After the electronic device executes this self-healing action, evaluate whether there is still a failure.

[0135] S104. The electronic device determines whether the self-healing is successful.

[0136] If the electronic device still has a failure, it means that the self-healing is not successful, and the electronic device may determine whether to execute the next-level self-healing action, that is, execute S106.

[0137] If the electronic device has no failure, it means that the self-healing is successful, and the electronic device may return the self-healing success, that is, execute S105.

[0138] S105. If the self-healing is successful, the electronic device returns the self-healing success.

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

[0140] In one example, if the self-healing is successful, the electronic device may output SUCCESS, and use SUCCESS to represent the self-healing success.

[0141] S106. If the self-healing is not successful, the electronic device determines whether to execute the next-level self-healing action.

[0142] Determine whether to execute the next-level self-healing action, which is used to indicate whether there are other self-healing actions.

[0143] If the default self-healing action includes one self-healing action, it means that there are no other self-healing actions to execute, and the electronic device may not execute the next-level self-healing action. If the default self-healing action includes multiple self-healing actions, it means that there are other self-healing actions to execute, and the electronic device may execute the second self-healing action among the multiple self-healing actions. The second self-healing action can be called the next-level action of the first self-healing action. The impact degree of the second self-healing action is greater than that of the first self-healing action, but smaller than that of the other self-healing actions among the multiple self-healing actions.

[0144] S107. If the next-level self-healing action is not executed, the electronic device returns that the self-healing is unsuccessful.

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

[0146] In one example, if the next-level self-healing action is not executed, the electronic device can output FALL or reject to indicate that the self-healing is unsuccessful through FALL or reject.

[0147] S108. If the next-level self-healing action is executed, the electronic device executes the next-level self-healing action.

[0148] If the next-level self-healing action is executed, after the electronic device executes this self-healing action, it evaluates whether there is still a fault, that is, executes the above S103.

[0149] For better understanding Figure 1 the method shown below, a specific example will be used for illustration.

[0150] Exemplarily, when a fault occurs when the electronic device uses the cellular network, the executable self-healing process includes: 1) Suppress SA; 2) Switch the data switch; 3) Restart the radio function; 4) Restart the modem.

[0151] That is to say, when a fault occurs in the electronic device, it first suppresses SA; after suppressing SA, if there is still a data fault, it switches the data switch; after switching the data switch, if there is still a fault, it restarts the radio function; after restarting the radio function, if there is still a fault, it restarts the modem.

[0152] In this implementation method, the phenomenon of a long fault duration occurs because the default self-healing action may have some unreasonable or ineffective self-healing actions, resulting in the inability to repair the fault in time, causing the phenomenon of a long fault duration. In addition, the default self-healing action is fixed and will not be adjusted according to the actual situation, so the flexibility is poor.

[0153] In view of this, an embodiment of the present application provides a fault handling method and related device, which determine corresponding self-healing actions based on the fault type, and can adjust the execution order of these self-healing actions, or can delete ineffective self-healing actions, which is beneficial to improving the success probability of self-healing actions, and further beneficial to reducing the probability of a long fault duration.

[0154] The method provided by the embodiment of the present application can be executed by an electronic device. For ease of understanding, the hardware structure of the electronic device provided by the embodiment of the present application will be introduced first.

[0155] Exemplarily, Figure 2 shows a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. As Figure 2 shown, 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, a headphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0156] Optionally, the above sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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.

[0157] It can be understood that the structure schematically shown in the embodiment of the present application does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0158] 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), etc. Among them, different processing units can be independent devices or integrated in one or more processors. Among them, the modem can provide cellular communication capabilities, and electronic devices can use the modem to implement a series of cellular communication functions such as sending and receiving text messages, 5G-related functions, making calls, and answering calls.

[0159] The SIM card interface 195 is used to insert a SIM card. The SIM card described in the embodiment of the present application can be understood as a module for providing user information in a cellular network or using a mobile cellular network. For example, a terminal device with a SIM card slot and a card reader can register 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 embodiment of the present application.

[0160] When the electronic device is deployed with a SIM card, the processor 110 can use the SIM card to station on the network, and after the stationing is successful, the cellular network can be used. In the case of a failure in the use of the cellular network, the processor 110 can obtain the corresponding self-healing action based on the fault type, and can adjust the execution order of these self-healing actions, or can delete invalid self-healing actions to obtain the self-healing action to be executed, and then execute the corresponding self-healing action to repair the fault.

[0161] The software system of the electronic device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The layered architecture can adopt an Android system, an Apple (IOS) system, or other operating systems, which are not limited in the embodiments of the present application. The following takes the Android system of the layered architecture as an example to exemplify the software architecture of the electronic device provided in the embodiments of the present application.

[0162] Figure 3 A schematic diagram of a software architecture of an electronic device provided in an embodiment of the present application is shown. Figure 3As shown, the layered architecture divides the software architecture of the electronic device into several layers, each layer having 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, which are, from top to bottom, the applications layer, the application framework layer, the hardware abstraction layer (HAL), the kernel layer, and the modem.

[0163] The applications layer may include a series of application packages. The applications layer runs the applications by calling the application programming interfaces (APIs) provided by the application framework layer. As Figure 3 shown, the application packages may include applications such as browsers, phones, games, and videos.

[0164] The application framework layer provides APIs and programming frameworks for the applications in the applications layer. The application framework layer includes some predefined functions. As Figure 3 shown, 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 fault type when the electronic device has a fault using the cellular network, determine the list of self-healing actions 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.

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

[0166] After executing this self-healing action, if there is still a fault, the fault type is the same as the fault type before executing this self-healing action, and this self-healing action has no next-level self-healing action, then end.

[0167] After executing this self-healing action, if there is still a fault and the fault type is different from the fault type before executing this self-healing action, then determine the list of self-healing actions corresponding to this fault type based on the current fault type, and repeat the above steps.

[0168] It should be noted that the fault handling module being in the application framework layer is just an example. The fault handling module can also be in other layers or other chips, and the embodiments of the present application do not limit this.

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

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

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

[0172] It should be understood that in some embodiments, the layer that implements the same function can be called by other names, or the layer that can implement the functions of multiple layers can be regarded as one layer, or the layer that can implement the functions of multiple layers can be divided into multiple layers. The embodiments of the present application do not limit this.

[0173] Above, in combination with Figure 2 and Figure 3 , the software and hardware structures of the electronic device in the embodiments of the present application are introduced. Next, the method applied to the electronic device is introduced.

[0174] Exemplarily, Figure 4 shows a schematic flowchart of a fault handling method provided by the embodiments of the present application. As Figure 4 shown, the method 400 may include the following steps:

[0175] S401. When a fault occurs in the electronic device using the cellular network, read the default self-healing action based on the fault type.

[0176] The electronic device presets the correspondence between the fault type and the self-healing action. 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 can include one or more self-healing actions, and the embodiments of the present application do not limit this. When the default self-healing action includes multiple self-healing actions, there is a preset sorting for these multiple self-healing actions, and the sorting is based on the impact degree of the self-healing actions.

[0177] Exemplarily, Table 1 shows a schematic diagram of the correspondence between a fault type and a self-healing action.

[0178] Table 1

[0179] Fault type Self-healing action Abnormal call signaling Switch cell, suppress SA Data lag Switch cell, suppress SA, re-register, restart radio function Weak signal Suppress SA Data activation failure Suppress SA, re-register, restart radio function

[0180] As shown in Table 1, the fault types may include abnormal call signaling, data lag, weak signal, and data activation failure. Among them, in the following scenarios, the electronic device can determine that the fault type is abnormal call signaling: when the electronic device responds to a call demand and sends a request message to the network device, and the network device rejects the request message for some reason, resulting in a call failure. When the fault type is abnormal call signaling, the self-healing actions that the electronic device can perform may include switching cells and suppressing SA.

[0181] When the electronic device experiences lag during the execution of cellular data services, it can be determined that the fault type is data lag. Among them, the electronic device's execution of cellular data services can be understood as the electronic device using the cellular network to open web pages, play videos or music, or download application programs, etc. When the fault type is data lag, the self-healing actions that the electronic device can perform may include switching cells, suppressing SA, re-registering, and restarting the radio function.

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

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

[0184] In the example shown in Table 1, when the electronic device has a fault using the cellular network, it determines the fault type and obtains the default self-healing actions based on the fault type and the corresponding relationship shown in Table 1. The default self-healing actions can also be referred to as the default self-healing action list or the self-healing action list. The embodiments of the present application do not make any limitations in this regard.

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

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

[0187] 1) User scenario

[0188] The user scenario is used to represent the environment where the electronic device is located or the state of the electronic device. In the embodiments 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] Among them, the weak field environment is used to indicate that the network signal at the location where the electronic device is located is poor, and the network signal may be a 5G signal or a 4G signal, etc. In a weak field environment, the failure of the electronic device is caused by the environment. The probability that the self-healing actions performed by the electronic device repair the failure is small, and some self-healing actions will also cause slow Internet access when the electronic device is in a non-weak field environment, resulting in an increase in negative benefits. Therefore, when the electronic device is in a weak field environment, all self-healing actions are intercepted, that is, the default self-healing actions are all deleted.

[0190] The rate-sensitive scenario is used to indicate that the applications running on the electronic device include applications that reflect the running rate. Applications that reflect the running rate include applications for testing the running rate of the electronic device and applications for displaying the running rate, etc. For example, an application for testing the configuration and performance of the electronic device can test the running rate of the electronic device. An application for downloading application programs can display the download rate. In a rate-sensitive scenario, some of the default self-healing actions may include self-healing actions that affect the rate. In order to reduce the impact on the running rate, the electronic device can delete the self-healing actions that affect the rate in the default self-healing actions.

[0191] Exemplarily, when the electronic device fails to use the cellular network and the electronic device is in the process of downloading a game application and the download rate is displayed, if suppressing SA is included in the default self-healing actions and the device switches from 5G to 4G, the download rate may be reduced, and the electronic device displays the reduced download rate, which will affect the user experience. In this scenario, the electronic device can delete the suppressing SA in the default self-healing actions.

[0192] The high-speed scenario is used to indicate that the position of the electronic device is in a relatively fast moving state. For example, the electronic device is on a high-speed train or in a car. In a high-speed scenario, the network fluctuates violently, and some self-healing actions have no benefits and become ineffective self-healing actions. The electronic device can delete the ineffective self-healing actions in the default self-healing actions.

[0193] For example, switching cells causes the cell where the electronic device is located to change due to the movement of the electronic device, resulting in no benefit from the self-healing action. Suppressing SA results in no 4G signal at the location where the electronic device is located due to the movement of the electronic device, resulting in no benefit from the self-healing action. Therefore, if switching cells or suppressing SA is included in the default self-healing actions, the electronic device can delete switching cells or suppressing SA.

[0194] 2) Prior information

[0195] The prior information is used to represent the historical execution situation of the self-healing actions. For example, the cell where the electronic device is located when the self-healing action is executed, the operating state of the electronic device when the self-healing action is executed, whether the self-healing action is successfully self-healed, the influence degree of the self-healing action, and the previous execution time, etc.

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

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

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

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

[0200] Each self-healing action is set with a protection time. After the self-healing action is executed, the self-healing action cannot be executed again within the corresponding protection time. For example, the inhibition of SA is set with a 5-minute protection time. Re-registration is set with a 15-minute protection time. Restarting the radio function is set with a 30-minute protection time.

[0201] The protection time can be fixed or adjustable. The embodiments of the present application do not make any limitations in this regard. If the protection time is adjustable, the protection time can change according to the change of the environment where the electronic device is located, so that the flexibility is stronger.

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

[0203] It can be understood that when each self-healing action is executed, the electronic device can start a timer, record the cell where the electronic device is located and the operating state of the electronic device, and can count the success rate of the self-healing action according to whether the self-healing action is successfully self-healed.

[0204] 3) Link information

[0205] Link information is used to represent the link state between an electronic device and a network device. For example, the link information may include no service, current service status, the cell where the device is located being in the idle state, the cell where the device is located being in the connected state, and network conditions, etc. Among them, no service is used to indicate that the electronic device fails to camp on the network. The current service status is used to indicate that the electronic device has successfully camped on the network. The cell being in the idle state is used to indicate that the communication link between the electronic device and the network device has not been successfully established. The cell where the device is located being in the connected state is used to indicate that the communication link between the electronic device and the network device has been successfully established. Network conditions are used to indicate the network signal type of the cell where the electronic device is located.

[0206] Based on the link information, the electronic device can determine the connection state between the electronic device and the network device, and can delete the ineffective self-healing actions included in some default actions.

[0207] Exemplarily, when a fault occurs in the electronic device using the cellular network and the cell where the electronic device is located is in the idle state, and cell switching only supports being executed in the connected state, so in the case where cell switching is included in the default self-healing actions, the electronic device can delete the cell switching in the default self-healing actions.

[0208] Exemplarily, when the electronic device has no service, self-healing actions such as cell switching, suppressing SA, and re-registration cannot take effect, so the electronic device can intercept self-healing actions such as cell switching, suppressing SA, and re-registration in the default self-healing actions.

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

[0210] S403. The electronic device can execute self-healing actions.

[0211] If the updated self-healing actions include one self-healing action, the electronic device can execute this self-healing action. If the updated self-healing actions include multiple self-healing actions and there is an order among these multiple self-healing actions, the electronic device can execute the first self-healing action among the multiple self-healing actions.

[0212] S404. After executing the self-healing actions, the electronic device starts to evaluate.

[0213] After the electronic device executes this self-healing action, it evaluates whether there is still a fault.

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

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

[0216] If the electronic device has no fault, it indicates that self-healing is successful. The electronic device can return that self-healing is successful, that is, execute S406.

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

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

[0219] S408: If the next-level self-healing action is not performed, the electronic device returns that self-healing is unsuccessful.

[0220] S409: If the next-level self-healing action is performed, the electronic device performs the next-level self-healing action.

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

[0222] In the fault handling method provided by the embodiments of the present application, for different fault types, the default self-healing actions included in the self-healing actions are different. Using the corresponding self-healing actions for different faults is beneficial to increasing the probability of successful self-healing and thus beneficial to shortening the fault duration. In addition, based on one or more of user scenarios, prior information, and link information, screening the self-healing actions to delete unreasonable or ineffective self-healing actions and adjusting the execution order of the self-healing actions is beneficial to increasing the probability of successful self-healing and thus beneficial to shortening the duration of repairing the fault.

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

[0224] In different scenarios, the screening rules of the electronic device are different. Exemplarily, Table II shows a correspondence between a user scenario and a screening rule. Among them, the screening rule can also be referred to as self-healing action management, which is not limited in the embodiments of the present application.

[0225] Table II

[0226] User scenario Network condition Filtering rule General scenario Network stability Default self-healing action Weak field environment Weak network signal, unstable environment Intercept all self-healing actions Rate-sensitive scenario Expected to camp on high-mode network Intercept self-healing actions that affect rate High-speed scenario Severe network fluctuations Intercept self-healing actions that actively trigger network switching

[0227] As shown in Table II, if the user scenario is a general scenario, it means that the network is stable, and the electronic device can not screen the self-healing actions, and the updated self-healing actions are the same as the default self-healing actions.

[0228] If the user scenario is a weak field environment, it means that the network signal is weak and the environment is unstable. At this time, the self-healing actions cannot repair the faults, and the electronic device can intercept all self-healing actions. In this way, the updated self-healing actions do not include any self-healing actions. In this case, when the user scenario is in a non-weak field environment, the electronic device repairs the faults.

[0229] If the user scenario is a rate-sensitive scenario, it means that it is expected to stay in a high-bandwidth network. At this time, suppressing SA is an unreasonable self-healing action, and the electronic device can intercept the suppression of SA. In this way, the updated self-healing actions do not include the suppression of SA.

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

[0231] To better understand this method, the following will be combined with Figure 5 for illustration.

[0232] Figure 5 shows a schematic flowchart of a fault handling method provided by an embodiment of the present application. As Figure 5 shown, the method may include the following steps:

[0233] S501. The electronic device receives a self-healing request for requesting to execute a self-healing action.

[0234] The electronic device may receive a self-healing request when a fault occurs in using the cellular network. In some implementations, the self-healing request may include a fault type.

[0235] S502. The electronic device reads the default self-healing actions in the configuration file.

[0236] The electronic device can obtain the default self-healing actions from the configuration file based on the self-healing request. The configuration file can include various self-healing actions, and these self-healing actions are sorted according to the degree of impact.

[0237] In some examples, the corresponding relationships shown in Table 1 above are stored in the configuration file. The electronic device can obtain the self-healing actions corresponding to this fault type from the configuration file based on the fault type in the self-healing request.

[0238] S503. The electronic device reads the user scenario.

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

[0240] 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 can also include a general scenario.

[0241] The manner in which the electronic device detects the user scenario can be as follows:

[0242] 1) The electronic device can identify whether it is in a weak field environment by judging the network signal strength. Among them, the network signal strength can include the strength of the received power of the reference signal (reference signal received power, RSRP), the strength of the received quality of the reference signal (reference signal received quality, RSRQ), or the strength of the signal-to-noise ratio (signal to noise ratio, SNR), or one or more of them.

[0243] Exemplarily, the electronic device can judge whether the electronic device is in a weak field environment based on the strength of the RSRP. If the strength of the RSRP is greater than or equal to the threshold value S, it means that the electronic device is in a non-weak field environment. If the strength of the RSRP is less than the threshold value S, it means that the electronic device is in a weak field environment. In some examples, S can be -115 or -110, and the embodiments of the present application do not limit this.

[0244] Exemplarily, the electronic device can judge whether the electronic device is in a weak field environment based on the strength of the RSRP, the strength of the RSRQ, and the strength of the SNR.

[0245] The threshold values corresponding to the strength of the RSRP, the strength of the RSRQ, and the strength of the SNR can be as shown in Table 3.

[0246] Table 3

[0247]

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

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

[0250] If the communication technology between the electronic device and the network device uses Sub 6Ghz technology, and the RSRP of the network signal < -115, the RSRQ of the network signal < -16, and the SNR of the network signal < 5, then the electronic device can determine that the electronic device is in a weak field environment. If such conditions are not met, the electronic device can determine that the electronic device is in a non-weak field environment.

[0251] If the communication technology between the electronic device and the network device uses Sub 1Ghz technology, and the RSRP of the network signal < -115, the RSRQ of the network signal < -16, and the SNR of the network signal < 5, then the electronic device can determine that the electronic device is in a weak field environment. If such conditions are not met, the electronic device can determine that the electronic device is in a non-weak field environment.

[0252] It should be noted that in Table III above, the same thresholds corresponding to different communication technologies are only an example, and the thresholds corresponding to different communication technologies can also be different. The embodiments of the present application do not make any limitations in this regard.

[0253] 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.

[0254] The electronic device can preset a whitelist, which can include one or more applications. The applications in the whitelist can be applications for testing the running rate of the electronic device or applications for displaying the running rate of the electronic device.

[0255] The whitelist can include one or more of the identification, name, or application package name of the application. The embodiments of the present application do not make any limitations in this regard. 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 cannot be found in the whitelist, the electronic device can determine that the electronic device is in a non-rate-sensitive scenario.

[0256] Exemplarily, the electronic device can obtain the application package names of the applications running on the electronic device, and determine whether there are the same package names as these application package names included in the whitelist. If there are, it means that the applications 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 applications running on the electronic device cannot be found in the whitelist, and the electronic device can determine that the electronic device is in a non-rate-sensitive scenario.

[0257] 3) The electronic device can identify whether it is in a high-speed scenario by determining whether the sensor data meets the threshold.

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

[0259] It should be noted that identifying whether it is in a high-speed scenario by determining whether the sensor data meets the threshold is only an example, and the embodiments of the present application do not limit the specific manner of identifying the high-speed scenario.

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

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

[0262] As shown in Table II 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, does not perform the self-healing action.

[0263] Exemplarily, if the electronic device continuously freezes and fails when playing a video, and the electronic device detects that the fault type is data freeze. In the example shown in Table I above, the electronic device can obtain that the default self-healing actions can include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the RSRP intensity is less than the threshold value S and the user scenario includes a weak field environment, the electronic device intercepts the default self-healing action, that is, does not perform the actions of switching cells, suppressing SA, re-registering, and restarting the radio function.

[0264] 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.

[0265] S507. If the user scenario includes a rate-sensitive scenario, the electronic device intercepts the self-healing actions that affect the rate.

[0266] 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 the self-healing actions that affect the rate, the electronic device can intercept the self-healing actions that affect the rate. For example, the electronic device can intercept the suppression of SA.

[0267] Exemplarily, if the electronic device continuously freezes and malfunctions while playing a video, and the electronic device detects that the fault type is data freeze, in the example shown in Table 1 above, the default self-healing actions that the electronic device can obtain 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 application programs 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 actions include switching cells -> re-registering -> restarting the radio function.

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

[0269] S509. If the user scenario includes a high-speed scenario, intercept the self-healing actions that actively trigger network switching.

[0270] 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 actions that actively trigger network switching, the electronic device can intercept the self-healing actions that actively trigger network switching. For example, the electronic device can intercept switching cells and suppressing SA.

[0271] Exemplarily, after intercepting the self-healing actions that affect the rate, the updated self-healing actions include switching cells -> re-registering -> restarting the radio function. If the user scenario includes a high-speed scenario, the electronic device can intercept switching cells and suppressing SA. In this way, the self-healing actions updated again include re-registering -> restarting the radio function.

[0272] S510. If the user scenario does not include a high-speed scenario, or after intercepting the self-healing actions that actively trigger network switching, the electronic device performs the next screening.

[0273] In some examples, if the user scenario does not include a high-speed scenario, the user scenario can be a general scenario, and the screening rule corresponding to the general scenario is the default self-healing actions, that is, do not intercept any actions in the default self-healing actions, and the next screening can be performed. The next screening can be that the electronic device screens the default self-healing actions based on prior information and / or link information.

[0274] In other examples, after intercepting the self-healing actions that actively trigger network switching, the electronic device can perform the next screening.

[0275] 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 screening, which is just 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 network switching, the electronic device may execute the above S403 to S409.

[0276] The fault handling method provided by the embodiments of the present application screens the default self-healing actions based on the user scenario to delete unreasonable or ineffective self-healing actions, which is beneficial to improving the probability of successful self-healing and further beneficial to shortening the duration of fault repair.

[0277] The above S402, the electronic device screens the default self-healing actions based on one or more of the user scenario, prior information, and link information to obtain updated self-healing actions, which may include: the electronic device screens the default self-healing actions based on the prior information to obtain updated self-healing actions.

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

[0279] To better understand this method, the following is combined with Figure 6 for illustration.

[0280] Exemplarily, Figure 6 shows a schematic flowchart of a fault handling method provided by the embodiments of the present application. As Figure 6 shown, the method may include the following steps:

[0281] S601. The electronic device reads a self-healing action from the default self-healing actions.

[0282] When the electronic device screens the self-healing actions based on the prior information, it may traverse the default self-healing actions and read each self-healing action in the default self-healing actions in turn.

[0283] Read a self-healing action from the default self-healing actions, where this self-healing action may be any one of the default self-healing actions, and the embodiments of the present application do not make any limitations in this regard.

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

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

[0286] S603. If the number of self-healing times of the self-healing action reaches T times and the success rate is greater than S1, the electronic device adjusts the sorting and advances the self-healing action.

[0287] If the number of self-healing times reaches T times and the success rate is greater than S1 under the same cell and the same motion state, it indicates that the probability of this self-healing action being able to repair the fault is relatively high, and the execution order of this self-healing action can be advanced. Among them, if this self-healing action is the first self-healing action that meets the conditions, the electronic device can adjust this self-healing action to the first self-healing action in the default self-healing actions. If this self-healing action is not the first self-healing action that meets the conditions, the electronic device can adjust it after the previous self-healing action that meets the conditions.

[0288] Exemplarily, T is 5 and S1 is 90%. If the electronic device continuously freezes during video playback and a fault occurs, and the electronic device detects that the fault type is data freezing. In the example shown in Table 1 above, the electronic device can obtain that the default self-healing actions 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 number of self-healing times of suppressing SA reaches 5 times under the same cell and the same motion state, and the success rate is greater than 90%, then the electronic device adjusts suppressing SA before switching cells, and the updated self-healing actions obtained are: suppressing SA -> switching cells -> re-registering -> restarting the radio function.

[0289] Optionally, if the number of self-healing times of the self-healing action reaches T times and the success rate is greater than S1, the electronic device adjusts the sorting and advances the self-healing action, which may include: when the number of self-healing times of the self-healing action reaches T times and the success rate is greater than S1, the electronic device determines whether this self-healing action is a preset self-healing action. If it is not a preset self-healing action, the self-healing action is advanced. Among them, the preset self-healing actions are self-healing actions with a relatively large impact degree. If it is a preset self-healing action, the electronic device does not advance the self-healing action.

[0290] In some examples, the preset self-healing actions are restarting the radio function and / or restarting the modem. If the number of self-healing times of suppressing SA reaches T times and the success rate is greater than S1, the electronic device determines whether suppressing SA is a preset self-healing action. Since suppressing SA is not a preset self-healing action, suppressing SA is advanced. If the number of self-healing times of restarting the radio function 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. Since restarting the radio function is a preset self-healing action, the suppression of restarting the radio function is not advanced, that is, the execution order of restarting the radio function remains unchanged.

[0291] In this way, while considering improving the repair of the fault, the impact on the user can also be taken into account.

[0292] S604. If the number of self-healing attempts of the self-healing action does not reach T times, or the success rate is not greater than S1, the electronic device may determine whether the number of self-healing attempts of the self-healing action reaches T times and whether the success rate is greater than S2.

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

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

[0295] If the number of self-healing attempts of the self-healing action reaches T times and the success rate is less than S2, it can be shown that the probability of the self-healing action being able to repair the fault is low, and the self-healing action can be deleted.

[0296] Exemplarily, T is 5, S1 is 90%, and S2 is 5%. If the electronic device continuously freezes during video playback 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 can obtain that the default self-healing actions 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 under the same cell and the same motion state is not greater than 90%. At the same time, the number of self-healing attempts of switching cells under 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 switching cells, and the updated self-healing actions obtained are: suppressing SA -> re-registering -> restarting the radio function.

[0297] S606. If the number of self-healing attempts 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.

[0298] Each self-healing action corresponds to a protection time. During this protection time, the self-healing action will not be executed repeatedly. Therefore, the electronic device may determine whether the self-healing action is within its corresponding protection time to decide whether to execute the self-healing action.

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

[0300] If the self-healing action is not within its corresponding protection time, no adjustment is made to the self-healing action, and the next self-healing action in the default self-healing actions can continue to be read, and the processes of S602 to S607 are repeated for the next self-healing action until all the self-healing actions in the default self-healing actions are read.

[0301] If the self-healing action is within its corresponding protection time, the electronic device can delete the self-healing action, that is, execute S605.

[0302] Exemplarily, if the electronic device continuously freezes and malfunctions while playing a video, and the electronic device detects that the fault type is data freeze. In the example shown in Table 1 above, the default self-healing actions that the electronic device can obtain 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 suppressing SA is within its corresponding protection time of 5 minutes, the electronic device can delete suppressing SA and obtain switching cells -> re-registering -> restarting the radio function.

[0303] The fault handling method provided by the embodiments of this application can sort the default self-healing actions based on prior information, so as to first execute the self-healing actions with a higher probability of fixing the fault subsequently, which is beneficial to shortening the duration of fixing the fault.

[0304] The above Figure 6 The method shown introduces screening the default self-healing actions based on prior information to obtain updated self-healing actions. In another example, the electronic device can also screen the default self-healing actions based on the user scenario and prior information to obtain updated self-healing actions.

[0305] In one implementation, the electronic device can screen the self-healing actions obtained based on the method shown above based on prior information to obtain updated self-healing actions. Figure 5

[0306] In another implementation, the electronic device can screen the self-healing actions obtained based on the method shown above based on the user scenario to obtain updated self-healing actions. Figure 6

[0307]

[0308] In this way, it is more beneficial to shorten the duration of fixing the fault.

[0309] In the above S402, the electronic device screens the default self-healing actions based on one or more of the user scenario, prior information, and link information to obtain updated self-healing actions, which may include: the electronic device screens the default self-healing actions based on the link information to obtain updated self-healing actions.

[0309] The electronic device can delete invalid actions based on the link information to obtain updated self-healing actions. Among them, the link information may include no service, current service status, the cell where it is located is in the idle state, the cell where it is located is in the connected state, and network conditions, etc.

[0310] To better understand this method, the following combinationFigure 7 Explanation is given as follows.

[0311] Exemplarily, Figure 7 A schematic flowchart of a fault handling method provided by an embodiment of the present application is shown. As Figure 7 shown, the method may include the following steps:

[0312] S701. The electronic device reads the default self-healing actions in the configuration file.

[0313] This step may refer to the above S502 and will not be elaborated here.

[0314] S702. The electronic device reads the current link state.

[0315] The electronic device can monitor the link state between the electronic device and the network device and store the monitored link state in the memory or storage. After the electronic device reads the default self-healing actions, it can read the current link state to screen the default self-healing actions according to the current link state.

[0316] S703. The electronic device determines whether the current link state is out of service.

[0317] S704. If the current link state is out of service, the electronic device can intercept the default self-healing actions.

[0318] If the current link state is out of service, it indicates that the electronic device fails to camp on the network successfully. At this time, the probability that all self-healing actions can repair the fault is relatively small. Therefore, the electronic device can intercept the default self-healing actions, so that the electronic device does not need to execute the self-healing actions.

[0319] S705. If the current link state is not out of service, the electronic device can determine whether the cell where the electronic device is located is in the idle state.

[0320] If the current link state is not out of service, it indicates that the camping on the network is successful. The electronic device can determine whether the cell where the electronic device is located is in the idle state, that is, determine whether the communication link between the electronic device and the network device is not successfully established. Among them, the communication link needs to be established before the service data is transmitted.

[0321] S706. If the cell where the electronic device is located is in the idle state, the electronic device intercepts the self-healing actions executed in the connected state.

[0322] If the cell where the electronic device is located is in the idle state, it indicates that the communication link between the electronic device and the network device is not successfully established. At this time, the self-healing actions that can be executed in the connected state are invalid and cannot achieve successful self-healing even if executed. Therefore, the electronic device intercepts the self-healing actions executed in the connected state.

[0323] Exemplarily, the self-healing actions performed in the connected state may include switching cells. If the electronic device continuously freezes and malfunctions while playing a video, and the electronic device detects that the fault type is data freeze, in the example shown in Table 1 above, the default self-healing actions that the electronic device can obtain may include switching cells -> suppressing SA -> re-registering -> restarting the radio function. If the cell where the electronic device is located is in the idle state, the electronic device intercepts the cell switch, that is, deletes the cell switch, and the updated self-healing actions obtained are: suppressing SA -> re-registering -> restarting the radio function.

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

[0325] If the cell where the electronic device is located is not in the idle state, it means that the cell where the electronic device is located is in the 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 where it is located is a 5G signal.

[0326] 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 merely 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, and the embodiments of the present application do not make limitations in this regard.

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

[0328] If the network signal type of the cell where the electronic device is located is not a 5G signal, the self-healing actions related to the 5G signal are ineffective, and self-healing cannot be successfully achieved even if they are executed. Therefore, the electronic device intercepts the self-healing actions related to the 5G signal. For example, the electronic device can intercept the suppression of SA.

[0329] If the network signal type of the cell where the electronic device is located is a 5G signal, or after intercepting the self-healing actions related to the 5G signal, the electronic device can perform the next screening. Among them, the next screening can be that the electronic device screens the default self-healing actions based on prior information and / or user scenarios.

[0330] If the network signal type of the cell where the electronic device is located is a 5G signal, or after intercepting the self-healing actions related to the 5G signal, the electronic device can perform the next screening, which is merely 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 intercepting the self-healing actions related to the 5G signal, the electronic device can execute the above S403 to S409.

[0331] The fault handling method provided by the embodiments of the present application filters the default self-healing actions based on link information to delete unreasonable or ineffective self-healing actions, which is beneficial to improving the probability of successful self-healing and further shortening the duration of fault repair.

[0332] The above introduces the method provided by the embodiments of the present application from the perspective of the specific implementation of the electronic device. Next, the method provided by the embodiments of the present application will be introduced in combination with application scenarios.

[0333] Exemplarily, the fault handling method provided by the embodiments of the present application may include: when the network fault of the electronic device is the first fault 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 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 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.

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

[0335] Optionally, when the network fault of the electronic device is the first fault 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.

[0336] In this way, when the electronic device is in a high-speed scenario and a rate-sensitive scenario, actions that affect the network rate are not performed, which is beneficial to shortening the fault duration.

[0337] Optionally, when the network fault of the electronic device is the first fault 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.

[0338] Optionally, when the network fault of the electronic device is the first fault 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 performed 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.

[0339] Optionally, 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 still in a service state, and the service state is used to indicate that the electronic device has successfully camped on the network.

[0340] It should be noted that the module names involved in the embodiments of the present application can all be defined as other names, as long as the functions of each module can be achieved, and no specific restrictions are imposed on the module names.

[0341] 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 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 need to comply with the relevant laws, regulations, and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or reject.

[0342] The fault handling method of the embodiments of the present application has been described above. Next, the device for executing the above method provided by the embodiments of the present application will be described. Those skilled in the art can understand that the method and the device can be combined and referenced with each other, and the relevant device provided by the embodiments of the present application can execute the steps in the above fault handling method.

[0343] Figure 8 It is a schematic structural diagram of a chip provided by an embodiment of the present application. As Figure 8 shown, the chip 80 includes one or more than two (including two) processors 801, a communication line 802, a communication interface 803, and a memory 804.

[0344] In some embodiments, the memory 804 stores the following elements: executable modules or data structures, or subsets thereof, or extended sets thereof.

[0345] The network lag handling method described in the embodiments of the present application above can be applied to or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above network lag handling method can be completed by the integrated logic circuit in hardware or instructions in software form in the processor 801. The above-mentioned processor 801 may be a general-purpose processor (e.g., 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 gate, transistor logic devices, or discrete hardware components. The processor 801 can implement or execute the various processing-related methods, steps, and logic block diagrams disclosed in the embodiments of the present application.

[0346] The steps of the network lag handling method disclosed in combination with the embodiments of the present application can be directly implemented by a hardware decoding processor or completed by a combination of hardware and software modules in the decoding processor. Among them, the software module can be located in mature storage media in the art such as random access memory, read-only memory, programmable read-only memory, or electrically erasable programmable read-only memory (EEPROM). This storage medium is located in the memory 804, and the processor 801 reads the information in the memory 804 and combines its hardware to complete the steps of the above method.

[0347] Communication can be carried out between the processor 801, the memory 804, and the communication interface 803 through the communication line 802.

[0348] In the above embodiment, the instructions stored in the memory for the processor to execute can be implemented in the form of a computer program product. Among them, the computer program product can be pre-written in the memory or downloaded and installed in the memory in software form.

[0349] The fault handling method provided in the embodiments of the present application can be applied to an electronic device with communication functions. The electronic device includes a terminal device, and the specific device form of the terminal device and the like can refer to the above relevant description and will not be elaborated here.

[0350] 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, and 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.

[0351] An embodiment of the present application provides a chip. The chip or chip system is applied to an electronic device. 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 fault handling method in the above-mentioned embodiment. Its implementation principle and technical effects are similar to those of the above-related embodiments, and will not be elaborated here.

[0352] An embodiment of the present application also provides 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 code on a computer-readable medium or transmitted on a computer-readable medium. The computer-readable medium can include a computer storage medium and a communication medium, 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 accessible by a computer.

[0353] In a possible implementation, the computer-readable medium may include RAM, ROM, a compact disc read-only memory (CD-ROM), or other optical disc memories, a magnetic disk memory, or other magnetic storage devices, or any other medium targeted at carrying or storing the required program code in the form of instructions or data structures and accessible by a computer. Moreover, any connection is properly referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio, and microwave is included in the definition of the medium. As used herein, disk and optical disc include optical disc, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while optical discs use lasers to optically reproduce data. The above combinations should also be included within the scope of the computer-readable medium.

[0354] 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 is caused to execute the above-mentioned fault handling method.

[0355] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable devices to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing devices generate means for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

[0356] The above specific implementation manners further elaborate on the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are only specific implementation manners of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solution of the present invention should be included in the protection scope 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 moving 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 of the first failure type and the moving 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 of the first failure type and the moving 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 also 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 of the first failure type and the moving 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 of the first failure type and the moving speed of the electronic device is the first speed, the electronic device is also in an idle state, and the first fault repair action also does not include actions in the first fault repair action list that cannot be executed in the idle state, where 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 of the first failure type and the moving speed of the electronic device is the first speed, the electronic device is also in a service state, where 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 moving 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 moving speed of the electronic device is the first speed; The electronic device performs the first fault repair action, including: The electronic device performs the second action; If after the second action is executed, the network failure of the electronic device is still of 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, then execute the fourth action.

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 moving 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 accessed network device, 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, wherein If the first scenario is distinguished according to the moving 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 moving speed of the electronic device meets a preset condition, delete the action for triggering network switching in the first fault repair action list 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, delete the actions that affect network rate in the first fault repair action list 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 accessed network 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 an idle state, delete the actions that cannot be executed in the idle state in the first fault repair action list 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 accessed network device 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 by 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 by 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 third action in the first fault repair action list is not included in the first target fault repair action. When the network fault of the electronic device is the first fault type, the number of times of successfully repairing the fault by 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 by 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 conforms to 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 call computer instructions to cause the electronic device to execute the method described in any one of claims 1 to 12, or to cause the electronic device to execute the method described in any one of claims 13 to 23.

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

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

Images