WO2022001689A1 - 用户数据恢复方法、装置、终端以及计算机存储介质 - Google Patents

用户数据恢复方法、装置、终端以及计算机存储介质 Download PDF

Info

Publication number
WO2022001689A1
WO2022001689A1 PCT/CN2021/100802 CN2021100802W WO2022001689A1 WO 2022001689 A1 WO2022001689 A1 WO 2022001689A1 CN 2021100802 W CN2021100802 W CN 2021100802W WO 2022001689 A1 WO2022001689 A1 WO 2022001689A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
user data
terminal
system version
backup
Prior art date
Application number
PCT/CN2021/100802
Other languages
English (en)
French (fr)
Inventor
周雪赞
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022001689A1 publication Critical patent/WO2022001689A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • 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
    • 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/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords

Definitions

  • the embodiments of the present application relate to, but are not limited to, the technical field of information security, and specifically relate to, but are not limited to, a user data recovery method, device, terminal, and computer storage medium.
  • user data on a terminal is encrypted by default.
  • a user uses the user data, he needs to obtain an encryption key first, and then decrypt the user data through the encryption key.
  • the encryption key is not stored in plaintext, but is encrypted and protected by some encryption algorithms.
  • the user needs to obtain the encrypted encryption key according to the preset password and the relevant parameters of the terminal's software and hardware.
  • the system version update of the terminal or other factors may cause the encryption key of the user data to be unavailable, so that the user data cannot be decrypted, causing losses to the user.
  • the user data recovery method, device, terminal, and computer storage medium provided by the embodiments of the present application.
  • An embodiment of the present application provides a user data recovery method, including: acquiring terminal user data and key data to be decrypted, and acquiring an encryption key of the terminal user data based on the key data, where the key data includes an encryption factor and a key ciphertext; if the encryption key of the terminal user data cannot be obtained, the key backup file previously backed up in the terminal storage space is retrieved, and the key backup file includes the terminal system version information and corresponding key data during backup; Restore the current terminal system version to the terminal system version at the time of backup, and obtain the encryption key of the terminal user data based on the corresponding key data under the restored terminal system version, and then encrypt the terminal based on the encryption key.
  • User data is decrypted.
  • the embodiment of the present application also provides a user data recovery device, including: a user data acquisition module, configured to acquire the terminal user data and key data to be decrypted, and based on the key data, acquire the encryption key of the terminal user data, so
  • the key data includes an encryption factor and a key ciphertext
  • the key backup acquisition module is configured to retrieve the key backup file previously backed up in the terminal storage space if the encryption key of the terminal user data cannot be obtained, and the encryption key
  • the key backup file includes the terminal system version information at the time of backup and the corresponding key data
  • the user data recovery module is configured to restore the current terminal system version to the terminal system version at the time of backup, and under the restored terminal system version,
  • the encryption key of the end user data is obtained based on the corresponding key data, and then the end user data is decrypted based on the encryption key.
  • An embodiment of the present application further provides a terminal, where the terminal includes a processor, a memory, and a communication bus; the communication bus is configured to implement connection and communication between the processor and the memory; the processor is configured to execute in-memory One or more stored computer programs are used to implement the steps of the user data recovery method described above.
  • Embodiments of the present application further provide a computer storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned Steps of user data recovery method.
  • FIG. 1 is a flowchart of a method for recovering user data according to Embodiment 1 of the present application
  • FIG. 2 is a schematic diagram of a backup file list according to an embodiment of the application.
  • FIG. 3 is a flowchart of a method for decrypting an encryption key according to an embodiment of the application
  • FIG. 5 is a structural block diagram of a user data recovery apparatus according to Embodiment 2 of the present application.
  • FIG. 6 is a structural block diagram of another user data recovery apparatus according to Embodiment 2 of the present application.
  • FIG. 7 is a structural block diagram of a terminal according to Embodiment 3 of the present application.
  • the embodiment of the present application provides a user data recovery method of the embodiment, which is applied to an intelligent mobile terminal of the Android system, Such as smartphones, tablets, etc.
  • FIG. 1 is a flowchart of a method for recovering user data according to an embodiment, which includes steps S101 to S103, which are described in detail below:
  • step S101 the terminal user data and key data to be decrypted are acquired, and based on the key data, an encryption key of the terminal user data is acquired, and the key data includes an encryption factor and a key ciphertext.
  • Step S102 if the encryption key of the terminal user data cannot be obtained, the key backup file previously backed up in the terminal storage space is retrieved, and the key backup file includes the terminal system version information and corresponding key data at the time of backup.
  • Step S103 restore the current terminal system version to the terminal system version at the time of backup, under the restored terminal system version, obtain the encryption key of the terminal user data based on the corresponding key data, and then encrypt the terminal user data based on the encryption key. data is decrypted.
  • the terminal storage space includes a backup file list, and in the backup file list, the key backup files are sequentially stored in the backup file list from top to bottom according to the backup sequence.
  • Each layer stores a key backup file corresponding to the terminal system version.
  • the key backup file includes the version information and key data of the terminal system version at the time of backup.
  • the key data consists of encryption factors and key ciphertext.
  • the version information of the system version corresponds to different encryption factors and key ciphertext, and the version information, encryption factor and key ciphertext of the terminal system version in the key backup file form a one-to-one correspondence.
  • the version information of the terminal system version in this embodiment at least includes the system version number.
  • step S102 retrieving the key backup files previously backed up in the terminal storage space includes: retrieving the stored key backup files in order from bottom to top in the backup file list until the key backup files are stored in the backup file list.
  • the encryption key of the terminal user data can be obtained based on the corresponding key data under the terminal system version in the key backup file.
  • the key backup file at the upper position in the backup list corresponds to the key data backed up in an earlier system version
  • the key backup file at the lower position corresponds to the system version that is closer to the current system version.
  • the encryption key of the end user data cannot be obtained, first retrieve the key backup file stored at the lowest level in the backup file list, and parse the system version information and the key backup file stored at the lowest level.
  • Corresponding key data after restoring the current terminal system version to the system version corresponding to the recalled key backup file, obtain the encryption key based on the corresponding key data, if the encryption key can be obtained, then based on the encryption key Decrypt the end user data. If the encryption key cannot be obtained, then retrieve the key backup file stored in the lowermost layer in the backup file list, based on the system version information in the key backup file and the corresponding encryption key. The encryption key is obtained from the key data, and the cycle is repeated until the encryption key can be obtained based on the key data.
  • any existing recoverable system version can be used to restore the terminal system version, and after decrypting and restoring the user data, the terminal system version can be restored to the current terminal system version.
  • the key data corresponds to the terminal system version
  • the key data in step S101 is the key data corresponding to the current terminal system version
  • the key data in steps S102 and S103 is the terminal system version at the time of backup corresponding key data.
  • the existing symmetric encryption algorithm is used to encrypt the end user data, such as the symmetric AES encryption algorithm, the encryption key for encrypting the end user data and the encryption key for decrypting the end user data in the symmetric encryption algorithm
  • the same encryption key that is, the same encryption key is used for both encryption and decryption. Therefore, for security reasons, the encryption key cannot be stored in plain text, and the encryption key needs to be encrypted and protected.
  • the encryption key When the user needs to decrypt the user When the user data is decrypted, the encryption key must be obtained by decryption before the user data can be decrypted through the encryption key. Please refer to FIG. 3.
  • FIG. 3 is a schematic flowchart of a method for decrypting an encryption key.
  • the encryption factor and the key ciphertext can jointly decrypt the encryption key protected by encryption.
  • Ciphertext where the encryption factor is the combination of the user's preset password and the relevant parameters of the terminal software and hardware. When the relevant parameters of the terminal software and hardware change, the encryption factor will also change, and then the key ciphertext will also change. However, no matter how the encryption factor and key ciphertext change, as long as the two match, the required encryption key can be uniquely decrypted. However, in some cases, due to some uncontrollable factors when the terminal system version is updated, the update is often caused by some uncontrollable factors. The state fails, or the encryption factor or key ciphertext is destroyed by external offensive means. In these scenarios, the user cannot obtain the encryption key through the encryption factor and the key ciphertext, resulting in failure to decrypt user data.
  • the previously backed up system version corresponding to The current terminal system version is restored to the system version at the time of the backup, and the encryption key is obtained based on the encryption factor and key ciphertext of the corresponding system version under the restored system version, so that the terminal The user data is decrypted and the user data is recovered.
  • FIG. 4 which also includes steps S104 and S105, which are specifically described below:
  • Step S104 monitoring whether the terminal system version is updated.
  • the version information of the terminal system version can be obtained through regular polling, and the version information includes at least the version number, and whether the system version is updated is detected by comparing whether the version number obtained each time is the same as the version number obtained last time, If it is different from the last version number, the terminal system version is updated; otherwise, the terminal system version is not updated.
  • the system data storage area in which the terminal system version information is stored may be monitored through data backup software installed on the terminal, and subsequent operations may be performed.
  • Step S105 if the terminal system version is updated, obtain the encryption factor and key ciphertext of the user data after the terminal system version is updated, and obtain the updated key data; associate the updated terminal system version information with the key data to obtain the terminal
  • the key backup file after the system version is updated, and the key backup file after the terminal system version is updated is backed up in the terminal storage space.
  • the key backup files are sequentially stored in the backup file list from top to bottom according to the backup sequence.
  • each layer in the backup file list stores a key backup file corresponding to the terminal system version, wherein the key backup file includes version information and key data of the terminal system version at the time of backup, and the key data consists of Encryption factor and key ciphertext.
  • the version information of different terminal system versions corresponds to different encryption factors and key ciphertext.
  • the version information, encryption factor and key ciphertext of the terminal system version form a one-to-one correspondence. For example, version 1->encryption factor 1->key ciphertext 1 is the encryption factor 1 and key ciphertext 1 corresponding to version 1 of the terminal system version.
  • backing up the updated key backup file of the terminal system version to the terminal storage space in step S105 includes: judging whether the number of key backup files stored in the backup file file list is greater than a preset threshold, and if greater than If the preset threshold is set, the top key backup file in the backup file list will be deleted, the rest of the key backup files will be moved up in sequence, and the updated key backup file of the terminal system version will be stored at the bottom of the backup file list; otherwise, Directly store the updated key backup file of the terminal system version in the top layer among all the free layers in the backup file list.
  • the backup file list is optimally 3-5 layers, that is, it can store 3-5 key backup files at most, so the preset threshold in this embodiment is optimally 2-4.
  • the key backup file list When storing the key backup file to the backup file list, if the number of key backup files in the backup file list does not exceed the preset threshold, there is still free space in the surface backup file list to store the key backup file. If the backup file list is empty, directly store the key backup file in the top layer of the backup file list, or in the backup file list. When only one key backup file is stored, the newly backed up key backup file is stored in the second layer from top to bottom in the backup file list. If the number of key backup files in the backup file list is greater than the preset threshold, it means that the key backup files in the backup file list are full. The key backup files are moved up one by one. At this time, the bottom layer in the backup file list will be free, and the newly backed up key backup file will be stored at the bottom layer.
  • the terminal storage space in this embodiment may be a certain space in the internal storage of the terminal itself, or may be a cloud backup space preset by the user.
  • the associated updated system version information, encryption factor and key ciphertext are backed up in the terminal storage space, so that each system version of the terminal has a corresponding backup key data, so that the backup key data and the corresponding system version information can be quickly retrieved when the user data is restored later.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 5 is a structural block diagram of a user data recovery apparatus according to an embodiment, which includes a user data acquisition module 101 , a key backup acquisition module 102 and a user data recovery module 103 .
  • the user data acquisition module 101 is configured to acquire terminal user data and key data to be decrypted, and based on the key data, acquire an encryption key of the terminal user data, and the key data includes an encryption factor and a key ciphertext.
  • the existing symmetric AES encryption algorithm is used to encrypt and decrypt the data used by the terminal.
  • the key backup obtaining module 102 is configured to retrieve the key backup file previously backed up in the terminal storage space if the encryption key of the terminal user data cannot be obtained, and the key backup file includes the terminal system version information and Corresponding key data, the key data is used to obtain the encryption key of the end user data.
  • the terminal storage space includes a backup file list, and in the backup file list, the key backup files are sequentially stored in the backup file list from top to bottom according to the backup sequence.
  • the key backup acquisition module 102 is configured to retrieve the key backup files previously backed up in the terminal storage space, including: the key backup acquisition module 102 sequentially retrieves the stored key backup files from bottom to top in the backup file list. until the encryption key of the end user data can be obtained based on the corresponding key data under the terminal system version in the retrieved key backup file.
  • the key backup file at the upper position in the backup list corresponds to the key data backed up in an earlier system version
  • the key backup file at the lower position corresponds to the system version that is closer to the current system version. key data.
  • any existing system version recoverable manner may be used to restore the terminal system version.
  • the user data recovery module 103 is configured to restore the current terminal system version to the terminal system version at the time of backup, and under the restored terminal system version, obtain the encryption key of the terminal user data based on the corresponding key data, and then obtain the encryption key of the terminal user data. End user data is decrypted based on the encryption key.
  • this embodiment further includes a version update monitoring module 104 and a key file backup module 105 , through which the backup operation of the key backup file is completed.
  • the version update monitoring module 104 is configured to monitor whether the terminal system version is updated.
  • the key file backup module 105 is configured to, if the terminal system version is updated, obtain the encryption factor and key ciphertext of the user data after the terminal system version is updated, and obtain the updated key data; The data is correlated, the key backup file after the terminal system version is updated is obtained, and the key backup file after the terminal system version is updated is backed up in the terminal storage space.
  • the key backup files are stored in the backup file list from top to bottom according to the backup sequence, and the version information of the terminal system version, the encryption factor and the key ciphertext in the key backup file form a one-to-one correspondence. , the higher the key backup file stored in the upper layer in the backup file list, the earlier the corresponding terminal system version.
  • the key file backup module 105 is configured to back up the key backup file after the terminal system version is updated to the terminal storage space, including: the key file backup module 105 determines the key stored in the backup file file list. Whether the number of backup files is greater than the preset threshold, if it is greater than the preset threshold, delete the top-level key backup file in the backup file list, move the remaining key backup files up in sequence, and back up the keys after the terminal system version is updated The file is stored at the bottom layer of the backup file list; otherwise, the key backup file after the version of the terminal system is updated is directly stored at the top layer among all the free layers in the backup file list.
  • the backup file list is optimally 3-5 layers, that is, it can store 3-5 key backup files at most, so the preset threshold in this embodiment is optimally 2-4.
  • the terminal storage space in this embodiment may be a certain space in the internal storage of the terminal itself, or may be a cloud backup space preset by the user.
  • the terminal system version by monitoring whether the terminal system version is updated, after associating the corresponding encryption factor and key ciphertext under the updated terminal system version with the updated version information, the associated updated system version information, encryption factor and The key ciphertext is backed up in the terminal storage space, so that each system version of the terminal is backed up with a corresponding key data, so that the backup key data and the corresponding system version information can be quickly retrieved when the user data is restored later.
  • the encryption corresponding to the previously backed up system version is retrieved factor and key ciphertext, and restore the current terminal system version to the system version at the time of the backup.
  • the encryption key is obtained based on the encryption factor and key ciphertext of the corresponding system version, so that the end user data Decryption and recovery of user data.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • This embodiment also provides a terminal, as shown in FIG. 7 , which includes a processor 201, a memory 202, and a communication bus 203, wherein:
  • the communication bus 203 is configured to realize the connection communication between the processor 201 and the memory 202;
  • the processor 201 is configured to execute one or more computer programs stored in the memory 202 to implement at least one step of the user data recovery method in the first embodiment above.
  • the present embodiments also provide a computer-readable storage medium embodied in any method or technology for storing information, such as computer-readable instructions, data structures, computer program modules, or other data volatile or nonvolatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory, random access memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, electrified Erasable Programmable Read-Only Memory) ), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store the desired information and that can be accessed by a computer.
  • the computer-readable storage medium in this embodiment may be used to store one or more computer programs, and the stored one or more computer programs may be executed by a processor to implement at least one of the user data recovery methods in the first embodiment above step.
  • the encryption key of the terminal user data cannot be obtained
  • the key backup file previously backed up in the terminal storage space is retrieved, and the The current terminal system version is restored to the terminal system version at the time of backup, and then the encryption key of the terminal user data is obtained by using the key data in the key backup file, and the terminal user data is decrypted based on the encryption key.
  • the implementation process avoids the problem that the encryption key of user data cannot be obtained due to terminal system version update or other factors.
  • the functional modules/units in the system, and the device can be implemented as software (which can be implemented by computer program codes executable by a computing device). ), firmware, hardware, and their appropriate combination.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components Components execute cooperatively.
  • Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • communication media typically embodies computer readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery, as is well known to those of ordinary skill in the art medium. Therefore, the present application is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Storage Device Security (AREA)

Abstract

一种用户数据恢复方法、装置、终端以及计算机存储介质，在无法获取终端用户数据的加密密钥时，通过调取之前备份在终端存储空间中的密钥备份文件，并将当前的终端系统版本恢复至备份时的终端系统版本，再利用密钥备份文件中的密钥数据来获取终端用户数据的加密密钥，基于该加密密钥对终端用户数据进行解密。

Description

用户数据恢复方法、装置、终端以及计算机存储介质
相关申请的交叉引用
本申请基于申请号为202010609569.3、申请日为2020年6月29日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于信息安全技术领域，具体而言，涉及但不限于一种用户数据恢复方法、装置、终端以及计算机存储介质。
背景技术
目前终端上的用户数据默认都是加密的，用户使用这些用户数据时需要先获取加密密钥，再通过加密密钥对用户数据进行解密。基于安全考虑，加密密钥并不是明文存储的，是通过一些加密算法进行加密保护的，用户需根据预先设置的密码和终端的软硬件相关参数来获取加密保护后的加密密钥。然而有时终端的系统版本更新或其它因素，会导致用户数据的加密密钥无法获取，从而无法解密用户数据，给用户造成损失。
发明内容
本申请实施例提供的用户数据恢复方法、装置、终端以及计算机存储介质。
本申请实施例提供一种用户数据恢复方法，包括：获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，所述密钥数据包括加密因子和钥匙密文；若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，所述密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据；将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的所述密钥数据获取终端用户数据的加密密钥，再基于所述加密密钥对终端用户数据进行解密。
本申请实施例还提供一种用户数据恢复装置，包括：用户数据获取模块，被配置为获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，所述密钥数据包括加密因子和钥匙密文；密钥备份获取模块，被配置为若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，所述密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据；用户数据恢复模块，被配置为将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的所述密钥数据获取终端用户数据的加密密钥，再基于所述加密密钥对终端用户数据进行解密。
本申请实施例还提供一种终端，所述终端包括处理器、存储器及通信总线；所述通信总线被配置为实现处理器和存储器之间的连接通信；所述处理器被配置为执行存储器中存储的一个或者多个计算机程序，以实现上述所述的用户数据恢复方法的步骤。
本申请实施例还提供一种计算机存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如上所述的用户数据恢复方法的步骤。
本申请其他特征和相应的有益效果在说明书的后面部分进行阐述说明，且应当理解，至少部分有益效果从本申请说明书中的记载变的显而易见。
附图说明
图1为本申请实施例一的一种用户数据恢复方法的流程图；
图2为本申请实施例的备份文件列表示意图；
图3为本申请实施例的解密加密密钥方法的流程图；
图4为本申请实施例一的另一种用户数据恢复方法的流程图；
图5为本申请实施例二的一种用户数据恢复装置的结构框图；
图6为本申请实施例二的另一种用户数据恢复装置的结构框图；
图7为本申请实施例三的一种终端的结构框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本申请实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
实施例一：
为了解决因终端系统版本更新或其他因素导致无法获取用户数据的加密密钥的问题，本申请实施例提供了一种实施例的用户数据恢复方法，该方法应用于安卓系统的智能移动终端上，例如智能手机、平板电脑等。
请参见图1，图1为一种实施例的用户数据恢复方法的流程图，其包括步骤S101至步骤S103，下面具体说明：
步骤S101，获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，密钥数据包括加密因子和钥匙密文。
步骤S102，若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据。
步骤S103，将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的密钥数据获取终端用户数据的加密密钥，再基于加密密钥对终端用户数据进行解密。
在一实施例中，终端存储空间包括备份文件列表，在备份文件列表中密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中，如图2所示，备份文件列表中的每一层存储有一个终端系统版本对应的密钥备份文件，其中密钥备份文件包括备份时终端系统版本的版本信息和密钥数据，密钥数据由加密因子和钥匙密文组成，不同的终端系统版本的版本信息对应于不同的加密因子和钥匙密文，在密钥备份文件中终端系统版本的版本信息、加密因子和钥匙密文形成一一对应关系。本实施例中的终端系统版本的版本信息至少包括系统版本号。
在一实施例中，步骤S102调取之前备份在终端存储空间中的密钥备份文件包括：在备份文件列表中按照从下到上的顺序依次调取所存储的密钥备份文件，直至在所调取密钥备份文件中的终端系统版本下能够基于对应的所述密钥数据获取终端用户数据的加密密钥为止。其中，在备份列表中靠上层位置的密钥备份文件对应的是更早系统版本时备份的密钥数据，靠下层位置的密钥备份文件则对应的与当前系统版本更近的系统版本时备份的密钥数据，因此若无法获取终端用户数据的加密密钥，先调取备份文件列表中最下层所储存的密钥备份文件，解析最下层所存储的密钥备份文件中的系统版本信息和对应的密钥数据，将当前的终端系统版本恢复至所调取密钥备份文件对应的系统版本后，基于对应的密 钥数据获取加密密钥，若能够获取加密密钥，则基于加密密钥解密终端用户数据，若还是无法获取加密密钥，则再调取备份文件列表中最下层的上一层所存储的密钥备份文件，基于该密钥备份文件中的系统版本信息和对应的密钥数据获取加密密钥，依此循环，直至能够基于密钥数据获取加密密钥为止。在本申请实施例中，可采用现有的任何可恢复系统版本的方式来恢复终端系统版本，待将用户数据解密恢复后，可将终端系统版本再恢复至当前终端系统版本。
本实施例中密钥数据和终端系统版本相对应，其中步骤S101中的密钥数据为当前的终端系统版本对应的密钥数据，步骤S102和步骤S103中的密钥数据为备份时终端系统版本对应的密钥数据。
在本实施例中，采用现有的对称加密算法对终端用户数据进行加密，例如对称AES加密算法，在对称加密算法中对终端用户数据进行加密的加密密钥和解密终端用户数据的加密密钥为同一加密密钥，也就是同一加密密钥既用来加密，也用来解密，因此出于安全考虑，加密密钥不能明文存储，需对加密密钥也进行加密保护，当用户需解密用户数据时，需先解密获取加密密钥，才能通过加密密钥解密用户数据。请参考图3，图3为一种解密加密密钥方法的流程示意图，加密因子和钥匙密文共同可对加密保护的加密密钥进行解密，也就是获取加密密钥需要先获取加密因子和钥匙密文，其中加密因子是用户预设密码和终端软硬件相关参数的结合，其中终端软件相关参数至少包含系统版本信息，终端硬件相关参数至少包含终端存储器的编号等信息，若用户预设密码或终端软硬件相关参数发生改变，加密因子也会随之改变，继而钥匙密文也会发生改变。但是无论加密因子和钥匙密文如何改变，只要两者相匹配，就可以唯一解密所需的加密密钥，然而在某些情况下，由于终端系统版本更新时常常会有一些不可控因素导致更新状态失败，或者外部具有攻击性的手段破坏了加密因子或钥匙密文，在这些场景下用户通过加密因子和钥匙密文无法获取加密密钥，从而导致无法解密用户数据。
因此，本申请实施例通过对终端每个系统版本的加密因子和钥匙密文进行备份，当发送上述通过加密因子和钥匙密文无法获取加密密钥的情况时，调取之前备份的系统版本对应的加密因子和钥匙密文，并将当前终端系统版本恢复至该备份时的系统版本，在恢复后的系统版本下基于对应系统版本的加密因子和钥匙密文来获取加密密钥，从而对终端用户数据进行解密，恢复了用户数据。
为了解决如何将每次更新的终端系统版本对应的密钥备份文件备份至终端存储空间中，请参考图4，其还包括步骤S104和步骤S105，下面具体说明：
步骤S104，监测终端系统版本是否更新。本实施例可通过定时轮询来获取终端系统版本的版本信息，该版本信息至少包括版本号，通过比对每次获取的版本号与上一次获取的版本号是否相同来检测系统版本是否更新，若与上一次的版本号不同，则终端系统版本更新，否则，终端系统版本未更新。在一种实施方式下，可以通过安装在终端上的数据备份软件来对终端系统版本信息所存储的系统数据存储区进行监测，并执行后续操作。
步骤S105，若终端系统版本更新，获取终端系统版本更新后用户数据的加密因子和钥匙密文，得到更新后的密钥数据；将更新后的终端系统版本信息与密钥数据相关联，得到终端系统版本更新后的密钥备份文件，将终端系统版本更新后的密钥备份文件备份至终端存储空间中。
在一实施例中，密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中。 如图2所示，备份文件列表中的每一层存储有一个终端系统版本对应的密钥备份文件，其中密钥备份文件包括备份时终端系统版本的版本信息和密钥数据，密钥数据由加密因子和钥匙密文组成，不同的终端系统版本的版本信息对应于不同的加密因子和钥匙密文，在密钥备份文件中终端系统版本的版本信息、加密因子和钥匙密文形成一一对应关系，例如版本1->加密因子1->钥匙密文1为终端系统版本的版本号1对应的加密因子1和钥匙密文1。
在一实施例中，步骤S105中将终端系统版本更新后的密钥备份文件备份至终端存储空间中包括：判断备份文件文件列表中存储的密钥备份文件的数量是否大于预设阈值，若大于预设阈值，则将备份文件列表中最上层的密钥备份文件删除，其余密钥备份文件依次上移，将终端系统版本更新后的密钥备份文件存储在备份文件列表的最下层；否则，直接将终端系统版本更新后的密钥备份文件存储在备份文件列表中所有空余层中的最上层。本实施例中，备份文件列表最优为3-5层，也就是其最多能存储3-5个密钥备份文件，因此本实施例中预设阈值最优为2至4个。在将密钥备份文件存储至备份文件列表时，若备份文件列表中的密钥备份文件数量并没有超过预设阈值，表面备份文件列表中还剩余有空闲的位置来存储密钥备份文件，此时直接将密钥备份文件存储至备份文件列表空余层的最上层即可，例如若备份文件列表为空时，则直接将密钥备份文件存储到备份文件列表的最上层，或者备份文件列表中只存储有一个密钥备份文件时，则将新备份的密钥备份文件存储到备份文件列表中从上至下的第二层。若备份文件列表中的密钥备份文件数量已大于预设阈值，表明此时备份文件列表中的密钥备份文件已存满，此时需要将最上层的密钥备份文件删除，再将其余密钥备份文件依次上移，此时备份文件列表中最下层会空余出来，则将新备份的密钥备份文件存储至最下层。
需要说明的是，本实施例中的终端存储空间可以为终端自身内部存储器中的某一空间，也可以为用户预先设置的云备份空间。
本申请实施例通过监测终端系统版本是否更新，将更新后的终端系统版本下对应的加密因子和钥匙密文与更新后的版本信息相关联后，将关联的更新后的系统版本信息、加密因子和钥匙密文备份至终端存储空间中，使得终端每个系统版本均对应备份有一个密钥数据，以便后期用户数据恢复时能够快速调取备份密钥数据以及对应的系统版本信息。
实施例二：
请参考图5，图5为一种实施例的用户数据恢复装置的结构框图，其包括用户数据获取模块101、密钥备份获取模块102和用户数据恢复模块103。
其中，用户数据获取模块101被配置为获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，密钥数据包括加密因子和钥匙密文。本实施例采用现有对称AES加密算法对终端用于数据进行加密和解密。
密钥备份获取模块102被配置为若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，所述密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据，所述密钥数据用于获取终端用户数据的加密密钥。在一实施例中，终端存储空间包括备份文件列表，在备份文件列表中密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中。
其中，密钥备份获取模块102被配置为调取之前备份在终端存储空间中的密钥备份文件包括：密钥备份获取模块102在备份文件列表中按照从下到上的顺序依次调取所存储的 密钥备份文件，直至在所调取密钥备份文件中的终端系统版本下能够基于对应的所述密钥数据获取终端用户数据的加密密钥为止。其中，在备份列表中靠上层位置的密钥备份文件对应的是更早系统版本时备份的密钥数据，靠下层位置的密钥备份文件则对应的与当前系统版本更近的系统版本时备份的密钥数据。在本申请实施例中，可采用现有的任何可恢复系统版本的方式来恢复终端系统版本。
用户数据恢复模块103被配置为将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的所述密钥数据获取终端用户数据的加密密钥，再基于加密密钥对终端用户数据进行解密。
请参考图6，本实施例还包括版本更新监测模块104和密钥文件备份模块105，通过其来完成密钥备份文件的备份操作。
其中，版本更新监测模块104被配置为监测终端系统版本是否更新。
密钥文件备份模块105被配置为若终端系统版本更新，获取终端系统版本更新后用户数据的加密因子和钥匙密文，得到更新后的密钥数据；将更新后的终端系统版本信息与密钥数据相关联，得到终端系统版本更新后的密钥备份文件，将终端系统版本更新后的密钥备份文件备份至终端存储空间中。
在一实施例中，密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中，在密钥备份文件中终端系统版本的版本信息、加密因子和钥匙密文形成一一对应关系，备份文件列表中越靠上层存储的密钥备份文件，其对应的终端系统版本越早。
在一实施例中，密钥文件备份模块105被配置为将终端系统版本更新后的密钥备份文件备份至终端存储空间中包括：密钥文件备份模块105判断备份文件文件列表中存储的密钥备份文件的数量是否大于预设阈值，若大于预设阈值，则将备份文件列表中最上层的密钥备份文件删除，其余密钥备份文件依次上移，将终端系统版本更新后的密钥备份文件存储在备份文件列表的最下层；否则，直接将终端系统版本更新后的密钥备份文件存储在备份文件列表中所有空余层中的最上层。本实施例中，备份文件列表最优为3-5层，也就是其最多能存储3-5个密钥备份文件，因此本实施例中预设阈值最优为2至4个。需要说明的是，本实施例中的终端存储空间可以为终端自身内部存储器中的某一空间，也可以为用户预先设置的云备份空间。本实施例通过监测终端系统版本是否更新，将更新后的终端系统版本下对应的加密因子和钥匙密文与更新后的版本信息相关联后，将关联的更新后的系统版本信息、加密因子和钥匙密文备份至终端存储空间中，使得终端每个系统版本均对应备份有一个密钥数据，以便后期用户数据恢复时能够快速调取备份密钥数据以及对应的系统版本信息。
本申请实施例通过对终端每个系统版本的加密因子和钥匙密文进行备份，当发生上述无法通过加密因子和钥匙密文获取加密密钥的情况时，调取之前备份的系统版本对应的加密因子和钥匙密文，并将当前终端系统版本恢复至该备份时的系统版本，在恢复后的系统版本下基于对应系统版本的加密因子和钥匙密文来获取加密密钥，从而对终端用户数据进行解密，恢复了用户数据。
实施例四：
本实施例还提供了一种终端，参见图7所示，其包括处理器201、存储器202及通信总线203，其中：
通信总线203被配置为实现处理器201和存储器202之间的连接通信；
处理器201被配置为执行存储器202中存储的一个或者多个计算机程序，以实现上述实施例一中的用户数据恢复方法中的至少一个步骤。本实施例还提供了一种计算机可读存储介质，该计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。计算机可读存储介质包括但不限于RAM(Random Access Memory，随机存取存储器),ROM(Read-Only Memory，只读存储器),EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
本实施例中的计算机可读存储介质可用于存储一个或者多个计算机程序，其存储的一个或者多个计算机程序可被处理器执行，以实现上述实施例一中的用户数据恢复方法的至少一个步骤。
根据本申请实施例提供的用户数据恢复方法、装置、终端以及计算机存储介质，在无法获取终端用户数据的加密密钥时，通过调取之前备份在终端存储空间中的密钥备份文件，并将当前的终端系统版本恢复至备份时的终端系统版本，再利用密钥备份文件中的密钥数据来获取终端用户数据的加密密钥，基于该加密密钥对终端用户数据进行解密，在某些实施过程中避免了因终端系统版本更新或其他因素导致无法获取用户数据的加密密钥的问题。
可见，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本申请不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本申请实施例所作的进一步详细说明，不能认定本申请的具体实施只局限于这些说明。对于本申请所属技术领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本申请的保护范围。

