Abnormal recovery method, device and equipment, medium and program product

Abstract

The invention discloses an exception recovery method and device, equipment, a medium and a program product in the technical field of communication. According to the method and the device, the firmware upgrading abnormity of the cellular communication module can be monitored, and the management driver is forcibly installed into the operating system when the firmware upgrading abnormity occurs, so that the operating system automatically creates the equipment node, the management driver is mounted to the equipment node, and the dependence of driver mounting on a BIOS (Basic Input / Output System) is relieved; then a restart command is sent to the management driver, so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded, so that re-upgrading of the cellular communication module after the firmware upgrading is abnormal is realized, and the problem of upgrading abnormity is solved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an abnormality recovery method, device, equipment, medium and program product. Background Art

[0002] Currently, for terminals with cellular (WWAN) communication modules, the firmware upgrade of the cellular communication module can usually be completed through a burning tool or a firmware upgrade driver. If the firmware upgrade driver is used for the upgrade, the BIOS needs to generate a device node and then complete the mounting of the firmware upgrade driver. This process is overly dependent on the BIOS.

[0003] Therefore, how to implement the firmware upgrade of the cellular communication module without relying on BIOS is a problem that those skilled in the art need to solve. Summary of the invention

[0004] In view of this, the purpose of this application is to provide an abnormal recovery method, device, equipment, medium and program product to implement the firmware upgrade of the cellular communication module without relying on BIOS. The specific scheme is as follows:

[0005] In a first aspect, the present application provides an abnormality recovery method, comprising:

[0006] If it is detected that the firmware upgrade of the cellular communication module is abnormal, the management driver is forcibly installed into the operating system so that the operating system creates a device node;

[0007] Mounting the management driver to the device node, and sending a restart command to the management driver, so that the management driver controls the cellular communication module to restart;

[0008] After the cellular communication module is restarted, the firmware of the cellular communication module is upgraded.

[0009] Optionally, the firmware upgrade exception of the cellular communication module is monitored, including:

[0010] The firmware burning failure result and the abnormal state of the port of the cellular communication module are monitored.

[0011] Optionally, the forcibly installing the management driver into the operating system includes:

[0012] Forcefully install the management driver into the operating system in Legacy mode.

[0013] Optionally, sending a restart command to the management driver includes:

[0014] Send a restart command defined by the IOCTL code to the management driver.

[0015] Optionally, the management driver controls the cellular communication module to restart, including:

[0016] The management driver restarts the cellular communication module through the GPIO pin of the cellular communication module.

[0017] Optionally, upgrading the firmware of the cellular communication module includes:

[0018] After handshaking communication with the cellular communication module, downloading the firmware of the cellular communication module into the cellular communication module;

[0019] After the download is completed, the firmware burning success result and the normal status of the port of the cellular communication module are monitored.

[0020] Optionally, after upgrading the firmware of the cellular communication module, the method further includes:

[0021] Uninstall the management driver and clean up corresponding useless data.

[0022] Optionally, before forcibly installing the management driver to the operating system, the following steps are also included:

[0023] Re-upgrading the firmware of the cellular communication module;

[0024] If the re-upgrade is successful, exit the process;

[0025] If the re-upgrade fails, perform the steps to forcibly install the management driver to the operating system and the subsequent steps.

[0026] In a second aspect, the present application provides an abnormality recovery device, comprising:

[0027] An installation module, for forcibly installing a management driver into an operating system if an abnormal firmware upgrade of the cellular communication module is detected, so that the operating system creates a device node;

[0028] an execution module, configured to mount the management driver to the device node, and send a restart command to the management driver, so that the management driver controls the cellular communication module to restart;

[0029] The upgrading module is used to upgrade the firmware of the cellular communication module after the cellular communication module is restarted.

[0030] In a third aspect, the present application provides an electronic device, including:

[0031] Memory for storing computer programs;

[0032] The processor is used to execute the computer program to implement the above-disclosed abnormality recovery method.

[0033] In a fourth aspect, the present application provides a non-volatile storage medium for storing a computer program, wherein the computer program implements the aforementioned disclosed exception recovery method when executed by a processor.

[0034] In a fifth aspect, the present application provides a computer program product, including a computer program / instruction, which implements the steps of the aforementioned disclosed exception recovery method when executed by a processor.

[0035] It can be seen from the above scheme that the present application provides an abnormal recovery method, including: if a firmware upgrade abnormality of the cellular communication module is monitored, forcibly installing a management driver into the operating system so that the operating system creates a device node; mounting the management driver to the device node, and sending a restart command to the management driver so that the management driver controls the cellular communication module to restart; after the restart of the cellular communication module is completed, upgrading the firmware of the cellular communication module.

[0036] It can be seen that the present application is able to monitor firmware upgrade anomalies of the cellular communication module, and force the installation of the management driver into the operating system when an anomaly occurs, so that the operating system automatically creates a device node, thereby mounting the management driver to the device node, eliminating the driver mounting's dependence on the BIOS; then sending a restart command to the management driver so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded, thereby achieving a re-upgrade of the cellular communication module's firmware after an abnormal upgrade, and solving the upgrade anomaly problem.

[0037] Correspondingly, an abnormal recovery device, equipment, medium and program product provided by the present application also have the above-mentioned technical effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0039] Figure 1 A flow chart of an abnormal recovery method disclosed in this application;

[0040] Figure 2 A framework diagram of an abnormal recovery solution disclosed in this application;

[0041] Figure 3 A flow chart of another abnormal recovery method disclosed in this application;

[0042] Figure 4 A schematic diagram of an abnormality recovery device disclosed in this application;

[0043] Figure 5 A schematic diagram of an electronic device disclosed in this application;

[0044] Figure 6 A server structure diagram provided for this application;

[0045] Figure 7 A terminal structure diagram provided for this application. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other examples obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] At present, for terminals with cellular (WWAN) communication modules, the firmware upgrade of the cellular communication module can usually be completed through a burning tool or a firmware upgrade driver. If the upgrade is performed with the help of a firmware upgrade driver, the BIOS needs to generate a device node and then complete the mounting of the firmware upgrade driver. This process is overly dependent on the BIOS. To this end, the present application provides an abnormal recovery solution that can implement the firmware upgrade of the cellular communication module without relying on the BIOS. WWAN technology enables laptops or other devices to connect to the Internet anywhere within the coverage of the cellular network.

[0048] See also Figure 1 As shown, the embodiment of the present application discloses an abnormality recovery method, including:

[0049] S101: If it is detected that the firmware upgrade of the cellular communication module is abnormal, a management driver is forcibly installed into the operating system so that the operating system creates a device node.

[0050] This embodiment can monitor the firmware upgrade process of the cellular communication module in real time. In one implementation, monitoring the firmware upgrade abnormality of the cellular communication module includes: monitoring the firmware burning failure result and the abnormal state of the port of the cellular communication module.

[0051] In one implementation, forcibly installing the management driver into the operating system includes: forcibly installing the management driver into the operating system in a legacy manner. Of course, the forcible installation of the management driver can also be achieved in other ways.

[0052] S102: Mount the management driver to the device node, and send a restart command to the management driver, so that the management driver controls the cellular communication module to restart.

[0053] In one implementation, sending a restart command to the management driver includes: sending a restart command defined by an IOCTL code to the management driver.

[0054] In one implementation, the management driver controls the cellular communication module to restart, including: the management driver restarts the cellular communication module through a GPIO pin of the cellular communication module.

[0055] S103: After the cellular communication module is restarted, the firmware of the cellular communication module is upgraded.

[0056] It should be noted that the basic logic of upgrading the firmware of the cellular communication module includes: when the port of the cellular communication module is normal, sending a reset and restart command to the cellular communication module to restart the module to the burning mode; the burning port appears in the burning mode, and then handshakes with the cellular communication module and downloads the firmware to the cellular communication module; after the download is successfully completed, the module restarts again and returns to the normal port state. Therefore, in one embodiment, upgrading the firmware of the cellular communication module includes: after handshaking communication with the cellular communication module, downloading the firmware of the cellular communication module to the cellular communication module; after the download is completed, monitoring the successful result of firmware burning and the normal state of the port of the cellular communication module.

[0057] In one implementation, after the firmware of the cellular communication module is upgraded, the method further includes: uninstalling the management driver and clearing corresponding useless data.

[0058] In one embodiment, before forcibly installing the management driver to the operating system, it also includes: re-upgrading the firmware of the cellular communication module; if the re-upgrade is successful, exiting the process; if the re-upgrade fails, executing the step of forcibly installing the management driver to the operating system and other subsequent steps.

[0059] It can be seen that the present embodiment is capable of monitoring firmware upgrade anomalies of the cellular communication module, and forcibly installing the management driver into the operating system when anomalies occur, so that the operating system automatically creates a device node, thereby mounting the management driver to the device node, eliminating the driver mounting's dependency on the BIOS; thereafter, a restart command is sent to the management driver, so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded, thereby achieving a re-upgrade of the cellular communication module's firmware after an abnormal upgrade, and solving the upgrade abnormality problem.

[0060] In another example, a background burning and monitoring service program is provided: FwUpgradeService, in which the relevant methods provided by the present application are implemented. The program specifically includes: a burning abnormal port monitoring function module: RecoveryMonitorFunc, a firmware download function module: DownloadFunc, and a forced restart driver (i.e., a management driver): ACPI-ReSet driver, which is published and pushed to the user's computer together with the component content of FwUpgradeService.

[0061] See also Figure 2 and Figure 3 , the corresponding method functions implemented in FwUpgradeService include:

[0062] (1) Abnormal monitoring.

[0063] After the firmware burning exception of the cellular communication module occurs, FwUpgradeService attempts to retry. If the retry succeeds, it ends normally. If the retry fails, the RecoveryMonitorFunc process is triggered.

[0064] (2) Start abnormal recovery.

[0065] RecoveryMonitorFunc confirms the abnormality according to the previous burning results and port status, and starts the abnormality recovery process.

[0066] (3) Install the driver in Legacy mode.

[0067] The program automatically builds an abnormal recovery environment and forcibly installs the ACPI-ReSet driver into the system in Legacy mode. The system automatically creates a node and mounts the ACPI-ReSet driver.

[0068] (4) ACPI restarts the cellular communication module.

[0069] FwUpgradeService notifies the ACPI-ReSet driver to restart the cellular communication module according to the defined IOCTL code (restart command), and notifies DownloadFunc to enter the burning handshake phase. Among them, the ACPI-ReSet driver implements PLDR (Platform-level Device Reset), which enables the BIOS to control GPIO to trigger the module restart.

[0070] (5) Firmware burning.

[0071] After the cellular communication module restarts, DownloadFunc promptly shakes hands with the burning port of the cellular communication module to re-download the previously interrupted firmware to the cellular communication module.

[0072] (6) The upgrade is successful.

[0073] After the firmware of the cellular communication module is successfully downloaded, the cellular communication module is restarted to restore it to a normal port, and RecoveryMonitorFunc will start the end of abnormal recovery.

[0074] (7) Uninstall and clean up the relevant data involved in the above process.

[0075] The program automatically uninstalls the ACPI-ReSet driver and cleans up components that were installed separately during the abnormal recovery process. The abnormal recovery process ends here.

[0076] It can be seen that this embodiment can automatically detect firmware upgrade anomalies in the background, and start the abnormal recovery process in a timely manner, and remove unnecessary components after recovery to ensure consistency during the normal use phase of the customer; the developed ACPI-ReSet driver supports Legacy installation, gets rid of the dependence on the BIOS node, and the driver restarts and recovers the cellular communication module in a standard PLDR manner, achieving compatibility with USB or PCIe interfaces.

[0077] An abnormality recovery device provided in an embodiment of the present application is introduced below. The abnormality recovery device described below can be referenced to other embodiments described in this document.

[0078] See also Figure 4 As shown, the embodiment of the present application discloses an abnormality recovery device, including:

[0079] The installation module 401 is used for forcibly installing the management driver into the operating system if it is detected that the firmware upgrade of the cellular communication module is abnormal, so that the operating system creates a device node;

[0080] The execution module 402 is used to mount the management driver to the device node and send a restart command to the management driver so that the management driver controls the cellular communication module to restart;

[0081] The upgrading module 403 is used to upgrade the firmware of the cellular communication module after the cellular communication module is restarted.

[0082] In one embodiment, the installation module is specifically used to:

[0083] The firmware burning failure result and the abnormal port status of the cellular communication module were monitored.

[0084] In one embodiment, the installation module is specifically used to:

[0085] Forcefully install the management driver into the operating system in Legacy mode.

[0086] In one implementation, the execution module is specifically used to:

[0087] Send a restart command defined by the IOCTL code to the management driver.

[0088] In one implementation, the management driver controls the cellular communication module to restart, including:

[0089] The management driver restarts the cellular communication module through the GPIO pin of the cellular communication module.

[0090] In one embodiment, the upgrade module is specifically used to:

[0091] After handshaking communication with the cellular communication module, downloading the firmware of the cellular communication module into the cellular communication module;

[0092] After the download is complete, the firmware is successfully burned and the port status of the cellular communication module is normal.

[0093] In one embodiment, it further includes:

[0094] The cleanup module is used to uninstall the management driver and clean up the corresponding useless data.

[0095] In one embodiment, it further includes:

[0096] The retry module is used to re-upgrade the firmware of the cellular communication module; if the re-upgrade is successful, the process is exited; if the re-upgrade fails, the step of forcibly installing the management driver to the operating system and other subsequent steps are executed.

[0097] Among them, for more specific working processes of each module and unit in this embodiment, reference can be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be repeated here.

[0098] It can be seen that the present embodiment provides an abnormality recovery device, which can monitor the firmware upgrade abnormality of the cellular communication module, and force the installation of the management driver into the operating system when the abnormality occurs, so that the operating system automatically creates a device node, thereby mounting the management driver to the device node, and eliminating the driver mounting's dependence on the BIOS; then sending a restart command to the management driver, so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded, thereby realizing the re-upgrade of the cellular communication module firmware after the abnormal upgrade, and solving the upgrade abnormality problem.

[0099] An electronic device provided in an embodiment of the present application is introduced below. The electronic device described below can be referenced to other embodiments described in this document.

[0100] See also Figure 5 As shown, the embodiment of the present application discloses an electronic device, including:

[0101] Memory 501, used for storing computer programs;

[0102] The processor 502 is used to execute the computer program to implement the method disclosed in any of the above embodiments.

[0103] In this embodiment, when the processor executes the computer program stored in the memory, the following steps can be specifically implemented: if an abnormal firmware upgrade of the cellular communication module is detected, the management driver is forcibly installed into the operating system so that the operating system creates a device node; the management driver is mounted to the device node, and a restart command is sent to the management driver so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded.

[0104] In this embodiment, when the processor executes the computer program stored in the memory, the following steps may be specifically implemented: monitoring the firmware burning failure result and the abnormal state of the port of the cellular communication module.

[0105] In this embodiment, when the processor executes the computer program stored in the memory, the following steps may be specifically implemented: forcibly installing the management driver into the operating system in a Legacy manner.

[0106] In this embodiment, when the processor executes the computer program stored in the memory, the following steps may be specifically implemented: sending a restart command defined by an IOCTL code to a management driver.

