Use of replicated copies to improve database backup performance
US-2015378830-A1 · Dec 31, 2015 · US
US9323822B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9323822-B2 |
| Application number | US-201113637349-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2011 |
| Priority date | Sep 1, 2010 |
| Publication date | Apr 26, 2016 |
| Grant date | Apr 26, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present invention relates to a mobile terminal technology. The present invention discloses a data back method and device for a mobile terminal. Since the data backup method and device of the mobile terminal provided in the present invention encodes a data in the mobile terminal into UTF-8 and stores it in the xml file, it is quite convenient to back up the data in the mobile terminal to the xml file. It is also beneficial for a user to manage the data in the mobile terminal. The present invention provides convenience for the user, the operation is simple, and the backup is easy to be done.
Opening claim text (preview).
What is claimed is: 1. A data backup method for a mobile terminal, comprising steps of: A. checking whether an xml file name and its file path used to store a backup data are validated or not, going to Step F if not validated, or else, creating an xml file and going to Step B, the xml file being used to store the backup data for the mobile terminal, the backup data being classified into a plurality of classifications including a phone book data, a short message data, and a multimedia message data; B. determining whether to export the phone book data from the mobile terminal to the xml file or not, if yes, go to a phone book data backup process to read a phone book entry from the mobile terminal and write it to the created xml file as the phone book data, and if not, turn to Step C for entering a short message export determination; C. determining whether to export the short message data from the mobile terminal to the xml file or not, if yes, go to a short message data backup process to read a short message entry from the mobile terminal and write it to the created xml file as the short message data, and if not, turn to Step D for entering a multimedia message export determination; D. determining whether to export the multimedia message data from the mobile terminal to the xml file or not, if not, go to Step F, and if yes, go to a multimedia message data backup process to read a multimedia message entry from the mobile terminal and write it to the created xml file as the multimedia message data; E. determining whether all the data backup processes are accomplished or not, if not, go back to Step B for proceeding next determination, and if yes, go to Step F; and F. terminating the whole process. 2. The data backup method according to claim 1 , wherein the phone book data backup process in Step B comprises steps of: B1. encoding the phone book entry that has been read into UTF-8 and writing it to the created xml file; and B2. determining whether the phone book data backup process is accomplished or not, if not, go back to Step B1, and if yes, go to Step E. 3. The data backup method according to claim 1 , wherein the short message data backup process in Step C comprises steps of: C1. encoding the short message entry that has been read into UTF-8 and writing it to the created xml file; and C2. determining whether the short message data backup process is accomplished or not, if not, go back to Step C1, and if yes, go to Step E. 4. The data backup method according to claim 1 , wherein the multimedia message data backup process in Step D comprises steps of: D1. encoding the multimedia message entry into UTF-8 and writing it to the created xml file; and D2. determining whether the multimedia message data backup process is accomplished or not, if not, go back to Step D1, and if yes, go to Step E. 5. The data backup method according to claim 1 , wherein UTF-8 is adopted to encode the created xml file. 6. The data backup method according to claim 1 , wherein the phone book data comprises one or more of a last name data, a first name data, a cell phone number data, a home telephone number data, an office telephone number data, and an email address data. 7. The data backup method according to claim 1 , wherein the short message data comprises a sender phone number data, a short message receiving time data, and/or a message content data, and the multimedia message data comprises a sender phone number data, a multimedia message receiving time data, a text message content data, an image file path data, a video file path data, and/or an audio file path data. 8. A data backup device for a mobile terminal, comprising: an xml file checking module, for checking whether an xml file name and its file path used to store a backup data are validated or not; an xml file creating module, for creating an xml file when the xml file name and its file path used to store the backup data are validated, the xml file being used to store the backup data for the mobile terminal, the backup data being classified into a plurality of classifications including a phone book data, a short message data, and a multimedia message data; a phone book data backup module, for determining whether to export the phone book data from the mobile terminal to the xml file or not, if yes, go to a phone book data backup process to read a phone book entry from the mobile terminal and write it to the created xml file as the phone book data; a short message backup module, for determining whether to export the short message data from the mobile terminal to the xml file or not, if yes, go to a short message data backup process to read a short message entry from the mobile terminal and write it to the created xml file as the short message data; a multimedia message backup module, for determining whether to export the multimedia message data from the mobile terminal to the xml file or not, if yes, go to a multimedia message data backup process to read a multimedia message entry from the mobile terminal and write it to the created xml file as the multimedia message data; and a backup checking module, for determining whether all the data backup processes are accomplished or not, if yes, terminate the whole process. 9. The data backup device according to claim 8 , wherein the phone book data backup module comprises: a phone book data reading unit, for reading the phone book entries one by one; a phone book data writing unit, for encoding the phone book entry that has been read into UTF-8 and writing it to the created xml file; and a phone book data determining unit, for determining whether the phone book data backup process is accomplished or not. 10. The data backup device according to claim 8 , wherein the short message data backup module comprises: a short message data reading unit, for reading the short message entries one by one; a short message data writing unit, for encoding the short message entry that has been read into UTF-8 and writing it to the created xml file; and a short message data determining unit, for determining whether the short message data backup process is accomplished or not, and the multimedia message data backup module comprises: a multimedia message data reading unit, for reading the multimedia message entries one by one; a multimedia message data writing unit, for encoding the multimedia message entry that has been read into UTF-8 and writing it to the created xml file; and a multimedia message data determining unit, for determining whether the multimedia message data backup process is accomplished or not. 11. A data backup method for a mobile terminal, comprising steps of: creating an xml file, which is used to store backup data for the mobile terminal, the backup data being classified into a plurality of classifications including a phone book data, a short message data, and a multimedia message data; encoding the xml file into a code suitable for the mobile terminal to store; and reading one of a phone book entry, a short message entry, and a multimedia message entry from the mobile terminal and write it to the created xml file as the phone book data, the short message data, or the multimedia message data. 12. The data backup method according to claim 11 , further comprising checking whether all the classifications of the backup data have been completely exported from the mobile terminal to the created xml file. 13. The data backup method according to claim 11 , wherein UTF-8 is adopted to encode the created xml file. 14. The data backup method according to claim 11 , wherein each class
Physics · mapped topic
of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML (content-based retrieval of web data G06F16/95) · CPC title
by selection of backup contents · CPC title
Asynchronous replication or reconciliation · CPC title
for networked environments · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.