Claims (12)

  1. 一种用户数据恢复方法，包括：
    获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，所述密钥数据包括加密因子和钥匙密文；
    若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，所述密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据；
    将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的所述密钥数据获取终端用户数据的加密密钥，再基于所述加密密钥对终端用户数据进行解密。
  2. 如权利要求1所述的用户数据恢复方法，还包括：
    监测终端系统版本是否更新；
    若终端系统版本更新，获取终端系统版本更新后用户数据的加密因子和钥匙密文，得到更新后的密钥数据；将更新后的终端系统版本信息与密钥数据相关联，得到终端系统版本更新后的密钥备份文件，将终端系统版本更新后的密钥备份文件备份至终端存储空间中。
  3. 如权利要求2所述的用户数据恢复方法，其中，所述终端存储空间包括备份文件列表，所述密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中。
  4. 如权利要求3所述的用户数据恢复方法，其中，所述将终端系统版本更新后的密钥备份文件备份至终端存储空间中包括：
    判断所述备份文件文件列表中存储的密钥备份文件的数量是否大于预设阈值，若大于预设阈值，则将备份文件列表中最上层的密钥备份文件删除，其余密钥备份文件依次上移，将终端系统版本更新后的密钥备份文件存储在备份文件列表的最下层；否则，直接将终端系统版本更新后的密钥备份文件存储在备份文件列表中所有空余层中的最上层。
  5. 如权利要求3所述的用户数据恢复方法，其中，所述调取之前备份在终端存储空间中的密钥备份文件包括：
    在所述备份文件列表中按照从下到上的顺序依次调取所存储的密钥备份文件，直至在所调取密钥备份文件中的终端系统版本下能够基于对应的所述密钥数据获取终端用户数据的加密密钥为止。
  6. 一种用户数据恢复装置，包括：
    用户数据获取模块，被配置为获取待解密的终端用户数据和密钥数据，基于密钥数据，获取终端用户数据的加密密钥，所述密钥数据包括加密因子和钥匙密文；
    密钥备份获取模块，被配置为若无法获取终端用户数据的加密密钥，调取之前备份在终端存储空间中的密钥备份文件，所述密钥备份文件包括备份时的终端系统版本信息和对应的密钥数据；
    用户数据恢复模块，被配置为将当前的终端系统版本恢复至备份时的终端系统版本，在恢复后的终端系统版本下，基于对应的所述密钥数据获取终端用户数据的加密密钥，再基于所述加密密钥对终端用户数据进行解密。
  7. 如权利要求6所述的用户数据恢复装置，还包括：
    版本更新监测模块，被配置为监测终端系统版本是否更新；
    密钥文件备份模块，被配置为若终端系统版本更新，获取终端系统版本更新后用户数据的加密因子和钥匙密文，得到更新后的密钥数据；将更新后的终端系统版本信息与密钥 数据相关联，得到终端系统版本更新后的密钥备份文件，将终端系统版本更新后的密钥备份文件备份至终端存储空间中。
  8. 如权利要求7所述的用户数据恢复装置，其中，所述终端存储空间包括备份文件列表，所述密钥备份文件按照备份先后顺序从上至下依次存储在备份文件列表中。
  9. 如权利要求8所述的用户数据恢复装置，其中，所述密钥文件备份模块还被配置为判断所述备份文件文件列表中存储的密钥备份文件的数量是否大于预设阈值，若大于预设阈值，则将备份文件列表中最上层的密钥备份文件删除，其余密钥备份文件依次上移，将终端系统版本更新后的密钥备份文件存储在备份文件列表的最下层；否则，直接将终端系统版本更新后的密钥备份文件存储在备份文件列表中所有空闲层中的最上层。
  10. 如权利要求8所述的用户数据恢复装置，其中，所述密钥备份获取模块还被配置为在所述备份文件列表中按照从下到上的顺序依次调取所存储的密钥备份文件，直至在所调取密钥备份文件中的终端系统版本下能够基于对应的所述密钥数据获取终端用户数据的加密密钥为止。
  11. 一种终端，包括处理器、存储器及通信总线；
    所述通信总线被配置为实现处理器和存储器之间的连接通信；
    所述处理器被配置为执行存储器中存储的一个或者多个计算机程序，以实现如权利要求1至5中任一项所述的用户数据恢复方法的步骤。
  12. 一种计算机可读存储介质，存储有一个或者多个计算机程序，其中，所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现如权利要求1至5中任一项所述的用户数据恢复方法的步骤。
PCT/CN2021/100802 2020-06-29 2021-06-18 用户数据恢复方法、装置、终端以及计算机存储介质 WO2022001689A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010609569.3A CN113935045A (zh) 2020-06-29 2020-06-29 用户数据恢复方法、装置、终端以及计算机存储介质
CN202010609569.3 2020-06-29

Publications (1)

Publication Number Publication Date
WO2022001689A1 true WO2022001689A1 (zh) 2022-01-06

Family

ID=79273156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/100802 WO2022001689A1 (zh) 2020-06-29 2021-06-18 用户数据恢复方法、装置、终端以及计算机存储介质

Country Status (2)

Country Link
CN (1) CN113935045A (zh)
WO (1) WO2022001689A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115225272A (zh) * 2022-09-20 2022-10-21 北方健康医疗大数据科技有限公司 基于国产商用密码算法的大数据灾备系统、方法和设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115297473A (zh) * 2022-07-22 2022-11-04 杭州涂鸦信息技术有限公司 智能设备的配网方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196304A (zh) * 2010-03-19 2011-09-21 华为软件技术有限公司 视频监控中生成密钥的方法及系统、设备
CN105978686A (zh) * 2016-05-10 2016-09-28 杭州海兴电力科技股份有限公司 密钥管理方法及系统
US20160350238A1 (en) * 2015-05-31 2016-12-01 Apple Inc. Backup Accessible By Subset Of Related Devices
CN107707347A (zh) * 2017-10-27 2018-02-16 深圳市文鼎创数据科技有限公司 用户密钥的备份方法及装置、用户密钥的导入方法及装置
CN109474424A (zh) * 2018-12-17 2019-03-15 江苏恒宝智能系统技术有限公司 区块链账户密钥备份及恢复的方法、系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196304A (zh) * 2010-03-19 2011-09-21 华为软件技术有限公司 视频监控中生成密钥的方法及系统、设备
US20160350238A1 (en) * 2015-05-31 2016-12-01 Apple Inc. Backup Accessible By Subset Of Related Devices
CN105978686A (zh) * 2016-05-10 2016-09-28 杭州海兴电力科技股份有限公司 密钥管理方法及系统
CN107707347A (zh) * 2017-10-27 2018-02-16 深圳市文鼎创数据科技有限公司 用户密钥的备份方法及装置、用户密钥的导入方法及装置
CN109474424A (zh) * 2018-12-17 2019-03-15 江苏恒宝智能系统技术有限公司 区块链账户密钥备份及恢复的方法、系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115225272A (zh) * 2022-09-20 2022-10-21 北方健康医疗大数据科技有限公司 基于国产商用密码算法的大数据灾备系统、方法和设备

