CN110888654A - Method for upgrading embedded operating system - Google Patents
Method for upgrading embedded operating system Download PDFInfo
- Publication number
- CN110888654A CN110888654A CN201911104687.2A CN201911104687A CN110888654A CN 110888654 A CN110888654 A CN 110888654A CN 201911104687 A CN201911104687 A CN 201911104687A CN 110888654 A CN110888654 A CN 110888654A
- Authority
- CN
- China
- Prior art keywords
- upgrade
- upgrading
- upgrade file
- operating system
- embedded operating
- 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
- 238000000034 method Methods 0.000 title claims abstract description 20
- 230000007547 defect Effects 0.000 claims abstract description 10
- 230000005540 biological transmission Effects 0.000 claims description 13
- 238000005192 partition Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/60—Software deployment
- G06F8/61—Installation
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an upgrading method of an embedded operating system, which comprises the following steps: forming an upgrade file: aiming at the loopholes and the defects of the old version of the embedded operating system, equipment manufacturers develop a plurality of targeted patch packages; the upgrading method of the embedded operating system has the advantages that the upgrading of the equipment which cannot be connected with the network can be conveniently carried out, the upgrading cost is reduced, the upgrading efficiency is improved, and the situation that the upgrading fails due to the chaos of the upgrading of the system can be avoided.
Description
Technical Field
The invention relates to the technical field of embedded systems, in particular to an upgrading method of an embedded operating system.
Background
The embedded operating system is an operating system for an embedded system, the embedded operating system is a system software with wide application, and generally comprises bottom layer driving software related to hardware, a system kernel, a device driving interface, a communication protocol, a graphical interface, a standardized browser and the like, the embedded operating system is responsible for the allocation of all software and hardware resources of the embedded system, task scheduling, control and coordination of concurrent activities, the embedded operating system must embody the characteristics of the system in which the embedded operating system is located, and functions required by the system can be achieved by loading and unloading certain modules.
With the development and wide application of embedded systems, the essential maintenance work becomes increasingly heavy, and in the using process of users, part of defects which cannot be found in the software development stage are gradually exposed, so that the maintenance cost is inevitably increased, and in the running period of equipment, users often put forward new functions or higher performance requirements to products based on original software and hardware, so that equipment manufacturers need to upgrade the embedded systems according to the requirements of customers, so as to add new functions or repair bugs of old versions, but some equipment provided with the embedded operating systems cannot be connected through networks, so that the transmission and installation of upgrade files are not facilitated, if the manufacturers send special persons to upgrade each equipment, the upgrade cost is increased, and the upgrade efficiency is reduced, so that an upgrade method of the embedded operating systems is provided, for solving the above-mentioned problems.
Disclosure of Invention
The invention aims to provide an upgrading method of an embedded operating system, which has the advantages of facilitating system upgrading of equipment which cannot be connected with a network, reducing upgrading cost, improving upgrading efficiency, avoiding confusion of system upgrading and causing upgrading failure, and solving the problems that some equipment provided with the embedded operating system cannot be connected with the network, is inconvenient when the system needs upgrading, has high upgrading cost and low upgrading efficiency, and can be confused during upgrading to cause upgrading failure.
In order to achieve the purpose, the invention provides the following technical scheme: an upgrading method of an embedded operating system comprises the following steps:
step 1: forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file;
step 2: and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished;
and step 3: detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified;
and 4, step 4: sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file;
and 5: self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system;
step 6: deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program;
and 7: and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Preferably, in step 2, a system boot program is installed in the upgrading device to boot the system loading program, the upgrading device and the equipment are both provided with special corresponding interfaces, and the upgrading device is sold together with the equipment when leaving the factory.
Preferably, in step 3, after the loader detects and identifies the upgrade file, the loader needs to interact with the user to obtain the update permission.
Preferably, in step 3, after the transmission of the upgrade file is completed, the embedded operating system loader may identify the upgrade file only when the embedded operating system is started.
Preferably, in step 3, after the transmission of the upgrade file is completed, the embedded operating system loader may identify the upgrade file only when the embedded operating system is started.
Preferably, in step 3, before splitting the upgrade file, the upgrade file needs to be copied to the designated logical partition.
Preferably, in step 5, if there is a certain system module that is not operating normally, step 4 is repeated to reinstall the upgrade.
Preferably, in step 5, if the system module still operates abnormally after being reinstalled and upgraded, the system determines that the upgrade has failed, and restarts and loads the old version system.
Compared with the prior art, the invention has the beneficial effects that: the upgrading method of the embedded operating system has the advantages that the upgrading of the equipment which cannot be connected with the network can be conveniently carried out, the upgrading cost is reduced, the upgrading efficiency is improved, and the situation that the upgrading fails due to the chaos of the upgrading of the system can be avoided.
Detailed Description
The present invention will now be described in more detail by way of examples, which are given by way of illustration only and are not intended to limit the scope of the present invention in any way.
The invention provides a technical scheme that: an upgrading method of an embedded operating system comprises the following steps:
step 1: forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file;
step 2: and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished;
and step 3: detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified;
and 4, step 4: sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file;
and 5: self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system;
step 6: deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program;
and 7: and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
The first embodiment is as follows:
forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file; and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished; detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified; sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file; self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system; deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program; and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Example two:
in the first embodiment, the following steps are added:
in step 2, a system bootstrap program is installed in the upgrading device to bootstrap the system loading program, the upgrading device and the equipment are both provided with special corresponding interfaces, and the upgrading device is sold together with the equipment when leaving the factory.
Forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file; and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished; detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified; sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file; self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system; deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program; and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Example three:
in the second embodiment, the following steps are added:
in step 3, after the loading program detects and identifies the upgrade file, the upgrade file needs to interact with a user to obtain an update permission; after the transmission of the upgrade file is completed, the embedded operating system loading program can identify the upgrade file only when the embedded operating system is started; before splitting the upgrade file, the upgrade file needs to be copied to a designated logical partition.
Forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file; and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished; detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified; sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file; self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system; deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program; and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Example four:
in the third embodiment, the following steps are added:
in step 1, the upgrade file includes boot application files in addition to the patch package files.
Forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file; and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished; detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified; sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file; self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system; deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program; and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Example five:
in the fourth example, the following steps were added:
in step 5, if one system module is not operated normally, repeating step 4 to reinstall the upgrade; if the system module still operates abnormally after being reinstalled and upgraded, the system judges that the upgrade fails, and restarts and loads the old version system.
Forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file; and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished; detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified; sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file; self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system; deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program; and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (8)
1. An upgrade method for an embedded operating system, comprising: the method comprises the following steps:
step 1: forming an upgrade file: aiming at the loopholes and the defects of the embedded operating system of the old version, equipment manufacturers develop a plurality of targeted patch packages and pack the patch packages into an upgrade file;
step 2: and (3) transmission of an upgrade file: downloading the upgrade file from the network end to a matched upgrade device by a user, and connecting the upgrade device with equipment to upgrade the equipment after the download is finished;
and step 3: detecting an upgrade file: the embedded operating system loads a program to detect and identify an upgrade file in the upgrade device, and splits the upgrade file into a plurality of patch upgrade files after the upgrade file is detected and identified;
and 4, step 4: sorting and installing the upgrade files: the system detects a plurality of patch upgrade files one by one until a module corresponding to the patch upgrade file in the system is detected, and independently installs and upgrades the module, and after the upgrade of a certain module is finished, the system continues to detect the next patch upgrade file;
and 5: self-checking: repeating the step 4, after the plurality of patch upgrading files are upgraded respectively, enabling the system to enter a self-checking program, and sequentially operating all system modules by an operating system;
step 6: deleting the upgrade file: after the system module normally operates, the upgrade file enters a deleting program;
and 7: and (3) finishing upgrading: restarting the embedded operating system, detecting again by the loading program after starting, starting normally after detecting, and informing the user of the upgrading result.
2. The method for upgrading an embedded operating system according to claim 1, wherein: in step 2, a system boot program is installed in the upgrading device to boot the system loading program, the upgrading device and the equipment are both provided with special corresponding interfaces, and the upgrading device is sold together with the equipment when leaving the factory.
3. The method for upgrading an embedded operating system according to claim 1, wherein: in step 3, after the loader detects and identifies the upgrade file, the loader needs to interact with the user to obtain the update permission.
4. The method for upgrading an embedded operating system according to claim 1, wherein: in step 3, after the transmission of the upgrade file is completed, the embedded operating system loader may identify the upgrade file only when the embedded operating system is started.
5. The method for upgrading an embedded operating system according to claim 1, wherein: in step 1, the upgrade file includes a boot application file, in addition to the patch package file.
6. The method for upgrading an embedded operating system according to claim 1, wherein: in step 3, before splitting the upgrade file, the upgrade file needs to be copied to the designated logical partition.
7. The method for upgrading an embedded operating system according to claim 1, wherein: and in the step 5, if one system module is not operated normally, repeating the step 4 to reinstall the upgrade.
8. The method for upgrading an embedded operating system according to claim 1, wherein: in step 5, if the system module still operates abnormally after being reinstalled and upgraded, the system determines that the upgrade fails, and restarts and loads the old version system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911104687.2A CN110888654A (en) | 2019-11-13 | 2019-11-13 | Method for upgrading embedded operating system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911104687.2A CN110888654A (en) | 2019-11-13 | 2019-11-13 | Method for upgrading embedded operating system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110888654A true CN110888654A (en) | 2020-03-17 |
Family
ID=69747380
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911104687.2A Pending CN110888654A (en) | 2019-11-13 | 2019-11-13 | Method for upgrading embedded operating system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110888654A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090113196A1 (en) * | 2007-10-27 | 2009-04-30 | Hsun-Yao Jan | Method and systems for advanced reprogrammable boot codes and in-application programming of embedded microprocessor systems |
| CN102541595A (en) * | 2011-12-20 | 2012-07-04 | Tcl集团股份有限公司 | Method and device for upgrading intelligent device and intelligent device |
| CN102662689A (en) * | 2012-03-15 | 2012-09-12 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading embedded software based on USB interface |
| CN103412779A (en) * | 2013-08-14 | 2013-11-27 | 浙江大学 | Patch file system implementation method of embedded real-time operating system |
| CN105740017A (en) * | 2016-01-29 | 2016-07-06 | 贵阳海信电子有限公司 | Cloud television system upgrading method and device |
| CN106484450A (en) * | 2015-08-28 | 2017-03-08 | 青岛海信移动通信技术股份有限公司 | A kind of method for upgrading software and device |
| WO2017219861A1 (en) * | 2016-06-20 | 2017-12-28 | 阿里巴巴集团控股有限公司 | Method and device for controlling system start-up mode |
| CN108536452A (en) * | 2017-02-28 | 2018-09-14 | 深圳市帝迈生物技术有限公司 | A kind of embedded device and its system software upgrading method, system and terminal |
| CN109918108A (en) * | 2019-03-08 | 2019-06-21 | 珠海妙微科技有限公司 | A kind of embedded equipment plug-in upgrade method and device |
-
2019
- 2019-11-13 CN CN201911104687.2A patent/CN110888654A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090113196A1 (en) * | 2007-10-27 | 2009-04-30 | Hsun-Yao Jan | Method and systems for advanced reprogrammable boot codes and in-application programming of embedded microprocessor systems |
| CN102541595A (en) * | 2011-12-20 | 2012-07-04 | Tcl集团股份有限公司 | Method and device for upgrading intelligent device and intelligent device |
| CN102662689A (en) * | 2012-03-15 | 2012-09-12 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading embedded software based on USB interface |
| CN103412779A (en) * | 2013-08-14 | 2013-11-27 | 浙江大学 | Patch file system implementation method of embedded real-time operating system |
| CN106484450A (en) * | 2015-08-28 | 2017-03-08 | 青岛海信移动通信技术股份有限公司 | A kind of method for upgrading software and device |
| CN105740017A (en) * | 2016-01-29 | 2016-07-06 | 贵阳海信电子有限公司 | Cloud television system upgrading method and device |
| WO2017219861A1 (en) * | 2016-06-20 | 2017-12-28 | 阿里巴巴集团控股有限公司 | Method and device for controlling system start-up mode |
| CN108536452A (en) * | 2017-02-28 | 2018-09-14 | 深圳市帝迈生物技术有限公司 | A kind of embedded device and its system software upgrading method, system and terminal |
| CN109918108A (en) * | 2019-03-08 | 2019-06-21 | 珠海妙微科技有限公司 | A kind of embedded equipment plug-in upgrade method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100445952C (en) | Software version update method and device in communication equipment | |
| CN102622298B (en) | Software testing system and method | |
| US8499289B2 (en) | Method, device and system for realizing kernel online patching | |
| CN107493290B (en) | OTA (over the air) upgrading method for Android smart television system software | |
| CA2724532C (en) | Enhanced upgrade path | |
| NO312269B1 (en) | Software Upgrade Automation Procedure | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| CN102163167A (en) | Method and device for rescuing system | |
| CN102023881A (en) | Method and device for upgrading software as well as embedded device | |
| CN101593120A (en) | Be with outer upgrade method and system | |
| CN104391713A (en) | Automatic installation method of Windows system | |
| CN106502713A (en) | A kind of method for upgrading software and system | |
| CN110780942A (en) | System starting method and device, node equipment and computer readable storage medium | |
| US8689048B1 (en) | Non-logging resumable distributed cluster | |
| CN101384063A (en) | Method and system for terminal equipment repairing and updating, system manufacturing method | |
| CN110888654A (en) | Method for upgrading embedded operating system | |
| US7340738B2 (en) | Time optimized replacement of a software application | |
| CN109284137B (en) | Hypervisor-based QNX operating system starting method and device | |
| CN102087607B (en) | Method and device for installing patch packets | |
| CN112860297A (en) | Storage system based on automobile binocular camera and system updating method | |
| CN116028084A (en) | Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform | |
| CN115659322B (en) | Code multiplexing attack defense method based on sequential scheduling and loading in runtime | |
| CN1924802A (en) | Self-upgrading method for updating program | |
| CN103810006A (en) | Installation method and device for service packs | |
| CN103823693A (en) | Service pack installation method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200317 |