US20150127615A1 - Data backup method and system - Google Patents

Data backup method and system Download PDF

Info

Publication number
US20150127615A1
US20150127615A1 US14/415,415 US201314415415A US2015127615A1 US 20150127615 A1 US20150127615 A1 US 20150127615A1 US 201314415415 A US201314415415 A US 201314415415A US 2015127615 A1 US2015127615 A1 US 2015127615A1
Authority
US
United States
Prior art keywords
data
backup
capacity
type
backed
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.)
Abandoned
Application number
US14/415,415
Other languages
English (en)
Inventor
Tao Liang
Lin Cheng
Zheng Zhao
Ping Cheng
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Netqin Technology Co Ltd
Original Assignee
Beijing Netqin Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Netqin Technology Co Ltd filed Critical Beijing Netqin Technology Co Ltd
Assigned to BEIJING NETQIN TECHNOLOGY CO., LTD. reassignment BEIJING NETQIN TECHNOLOGY CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHENG, LIN, CHENG, Ping, LIANG, TAO, ZHAO, ZHENG
Publication of US20150127615A1 publication Critical patent/US20150127615A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80—Database-specific techniques

Definitions

  • the present disclosure relates to the field of mobile terminals, and in particular, to a data backup method and system.
  • an object of the present disclosure is to provide a data backup method and system for providing mobile terminal data with a back up method, thereby satisfying users' requirements for security.
  • the present disclosure provides a data backup method comprising:
  • step B calculating a first capacity of data having the same data type, detecting a second residual user capacity on a server side, and comparing the first capacity with the second capacity, wherein if the first capacity is greater than the second capacity, the backup process is interrupted, and if the first capacity is not greater than the second capacity, step C is performed;
  • the data type comprises any one of image, video, short message, call record, and personal contact, or any combination thereof, and wherein a personal contact comprises a contact name, a telephone number, and a personal incoming call processing manner.
  • the server side receives an instruction of requesting for data backup from the mobile terminal, and receives data uploaded by the mobile terminal.
  • the method further comprises: after the backup process is interrupted, if the user chooses to continue the backup, continuing the backup from a point where the data has been backed up.
  • the method further comprises: processing, by the server side, the uploaded data to be backed up by:
  • the present disclosure provides a data backup system comprising a display module, the system further comprising: a mobile terminal comprising an acquisition module, a calculation and processing module, and an encryption and upload module; and a server side comprising a database, wherein
  • the acquisition module is configured to receive a data type of data which is selected by a user to be backed up;
  • the calculation and processing module is configured to calculate a first capacity of data having the same data type, configured to detect a second residual user capacity on the server side, and configured to compare the first capacity with the second capacity, wherein if the first capacity is greater than the second capacity, the backup process is interrupted, and if the first capacity is not greater than the second capacity, a backup operation is performed by the encryption and upload module; and
  • the encryption and upload module is configured to encrypt and upload the data to be backed up to the database on the server side for backup;
  • the display module is configured to display a backup result after the backup is completed
  • the database is configured to store the data to be backed up.
  • the data type comprises any one of image, video, short message, call record, and personal contact, or any combination thereof
  • a personal contact comprises a contact name, a telephone number, and a personal incoming call processing manner.
  • the server side comprises a communication module configured to receive an instruction of requesting for data backup from the mobile terminal, and configured to receive data uploaded by the mobile terminal.
  • system is further configured to continue the backup from a point where the data has been backed up if the user chooses to continue the backup after the backup process is interrupted.
  • the server side further comprises a processing module configured to process the uploaded data to be backed up by:
  • FIG. 1 is a flowchart of a data backup method according to an embodiment of the present disclosure
  • FIG. 2 is a diagram of a display interface of a mobile terminal according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a data backup operation for a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 4 is a block diagram of a data backup system for a mobile terminal according to an embodiment of the present disclosure.
  • a data backup method according to an embodiment of the present disclosure, the method comprising following steps.
  • Step S 110 a data type of data which is selected by a user to be backed up is received.
  • Step S 120 a first capacity of data having the same data type is calculated, a second residual user capacity on a server side is detected, and the first capacity is compared with the second capacity. If the first capacity is greater than the second capacity, then the backup process is interrupted, and if the first capacity is not greater than the second capacity, step S 130 is performed.
  • Step S 130 the data to be backed up is encrypted and uploaded to a database on the server side for backup, and a backup result is displayed after the backup is completed.
  • the use of the above data backup method on users' personal information takes precedence. That is, the backup function can only be used after a user is authorized and properly logs in.
  • FIG. 2 illustrated is a diagram of a display interface of a mobile terminal according to an embodiment of the present disclosure.
  • the mobile terminal could be any device, which includes but not limited to a mobile phone, a tablet, a notebook computer, etc.
  • There are several options on a display interface 200 such as 210 , 220 , 230 , 240 , and 250 , etc.
  • Data types represented by these options comprise but not limited to image, video, short message, call record, and/or personal contact, etc.
  • Content of a file having the image type includes the image file per se, as well as a file name, an original path, time attributes, and/or tag attributes, etc.; content of a file having the video type includes the video file per se, as well as a file name, an original path, time attributes, and/or tag attributes, etc.; content of a file having the short message type includes a telephone number, short message content, a short message type (transmission or reception), and/or a transmission or reception time, etc.; content of a file having the call record type includes a telephone number, a type (an incoming call, an outgoing call, a missed call, a rejected call, and/or a rejection manner), time, and/or a duration, etc.; and content of a file having the personal contact type includes a contact name, a telephone number(s), and/or a personal incoming call processing manner.
  • Step S 310 data type options, for which data backup can be performed, is displayed on the display interface 200 , and a user selects any data type for which data is to be backed up.
  • the user may click the data type options by using a mouse, a keyboard, a touch screen, etc.
  • the user can only select the types, rather than a single picture, a single video, a single contact, or a single short message, etc.
  • the backup function has a setting option, which may be used by the user to modify data types for backup or to set whether the selection of the data types for backup are prompted every time the data is to be backed up.
  • Step S 320 the mobile terminal receives the data type of the data which is selected by the user to be backed up, and the user is prompted to select a backup operation.
  • the mobile terminal needs to perform some steps of detection and calculation to ensure that the data is rapidly and accurately backed up.
  • Step S 330 before the backup is formally performed, the mobile terminal first checks a network condition. The mobile terminal backs up the data to the server side preferentially through a WiFi network. If the WiFi network is unavailable, then the mobile terminal needs to prompt the user that the WiFi network is unavailable, and inquire of the user about whether to back up the data through a data network. If the data network is also unavailable, then the backup process is interrupted, and step S 380 will be performed.
  • the backup operation may be set by the user to be automatically performed when the WiFi network is started to be available.
  • the mobile terminal checks whether the WiFi network is available at a fixed time point (a time point at which the user starts the function). If it is available, the data is automatically backed up. In the automatic backup process, backup is only performed for the data types which are set by the user in the setting option to be backed up.
  • Step S 340 the mobile terminal is connected to the server side, to update information about a user capacity and a growth rate, information with regard to the files which have already been backed up is synchronized, and the files are packed.
  • users include normal users and premium users.
  • a usage space of 1 G is provided to a normal user, which has a growth rate of 0, while in addition to the usage space of 1 G, a capacity of 4 G is provided to a premium user.
  • a premium user is always in a usage state, its user capacity will grow at a rate of 1K per second.
  • the mobile terminal is connected to the server side, to synchronize the information of files which have already been backed up, and those files which have already been backed up will not be upload.
  • uniqueness of a file is determined based on MD5 values and its original path. If two files have a same MD5 value but different original paths, the files should be considered as different files, and will not be uploaded repeatedly in the backup process, but should be counted in the backup capacity;
  • the call record type, and/or the personal contact type are packed into a data package, and are combined and de-duplicated by the server side.
  • Step S 350 a first capacity of the data to be backed up by the user is calculated, and a second residual user capacity at the server side is detected.
  • Various approaches for calculating capacities of the backed-up data having different types includes: with respect to the image type, the capacity is calculated based on file sizes with a minimal unit of 1 KB, wherein if there are repeated files, the capacity needs to be calculated repeatedly; with respect to the video type, the capacity is calculated based on file sizes with a minimal unit of 1 KB, wherein if there are repeated files, the capacity needs to be calculated repeatedly; with respect to the personal contact type, the capacity calculated based on the length of text information therein with a minimal unit of 1 KB; and with respect to the short message type and the call record type, the capacity is calculated based on the length of text information therein with a minimal unit of 1 KB.
  • Step S 360 the first capacity is compared with the second residual user capacity to determine whether the first capacity is greater than the second residual user capacity, and if so, the backup process is interrupted, and step S 380 is performed; otherwise, step S 370 is performed.
  • Step S 370 the data to be backed up is encrypted and uploaded to a database on the server side for backup, and a backup result is displayed after the backup is completed.
  • the data of the mobile terminal is encrypted and stored in a self-built database, and therefore before the data is encrypted and uploaded, the data needs to be decrypted.
  • the data to be backed up may be encrypted with the HTTPS protocol, and a progress bar representing “the data is being encrypted” is displayed on the mobile terminal. After the encryption is completed, a progress bar representing “the data is being backed up” is displayed, and the data starts to be uploaded to the server side.
  • the server side receives an instruction of requesting for data backup from the mobile terminal, and receives the data uploaded by the mobile terminal. After the uploaded data is received, the server side needs to process and store the data.
  • an incremental backup processing approach is as follows. Uniqueness of the file is determined based on its MD5 value and its original path. If two files have a same MD5 value but different original paths, the files should be considered as different files, and the server side encrypts and stores the combined data to be backed up in the database.
  • an incremental backup processing approach is as follows.
  • the server side performs combination and de-duplication processes.
  • any difference in any field indicates different records.
  • an incremental backup processing approach is as follows.
  • the server side performs combination and de-duplication processes.
  • Combining rules are as follows:
  • the data package having the short message type, the call record type, and/or the personal contact type which is packed and uploaded by the mobile terminal, the data package is first unpacked by the server side to the original data, and is combined and de-duplicated together with existing data having the same type(s) on the server side, and then the server side packs, encrypts, and stores the combined data to be backed up in the database.
  • the backup process may be cancelled by the user at any time.
  • the backup process may be cancelled by clicking on a cancel button or clicking on a return key. If a part of files have been backed up, after the cancellation, a result of a size of data which has been backed up should be displayed. A situation where a part of a file has been successfully backed up does not exist.
  • the packed data should be considered as one file.
  • breakpoint resume is supported. If the user cancels the backup process or the backup process is interrupted temporarily due to network conditions, the backup process should be paused. If the user chooses to continue the backup, the backup continues from a point at which the data has just been backed up, rather than starting from the very beginning. There is no need to support breakpoint resume for a single file.
  • the backup process if the user presses the HOME key to switch to another application program, the backup process will not be interrupted. When it is switched back to the backup operation, the backup process should still be displayed.
  • a backup result is displayed by the mobile terminal. It is only needed to display a total size of the uploaded data and sizes for various data types, without displaying a specific number of files which have been backed up.
  • Step S 380 the backup process is interrupted, and the data backup operation ends.
  • data backup is a measure for security protection of user's personal information, and may be manually operated by a user or may also be configured as an automatic backup.
  • the system 400 includes a mobile terminal 400 a and a server side 400 b .
  • the mobile terminal 400 a includes a display module 410 configured to display a backup result after the backup is completed; an acquisition module 420 configured to receive a data type of data which is selected by a user to be backed up; a calculation and processing module 430 configured to calculate a first capacity of data having the same data type, detect a second residual user capacity on the server side 400 b , and compare the first capacity with the second capacity; and an encryption and upload module 440 configured to encrypt and upload the data to be backed up to a database 470 on the server side 400 b for backup.
  • the server side 400 b includes a communication module 450 configured to receive an instruction of requesting for data backup from the mobile terminal 400 a , and receive the data uploaded by the mobile terminal 400 a ; and the database 470 configured to store the data to be backed up.
  • the mobile terminal 400 a is connected to the server side 400 b , and therefore the acquisition module 420 may acquire file information from the server side 400 b , to synchronize the information of files which have already been backed up.
  • the data of the mobile terminal 400 a is encrypted and stored in a self-built database, and therefore before the data to be backed up is encrypted and uploaded for backup, the calculation and processing module 430 needs to decrypt the data, and then also needs to pack all files having the short message type, the call record type, and/or the personal contact type into a data package(s).
  • the data to be backed up is encrypted by the calculation and processing module 430 through the HTTPS protocol.
  • a data type which may be selected by the user include but not limited to image, video, short message, call record, and/or personal contact.
  • a personal contact includes a contact name, a telephone number(s), and/or a personal incoming call processing manner.
  • the system 400 is further configured to continue the backup from a point at which the data has just been backed up if the user chooses to continue the backup after the backup process is interrupted.
  • breakpoint resume is supported in the backup process. If the user cancels the backup process or the backup process is interrupted temporarily due to network conditions, the backup process should be paused. If the user chooses to continue the backup, the backup continues from a point at which the data has just been backed up, rather than starting from the very beginning. There is no need to support breakpoint resume for a single file.
  • the server side 400 b further comprises a processing module 460 configured to process the uploaded data to be backed up.
  • an incremental backup processing approach is as follows. Uniqueness of the file is determined based on its MD5 value and its original path. If two files have a same MD5 value but different original paths, the files should be considered as different files, and the processing module 460 combines the data to be backed up, and encrypts and stores the combined data to be backed up in the database 470 .
  • an incremental backup processing approach is as follows.
  • the processing module 460 performs combination and de-duplication processes. For a short message and/or a call record, any difference in any field may indicate different records.
  • an incremental backup processing approach is as follows.
  • the processing module 460 performs combination and de-duplication processes. Combining rules are as follows:
  • the data package(s) having the short message type, the call record type, and/or the personal contact type which is packed and uploaded by the mobile terminal 400 a the data package(s) is firstly unpacked by the processing module 460 into the original data, and is combined and de-duplicated together with existing data having the same type(s) on the server side 400 b , and then the processing module 460 packs, encrypts, and stores the combined data to be backed up in the database 470 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US14/415,415 2012-07-30 2013-03-14 Data backup method and system Abandoned US20150127615A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201210268471.1 2012-07-30