Also Published As

Publication number Publication date
CN113935045A (zh) 2022-01-14

Similar Documents

Publication Publication Date Title
US9141814B1 (en) Methods and computer systems with provisions for high availability of cryptographic keys
US9256499B2 (en) Method and apparatus of securely processing data for file backup, de-duplication, and restoration
US9621549B2 (en) Integrated circuit for determining whether data stored in external nonvolative memory is valid
CN109995505B (zh) 一种雾计算环境下数据安全去重系统及方法、云存储平台
US9122882B2 (en) Method and apparatus of securely processing data for file backup, de-duplication, and restoration
WO2022001689A1 (zh) 用户数据恢复方法、装置、终端以及计算机存储介质
US11595191B2 (en) Encryption key management system and encryption key management method
EP3200093B1 (en) Data synchronization method and device
US9064133B2 (en) Method and apparatus of securely processing data for file backup, de-duplication, and restoration
US9405925B2 (en) Content item encryption on mobile devices
US10089245B2 (en) Management of encryption keys for multi-mode network storage device
CN114556869B (zh) 用于加密数据的密钥管理方法、数据处理系统及存储介质
CN106681865B (zh) 业务恢复方法及装置
US20200089884A1 (en) Method and apparatus for ransomware detection
US8880904B2 (en) System and method for securing data
US11238157B2 (en) Efficient detection of ransomware attacks within a backup storage environment
US9054864B2 (en) Method and apparatus of securely processing data for file backup, de-duplication, and restoration
CN104572891A (zh) 一种用于网络信息分离存储的文件更新方法
CN110727940A (zh) 一种电子设备密码管理方法、装置、设备及存储介质
CN111143863A (zh) 一种数据处理方法、装置、设备及计算机可读存储介质
US20210050998A1 (en) Secret key updating system, secret key updating method, and secret key updating program
CN110795702A (zh) 一种软件防破解方法、装置、设备、介质
CN116628675A (zh) 密码恢复方法、装置、计算机设备、存储介质和程序产品
CN116432199A (zh) 云平台远程数据备份方法及其恢复方法、电子设备
JP2019159721A (ja) ストレージ装置、制御方法及び制御プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21831549

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 15/05/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21831549

Country of ref document: EP

Kind code of ref document: A1