CN114443081A - Terminal upgrading method and terminal - Google Patents
Terminal upgrading method and terminal Download PDFInfo
- Publication number
- CN114443081A CN114443081A CN202011219326.5A CN202011219326A CN114443081A CN 114443081 A CN114443081 A CN 114443081A CN 202011219326 A CN202011219326 A CN 202011219326A CN 114443081 A CN114443081 A CN 114443081A
- Authority
- CN
- China
- Prior art keywords
- partition
- size
- upgrade
- terminal
- user data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a terminal upgrading method and a terminal, and belongs to the field of system upgrading. The method comprises the following steps: receiving an upgrade package of a target version, wherein the upgrade package comprises upgrade data of the target version; storing the upgrade package in user data blocking equipment, wherein the block equipment is in an uninstalled state in an upgrade process, and the offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than an available space after the block equipment is upgraded; mapping the upgrading data to a memory of the terminal through a memory mapping function mmap; and upgrading the terminal from the current version to the target version based on the upgrading data in the memory. The method provided by the embodiment of the application can solve the problem of upgrading failure caused by data partition change in the upgrading process.
Description
Technical Field
The present application relates to the field of system upgrade, and in particular, to a method for upgrading a terminal and a terminal.
Background
In order to obtain the latest use experience, a user needs to perform system upgrade on the terminal. Generally, a system upgrade is to download an upgrade package through an Over The Air (OTA) technique, store the downloaded upgrade package in a user data (data) partition, and upgrade the terminal system from a low version to a high version using the upgrade package. However, during the upgrade process, other partitions may occupy the space of the data partition, so that the data partition is modified, and thus, the upgrade package in the data partition in the file system is damaged, and the upgrade fails.
Disclosure of Invention
The application provides a terminal upgrading method and a terminal, and the problem that upgrading fails due to the fact that an upgrading packet is damaged in the upgrading process is solved by storing the upgrading packet in a block device.
In a first aspect, a method for upgrading a terminal is provided, including: receiving an upgrade package of a target version, wherein the upgrade package comprises upgrade data of the target version; storing the upgrade package in user data blocking equipment, wherein the block equipment is in an uninstalled state in an upgrade process, and the offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than an available space after the block equipment is upgraded; mapping the upgrading data to a memory of the terminal through a memory mapping function mmap; and upgrading the terminal from the current version to the target version based on the upgrading data in the memory.
The user data blocking device may also be represented by a data blocking device in the following, or the block device in the following is also the data blocking device herein.
According to the method for upgrading the terminal, the upgrading packet is stored in the user data block device in the non-mounted state, the upgrading data are mapped to the memory in the mmap mode, the terminal updates each partition by using the upgrading data in the memory, system upgrading is achieved, the upgrading packet can be guaranteed not to be damaged in the upgrading process, and the probability of successful OTA upgrading is improved.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: and unloading the access path of the block device in the file system.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: receiving first information sent by the OTA server, wherein the first information comprises partition information in the target version; and determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: and determining a first offset of the starting position relative to a reference position in the block device according to the starting position of the upgrade package in the block device and the size of the user data partitioning device, wherein the reference position comprises the position of the tail of the block device.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: generating an upgrade command, wherein the upgrade command comprises a path of the user data blocking device, the first offset and the size of the upgrade packet; and storing the upgrading command in at least one standby partition, wherein the standby partition is a partition which is not updated in the upgrading process.
With reference to the first aspect, in certain implementations of the first aspect, the first offset includes a byte alignment size, and the byte alignment size is used to align the starting position with an integer multiple of a byte position of the mmap reading mode.
With reference to the first aspect, in certain implementations of the first aspect, the first information specifically includes indication information of a size of a user data partition in the target version, and the partition information in the current version includes the size of the user data partition in the current version; the determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version includes: when the size of the user data partition in the target version is different from the size of the user data partition in the current version, determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version.
With reference to the first aspect, in certain implementations of the first aspect, the first information includes indication information of a size of a partition other than a user data partition in the target version, and the partition information in the current version includes indication information of a size of a partition other than a user data partition in the current version; the determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version includes: determining that the size of the user partition in the target version is changed relative to the size of the user partition in the current version when the sum of the sizes of the partitions in the target version other than the user data partition is different from the sum of the sizes of the partitions in the current version other than the user data partition.
In a second aspect, a terminal is provided, including: the download module is used for receiving an upgrade package of a target version, and the upgrade package comprises upgrade data of the target version; the upgrading system is used for storing the upgrading packet in user data blocking equipment, wherein the blocking equipment is in an uninstalled state in the upgrading process, and the offset of the initial position of the upgrading packet relative to the tail part of the blocking equipment is smaller than the available space of the blocking equipment after upgrading; the upgrading module is used for mapping the upgrading data to the memory of the terminal through a memory mapping function mmap; and upgrading the current version of the terminal to the target version based on the upgrading data in the memory.
With reference to the second aspect, in some implementations of the second aspect, the terminal further includes: and the unloading module is used for unloading the access path of the block device in the file system.
With reference to the second aspect, in some implementation manners of the second aspect, the terminal further includes a pre-download module and a determination module, where the pre-download module is configured to receive first information sent by the OTA server, where the first information includes partition information in the target version; and the judging module is used for determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version.
With reference to the second aspect, in some implementation manners of the second aspect, the terminal further includes an upgrade preprocessing module, configured to determine, according to a starting position of the upgrade package in the block device and a size of the user data partitioning block device, a first offset of the starting position with respect to a tail of the block device.
With reference to the second aspect, in some implementation manners of the second aspect, the upgrade preprocessing module is further configured to generate an upgrade command, where the upgrade command includes a path of the user data blocking device, the first offset, and the upgrade packet size; the storage module is further configured to store the upgrade command in at least one standby partition, where the standby partition is a partition that is not updated in the upgrade process.
With reference to the second aspect, in certain implementations of the second aspect, the first offset includes a byte alignment size used to align the starting position with an integer multiple of byte positions of the mmap read mode.
With reference to the second aspect, in some implementations of the second aspect, the first information specifically includes indication information of a size of a user data partition in the target version, and the partition information in the current version includes the size of the user data partition in the current version; the processing module is further configured to determine that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version when the size of the user data partition in the target version is different from the size of the user data partition in the current version.
With reference to the second aspect, in certain implementations of the second aspect, the first information includes indication information of a size of a partition other than a user data partition in the target version, and the partition information in the current version includes indication information of a size of a partition other than a user data partition in the current version; the processing module is further configured to determine that the size of the user partition in the target version is changed relative to the size of the user partition in the current version when the sum of the sizes of the partitions in the target version other than the user data partition is different from the sum of the sizes of the partitions in the current version other than the user data partition.
In a third aspect, a terminal is provided, including: a processor; a memory for storing executable instructions of the processor; wherein the executable instructions, when executed by the processor, cause the terminal to perform the steps of: receiving an upgrade package of a target version, wherein the upgrade package comprises upgrade data of the target version; storing the upgrade package in user data blocking equipment, wherein the block equipment is in an uninstalled state in an upgrade process, and the offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than an available space after the block equipment is upgraded; mapping the upgrading data to a memory of the terminal through a memory mapping function mmap; and upgrading the terminal from the current version to the target version based on the upgrading data in the memory.
With reference to the third aspect, in certain implementations of the third aspect, the executable instructions, when executed by the processor, cause the terminal to perform the steps of: and unloading the access path of the block device in the file system.
With reference to the third aspect, in certain implementations of the third aspect, the executable instructions, when executed by the processor, cause the terminal to perform the steps of: receiving first information sent by the OTA server, wherein the first information comprises partition information in the target version; and determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version.
With reference to the third aspect, in certain implementations of the third aspect, the executable instructions, when executed by the processor, cause the terminal to perform the steps of: and determining a first offset of the starting position relative to a reference position in the block device according to the starting position of the upgrade package in the block device and the size of the user data partitioning device, wherein the reference position comprises the position of the tail of the block device.
With reference to the third aspect, in certain implementations of the third aspect, the executable instructions, when executed by the processor, cause the terminal to perform the steps of: generating an upgrade command, wherein the upgrade command comprises a path of the user data blocking device, the first offset and the size of the upgrade packet; and storing the upgrading command in at least one standby partition, wherein the standby partition is a partition which is not updated in the upgrading process.
With reference to the third aspect, in certain implementations of the third aspect, the first offset includes a byte alignment size, and the byte alignment size is used to align the starting position with an integer multiple of a byte position of the mmap reading mode.
With reference to the third aspect, in certain implementations of the third aspect, the first information specifically includes indication information of a size of a user data partition in the target version, and the partition information in the current version includes the size of the user data partition in the current version; when the processor executes the executable instructions, the terminal is enabled to realize the following steps: and when the size of the user data partition in the target version is different from the size of the user data partition in the current version, determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version.
With reference to the third aspect, in certain implementations of the third aspect, the first information includes indication information of a size of a partition other than a user data partition in the target version, and the partition information in the current version includes indication information of a size of a partition other than a user data partition in the current version; when the processor executes the executable instructions, the terminal is caused to implement the steps of: determining that the size of the user partition in the target version is changed relative to the size of the user partition in the current version when the sum of the sizes of the partitions in the target version other than the user data partition is different from the sum of the sizes of the partitions in the current version other than the user data partition.
In a fourth aspect, a communication system is provided, which includes an OTA server and a terminal, wherein the terminal is configured to perform the method for upgrading the terminal as described in any implementation manner of the first aspect.
In a fifth aspect, a computer readable storage medium is provided, having program instructions which, when executed directly or indirectly, enable a method of upgrading a terminal as described in any of the implementations of the first aspect above to be implemented.
A sixth aspect provides a computer program which, when executed in at least one processor, causes the method of upgrading a terminal as described in any of the implementations of the first aspect described above to be implemented.
In a seventh aspect, a computer program product is provided, which, when executed on at least one processor, causes the method of upgrading a terminal as described in any of the implementations of the first aspect above to be implemented.
Drawings
Fig. 1 is a schematic diagram of a terminal structure according to an embodiment of the present disclosure.
Fig. 2 is a schematic flowchart of a method for upgrading a terminal according to an embodiment of the present application.
Fig. 3 is a schematic diagram of a storage location of an upgrade package in a block device according to an embodiment of the present application.
Fig. 4 is a schematic flowchart of another method for upgrading a terminal according to an embodiment of the present disclosure.
Fig. 5 is a schematic diagram of a graphical user interface provided in an embodiment of the present application.
Fig. 6A and fig. 6B are schematic diagrams of partition changes before and after upgrading according to an embodiment of the present application.
Fig. 7 is a schematic diagram of a terminal structure according to an embodiment of the present application.
Detailed Description
The embodiments of the present application will be described below with reference to the drawings.
It is noted that the terminology used in the description of the embodiments of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. In the description of the embodiments of the present application, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more, and "at least one", "one or more" means one, two or more, unless otherwise specified.
In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying a relative importance or implying an implicit indication of the number of technical features indicated. Thus, a definition of "a first" or "a second" feature may explicitly or implicitly include one or more of the features.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
With the evolution of the terminal system version, when the terminal is upgraded from a low version to a high version, the problem of insufficient system space occurs, and at this time, the system partition needs to be increased and the user data (data) partition needs to be reduced. However, as described in the background, in the current upgrade process, the upgrade package is usually stored in the data partition of the file system through the file system, and if the data partition is reduced, the data partition is destroyed, so that the upgrade package is destroyed, and the OTA upgrade cannot be performed.
In order to solve the above problems, one existing solution is: the upgrade package is backed up to a memory, such as a Random Access Memory (RAM), and when the upgrade package in the data partition is damaged, the upgrade package data in the memory can be used to continue the upgrade process. However, this solution has the following problems: firstly, the memory space of the memory is generally smaller, and with the development of a terminal system, the upgrade package is larger and larger, and the memory space is not enough to accommodate the upgrade package; in addition, because the memory is a temporary storage medium, if the terminal power supply is turned off, data in the memory is lost, which results in failure of upgrading.
In view of the above problems, an embodiment of the present application provides a method for upgrading a terminal, in which an upgrade package is stored in a data block partitioning device (the block device may be in an uninstalled state during an upgrade process), upgrade data in the block device is mapped into a memory by using a memory mapping function mmap mode, and then the terminal reads the upgrade data in the memory to complete the upgrade. According to the method, the problem that the upgrading packet cannot be upgraded due to damage of the upgrading packet when the data partition is changed can be solved, in addition, the upgrading packet does not need to be written into the memory, the upgrading process is not limited by the space capacity of the memory, and therefore the successful upgrading probability is improved.
The method for upgrading the terminal can be applied to scenes of batch wireless upgrading of the terminal on a terminal production line; or, the method can also be applied to a scene that a user or a maintenance point performs repair upgrade on the terminal.
The method for upgrading the terminal provided by the embodiment of the application can be applied to a mobile phone, a tablet personal computer, a television, wearable equipment (such as an intelligent watch, an intelligent bracelet, intelligent glasses, intelligent jewelry and the like), vehicle-mounted equipment, Augmented Reality (AR)/Virtual Reality (VR) equipment, and a notebook computerAnd ultra-mobile personal computers (UMPCs), netbooks, Personal Digital Assistants (PDAs), and other electronic devices. The embodiment of the present application does not set any limit to the specific type of the terminal. An exemplary embodiment of the terminal comprises the piggybacking
And the like operating the system.
Exemplarily, as shown in fig. 1, a schematic structural diagram of a terminal provided in an embodiment of the present application is shown. The terminal 100 includes a pre-download module 101, a determination module 102, a download module 103, an upgrade pre-processing module 104, and an upgrade module 105. Wherein the various modules may be communicatively coupled via a bus 106.
In some embodiments, the pre-download module 101 may be configured to obtain the relevant information of the target version through a channel including, but not limited to, wireless fidelity (WI-FI) download or Universal Serial Bus (USB) transmission; the related information includes, but is not limited to: upgrade package size, data partition information, etc.; the data partition information can further comprise information such as partition size, starting position and the like, or can also comprise information which is not limited in the form of partition tables and the like and can calculate the starting position of the target version data partition.
In some embodiments, the determining module 102 may be configured to determine whether the data partitions in the current version and the target version change according to the related information of the target version acquired by the pre-download module, where the determining manner includes, but is not limited to, the following two manners: (1) judging whether the size of the data partition is changed or not; (2) it is determined whether the total amount of partition sizes other than the data partition has changed.
In some embodiments, the download module 103 may be configured to download the upgrade package. In addition, the downloading module 103 can also be used for calculating information such as the starting position of the upgrade package in the data partitioning device.
In some embodiments, the upgrade preprocessing module 104 may be configured to calculate storage location information of the upgrade package, such as an offset of a start location of the upgrade package storage with respect to a tail of the data blocking device; in addition, the upgrade preprocessing module can be used for generating an upgrade command comprising the storage position information of the upgrade package, so that the upgrade module can acquire upgrade data according to the upgrade command.
In some embodiments, the upgrade module 105 may be configured to map upgrade data in the data partitioning device to a memory of the terminal in an mmap manner, and then read the upgrade data in the memory to update each partition, so as to implement terminal upgrade.
It should be understood that, in the embodiment of the present application, for convenience and simplicity of description, only the division of the above functional modules is illustrated, in an actual application, the above function distribution may be completed by different functional modules according to needs, that is, an internal structure of the terminal is divided into different functional modules to complete all or part of the functions described above, for the division of the modules or units, only one logical function division is performed, in an actual implementation, the terminal may further include more or less modules than those shown in fig. 1, for example, the terminal may further include an unloading module for unloading an access path of a block device in a file system, which is not limited in the present application.
The following describes a method for upgrading a terminal according to an embodiment of the present application in detail with reference to the accompanying drawings.
Exemplarily, as shown in fig. 2, a schematic flowchart of a method for upgrading a terminal provided in an embodiment of the present application is shown. The method can be executed by a terminal and mainly comprises the following steps:
s201, receiving an upgrade package of a target version, wherein the upgrade package comprises upgrade data of the target version.
In some embodiments, the OTA server may make an upgrade package of the target version, where the upgrade package includes upgrade data of the target version, such as a partition table of the target version, where the partition table may include information about an actual location of each partition in the target version (e.g., a starting location of each partition), a size of each partition, and so on.
In some embodiments, the OTA server may notify the terminal that the target version is available after generating the target version. For example, the OTA server sends a notification message to the terminal to indicate that the terminal has a target version available or that an upgrade package for the target version is available for download. In response to the notification message, the terminal may download the target version-up package by the OTA.
The number of the upgrade packages in the embodiment of the present application may be one or more. Alternatively, when there are a plurality of upgrade packages, the terminal may download each upgrade package in segments.
S202, storing the upgrade package in user data block equipment, wherein the block equipment is in an uninstalled state in the upgrade process, and the first offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than the available space of the block equipment after upgrade.
Wherein, the condition that the block device is in an uninstalled state in the upgrading process refers to that: during the upgrading process, an access path of the data partitioning device is not included on the file system. In other words, before upgrading, the terminal can delete the mapping relationship between the data partitioning device and the file system by calling a system command.
In one implementation, the offset of the start position of the upgrade packet in the data blocking device relative to the tail end of the block device is less than or equal to the available space of the upgraded user data blocking device. Specifically, the storage location of the upgrade package in the data partition block device may be close to the tail of the block device (as shown in fig. 3) to avoid being overwritten by data of other partitions (such as bootloader, boot, recovery, system, data partition, etc. shown in fig. 3).
It should be understood that, generally speaking, the size of the data partitioning device of the terminal will be larger than the size of the upgrade package of the corresponding version (such as the target version), therefore, if the upgrade package is stored at the tail of the user data partitioning device, it can be ensured that, in the upgrade process, even if the user data partition becomes small (such as a part of space occupied by other partitions), the upgrade package data will not be covered, and the upgrade is ensured to be completed smoothly.
In some embodiments, when there are multiple upgrade packages, the multiple upgrade packages may be sequentially arranged and stored at the tail of the data blocking device.
And S203, mapping the upgrade data to the memory of the terminal through a memory mapping function mmap.
In some embodiments, the upgrade module of the terminal may map the upgrade package data into the memory according to a storage location of the upgrade package.
Specifically, the upgrade module of the terminal may map the upgrade data in the data partitioning device to the terminal memory in a mmap manner according to the start position of the upgrade packet and the size of the upgrade packet.
It should be understood that, in the above method, the upgrade data in the block device is mapped to the terminal memory through the memory function mapping mmap, so that the terminal is no longer limited by the size of the memory during the upgrade process, and the method does not need to perform read/write operations on the upgrade data, and can achieve efficient data access.
And S204, upgrading the current version into a target version based on the upgrading data in the memory.
In some embodiments, the upgrade module of the terminal may read upgrade data from a terminal memory; and then, the upgrading module updates each partition according to the actual position (such as the initial position) of each partition indicated by the upgrading data and the size of each partition, so that the terminal system is upgraded from the current version to the target version.
It should be understood that, with the method for upgrading a terminal provided in this embodiment of the present application, the upgrade package may be stored in the data block partitioning device in an unmounted state, where the upgrade package is stored in the block device layer. After the upgrade package is stored in the data block partitioning device, the original data of the block device can be damaged (for example, cleared), and the upgrade package can be continuously stored in a section of available space in the block device; in the upgrading process, the upgrading module can map the upgrading data to the terminal memory according to the storage position of the upgrading packet in the block device, and then the upgrading data in the memory is read to realize system upgrading. In other words, according to the method for upgrading the terminal provided by the embodiment of the application, even if the data partition changes in the upgrading process, as long as the upgrade package is not covered by the upgrade data image, the upgrade package is available, and the upgrading process can be continuously executed. However, the currently adopted method of storing the upgrade package in the data partition of the file system cannot continuously distribute the upgrade package on the data partition block device, and if the size of the data partition of the file system changes or other data is written in during the upgrade process, the data partition may be damaged (for example, data in the data partition is disordered), and the upgrade package in the data partition is inevitably damaged, thereby resulting in upgrade failure.
According to the method for upgrading the terminal, the upgrade package is stored in the user data block device in the uninstalled state, and the upgrade data is mapped to the memory in the mmap mode, so that the terminal updates each partition by using the upgrade data in the memory, system upgrade is realized, the upgrade package can be guaranteed not to be damaged in the upgrade process, and the system version upgrade efficiency is improved.
In order to better understand the method for upgrading the terminal provided in the embodiments of the present application, the following describes a specific process of the method in more detail with reference to the accompanying drawings.
Exemplarily, fig. 4 shows a schematic flowchart of a method for upgrading a terminal according to an embodiment of the present application. The method can be executed by a terminal, and specifically comprises the following steps:
s401, the terminal acquires first information of the upgrade package.
The first information is used for indicating the size of the upgrade package and partition information of the target version.
In some embodiments, after the OTA server generates the available target version, a notification message may be sent to the terminal to indicate that the terminal has the available target version or an upgrade package of the target version available for downloading; after detecting the notification message sent by the OTA server, the terminal may prompt the user whether version upgrade is required.
For example, the terminal may pop up a prompt message on the display interface to confirm to the user whether to perform the version upgrade. Taking a terminal as a mobile phone, as shown in fig. 5, a Graphical User Interface (GUI) diagram provided in the embodiment of the present application is provided, where the GUI may be a main interface after the mobile phone is unlocked, and the main interface includes multiple Applications (APPs) such as a clock, a calendar, a gallery, a memo, and an intelligent life. After receiving the notification message sent by the OTA server, the mobile phone may pop-up a prompt message on the main interface in response to the notification message: "does you detect that a new system version is available for your handset, does a version update? "; then, if the mobile phone detects that the user clicks the 'confirmation' icon, the upgrading operation is executed; and if the mobile phone detects that the user clicks the 'cancel' icon, the version upgrading is not executed. Optionally, when the user chooses not to perform version upgrade, the mobile phone may further determine whether to perform version upgrade to the user again after a preset period of time, which is not limited in the present application.
In some embodiments, when the terminal detects that the user selects the operation of version upgrade, the terminal may request the OTA server to query the relevant information of the target version, such as the size of the target version upgrade package, the data partition information in the target version, and the like; in response to the query request of the terminal, the OTA server may send first information to the terminal, where the first information may be indication information of the upgrade package, and may be specifically used to indicate a size of the upgrade package, partition information of the target version, and the like. The partition information of the target version includes, for example, an actual start position of each partition in the target version, a size of each partition, and the like. Alternatively, the first information may be a partition table of the target version.
In some possible implementations, the first information may include a size and a starting position of the data partition in the target version; alternatively, the first information may also include information capable of calculating the size of the data partition and the start position of the upgrade package in the target version. In other words, the first information may indicate the data partition size and the start position in a direct or indirect manner, which is not limited in this application.
S402, judging whether the size of the data subarea changes.
In some embodiments, the terminal may determine whether the size of the data partition changes in the two versions based on the acquired first information in combination with the partition information in the current version.
As shown in fig. 6A and fig. 6B, which are schematic diagrams respectively illustrating changes of a data partition in a target version relative to a data partition in a current version, fig. 6A and fig. 6B respectively illustrate a bootloader partition, a boot partition, a recovery partition, a system partition, and a data partition. Specifically, in FIG. 6A, the space of the data partition in the target version is getting smaller relative to the space of the data partition in the current version; in FIG. 6B, the space of the data partition in the target version is enlarged relative to the space of the data partition in the current version.
If the size of the data partition changes, determining to store an upgrade package in the dimension of the block device; if the size of the data partition is not changed, the upgrade package can be stored in a file system writing mode. The method for upgrading the terminal provided by the embodiment of the present application is mainly introduced below for the situation that the size of the upgraded data partition changes.
It should be understood that when the data partition in the target version is not changed, which means that the data partition does not need to be damaged in the upgrading process, the upgrade package may be stored to the data partition through the file system, or may also be stored to the data partition block device in an unmounted state; when the data partition in the target version changes (for example, the space becomes smaller or larger), then, in the upgrading process, the corresponding data partition under the file system is damaged, and at this time, if the upgrade package is continuously stored to the data partition through the file system, the upgrade package is also damaged, and upgrading cannot be realized.
Generally, the size of the data partition of the terminal is larger than the size of the upgrade package, however, in order to further determine whether the available space of the data partition is sufficient to accommodate the upgrade package during the upgrade process, the method for upgrading the terminal provided in the embodiment of the present application may further include the following steps:
optionally, the terminal may determine whether the upgrade package can be stored in the data partitioning device based on the size of the upgrade package and the size of the data partition in the target version. For example, when the terminal determines that the size of the data partition in the target version is larger than the size of the upgrade package, it indicates that the available space of the data partition is sufficient to accommodate the upgrade package during the upgrade process, and at this time, it is determined that the upgrade package can be stored in the user data partition block device, that is, the upgrade package is stored in the block device dimension.
And S403, writing the upgrade package into the data block partitioning device.
In some embodiments, when it is determined in step S402 that a change in the size of the data partition in the target version has occurred, the path of the data partition block device may be offloaded in the file system such that the data partition block device is in an unmounted state. Specifically, the manner of bringing the block device into the unmounted state is, for example: and calling a system command to unload an access path of the block device in the file system, or calling the system command to delete the mapping relation between the data partition device and the file system.
It should be understood that, in general, if a block device is mounted, the computer files and directories on the block device are accessible to a user via a file system, and the user or system may write data to the block device via the file system. However, when the upgrade package is stored in the block device, if the block device is still in the mount state, the upgrade package may be damaged when other data is written into the block device during the upgrade process, resulting in a failure of the upgrade. Therefore, in the embodiment of the application, the block device can be uninstalled, so that the block device is in an uninstalled state, writing of other data is avoided, and the integrity and the availability of the upgrade package are ensured.
Optionally, after the upgrade package is stored, the block device may be in an uninstalled state; alternatively, the block device may be placed in an unmounted state before the upgrade package is stored. According to the method and the device, the data partitioning device is only required to be in the uninstalled state in the upgrading process, and the specific time for enabling the block device to be in the uninstalled state is not limited.
It should be appreciated that when the upgrade package is stored in the data partitioning device, the data in front of the data partitioning device is destroyed, such as cleared, and the upgrade package may be stored in the data partitioning device at a storage location (e.g., a start location) calculated according to a predetermined criterion.
When the terminal stores the upgrade package to the data block partitioning device, a first offset of a starting position of the upgrade package in the data block partitioning device relative to the tail end of the block device is smaller than or equal to an available space of the upgraded user data block partitioning device. Specifically, the storage location of the upgrade package in the data partition block device may be close to the tail of the block device (refer to fig. 3) to avoid being overwritten by data of other partitions.
Specifically, the starting position (startaddr) of the upgrade package can be calculated according to the size (packageSize) of the target version upgrade package and the size (dataSize) of the data blocking device, and the calculation method is as follows: starAddr ═ dataSize-packageSize-align, where align is the size needed for byte alignment.
It should be understood that the size required for byte alignment needs to be considered here because when the upgrade packet data is subsequently read from the data partitioning device in mmap mode, the data needs to be read smoothly from the position of integral multiple of the reading mode (e.g. 4K). In other words, align is to align the start position of the upgrade package at the position of the integer multiple of the reading mode (e.g. 4K), so as to ensure that the upgrade package data is smoothly mapped into the memory by mmap mode.
For example, when the mmap method reads data with 4K as the reading unit, if the start position of the upgrade package is 1G, the data can be read smoothly; if the initial position of the upgrade package is 1G more than 1 byte, the upgrade package is not an integral multiple of 4K, so that the data cannot be read smoothly, and at the moment, the offset of the initial position of the upgrade package relative to the tail of the data blocking device can be increased by utilizing the size of the aligned byte, so that the initial position is aligned with the position of the integral multiple of 4K byte, and the upgrade module is ensured to map the upgrade data in a mmap mode.
S404, writing the upgrading command into at least one standby partition.
It should be understood that in the actual upgrade process, the upgrade process is often unexpectedly stopped due to the terminal power off and the like, however, when the terminal is restarted, since the data partition may have been changed due to the previous upgrade process, the upgrade data mapped based on the storage location of the previous upgrade package may be in error. Therefore, in order to facilitate the search of the upgrade package and ensure the accuracy of the position of the upgrade package, the embodiment of the application indicates the storage position of the upgrade package by using the first offset of the start position of the upgrade package relative to the tail end position of the data blocking device.
Specifically, the terminal may calculate a first offset (offset) of a start position of the upgrade package with respect to a tail end of the data blocking device according to information of a storage position of the upgrade package in the blocking device, and the first offset may be used to indicate the storage position of the upgrade package during the upgrade process. The first offset can be obtained by calculating according to the size (dataSize) of the data blocking device and the starting position (startaddr) of the upgrade package, and the calculation mode is as follows: offset is dataSize-starAddr.
In some embodiments, after the upgrade package is stored, an upgrade command indicating the storage location of the upgrade package may be generated according to the storage location of the upgrade package, and the upgrade command may be stored in the standby partition, so that when the upgrade data needs to be obtained again (for example, in a scenario of restarting after power off of the terminal), the location where the upgrade package is located is accurately found, and the upgrade process is continued.
For example, the upgrade command may include information such as data block device path information, the first offset, and an upgrade packet size, or the upgrade command may further include other information that can be used to calculate the first offset, which is not limited in this application. The format of the upgrade command may be, for example:
--updata_package＝/dev/block/by-name/userdata:offset:packageSize。
in some embodiments, the spare partition may be a pre-partitioned fixed partition, and the spare partition is not updated during the upgrade process, in other words, the position, size, etc. of the spare partition is not changed during the version iteration process. The standby partition may be used to store a startup parameter indicating the type of mode to restart, such as start up upgrade mode. Wherein the standby partition may also be used to store upgrade commands. Illustratively, the spare partition is, for example, a misc partition.
In some embodiments, after the upgrade command is stored in the standby partition, the upgrade preprocessing module of the terminal may send a notification message to the upgrade module, and the notification upgrade module may read the upgrade command from the standby partition, and obtain the upgrade packet data according to the storage location of the upgrade packet indicated by the upgrade command.
For example, assuming that the data partition has changed due to the updated partition table when the terminal is powered off, since the first offset (offset) of the upgrade packet relative to the tail end of the data partition block device and the updated data partition block device size (newDataSize) are stored in the upgrade command of the standby partition at this time, after the terminal is restarted, the upgrade module may calculate the actual position of the upgrade packet in the new data partition block device through the offset and newDataSize, where the new starting position of the upgrade packet is: newswaraddr is newDataSize-offset. And then, the upgrading module maps the upgrading data in the data block partitioning device to a terminal memory in a mmap mode according to the new initial position, and continues the upgrading process.
According to the method, the upgrading command is stored in the at least one standby partition, so that the problem that the upgrading module cannot read upgrading data to cause upgrading failure due to the fact that the upgrading packet is lost in the scene that the upgrading process is stopped accidentally due to the terminal power failure and the like can be solved.
S405, mapping the upgrading data in the data block partitioning device to a terminal memory in a mmap mode.
And the terminal upgrading module acquires the storage position information of the upgrading packet in the data block partitioning device according to the upgrading command. Specifically, the upgrading module can obtain information of a path, a first offset, a size of the data partitioning device, a size of the upgrading packet and the like of the data partitioning device of the upgrading packet in the data partitioning device through an upgrading command; and then calculating the initial position of the upgrade package in the data block partitioning device according to the information.
In some embodiments, the upgrade module maps the upgrade data to the terminal memory in a mmap manner according to the storage location of the upgrade package.
In some embodiments, after the upgrade package is mapped to the terminal memory in the mmap manner, the upgrade module of the terminal may check the upgrade package, such as checking the signature and integrity of the upgrade package, to check whether the source of the upgrade package is legal and whether the upgrade package is complete.
The method maps the upgrade data to the terminal memory in a mmap mode, so that the condition that the upgrade process is limited by the size of the memory can be avoided, in other words, the problem of upgrade failure caused by the fact that the size of an upgrade packet is larger than the capacity of the memory during the current upgrade can be solved.
S406, upgrading the terminal system based on the upgrading data in the terminal memory.
In some embodiments, the upgrade module of the terminal may read upgrade data from a memory of the terminal; and then, the upgrading module updates each partition according to the actual position (such as the initial position) of each partition indicated by the upgrading data and the size of each partition, so that the terminal system is upgraded from the current version to the target version.
In some embodiments, after the data partitioning device stores the upgrade package, the data partitioning is destroyed, so that after each partition is updated, the upgrade module can refresh the data partitioning device data by formatting or writing the mirror image data.
According to the method for upgrading the terminal, the upgrading packet is stored in the user data block device in the non-mounted state, the upgrading data are mapped to the memory in the mmap mode, the terminal updates each partition by using the upgrading data in the memory, system upgrading is achieved, the upgrading packet can be guaranteed not to be damaged in the upgrading process, and the probability of successful OTA upgrading is improved.
Exemplarily, as shown in fig. 7, an embodiment of the present application further provides a schematic structural diagram of a terminal. The terminal 700 comprises a processor 701, a memory 702 and a communication interface 703, as well as a bus 704 connecting these devices. The memory 702 includes computer instructions, and when the computer instructions are executed in the processor 701, the terminal 700 is enabled to implement the method for upgrading the terminal according to the embodiment of the present application.
In addition, the embodiment of the present application further provides a communication system, which includes an OTA server and a terminal, where the OTA server and the terminal are configured to execute the method for upgrading the terminal in the embodiment of the present application.
The embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium has program instructions, and when the program instructions are directly or indirectly executed, the computer is enabled to implement the method for upgrading the terminal provided in the embodiment of the present application.
The embodiment of the present application further provides a computer program, and when the computer program is executed in at least one processor, the computer is enabled to implement the method for upgrading the terminal provided by the embodiment of the present application.
Embodiments of the present application further provide a computer program product, which when executed in at least one processor, enables the computer to implement the method for upgrading a terminal provided in the embodiments of the present application.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optics, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.
The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the embodiments of the present application should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.
Claims (20)
1. A method for upgrading a terminal is applied to the terminal and comprises the following steps:
receiving an upgrade package of a target version, wherein the upgrade package comprises upgrade data of the target version;
storing the upgrade package in user data blocking equipment, wherein the block equipment is in an uninstalled state in an upgrade process, and the offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than an available space after the block equipment is upgraded;
mapping the upgrading data to a memory of the terminal through a memory mapping function mmap;
and upgrading the terminal from the current version to the target version based on the upgrading data in the memory.
2. The method of claim 1, further comprising:
and unloading the access path of the block device in the file system.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
receiving first information sent by an OTA server, wherein the first information comprises partition information in the target version;
and determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version.
4. The method according to any one of claims 1-3, further comprising:
and determining a first offset of the starting position relative to the tail part in the block device according to the starting position of the upgrade package in the block device and the size of the user data blocking device.
5. The method of claim 4, further comprising:
generating an upgrade command, wherein the upgrade command comprises a path of the user data blocking device, the first offset and the size of the upgrade packet;
storing the upgrade command in at least one spare partition, the spare partition being a partition that is not updated during an upgrade process.
6. The method of claim 4 or 5, wherein the first offset comprises a byte alignment size used to align the starting position with an integer multiple of a byte position of the mmap read mode.
7. The method according to any of claims 3-6, wherein the first information specifically includes indication information of the size of the user data partition in the target version, and the partition information in the current version includes the size of the user data partition in the current version;
the determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version includes:
and when the size of the user data partition in the target version is different from the size of the user data partition in the current version, determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version.
8. The method according to any of claims 3-6, wherein the first information comprises indication information of the size of the other partition in the target version except the user data partition, and the partition information in the current version comprises indication information of the size of the other partition in the current version except the user data partition;
the determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version includes:
determining that the size of the user partition in the target version is changed relative to the size of the user partition in the current version when the sum of the sizes of the partitions in the target version other than the user data partition is different from the sum of the sizes of the partitions in the current version other than the user data partition.
9. A terminal, comprising:
the download module is used for receiving an upgrade package of a target version, and the upgrade package comprises upgrade data of the target version; storing the upgrade package in user data block equipment, wherein the block equipment is in an uninstalled state in the upgrade process, and the offset of the initial position of the upgrade package relative to the tail part of the block equipment is smaller than the available space of the block equipment after upgrade;
the upgrading module is used for mapping the upgrading data to the memory of the terminal through a memory mapping function mmap; and upgrading the current version of the terminal to the target version based on the upgrading data in the memory.
10. The terminal of claim 9, further comprising:
and the unloading module is also used for unloading the access path of the block device in the file system.
11. The terminal according to claim 9 or 10, wherein the terminal further comprises a pre-download module and a determination module, wherein,
the pre-download module is used for receiving first information sent by an OTA server, wherein the first information comprises partition information in the target version;
and the judging module is used for determining that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version according to the first information and the partition information in the current version.
12. The terminal according to any of claims 9-11, further comprising an upgrade preprocessing module configured to determine a first offset of the start position with respect to the tail of the block device according to a start position of the upgrade package in the block device and a size of the user data partitioning block device.
13. The terminal of claim 12, wherein the upgrade preprocessing module is further configured to generate an upgrade command, and the upgrade command includes a path of the user data blocking device, the first offset, and the upgrade packet size; and storing the upgrade command in at least one standby partition, wherein the standby partition is a partition which is not updated in the upgrade process.
14. The terminal of claim 12 or 13, wherein the first offset comprises a byte alignment size, and wherein the byte alignment size is used to align the starting position with an integer multiple of a byte position of the mmap read mode.
15. The terminal according to any of claims 11-14, wherein the first information specifically includes information indicating a size of a user data partition in the target version, and the partition information in the current version includes a size of a user data partition in the current version;
the judging module is further configured to determine that the size of the user data partition in the target version is changed relative to the size of the user data partition in the current version when the size of the user data partition in the target version is different from the size of the user data partition in the current version.
16. A terminal according to any one of claims 11-14, wherein the first information comprises information indicative of the size of a partition other than a user data partition in the target version, and the partition information in the current version comprises information indicative of the size of a partition other than a user data partition in the current version;
the judging module is further configured to determine that the size of the user partition in the target version is changed relative to the size of the user partition in the current version when the sum of the sizes of the partitions in the target version other than the user data partition is different from the sum of the sizes of the partitions in the current version other than the user data partition.
17. A terminal, comprising:
a processor;
a memory for storing executable instructions of the processor;
the executable instructions, when executed by the processor, cause the terminal to implement the method of any one of claims 1 to 8.
18. A communication system comprising an OTA server and a terminal, wherein the terminal is configured to perform the method of any of claims 1 to 8.
19. A computer-readable storage medium, having program instructions which, when executed directly or indirectly, cause the computer to carry out the method of any one of claims 1 to 8.
20. A computer program, characterized in that it causes a computer to carry out the method according to any one of claims 1 to 8 when it is executed in at least one processor.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011219326.5A CN114443081A (en) | 2020-11-04 | 2020-11-04 | Terminal upgrading method and terminal |
| PCT/CN2021/126472 WO2022095758A1 (en) | 2020-11-04 | 2021-10-26 | Terminal upgrade method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011219326.5A CN114443081A (en) | 2020-11-04 | 2020-11-04 | Terminal upgrading method and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114443081A true CN114443081A (en) | 2022-05-06 |
Family
ID=81361797
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011219326.5A Pending CN114443081A (en) | 2020-11-04 | 2020-11-04 | Terminal upgrading method and terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114443081A (en) |
| WO (1) | WO2022095758A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116719670A (en) * | 2022-09-30 | 2023-09-08 | 荣耀终端有限公司 | Data processing method, electronic device and readable storage medium |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115175171B (en) * | 2022-06-29 | 2024-05-14 | 智己汽车科技有限公司 | Vehicle OTA upgrading system and vehicle OTA upgrading method |
| WO2024000535A1 (en) * | 2022-06-30 | 2024-01-04 | 北京小米移动软件有限公司 | Partition table update method and apparatus, and electronic device and storage medium |
| CN115952564B (en) * | 2023-03-01 | 2023-08-15 | 荣耀终端有限公司 | Data writing method and terminal equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8898417B1 (en) * | 2009-10-20 | 2014-11-25 | Micron Technology, Inc. | Block-based storage device with a memory-mapped interface |
| US9557983B1 (en) * | 2010-12-29 | 2017-01-31 | Emc Corporation | Flexible storage application deployment mechanism |
| CN106293782A (en) * | 2015-05-15 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of method for upgrading system and terminal |
| CN106484448A (en) * | 2015-08-28 | 2017-03-08 | 青岛海信移动通信技术股份有限公司 | A kind of method for upgrading software and device |
| CN109086078B (en) * | 2017-06-14 | 2022-03-01 | 展讯通信（上海）有限公司 | Android system upgrading method and device, server and mobile terminal |
| CN109062598B (en) * | 2018-06-26 | 2022-07-26 | 珠海全志科技股份有限公司 | Safe OTA (over the air) upgrading method and system |
-
2020
- 2020-11-04 CN CN202011219326.5A patent/CN114443081A/en active Pending
-
2021
- 2021-10-26 WO PCT/CN2021/126472 patent/WO2022095758A1/en active Application Filing
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116719670A (en) * | 2022-09-30 | 2023-09-08 | 荣耀终端有限公司 | Data processing method, electronic device and readable storage medium |
| CN116719670B (en) * | 2022-09-30 | 2024-04-12 | 荣耀终端有限公司 | Data processing method, electronic device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022095758A1 (en) | 2022-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114443081A (en) | Terminal upgrading method and terminal | |
| US7584379B2 (en) | Mobile terminal and software update method | |
| CN111796856B (en) | Differential upgrading method and device, storage medium and computer equipment | |
| US20120102477A1 (en) | Firmware update method and apparatus for a mobile device | |
| US20040093597A1 (en) | Firmware update system for facilitating firmware update in mobile handset related applications | |
| CN110825563B (en) | System recovery method and device and electronic equipment | |
| US20080216066A1 (en) | Program upgrade system and method for ota-capable mobile terminal | |
| US20100325622A1 (en) | Updating Firmware of an Electronic Device | |
| CN110704335A (en) | Data reading and writing method and device based on asynchronous ring buffer | |
| US20230393840A1 (en) | File update method and apparatus, device and storage medium | |
| KR101555210B1 (en) | Apparatus and method for downloadin contents using movinand in portable terminal | |
| CN109086078B (en) | Android system upgrading method and device, server and mobile terminal | |
| CN106951284B (en) | User interface upgrading method and device based on android system application and intelligent terminal | |
| CN111221682B (en) | Method for mirroring storage system | |
| US20170052779A1 (en) | Method and Device for Running Version File | |
| WO2023169035A1 (en) | Operating system upgrade method, electronic device, and storage medium | |
| CN116737214A (en) | Upgrade method of operating system, electronic equipment and storage medium | |
| CN112148337A (en) | Firmware upgrading method and device | |
| CN114780019A (en) | Electronic device management method and device, electronic device and storage medium | |
| CN112860291B (en) | Firmware upgrading method and device | |
| US20050010914A1 (en) | Method for upgrading firmware | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| CN107436783B (en) | Differential upgrading method for mobile terminal, storage medium and mobile terminal | |
| EP3992783A1 (en) | Patch releasing method, server and terminal device | |
| CN114745268A (en) | Method for online updating and loading algorithm library of network camera |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |