CN111562934A - Software system upgrading method based on hot patch, terminal and storage medium - Google Patents
Software system upgrading method based on hot patch, terminal and storage medium Download PDFInfo
- Publication number
- CN111562934A CN111562934A CN202010259016.XA CN202010259016A CN111562934A CN 111562934 A CN111562934 A CN 111562934A CN 202010259016 A CN202010259016 A CN 202010259016A CN 111562934 A CN111562934 A CN 111562934A
- Authority
- CN
- China
- Prior art keywords
- code
- software system
- program
- patch
- patch file
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal 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 invention discloses a hot patch-based software system upgrading method, a terminal and a storage medium, wherein the hot patch-based software system upgrading method comprises the following steps: detecting a patch file in a software system, and acquiring positioning information of a code to be modified and a new code to be written in the patch file; searching a code to be modified in a program through the positioning information; and installing the patch file, and writing the new code to be written into a code storage area of the program. The invention replaces the traditional upgrading program file with the patch file, greatly reduces the size of the traditional upgrading program file, thereby saving the time of file transmission and file writing when the software system based on the hot patch is upgraded; moreover, under the condition that the software system normally operates, the installation of the patch file is supported, and the phenomena of interference and interruption of the service of the software system in operation are avoided.
Description
Technical Field
The present invention relates to the field of terminal applications, and in particular, to a method for upgrading a software system based on a hot patch, a terminal, and a storage medium.
Background
The existing software system has the characteristics of complex structure, various functions, variable requirements and the like, and the software system is frequently required to be updated and upgraded in order to ensure the running stability of the software system; especially at the beginning of software system application, it is often necessary to change the program code in the software system.
In the upgrading process of the software system, the software system is generally upgraded by adopting a program file replacing mode; in the process of replacing the program files, large program files need to be transmitted and written, so that the time consumption of the upgrading process is long, and the software system needs to be restarted after the upgrading process is finished, so that the software system upgrading based on the hot patch can be effective; in addition, in the upgrading process of the software system, the functions of the software system are also temporarily terminated, so that the running service in the software system is interrupted, and the normal use of the software system by a user is inconvenient.
Accordingly, the prior art is yet to be improved and developed.
Disclosure of Invention
The technical problem to be solved by the invention is that, aiming at the defects of the prior art, the invention provides a software system upgrading method, a terminal and a storage medium based on hot patching, wherein a traditional program file is replaced by a patch file, so that the size of the traditional program file is greatly reduced, and the time for file transmission and file writing is saved when the software system based on hot patching is upgraded; moreover, under the condition that the software system normally operates, the installation of the patch file is supported, and the phenomena of interference and interruption of the service of the software system in operation are avoided.
The technical scheme adopted by the invention for solving the technical problem is as follows:
in a first aspect, the present invention provides a method for upgrading a software system based on a hot patch, wherein the method for upgrading a software system based on a hot patch includes the following steps:
detecting a patch file in a software system, and acquiring positioning information of a code to be modified and a new code to be written in the patch file;
searching a code to be modified in a program through the positioning information;
and installing the patch file, and writing the new code to be written into a code storage area of the program.
Further, still include:
and generating the patch file in advance according to the program.
Further, still include:
and setting an installation process and an uninstallation process of the patch file, and storing the installation process and the uninstallation process in the program.
Further, the detecting a patch file in a software system, and acquiring the location information of a code to be modified and a new code to be written in the patch file specifically includes the following steps:
when detecting that a program of the software system runs, detecting a patch file in the software system;
reading version information and verification information in the patch file, and verifying the patch file through the version information and the verification information;
and acquiring the positioning information of the code to be modified and the new code to be written in the patch file according to the verification result.
Further, the searching for the code to be modified in the program through the positioning information specifically includes the following steps:
closing a write protection process of the running program in the software system;
searching a code to be modified in the program through the positioning information;
and copying the code to be modified according to the search result, and writing the copied code to be modified into a memory for backup so as to restore the code to be modified when the patch file is unloaded.
Further, the installing the patch file and writing the new code to be written into the code storage area of the program specifically includes the following steps:
installing the patch file, and writing a corresponding jump execution code in the code to be modified; the jump target of the jump execution code is the new code to be written;
and writing the new code to be written into a code storage area of the program, and starting a write protection process of the running program in the software system.
Further, the installing the patch file and writing the new code to be written in a code storage area of the program further includes:
and when detecting a new patch file, installing the new patch file, and uninstalling the original patch file in the program.
Further, the patch file is an ELF format file, which includes: version information, verification information, positioning information and the new code to be written.
In a second aspect, the present invention further provides a terminal, including a processor, and a memory connected to the processor, where the memory stores a hot patch based software system upgrade program, and the hot patch based software system upgrade program is used for implementing the operation of the hot patch based software system upgrade method according to the first aspect when executed by the processor.
In a third aspect, the present invention further provides a storage medium, where the storage medium stores a hot patch based software system upgrade program, and the hot patch based software system upgrade program is used to implement the operation of the hot patch based software system upgrade method according to the first aspect when executed by a processor.
The invention adopts the technical scheme and has the following effects:
the invention replaces the traditional upgrading program file with the patch file, greatly reduces the size of the traditional upgrading program file, thereby saving the time of file transmission and file writing when the software system based on the hot patch is upgraded; moreover, under the condition that the software system normally operates, the installation of the patch file is supported, and the phenomena of interference and interruption of the service of the software system in operation are avoided.
Drawings
FIG. 1 is a flowchart of a method for upgrading a software system based on hot patching according to an embodiment of the present invention.
Fig. 2 is a functional schematic diagram of a terminal in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Example one
The embodiment provides a hot patch based software system upgrading method, which is applied to a terminal, where the terminal includes but is not limited to: mobile terminals and computers; in this embodiment, the terminal is provided with a corresponding software system (i.e., an application), and a compiling tool (e.g., a compiler) for compiling the code and the patch file.
Compared with the traditional upgrading mode, the patch file adopted in the embodiment is smaller, so that the time for file transmission and file writing during upgrading can be saved, the normal operation of the software system is supported, and the interruption of the running service during upgrading is avoided.
As shown in fig. 1, in an implementation manner of this embodiment, the method for upgrading a software system based on hot patches includes the following steps:
step S100, detecting a patch file in a software system, and acquiring positioning information of a code to be modified and a new code to be written in the patch file.
In general, one software system upgrade only modifies one-thousandth of the code amount of the whole system program; when the software system is upgraded, recompilation for tiny code change can be avoided, namely, new program files are avoided from being generated again, and the size of the upgrade files is reduced by setting a program patch file to replace the traditional upgrade program files; therefore, compared with the traditional upgrading mode, the patch file adopted by the method is not more than one percent of the whole program file, and therefore time consumption of file transmission and file writing during software system upgrading can be reduced.
In this embodiment, before upgrading a software system, the patch file needs to be set; wherein the patch file includes: version information, verification information, positioning information and a new code to be written; in this embodiment, when the patch file is set, the new code to be written is used as the main content of the patch file.
Specifically, when the patch file is set, the patch file may be set in an ELF file format commonly used for code files, and in general, the ELF file is organized by segmented data, a header of the file is provided with a fixed format definition, the format defines a plurality of segments included in the file, and each segment may flexibly customize data content of the segment.
In this embodiment, when setting the patch file, three segments are defined in the header of the patch file, where the three segments are respectively: the version information and the verification information of the patch file, the positioning information of the code to be modified (namely the positioning information of the code to be modified), and the new code to be written.
The method comprises the following steps that the version number, the generation time and a CRC (redundancy check code) of a patch file are defined in a segment containing version information and check information of the patch file, and data in the segment can be used for distinguishing the identities of a plurality of patch files and checking the correctness of the data in each patch file; therefore, when the software system is upgraded, whether the patch file is matched with the software system can be determined through the data in the segment.
In the segment containing the positioning information of the code to be modified, the addresses of all modified function codes (namely, the original code in the original program, which is abbreviated as the original code hereinafter) are recorded, and the jump code which jumps to the corresponding new written code is recorded (namely, the original code can be bypassed by the jump code); therefore, when the software system is upgraded, the position information of the original code in the original program can be found through the data in the segment, and then the code executed at the position jumping to the new code is written; therefore, when the program of the software system runs, the original code is bypassed, and the new code is skipped and executed.
In the segment containing the new code to be written, all new function codes are contained, and the new function codes can be generated by a compiler after programming; therefore, when the software system is upgraded, the data of the segment is written into the original program, and the software system can be upgraded.
Namely, before the step S100, the method further includes the following steps:
and step S001, generating the patch file in advance according to the program.
In this embodiment, before upgrading the software system, an installation process and an uninstallation process of the patch file need to be set in an original program; by setting the installation process, when the software system is upgraded, the software system can detect a patch file in a file system, so that a new function code in the patch file is automatically installed under the condition that a system program normally runs; after the system program is installed successfully, when the system program runs to the original code position, jumping to the corresponding new code position, and executing the corresponding new code; and by setting the uninstalling process, the installed patch file can be automatically uninstalled when the software system is upgraded next time.
Namely, before the step S100, the method further includes the following steps:
step S002, setting an installation process and an uninstallation process of the patch file, and storing the installation process and the uninstallation process in the program.
In this embodiment, when the software system is upgraded, the terminal may detect an operating state of a program of the software system; when detecting that the program of the software system runs, the terminal further detects a patch file in the software system; and if the patch file is detected to be arranged in the software system, performing identity verification on the patch file, thereby determining whether the patch file is matched with the software system.
Specifically, when the patch file is verified, version information and verification information in the patch file can be read, and the patch file is verified through the version information and the verification information, that is, verification data (for example, version number, generation time, CRC check code) in the patch file is compared with verification data in an original program; if the verification is successful, the patch file is matched with the software system, and the software system can be upgraded through the patch file; and if the verification fails, the patch file is not matched with the software system.
And under the condition of successful verification, the terminal acquires the positioning information of the code to be modified and the new code to be written in the patch file, so that the software system is upgraded according to the acquired positioning information and the new code to be written.
Namely, the step S100 specifically includes the following steps:
step S110, when detecting that the program of the software system runs, detecting a patch file in the software system;
step S120, reading version information and verification information in the patch file, and verifying the patch file through the version information and the verification information;
step S130, acquiring the positioning information of the code to be modified and the new code to be written in the patch file according to the verification result.
In the embodiment, by detecting the patch file in the software system, the function of automatic upgrading can be realized under the condition that the software system program runs; and by verifying the patch file, the patch file can be ensured to be matched with the software system when the software system is upgraded, and the patch file with an upgrade error is avoided.
As shown in fig. 1, in an implementation manner of this embodiment, the method for upgrading a software system based on hot patches further includes the following steps:
and step S200, searching a code to be modified in a program through the positioning information.
In this embodiment, after verifying the patch file, the terminal may close a write protection process of an operating program in the software system; the write-in protection process is a program operation protection process, namely when a program of a software system operates, other codes are not allowed to be written in an original program, and the program of the software system is prevented from operating abnormally; the purpose of the embodiment to turn it off is: and under the condition that the software system program normally runs, the software system is upgraded, and the running service in the software system is not interrupted.
Further, after the write protection process is closed, the original code in the program can be searched through the positioning information so as to copy the original code in the program and determine the position of the original code in the program; if the original code in the program is found, copying the original code; and if the original code in the program is not found, terminating the upgrading of the software system.
When copying the original code, the software system may be applied for saving the original code by using the memory, that is, the copied original code is written into the memory for backup, and the purpose of the backup is to restore the modified code (i.e., the original code) when the patch file is uninstalled.
That is, the step S200 specifically includes the following steps:
step S210, closing the write-in protection process of the running program in the software system;
step S220, searching a code to be modified in the program through the positioning information;
step S230, copying the code to be modified according to the search result, and writing the copied code to be modified into a memory for backup, so as to recover the code to be modified when the patch file is unloaded.
In this embodiment, by closing the write protection process, the software system is upgraded under the condition that the software system program normally runs, so as to avoid interrupting the running service; and writing the copied original code into the internal memory so as to restore the original code in the original program when the patch file is unloaded.
As shown in fig. 1, in an implementation manner of this embodiment, the method for upgrading a software system based on hot patches further includes the following steps:
and step S300, installing the patch file, and writing the new code to be written into a code storage area of the program.
In this embodiment, after writing the copied original code into the memory, the terminal installs the patch file, and writes a corresponding jump execution code at the original code, where a jump target of the jump execution code is the new code to be written; and then, writing the new code to be written into a code storage area of the program, and starting a write protection process of the running program in the software system.
Specifically, when the patch file is installed, reading new code segments of the patch file, and uniformly copying all the new code segments to the tail of the whole code storage area of a program; then, the position of each original code is searched and obtained, a corresponding jump code which is jumped to the new code to be executed is written in respectively (namely, a jump code is written in the position of the original code correspondingly), when the program of the software system runs to the original code, the jump code is executed, and the program is transferred to the code storage area through the jump code so as to execute the corresponding new code.
It should be noted that, after the jump code is written, the write protection process of the program code fragment is also reopened in the embodiment, so that the security of all codes in the upgraded program is ensured.
Namely, the step S300 specifically includes the following steps:
step S310, installing the patch file, and writing a corresponding jump execution code in the code to be modified; the jump target of the jump execution code is the new code to be written;
step S320, writing the new code to be written into the code storage area of the program, and starting a write protection process of the running program in the software system.
The technical principle of the embodiment is as follows: the program codes of the software system are organized according to functions, wherein each function corresponds to a section of code; any function can jump to the code of another function to be executed by the program of the software system; after the code of the called function is executed, the code of the called function returns to the original position to be executed continuously.
If the code of a function needs to be changed, writing a jump code at the original code address, and writing a new code in a code storage area; new code is not written at the original code address because the new code may be longer than the primary code, with insufficient space to write; and after the new function is executed, returning to the function calling the original function to continue executing.
In another implementation manner of this embodiment, when patch files are installed for many times, if a plurality of patch files modify codes of the same function in sequence, the function has two new codes, which is inconvenient for the software system to distinguish and manage; therefore, it is also necessary to uninstall the patch file of the previously modified code and then install a new patch file.
Specifically, when a new patch file is detected, the terminal closes the write protection process of the program code segment, then searches for a code in the code storage area, obtains a code segment written last time (i.e., a code segment written when the patch file was installed last time), and deletes the code segment; and finally, searching to obtain the position of each original code, and restoring the original code stored in the memory to the original position.
It should be noted that, after the modified code is restored (the patch file is uninstalled), the write protection process of the program code segment is also reopened in the embodiment, so as to ensure the security of all the codes in the upgraded program.
That is, in another implementation manner of this embodiment, the method for upgrading a software system based on a hot patch further includes the following steps:
and step S400, when a new patch file is detected, installing the new patch file, and uninstalling the original patch file in the program.
In the embodiment, the patch file is used for replacing the traditional upgrading program file, so that the size of the traditional upgrading program file is greatly reduced, and the time for file transmission and file writing is saved when the software system based on the hot patch is upgraded.
Example two
As shown in fig. 2, the present embodiment provides a terminal, which includes a processor 10, and a memory 20 connected to the processor 10, where the memory 20 stores a hot patch based software system upgrade program, and the hot patch based software system upgrade program is used for implementing the operation of the hot patch based software system upgrade method according to the first embodiment when executed by the processor 10; as described above.
EXAMPLE III
The present embodiment provides a storage medium, wherein the storage medium stores a hot patch based software system upgrade program, and the hot patch based software system upgrade program is used for implementing the operation of the hot patch based software system upgrade method according to the first embodiment when being executed by a processor; as described above.
In summary, the patch file replaces the traditional upgrade program file, so that the size of the traditional upgrade program file is greatly reduced, and the time for file transmission and file writing is saved when the software system based on the hot patch is upgraded; moreover, under the condition that the software system normally operates, the installation of the patch file is supported, and the phenomena of interference and interruption of the service of the software system in operation are avoided.
Of course, it will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by a computer program instructing relevant hardware (such as a processor, a controller, etc.), and the program may be stored in a computer readable storage medium, and when executed, the program may include the processes of the above method embodiments. The storage medium may be a memory, a magnetic disk, an optical disk, etc.
It is to be understood that the invention is not limited to the examples described above, but that modifications and variations may be effected thereto by those of ordinary skill in the art in light of the foregoing description, and that all such modifications and variations are intended to be within the scope of the invention as defined by the appended claims.
Claims (10)
1. A hot patch based software system upgrading method is characterized by comprising the following steps:
detecting a patch file in a software system, and acquiring positioning information of a code to be modified and a new code to be written in the patch file;
searching a code to be modified in a program through the positioning information;
and installing the patch file, and writing the new code to be written into a code storage area of the program.
2. The method for hot patch based software system upgrade as claimed in claim 1, further comprising:
and generating the patch file in advance according to the program.
3. The method for hot-patch based software system upgrade as claimed in claim 2, further comprising:
and setting an installation process and an uninstallation process of the patch file, and storing the installation process and the uninstallation process in the program.
4. The method for upgrading a software system according to claim 1, wherein the detecting a patch file in the software system and obtaining the location information of a code to be modified and a new code to be written in the patch file comprises the following steps:
when detecting that a program of the software system runs, detecting a patch file in the software system;
reading version information and verification information in the patch file, and verifying the patch file through the version information and the verification information;
and acquiring the positioning information of the code to be modified and the new code to be written in the patch file according to the verification result.
5. The method for upgrading a software system according to claim 1, wherein the step of searching for a code to be modified in a program through the location information specifically includes the steps of:
closing a write protection process of the running program in the software system;
searching a code to be modified in the program through the positioning information;
and copying the code to be modified according to the search result, and writing the copied code to be modified into a memory for backup so as to restore the code to be modified when the patch file is unloaded.
6. The method for upgrading a software system according to claim 5, wherein the installing the patch file and writing the new code to be written into the code storage area of the program comprises the following steps:
installing the patch file, and writing a corresponding jump execution code in the code to be modified; the jump target of the jump execution code is the new code to be written;
and writing the new code to be written into a code storage area of the program, and starting a write protection process of the running program in the software system.
7. The method for upgrading a software system according to claim 1, wherein the installing the patch file and writing the new code to be written in a code storage area of the program further comprises:
and when detecting a new patch file, installing the new patch file, and uninstalling the original patch file in the program.
8. The method for upgrading a software system according to claim 1, wherein the patch file is an ELF format file, which includes: version information, verification information, positioning information and the new code to be written.
9. A terminal comprising a processor, and a memory coupled to the processor, the memory storing a hot patch based software system upgrade program for implementing the operations of the hot patch based software system upgrade method as claimed in any one of claims 1-8 when executed by the processor.
10. A storage medium storing a hot-patch based software system upgrade program for implementing the operations of the hot-patch based software system upgrade method as claimed in any one of claims 1-8 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010259016.XA CN111562934B (en) | 2020-04-03 | 2020-04-03 | Software system upgrading method based on hot patch, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010259016.XA CN111562934B (en) | 2020-04-03 | 2020-04-03 | Software system upgrading method based on hot patch, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111562934A true CN111562934A (en) | 2020-08-21 |
| CN111562934B CN111562934B (en) | 2023-08-11 |
Family
ID=72074215
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010259016.XA Active CN111562934B (en) | 2020-04-03 | 2020-04-03 | Software system upgrading method based on hot patch, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111562934B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930411A (en) * | 2020-09-30 | 2020-11-13 | 腾讯科技（深圳）有限公司 | Code upgrading method and device, computer equipment and storage medium |
| CN112199110A (en) * | 2020-10-16 | 2021-01-08 | 上海睿成软件有限公司 | Restart-free operation and maintenance upgrading method, system, device and medium |
| CN113312079A (en) * | 2020-11-20 | 2021-08-27 | 锐捷网络股份有限公司 | Hot patch upgrading method and device, electronic equipment and storage medium |
| CN113672272A (en) * | 2021-08-27 | 2021-11-19 | 大唐高鸿信安（浙江）信息科技有限公司 | Application dynamic upgrade method, generation method, device and electronic device |
| CN114125915A (en) * | 2022-01-26 | 2022-03-01 | 舟谱数据技术南京有限公司 | Positioning thermal repair system and method for setting terminal APP |
| CN115344434A (en) * | 2022-10-19 | 2022-11-15 | 紫光同芯微电子有限公司 | Patching method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799763A (en) * | 2009-02-10 | 2010-08-11 | 华为技术有限公司 | Method, device and system for patching kernel on line |
| CN102193805A (en) * | 2010-03-11 | 2011-09-21 | 华为技术有限公司 | Device and method for upgrading software patches |
| CN103885808A (en) * | 2014-04-08 | 2014-06-25 | 北京奇虎科技有限公司 | Hotfix processing method and device |
| CN104239082A (en) * | 2013-06-20 | 2014-12-24 | 上海博达数据通信有限公司 | Hot patching implementation method of embedded system |
| CN108228214A (en) * | 2017-12-29 | 2018-06-29 | 北京致远互联软件股份有限公司 | A kind of update method of application program, medium and equipment |
| CN109753793A (en) * | 2017-11-07 | 2019-05-14 | 华为终端（东莞）有限公司 | A kind of hot patch method and hot patch device |
| CN109828772A (en) * | 2019-02-19 | 2019-05-31 | 百度在线网络技术（北京）有限公司 | Hot update method, operating system, terminal device and storage medium |
-
2020
- 2020-04-03 CN CN202010259016.XA patent/CN111562934B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799763A (en) * | 2009-02-10 | 2010-08-11 | 华为技术有限公司 | Method, device and system for patching kernel on line |
| CN102193805A (en) * | 2010-03-11 | 2011-09-21 | 华为技术有限公司 | Device and method for upgrading software patches |
| CN104239082A (en) * | 2013-06-20 | 2014-12-24 | 上海博达数据通信有限公司 | Hot patching implementation method of embedded system |
| CN103885808A (en) * | 2014-04-08 | 2014-06-25 | 北京奇虎科技有限公司 | Hotfix processing method and device |
| CN109753793A (en) * | 2017-11-07 | 2019-05-14 | 华为终端（东莞）有限公司 | A kind of hot patch method and hot patch device |
| CN108228214A (en) * | 2017-12-29 | 2018-06-29 | 北京致远互联软件股份有限公司 | A kind of update method of application program, medium and equipment |
| CN109828772A (en) * | 2019-02-19 | 2019-05-31 | 百度在线网络技术（北京）有限公司 | Hot update method, operating system, terminal device and storage medium |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930411A (en) * | 2020-09-30 | 2020-11-13 | 腾讯科技（深圳）有限公司 | Code upgrading method and device, computer equipment and storage medium |
| CN112199110A (en) * | 2020-10-16 | 2021-01-08 | 上海睿成软件有限公司 | Restart-free operation and maintenance upgrading method, system, device and medium |
| CN112199110B (en) * | 2020-10-16 | 2022-05-31 | 上海睿成软件有限公司 | Restart-free operation and maintenance upgrading method, system, device and medium |
| CN113312079A (en) * | 2020-11-20 | 2021-08-27 | 锐捷网络股份有限公司 | Hot patch upgrading method and device, electronic equipment and storage medium |
| CN113672272A (en) * | 2021-08-27 | 2021-11-19 | 大唐高鸿信安（浙江）信息科技有限公司 | Application dynamic upgrade method, generation method, device and electronic device |
| CN114125915A (en) * | 2022-01-26 | 2022-03-01 | 舟谱数据技术南京有限公司 | Positioning thermal repair system and method for setting terminal APP |
| CN114125915B (en) * | 2022-01-26 | 2022-04-12 | 舟谱数据技术南京有限公司 | Positioning thermal repair system and method for setting terminal APP |
| CN115344434A (en) * | 2022-10-19 | 2022-11-15 | 紫光同芯微电子有限公司 | Patching method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111562934B (en) | 2023-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111562934B (en) | Software system upgrading method based on hot patch, terminal and storage medium | |
| US20230393840A1 (en) | File update method and apparatus, device and storage medium | |
| EP1591893A1 (en) | Method and system for fail-safe updating of boot code | |
| CN104239082A (en) | Hot patching implementation method of embedded system | |
| CN112015447B (en) | System updating method and device of electronic equipment, electronic equipment and storage medium | |
| CN110659041A (en) | Application upgrading method and system based on Android platform | |
| CN108733517A (en) | SSD firmware upgrades guard method and device | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| US7818557B2 (en) | Method for re-imaging a computer system | |
| CN110750280A (en) | Application upgrading method and system based on Android platform and storage medium | |
| CN113157303A (en) | Upgrading method, embedded system, terminal and computer storage medium | |
| CN112925549A (en) | System application upgrading system based on android frame | |
| CN113849200B (en) | Installation optimization method and system for android application in android compatible environment | |
| CN117687663B (en) | OTA-based partition dynamic adjustment method, device, equipment and storage medium | |
| CN116361817B (en) | Protection method of ubi file system under Linux | |
| CN118656101A (en) | Baseboard management controller firmware upgrade method, device, equipment and medium | |
| CN113467797A (en) | Program updating method, device and system and computer readable storage medium | |
| CN110928570A (en) | Firmware upgrading method and device and readable storage medium | |
| CN116880877A (en) | Virtual machine enhancement tool upgrading method and device, computer equipment and storage medium | |
| CN115421761A (en) | Method, device, system, equipment and medium for upgrading micro-control unit application program | |
| CN113641389B (en) | Software upgrading method, device and equipment based on OpenCPU | |
| CN116679971A (en) | Thermal repair method, device, electronic equipment and storage medium | |
| CN114398087A (en) | Method for improving running stability of single chip microcomputer after program updating and single chip microcomputer | |
| KR20060068558A (en) | How to Upgrade Firmware for Mobile Devices | |
| CN117270914B (en) | System upgrading method, device, equipment and medium of terminal equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |