Method and device for recovering firmware package of wireless communication module and electronic equipment
By obtaining the subsystem identification and firmware version number from the startup parameter partition of the wireless communication module when the target device is turned on, one-time firmware update is achieved, which solves the problems of firmware recovery time and MBIM port blockage in the existing technology, and improves wireless communication Recovery efficiency and reliability of modules.
Patent Information
- Application Number
- CN202411096710.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2024-12-06
AI Technical Summary
In the prior art, the 5G module firmware recovery requires two upgrades, which takes a long time, and the MBIM port blockage will cause the wireless communication module to be unable to recover.
When the target device is powered on, it obtains the subsystem identifier from the startup parameter partition of the wireless communication module, determines the firmware version number, and downloads the corresponding firmware package to complete a one-time firmware update, avoiding relying on the MBIM port.
Simplifies the firmware update process, improves efficiency and reliability, and avoids recovery failures caused by MBIM port blockage.
Smart Images

Figure CN119088425A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computers, and in particular to a method and device for recovering a firmware package of a wireless communication module, and an electronic device. Background Art
[0002] In order to reduce the maintenance and release of 5G module drivers, various PC (Personal Computer) manufacturers will integrate different models of 5G module firmware into the same version of the driver package for Windows Update (automatic update tool) release. After the terminal user updates the 5G module driver through Windows Update, the host-side upgrade service program will upgrade the firmware of the local module. When the module is abnormally interrupted during the firmware upgrade process, resulting in image damage or data abnormalities during normal operation and unable to boot normally, the MBIM (Mobile Broadband Interface Model, an interface standard widely used by mobile devices) port cannot be enumerated, and the PCIE Subsystem ID (subsystem identifier) cannot be read through the MBIM command to identify the module model. The host-side upgrade service program will first upgrade the module to the general firmware version. After the module is normally powered on, the MBIM command is used to query the PCIE Subsystem ID stored in the Nv (Nv Storage, volatile storage) of the module to identify the current module model, and then the firmware version corresponding to the module model is upgraded to the module for recovery. The module manufacturer will store the PCIE SubsystemID of the corresponding model in the module Nv system at the factory, save it when the power is off and keep it after upgrading, and use it later to identify the module model through the MBIM command for the host-side upgrade service program. The host-side driver will store the mapping table of the firmware version of each module model and the PCIE SubsystemID and the module firmware version, which is used to identify the firmware version of each module model. The first defect of the prior art: Firmware recovery needs to be upgraded to the general firmware version first, and then the module model is identified according to the PCIE SubsystemID, and then upgraded to the corresponding version. This process requires two firmware upgrades to complete the recovery operation, which takes a long time and is not user-friendly. Defect 2: Firmware recovery needs to rely on the MBIM port to send a command to query the PCIE SubsystemID. The MBIM port is the port for communication between Windows and the 5G module. During the communication transmission, it is frequent. If the MBIM port is blocked and the MBIM command cannot be sent, the recovery action cannot be triggered to restore the module to normal. Summary of the invention
[0003] The present application provides a method, device and electronic device for recovering a wireless communication module firmware package, so as to solve the technical problem that when an abnormal power failure or upgrade failure occurs during a firmware package upgrade, resulting in the abnormal inability to start the wireless communication module normally, two firmware upgrades need to be triggered to restore the wireless communication module to normal, which takes a long time, and if the MBIM port is blocked, the wireless communication module cannot be restored.
[0004] In the first aspect, the present application provides a method for recovering a wireless communication module firmware package, comprising: when the target device is turned on and jumps to the download agent program execution, obtaining the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module of the target device; determining the firmware version number corresponding to the subsystem identifier based on the subsystem identifier; obtaining the firmware package corresponding to the firmware version number, and downloading the firmware package to the wireless communication module, and the target device completes the startup.
[0005] In the second aspect, the present application provides a device for recovering a wireless communication module firmware package, including: a first acquisition module, used to obtain the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module of the above-mentioned target device when the target device is turned on and jumps to the download agent program execution; a determination module, used to determine the firmware version number corresponding to the above-mentioned subsystem identifier based on the above-mentioned subsystem identifier; a download module, used to obtain the firmware package corresponding to the above-mentioned firmware version number, and download the above-mentioned firmware package to the above-mentioned wireless communication module, and the above-mentioned target device completes the startup.
[0006] As an optional example, the target device is provided with the wireless communication module, the wireless communication is provided with a preset startup parameter partition, the subsystem identifier of the wireless communication module is stored in the startup parameter partition, wherein the startup parameter partition is in read-only mode.
[0007] As an optional example, the above-mentioned device also includes: a second acquisition module, which is used to obtain the new download protocol of the above-mentioned download agent program when obtaining the subsystem identifier of the above-mentioned wireless communication module from the startup parameter partition of the wireless communication module, wherein the above-mentioned new download protocol is a modified download protocol, and the above-mentioned new download protocol is used for the above-mentioned target device to obtain the above-mentioned subsystem identifier from the above-mentioned startup parameter partition and download the firmware package corresponding to the firmware version number corresponding to the above-mentioned subsystem identifier to the above-mentioned wireless communication module after the above-mentioned download agent program starts to run; a control module, which is used to control the operation of the above-mentioned download agent program according to the above-mentioned new download protocol.
[0008] As an optional example, the above-mentioned determination module includes: an acquisition unit, used to obtain a firmware package mapping table from internal storage, wherein the above-mentioned firmware package mapping table contains a firmware version number corresponding to each subsystem identifier; a processing unit, used to traverse the above-mentioned firmware package mapping table to read a mapping relationship matching the above-mentioned subsystem identifier; and a determination unit, used to determine the firmware version number corresponding to the above-mentioned subsystem identifier based on the above-mentioned mapping relationship.
[0009] As an optional example, the above subsystem identification includes a subsystem manufacturer identification and a subsystem device identification.
[0010] In a third aspect, the present application provides a storage medium storing a computer program, wherein the computer program executes the above-mentioned method for recovering the wireless communication module firmware package when executed by a processor.
[0011] In a fourth aspect, the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned method for recovering the wireless communication module firmware package through the computer program.
[0012] In an embodiment of the present application, a method is adopted in which, when the target device is turned on and jumps to the download agent program running, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module of the target device; the firmware version number corresponding to the subsystem identifier is determined according to the subsystem identifier; the firmware package corresponding to the firmware version number is obtained, and the firmware package is downloaded to the wireless communication module, and the target device completes the startup. Since in the above method, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module by downloading to identify the module model, only one firmware upgrade is required, and the MBIM port is not relied on, thereby simplifying the firmware update process and making the process more efficient and reliable, thereby solving the technical problem that when the wireless communication module cannot be started normally due to abnormal power failure or upgrade failure during the firmware package upgrade process, it is necessary to trigger two firmware upgrades to restore the wireless communication module to normal, which takes a long time, and if the MBIM port is blocked, the wireless communication module cannot be restored. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0014] 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0015] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0016] Figure 1 is a flowchart of an optional method for restoring a wireless communication module firmware package according to an embodiment of the present application;
[0017] Figure 2 It is a firmware data partition structure diagram of a wireless communication module according to an optional method for recovering a wireless communication module firmware package according to an embodiment of the present application;
[0018] Figure 3 is a specific implementation flow chart of an optional method for restoring a wireless communication module firmware package according to an embodiment of the present application;
[0019] Figure 4 is a structural schematic diagram of an optional wireless communication module firmware package recovery device according to an embodiment of the present application;
[0020] Figure 5 is a schematic diagram of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0021] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.
[0022] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.
[0023] According to a first aspect of an embodiment of the present application, a method for recovering a wireless communication module firmware package is provided. Optionally, as follows: Figure 1 As shown, the above method includes:
[0024] S102, when the target device is powered on and jumps to the download agent program execution, obtaining a subsystem identifier of the wireless communication module from a startup parameter partition of the wireless communication module of the target device;
[0025] S104, determining a firmware version number corresponding to the subsystem identifier according to the subsystem identifier;
[0026] S106, obtaining a firmware package corresponding to the firmware version number, and downloading the firmware package to the wireless communication module, and the target device completes booting.
[0027] Optionally, in this embodiment, the download agent refers to the process of downloading the firmware package. When the firmware package needs to be updated, the system will switch to a program specifically responsible for processing the firmware package download, that is, the download agent. This program is responsible for managing the various steps of firmware download, including communicating with the module, verifying the firmware, and performing firmware updates. The wireless communication module can be a 5G module. Subsystem identification, PCIE Subsystem ID, is an identifier on a PCIE (Peripheral Component Interconnect Express, Peripheral Component Interconnect Extension) device. PCIE is a computer bus standard for connecting various peripheral devices, such as graphics cards, network cards, storage controllers, etc. to the central processing unit (CPU) and memory on the motherboard. PCIE devices usually contain a unique Subystem ID, which is used to identify the manufacturer and model of the device and other information. Subsystem ID is a parameter on the PCIE device and can be found in the configuration space of the device. This ID is usually assigned by the device manufacturer so that the operating system or other software can identify the device and provide corresponding drivers or support.
[0028] Optionally, in this embodiment, a data partition boot parameter partition bootpara is divided in the NAND Flash partition of the wireless communication module, which is independent of the firmware partition, and is used to store the subsystem identifier PCIE Subsystem ID. When the download agent on the host side is ready to download the firmware, it will first read the subsystem identifier PCIE Subsystem ID stored in the factory of the wireless communication module from the NAND Flash partition of the wireless communication module, and then according to the subsystem identifier PCIE Subsystem ID obtained in the previous step, the system will search for the corresponding firmware version number, and the download agent will download the corresponding firmware package from the firmware warehouse or server according to the firmware version number determined in the previous step. After downloading and installing the firmware, the wireless communication module completes the boot process.
[0029] Optionally, in this embodiment, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module by downloading to identify the module model, and the firmware only needs to be upgraded once, and the MBIM port is not relied on, thereby simplifying the firmware update process and making the process more efficient and reliable. This solves the problem that when the wireless communication module cannot be started normally due to abnormal power failure or upgrade failure during the firmware package upgrade process, it is necessary to trigger two firmware upgrades to restore the wireless communication module to normal, which takes a long time, and if the MBIM port is blocked, the wireless communication module cannot be restored.
[0030] As an optional example, the target device is provided with a wireless communication module, a preset startup parameter partition is provided in the wireless communication, a subsystem identifier of the wireless communication module is stored in the startup parameter partition, wherein the startup parameter partition is in read-only mode.
[0031] Optionally, in this embodiment, the wireless communication module is an independent hardware device, which has its own storage space for storing configuration information, firmware, etc. A new partition is added to the NAND Flash partition of the wireless communication module to store boot parameters, that is, the boot parameter partition bootpara. Before the wireless communication module leaves the factory, the subsystem identifier PCIE Subsystem ID of the wireless communication module will be stored in the newly created boot parameter partition bootpara. In order to ensure that the information stored in the boot parameter partition bootpara is not accidentally modified, the boot parameter partition bootpara is set to read-only mode. This means that under normal circumstances, the system can only read the contents of the boot parameter partition bootpara, but cannot write or modify it, thereby protecting the important information stored in the partition from accidental damage or tampering.
[0032] As an optional example, when obtaining the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module, the above method further includes:
[0033] Obtaining a new download protocol of the download agent program, wherein the new download protocol is a modified download protocol, and the new download protocol is used for the target device to obtain a subsystem identifier from a startup parameter partition and download a firmware package corresponding to a firmware version number corresponding to the subsystem identifier to a wireless communication module after the download agent program starts running;
[0034] Control the download agent program running according to the new download protocol.
[0035] Optionally, in this embodiment, before the host side is powered on, the download protocol of the download agent program of the device is modified so that after the host side is powered on and the download agent program starts running, the download agent program obtains the subsystem identifier from the startup parameter partition and downloads the firmware package corresponding to the firmware version number corresponding to the subsystem identifier to the wireless communication module, thereby completing the firmware update.
[0036] As an optional example, determining the firmware version number corresponding to the subsystem identifier according to the subsystem identifier includes:
[0037] Obtain a firmware package mapping table from the internal storage, wherein the firmware package mapping table includes a firmware version number corresponding to each subsystem identifier;
[0038] Traverse the firmware package mapping table to read the mapping relationship that matches the subsystem identifier;
[0039] Determine the firmware version number corresponding to the subsystem identifier according to the mapping relationship.
[0040] Optionally, in this embodiment, the host side will maintain a mapping table of subsystem identifier PCIE Subsystem ID and module firmware version number. The function of this mapping table is to map each subsystem identifier PCIE Subsystem ID to the corresponding firmware version number, so as to determine which firmware version should be upgraded to the current module. When determining the firmware version number corresponding to the subsystem identifier based on the subsystem identifier, first, the download agent program will obtain the firmware package mapping table from the internal storage of the device or system. The download agent program will check the entries in the firmware package mapping table one by one, in order to find a mapping relationship that matches the subsystem identifier PCIE Subsystem ID being checked. When the program finds a matching mapping relationship, it reads this relationship. Finally, the download agent program determines the firmware version number corresponding to the subsystem identifier PCIE Subsystem ID based on the read mapping relationship.
[0041] As an optional example, the subsystem identifier includes a subsystem manufacturer identifier and a subsystem device identifier.
[0042] Optionally, in this embodiment, the subsystem identifier PCIE Subsystem ID includes a subsystem manufacturer identifier PCIE Subsystem vendor ID and a subsystem device identifier PCIE Subsystem device ID.
[0043] With reference to an example for illustration, the present application provides a firmware recovery solution for identifying the model of a wireless communication module by obtaining a subsystem identifier PCI Subsystem ID based on downloading. When the firmware upgrade is abnormally interrupted or a data abnormality occurs during normal operation and the device cannot be started normally, the module firmware of the corresponding model can be restored by upgrading the firmware once. This solution is used to solve the problem that the recovery process takes a long time and the wireless communication module cannot be restored to normal when MBIM communication is abnormal.
[0044] like Figure 2 The firmware data partition structure diagram of the wireless communication module shown in the figure shows that a data partition boot parameter partition bootpara is divided in the NAND Flash partition of the wireless communication module, which is independent of the firmware partition, and is used to store the subsystem identifier PCIE Subsystem ID. The module manufacturer writes the PCIE Subsystem ID of each module model into the data partition before the module leaves the factory, and the partition is a read-only data partition after leaving the factory.
[0045] like Figure 3 The specific implementation flow chart shown in the figure modifies the module firmware download protocol. During the firmware download process, the PCIE Subsystem ID check process is added. First, the subsystem identifier PCIE Subsystem ID is obtained from the boot parameter partition bootpara through the firmware upgrade port, and the corresponding firmware version of each module model is found through the associated mapping table, and then the corresponding firmware download module is restored. Only one firmware upgrade is required, and it does not rely on the MBIM port, which can solve the problem that the module cannot be restored to normal due to MBIM port abnormality.
[0046] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0047] According to another aspect of the embodiment of the present application, a device for recovering a wireless communication module firmware package is also provided. Figure 4 As shown, including:
[0048] The first acquisition module 402 is used to acquire the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module of the target device when the target device is powered on and jumps to the download agent program runtime;
[0049] A determination module 404 is used to determine a firmware version number corresponding to the subsystem identifier according to the subsystem identifier;
[0050] The download module 406 is used to obtain a firmware package corresponding to the firmware version number and download the firmware package to the wireless communication module, so that the target device completes booting.
[0051] Optionally, in this embodiment, the download agent refers to the process of downloading the firmware package. When the firmware package needs to be updated, the system will switch to a program specifically responsible for processing the firmware package download, that is, the download agent. This program is responsible for managing the various steps of firmware download, including communicating with the module, verifying the firmware, and performing firmware updates. The wireless communication module can be a 5G module. Subsystem identification, PCIE Subsystem ID, is an identifier on a PCIE (Peripheral Component Interconnect Express, Peripheral Component Interconnect Extension) device. PCIE is a computer bus standard for connecting various peripheral devices, such as graphics cards, network cards, storage controllers, etc. to the central processing unit (CPU) and memory on the motherboard. PCIE devices usually contain a unique Subystem ID, which is used to identify the manufacturer and model of the device and other information. Subsystem ID is a parameter on the PCIE device and can be found in the configuration space of the device. This ID is usually assigned by the device manufacturer so that the operating system or other software can identify the device and provide corresponding drivers or support.
[0052] Optionally, in this embodiment, a data partition boot parameter partition bootpara is divided in the NAND Flash partition of the wireless communication module, which is independent of the firmware partition, and is used to store the subsystem identifier PCIE Subsystem ID. When the download agent on the host side is ready to download the firmware, it will first read the subsystem identifier PCIE Subsystem ID stored in the factory of the wireless communication module from the NAND Flash partition of the wireless communication module, and then according to the subsystem identifier PCIE Subsystem ID obtained in the previous step, the system will search for the corresponding firmware version number, and the download agent will download the corresponding firmware package from the firmware warehouse or server according to the firmware version number determined in the previous step. After downloading and installing the firmware, the wireless communication module completes the boot process.
[0053] Optionally, in this embodiment, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module by downloading to identify the module model, and the firmware only needs to be upgraded once, and the MBIM port is not relied on, thereby simplifying the firmware update process and making the process more efficient and reliable. This solves the problem that when the wireless communication module cannot be started normally due to abnormal power failure or upgrade failure during the firmware package upgrade process, it is necessary to trigger two firmware upgrades to restore the wireless communication module to normal, which takes a long time, and if the MBIM port is blocked, the wireless communication module cannot be restored.
[0054] As an optional example, the target device is provided with a wireless communication module, a preset startup parameter partition is provided in the wireless communication, a subsystem identifier of the wireless communication module is stored in the startup parameter partition, wherein the startup parameter partition is in read-only mode.
[0055] Optionally, in this embodiment, the wireless communication module is an independent hardware device, which has its own storage space for storing configuration information, firmware, etc. A new partition is added to the NAND Flash partition of the wireless communication module to store boot parameters, that is, the boot parameter partition bootpara. Before the wireless communication module leaves the factory, the subsystem identifier PCIE Subsystem ID of the wireless communication module will be stored in the newly created boot parameter partition bootpara. In order to ensure that the information stored in the boot parameter partition bootpara is not accidentally modified, the boot parameter partition bootpara is set to read-only mode. This means that under normal circumstances, the system can only read the contents of the boot parameter partition bootpara, but cannot write or modify it, thereby protecting the important information stored in the partition from accidental damage or tampering.
[0056] As an optional example, the above device further includes:
[0057] A second acquisition module is used to acquire a new download protocol for the download agent program when acquiring the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module, wherein the new download protocol is a modified download protocol, and the new download protocol is used for the target device to acquire the subsystem identifier from the startup parameter partition and download the firmware package corresponding to the firmware version number corresponding to the subsystem identifier to the wireless communication module after the download agent program starts to run;
[0058] The control module is used to control the running of the download agent program according to the new download protocol.
[0059] Optionally, in this embodiment, before the host side is powered on, the download protocol of the download agent program of the device is modified so that after the host side is powered on and the download agent program starts running, the download agent program obtains the subsystem identifier from the startup parameter partition and downloads the firmware package corresponding to the firmware version number corresponding to the subsystem identifier to the wireless communication module, thereby completing the firmware update.
[0060] As an optional example, the determination module includes:
[0061] An acquisition unit, used to acquire a firmware package mapping table from an internal storage, wherein the firmware package mapping table includes a firmware version number corresponding to each subsystem identifier;
[0062] A processing unit, used to traverse the firmware package mapping table to read a mapping relationship matching the subsystem identifier;
[0063] The determination unit is used to determine the firmware version number corresponding to the subsystem identifier according to the mapping relationship.
[0064] Optionally, in this embodiment, the host side will maintain a mapping table of subsystem identifier PCIE Subsystem ID and module firmware version number. The function of this mapping table is to map each subsystem identifier PCIE Subsystem ID to the corresponding firmware version number, so as to determine which firmware version should be upgraded to the current module. When determining the firmware version number corresponding to the subsystem identifier based on the subsystem identifier, first, the download agent program will obtain the firmware package mapping table from the internal storage of the device or system. The download agent program will check the entries in the firmware package mapping table one by one, in order to find a mapping relationship that matches the subsystem identifier PCIE Subsystem ID being checked. When the program finds a matching mapping relationship, it reads this relationship. Finally, the download agent program determines the firmware version number corresponding to the subsystem identifier PCIE Subsystem ID based on the read mapping relationship.
[0065] As an optional example, the subsystem identifier includes a subsystem manufacturer identifier and a subsystem device identifier.
[0066] Optionally, in this embodiment, the subsystem identifier PCIE Subsystem ID includes a subsystem manufacturer identifier PCIE Subsystem vendor ID and a subsystem device identifier PCIE Subsystem device ID.
[0067] For other examples of this embodiment, please refer to the above examples and will not be repeated here.
[0068] Figure 5 is a schematic diagram of an optional electronic device according to an embodiment of the present application, such as Figure 5 As shown, it includes a processor 502, a communication interface 504, a memory 506 and a communication bus 508, wherein the processor 502, the communication interface 504 and the memory 506 communicate with each other through the communication bus 508, wherein,
[0069] Memory 506, used for storing computer programs;
[0070] The processor 502 is used to execute the computer program stored in the memory 506 to implement the following steps:
[0071] When the target device is powered on and jumps to the download agent program running, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module of the target device;
[0072] Determine the firmware version number corresponding to the subsystem identifier according to the subsystem identifier;
[0073] Obtain the firmware package corresponding to the firmware version number, and download the firmware package to the wireless communication module, and the target device completes booting.
[0074] Optionally, in this embodiment, the communication bus may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The communication interface is used for communication between the above electronic device and other devices.
[0075] The memory may include RAM, or may include non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.
[0076] As an example, the memory 506 may include, but is not limited to, the first acquisition module 402, the determination module 404, and the download module 406 in the recovery device of the wireless communication module firmware package. In addition, it may also include, but is not limited to, other module units in the recovery device of the wireless communication module firmware package, which will not be repeated in this example.
[0077] The above-mentioned processor can be a general-purpose processor, which can include but not be limited to: CPU (Central Processing Unit), NP (Network Processor), etc.; it can also be DSP (Digital Signal Processing), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
[0078] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.
[0079] The electronic device provided in the embodiment of the present application may specifically be a module capable of realizing a communication function or a terminal device including the module, etc. The terminal device may be a mobile terminal or a smart terminal. The mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a laptop computer, etc.; the smart terminal may specifically be a terminal including a wireless communication module such as a smart car, a smart watch, a shared bicycle, a smart cabinet, etc.; the module may specifically be a wireless communication module, such as any one of a 2G communication module, a 3G communication module, a 4G communication module, a 5G communication module, and a NB-IOT communication module.
[0080] It can be understood by those skilled in the art that Figure 5 The structure shown is for illustration only. The device for implementing the above-mentioned method for recovering the wireless communication module firmware package may be a terminal device, which may be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, and other terminal devices. Figure 5 The structure of the electronic device is not limited. For example, the electronic device may also include Figure 5 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 5 Different configurations shown.
[0081] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, which can include: a flash drive, ROM, RAM, a magnetic disk or an optical disk, etc.
[0082] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program executes the steps in the above-mentioned method for recovering the wireless communication module firmware package when executed by a processor.
[0083] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.
[0084] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0085] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
[0086] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.
[0087] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
[0088] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0089] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0090] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A method for recovering a wireless communication module firmware package, characterized in that: include: When the target device is powered on and jumps to the running state of the download agent program, the subsystem identifier of the wireless communication module is obtained from the startup parameter partition of the wireless communication module of the target device; Determine the firmware version number corresponding to the subsystem identifier according to the subsystem identifier; A firmware package corresponding to the firmware version number is obtained, and the firmware package is downloaded to the wireless communication module, and the target device completes booting.
2. The method according to claim 1, characterized in that The target device is provided with the wireless communication module, the wireless communication is provided with a preset startup parameter partition, the subsystem identification of the wireless communication module is stored in the startup parameter partition, wherein the startup parameter partition is in read-only mode.
3. The method according to claim 1, characterized in that When obtaining the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module, the method further includes: Obtaining a new download protocol of the download agent program, wherein the new download protocol is a modified download protocol, and the new download protocol is used for the target device to obtain the subsystem identifier from the startup parameter partition and download a firmware package corresponding to the firmware version number corresponding to the subsystem identifier to the wireless communication module after the download agent program starts running; The download agent program is controlled to run according to the new download protocol.
4. The method according to claim 1, characterized in that: Determining the firmware version number corresponding to the subsystem identifier according to the subsystem identifier includes: Obtaining a firmware package mapping table from internal storage, wherein the firmware package mapping table includes a firmware version number corresponding to each subsystem identifier; Traversing the firmware package mapping table to read a mapping relationship matching the subsystem identifier; The firmware version number corresponding to the subsystem identifier is determined according to the mapping relationship.
5. The method according to claim 1, characterized in that The subsystem identification includes a subsystem manufacturer identification and a subsystem device identification.
6. A device for recovering a wireless communication module firmware package, characterized in that: include: A first acquisition module is used to acquire the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module of the target device when the target device is powered on and jumps to the download agent program execution; A determination module, configured to determine a firmware version number corresponding to the subsystem identifier according to the subsystem identifier; The download module is used to obtain the firmware package corresponding to the firmware version number, and download the firmware package to the wireless communication module, so that the target device completes the startup.
7. The device according to claim 6, characterized in that The target device is provided with the wireless communication module, the wireless communication is provided with a preset startup parameter partition, the subsystem identification of the wireless communication module is stored in the startup parameter partition, wherein the startup parameter partition is in read-only mode.
8. The device according to claim 1, characterized in that The device also includes: a second acquisition module, configured to acquire a new download protocol of the download agent program when acquiring the subsystem identifier of the wireless communication module from the startup parameter partition of the wireless communication module, wherein the new download protocol is a modified download protocol, and the new download protocol is used for the target device to acquire the subsystem identifier from the startup parameter partition and download a firmware package corresponding to the firmware version number corresponding to the subsystem identifier to the wireless communication module after the download agent program starts to run; The control module is used to control the running of the download agent program according to the new download protocol.
9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is executed.
10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 5 through the computer program.