[0107] In this embodiment, when the processor executes the computer program stored in the memory, the following steps may be specifically implemented: managing the driver to restart the cellular communication module through the GPIO pin of the cellular communication module.

[0108] In this embodiment, when the processor executes the computer program stored in the memory, the following steps can be specifically implemented: after handshake communication with the cellular communication module, the firmware of the cellular communication module is downloaded to the cellular communication module; after the download is completed, the successful result of firmware burning and the normal status of the port of the cellular communication module are monitored.

[0109] In this embodiment, when the processor executes the computer program stored in the memory, the following steps may be specifically implemented: uninstalling the management driver and clearing corresponding useless data.

[0110] In this embodiment, when the processor executes the computer program stored in the memory, the following steps can be specifically implemented: re-upgrading the firmware of the cellular communication module; if the re-upgrade is successful, exiting the process; if the re-upgrade fails, executing the step of forcibly installing the management driver to the operating system and other subsequent steps.

[0111] Furthermore, the present application also provides an electronic device. The electronic device can be Figure 6 The server shown can also be Figure 7 Terminal shown. Figure 6 and Figure 7 All of them are structural diagrams of electronic devices according to an exemplary embodiment, and the contents in the diagrams cannot be regarded as any limitation on the scope of use of the present application.

[0112] Figure 6 A schematic diagram of the structure of a server provided in an embodiment of the present application. The server may specifically include: at least one processor, at least one memory, a power supply, a communication interface, an input / output interface, and a communication bus. The memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement the relevant steps in the abnormal recovery disclosed in any of the aforementioned embodiments.

[0113] In this embodiment, the power supply is used to provide working voltage for each hardware device on the server; the communication interface can create a data transmission channel between the server and external devices, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0114] In addition, the memory as a carrier for resource storage can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon include operating system, computer programs and data, etc. The storage method can be temporary storage or permanent storage.

[0115] The operating system is used to manage and control the hardware devices and computer programs on the server to realize the operation and processing of the data in the memory by the processor, and it can be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the abnormal recovery method disclosed in any of the above embodiments, the computer program can further include computer programs that can be used to complete other specific tasks. In addition to data such as application update information, the data can also include data such as application developer information.

[0116] Figure 7 A schematic diagram of the structure of a terminal provided in an embodiment of the present application, the terminal may specifically include but is not limited to a smart phone, a tablet computer, a laptop computer or a desktop computer, etc.

[0117] Generally, the terminal in this embodiment includes: a processor and a memory.

[0118] Among them, the processor may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0119] The memory may include one or more computer non-volatile storage media, which may be non-transitory. The memory may also include high-speed random access memory, and non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory is at least used to store the following computer program, wherein, after the computer program is loaded and executed by the processor, it can implement the relevant steps in the abnormal recovery method performed by the terminal side disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory may also include an operating system and data, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system may include Windows, Unix, Linux, etc. The data may include, but is not limited to, update information of the application.

[0120] In some embodiments, the terminal may also include a display screen, an input and output interface, a communication interface, a sensor, a power supply, and a communication bus.

[0121] Those skilled in the art will understand that Figure 7 The structure shown in the figure does not constitute a limitation on the terminal, and may include more or fewer components than those shown in the figure.

[0122] A non-volatile storage medium provided in an embodiment of the present application is introduced below. The non-volatile storage medium described below can be cross-referenced with other embodiments described herein.

[0123] A non-volatile storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the abnormality recovery method disclosed in the above-mentioned embodiment. The non-volatile storage medium is a computer-readable non-volatile storage medium, which, as a carrier for storing resources, may be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon include an operating system, a computer program and data, etc., and the storage method may be temporary storage or permanent storage.

[0124] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps can be specifically implemented: if a firmware upgrade exception of the cellular communication module is detected, the management driver is forcibly installed into the operating system so that the operating system creates a device node; the management driver is mounted to the device node, and a restart command is sent to the management driver so that the management driver controls the cellular communication module to restart; after the cellular communication module is restarted, the firmware of the cellular communication module is upgraded.

[0125] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps may be specifically implemented: monitoring the firmware burning failure result and the abnormal state of the port of the cellular communication module.

[0126] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps may be specifically implemented: forcibly installing the management driver into the operating system in a Legacy manner.

[0127] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps may be specifically implemented: sending a restart command defined by an IOCTL code to a management driver.

[0128] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps may be specifically implemented: managing the driver to restart the cellular communication module through the GPIO pin of the cellular communication module.

[0129] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps can be specifically implemented: after handshake communication with the cellular communication module, the firmware of the cellular communication module is downloaded to the cellular communication module; after the download is completed, the successful result of firmware burning and the normal status of the port of the cellular communication module are monitored.

[0130] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps may be specifically implemented: uninstalling the management driver and clearing corresponding useless data.

[0131] In this embodiment, when the processor executes the computer program stored in the non-volatile storage medium, the following steps can be specifically implemented: re-upgrading the firmware of the cellular communication module; if the re-upgrade is successful, exiting the process; if the re-upgrade fails, executing the step of forcibly installing the management driver to the operating system and other subsequent steps.

[0132] A computer program product provided in an embodiment of the present application is introduced below. The computer program product described below can be referenced to other embodiments described in this document.

[0133] A computer program product includes a computer program / instruction, which implements the steps of the above-disclosed exception recovery method when executed by a processor.

[0134] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0135] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of non-volatile storage medium known in the art.

[0136] Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. An abnormality recovery method, characterized in that: include: If it is detected that the firmware upgrade of the cellular communication module is abnormal, the management driver is forcibly installed into the operating system so that the operating system creates a device node; Mounting the management driver to the device node, and sending a restart command to the management driver, so that the management driver controls the cellular communication module to restart; After the cellular communication module is restarted, the firmware of the cellular communication module is upgraded.

2. The method according to claim 1, characterized in that The firmware upgrade of the cellular communication module was detected to be abnormal, including: The firmware burning failure result and the abnormal state of the port of the cellular communication module are monitored.

3. The method according to claim 1, characterized in that The forcible installation management driver into the operating system includes: Forcefully install the management driver into the operating system in Legacy mode.

4. The method according to claim 1, characterized in that Sending a restart command to the management driver includes: Send a restart command defined by the IOCTL code to the management driver.

5. The method according to claim 1, characterized in that The management driver controls the cellular communication module to restart, including: The management driver restarts the cellular communication module through the GPIO pin of the cellular communication module.

6. The method according to claim 1, characterized in that Upgrading the firmware of the cellular communication module includes: After handshaking communication with the cellular communication module, downloading the firmware of the cellular communication module into the cellular communication module; After the download is completed, the firmware burning success result and the normal status of the port of the cellular communication module are monitored.

7. The method according to any one of claims 1 to 6, characterized in that: After upgrading the firmware of the cellular communication module, the method further includes: Uninstall the management driver and clean up corresponding useless data.

8. The method according to any one of claims 1 to 6, characterized in that: Before forcibly installing the management driver to the operating system, it also includes: Re-upgrading the firmware of the cellular communication module; If the re-upgrade is successful, exit the process; If the re-upgrade fails, perform the steps to forcibly install the management driver to the operating system and the subsequent steps.

9. An abnormality recovery device, characterized in that: include: An installation module, for forcibly installing a management driver into an operating system if an abnormal firmware upgrade of the cellular communication module is detected, so that the operating system creates a device node; an execution module, configured to mount the management driver to the device node, and send a restart command to the management driver, so that the management driver controls the cellular communication module to restart; The upgrading module is used to upgrade the firmware of the cellular communication module after the cellular communication module is restarted.

10. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program to implement the method according to any one of claims 1 to 8.

11. A non-volatile storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

12. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images