CN106325901A - Software version management method and system - Google Patents
Software version management method and system Download PDFInfo
- Publication number
- CN106325901A CN106325901A CN201510353090.7A CN201510353090A CN106325901A CN 106325901 A CN106325901 A CN 106325901A CN 201510353090 A CN201510353090 A CN 201510353090A CN 106325901 A CN106325901 A CN 106325901A
- Authority
- CN
- China
- Prior art keywords
- software version
- program
- software
- described program
- version
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a software version management method, comprising the following steps: acquiring an upgrading file of a new software version; associating a corresponding program according to the upgrading file; judging whether a currently running software version of the program needs a backup or not; if the backup is needed, making a backup of the software version in a storage space; and installing the upgrading file to upgrade the program to a corresponding new version state. The invention also provides a corresponding software version management system. According to the software version management method and system provided by the invention, when a certain program is upgraded to the new version and has problems, the program can be switched to an original old version to continue to be used, and thus simple and easy operations can be achieved; and meanwhile, all original setting parameters can be saved because the program does not need to be uninstalled and reinstalled.
Description
Technical field
The present embodiments relate to data processing technique, especially relate to a kind of software version
Management method and system.
Background technology
Along with the development of mobile communication technology, the function of electronic installation is the most complicated, for expanding
Open up the function of electronic installation or for solving compatible with electronic device problem, need electronics
The software of device is upgraded.
Therefore, the electronic installation such as application program on mobile phone or bsp driver generally every
A period of time there will be new version, for customer upgrade.But, electronics sometimes
Device is after new version software of having upgraded, it may appear that operation is slowed by, instability etc. is asked
Topic, and this new version software is likely to new compatibility issue occur to its associated software,
Certainly, new version software itself is likely to have the most serious defect.
In the prior art, the problems referred to above to be solved, generally there are two kinds of methods, one is
Being iterated updating after next version occurs, two is by program unloading or by electronics dress again
Put factory reset, then re-download original legacy version software and install.Aobvious and easy
Seeing, first method is time-consuming, and second method is laborious, and uses second method to make
The many original parameters that arranges of calling program are all lost, thus need to reset, the most numerous
Trivial.
Summary of the invention
In view of the foregoing, it is necessary to a kind of software version management method is provided, can be in journey
After sequence is upgraded to redaction, it is conveniently switched to legacy version.
In view of the foregoing, there is a need to provide a kind of software version management system, Ke Yi
After program is upgraded to redaction, it is conveniently switched to legacy version.
Described software version management method includes step: obtain the upgrade file of software redaction；
According to the program that the association of described upgrade file is corresponding；Judge the software that described program is currently run
Version is the need of backup；If desired back up, then described software version is backed up in storage sky
Between；Described upgrade file is installed, described program to be upgraded to corresponding redaction state.
Described software version management system includes: acquisition module, is used for obtaining software redaction
Upgrade file；Relating module, for the program corresponding according to the association of described upgrade file；
First judge module, for judging that software version that described program currently runs is the need of standby
Part；Backup module, for if desired backing up, backs up described software version in memory space；
And, module is installed, is used for described upgrade file is installed, described program to be upgraded to accordingly
Redaction state.
Compared to prior art, described software version management method and system, by journey
The software version that sequence is currently run backs up, to be upgraded go wrong to redaction after, can
To recover/to switch back into the software version state before this upgrading easily by this backup, operation letter
Easily, and resetting owing to need not unloading, the parameter that arranges originally is all preserved.
Certainly, know this operator and can know more about the embodiment of the present invention upon review of the specification
Other benefit or other purpose.
Accompanying drawing explanation
Fig. 1 is the functional block diagram of invention software edition management system preferred embodiment.
Fig. 2 is the flow chart of invention software method for edition management preferred embodiment.
Main element symbol description
| Electronic installation | 2 |
| Cloud Server | 4 |
| Software version management system | 10 |
| Memorizer | 20 |
| Processor | 30 |
| Acquisition module | 100 |
| Relating module | 200 |
| First judge module | 300 |
| Backup module | 400 |
| Module is installed | 500 |
| Analyze module | 600 |
| Second judge module | 700 |
| Handover module | 800 |
| Mapping block | 900 |
| Management module | 1000 |
Following detailed description of the invention will further illustrate the present invention in conjunction with above-mentioned accompanying drawing.
Detailed description of the invention
Refering to shown in Fig. 1, it it is the function of invention software edition management system 10 preferred embodiment
Module map.Described software version management system 10 runs in electronic installation 2, electronic installation 2
Also include memorizer 20, processor 30 and communications module 40.Electronic installation 2 passes through communications module
40 are connected to Cloud Server 4.
Software version management system 10 for the upgrading of software version, backup, version switching,
Version match between distinct program or mapping, and the deletion etc. of version, to ensure this journey
Sequence can select suitable software version according to running environment instantly.
Described software version management system 10 can include acquisition module 100, relating module 200,
First judge module 300, backup module 400, install module 500, analyze module 600, the
Two judge modules 700, handover module 800, mapping block 900, management module 1000.Wherein
Module 100-1000 is for realizing the management processes such as the upgrading of software version, switching.Described mould
Block is configured to be performed by one or more processors (the present embodiment is processor 30), with
Complete the embodiment of the present invention.Module alleged by the embodiment of the present invention completes a specific function
Computer program code segments.Memorizer 20 provides for the program code etc. of software version management system 10
Material.
Acquisition module 100 is for obtaining the upgrade file of software redaction.In the present embodiment,
Described upgrade file can obtain from the server of software supplier, it is also possible to passes through computer
Or other modes obtain.Described upgrade file includes software upgrade package, software upgrading delta package
Or on-line updating of network link or script etc..
Relating module 200 is for the program corresponding according to the association of described upgrade file.In this enforcement
In example, according to this upgrade file more new script (updater-script), by this script
Find the program being currently installed on electronic installation 2 correspondence.Described " program " can be application
Program, bsp driver or system program.If it should be noted that acquisition module 100
Acquired upgrade file is compressed format files, then need first to solve this upgrade file
Pressure processes.
Whether the software version that the first judge module 300 currently runs for judging described program
Need backup.In the present embodiment, the first judge module 300 judges whether that the foundation of backup can
It is multiple to have, for example, it is possible to the software version currently run according to described program changes in program
Depending on importance during Dai, if software version belongs to the important version during version iteration
This, or belong to the stable release in version generation-inter-iteration, then judge that needs back up, when
So, if having backed up before, then need not repeat backup.
If the backup of described memory space has multiple software versions of described program, then need to do
Following operation: check the release status of the software version that described program currently runs: if described
The release status of the software version that program is currently run, higher than described program at described storage sky
The release status of all software versions of backup between, then judge to need to perform backup operation,
Performed by backup module 400；If the release status of the software version that described program is currently run,
Version less than one or more software versions that described program backs up in described memory space
State, then judge to need not perform backup operation, and by handover module 800 by described program
The highest version state being switched in the software version of this backup.
As a example by application program " com.android.serttings ": due to renewal repeatedly
Iteration, this program in memory space may backup have repeatedly update iteration stay multiple soft
Part version (V1.0, V2.3, V4.1, V5.0), obtains now V6.0 version and prepares to rise
Level, before this program is upgraded to V6.0, first checks the software that this program is currently run
The release status of version, if checking the software version that this program currently runs is V5.5, then
The software version that the software version that this program is currently run backs up higher than other is described, then judges
Need to perform backup operation, backup module 400 this software version V5.5 is backed up；If
Checking the software version that this program currently runs is V4.0, is readily obtained, in memory space
The release status of the software version V5.0 of backup is the highest, and has backed up, the most not
Need again to back up, but, owing to software version update is to do according to a upper recent release
Patch (patch), so when upgrading, will select the recent software version with present procedure
Based on upgrade.Therefore, in order to install V6.0 smoothly, need by switching mould
Block 800 will be somebody's turn to do " com.android.serttings " and first be switched to the release status of V5.0.
Backup module 400, for if desired backing up, backs up described software version in storage sky
Between.In the present embodiment, if according to judged result or the instruction of user, need to back up,
Then perform backup operation, to back up described software version in memory space.Described storage sky
Between can be memorizer 20, it is also possible to be Cloud Server 4.
Module 500 is installed be used for described upgrade file is installed, described program to be upgraded to accordingly
Redaction state.
Analyzed module 600 is used for analyzing described program and is upgraded to after redaction in running
The mistake occurred.In the present embodiment, if this program is bsp driver, described analysis
Module 600 can use or start during kernel module (kernel log) analysis program is run
Existing relevant mistake, if this program is application program, described analysis module 600 can use or
Start virtual machine debugging monitoring service (ddms, dalvik debug monitor service)
Analysis program be in operation occur relevant mistake；Kernel module or virtual machine debugging monitoring clothes
After business checks mistake, the number of times of mistake is carried out record, and the destructiveness of mistake is entered
Row assessment.
Second judge module 700, for according in the unit interval described mistake occur number of times or
The order of severity of described mistake, it may be judged whether need soft by back up in described memory space
Part version, is switched to legacy version state by described program.In the present embodiment, according to program
In running, the number of times of mistake occurs as whether switching software version shape in the unit interval
The foundation of state, it is of course also possible to using the order of severity of mistake as whether switching software version
The foundation of state.Such as, within one day, occur that more than 3 times mistakes or mistake cause program sudden strain of a muscle to move back, block
Dead or cause electronic installation 2 to be delayed machine etc., then program is switched to other release status, or to
Other release status is recommended to be switched to program in family.I.e. can automatically switch other release status,
Can also be that handoff advice is pushed to user by the interface of electronic installation 2, user determine
Whether it is switched to other software version state.
Handover module 800 is for being switched to legacy version state by described program.Certainly, this switching
Module 800 is not limited to this, and it can be according to the demand of user, each software version to program
Originally free switching is carried out.
Mapping block 900 associates with described program for each software version in described program
Mapping relations are set up according to matching degree between each software version of software；When described program needs
When being switched to other software version state, the software version shape switched according to described program
State, is switched to corresponding software version shape by described handover module 800 by described associated software
State.Described associated program, refers to when an equation changes, and the opposing party is also required to do adaptability
The program changed, is often referred to occur intersecting, call, be called at running, compatible
Program, or there is the program of the relations of dependence.
Such as, if program A has relatedness respectively at program B, C and D, each of its program A
Software version is as follows with the mapping of program B, the internet adapter software version of C, D:
| Program A | Program B | Program C | Program D |
| V1.0 | V1.0 | V1.1 | V1.5 |
| V2.0 | V1.1 | V1.2 | V2.0 |
| V3.0 | V2.0 | V2.0 | V3.5 |
As above table, the software version V1.0 of program A and the software version V1.0 of program B, program C
Software version V1.1 and the software version V1.5 of program D the most adaptive, as space is limited, not to upper
State form to illustrate one by one.
It is recognised that when the software version of program A to be switched to V1.0 from V3.0, program B
Also accordingly the software version of self can be switched to V1.0, program C also can be accordingly by self
Software version be switched to V1.1 program D and also can accordingly the software version of self be switched to
V1.5。
Management module 1000, for managing each software version of described program, such as each
The deletion of software version, store, sort, user oriented interface display, add up each journey
The software version that ordered pair is answered is detailed.
Refering to shown in Fig. 2, it it is the flow process of invention software method for edition management preferred embodiment
Figure.Described software version management method is applied in electronic installation 2, is performed by processor 30
In memorizer 20, the program code of storage realizes.Described software version management system 10 can be used
Version match between the upgrading of software version, backup, version switching, distinct program or
Map, and the deletion etc. of version, to ensure that program can be selected according to running environment instantly
Select suitable software version.
Step S10, the upgrade file of acquisition software redaction.In the present embodiment, described liter
Level file can obtain from the server of software supplier, it is also possible to by computer or other
Mode obtains.Described upgrade file includes software upgrade package, software upgrading delta package or network
Online upgrading link or script etc..
Step S12, according to program corresponding to described upgrade file association.In the present embodiment,
According to this upgrade file more new script (updater-script), found by this script and work as
Before be installed on electronic installation 2 correspondence program.Described " program " can be application program,
Bsp driver or system program.If it should be noted that the liter acquired in step S10
Level file is compressed format files, then need first to carry out this upgrade file decompression processing.
S14, judge that software version that described program currently runs is the need of backing up.?
In the present embodiment, it may be judged whether the foundation of backup can have multiple, for example, it is possible to according to institute
Depending on the software version that program of stating currently is run importance in program iterative process, if soft
Part version belongs to the master version during version iteration, or belongs in version generation-inter-iteration
Stable release, then judge that needs back up, and certainly, if having backed up before, are then not required to
Repeat backup.
If the backup of described memory space has multiple software versions of described program, then need to do
Following operation: check the release status of the software version that described program currently runs: if described
The release status of the software version that program is currently run, higher than described program at described storage sky
The release status of all software versions of backup between, then judge to need to perform backup operation；
If the release status of the software version that described program is currently run, less than described program described
The release status of one or more software versions of backup in memory space, then judge need not
Perform backup operation, and the highest version described program being switched in the software version of this backup
This state.
As a example by application program " com.android.serttings ": due to renewal repeatedly
Iteration, this program in memory space may backup have repeatedly update iteration stay multiple soft
Part version (V1.0, V2.3, V4.1, V5.0), obtains now V6.0 version and prepares to rise
Level, before this program is upgraded to V6.0, first checks the software that this program is currently run
The release status of version, if checking the software version that this program currently runs is V5.5, then
The software version that the software version that this program is currently run backs up higher than other is described, then judges
Need to perform backup operation, perform step S16；If check that this program currently runs is soft
Part version is V4.0, is readily obtained, the version of the software version V5.0 of backup in memory space
State is the highest, and has backed up, and therefore need not again back up, but, due to
Software version update is to be Patch (patch) according to a upper recent release, so in upgrading
Time, select to upgrade based on the recent software version of present procedure.Therefore, for
The execution of step S18, needs " com.android.serttings " to be first switched to
The release status of V5.0.
If step S16 is according to judged result or the instruction of user, needs to back up, then hold
Row backup operation, to back up described software version in memory space.In the present embodiment,
Described memory space can be memorizer 20, it is also possible to be Cloud Server 4.
Step S18, described upgrade file is installed, described program to be upgraded to described upgrading literary composition
The redaction state that part is corresponding.
Step S20, analyze the mistake that described program is upgraded to occur in running after redaction
By mistake.In the present embodiment, if this program is bsp driver, kernel module can be started
(kernel log) analyzes the relevant mistake of program emerged in operation, if this program is application
Program, can start virtual machine debugging monitoring service (ddms, dalvik debug monitor
Service) analysis program be in operation occur relevant mistake；Kernel module or virtual machine are adjusted
Examination monitoring service inspection, to after mistake, carries out record to the number of times of mistake, and to mistake
Destructiveness is estimated.
Step S22, the number of times occurred according to mistake described in the unit interval or described mistake tight
Weight degree, it may be judged whether need by the software version of backup in described memory space, by institute
The program of stating is switched to legacy version state.In the present embodiment, according in program operation process,
The number of times of mistake occurs as whether switching the foundation of software version state in the unit interval, when
So, it is also possible to using the order of severity of mistake as the foundation whether switching software version state.
Such as, within one day, occur more than 3 times mistakes or mistake cause program dodge move back, stuck or cause electronics
Device 2 is delayed machine etc., then program is switched to other release status, or recommends program to user
It is switched to other release status.I.e. can automatically switch to other software version state, it is possible to
Being handoff advice to be pushed to user by the interface of electronic installation 2, by the user decide whether
It is switched to other software version state.
Preferably, each of each software version of described program and described program associated software
Set up according to matching degree between software version and have mapping relations；When described program needs to be switched to
During other software version state, the software version state switched according to described program, by institute
State associated software and be switched to corresponding software version state.Described associated program, refers to when one
Equation changes, and the opposing party is also required to do the program of adaptive change, is often referred to running
Intersecting, call, be called occur in journey, compatible program, or has the program of the relations of dependence.
Such as, if program A has relatedness respectively at program B, C and D, each of its program A
Software version is as follows with the mapping of program B, the internet adapter software version of C, D:
| Program A | Program B | Program C | Program D |
| V1.0 | V1.0 | V1.1 | V1.5 |
| V2.0 | V1.1 | V1.2 | V2.0 |
| V3.0 | V2.0 | V2.0 | V3.5 |
As above table, the software version V1.0 of program A and the software version V1.0 of program B, program C
Software version V1.1 and the software version V1.5 of program D the most adaptive, as space is limited, not to upper
State form to illustrate one by one.
It is recognised that when the software version of program A to be switched to V1.0 from V3.0, program B
Also accordingly the software version of self can be switched to V1.0, program C also can be accordingly by self
Software version be switched to V1.1 program D and also can accordingly the software version of self be switched to
V1.5。
Described electronic installation 2 includes based on Windows, Lunix, Android, IOS, WP
Etc. the computer of system, smart mobile phone, panel computer, electricity paper book, intelligent watch etc., at this
Different enumerate.
Above example is only in order to illustrate technical scheme and unrestricted, although reference
The present invention has been described in detail by preferred embodiment, and those of ordinary skill in the art should
Understand, technical scheme can be modified or equivalent, without deviating from this
The spirit and scope of inventive technique scheme.
Claims (9)
1. a software version management method, it is characterised in that the method comprising the steps of:
Obtain the upgrade file of software redaction；
According to the program that the association of described upgrade file is corresponding；
Judge that software version that described program currently runs is the need of backup；
If desired back up, then described software version is backed up in memory space；
Described upgrade file is installed, described program to be upgraded to corresponding redaction state.
2. software version management method as claimed in claim 1, it is characterised in that described in described installation
After the step of upgrade file, further comprise the steps of:
Analyze the mistake occurred in running after described program is upgraded to redaction；
The number of times occurred according to mistake described in the unit interval or the order of severity of described mistake, it may be judged whether need
By the software version of backup in described memory space, described program is switched to legacy version state.
3. software version management method as claimed in claim 1, it is characterised in that described memory space is standby
Part has multiple software versions of described program, and whether the described software version judging that described program is currently run needs
Step to be backed up, specifically includes:
Check the release status of the software version that described program currently runs:
If the release status of the software version that described program is currently run, higher than described program at described storage sky
The release status of all software versions of backup between, then judge to need to perform backup operation；
If the release status of the software version that described program is currently run, less than described program at described storage sky
The release status of one or more software versions of backup between, then judge to need not perform backup operation, and
The highest version state that described program is switched in the software version of this backup.
4. software version management method as claimed in claim 1, it is characterised in that each of described program is soft
Set up according to matching degree between each software version of part version and described program associated software and have mapping relations；
When described program needs to be switched to other software version state, the software switched according to described program
Release status, is switched to corresponding software version state by described associated software.
5. a software version management system, it is characterised in that including:
Acquisition module, for obtaining the upgrade file of software redaction；
Relating module, for the program corresponding according to the association of described upgrade file；
First judge module, for judging that software version that described program currently runs is the need of backup；
Backup module, for if desired backing up, backs up described software version in memory space；And
Module is installed, is used for described upgrade file is installed, so that described program to be upgraded to corresponding redaction shape
State.
6. software version management system as claimed in claim 5, it is characterised in that this system also includes point
Analysis module, the second judge module and handover module:
Described analysis module, for analyzing the mistake occurred in running after described program is upgraded to redaction；
Described second judge module, for the number of times occurred according to mistake described in the unit interval or described mistake
The order of severity, it may be judged whether need by described memory space backup software version, by described program
It is switched to legacy version state；
Described handover module, for being switched to legacy version state by described program.
7. software version management system as claimed in claim 5, it is characterised in that described memory space is standby
Part has multiple software versions of described program, and described first judge module is additionally operable to:
Check the release status of the software version that described program currently runs:
If the release status of the software version that described program is currently run, higher than described program at described storage sky
The release status of all software versions of backup between, then judge to need to perform backup operation；
If the release status of the software version that described program is currently run, less than described program at described storage sky
The release status of one or more software versions of backup between, then judge to need not perform backup operation, and
The highest version state described program being switched in the software version of this backup by described handover module.
8. software version management system as claimed in claim 5, it is characterised in that this system also includes mapping
Module, for each software version of described program and described program associated software each software version it
Between set up mapping relations according to matching degree；
When described program needs to be switched to other software version state, the software switched according to described program
Release status, is switched to corresponding software version state by described handover module by described associated software.
9. the software version management system as described in claim 5-8 any one, it is characterised in that this system
Also include managing module, for managing each software version of described program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510353090.7A CN106325901A (en) | 2015-06-24 | 2015-06-24 | Software version management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510353090.7A CN106325901A (en) | 2015-06-24 | 2015-06-24 | Software version management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106325901A true CN106325901A (en) | 2017-01-11 |
Family
ID=57727855
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510353090.7A Pending CN106325901A (en) | 2015-06-24 | 2015-06-24 | Software version management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106325901A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107357614A (en) * | 2017-06-30 | 2017-11-17 | 深圳前海弘稼科技有限公司 | Parameter updating method and device, planting box and storage medium |
| CN107423102A (en) * | 2017-08-30 | 2017-12-01 | 杭州为诺智能科技有限公司 | A kind of quick device for realizing same table parameter setting |
| CN107479933A (en) * | 2017-08-21 | 2017-12-15 | 惠州Tcl移动通信有限公司 | A kind of application program for mobile terminal upgrade method, storage device and mobile terminal |
| CN108628642A (en) * | 2017-03-20 | 2018-10-09 | 北京京东尚科信息技术有限公司 | The method and apparatus and storage medium of the version of switching system |
| CN109814908A (en) * | 2019-01-17 | 2019-05-28 | 深圳忆联信息***有限公司 | Firmware stablizes method, apparatus, computer equipment and the storage medium of upgrading |
| CN110175034A (en) * | 2019-05-30 | 2019-08-27 | 烽火通信科技股份有限公司 | A kind of restoration methods and system of application program |
| CN111381849A (en) * | 2019-02-19 | 2020-07-07 | 鸿合科技股份有限公司 | Software updating method and device and electronic equipment |
| CN111443624A (en) * | 2019-01-17 | 2020-07-24 | 厦门地平线征程智能科技有限公司 | Vehicle-mounted equipment and detection method thereof |
| CN116088926A (en) * | 2023-01-10 | 2023-05-09 | 睿智合创(北京)科技有限公司 | Decision component version management method |
| CN116225966A (en) * | 2023-04-25 | 2023-06-06 | 深圳曼瑞德科技有限公司 | Application evaluation method and system based on intelligent watch |
| CN111381849B (en) * | 2019-02-19 | 2024-07-02 | 鸿合科技股份有限公司 | Software updating method and device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040123285A1 (en) * | 2002-12-24 | 2004-06-24 | Berg Daniel C | Self-healing version and configuration model for an application server |
| US20070245337A1 (en) * | 2004-01-27 | 2007-10-18 | Willis Edward S Ii | Software-delivered dynamic persistent data |
| CN101184309A (en) * | 2007-12-21 | 2008-05-21 | 深圳国人通信有限公司 | Embedded system remote upgrade method for repeater equipment |
| CN101533356A (en) * | 2009-04-21 | 2009-09-16 | 华为技术有限公司 | A method, a device and a system for realizing software online upgrade |
| CN101697133A (en) * | 2009-10-26 | 2010-04-21 | 中兴通讯股份有限公司 | Software upgrading method, software upgrading system and client |
| CN102023881A (en) * | 2010-12-14 | 2011-04-20 | 福建星网锐捷网络有限公司 | Method and device for upgrading software as well as embedded device |
-
2015
- 2015-06-24 CN CN201510353090.7A patent/CN106325901A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040123285A1 (en) * | 2002-12-24 | 2004-06-24 | Berg Daniel C | Self-healing version and configuration model for an application server |
| US20070245337A1 (en) * | 2004-01-27 | 2007-10-18 | Willis Edward S Ii | Software-delivered dynamic persistent data |
| CN101184309A (en) * | 2007-12-21 | 2008-05-21 | 深圳国人通信有限公司 | Embedded system remote upgrade method for repeater equipment |
| CN101533356A (en) * | 2009-04-21 | 2009-09-16 | 华为技术有限公司 | A method, a device and a system for realizing software online upgrade |
| CN101697133A (en) * | 2009-10-26 | 2010-04-21 | 中兴通讯股份有限公司 | Software upgrading method, software upgrading system and client |
| CN102023881A (en) * | 2010-12-14 | 2011-04-20 | 福建星网锐捷网络有限公司 | Method and device for upgrading software as well as embedded device |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108628642B (en) * | 2017-03-20 | 2021-07-30 | 北京京东尚科信息技术有限公司 | Method and apparatus for switching versions of system and storage medium |
| CN108628642A (en) * | 2017-03-20 | 2018-10-09 | 北京京东尚科信息技术有限公司 | The method and apparatus and storage medium of the version of switching system |
| CN107357614A (en) * | 2017-06-30 | 2017-11-17 | 深圳前海弘稼科技有限公司 | Parameter updating method and device, planting box and storage medium |
| CN107479933A (en) * | 2017-08-21 | 2017-12-15 | 惠州Tcl移动通信有限公司 | A kind of application program for mobile terminal upgrade method, storage device and mobile terminal |
| CN107423102A (en) * | 2017-08-30 | 2017-12-01 | 杭州为诺智能科技有限公司 | A kind of quick device for realizing same table parameter setting |
| CN111443624B (en) * | 2019-01-17 | 2021-03-23 | 北京地平线机器人技术研发有限公司 | Vehicle-mounted equipment and detection method thereof |
| CN111443624A (en) * | 2019-01-17 | 2020-07-24 | 厦门地平线征程智能科技有限公司 | Vehicle-mounted equipment and detection method thereof |
| CN109814908A (en) * | 2019-01-17 | 2019-05-28 | 深圳忆联信息***有限公司 | Firmware stablizes method, apparatus, computer equipment and the storage medium of upgrading |
| CN111381849A (en) * | 2019-02-19 | 2020-07-07 | 鸿合科技股份有限公司 | Software updating method and device and electronic equipment |
| CN111381849B (en) * | 2019-02-19 | 2024-07-02 | 鸿合科技股份有限公司 | Software updating method and device and electronic equipment |
| CN110175034A (en) * | 2019-05-30 | 2019-08-27 | 烽火通信科技股份有限公司 | A kind of restoration methods and system of application program |
| CN116088926A (en) * | 2023-01-10 | 2023-05-09 | 睿智合创(北京)科技有限公司 | Decision component version management method |
| CN116088926B (en) * | 2023-01-10 | 2023-10-20 | 睿智合创(北京)科技有限公司 | Decision component version management method |
| CN116225966A (en) * | 2023-04-25 | 2023-06-06 | 深圳曼瑞德科技有限公司 | Application evaluation method and system based on intelligent watch |
| CN116225966B (en) * | 2023-04-25 | 2023-08-04 | 深圳曼瑞德科技有限公司 | Application evaluation method and system based on intelligent watch |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106325901A (en) | Software version management method and system | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US9417865B2 (en) | Determining when to update a package manager software | |
| US8954930B2 (en) | System and method for reducing test effort by object risk analysis | |
| US8176552B2 (en) | Computer system, computer program product and method for assessing a profile of a computer system | |
| CN105740093A (en) | Backup Method, Pre-Testing Method For Environment Updating And System Thereof | |
| CN105302722B (en) | CTS automatic testing method and device | |
| CN102736978A (en) | Method and device for detecting installation status of application program | |
| CN109388569B (en) | Method for remotely detecting environmental anomaly of client, test server and storage medium | |
| CN105224458A (en) | A kind of database method of testing and system | |
| CN112445708B (en) | Pressure testing method and device and computing equipment | |
| CN111143150A (en) | Method and system for testing PCBA (printed circuit board assembly), testing equipment and micro-control unit | |
| CN105677344A (en) | Updating system of firmware of complex programmable logic device and updating method of updating system | |
| CN109543417B (en) | Vulnerability mining method and device based on Qemu platform | |
| CN111427601A (en) | Method and device for automatically upgrading BIOS in batches, computer equipment and storage medium | |
| CN112115051A (en) | Page traversal detection method, device and equipment for application and readable storage medium | |
| CN110990289B (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| US20190370116A1 (en) | Index based smart folder scan system and method for cloud-computing provider network | |
| CN110688305B (en) | Test environment synchronization method, device, medium and electronic equipment | |
| CN115269399A (en) | Equipment stability testing method and device, computer equipment and storage medium | |
| CN102841825A (en) | Drive backup method and device and drive restoration method and device | |
| CN106603289A (en) | LMT configuration file smooth upgrade method | |
| CN111857771A (en) | Deep learning-based automatic operating system patch installation method and system | |
| CN109146096B (en) | Processing method and device for repair event, storage medium and electronic equipment | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170111 |
|
| RJ01 | Rejection of invention patent application after publication |