CN107220315A - The user data protection method that database degrades during a kind of APP version updatings - Google Patents
The user data protection method that database degrades during a kind of APP version updatings Download PDFInfo
- Publication number
- CN107220315A CN107220315A CN201710343960.1A CN201710343960A CN107220315A CN 107220315 A CN107220315 A CN 107220315A CN 201710343960 A CN201710343960 A CN 201710343960A CN 107220315 A CN107220315 A CN 107220315A
- Authority
- CN
- China
- Prior art keywords
- database
- version
- data
- user data
- name
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
- G06F16/2329—Optimistic concurrency control using versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to the user data protection method that database during a kind of APP version updatings degrades, comprise the following steps：Step 1, current mounted database name and database version number are obtained；Step 2, obtain database name to be mounted and database version number；Step 3, current mounted database name is judged and whether database name to be mounted is identical；It is identical, then go to step 4；Step 4, current mounted database version number and the similarities and differences by database version number to be mounted are judged；Or operation, or database upgrade are not updated to database, or database degrades；The table of database, the naming rule of table is：Prefix _ table name _ suffix, wherein suffix are equal to database version number.The present invention, using simple, can effectively protect user data, it is to avoid the caused user data loss problem because database degrades.
Description
Technical field
The present invention relates to user data protection technique field, specifically database degrades during a kind of APP version updatings
User data protection method.
Background technology
In android system, light-weight database SQLite, SQLite are built-in with even without installation and starts clothes
Business process, it is the database file that a suffix is .db, but it supports SQL statement.
Use on SQLite needs a SQLiteDataBase class, and such bottom is exactly a database file,
One such represent a database, the operation to database will also pass through SQLiteDataBase classes.SQLiteDatabase
The class wrapper API of certain operations databases, can be added using such with complete paired data（Create）, inquiry
（Retrieve）, update（Update）And deletion（Delete）Operation.
SQLiteOpenHelper classes are an abstract class for being used for the establishment of Added Management database and edition upgrading problem.
We can inherit this abstract class, realize that its certain methods to carry out self-defining operation to database.Following two method
It must rewrite：
public void onCreate（SQLiteDatabase db）
public void onUpgrade（SQLiteDatabase db, int oldVersion, int newVersion）
onCreate：It is that user installs startup after application first to call opportunity, or removes startup after App database files.This
When the establishment of initial tables of data can be completed in this function.
onUpgrade：It is that user is being done using updating to call opportunity, and covering starts after installing, if data in redaction
Storehouse version number calls than the database version Gao Zehui in legacy version.At this moment version database can be completed in this function
The compatibling problem for the legacy version that this upgrading is brought, and data migration problems.
With the getWritableDatabase in SQLiteOpenHelper classes（）And getReadableDatabase（）
Method can obtain the reference of database.
Also one need not generally rewrite, but reverse degrade occurs in application（As application is degraded by version number 4
The bag that version number is 3 is installed）The method onDowngrade that Shi Bixu is rewritten, does not rewrite when if application degrades, covering is installed
Party's rule can collapse.
Other SQLiteOpenHelper subclasses necessarily refer to determine the title of current database when constructing example（name）, version
This number（version）.And file name when title just determines database purchase here, and version number here exists with App
The versionCode that AndroidMainfest.xml is defined definitely is not associated.If the database namely when App updates
Data structure not as changing the version number of database be then increased without.
Database do upgrade when we can clearly know it is current we to carry out which type of operation comes to each old table
Compatible redaction.But if when database degrades, situation is just different.For example：
Develop version 2（Relative to version 1, this is a redaction）When, we can not clearly know later redaction（Than
Such as version 3, edition 4）Database structure trend what kind of is.At this moment, when user from version 3 return back to version 2, due to version
2 can not predict the table structure of version 3 at that time in exploitation, it is not known that can the tables of data of version 3 compatible arrive version 2（If version 3
Deleted during upgrading a version 2 always literary name section, at this moment rollback data structure may just it is incompatible）.
Therefore, degraded operation likely results in the loss of user data, and this may bring irremediable damage to user
Lose, the problem has clearly a need for solving, to avoid influenceing experience and the safety of user data of user.
Alternatively possible situation is：Sometimes certain APP has automatically carried out updating operation, but user may feel still
Early version is handy, therefore still wants to gain early version, but thinks retention data, it is undesirable to because gain early version cause data by
Loss.
The content of the invention
For defect present in prior art, it is an object of the invention to provide database during a kind of APP version updatings
The user data protection method of degradation, using simple, can effectively protect user data, it is to avoid because database is used caused by degrading
User data loses problem.
To achieve the above objectives, the present invention is adopted the technical scheme that：
The user data protection method that database degrades during a kind of APP version updatings, it is characterised in that comprise the following steps：
Step 1, current mounted database name and database version number are obtained；
Step 2, obtain database name to be mounted and database version number；
Step 3, current mounted database name is judged and whether database name to be mounted is identical；
It is identical, then go to step 4；
Difference, then：The data that recording step 1 and step 2 are obtained, turn corresponding processing；
Step 4, current mounted database version number and the similarities and differences by database version number to be mounted are judged；
Identical, then database is directly continued to use, and operation is not updated to database；
Database upgrade, then：Go to step 5；
Database degrades, then：Go to step 6；
Step 5, database upgrade, carries out Data Migration in the following ways：
Step 5.1, the table of the database corresponding to redaction is created in database, the naming rule of table is：Prefix _ table name _
Suffix, wherein suffix are equal to database version number,
Step 5.2, by corresponding to the user data in the table of the database of legacy version, moved to and corresponded to by the way of duplication
The table of the database of redaction；
Step 6, database degrades, and Data Migration is carried out in the following ways：
Step 6.1, quantity and the name of table of the table for the database for corresponding to legacy version are obtained；
Step 6.2, according to the name of table, judge whether there is the table in database one by one, to without table create, the life of table
Name rule be：Prefix _ table name _ suffix, wherein suffix are equal to database version number.
On the basis of above-mentioned technical proposal, APP quickly judges the data of which version of table correspondence according to suffix
Storehouse.
On the basis of above-mentioned technical proposal, when storing each pen data in table, the creation time of the data is recorded；
When updating each pen data in table, the renewal time of the data is recorded；
The date and time of data storage qurush level in database,
Data storage storehouse degrades in database date and time.
On the basis of above-mentioned technical proposal, with reference to the date and time of upgrading, it is after upgrading to judge which data
New data, which data are the legacy datas before upgrading；
With reference to the date and time of degradation, it is the new data after degrading to judge which data, and which data is old before degrading
Data.
On the basis of above-mentioned technical proposal, when obtaining user data：
Mode one, according to currently mounted database version number, the naming rule group of table is pressed as suffix and table name
Close, obtain current version table, directly obtain user data from current version table；
Mode two, determines whether that the table that table name is identical, suffix is more than current mounted database version number is present,
If any then, the table is updates version table, now：
The list item title in current version table is further obtained, is inquired about one by one in version table is updated,
There is corresponding list item then to read the user data wherein recorded,
A default value is then returned as user data without correspondence list item；
Such as nothing, then terminate to obtain user data.
On the basis of above-mentioned technical proposal, using the date and time or the date and time of degradation of upgrading, contrast is worked as
Whether preceding time, auxiliary judgment there may exist renewal version table.
On the basis of above-mentioned technical proposal, pass through try/catch（）To catch the exception, turn respective handling.
The user data protection method that database degrades during APP version updatings of the present invention, can be effective using simple
Protect user data, it is to avoid the caused user data loss problem because database degrades.
Embodiment
The user data protection method that database degrades during APP version updatings of the present invention, comprises the following steps：
Step 1, current mounted database name and database version number are obtained；
For example：Certain APP having been mounted among mobile phone, currently mounted database name and database version number have been for it：
DATABASE_NAME = "Xx_crm.db"；
DATABASE_VERSION = 3；
Step 2, obtain database name to be mounted and database version number；
For example：Certain APP described in when step 1 is illustrated is, it is necessary to reinstall, then the installation kit of certain APP may have following feelings
Condition occurs, certainly, it is also possible to there is other situations, is not belonging to the present invention and scope is discussed；
Situation 1：
DATABASE_NAME = "Xx_crm.db"；
DATABASE_VERSION = 4；
Obviously this is the situation for belonging to database upgrade；
Situation 2：
DATABASE_NAME = "Xx_crm.db"；
DATABASE_VERSION = 2；
Obviously this is the situation for belonging to database degradation；
Step 3, current mounted database name is judged and whether database name to be mounted is identical；
It is identical, then go to step 4；
Difference, then：The data that recording step 1 and step 2 are obtained, turn corresponding processing；
Corresponding processing can be set according to actual needs, be not belonging to the present invention and scope is discussed；For example：Can simply it provide
Report an error prompting, can also terminate the installation process of the installation kit of certain APP, or carry out corresponding fault-tolerant processing, etc.；
Step 4, current mounted database version number and the similarities and differences by database version number to be mounted are judged；
Identical, then database is directly continued to use, and operation is not updated to database；
Database upgrade, then：Go to step 5；
Database degrades, then：Go to step 6；
Step 5, database upgrade, carries out Data Migration in the following ways：
Step 5.1, the table of the database corresponding to redaction is created in database, the naming rule of table is：Prefix _ table name _
Suffix, wherein suffix are equal to database version number,
Step 5.2, by corresponding to the user data in the table of the database of legacy version, moved to and corresponded to by the way of duplication
The table of the database of redaction；
Thus：
During database upgrade, it is clear that the table corresponding to the database of redaction is non-existent, is required for being created,
First, complete reservation can be given corresponding to the table of the database of legacy version, is changed without any, because suffix can be with
Table is distinguished, is so also effectively kept corresponding to existing subscriber's data in the table of the database of legacy version；
Second, the migrating data by the way of duplication, then the table corresponding to the database of redaction perfectly contain original
Data, follow-up additions and deletions change to look into directly to be carried out in the table corresponding to the database of redaction, is not on the one hand interfered with pair
Should be in the user data in the table of the database of legacy version, additions and deletions of two aspects to data, which change, looks into and will not have a negative impact；
3rd, although be replicate mode migrating data, be actually also the user data of old specification has been carried out it is stylistic
Upgrading, complies with the call format of the user data of new spec；
For example：Corresponding to the table of the database of legacy version, " T_table_2 " is named as, it is 2 that it, which corresponds to database version number,
Database；
For example：Corresponding to the table of the database of redaction, " T_table_3 " is named as, it is 3 that it, which corresponds to database version number,
Database；
In " T_table_2 " table and " T_table_3 ", the field of table is identical or variant, but contributes to store certain class data,
For example：Contribute to storage student name, sex, grade, student number；
Obviously, according to suffix, APP can also know that the table is suitable for the APP of which version and used；
Step 6, database degrades, and Data Migration is carried out in the following ways：
Step 6.1, quantity and the name of table of the table for the database for corresponding to legacy version are obtained；
Step 6.2, according to the name of table, judge whether there is the table in database one by one, to without table create, the life of table
Name rule be：Prefix _ table name _ suffix, wherein suffix are equal to database version number；
Thus：
First, when database degrades, corresponding to the table of the database of legacy version, it is possible to existing, it is also possible to by user
Delete, then need according to circumstances to decide whether to create；
Second, during degraded operation, it will not correspond to legacy version corresponding to the user data write-in in the table of the database of redaction
Database table,
First, the database after upgrading, the field of table or has been varied from, data of the user data write-in corresponding to legacy version
The table in storehouse is possible to instead result in loss of data or confusion, since it is also retained in the table corresponding to the database of redaction,
That wouldn't can just be handled；
Second, once being write, it is unfavorable that the user data in the table corresponding to the database of legacy version may be produced, and maintains
Legacy data is in the table corresponding to the database of legacy version, new data in the table corresponding to the database of redaction, more favorably
Arrangement, maintenance in data.
Degraded operation is primary concern is that non-existent table should be re-created, to avoid the database of legacy version because endless
Operation that is whole and influenceing APP, meanwhile, avoid the user data of new and old specification to mix as far as possible.
In the naming rule of above-mentioned table, suffix is equal to database version number, then according to the suffix, can quickly judge this
Table corresponds to the database of which version, is conducive to the maintenance and processing of data, can effectively improve treatment effeciency.
On the basis of above-mentioned technical proposal, when storing each pen data in table, the creation time of the data is recorded；
When updating each pen data in table, the renewal time of the data is recorded；
The date and time of data storage qurush level in database,
Data storage storehouse degrades in database date and time.
The benefit of this scheme is：
With reference to the date and time of upgrading, it can be determined that it is the new data after upgrading to go out which data, before which data is upgrading
Legacy data；
With reference to the date and time of degradation, it can be determined that it is the new data after degrading to go out which data, before which data is degradation
Legacy data.
For example：
The data of first record, then creation time be equal to renewal time be equal to the first record time；
There are the data of modification, then creation time is constant, renewal time is equal to modification time；
The judgement of passage time node, can quickly distinguish new legacy data, and then judge that changing data from additions and deletions in which table is advisable.
On the basis of above-mentioned technical proposal, when obtaining user data：
Mode one, according to currently mounted database version number, the naming rule group of table is pressed as suffix and table name
Close, obtain current version table, directly obtain user data from current version table；
Mode two, determines whether that the table that table name is identical, suffix is more than current mounted database version number is present,
If any then, the table is updates version table, now：
The list item title in current version table is further obtained, is inquired about one by one in version table is updated,
There is corresponding list item then to read the user data wherein recorded,
A default value is then returned as user data without correspondence list item；
Such as nothing, then terminate to obtain user data.
Further, using the date and time or the date and time of degradation of upgrading, current time, auxiliary judgment are contrasted
Whether renewal version table there may exist.
On the basis of above-mentioned technical proposal, pass through try/catch（）To catch the exception, turn respective handling.
The content not being described in detail in this specification belongs to prior art known to professional and technical personnel in the field.
Claims (7)
1. the user data protection method that database degrades during a kind of APP version updatings, it is characterised in that comprise the following steps：
Step 1, current mounted database name and database version number are obtained；
Step 2, obtain database name to be mounted and database version number；
Step 3, current mounted database name is judged and whether database name to be mounted is identical；
It is identical, then go to step 4；
Difference, then：The data that recording step 1 and step 2 are obtained, turn corresponding processing；
Step 4, current mounted database version number and the similarities and differences by database version number to be mounted are judged；
Identical, then database is directly continued to use, and operation is not updated to database；
Database upgrade, then：Go to step 5；
Database degrades, then：Go to step 6；
Step 5, database upgrade, carries out Data Migration in the following ways：
Step 5.1, the table of the database corresponding to redaction is created in database, the naming rule of table is：Prefix _ table name _
Suffix, wherein suffix are equal to database version number,
Step 5.2, by corresponding to the user data in the table of the database of legacy version, moved to and corresponded to by the way of duplication
The table of the database of redaction；
Step 6, database degrades, and Data Migration is carried out in the following ways：
Step 6.1, quantity and the name of table of the table for the database for corresponding to legacy version are obtained；
Step 6.2, according to the name of table, judge whether there is the table in database one by one, to without table create, the life of table
Name rule be：Prefix _ table name _ suffix, wherein suffix are equal to database version number.
2. the user data protection method that database degrades during APP version updatings as claimed in claim 1, it is characterised in that：
APP quickly judges the database of which version of table correspondence according to suffix.
3. the user data protection method that database degrades during APP version updatings as claimed in claim 1, it is characterised in that：
When storing each pen data in table, the creation time of the data is recorded；
When updating each pen data in table, the renewal time of the data is recorded；
The date and time of data storage qurush level in database,
Data storage storehouse degrades in database date and time.
4. the user data protection method that database degrades during APP version updatings as claimed in claim 3, it is characterised in that：
With reference to the date and time of upgrading, it is the new data after upgrading to judge which data, and which data is the legacy data before upgrading；
With reference to the date and time of degradation, it is the new data after degrading to judge which data, and which data is old before degrading
Data.
5. the user data protection method that database degrades during APP version updatings as claimed in claim 3, it is characterised in that：
When obtaining user data：
Mode one, according to currently mounted database version number, the naming rule group of table is pressed as suffix and table name
Close, obtain current version table, directly obtain user data from current version table；
Mode two, determines whether that the table that table name is identical, suffix is more than current mounted database version number is present,
If any then, the table is updates version table, now：
The list item title in current version table is further obtained, is inquired about one by one in version table is updated,
There is corresponding list item then to read the user data wherein recorded,
A default value is then returned as user data without correspondence list item；
Such as nothing, then terminate to obtain user data.
6. the user data protection method that database degrades during APP version updatings as claimed in claim 5, it is characterised in that：
Using the date and time or the date and time of degradation of upgrading, current time is contrasted, whether auxiliary judgment there may exist more
Redaction table.
7. the user data protection side that database degrades during APP version updatings as described in claim 1 or 2 or 3 or 4 or 5 or 6
Method, it is characterised in that：Pass through try/catch（）To catch the exception, turn respective handling.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710343960.1A CN107220315B (en) | 2017-05-16 | 2017-05-16 | User data protection method for database degradation during APP version updating |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710343960.1A CN107220315B (en) | 2017-05-16 | 2017-05-16 | User data protection method for database degradation during APP version updating |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107220315A true CN107220315A (en) | 2017-09-29 |
| CN107220315B CN107220315B (en) | 2020-08-25 |
Family
ID=59944015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710343960.1A Active CN107220315B (en) | 2017-05-16 | 2017-05-16 | User data protection method for database degradation during APP version updating |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107220315B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729180A (en) * | 2017-09-30 | 2018-02-23 | 珠海市魅族科技有限公司 | Abnormal information processing method and processing device, computer installation and readable storage medium storing program for executing |
| CN108549672A (en) * | 2018-03-29 | 2018-09-18 | 中航技国际经贸发展有限公司 | A kind of intelligent data analysis method and system |
| CN110059096A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Data version management method, apparatus, equipment and storage medium |
| CN112016284A (en) * | 2020-08-27 | 2020-12-01 | 北京字节跳动网络技术有限公司 | Processing method and equipment of electronic form |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103324716A (en) * | 2013-06-25 | 2013-09-25 | 四川九洲电器集团有限责任公司 | Application database updating method based on Android system |
| CN103678532A (en) * | 2013-12-02 | 2014-03-26 | 中国移动（深圳）有限公司 | Alternation statement reverse analysis method, database alternating and backspacing method and database alternating and backspacing system |
| CN105630898A (en) * | 2015-12-18 | 2016-06-01 | 国云科技股份有限公司 | Method applicable to switch application database table data version |
| CN105740443A (en) * | 2016-02-01 | 2016-07-06 | 深圳市盛弘电气股份有限公司 | Android database-based data management method and device |
| US9501368B2 (en) * | 2008-09-30 | 2016-11-22 | Veritas Technologies Llc | Backing up and restoring selected versioned objects from a monolithic database backup |
-
2017
- 2017-05-16 CN CN201710343960.1A patent/CN107220315B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9501368B2 (en) * | 2008-09-30 | 2016-11-22 | Veritas Technologies Llc | Backing up and restoring selected versioned objects from a monolithic database backup |
| CN103324716A (en) * | 2013-06-25 | 2013-09-25 | 四川九洲电器集团有限责任公司 | Application database updating method based on Android system |
| CN103678532A (en) * | 2013-12-02 | 2014-03-26 | 中国移动（深圳）有限公司 | Alternation statement reverse analysis method, database alternating and backspacing method and database alternating and backspacing system |
| CN105630898A (en) * | 2015-12-18 | 2016-06-01 | 国云科技股份有限公司 | Method applicable to switch application database table data version |
| CN105740443A (en) * | 2016-02-01 | 2016-07-06 | 深圳市盛弘电气股份有限公司 | Android database-based data management method and device |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107729180A (en) * | 2017-09-30 | 2018-02-23 | 珠海市魅族科技有限公司 | Abnormal information processing method and processing device, computer installation and readable storage medium storing program for executing |
| CN107729180B (en) * | 2017-09-30 | 2020-07-03 | 珠海市魅族科技有限公司 | Abnormal information processing method and device, computer device and readable storage medium |
| CN108549672A (en) * | 2018-03-29 | 2018-09-18 | 中航技国际经贸发展有限公司 | A kind of intelligent data analysis method and system |
| CN110059096A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Data version management method, apparatus, equipment and storage medium |
| CN112016284A (en) * | 2020-08-27 | 2020-12-01 | 北京字节跳动网络技术有限公司 | Processing method and equipment of electronic form |
| WO2022042322A1 (en) * | 2020-08-27 | 2022-03-03 | 北京字节跳动网络技术有限公司 | Spreadsheet processing method and device |
| CN112016284B (en) * | 2020-08-27 | 2023-08-01 | 北京字节跳动网络技术有限公司 | Electronic form processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107220315B (en) | 2020-08-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107220315A (en) | The user data protection method that database degrades during a kind of APP version updatings | |
| US10496399B2 (en) | Using a data dictionary to determine an upgrade edition of a relational database table | |
| US8789035B2 (en) | Method and apparatus for updating firmware | |
| CN101026848B (en) | Mobile terminal and software update method | |
| US7155713B1 (en) | Componentized operating system | |
| US20070245337A1 (en) | Software-delivered dynamic persistent data | |
| CN102082730B (en) | Router upgrading method and router | |
| CN102236764B (en) | Method and monitoring system for Android system to defend against desktop information attack | |
| CN104918114B (en) | A kind of operating system update method and device | |
| CN106201614A (en) | A kind of universal method and system that multiple similar software can be carried out chain type upgrading | |
| CN107479933A (en) | A kind of application program for mobile terminal upgrade method, storage device and mobile terminal | |
| CN104899257B (en) | Data-updating method and device in Distributed Data Warehouse | |
| CN103064715A (en) | Remote upgrade method and system for automatic drive test systems | |
| CN106445663A (en) | Application data migration method and device | |
| CN109002330A (en) | A kind of method, device and equipment identifying UEFI OS startup item | |
| CN104007992A (en) | Methods and devices for program updating and starting | |
| CN112463191A (en) | File updating method and device, equipment and storage medium | |
| CN101426032B (en) | Terminal and method for Java application installation | |
| CN102938817B (en) | Storage mount achieving method and device under recovery mode of mobile phone | |
| JP4859465B2 (en) | Software updating method and mobile terminal device | |
| CN104461621B (en) | A kind of method and device of Update attribute information | |
| CN104657164A (en) | Method and device for updating and processing software | |
| CN105335182A (en) | Method and device for realizing making of upgrade patches | |
| CN105700900B (en) | A kind of method and device optimizing wireless lan function | |
| WO2016082450A1 (en) | Method for upgrading user terminal, and user terminal |
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 |