CN201210268471.1A CN103577280A (zh) 2012-07-30 2012-07-30 一种数据备份的方法和系统
PCT/CN2013/072606 WO2014019362A1 (zh) 2012-07-30 2013-03-14 一种数据备份的方法和系统

Publications (1)

Publication Number Publication Date
US20150127615A1 true US20150127615A1 (en) 2015-05-07

Family

ID=50027192

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/415,415 Abandoned US20150127615A1 (en) 2012-07-30 2013-03-14 Data backup method and system

Country Status (3)

Country Link
US (1) US20150127615A1 (zh)
CN (1) CN103577280A (zh)
WO (1) WO2014019362A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10860438B1 (en) * 2019-06-27 2020-12-08 EMC IP Holding Company LLC Stream level uninterrupted backup operation using an interrupt service routine approach

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105988896B (zh) * 2015-02-12 2018-01-19 广东欧珀移动通信有限公司 一种移动终端数据的备份方法及装置
CN105242993A (zh) * 2015-11-13 2016-01-13 上海斐讯数据通信技术有限公司 数据备份方法及系统
CN106484326B (zh) * 2016-09-14 2019-08-27 Oppo广东移动通信有限公司 一种数据传输处理方法及移动终端
CN106507269B (zh) * 2016-09-14 2020-02-07 Oppo广东移动通信有限公司 一种数据迁移方法及终端设备
CN106487911A (zh) * 2016-10-25 2017-03-08 广东欧珀移动通信有限公司 一种数据同步方法、装置和系统
CN107168820B (zh) * 2017-04-01 2020-12-08 华为技术有限公司 一种数据镜像方法及存储系统
CN109684903A (zh) * 2017-10-19 2019-04-26 中兴通讯股份有限公司 一种家庭网关设备、图像处理方法及系统
CN110362422A (zh) * 2018-04-11 2019-10-22 武汉海康存储技术有限公司 一种数据备份方法、装置及系统
CN113641533B (zh) * 2020-04-27 2024-03-12 青岛海信移动通信技术有限公司 终端及短信息处理方法
CN112929423A (zh) * 2021-01-25 2021-06-08 上海契云科技有限公司 一种用于终端设备数据打包的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070271314A1 (en) * 2006-05-17 2007-11-22 Samsung Electronics Co., Ltd. Data recovery method and system of mobile device
US20110072520A1 (en) * 2003-08-23 2011-03-24 Softex Incorporated System And Method For Protecting Files Stored On An Electronic Device
US20120102477A1 (en) * 2010-10-21 2012-04-26 Samsung Electronics Co., Ltd. Firmware update method and apparatus for a mobile device
US20120317379A1 (en) * 2011-06-08 2012-12-13 Microsoft Corporation Storage architecture for backup application

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100407835C (zh) * 2006-06-29 2008-07-30 宇龙计算机通信科技(深圳)有限公司 移动终端中数据的备份及恢复方法
WO2008086249A1 (en) * 2007-01-07 2008-07-17 Apple Inc. Data synchronization with host device in accordance with synchronization preferences
CN101052167A (zh) * 2007-02-14 2007-10-10 乔超 一种通信号码自动更新系统及其实现方法
CN101252703B (zh) * 2008-03-28 2012-05-30 宇龙计算机通信科技(深圳)有限公司 一种终端资料的保护方法、系统以及移动通信终端
US20110016089A1 (en) * 2009-07-16 2011-01-20 Apple Inc. Restoring data to a mobile device
CN102325026A (zh) * 2011-07-14 2012-01-18 易讯天空计算机技术（深圳）有限公司 账号密码安全加密系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110072520A1 (en) * 2003-08-23 2011-03-24 Softex Incorporated System And Method For Protecting Files Stored On An Electronic Device
US20070271314A1 (en) * 2006-05-17 2007-11-22 Samsung Electronics Co., Ltd. Data recovery method and system of mobile device
US20120102477A1 (en) * 2010-10-21 2012-04-26 Samsung Electronics Co., Ltd. Firmware update method and apparatus for a mobile device
US20120317379A1 (en) * 2011-06-08 2012-12-13 Microsoft Corporation Storage architecture for backup application

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10860438B1 (en) * 2019-06-27 2020-12-08 EMC IP Holding Company LLC Stream level uninterrupted backup operation using an interrupt service routine approach

