CN116723203B

CN116723203B - Data backup method, data recovery method and electronic equipment

Info

Publication number: CN116723203B
Application number: CN202211235564.4A
Authority: CN
Inventors: 黄智辉
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-10-10
Filing date: 2022-10-10
Publication date: 2024-04-19
Anticipated expiration: 2042-10-10
Also published as: CN116723203A

Abstract

The application provides a data backup method, a data recovery method and electronic equipment, wherein the data backup method comprises the following steps: receiving a first token from a first server, and logging in the first server by a first account of a first user; receiving a second account number and a first password of a second user; receiving a second token from the first server when the second account number and the first password match; after receiving the second token, sending a notification; receiving backup data from the second electronic device; the first token, the second token, and the backup data are sent to the second server to cause the second server to store the backup data in accordance with the first token and the second token. Therefore, the backup and recovery of the data are realized, the privacy of the data backup is ensured, and the data backup experience of a user is improved.

Description

Data backup method, data recovery method and electronic equipment

Technical Field

The application belongs to the technical field of terminals, and particularly relates to a data backup method, a data recovery method and electronic equipment.

Background

As electronic devices become more functional, so too does the data stored in the electronic devices. For example, a mobile phone stores therein data such as pictures, videos, documents, and music. Therefore, in the event of a failure of the electronic device, or other need to empty the data in the electronic device, the data in the electronic device needs to be backed up.

Currently, when backing up data, an electronic device may backup the data to a server through a cloud backup application in the electronic device, or the electronic device may copy the data to another electronic device such that the data is backed up on the other electronic device.

However, in the implementation process, the efficiency of backing up the data is not good, or the privacy is not high, and security risks are easily generated.

Disclosure of Invention

The application provides a data backup method, a data recovery method and electronic equipment, which can improve the privacy and safety of data backup.

In a first aspect, the present application provides a data backup method, applied to a first electronic device, where the method includes: receiving a first token from a first server, logging in the first server by a first account of a first user, wherein the first account is associated with the first token; receiving a second account number and a first password of a second user, wherein the first user and the second user are different; receiving a second token from the first server when the second account matches the first password, the second token being associated with the second account; after receiving the second token, sending a notification for reminding the second electronic device to send backup data to the first electronic device; receiving backup data from the second electronic device; the first token, the second token, and the backup data are sent to the second server such that a verification notification received by the second server from the first server indicates that both the first token and the second token are verified, and the backup data is stored.

According to the method, when the second user needs to backup the data in the second electronic device, the first electronic device can acquire the first token associated with the first account number and acquire the second token associated with the second account number by means of the first server, and the first electronic device stores the backup data sent by the second electronic device to the second server to prepare the data.

After receiving the second token, the first electronic device can inform the second electronic device to send the backup data, so that the first electronic device can send the backup data to the second electronic device in time.

The backup data is data in a second electronic device which needs to be backed up by a second user.

In addition, when the second server stores backup data according to the first token and the second token, the second server can send the first token and the second token to the first server, and the first server verifies the first token and the second token respectively. When the first server determines that the first account is in a login state in the first electronic device according to the first token and the first server determines that the second account passes the identity verification in the first electronic device according to the second token, the first server notifies the second server that the first token and the second token pass the identity verification.

Therefore, the first server verifies the first token, ensures that the first account is in a login state in the first electronic device, and is convenient for the first electronic device to smoothly and continuously send backup data in the second electronic device to the second server; the first server verifies the second token, so that the second account number passes the identity verification in the first electronic device, and the first electronic device can conveniently and smoothly send backup data in the second electronic device corresponding to the second account number to the second server. That is, the first account is in a login state in the first electronic device, and the second account passes the authentication in the first electronic device, so that the first electronic device is favorable for continuously storing backup data in the second electronic device corresponding to the second account into the second server based on the first account in the login state. Therefore, the second server can receive the backup data sent by the second electronic equipment and store the backup data.

Therefore, the method realizes data backup, prepares for data recovery, ensures the privacy and safety of the data backup, and improves the data backup experience of users.

With reference to the first aspect, in certain implementation manners of the first aspect, the backup data is stored in a first storage space of the second server, and the first storage space is associated with the second account; and/or the backup data is stored in a second storage space of the second server, and the second storage space is respectively associated with the first account and the second account.

In the method, the first electronic device transmits the backup data to the second server, the second server stores the backup data in the first storage space of the second server, the first storage space is associated with the second account, and the user can conveniently recover the data according to the second account associated with the second token.

Or the first electronic device transmits the backup data to the second server, and the second server stores the backup data in a second storage space of the second server, wherein the second storage space is respectively associated with the first account number and the second account number, so that the data can be conveniently recovered according to the second account number associated with the second token or the first account number associated with the first token.

In addition, the validity period of the first token and the second token is typically one hour.

The first memory space remains valid after the old second token fails. The second memory space remains valid after the old first token fails.

Thus, the storage space may not be directly associated with the token, but rather with the account number. When the second server stores data, the backup data can be stored in a first storage space associated with the second account according to the second token, and can also be stored in a second storage space respectively associated with the first account and the second account according to the first token.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: establishing a data channel between the first electronic equipment and the second electronic equipment, wherein the data channel is used for data transmission between the first electronic equipment and the second electronic equipment; receiving backup data from a second electronic device, comprising: and receiving backup data from the second electronic device through the data channel.

And a data channel is established between the first electronic device and the second electronic device, so that the second electronic device can send the backup data to the first electronic device, and the first electronic device can receive the backup data sent by the second electronic device.

The data channels may be established via a universal serial bus (universal serial bus, USB) data line, bluetooth, or wireless network (WIRELESS FIDELITY, wiFi).

With reference to the first aspect, in certain implementations of the first aspect, the data channel is established through a USB data line.

The second electronic device transmits data to the first electronic device through the USB data line faster, and the second electronic device is not required to be in a state of transmitting data for a long time.

With reference to the first aspect, in certain implementations of the first aspect, receiving a first token from a first server and logging into the first server with a first account of a first user includes: receiving a first account number and a second password of a first user; transmitting the first account number and the second password to a first server; receiving a first token from a first server, the first token being sent by the first server upon determining that the first account number and the second password match; after receiving the first token, logging in the first server with the first account number and the second password.

The first electronic device can receive the first token when the first server determines that the first account number is matched with the second password, and after the first token is received, the first account number on the first electronic device is in a login state, so that the first electronic device can backup data of the second electronic device to the second server.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: displaying a first interface; receiving a first account number and a second password in response to a first operation in a first interface; after receiving the first token, logging in a first server with a first account in a first interface.

According to the method, the first interface is displayed, so that the first electronic equipment can receive the first account number and the second password through the first interface.

With reference to the first aspect, in certain implementations of the first aspect, when the second account number and the first password match, receiving the second token from the first server includes: sending the second account number and the first password to a first server; a second token is received from the first server, the second token being sent by the first server upon determining that the second account number and the first password match.

The first electronic device can receive the second token when the first server determines that the second account number is matched with the first password, and after the second token is received, the second account number on the first electronic device passes the authentication, so that the first electronic device can backup data of the second electronic device corresponding to the second account number to the second server.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: displaying a second interface; and receiving a second account number and a first password in response to a second operation in the second interface.

According to the method, the second interface is displayed, so that the first electronic equipment can receive the second account number and the first password through the second interface.

With reference to the first aspect, in certain implementations of the first aspect, the backup data is encrypted data.

The second electronic device encrypts the backup data and then sends the encrypted backup data to the first electronic device, so that data leakage can be avoided, and the safety of the data is ensured.

With reference to the first aspect, in certain implementations of the first aspect, the first electronic device is a personal computer PC; the second electronic equipment is a mobile phone; the first server is an account server; the second server is a backup server.

In a second aspect, the present application provides a data recovery method, applied to a third electronic device, where the method includes: logging in the first server by a second account of a second user; displaying a third interface; responding to the recovery operation on the third interface, and sending a second account number or a third token to a second server, wherein the second account number is associated with the third token; and receiving backup data from the second server, wherein the backup data is data acquired by the second server according to the second account number or the third token.

According to the method, when the second user needs to recover the data in the second electronic device, the third electronic device can acquire the backup data from the second server through the second account or the third token associated with the second account, so that the safety of data recovery is ensured.

The second electronic device and the third electronic device may be the same electronic device or different electronic devices.

With reference to the second aspect, in some implementations of the second aspect, logging in to the first server with a second account of the second user includes: receiving a second account number and a first password of a second user; sending the second account number and the first password to a first server; receiving a third token from the first server, the third token being sent by the first server upon determining that the second account number and the first password match; after receiving the third token, logging in the first server with the second account number and the first password.

The third electronic device can receive the third token when the first server determines that the second account number is matched with the first password, and the second account number on the third electronic device is in a login state after the third token is received, so that the third electronic device can restore backup data from the second server according to the second account number or the third token associated with the second account number.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: logging in the first server by the second account in the fourth interface; after logging in the first server with the second account, a third interface is displayed.

According to the method, the user can input the second account and the first password through the fourth interface, so that the second account is in a login state. Therefore, the third electronic device can display the third interface when the second account is in the login state, so that the second user can conveniently execute the recovery operation on the third interface.

With reference to the second aspect, in certain implementations of the second aspect, the backup data is encrypted data.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: and decrypting the backup data.

Since the backup data is encrypted data, decryption of the backup data is required when the backup data is restored.

In a third aspect, the present application provides an apparatus comprising one or more modules for performing the data backup method in any one of the possible designs of the first aspect and the first aspect, or for performing the data recovery method in any one of the possible designs of the second aspect and the second aspect.

In a fourth aspect, the present application provides an electronic device comprising a processor; the computer code or instructions in the memory, when executed by the processor, cause the electronic device to perform the data backup method in any one of the possible designs of the first aspect and the first aspect, or to perform the data recovery method in any one of the possible designs of the second aspect and the second aspect.

In a fifth aspect, the present application provides an electronic device comprising one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the data backup method of the first aspect and any of the possible designs of the first aspect, or the data recovery method of the second aspect and any of the possible designs of the second aspect.

In a sixth aspect, the present application provides a communication system, including a first electronic device, a third electronic device, a first server, and a second server, where the first electronic device is configured to execute the data backup method in any one of the first aspect and the possible designs of the first aspect, the third electronic device is configured to execute the data recovery method in any one of the second aspect and the possible designs of the second aspect, the third electronic device and the second electronic device may be the same electronic device or different electronic devices, and the second electronic device is an electronic device configured to send backup data to the first electronic device. The first server is used for storing and verifying account numbers and passwords, and the second server is used for backing up data.

In a seventh aspect, the present application provides a chip system comprising a processor for calling and running a computer program from a memory, such that an electronic device on which the chip system is installed performs the data backup method in any one of the possible designs of the first aspect and the first aspect, or performs the data recovery method in any one of the possible designs of the second aspect and the second aspect.

The chip system can comprise a display screen or be externally connected with the display screen. The system-on-chip may also not include a display screen.

Wherein, the chip system can comprise one chip or a plurality of chips; when a plurality of chips are included in a chip system, the present application does not limit parameters such as the type and the number of chips.

In an eighth aspect, the present application provides a computer readable storage medium comprising a computer program which, when run on an electronic device, causes the electronic device to perform the data backup method of any one of the first aspect and the possible designs of the first aspect, or to perform the data recovery method of any one of the second aspect and the possible designs of the second aspect.

In a ninth aspect, the application provides a computer program product for causing a computer to perform the data backup method of any one of the first aspect and the possible designs of the first aspect, or the data recovery method of any one of the second aspect and the possible designs of the second aspect, when the computer program product is run on the computer.

It will be appreciated that the advantages of the third to ninth aspects may be found in the relevant description of the first and/or second aspects and are not described in detail herein.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic view of a communication system according to an embodiment of the present application;

Fig. 2A-2S are schematic diagrams of a man-machine interaction interface according to an embodiment of the present application;

FIG. 3 is a flowchart of a data backup and restore method according to an embodiment of the present application;

FIG. 4 is a flowchart of a data backup method according to an embodiment of the present application;

fig. 5 is a flowchart of a data recovery method according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Wherein, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.

The terms "first," "second," "third," and the like, are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", or a third "may explicitly or implicitly include one or more such feature.

The application can provide a data backup method, a data recovery method, an electronic device, a chip system, a computer readable storage medium and a computer program product, when a user needs to backup data in one electronic device, the other electronic device can obtain the authority of the backup data through a service account by means of an account server, and obtain the authority of identity confirmation through a personal account. Therefore, the other electronic device can transmit the data, the service account number and the personal account number in one electronic device to the backup server, so that the backup server can store the data in one electronic device by means of the account number server after determining that the other electronic device acquires the two rights according to the service account number and the personal account number.

Therefore, the data backup is realized, whether the equipment for backing up the data has the backup authority is verified through the service account number and the personal account number, and the privacy of the data backup is ensured.

In addition, the backup server can store data in one electronic device through a personal account number or a service account number.

When the user needs to restore the data in one electronic device, the other electronic device can acquire the data in one electronic device from the backup server through the personal account number or the service account number.

Therefore, data recovery is realized, whether the equipment for recovering the data has the recovered authority is verified through the service account or the personal account, and the safety of data recovery is ensured.

Wherein one electronic device and another electronic device may be the same electronic device or different electronic devices.

In addition, the other electronic device may be a repair shop electronic device, or other trusted third person electronic device.

When the other electronic device is an electronic device for repairing a store, the service account number may be an account number of the repair store to which the store user belongs.

When the other electronic device is an electronic device of another trusted third person, the service account number may be an account number of the third person or an account number of a group to which the third person belongs. Such as a family account number of a family. Referring to fig. 1, fig. 1 is a schematic diagram illustrating an architecture of a communication system according to an embodiment of the application.

As shown in fig. 1, the communication system of the present application may include: electronic device 10, electronic device 20, account server 30, and backup server 40.

The data backup and recovery method provided by the application can be realized through the mutual coordination of the electronic device 10, the electronic device 20, the account server 30 and the backup server 40.

For convenience of explanation, the electronic device 10 is taken as an electronic device needing to backup data, the electronic device 20 is taken as an electronic device for backing up the data of the electronic device 10 to the backup server 40, the personal account number is an account number of a maintenance user, and the service account number is illustrated as an account number of a store to which the store user belongs.

When the maintenance user needs to backup the data in the electronic device 10, the electronic device 20 can obtain the authority of the backup data through the service account by means of the account server 30, and obtain the authority of the identity verification through the personal account. The electronic device 10 may send data to the electronic device 20 over a universal serial bus (universal serial bus, USB) data line, bluetooth, or wireless network (WIRELESS FIDELITY, wiFi). The electronic device 20 may transmit the data, the service account number, and the personal account number in the electronic device 10 to the backup server 40, so that the backup server 40 may store the data in the electronic device 10 after determining, by means of the account server, that the electronic device 20 obtains the two rights.

When a service user needs to restore data in the electronic device 10, the electronic device 10 may obtain the data in the electronic device 10 from the backup server 40 through a personal account number or a service account number.

The electronic device 10 or the electronic device 20 may be an electronic device with display hardware and corresponding software support. The type of electronic device 20 may be the same as or different from the type of electronic device 10.

For example, the electronic device 10 or the electronic device 20 may be a mobile phone, a desktop computer, a tablet computer, a wearable device, a vehicle-mounted device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a home device, or the like, and the present application is not limited to the specific type of the electronic device 10 or the electronic device 20.

For convenience of description, in fig. 1, an electronic device 10 is taken as a mobile phone, and an electronic device 20 is taken as a personal computer PC as an example. The structure of the electronic device 20 may be the same as that of the electronic device 10.

In some embodiments, the electronic device 10 may include a processor, memory, a communication module, a display screen, and the like.

The processor may include one or more processing units, among others, and the memory is used for storing program codes and data. In the present application, the processor may execute computer-executable instructions stored in the memory for controlling and managing the operation of the electronic device 10.

The communication module may be used for communication between various internal modules of the electronic device 10, communication between the electronic device 10 and other external electronic devices, or the like. By way of example, if the electronic device 10 communicates with other electronic devices by way of a wired connection, the communication module may include an interface or the like, for example, a USB interface, which may be an interface conforming to the USB standard specification, specifically, a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface may be used to connect a charger to charge the electronic device 10, or may be used to transfer data between the electronic device 10 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as augmented reality (augmented reality, AR) devices, and the like.

Or the communication module may include an audio device, a radio frequency circuit, a bluetooth chip, a wireless fidelity (WIRELESS FIDELITY, wi-Fi) chip, a near-field communication technology (NFC) module, etc., and interaction between the electronic device 10 and other electronic devices may be achieved in a variety of different manners.

The display screen can display images or videos in the human-computer interaction interface.

Optionally, the electronic device 10 may also include peripheral devices such as a mouse, keyboard, speakers, microphone, etc.

It should be understood that the present application is not limited in particular to the structure of the electronic device 10, except as to the various components or modules listed above.

In addition, the electronic device 10 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Wherein the account server 30 and the backup server 40 may be different servers. The account server 30 may be used to store and verify account numbers and passwords. The backup server 40 may be used to backup data. The type of backup server 40 may be the same as or different from the type of account server 30.

For example, the account server 30 or the backup server 40 may be a cloud server or a proprietary server, which is not particularly limited herein.

In addition, the account server 30 and the backup server 40 may be the same server.

The electronic device 10 and the electronic device 20 may communicate via a USB data line, bluetooth, wiFi, or the like. The electronic device 20 and the account server 30 may communicate over a network. Where the account server 30 and the backup server 40 are different servers, the account server 30 and the backup server 40 may communicate over a network. The electronic device 10 and the account server 30 may communicate over a network. The electronic device 10 and the backup server 40 may communicate over a network.

Based on the foregoing description, the data backup and restore method of the present application will be described in detail with reference to fig. 2A to 2S. For convenience of description, in fig. 2A to 2S, the electronic device 10 is taken as a mobile phone, and the electronic device 20 is taken as a PC for illustration.

Referring to fig. 2A-2S, fig. 2A-2S show a schematic diagram of a man-machine interface according to an embodiment of the application.

The PC may display an interface 21 as shown in fig. 2A, where the interface 21 is used to display a connection condition between the PC and the mobile phone, and also is used to display a login condition of the service account. For example, the interface 21 may include: control 201, control 202, and control 203. The control 201 is used to display the login status of the service account. The control 202 is used to display the connection mode of the PC and the mobile phone. The control 203 is used for displaying the connection state of the PC and the mobile phone. In fig. 2A, the login status of the service account displayed by the control 201 is unregistered. The PC displayed by control 202 is connected to the handset in a manner that USB is not connected. The connection state of the PC and the mobile phone displayed by the control 203 is unconnected.

Upon receiving an operation (such as a click, double click, or long press operation) by the store user to trigger the control 201 shown in fig. 2A, the PC may change from the interface 21 shown in fig. 2A to display the interface 21 shown in fig. 2B.

In fig. 2B, the interface 21 may further include: control 204, control 205, and control 206. Control 204 is used to receive a service account number. Control 205 is used to receive a service password. Control 206 is used to receive login operations.

After receiving the service account number input by the store user on the control 204 shown in fig. 2B, the service password input by the store user on the control 205 shown in fig. 2B, and the operation of the store user triggering the control 206 shown in fig. 2B, the account number server may determine that the service account number matches the service password, and the PC may obtain the authority of the backup data. Thus, the PC can change from the interface 21 shown in fig. 2B to display the interface 21 shown in fig. 2C. In fig. 2C, the login state of the service account displayed by the control 201 becomes logged in.

Based on this, the PC and the mobile phone can be connected through the USB data line, so that the PC can transmit a connection notification to the mobile phone, the connection notification being used to notify that the mobile phone can be connected to the PC through the data line.

The handset may display an interface 11 as shown in fig. 2D, the interface 11 being used to display icons of various Applications (APPs) installed on the handset. For example, the interface 11 may include: control 101 and control 102. Wherein, control 101 is used for displaying the icon of file management APP. Control 102 is used to display an icon of cloud backup APP.

Upon receiving the connection notification transmitted from the PC and upon receiving the operation of pulling down the interface 11 shown in fig. 2D performed by the maintenance user, the cellular phone may change from the interface 11 shown in fig. 2D to the interface 11 shown in fig. 2E.

In fig. 2E, the interface 11 may further include a control 103, where the control 103 is used to trigger displaying a connection manner of the USB.

Upon receiving the operation of the maintenance user triggering the control 103 shown in fig. 2E, the mobile phone may change from the interface 11 shown in fig. 2E to display the interface 12 shown in fig. 2F. The interface 12 is used to display the connection mode of the USB.

In fig. 2F, control 104 may be included in interface 12, control 104 being capable of transmitting data with a PC using a trigger handset.

Upon receiving the operation of the maintenance user triggering the control 104 shown in fig. 2F, the mobile phone may change from the interface 11 shown in fig. 2F to displaying the interface 12 shown in fig. 2G.

In fig. 2G, the interface 12 may further include a control 105, where the control 105 is connected to the PC by a trigger handset.

After receiving the operation of the maintenance user to trigger the control 105 shown in fig. 2G, the mobile phone can be connected to the PC, so that the mobile phone establishes a data channel between the mobile phone and the PC, through which data can be transmitted.

Thus, the PC may display an interface 21 as shown in FIG. 2H, and controls 207 may also be included in the interface 21. Control 207 is used to indicate that the PC is able to receive and backup data sent by the handset.

In addition, in fig. 2H, the connection mode between the PC and the mobile phone, which is shown by the control 202, is that the USB is connected. The connection state of the PC and the mobile phone displayed by the control 203 is connected.

Upon receiving an operation of triggering the control 207 shown in fig. 2H by the store user or the maintenance user, the PC may change from the interface 21 shown in fig. 2H to display the interface 21 shown in fig. 2I.

In fig. 2I, the interface 21 may further include: control 208, control 209, and control 210. Control 208 is used to receive a personal account number. Control 209 is used to receive a personal password. Control 210 is used to receive verification operations.

After receiving the personal account number input by the maintenance user on the control 208 shown in fig. 2I, the personal password input by the maintenance user on the control 209 shown in fig. 2I, and the operation of the maintenance user to trigger the control 210 shown in fig. 2I, the account server may determine that the personal account number matches the personal password, and the PC may obtain the authority of identity confirmation.

Based on this, the PC can transmit an upload data notification to the mobile phone, the upload data being used to notify the mobile phone that the data can be transmitted to the PC.

Upon receiving the upload data notification and upon receiving the operation of the maintenance user triggering the control 101 shown in fig. 2D, the mobile phone may change from the interface 11 shown in fig. 2D to the interface 13 shown in fig. 2J.

Or upon receiving the upload data notification, the handset may display an interface 13 as shown in fig. 2J.

In fig. 2J, the interface 13 is used to display various folders stored on the cell phone. Such as folders of documents, folders of pictures, folders of videos, and folders of music. Control 106, control 107, control 108, control 109, control 110, and control 111 may be included in interface 13. The control 106 is used for displaying a prompt for reminding a maintenance user of selecting data to be backed up. Control 107 is used to trigger the sending of data to be backed up to the PC. Control 108 is used to trigger the folder of the selected document. Control 109 is used to trigger the folder of the selected picture. Control 110 is used to trigger the folder of the selected video. The control 111 is used to trigger the folder of the selected music.

Upon receiving the operations of the maintenance user triggering the controls 108, 109, 110, and 111 shown in fig. 2J, the mobile phone may change from the interface 13 shown in fig. 2J to displaying the interface 13 shown in fig. 2K. In interface 13, controls 108, 109, 110, and 111 all display the selected state of the folder, at which point the folder of the document, the folder of the picture, the folder of the video, and the folder of the music are all selected.

Upon receiving the operation of the maintenance user triggering the control 107 shown in fig. 2K, the handset may determine to be able to send data to the PC. Thus, the handset may change from the interface 13 shown in fig. 2K to display the interface 13 shown in fig. 2L. Controls 112 may also be included in interface 13. Control 112 is used to receive an encrypted password entered by a service user.

Upon receiving the encryption password entered by the service user in control 112 shown in fig. 2L, the handset may encrypt the folders of the selected document, the folders of the picture, the folders of the video, and the folders of the music, and initiate the transmission of data to the PC. Thus, the handset may change from the interface 13 shown in fig. 2L to display the interface 13 shown in fig. 2M.

In fig. 2M, the interface 13 may further include a control 113, where the control 113 is used to display a transmission state of data. At this point, the reminder text displayed on control 113 is "send-in-process …" which is used to remind the handset that data is being sent to the PC.

In addition, in the process of uploading data to the PC, the PC may change from the interface 21 shown in fig. 2I to the interface 21 shown in fig. 2N.

In fig. 2N, the interface 21 may further include a control 211, where the control 211 is used to display a receiving state of data. At this time, the reminder text displayed on the control 211 is "receiving …", which is used to remind the PC that the data sent by the mobile phone is being received.

After the data reception is completed, the PC may change from the interface 21 shown in fig. 2N to display the interface 21 shown in fig. 2O. At this time, the reminder text displayed by the control 211 is changed from "receiving …" to "receiving completed", and the reminder text is used to remind the PC that the data sent by the mobile phone has been received.

In addition, in fig. 2O, the interface 21 may further include a control 212, where the control 212 is configured to trigger sending data received by the PC to the backup server. Thus, the control 207 can provide access to the backup server for sending data in the handset received by the PC.

Upon receiving the trigger operation for control 212 shown in fig. 2O, the PC may send the data, personal account number, and service account number in the handset to the backup server.

The backup server can determine the authority of the PC to obtain the backup data through the service account by means of the account server, and determine the authority of the PC to obtain the identity confirmation through the personal account.

Thus, the backup server can receive the data in the handset sent by the PC.

In some embodiments, the backup server may store the received encrypted data in the storage space 1 of the personal account number.

In other embodiments, the backup server may store the received encrypted data in the storage space 2 of the service account number and associate the storage space 2 with the personal account number.

Therefore, the mobile phone can acquire and decrypt the data from the backup server according to the personal account number, so that the mobile phone recovers the data.

When the maintenance user needs to restore the data in the mobile phone, the mobile phone can respond to the restoration operation triggered by the maintenance user to acquire the data from the backup server.

Upon receiving the operation of the maintenance user triggering the control 102 shown in fig. 2D, the handset may change from the interface 11 shown in fig. 2D to display the interface 14 shown in fig. 2P. The interface 14 is used to display the login status of the personal account number. Controls 114, 115, and 116 may be included in interface 14. Control 114 is used to receive a personal account number. Control 115 is used to receive a personal password. Control 116 is used to receive login operations.

It should be appreciated that the personal account number in fig. 2P is the same as the personal account number in fig. 2I. The personal password in fig. 2P is the same as the personal password in fig. 2I.

Upon receiving the personal account number entered by the service user on control 114 shown in fig. 2P, the personal password entered by the service user on control 115 shown in fig. 2P, and the operation of the service user to trigger control 116 shown in fig. 2P, the handset may change from interface 14 shown in fig. 2P to display interface 15 shown in fig. 2Q. The interface 15 is used to display the recovery of data in the handset.

In fig. 2Q, the interface 15 may further include: control 117. The control 117 is used to trigger the mobile phone to be able to obtain data from the backup server.

Upon receiving the operation of the maintenance user triggering the control 117 shown in fig. 2Q, the mobile phone may initiate acquiring data from the backup server according to the personal account number. Thus, the handset may change from the interface 15 shown in fig. 2Q to display the interface 15 shown in fig. 2R. Controls 118 may also be included in interface 15. Control 118 is used to receive a decryption password entered by the service user.

Upon receiving the decryption password entered by the service user at control 118 shown in fig. 2R, the handset may recover the data.

It should be appreciated that the encryption password in fig. 2R is the same as the decryption password in fig. 2L.

Upon receiving the operation of the maintenance user triggering the control 101 shown in fig. 2D, the mobile phone may change from the interface 11 shown in fig. 2D to display the interface 13 shown in fig. 2S. The interface 13 displays various folders after the restoration. Such as folders of documents, folders of pictures, folders of videos, and folders of music.

In summary, when the user needs to backup the data in the mobile phone, the PC can obtain the authority of the backup data through the service account by means of the account server, and obtain the authority of identity confirmation through the personal account. After the mobile phone encrypts the data, the data is sent to the PC, and the PC can transmit the data, the service account number and the personal account number in the mobile phone to the backup server, so that the backup server can determine that the PC obtains the two rights by means of the service account number. Thus, the backup server can receive the data in the handset sent by the PC.

In addition, when the user needs to restore the data in the mobile phone, the data can be acquired from the backup server according to the personal account number.

Next, a specific implementation procedure of the data backup and restore method of the present application will be described in detail with reference to fig. 3.

FIG. 3 is a flowchart illustrating an exemplary data backup and restore method according to the present application.

As shown in fig. 3, the method can be divided into three different phases, namely a 1.1 login phase, a 1.2 backup phase, and a 1.3 restore phase.

1.1 The login phase can be understood as the phase of the PC obtaining the rights to the backup data through the service account.

The 1.2 backup stage can be understood as a stage in which the PC obtains the right of identity confirmation through the personal account number, and the backup server determines that the PC obtains the two right by means of the account number server and then backs up the data in the mobile phone in the backup server.

1.3 The recovery phase can be understood as the phase of the mobile phone recovering data from the backup server according to the personal account number.

As shown in fig. 3, the data backup and recovery method of the present application may include:

[ 1.1 Login phase ]

S11, the PC receives a service account number, a service password and a login operation 1.

The service account number is an account number of a maintenance store to which the store user belongs.

The service password is a password corresponding to a service account number of a maintenance store to which the store user belongs.

The service account number may include, but is not limited to, at least one parameter of Identity (ID), mobile phone number, user name, mailbox, etc. of the store user.

The user ID of the store user may include, but is not limited to, an identification card number of the store user. The user name of the store user may include, but is not limited to, a user name of the store user, e.g., the user name of the store user may include characters, letters, binary numbers, etc.

Any two parameters in the service account number are in one-to-one correspondence, namely, any one parameter in the service account number corresponds to the rest of parameters in the service account number.

For example, the PC may determine the remaining parameters of the corresponding store user's cell phone number, user name, and mailbox based on the store user's user ID.

In some embodiments, the service password is a password or an authentication code.

In other embodiments, the service password is a password and an authentication code, so that the security of the service account login is enhanced.

In addition, the PC can also log in through a mode of scanning the code by the mobile phone of the logged-in service account (the PC can display the two-dimensional code, and a store user can finish logging in the service account by scanning the two-dimensional code by using the mobile phone of the logged-in service account).

In some embodiments, the PC is a PC used by a repair shop to backup data in a cell phone to a backup server.

The PC can display a display interface, wherein the display interface is used for displaying the connection condition of the PC and the mobile phone and displaying the login condition of the service account. The application does not limit the specific implementation mode of the display interface.

In some embodiments, control 1, control 2, and control 3 may be included in the display interface. Control 1 is used to receive a service account number. Control 2 is used to receive a service password. The login control is used to trigger login operation 1.

The application does not limit the parameters such as the display positions, the display styles, the display sizes and the like of the control 1, the control 2 and the control 3.

Thus, the PC may receive a service account number through control 1, a service password through control 2, and a login operation 1 through control 3.

The PC may receive the service account number and the service password first, and then receive the login operation 1. The order in which the PC receives the service account number and the service password is not sequential.

And S12, the PC responds to the login operation 1 and sends a service account and a service password to the account server.

After receiving the service account number, the service password, and the login operation 1, the PC may send the service account number and the service password to the account server in response to the login operation 1, so as to prepare data for the account server to perform matching verification on the service account number and the service password.

In other embodiments, control 1 and control 2 may be included in the display interface.

The PC may receive a service account number via control 1 and a service password via control 2. After a preset period of time, the PC may send a service account and a service password to the account server.

S13, the account server determines whether the service account and the service password are matched.

It should be appreciated that the service account number corresponds to a service password. The service account is an account which is successfully registered in advance, and the service password is a password corresponding to the service account when the service account is registered in advance.

Wherein, at registration, the PC may receive the service account number, the service password, and a registration operation, and send the service account number and the service password to the account server in response to the registration operation. The account server may receive a service account and a service password.

Thus, the account server may store the service account and the service password.

After receiving the service account and the service password, the account server can perform matching verification on the service account and the service password, namely determining whether the service account and the service password are matched.

The service account number and the service password are matched to indicate that the service account number received by the PC is the service account number in registration, and the service password is the service password in registration.

And S14, when the service account number is matched with the service password, the account number server sends an access token 1 to the PC.

When the service account number is matched with the service password, the account number server can send an access token 1 to the PC, after the access token 1 is received, the display interface of the PC can display that the service account number is in a login state, and the PC obtains the authority of backup data.

Wherein the access token 1 is used to indicate that the PC has the right to back up data. The access token 1 may carry information such as a service account number, an internet protocol address (internet protocol address, IP) of the PC, etc.

The PC has the authority to backup the data, indicating that the PC has the function of backing up the data.

When the service account number and the service password do not match, the account server may send an error code to the PC. After receiving the error code, the PC can display a prompt on the display interface according to the error code. The prompt is used for reminding that the service account number and the service password are not matched. For example, the prompt may be: account errors, password errors, or login failures.

After the prompt is displayed, the store user can input the service account again through the control 1, and the PC can receive the service account again; the store user inputs the service account again through the control 2, and the PC can receive the service password again; the store user may re-trigger login operation 1 via control 3 and the pc may re-receive login operation 1.

In addition, the account server may store the access token 1 when sending the access token 1 to the PC. The validity period of the access token 1 is typically one hour (e.g. one hour post refresh).

The account server may generate an encrypted string corresponding to the access token 1 instead of storing the access token 1, and store the encrypted string corresponding to the access token 1.

That is, the account server may encrypt information such as the service account, the authority of the backup data of the service account, and the validity period of the access token 1 by a key or calculate an information digest as a signature.

Thus, the PC may send the service account and the service password to the account server again in response to the login operation 1 until the account server determines that the service account matches the service password, and the PC receives the access token 1.

S15, displaying the login interface 1.

When the PC displays the login interface 1, the login state of the service account on the PC is logged in.

In summary, when the service account and the service password are received, the account server can perform matching verification on the service account and the service password, so that the service account and the service password are ensured to be matched, the PC obtains the authority of the backup data, and the PC can backup the data in the mobile phone to the backup server conveniently.

In addition, the service account number keeps a long-term login state on the PC, so that time and energy spent by store users in each login can be saved, data preparation is made for maintenance users to carry out data backup before the mobile phone is maintained, and inconvenience brought to the store users and the maintenance users is avoided.

[ 1.2 Backup phase ]

S16, the PC or the mobile phone establishes a data channel between the PC and the mobile phone for transmitting data, so that the PC and the mobile phone can mutually transmit data.

Wherein S16 may also be performed before S11.

After the PC or the mobile phone establishes a data channel between the PC and the mobile phone for transmitting data, the PC can determine that the data transmitted by the mobile phone can be received and the data transmitted by the mobile phone can be backed up.

The manner in which the PC or the mobile phone establishes the data channel between the PC and the mobile phone for transmitting data may be various.

For example, the PC or the mobile phone may establish a data channel between the PC and the mobile phone through a USB data line, bluetooth, or wireless network (WIRELESS FIDELITY, wiFi) or other communication methods.

Assume that the handset establishes a data channel between the PC and the handset via a USB data line.

The speed of the mobile phone for sending data through the USB data line is 50-80MB/s.

Therefore, the mobile phone and the PC are connected through the USB data line, so that the speed of sending data from the mobile phone to the PC is high.

In addition, the mobile phone sends data to the PC through the USB data line, and the mobile phone is not limited by the current use state of the mobile phone. For example, the wireless network (WIRELESS FIDELITY, wiFi) is unstable, wiFi disconnected, or insufficient power.

In addition, the mobile phone sends data to the PC through the USB data line, so that the speed is high, the mobile phone does not need to be in a state of sending data for a long time, and the mobile phone can be maintained as soon as possible.

S17, the PC displays a verification interface.

After determining that the data sent by the handset can be received, the PC may display a verification interface. The verification interface is used for displaying the verification condition of the personal account number. The application does not limit the specific implementation mode of the verification interface.

The verification interface may be displayed in a partial area of the login interface 1, or may be a different interface from the login interface 1.

S18, the PC receives the personal account number, the personal password and the verification operation.

The personal account number is an account number of a maintenance user.

The personal password is a password corresponding to the personal account number of the maintenance user.

The personal account number may include, but is not limited to, at least one parameter of an Identity (ID) number of the maintenance user, a cell phone number, a user name, a mailbox, and the like.

Wherein the user ID of the maintenance user may include, but is not limited to, the identification card number of the maintenance user. The user name of the service user may include, but is not limited to, the user name of the service user, e.g., the user name of the service user may include characters, letters, binary numbers, etc.

Any two parameters in the personal account number are in one-to-one correspondence, namely, any one parameter in the personal account number corresponds to the rest of parameters in the personal account number.

For example, the PC may determine the remaining parameters of the corresponding service subscriber's cell phone number, user name, and mailbox based on the service subscriber's user ID.

In some embodiments, the personal password is a password or an authentication code.

In other embodiments, the personal password is a password and an authentication code, so that the security of personal account login is enhanced.

In addition, the PC can also perform verification in a code scanning mode through the mobile phone of the logged-in personal account number (the PC can display the two-dimensional code, and a maintenance user can scan the two-dimensional code through the mobile phone of the logged-in personal account number to finish verification of the personal account number).

In some embodiments, the mobile phone is a mobile phone that needs backup data.

In some embodiments, control 4, control 5, and control 6 may be included in the verification interface. Control 4 is used to receive a personal account number. Control 5 is used to receive a personal password. The control 6 is used to trigger a verification operation.

The application does not limit the parameters such as the display positions, the display styles, the display sizes and the like of the control 4, the control 5 and the control 6.

Thus, the PC may receive a personal account number through control 4, a personal password through control 5, and a validation operation through control 6.

The PC may receive the personal account number and the personal password first, and then receive the authentication operation. The order in which the personal account number and the personal password are received by the PC is not sequential.

And S19, the PC responds to the verification operation and sends the personal account number and the personal password to the account server.

After receiving the personal account number, the personal password, and the authentication operation, the PC may send the personal account number and the personal password to the account server in response to the authentication operation, and prepare data for the account server to perform matching authentication on the personal account number and the personal password.

In other embodiments, control 4 and control 5 may be included in the verification interface.

The PC may receive a personal account number via control 4 and a personal password via control 5. After a preset period of time, the PC may send a personal account number and a personal password to the account server.

S20, the account server determines whether the personal account number is matched with the personal password.

It should be understood that the personal account number and the personal password are matched, the personal account number is an account number and a password which are successfully registered in advance, and the personal password is a password corresponding to the personal account number when the personal account number is registered in advance.

The mobile phone can receive the personal account number, the personal password and the registration operation during registration, and send the personal account number and the personal password to the account server in response to the registration operation. The account server may receive a personal account number and a personal password.

Thus, the account server may store the personal account number and the personal password.

After receiving the personal account number and the personal password, the account number server can perform matching verification on the personal account number and the personal password, namely, whether the personal account number and the personal password are matched or not is determined.

The personal account number and the personal password are matched to indicate that the personal account number received by the PC is the personal account number in registration, and the personal password is the personal password in registration.

S21, the account server sends an identity token to the PC when the personal account is matched with the personal password.

When the personal account number and the personal password are matched, the account number server can send an identity token (id token) to the PC, and after the identity token is received, the PC can change from displaying the verification interface to displaying the login interface 1, and the PC obtains the authority of identity confirmation.

The identity token is used for indicating that the PC has the authority of identity confirmation. The identity token may carry information such as a personal account number, an IP address of the PC, etc.

The PC has the right to restore the data, which means that the PC has the function of backing up the data according to the personal account number.

The account server may send an error code to the PC when the personal account number and the personal password do not match. After receiving the error code, the PC can display a prompt on the verification interface according to the error code. The prompt is used for reminding that the personal account number and the personal password are not matched. For example, the prompt may be: account errors, password errors, or login failures.

After the prompt is displayed, the maintenance user can re-input the personal account number through the control 4, and the PC can re-receive the personal account number; the maintenance user can re-input the personal code through the control 5, and the PC can re-receive the personal code; the service user can re-trigger the authentication operation through control 6 and the PC can re-receive the authentication operation.

The PC may again send the personal account number and the personal password to the account server in response to the authentication operation until the account server determines that the personal account number matches the personal password, the PC receiving the identity token.

In addition, the account server may store the identity token when sending the identity token to the PC. The validity period of an identity token is typically one hour (e.g. one hour post refresh).

The account server may not store the identity token, but may generate an encrypted string corresponding to the identity token.

That is, the account server may encrypt the personal account, the authority of identity confirmation of the personal account, the validity period of the identity token, etc. by using the key or calculate a digest as the signature.

Therefore, when the personal account number and the personal password are received, the account number server can verify the personal account number and the personal password, so that the personal account number and the personal password are matched, the PC obtains the authority of identity confirmation, namely, the PC can use the personal account number to backup data, and the backup server can backup the data in the mobile phone corresponding to the personal account number conveniently.

In addition, the personal account number only needs single authentication and authorization on the PC, and the personal account number does not keep a login state, so that the security risk and inconvenience caused by long-term login of the personal account number on the PC and data backup can be avoided.

S22, the PC sends an uploading data notification to the mobile phone.

Wherein upon receipt of the identity token, the PC may send an upload data notification to the handset.

The upload data notification is used to notify the mobile phone that it can send data to the PC, and the PC can backup the data in the mobile phone to the backup server.

Thus, the mobile phone can determine that the data can be transmitted to the PC after receiving the upload data notification.

S23, the mobile phone sends the encrypted data to the PC.

The mobile phone can encrypt the data which the maintenance user wants to backup, and then send the encrypted data to the PC.

In some embodiments, the handset may select the data that the maintenance user wants to backup, set an encryption password for the data after the selection, encrypt the data, and send the encrypted data to the PC.

The application is not limited to the specific implementation of the encrypted data.

Therefore, the mobile phone encrypts the data and then transmits the encrypted data to the PC, so that the data leakage can be avoided, and the safety of the data is ensured.

S24, the PC sends the access token 1, the identity token and the encrypted data to the backup server.

S25, the backup server sends the access token 1 and the identity token to the account server.

After receiving the encrypted data sent by the mobile phone, the PC may send the access token 1, the identity token, and the encrypted data to the backup server.

After receiving the access token 1 and the identity token sent by the PC, the backup server can send the access token 1 and the identity token to the account server, so that the account server can conveniently verify the access token 1 and the identity token respectively.

S26, the account server respectively verifies the access token 1 and the identity token.

When the account server verifies the access token 1 received by the backup server from the PC, the access token 1 may be decrypted, and the access token 1 may be verified by whether the access token 1 received by the backup server from the PC is associated with a service account and whether the account server stores the same access token as the access token 1. After decryption, the backup server determines that the service account is associated with the access token 1 received from the PC, and when the account server stores the same access token as the access token 1, the account server may determine that the service account is already in a login state on the PC, and the PC has obtained the authority of the backup data.

In addition, after decryption, the backup server determines that the access token 1 received from the PC is associated with the service account, and when the account server stores an encrypted string corresponding to the access token matched with the access token 1, the account server can determine that the service account is in a login state on the PC, and the PC obtains the authority of the backup data.

Wherein, the service account number associated with the access token 1 can comprise: the access token 1 carries a service account number, or the access token 1 has a corresponding relation with the service account number.

The account server verifies the access token 1 received by the backup server from the PC, so that the service account is in a login state on the PC, the PC has obtained the authority of the backup data, and the PC can smoothly send the data in the mobile phone to the backup server.

When the account server verifies the identity token received by the backup server from the PC, the identity token can be decrypted, and the identity token is verified through whether the identity token received by the backup server from the PC is related to the personal account or not and whether the account server stores the identity token which is the same as the identity token or not. After decryption, the backup server determines that the personal account is associated with the identity token received from the PC, and when the account server stores the identity token identical to the identity token, the account server can determine that the personal account passes the identity verification on the PC, and the PC obtains the authority of the identity verification.

In addition, after decryption, the backup server determines that the personal account is associated with the identity token received from the PC, and when the account server stores an encrypted character string corresponding to the identity token matched with the identity token, the account server can determine that the personal account passes the identity verification on the PC, and the PC obtains the authority of the identity verification.

Wherein the identity token associated personal account number may comprise: the identity token carries the personal account number, or the identity token has a corresponding relation with the personal account number.

The account server verifies the identity token received by the backup server from the PC, so that the personal account can pass the identity verification on the PC, the PC obtains the authority of identity verification, and the PC can conveniently and smoothly send the data in the mobile phone corresponding to the personal account to the backup server.

And S27, the account server sends verification notification to the backup server.

When the access token 1 and/or the identity token fails to verify, the account server may determine that the service account is not in a login state on the PC, or that the identity of the personal account fails to verify, and the account server may send a verification notification to the backup server, where the verification notification indicates that the access token 1 and/or the identity token fails to verify.

When the received authentication notification indicates that both the access token 1 and the identity token are authenticated, the account server may determine that the service account is in a login state on the PC and that the personal account has been authenticated, and the account server may send an authentication notification to the backup server indicating that both the access token 1 and the identity token are authenticated.

And S281, when the received verification notification is used for indicating that the identity token and the access token 1 pass verification, the backup server receives the encrypted data and stores the encrypted data in the storage space 1 corresponding to the identity token.

Upon receiving the authentication notification indicating that the access token 1 and/or the identity token is not authenticated, the backup server may send an error code to the PC. After receiving the error code, the PC can display a prompt on the display interface according to the error code. The prompt is used for reminding that the service account is not in a login state or that the personal account fails to pass the authentication. For example, the prompt may be: service account login failure, or personal account authentication failure.

Therefore, when the prompt is invalid for the login of the service account, the store user can input the service account again through the control 1, and the PC can receive the service account again; the store user inputs the service account again through the control 2, and the PC can receive the service password again; the store user may re-trigger login operation 1 via control 3 and the pc may re-receive login operation 1.

The PC may again respond to the login operation 1 by sending the service account and the service password to the account server until the account server determines that the service account matches the service password, and the PC receives the access token 1.

When the prompt is invalid for personal account verification, the maintenance user can input the personal account again through the control 4, and the PC can receive the personal account again; the maintenance user can re-input the personal code through the control 5, and the PC can re-receive the personal code; the service user can re-trigger the authentication operation through control 6 and the PC can re-receive the authentication operation.

Upon receiving the authentication notification indicating that both the access token 1 and the identity token are authenticated, the backup server may determine to be able to receive encrypted data sent by the PC.

Therefore, the backup server respectively verifies the access token 1 and the identity token by means of the account server, so that the backup server can stably and safely backup data.

Wherein, after S27, the backup server may execute S281, or may execute S282.

The backup server may preset a storage space corresponding to the identity token, that is, a storage space corresponding to the personal account number.

In some embodiments, when the received verification notification is used to indicate that both the identity token and the access token 1 pass verification, the backup server may allocate, according to a preset storage space corresponding to the identity token, the storage space 1 to correspond to the identity token, so that the personal account corresponding to the identity token has the recovery authority.

Therefore, the personal account number is carried in the identity token, and the mobile phone can recover data from the storage space 1 of the backup server according to the personal account number.

After the old identity token has expired (e.g. until the identity token expires or the personal account number has been logged out, resulting in an expiration), the storage space 1 remains valid.

Thus, the storage space 1 may not be directly associated with an identity token, but with a personal account number. When the backup server stores data, the encrypted data can be stored in the storage space 1 associated with the personal account number according to the identity token.

Thus, when the received authentication notification is used to indicate that both the identity token and the access token 1 pass authentication, the backup server may receive the encrypted data sent by the PC, and store the encrypted data in the storage space 1 corresponding to the identity token.

Based on the embodiment shown in S281, the backup server may store the data in the mobile phone sent by the PC in the storage space 1 corresponding to the identity token, so that the mobile phone can restore the data in the mobile phone stored in the storage space 1 of the identity token according to the personal account number.

And S282, when the received verification notification is used for indicating that the identity token and the access token 1 pass verification, the backup server receives the encrypted data and stores the encrypted data in the storage space 2 corresponding to the access token 1, and the storage space 2 is associated with the personal account.

Wherein S282 is an optional step.

The backup server may preset a storage space corresponding to the access token 1, that is, a storage space corresponding to the service account number.

The storage space corresponding to the identity token preset by the backup server is usually smaller, so that the storage space which can be allocated by the backup server for the identity token is smaller, and the situation that the data in the mobile phone is not stored enough may exist.

The storage space corresponding to the access token 1 preset by the backup server is usually larger, and data corresponding to a plurality of identity tokens can be stored. Then, the backup server can allocate a larger storage space for the access token 1 and can store the data in the mobile phone.

Assuming that the storage space corresponding to the preset identity token is 20G, the storage space corresponding to the preset identity token is 500G, and the data in the mobile phone which needs to be backed up by the user is 30G.

Then the backup server can allocate 20G of storage space for the identity token, which is insufficient to store the data in the handset. The backup server can allocate 500G of memory space for the access token 1 and can store data in the mobile phone.

Thus, the backup server may be preset to store the received data in the mobile phone sent by the PC in the storage space 2 of the access token 1.

That is, the backup server may use the storage space corresponding to the access token 1 set in advance as the storage space corresponding to the identity token.

In some embodiments, when the received verification notification is used to indicate that both the identity token and the access token 1 pass verification, the backup server may allocate the storage space 2 corresponding to the access token 1 according to the preset storage space corresponding to the access token 1, and associate the storage space 2 with the personal account, so that the personal account has the recovery authority.

That is, the backup server may preset a sharing relationship, and after the backup server stores the data in the mobile phone in the storage space 2 of the access token 1, the storage space 2 is associated with the personal account number, so that the backup server can share the storage space 2 corresponding to the access token 1 with the personal account number corresponding to the identity token.

Thus, the mobile phone can restore the data stored in the mobile phone in the memory space 2 of the access token 1 according to the personal account number.

Or the PC can restore the data stored in the handset in the memory space 2 of the access token 1 according to the service account number.

After the old access token 1 expires (e.g., until the access token 1 expires or the service account is logged out, resulting in an expiration), the storage space 2 remains available.

Thus, the storage space 2 may not be directly associated with the access token 1, but with the personal account number and the service account number, respectively. When the backup server stores data, the encrypted data can be stored in the storage space 2 respectively associated with the personal account number and the service account number according to the access token 1.

Therefore, when the received verification notification indicates that the identity token and the access token 1 pass verification, the backup server can receive data in the mobile phone sent by the PC, store the data in the storage space 2 of the access token 1, associate the storage space 2 with the personal account, ensure that the data in the mobile phone can be stored in the backup server, and enable the personal account to have restoration authority.

Based on the embodiment shown in S282, the backup server may store the data in the mobile phone in the storage space 2 of the access token 1, and enable the personal account corresponding to the identity token to have the restoration authority, so that the mobile phone can restore the data in the mobile phone stored in the storage space 2 of the access token 1 according to the personal account.

In addition, after the backup server finishes the backup of the data in the mobile phone in the 1.2 backup stage, the PC can delete the received data in the mobile phone so as to ensure the privacy and the safety of the data of the maintenance user.

It can be seen that for the embodiment shown in S281 and the embodiment shown in S282:

The embodiment shown in S281 is applicable to the case where the storage space corresponding to the identity token preset by the backup server is large.

The embodiment shown in S282 is applicable to the case where the storage space corresponding to the identity token preset by the backup server is smaller, and the storage space corresponding to the access token 1 preset by the backup server is larger. The backup server can use the storage space corresponding to the preset access token 1 as the storage space corresponding to the identity token, so that the data in the mobile phone can be stored in the backup server.

The backup server may preset that the storage space corresponding to the access token 1 is smaller, and when it is difficult to store the encrypted data, the backup server may allocate a temporary storage space with a preset size for the access token 1, and may temporarily store the encrypted data.

In addition, the stored encrypted data may be automatically released after the data is restored or after the temporary storage space expires.

In conclusion, after the mobile phone can encrypt the data, the data is sent to the PC through the USB data line, and the data is transmitted through the USB data line because the USB data line is faster, so that the data transmission efficiency can be ensured.

In addition, the mobile phone encrypts the data, so that the safety of data backup can be ensured.

The backup server can confirm that the service account is in a login state on the PC by respectively verifying the identity token and the access token 1 by means of the account server, and the personal account passes the identity verification on the PC, the backup server can store the encrypted data in the storage space 1 of the identity token or the storage space 2 of the access token 1 and associate the storage space 2 with the personal account, and the backup mode can avoid the risk of data loss caused by abnormal backup (such as the loss of a PC disk or a U disk for backing up the data), so that the safety and the privacy of data backup are ensured.

[ 1.3 Recovery phase ]

S29, the mobile phone receives the personal account number, the personal password and the login operation 2.

The personal account number in S29 is the personal account number in S18. The personal password in S29 is the personal password in S18.

The mobile phone may display a login interface 2, where the login interface 2 is used to display the login condition of the personal account. The present application is not limited to the specific implementation of the login interface 2.

In addition, in the 1.3 recovery phase, the mobile phone for recovering the data in the mobile phone backed up in S281 or S282 may be: the mobile phone after maintenance or other mobile phones except for the mobile phone after maintenance of the user.

In some embodiments, controls 7, 8, and 9 may be included in login interface 2. Control 7 is used to receive a personal account number. Control 8 is used to receive a personal password. The control 9 is used to trigger the login operation 2.

The handset may receive a personal account number via control 7, a personal password via control 8, and a login operation 2 via control 9.

The application does not limit the parameters such as the display positions, the display styles, the display sizes and the like of the control 7, the control 8 and the control 9.

The mobile phone may receive the personal account number and the personal password first, and then receive the login operation 2. The order of the mobile phone receiving the personal account number and the personal password is not sequential.

S30, the mobile phone responds to the login operation 2, acquires the access token 2 and displays a recovery interface.

After receiving the personal account number, the personal password, and the login operation 2, the mobile phone may send the personal account number and the personal password to the account server in response to the login operation 2.

In other embodiments, controls 7 and 8 may be included in login interface 2.

The mobile phone can receive the personal account number through the control 7 and receive the personal password through the control 8. After the preset time, the mobile phone can send the personal account number and the personal password to the account server.

When the personal account number and the personal password are matched, the account server can send an access token 2 to the mobile phone, and after receiving the access token 2, the personal account number can be in a login state.

The access token 2 is used for indicating that the mobile phone has the right of recovering data. The access token 2 may carry information such as a personal account number.

The mobile phone has the right of recovering the data, which means that the mobile phone has the function of recovering the data.

When the personal account number and the personal password are not matched, the account server can send error codes to the mobile phone. After receiving the error code, the mobile phone can display a prompt on the recovery interface according to the error code. The prompt is used for reminding that the personal account number and the personal password are not matched. For example, the prompt may be: account errors, password errors, or login failures.

After the prompt is displayed, the maintenance user can input the personal account again through the control 7, and the mobile phone can receive the personal account again; the maintenance user can input the personal code again through the control 8, and the mobile phone can receive the personal code again; the maintenance user can trigger the login operation 2 again through the control 9, and the mobile phone can receive the login operation 2 again.

The mobile phone can respond to the login operation 2 again, and send the personal account number and the personal password to the account number server until the account number server determines that the personal account number is matched with the personal password, and the mobile phone receives the access token 2.

Therefore, when the personal account number and the personal password are received, the account number server can verify the personal account number and the personal password, so that the personal account number and the personal password are matched, the personal account number is in a login state on the mobile phone, and the mobile phone can recover data according to the personal account number conveniently.

S31, the mobile phone receives the recovery operation.

S32, the mobile phone responds to the recovery operation and sends the personal account number to the backup server.

After receiving the access token 2, the interface of the mobile phone is changed from the display interface to the display recovery interface. The recovery interface is used for receiving recovery operation, and the recovery interface can display that the personal account number is in a login state. The application does not limit the specific implementation mode of the recovery interface.

In some embodiments, a data recovery control may be included in the recovery interface. The data recovery control is used for triggering the mobile phone to recover data.

The application does not limit the parameters such as the display position, the display style, the display size and the like of the data recovery control.

Thus, after receiving a restore operation indicated by the maintenance user through the restore control, the handset may send the personal account number or access token 2 to the backup server in response to the restore operation.

S33, the backup server sends the encrypted data to the mobile phone.

Upon receiving the personal account number or access token 2, the backup server may determine that the service user wants to restore the data.

Thus, the backup server may determine, according to the personal account number or the access token 2, a storage space associated with the personal account number, and send the encrypted data in the storage space to the mobile phone.

In some embodiments, the encrypted data is stored in the storage space 1 of the identity token, and the identity token carries the personal account number, the access token 2 carries the personal account number, and the backup server can send the data stored in the storage space 1 of the identity token to the mobile phone according to the personal account number or the access token 2.

In other embodiments, the encrypted data stores the storage space 2 of the access token 1, and the storage space 2 is associated with the personal account number, so that the access token 2 carries the personal account number, and the backup server can send the data stored in the storage space 2 of the access token 1 to the mobile phone according to the personal account number or the access token 2.

S34, decrypting and recovering the data by the mobile phone.

After receiving the encrypted data, the mobile phone can decrypt the encrypted data. Thus, after decryption, the handset may recover the data.

In some embodiments, after receiving the encrypted data, the mobile phone may further display a control 10 in the recovery interface, where the control 10 is used to receive the decryption password.

The present application is not limited to the parameters such as the display position, the display style, and the display size of the control 10.

After receiving the decryption password input by the maintenance user, the mobile phone can restore the data.

In addition, the decryption password in S34 is the same as the encryption password in S23.

The application is not limited to the specific implementation of decrypting the data.

In summary, the mobile phone can respond to the recovery operation and send the personal account number or the access token 2 to the backup server, so that the backup server can send the encrypted data to the mobile phone according to the personal account number or the personal account number carried by the access token 2, and after decrypting the encrypted data, the mobile phone can recover the data, thereby ensuring the safety of data recovery.

In the application, when a maintenance user needs to backup the data in the mobile phone, the PC can acquire the access token 1 through the service account by means of the account server, so that the PC obtains the authority of the backup data, and the PC can smoothly backup the data to prepare the data. The PC can also acquire the identity token through the personal account by means of the account server, so that the PC acquires the authority of identity confirmation, and the backup server can backup the data in the mobile phone corresponding to the personal account conveniently.

The mobile phone can send data to the PC through the USB data line, and the data transmission efficiency can be ensured through the USB data line because the data line is faster in data transmission. The mobile phone encrypts the data and then sends the encrypted data to the PC, so that the safety of data transmission can be ensured.

The backup server can verify the access token 1 and the identity token by means of the account server to determine that the service account is in a login state on the PC, and the backup server can verify the identity token by means of the account server to determine that the personal account passes the identity verification on the PC.

When the received verification notification is used for indicating that the identity token and the access token 1 pass verification, the backup server can receive data in the mobile phone sent by the PC and store the data in the storage space 1 corresponding to the identity token. The identity token may carry a personal account number, and the storage space 1 is associated with the personal account number.

When the received verification notification is used for indicating that the identity token and the access token 1 pass verification, the backup server can receive data in the mobile phone sent by the PC, store the data in the storage space 2 corresponding to the access token 1, and associate the storage space 2 with the personal account number.

Therefore, the backup realization process can avoid the risk of losing the data, and ensure the safety and privacy of the data backup.

In addition, when the maintenance user needs to recover the data in the mobile phone, the mobile phone can acquire the data in the mobile phone from the storage space associated with the personal account number in the backup server according to the personal account number or the access token 2, and the mobile phone can recover the data after decryption, so that the safety of data recovery is ensured.

Based on the foregoing embodiments, the data backup method and the data recovery method provided by the present application are described below.

Illustratively, the present application provides a data backup method.

For ease of illustration, the data backup method of the present application may be performed by a first electronic device.

The first electronic device may be a mobile phone, a desktop computer, a tablet computer, a wearable device, a vehicle-mounted device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a home device, or the like.

For example, the first electronic device is a personal computer PC.

Referring to fig. 4, fig. 4 is a flowchart illustrating a data backup method according to an embodiment of the application.

As shown in fig. 4, the data backup method provided by the present application may include:

s101, logging in a first server by a first account number of a first user, and receiving a first token from the first server, wherein the first account number is associated with the first token.

The first account may be one or more of a management account, a service account, an enterprise account, a personal account, a home account, or a work account.

Correspondingly, the first user may be one or more of an enterprise management layer user, a store user of a repair store, an enterprise user, a repair user, a home user, or a work user.

For example, the first user is a store user servicing a store, and the first account is a service account of the service store.

In addition, the first token may refer to the description of the access token 1 in S14 in fig. 3.

The first server may be a cloud server or a proprietary server.

For example, the first server is an account server.

The specific implementation of S101 may be referred to the interface 21 in fig. 2A-2C, and the descriptions of S11-S15 in fig. 3, which are not repeated here.

S102, receiving a second account number and a first password of a second user, wherein the first user and the second user are different.

The type of the second account may be the same as or different from the type of the first account. The first user and the second user are different.

For example, the second user is a maintenance user and the second account is a personal account of the maintenance user.

The specific implementation of S102 may be referred to the interface 21 in fig. 2H-2I, and the descriptions of S17-S18 in fig. 3, which are not repeated here.

And S103, receiving a second token from the first server when the second account number is matched with the first password, wherein the second token is associated with the second account number.

The specific implementation of S103 may be referred to the descriptions of S20-S21 in fig. 3, and will not be described here.

In addition, the second token may refer to the description of the identity token 1 in S21 in fig. 3.

And S104, after receiving the second token, sending a notification for reminding the second electronic device to send backup data to the first electronic device.

The notification in S104 may refer to the upload data notification of S22 in fig. 3.

The specific implementation of S104 may be referred to the interface 13 in fig. 2J, and the description of S22 in fig. 3, which is not described herein.

S105, receiving backup data from the second electronic device.

The second electronic device may be a mobile phone, a desktop computer, a tablet computer, a wearable device, a vehicle-mounted device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a home device, or the like.

For example, the second electronic device is a mobile phone.

The backup data is data in the second electronic device which the second user wants to backup or data after processing the data in the second electronic device.

The specific implementation of S105 may be referred to the interface 21 in fig. 2N-2O, and the description of S23 in fig. 3, which are not repeated here.

And S106, sending the first token, the second token and the backup data to the second server so that the second server stores the backup data according to the first token and the second token.

The second server may be a cloud server or a proprietary server.

For example, the second server is a backup server.

Thus, in addition, the second server may verify the first token and the second token, respectively, by means of the first server when the second server stores backup data in accordance with the first token and the second token. When the first server determines that the first account number is in a login state in the first electronic device according to the first token and the first server determines that the second account number passes identity verification in the first electronic device according to the second token, the second server is informed that the first token and the second token pass the identity verification, and therefore the second server can receive backup data sent by the second electronic device and store the backup data.

The specific implementation of S106 can be seen in the interface 21 in fig. 2O, and the descriptions of S24-S281/S282 in fig. 3, which are not repeated here.

According to the data backup method, when the second user needs to backup the data in the second electronic device, the first electronic device can acquire the first token through the first account number by means of the first server, acquire the second token through the second account number, receive backup data sent by the second electronic device, and store the backup data in the second server according to the first token and the second token, so that data backup is realized, privacy and safety of the data backup are guaranteed, and data backup experience of the user is improved.

In some embodiments, the backup data is stored in a first storage space of the second server, the first storage space being associated with the second account; and/or the backup data is stored in a second storage space of the second server, and the second storage space is respectively associated with the first account and the second account.

The first storage space may be described with reference to storage space 1 in S281 in fig. 3.

The second storage space can be described with reference to storage space 2 in S282 in fig. 3.

The specific implementation of the backup data storage may be referred to in S281-S282 in fig. 3, which are not described herein.

In some embodiments, the data backup method of the present application further includes:

And establishing a data channel between the first electronic equipment and the second electronic equipment, wherein the data channel is used for data transmission between the first electronic equipment and the second electronic equipment.

The application can receive backup data from the second electronic device through the data channel.

In addition, the data channel is established through a USB data line.

Therefore, the second electronic device sends data to the first electronic device through the USB data line, the speed is high, and the second electronic device does not need to be in a state of sending data for a long time.

The specific implementation manner of establishing the data channel may refer to the interface 11 in fig. 2D-2E, the interface 12 in fig. 2F-2G, and the description of S16 in fig. 3, which are not repeated herein.

In some embodiments, the data backup method of the present application may include:

Step 201, a first account number and a second password of a first user are received.

The specific implementation of step 201 may be referred to the interface 21 in fig. 2B, and the description of S11 in fig. 3, which is not repeated here.

Step 202, a first account number and a second password are sent to a first server.

The specific implementation of step 202 may be referred to the description of S12 in fig. 3, and will not be described herein.

Step 203, receiving a first token from a first server, wherein the first token is sent by the first server when the first account number and the second password are determined to match.

The specific implementation of step 203 may be referred to the description of S14 in fig. 3, and will not be described herein.

Step 204, after receiving the first token, logging in the first server with the first account.

The specific implementation of step 204 can be seen from the descriptions of S14-S15 in fig. 3, and will not be described here.

step 301, a second account number and a first password are sent to a first server.

The specific implementation of step 301 may be referred to the description of S19 in fig. 3, and will not be described herein.

Step 302, receiving a second token from the first server, the second token being sent by the first server when it is determined that the second account number and the first password match.

The specific implementation of step 302 can be seen from the descriptions of S20-S21 in fig. 3, and will not be described here.

In some embodiments, the backup data is encrypted data.

The specific implementation of the encrypted data may be referred to the interface 13 in fig. 2L, and S23 in fig. 3, which are not described herein.

Therefore, the data can be encrypted, the data leakage can be prevented as much as possible, and the safety of the data is ensured.

In some embodiments, the data backup method of the present application may further include:

step 401, displaying a first interface.

The first interface may refer to the interface 21 in fig. 2A, and the description of the display interface in S11 in fig. 3.

The specific implementation of step 401 may be referred to the interface 21 in fig. 2A, and S11 in fig. 3, which are not described herein.

Step 402, receiving a first account number and a second password in response to a first operation in a first interface.

Specific implementation of the first operation may refer to operations on the control 204 and the control 205 of the interface 21 in fig. 2B, and descriptions of operations on the control 1 and the control 2 in S11 in fig. 3.

The specific implementation of step 402 may be referred to the interface 21 in fig. 2B, and S11 in fig. 3, which are not described herein.

Step 403, after receiving the first token, logging in the first server in the first interface with the first account number and the second password.

step 501, displaying a second interface.

The second interface may refer to the interface 21 in fig. 2I, and the description of the verification interface in S15 in fig. 3.

The specific implementation of step 501 may be referred to the interface 21 in fig. 2I, and the description of S17 in fig. 3, which is not described herein.

Step 502, receiving a second account number and a first password in response to a second operation in the second interface.

A specific implementation of the second operation may be found in the operations on the controls 208 and 209 of the interface 21 in fig. 2I, and in the descriptions of the operations on the controls 4 and 5 in S18 in fig. 3.

The specific implementation of step 502 may be referred to the interface 21 in fig. 2I, and the description of S18 in fig. 3, which will not be repeated here.

In some embodiments, the first electronic device may be a PC. The second electronic device may be a cell phone. The first server may be an account server. The second server may be a backup server.

Illustratively, the present application provides a data recovery method.

For ease of illustration, the data recovery method of the present application may be performed by a third electronic device.

The third electronic device and the second electronic device may be the same electronic device or different electronic devices, and the second electronic device is an electronic device for sending backup data to the first electronic device. For example, the third device is a cell phone.

Referring to fig. 5, fig. 5 is a flowchart illustrating a data recovery method according to an embodiment of the application.

As shown in fig. 5, the data recovery method provided by the present application may include:

s601, logging in a first server by a second account of a second user.

The specific implementation of S601 may be referred to the descriptions of S29-S30 in fig. 3, and will not be described here.

S602, displaying a third interface.

The third interface may be described with reference to interface 15 in fig. 2Q, and the recovery interface in S30 in fig. 3.

The specific implementation of S602 may be referred to the interface 15 in fig. 2Q, and the description of S30 in fig. 3, which are not described herein.

And S603, responding to the recovery operation on the third interface, and sending a second account number or a third token to the second server, wherein the second account number is associated with the third token.

Wherein the third token may be referred to as the description of the access token 2 in S30 in fig. 3.

Specific implementation of the recovery operation can be referred to as operation on the control 117 of the interface 15 in fig. 2Q, and description of operation on the data recovery control in S32 in fig. 3.

The specific implementation of S603 may be referred to the interface 15 in fig. 2Q-2R, and the description of S32 in fig. 3, which are not repeated here.

And S604, receiving backup data from the second server, wherein the backup data is data acquired by the second server according to the second account number or the third token.

The backup data in S604 is the backup data in S104.

The specific implementation of S604 can be seen from the descriptions of S33-S34 in fig. 3, and will not be described here.

In some embodiments, the data recovery method of the present application may further include:

Step 701, receiving a second account number and a first password of a second user.

The second account in step 701 is the second account in S102. The first password in step 601 is the first password in S102.

The specific implementation of step 701 may be referred to the interface 14 in fig. 2P, and S29 in fig. 3, which are not described herein.

Step 702, a second account number and a first password are sent to a first server.

The specific implementation of step 701 may be referred to as S30 in fig. 3, which is not described herein.

Step 703, receiving a third token from the first server, the third token being sent by the first server when it is determined that the second account number and the first password match.

The specific implementation of step 703 may be referred to as S30 in fig. 3, which is not described herein.

Step 704, after receiving the third token, logging in the first server with the second account and the first password.

The specific implementation of step 704 may be referred to as S30 in fig. 3, and will not be described herein.

step 801, logging in the first server with the second account in the fourth interface.

The fourth interface may refer to the interface 14 in fig. 2P, and the description of the login interface 2 in S29 in fig. 3.

Specific implementation of step 801 may refer to interface 14 in fig. 2P, and S29 in fig. 3, which are not described herein.

Step 802, after logging in the first server with the second account, displaying a third interface.

The specific implementation of step 802 may be referred to the interface 15 in fig. 2Q, and S30 in fig. 3, which are not described herein.

In some embodiments, the backup data is encrypted data.

and decrypting the backup data.

The specific implementation of decrypting the data may refer to the interface 15 in fig. 2R, and S34 in fig. 3, which are not described herein.

The decryption password used to decrypt the backup data is an encryption password used to encrypt the backup data.

Illustratively, the present application provides an apparatus that may include one or more modules for performing the data backup method, or the data recovery method in the previous embodiments.

Illustratively, the present application provides an electronic device comprising a processor; the computer code or instructions in the memory, when executed by the processor, cause the electronic device to perform the data backup method, or the data recovery method, of the previous embodiments.

Illustratively, the present application provides an electronic device comprising one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the data backup method, or the data recovery method, of the previous embodiments.

The communication system includes a first electronic device, a third electronic device, a first server, and a second server, where the first electronic device is configured to execute the data backup method in the foregoing embodiment, the third electronic device is configured to execute the data recovery method in the foregoing embodiment, the third electronic device and the second electronic device may be the same electronic device or different electronic devices, and the second electronic device is an electronic device configured to send backup data to the first electronic device. The first server is used for storing and verifying account numbers and passwords, and the second server is used for backing up data.

The present application provides, as an example, a chip system including a processor for calling and running a computer program from a memory, so that an electronic device mounted with the chip system performs the data backup method, or the data restoration method in the foregoing embodiment.

Illustratively, the present application provides a computer-readable storage medium having stored therein code or instructions which, when executed on an electronic device, cause the electronic device to perform the data backup method, or the data recovery method, of the previous embodiments.

The present application illustratively provides a computer program product which, when run on a computer, causes an electronic device to implement the data backup method, or the data recovery method, of the previous embodiments.

In the above-described embodiments, all or part of the functions may be implemented by software, hardware, or a combination of software and hardware. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer codes or instructions. When the computer program code or instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer code or instructions may be stored in a computer readable storage medium. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tape), optical media (e.g., DVD), or semiconductor media (e.g., solid State Disk (SSD)) or the like.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: a Read Only Memory (ROM) or a random access memory (random access memory, RAM), a magnetic disk or an optical disk, or the like.

Claims

1. A data backup method, applied to a first electronic device, the method comprising:

Receiving a first token from a first server, and logging in the first server by a first account of a first user, wherein the first account is associated with the first token;

Receiving a second account number and a first password of a second user, wherein the first user and the second user are different;

Receiving a second token from the first server when the second account and the first password match, the second token being associated with the second account;

after receiving the second token, sending a notification for reminding the second electronic device to send backup data to the first electronic device;

receiving the backup data from the second electronic device;

And sending the first token, the second token and the backup data to a second server, so that the second server stores the backup data according to the first token and the second token when the first token and the second token are verified by the first server, the right of the first electronic device to obtain the backup data and the right of identity confirmation are determined.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The backup data is stored in a first storage space of the second server, and the first storage space is associated with the second account;

and/or the backup data is stored in a second storage space of the second server, and the second storage space is respectively associated with the first account number and the second account number.

3. The method according to claim 1, wherein the method further comprises:

establishing a data channel between the first electronic device and the second electronic device, wherein the data channel is used for data transmission between the first electronic device and the second electronic device;

the receiving backup data from the second electronic device includes:

And receiving the backup data from the second electronic equipment through the data channel.

4. The method of claim 1, wherein the receiving the first token from the first server and logging into the first server with the first account of the first user comprises:

receiving the first account number and a second password of the first user;

transmitting the first account number and the second password to the first server;

Receiving the first token from the first server, the first token being sent by the first server upon determining that the first account number and the second password match;

After receiving the first token, logging in the first server with the first account number and the second password.

5. The method according to claim 4, wherein the method further comprises:

Displaying a first interface;

receiving the first account number and the second password in response to a first operation in the first interface;

after the first token is received, logging in the first server with the first account in the first interface.

6. The method of any of claims 1-5, wherein the receiving a second token from the first server when the second account number and the first password match comprises:

transmitting the second account number and the first password to the first server;

The second token is received from the first server, and the second token is sent by the first server when the second account number and the first password are determined to match.

7. The method of claim 5, wherein the method further comprises:

displaying a second interface;

and receiving the second account number and the first password in response to a second operation in the second interface.

8. The method of any of claims 1-5, wherein the backup data is encrypted data.

9. A data recovery method, applied to a third electronic device, the method comprising:

Logging in a first server by a second account number and a first password of a second user;

displaying a third interface;

Responsive to a recovery operation on the third interface, sending the second account number or a third token to a second server, the second account number being associated with the third token;

Receiving backup data from the second server, wherein the backup data is data acquired by the second server according to the second account number or the third token;

The backup data are stored when the second server verifies a first token and a second token through the first server, the permission of a first electronic device to obtain the backup data is determined, the permission of identity confirmation is determined, the first token, the second token and the backup data are sent to the second server by the first electronic device, the first token is obtained when the first electronic device logs in the first server through a first account number of a first user, the second token is obtained when the first electronic device determines that the second account number is matched with the first password through the first server, the first account number is associated with the first token, the first user is different from the second user, and the backup data are sent to the first electronic device when the second electronic device receives the backup data notification sent by the first electronic device based on the second token.

10. The method of claim 9, wherein the logging into the first server with the second account of the second user and the first password comprises:

receiving the second account number and the first password;

receiving the third token from the first server, the third token being sent by the first server upon determining that the second account number and the first password match;

After receiving the third token, logging in the first server with the second account number and the first password.

11. The method according to claim 10, wherein the method further comprises:

Logging in the first server with the second account in a fourth interface;

and after logging in the first server by the second account, displaying the third interface.

12. The method of any of claims 9-11, wherein the backup data is encrypted data.

13. The method of any of claims 9-11, wherein after the receiving backup data from the second server, the method further comprises:

Decrypting the backup data.

14. An electronic device, comprising:

one or more processors;

A memory;

And one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the data backup method of any of claims 1-8, or the data recovery method of any of claims 9-13.

15. A chip system comprising a processor for calling and running a computer program from a memory, so that an electronic device on which the chip system is mounted performs the data backup method according to any one of claims 1-8 or the data recovery method according to any one of claims 9-13.

16. A computer readable storage medium comprising a computer program, characterized in that the computer program, when run on an electronic device, causes the electronic device to perform the data backup method of any of claims 1-8 or the data recovery method of any of claims 9-13.