Communication module maintenance method, electronic equipment and storage medium

Abstract

The invention provides a maintenance method of a communication module, electronic equipment and a storage medium. The communication module is a 5G RedCap OPEN module, and the method comprises the steps that when the communication module is flashed, if current flashing is not first flashing, whether a private key in a current firmware package is matched with a public key in the communication module or not is judged, and the current firmware package is a firmware package used by current flashing; when the private key is matched with the public key, flashing the communication module by using the current firmware package; wherein the new firmware obtained by flashing each time is stored in the startup partition of the communication module. According to the method, the security of the communication module can be effectively improved, the user experience is improved, the benefits of module manufacturers are maintained, the after-sales cost and material waste are reduced, and the environmental burden is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of communication modules, and more particularly to a maintenance method for a communication module, an electronic device, and a storage medium. Background Art

[0002] The 5G RedCap OPEN module, also known as OpenCPU, is an application method with the module as the main processor. With the development of 5G RedCap communication module technology and the continuous changes in the market, more and more users have recognized the advantages of the OpenCPU solution. In particular, it simplifies the development process of wireless communication products for users, streamlines the hardware structure design, and essentially, through open-source structure code and personalized customization services, enables traditional modules to play the role of the main controller, and supports the allocation of redundant threads and resources to the user's code for self-logic development, thus no longer requiring an additional MCU as the main controller, greatly saving costs in both software and hardware, and making it highly favored by industry users.

[0003] In the related art, the security of the firmware running environment of the 5G RedCap OPEN module is relatively low, and there is a lack of an anti-flashing mechanism, resulting in the firmware being easily damaged by improper technical operations or accidental flashing, affecting the use of users.

[0004] In view of this, the present invention is specifically proposed. Summary of the Invention

[0005] In consideration of the above problems, the present invention is proposed. According to one aspect of the present invention, a maintenance method for a communication module is provided. The communication module is a 5G RedCap OPEN module, and the method includes: When flashing the communication module, If the current flashing is not the first flashing, determine whether the private key in the current firmware package matches the public key in the communication module. The current firmware package is the firmware package used for the current flashing; When the private key matches the public key, use the current firmware package to flash the communication module; Wherein, the new firmware obtained from each flashing is stored in the startup partition of the communication module.

[0006] Exemplarily, the method further includes: When the private key does not match the public key, generate a prompt message.

[0007] Exemplarily, the method further includes: If the current flashing is the first flashing, write the public key into the system partition of the communication module; Use the current firmware package to flash the communication module.

[0008] Exemplarily, when the current flashing is the first flashing, after the flashing is completed, the method further includes: Performing a restart detection operation; The restart detection operation includes: After the flashing is completed, restart the communication module; If no abnormality occurs during the restart of the communication module, set the flag file in the startup partition to a preset value before the communication module finishes booting; Preferably, the restart detection operation is performed after each flashing is completed.

[0009] Exemplarily, before determining whether the private key in the current firmware package matches the public key in the communication module, the method further includes: Determining whether the flag file is a preset value; Wherein, the step of determining whether the private key in the current firmware package matches the public key in the communication module is performed when the flag file is a preset value.

[0010] Exemplarily, the method further includes: When the flag file is not a preset value, write the public key in the current firmware package into the system partition of the communication module, and flash the communication module using the current firmware package.

[0011] Exemplarily, the method further includes: When updating the user application in the communication module, Determining whether the private key attached to the update package of the user application matches the public key; When the private key attached to the update package matches the public key, upgrade the user application using the update package.

[0012] Exemplarily, before updating the user application in the communication module, the method further includes: Signing the update package to attach the private key to the update package.

[0013] According to another aspect of the present invention, there is provided an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and the processor is configured to execute the computer program to implement the method as described above.

[0014] According to still another aspect of the present invention, there is provided a computer-readable storage medium storing computer programs / instructions, and when the computer programs / instructions are executed by a processor, the method as described above is implemented.

[0015] In the above technical solution, before flashing the firmware, the firmware package is securely verified using a public key and a private key. When the flashing is completed, the new firmware obtained from the flashing is stored in the boot partition of the communication module. This method can reduce the module being scrapped or bricked due to improper technical operations or accidental flashing, prevent criminals from damaging the firmware of the communication module through technical means and the firmware from being repackaged and stolen. Thus, it can effectively improve the security of the communication module, enhance the user experience, safeguard the interests of the module manufacturers, and help reduce after-sales costs and material waste, as well as reduce the environmental burden.

[0016] The above description is only an overview of the technical solution of the present invention. In order to be able to more clearly understand the technical means of the present invention, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable, the following specifically illustrates the specific embodiments of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] By describing the embodiments of the present invention in more detail in conjunction with the accompanying drawings, the above and other purposes, features and advantages of the present invention will become more obvious. The drawings are used to provide a further understanding of the embodiments of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation to the present invention. In the drawings, the same reference numerals generally represent the same components or steps.

[0018] Figure 1 A schematic flowchart showing a maintenance method of a communication module according to an embodiment of the present invention; Figure 2 A schematic flowchart showing the technical principle of a communication module according to an embodiment of the present invention; Figure 3 A schematic diagram showing the partition structure of a 5G RedCap OPEN module according to an embodiment of the present invention; Figure 4 A schematic diagram showing a flashing process according to an embodiment of the present invention; Figure 5 A schematic diagram showing an upgrade process according to an embodiment of the present invention; Figure 6 A schematic block diagram showing an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] To make the objectives, technical solutions, and advantages of the present invention more apparent, exemplary embodiments according to the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all embodiments of the present invention. It should be understood that the present invention is not limited by the exemplary embodiments described herein. Based on the embodiments of the present invention described herein, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present invention.

[0020] With the rapid rise of 5G RedCap OPEN modules in the market, security and after-sales issues have become increasingly prominent. These issues not only damage the user experience and cause losses to users, but also seriously affect the reputation of 5G RedCap OPEN module manufacturers, thereby damaging their interests. Specifically, currently, most 5G RedCap OPEN module manufacturers in the market have insufficient understanding of anti-flashing and secure boot, resulting in a relatively low overall security level of the market environment in which 5G RedCap OPEN modules operate. The technical levels of personnel in the technical field vary, and improper technical operations or accidental flashing are likely to cause damage to 5G RedCap OPEN modules. In addition, criminals may use technical means to damage the original firmware or apps of 5G RedCap OPEN modules, causing losses to the normal use of users. Moreover, the frequent damage of 5G RedCap OPEN modules brings about a great waste of hardware and materials, and also causes an environmental burden. Therefore, finding a method that can protect the security of the basic operating environment of 5G RedCap OPEN modules to reduce after-sales costs and human damage has become an urgent problem to be solved in the industry. In view of this, the present invention provides a maintenance method, an electronic device, and a storage medium for a communication module. This maintenance method can effectively improve the environmental security during the maintenance of the communication module, thereby effectively avoiding damage to the firmware in the communication module caused by misoperations or illegal technical means. This helps to improve the user experience and also helps to reduce after-sales costs and material waste. The maintenance method, electronic device, and storage medium will be described in detail below.

[0021] According to one aspect of the embodiments of the present invention, a maintenance method for a communication module is provided. In this article, the communication module is a 5G RedCap OPEN module. The application scope of this communication module includes, but is not limited to, communication modules on new energy vehicles, smart meters, power collectors, and power concentrators.

[0022] Figure 1 A schematic flowchart showing a maintenance method for a communication module according to an embodiment of the present invention is shown. As Figure 1 shown, the method may include the following steps S110 and step S120.

[0023] In step S110, when the communication module is flashed, if the current flashing is not the first flashing, it is determined whether the private key in the current firmware package matches the public key in the communication module, and the current firmware package is the firmware package used for the current flashing.

[0024] Flashing is a common maintenance method for communication modules. By flashing, the firmware in the communication module can be updated to improve the performance of the communication module and improve the system stability and security of the communication module. In terms of software functions, the manufacturer of the 5G RedCapOPEN module generally opens a set of OpenCPU SDK, which includes compilation methods and burning tools. The firmware package in this article can be the system firmware or SDK compiled using the compilation method provided by the manufacturer. Figure 2 The following is a flow chart showing the technical principle of a communication module according to an embodiment of the present invention. Figure 2 In the illustrated embodiment, the 5G RedCap OPEN module includes an OPEN module system firmware layer and an OPEN API interface layer. The 5G RedCap OPEN module allows users to independently develop an APP layer using the open OpenCPU SDK, and store the developed APP layer in the application layer. Thus, the application program (i.e., user application program) developed by the user as needed can be stored in the partition with the firmware package.

[0025] In this article, the public key and private key can be generated using an algorithm provided by the manufacturer, or can be generated using any existing or future developed key generation algorithm, and the present invention does not limit this. After generating the public key and the matching private key, the public key can be saved in the communication module, and the private key can be compiled simultaneously with the firmware package when compiling the firmware package, so as to facilitate security monitoring of the firmware package. In actual scenarios, the private key matching the public key can be saved by the manufacturer, and the manufacturer can provide a new firmware package for flashing the communication module according to the customer or actual needs. The specific method for determining whether the public key and the private key match includes but is not limited to verifying the matching through conventional verification processes such as encryption and decryption or signing and verification, which will not be repeated.

[0026] In step S120, when the private key matches the public key, the communication module is flashed using the current firmware package; wherein the new firmware obtained each time by flashing is stored in the boot partition of the communication module.

[0027] When the public key and private key match, it indicates that the current firmware package is a relatively safe firmware package provided by the manufacturer or an authorized party authorized by the manufacturer. In this way, improper technical operations, wrong flashing, or illegal elements destroying the firmware of the communication module through technical means can be avoided.

[0028] In this example, the new firmware obtained each time of flashing is stored in the boot partition of the communication module, and this system partition is the BOOT partition of the 5G RedCap OPEN module. Figure 3 Figure showing the partition structure of the 5G RedCap OPEN module according to an embodiment of the present invention. As Figure 3 shown, the partitions of the 5G RedCap OPEN module include the OPEN module system main partition and the DATA partition. The OPEN module system main partition includes the system partition SYSTEM and the boot partition BOOT. In the solution of this example, the firmware is located in the BOOT. This boot partition has the characteristic of being tamper-proof. Storing the firmware in the boot partition can prevent criminals from attacking the firmware.

[0029] In the solution of this example, when the public key and the private key match, the boot boot process of flashing can continue to perform flashing. Those skilled in the art can understand the specific process of flashing and upgrading the communication module, which will not be elaborated.

[0030] In the solution of this embodiment, by implementing digital signatures of asymmetric encryption algorithms such as RSA / ECC on the firmware package, the integrity and source credibility of the firmware are ensured. The validity of the signature needs to be verified before flashing. In this case, the private key of the firmware package has a dynamic matching relationship with the private key in the communication module. And this private key and public key are usually generated by the manufacturer and the chip manufacturer and are unique. In this case, even if a thief steals the firmware in a certain communication module, since the private key in this firmware may not match the public key in other communication modules, it cannot be stolen and run on other devices. In some embodiments, symmetric encryption algorithms such as AES can be used simultaneously to protect the firmware file in storage to further improve security. In some embodiments, the firmware package can also be deeply bound to the unique hardware identification code of the device (i.e., the communication module) (such as the module IMEI, SN). Each time of flashing, the dynamic matching relationship between the hardware identification code and the firmware encryption parameters needs to be verified to implement the "one device, one firmware" mechanism. This identification code is unique, jointly generated by the manufacturer and the chip manufacturer, and has a verification function and cannot be forged. Then the thief cannot copy this physical characteristic, and even if the firmware is obtained, it cannot be stolen and run on other devices. Thus, the security of the firmware can be further improved.

[0031] In the above technical solution, before flashing the firmware, the firmware package is securely verified using a public key and a private key. When the flashing is completed, the new firmware obtained from the flashing is stored in the boot partition of the communication module. This method can reduce the module from being scrapped and becoming bricked due to improper technical operations or accidental flashing, prevent criminals from damaging the firmware of the communication module through technical means and stealing the firmware by repackaging it. Therefore, it can effectively improve the security of the communication module, enhance the user experience, safeguard the interests of module manufacturers, and help reduce after-sales costs and material waste, as well as reduce the environmental burden.

[0032] Exemplarily, the method further includes: generating a prompt message when the private key does not match the public key.

[0033] When the public key and the private key do not match, the current firmware package may not be the one provided by the manufacturer or the authorized party. In this case, the entry into the flashing boot process can be rejected and a prompt message can be generated.

[0034] In this example, the prompt message can be displayed in a graphical and textual manner, or output using light prompts, voice prompts, etc. For example, an error message can be returned on the flashing download interface.

[0035] By outputting the prompt message in the above technical solution, users can be timely reminded to check and confirm the current firmware package, which helps to ensure the flashing efficiency.

[0036] Exemplarily, the method further includes: if the current flashing is the first flashing, writing the public key into the system partition of the communication module; flashing the communication module using the current firmware package.

[0037] It can be understood that the first flashing of the communication module is generally completed before leaving the factory to ensure normal use when delivered to users. Therefore, the firmware package used for the first flashing is relatively reliable and can be used for flashing without verification. Specifically, the flashing tool is generally provided by the module or chip manufacturer. If it is detected that it is the first flashing, the public key can be directly written into the system partition of the module through the flashing tool. In an actual scenario, this step is generally factory flashing, which is performed before the module leaves the factory and generally does not require the user to execute this factory flashing.

[0038] By writing the public key into the system partition of the communication module during the first flashing in the above solution, it helps to provide an accurate basis for security detection during subsequent flashing or user application updates, thus helping to ensure the system stability of the communication module. And writing the public key into the non-tamperable system partition can prevent the public key from being tampered with and ensure the security of the communication module.

[0039] In the above example, the public key is written during the first firmware flashing. In an implementation not shown in this article, the public key can also be written in other ways before firmware flashing, and this article does not limit this.

[0040] Exemplarily, when the current firmware flashing is the first one, after the firmware flashing is completed, the method further includes: performing a restart detection operation; the restart detection operation includes: after the firmware flashing is completed, restarting the communication module; if no exception occurs during the restart process of the communication module, then before the communication module finishes booting, setting the flag file in the boot partition to a preset value.

[0041] In the solution of this example, when there is no exception during the restart after firmware flashing, before the booting is completed, the flag file in the boot partition is set to a preset value. The size of this preset value can be selected according to actual needs, for example, it can be 1.

[0042] In the solution of this example, the public key is written first during the first firmware flashing, and the flag file is set to a preset value after the first firmware flashing. This flag file is a file in the boot partition used to record whether it is signed or not. In this example, the value of this flag file can be used to indicate whether the public key is stored in the current communication module. Thus, during subsequent firmware flashing processes, meaningless executions of steps can be avoided.

[0043] The above technical solution performs a restart detection after the first firmware flashing is completed, which can verify whether the communication module can be used normally after firmware flashing and ensure the stability of the system. At the same time, setting the flag file to a preset value after the firmware flashing is completed can be used to judge whether the public key is stored in the communication module during subsequent firmware flashing processes, which helps to avoid meaningless executions of steps.

[0044] Exemplarily, the restart detection operation is performed after each firmware flashing is completed. In the solution of this example, after each firmware flashing is completed, a restart detection operation is performed, which helps to ensure the stability of the system after each firmware flashing. At the same time, resetting the value of the flag file after each firmware flashing can prevent the value of the flag file from changing due to unknown exceptions and ensure the correctness of the system state, thereby ensuring the reliable execution of subsequent steps.

[0045] Exemplarily, before judging whether the private key in the current firmware package matches the public key in the communication module, the method further includes: judging whether the flag file is a preset value; among them, the step of judging whether the private key in the current firmware package matches the public key in the communication module is executed when the flag file is a preset value.

[0046] In the solution of this example, when flashing the firmware again, first judge whether the flag file is a preset value, that is, whether it is in a signed state. In this way, it can be judged whether the public key is stored in the communication module, thereby avoiding meaningless executions of subsequent steps and improving the firmware flashing efficiency.

[0047] Exemplarily, the method further includes: when the flag file is not the preset value, writing the public key in the current firmware package into the communication module, and flashing the communication module with the current firmware package.

[0048] As described above, the value of the flag file can be used to indicate whether the public key is stored in the current communication module. In the solution of this example, when the flag file is not the preset value, the public key in the current firmware package is written into the system partition of the communication module. This can ensure that during the subsequent flashing process, the public key can be used for security verification, thereby improving the security of flashing.

[0049] Figure 4 Shows a schematic diagram of the flashing process according to an embodiment of the present invention. As Figure 4 shown, the flashing process includes the following steps S410, S420, S430, S440, S450, and S460.

[0050] Step S410, when flashing again, determine whether the anti-flashing flag bit (i.e., the flag file) is 1. If the result is yes, execute step S420, otherwise, execute step S430.

[0051] In step S420, read the public key file in the system partition and match it with the private key in the current firmware package. If the public key and the private key match, execute step S440, otherwise, execute step S450.

[0052] In step S430, write the public key in the firmware package into the system partition of the communication module, and execute step S440 after the writing is completed.

[0053] In step S440, enter the boot boot process of flashing to complete the flashing. After the flashing is completed, execute step S460.

[0054] In step S450, reject entering the flashing process and return an error prompt at the same time.

[0055] In step S460, if there is no abnormality during restart, before power-on, set the flag file in the startup partition to 1, and then power on normally.

[0056] Exemplarily, the method further includes: when updating the user application program in the communication module, determine whether the private key attached to the update package of the user application program matches the public key; when the private key attached to the update package matches the public key, upgrade the user application program with the update package.

[0057] In the solution of this example, when the user only needs to upgrade the user application in the communication module and does not want to repeat the flashing process, the user application can be directly upgraded using the update package attached with the private key. In a specific embodiment, the built-in local upgrade API interface of the 5G RedCap OPEN module can be called for local upgrade. Before the upgrade, first verify whether the private key attached to the update package of the user application matches the public key in the 5G RedCap OPEN module. If they match, enter the local upgrade process, automatically restart and complete the upgrade. If they do not match, reject entering the local upgrade process. In some embodiments, when they do not match, an error prompt message can be output (for easy distinction, the prompt message output when the private key and public key of the firmware package do not match in the above text can be called the first prompt message, and the prompt message in this paragraph can be called the second prompt message).

[0058] During the research on the 5G RedCap OPEN module, the inventors also found that: for the app user self-built part of the 5G RedCap OPEN module (that is, the application developed by the user according to needs, that is, the user application), there is currently a lack of a secure and effective independent upgrade method, and incorrect upgrades may also cause the 5G RedCap OPEN module to be unusable. The above technical solution can ensure the integrity and authenticity of the update package by verifying the matching of the private key on the update package and the public key in the communication module, preventing malicious software or tampered software from being installed into the system, which helps to ensure the independent, secure, and accurate upgrade of the user application.

[0059] Exemplarily, before updating the user application in the communication module, the method further includes: signing the update package to attach the private key to the update package.

[0060] In some implementation solutions of this example, the compiled update package can be first placed on the kernel side, and the update package can be signed to make the upgrade package carry the private key through the signing method. Then, the upgrade package carrying the private key can be placed in the local file system of the 5G RedCap OPEN module, and the upgrade process can be executed using this upgrade package.

[0061] The above solution attaches the private key to the update package through the signing method, which is simple to operate and is conducive to performing security verification on the update package using the signing information (that is, the attached private key) before the upgrade.

[0062] Figure 5 A schematic diagram showing the upgrade process according to an embodiment of the present invention is as follows Figure 5 As shown, the upgrade process may include the following steps S510, S520, S530, S540, S550, and S560.

[0063] In step S510, the compiled update package is placed on the kernel side, and the update package is signed.

[0064] In step S520, the upgrade package carrying the private key is placed in the local file system of the 5G RedCap OPEN module.

[0065] In step S530, the local upgrade API interface is called to perform a local upgrade.

[0066] In step S540, it is determined whether the private key attached to the update package of the user application program matches the public key. When they match, step S550 is executed; otherwise, step S560 is executed.

[0067] In step S550, the user application program is upgraded using the update package.

[0068] In step S560, the upgrade is rejected.

[0069] According to another aspect of the embodiments of the present invention, an electronic device is further provided. Figure 6 A schematic block diagram of an electronic device according to an embodiment of the present invention is shown. As Figure 6 shown, the electronic device 600 includes: a processor 610 and a memory 620. A computer program is stored in the memory 620, and the processor 610 is configured to execute the computer program to implement the above method.

[0070] According to still another aspect of the embodiments of the present invention, a computer-readable storage medium is further provided. A computer program / instructions is stored in the storage medium, and when the computer program / instructions is executed by a processor, the above method is implemented. The storage medium may include, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a portable compact disc read-only memory (CD-ROM), a USB memory, or any combination of the above storage media. The computer-readable storage medium may be any combination of one or more computer-readable storage media.

[0071] Those of ordinary skill in the art can easily understand the implementation structure, working principle, and beneficial effects of the electronic device and the computer-readable storage medium by reading the above method. For the sake of brevity, they will not be elaborated here.

[0072] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present invention thereto. Those of ordinary skill in the art can make various changes and modifications therein without departing from the scope and spirit of the present invention. All such changes and modifications are intended to be included within the scope of the present invention as claimed in the appended claims.

[0073] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present invention.

[0074] In several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0075] In the specification provided herein, a large number of specific details are described. However, it can be understood that the embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures, and technologies are not shown in detail so as not to obscure the understanding of this specification.

[0076] Similarly, it should be understood that, in order to streamline the present invention and help understand one or more of the various inventive aspects, in the description of the exemplary embodiments of the present invention, the various features of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, the method of the present invention should not be construed as reflecting the intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected by the corresponding claims, the inventive point lies in being able to solve the corresponding technical problem with fewer features than all the features of a single disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into the detailed description, where each claim itself serves as a separate embodiment of the present invention.

[0077] Those skilled in the art can understand that, except for features that are mutually exclusive, any combination can be used for all the features disclosed in this specification (including the accompanying claims, abstract, and drawings) and for all the processes or units of any method or device so disclosed. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) can be replaced by an alternative feature that provides the same, equivalent, or similar purpose.

[0078] In addition, those skilled in the art can understand that although some embodiments described herein include certain features included in other embodiments rather than other features, the combination of features of different embodiments means that it is within the scope of the present invention and forms different embodiments. For example, in the claims, any one of the claimed embodiments can be used in any combination.

[0079] Each component embodiment of the present invention can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) can be used in practice to implement some or all of the functions of some modules in the electronic device according to the embodiments of the present invention. The present invention can also be implemented as a device program (such as a computer program and a computer program product) for executing part or all of the methods described herein. Such a program for implementing the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0080] It should be noted that the above embodiments illustrate the present invention rather than limit the present invention, and those skilled in the art can design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention can be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In the unit claims listing several devices, several of these devices can be embodied by the same item of hardware. The use of the words first, second, and third, etc. does not denote any order. These words can be interpreted as names.

[0081] As described above, it is only the specific implementation manner of the present invention or the description of the specific implementation manner. The protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, and all of them should be covered by the protection scope of the present invention. The protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A maintenance method for a communication module, characterized in that, The communication module is a 5G RedCap OPEN module, and the method includes: When flashing the communication module, If the current flashing is not the first flashing, determine whether the private key in the current firmware package matches the public key in the communication module, where the current firmware package is the firmware package used for the current flashing; When the private key matches the public key, use the current firmware package to flash the communication module; Among them, the new firmware obtained from each flashing is stored in the boot partition of the communication module.

2. The maintenance method according to claim 1, characterized in that, The method further includes: When the private key does not match the public key, generate a prompt message.

3. The maintenance method according to claim 1, wherein The method further includes: If the current flashing is the first flashing, write the public key into the system partition of the communication module; Use the current firmware package to flash the communication module.

4. The maintenance method according to claim 3, characterized in that When the current flashing is the first flashing, after the flashing is completed, the method further includes: Perform a restart detection operation; The restart detection operation includes: After the flashing is completed, restart the communication module; If no abnormality occurs during the restart process of the communication module, set the flag file in the boot partition to a preset value before the communication module finishes booting; Preferably, the restart detection operation is performed after each flashing is completed.

5. The maintenance method according to claim 4, characterized in that Before determining whether the private key in the current firmware package matches the public key in the communication module, the method further includes: Determine whether the flag file is a preset value; Among them, the step of determining whether the private key in the current firmware package matches the public key in the communication module is performed when the flag file is a preset value.

6. The maintenance method according to claim 4, characterized in that The method further includes: When the flag file is not a preset value, write the public key in the current firmware package into the system partition of the communication module, and use the current firmware package to flash the communication module.

7. The maintenance method according to claim 1, characterized in that The method further includes: When updating the user application program in the communication module, Determine whether the private key attached to the update package of the user application program matches the public key; When the private key attached to the update package matches the public key, use the update package to upgrade the user application program.

8. The maintenance method according to claim 7, wherein Before updating the user application program in the communication module, the method further includes: Sign the update package to attach the private key to the update package.

9. An electronic device, characterized in that, It includes a processor and a memory, and a computer program is stored in the memory. The processor is used to execute the computer program to implement the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that A computer program / instruction is stored, and when the computer program / instruction is executed by the processor, the method according to any one of claims 1-7 is implemented.

Images