Also Published As

Publication number Publication date
WO2014019362A1 (zh) 2014-02-06
CN103577280A (zh) 2014-02-12

Similar Documents

Publication Publication Date Title
US20150127615A1 (en) Data backup method and system
US20150161013A1 (en) Data recovery method and system
US9235713B2 (en) Method, device, and system for encrypting and decrypting image
TW201141125A (en) System for remotely erasing data, method, server, and mobile device thereof, and computer program product
CN104601325B (zh) 数据加密方法、数据解密方法、装置、设备及系统
EP2955617A1 (en) Method and device for unlocking screen, and terminal
EP3816909A1 (en) Payment processing method for offline scenario, server, and readable storage medium
WO2014201940A1 (zh) 拍照方法、装置和存储介质
US20160088151A1 (en) Communication method, apparatus, and system
CN106341371A (zh) 云存储数据的加密方法及其系统
CN104866389A (zh) 基于移动操作系统的数据备份及恢复方法、装置及系统
CN104065681B (zh) 对附件中的加密压缩包进行预览的方法和系统
CN110855833A (zh) 终端找回方法、装置、终端及存储介质
US20150149528A1 (en) Methods, Systems and Apparatus to Determine a Distributed Content Share Storage Scheme
CN103246510B (zh) 一种进行系统复制和还原的方法和装置
US20130227027A1 (en) Method, system and apparatus for managing electronic subscriptions at a communication device
CN108900510A (zh) 离线数据存储方法、装置、计算机设备及存储介质
CN105426270B (zh) 一种移动终端相册数据备份方法、系统、移动终端及u盘
WO2015021438A1 (en) System and method for archiving messages
CN113296737A (zh) 随机数的生成系统、方法、装置和云端服务器
CN104703175B (zh) 移动终端的数据安全保护方法及设备
WO2013110054A1 (en) Methods and apparatus for restoring a user-selected subset of application data
EP3073360B1 (en) Multi-media data backup method, user terminal and synchronizer
CN113467989A (zh) 快照创建与读取方法、设备及存储介质
CN113132369A (zh) 一种Android手机密码自动填充方法及装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: BEIJING NETQIN TECHNOLOGY CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIANG, TAO;CHENG, LIN;ZHAO, ZHENG;AND OTHERS;REEL/FRAME:034753/0799

Effective date: 20141231

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION