Data backup method and system and electronic equipment

By sending a data backup request on the second device, the first device can complete data backup even if the screen is unavailable, solving the problem of inability to backup when the screen is unavailable and improving the user experience.

CN119862068APending Publication Date: 2025-04-22HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311366393.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-10-19
Publication Date
2025-04-22

AI Technical Summary

Technical Problem

When the screen of an electronic device is unavailable, data backup cannot be completed, resulting in data loss and affecting the user experience.

Method used

By sending a data backup request on the second device, the first device can directly send backup data to the second device even if the screen is unavailable, and complete data backup.

Benefits of technology

It realizes that data backup can be completed when the first device screen is unavailable, avoiding data loss and improving user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119862068A_ABST
    Figure CN119862068A_ABST
Patent Text Reader

Abstract

The invention provides a data backup method and system and electronic equipment, relates to the technical field of terminals, and aims to complete data backup on first equipment when a screen of the first equipment is unavailable so as to ensure the use experience of a user. In the data backup method, the first device is in a failure state in which a screen is unavailable, and the first device communicates with the second device. And the second device sends a data backup request to the first device. A first device receives a data backup request, and determines first backup data in the first device in response to the data backup request. And the first device sends the first backup data to the second device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a data backup method, system and electronic device. Background Art

[0002] When users use electronic devices (such as mobile phones, tablets, etc.), they will generate application data such as pictures, documents, videos, audio, chat records, etc. When some software and hardware of the electronic device fails, these application data may be lost, thus affecting the user's experience.

[0003] At present, data backup is often used to back up application data in one electronic device (such as device A) to another electronic device (such as device B), so as to ensure that the application data in the electronic device (such as device A) will not be lost when the electronic device (such as device A) fails. In this process, the user needs to perform a series of operations on the screen of the electronic device (such as device A) to complete the data backup. However, if the electronic device (such as device A) has failed and the screen cannot be used, the data backup will not be able to be performed. Summary of the invention

[0004] The embodiments of the present application provide a data backup method, system and electronic device to solve the problem that the data backup on the first device cannot be completed when the screen of the first device is unavailable, thereby ensuring the user experience.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a data backup method is provided, which can be applied to a data backup system, wherein the data backup system includes a first device and a second device, the first device communicates with the second device, and the first device is in a fault state, wherein the fault state includes that a screen of the first device is unavailable.

[0007] In the data backup method, the second device sends a data backup request to the first device. The first device receives the data backup request and determines the first backup data in the first device in response to the data backup request. The first device sends the first backup data to the second device.

[0008] The above method can achieve the purpose of backing up the data in the faulty first device to the second device. Among them, the fault state of the first device can indicate that the screen of the first device is unavailable. When the screen of the first device is unavailable, the user does not need to operate on the first device to complete the backup of the data on the first device. The first device can directly send the backup data to the second device according to the data backup request of the second device. In this way, when the screen of the first device is unavailable, the data backup on the first device can also be completed, which will not cause the data loss on the first device, and ensure the user experience.

[0009] In an implementation of the first aspect, the second device displays a first page, the first page is used to prompt the user to enter unlock information of the first device. In response to the user entering the unlock information on the first page, the second device sends a data backup request to the first device.

[0010] In this implementation, the first device may be provided with a lock screen function or a lock function to ensure the security of the data and information on the first device. In order to ensure that the second device can back up the data or information on the first device, the user needs to input the unlocking information (such as an unlocking code, unlocking string, unlocking gesture, unlocking fingerprint, unlocking voiceprint, etc.) used to unlock the first device on the second device, thereby releasing the lock screen function or the lock function of the first device, so that the data or information on the first device can be transmitted to the second device.

[0011] Exemplarily, the second device may display a first page, wherein the first page may prompt the user to enter unlock information of the first device. When the user enters the unlock information on the first page, the second device sends a data backup request to the first device, thereby requesting to backup the data or information on the first device.

[0012] In an implementation manner of the first aspect, the data backup request includes unlocking information. When the unlocking information in the data backup request matches the preset information, the first device determines the first backup data.

[0013] In this implementation, the process of matching the unlocking information with the preset information may also be referred to as an authentication or verification process. When the unlocking information matches the preset information, it may be regarded as a successful authentication or verification. In this case, the first device allows the second device to back up the data on the first device, and the first device continues to determine the first backup data.

[0014] In an implementation of the first aspect, the second device displays a second page, the second page being used to display information of the data to be backed up on the first device. In response to a user selecting the data to be backed up on the second page, the second device sends a data backup request to the first device.

[0015] In this implementation, the application software data and user data waiting to be backed up stored on the first device can be divided into different types according to attributes, sources, etc. When backing up data, the user can select some types of data to back up according to actual needs, or select all types of data to back up.

[0016] Exemplarily, the second device may display a second page, wherein the second page may display information of the data to be backed up on the first device. When the user selects the data to be backed up on the second page, the second device sends a data backup request to the first device, thereby requesting to back up the corresponding data on the first device.

[0017] In an implementation of the first aspect, the data backup request includes information of the data to be backed up selected by the user. The first device determines the first backup data from the data to be backed up of the first device according to the information of the data to be backed up selected by the user in the data backup request.

[0018] In an implementation of the first aspect, the second device displays a first page, and the first page is used to prompt the user to enter unlock information of the first device. In response to the user inputting the unlock information on the first page, the second device sends the unlock information to the first device. The second device receives a notification message sent by the first device, and the notification message is a message sent by the first device when the unlock information matches the preset information. In response to the notification message, the second device displays a second page, and the second page is used to display information of the data to be backed up on the first device. In response to the user selecting the data to be backed up on the second page, the second device sends a data backup request to the first device.

[0019] In this implementation, the purpose of unlocking the first device on the second device can also be achieved.

[0020] In an implementation manner of the first aspect, the notification message includes information about the data to be backed up on the first device. The second device displays the second page according to the information about the data to be backed up in the notification message.

[0021] In this implementation, the second device can obtain information about the data to be backed up on the first device, so that the second device can display the second page based on the obtained information about the data to be backed up. In this way, since the information about the data to be backed up is obtained from the first device, the information about the data to be backed up can better reflect the actual type of the data to be backed up on the first device and the actual storage space occupied. As a result, the information about the data to be backed up on the second page displayed by the second device can also be more accurate and more in line with the actual situation of the data on the first device.

[0022] In an implementation of the first aspect, the second page is further used to prompt for input of encryption information for encrypting the first backup data; the data backup request also includes the encryption information. The first device saves the first backup data to a memory buffer; the first device uses the encryption information in the data backup request to encrypt the first backup data in the memory buffer, and sends the encrypted first backup data to the second device.

[0023] In this implementation, the first device can save the first backup data in a memory buffer, and the first device then encrypts the first backup data in the memory buffer and sends the encrypted first backup data to the second device, thereby ensuring the security of data transmission between the first device and the second device and reducing the risk of leakage or tampering during data transmission.

[0024] In an implementation manner of the first aspect, the method further includes: the second device receives the encrypted first backup data; and the second device decrypts the encrypted first backup data according to the encryption information to obtain the first backup data.

[0025] In this implementation, the first device encrypts the first backup data before sending it, which can ensure the security of the first backup data; the second device then uses the same encryption information to decrypt the received data to obtain accurate first backup data, thereby completing the data backup operation between the first device and the second device.

[0026] In an implementation manner of the first aspect, the first device saves the first backup data to a memory buffer; the first device encrypts the first backup data in the memory buffer using a preset key, and sends the encrypted first backup data and the preset key to the second device.

[0027] In this implementation, the first device can save the first backup data in a memory buffer, and the first device then encrypts the first backup data in the memory buffer, and sends the encrypted first backup data and a preset key to the second device, thereby ensuring the security of data transmission between the first device and the second device and reducing the risk of leakage or tampering during data transmission.

[0028] In an implementation manner of the first aspect, the method further includes: the second device receives the encrypted first backup data and a preset key; and the second device decrypts the encrypted first backup data according to the preset key to obtain the first backup data.

[0029] In this implementation, the second device can also use the same preset key to decrypt the received data to obtain accurate first backup data, thereby completing the data backup operation between the first device and the second device.

[0030] In an implementation manner of the first aspect, the first device segments the encrypted first backup data in the memory buffer to obtain at least one data segment; and the first device sends the at least one data segment to the second device in sequence.

[0031] In this implementation, when the data of the first device is large and requires a long transmission time, segmented processing of the data of the first device can achieve the purpose of resuming data transmission at breakpoints.

[0032] In an implementation manner of the first aspect, the method further includes: when the second device is connected to the third device, sending the first backup data to the third device. The third device performs data recovery according to the first backup data.

[0033] In this implementation, when a first device used by a user fails, not only data backup operations can be implemented, but also data recovery operations can be implemented, providing a better user experience for the user.

[0034] In an implementation manner of the first aspect, the first device communicates with the second device through a preset connection method, and the preset connection method includes connecting through a universal serial bus USB, connecting through a lightning interface Lightning, or connecting through wireless fidelity WIFI technology.

[0035] In a second aspect, a data backup method is provided, which can be applied to a first device in a data backup system, the data backup system also includes a second device, the first device communicates with the second device, the first device is in a fault state, and the fault state includes that the screen of the first device is unavailable. In the method, the first device receives a data backup request sent by the second device, and determines the first backup data in the first device in response to the data backup request. The first device then sends the first backup data to the second device.

[0036] In an implementation manner of the second aspect, the data backup request is sent by the second device in response to a user inputting unlock information on a first page, and the first page is used to prompt for input of unlock information of the first device.

[0037] In an implementation manner of the second aspect, the data backup request includes unlocking information. When the unlocking information in the data backup request matches the preset information, the first device determines the first backup data.

[0038] In an implementation manner of the second aspect, the data backup request is sent by the second device in response to a user selecting data to be backed up on a second page, and the second page is used to display information about the data to be backed up on the first device.

[0039] In an implementation of the second aspect, the data backup request includes information of the data to be backed up selected by the user. The first device determines the first backup data from the data to be backed up of the first device according to the information of the data to be backed up selected by the user in the data backup request.

[0040] In an implementation of the second aspect, the first device receives unlock information sent by the second device, the unlock information is sent by the second device in response to a user inputting unlock information on a first page, and the first page is used to prompt the user to input the unlock information of the first device. When the unlock information matches the preset information, the first device sends a notification message to the second device. The first device receives a data backup request sent by the second device, the data backup request is sent by the second device in response to a user selecting data to be backed up on the second page, the notification message is used to instruct the second device to display a second page, and the second page is used to display information on the data to be backed up on the first device.

[0041] In an implementation of the second aspect, the data backup request includes information of the data to be backed up selected by the user. The first device determines the first backup data from the data to be backed up of the first device according to the information of the data to be backed up selected by the user in the data backup request.

[0042] In an implementation manner of the second aspect, the notification message includes information about the data to be backed up on the first device, and the notification message is used to instruct the second device to display the second page according to the information about the data to be backed up.

[0043] In an implementation of the second aspect, the second page is further used to prompt for input of encryption information for encrypting the first backup data. The data backup request also includes encryption information. The first device saves the first backup data to a memory buffer. The first device uses the encryption information in the data backup request to encrypt the first backup data in the memory buffer, and sends the encrypted first backup data to the second device.

[0044] In an implementation of the second aspect, the first device saves the first backup data to a memory buffer, encrypts the first backup data in the memory buffer using a preset key, and sends the encrypted first backup data and the preset key to the second device, where the preset key is used by the second device to decrypt the first backup data.

[0045] In an implementation of the second aspect, the first device processes the encrypted first backup data in the memory buffer into segments to obtain at least one data segment, and the first device sends the at least one data segment to the second device in sequence.

[0046] According to a third aspect, a data backup system is provided. The data backup system includes a first device and a second device. The first device communicates with the second device. The first device is in a fault state. The fault state includes that a screen of the first device is unavailable.

[0047] The second device is used to send a data backup request to the first device. The first device is used to receive the data backup request and determine the first backup data in the first device in response to the data backup request. The first device is used to send the first backup data to the second device.

[0048] In a fourth aspect, an electronic device is provided, comprising a memory and one or more processors; the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code comprises computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the data backup method as in the first aspect and any implementation thereof.

[0049] In a fifth aspect, a computer-readable storage medium is provided, comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the data backup method in the first aspect and any implementation thereof.

[0050] In a sixth aspect, a computer program product is provided. When the computer program product is run on a computer, the computer executes the data backup method in the first aspect and any implementation manner thereof.

[0051] It can be understood that the beneficial effects that can be achieved by the data backup method described in the second aspect, the data backup system described in the third aspect, the electronic device described in the fourth aspect, the computer-readable storage medium described in the fifth aspect, and the computer program product described in the sixth aspect can refer to the beneficial effects in the first aspect and any possible design method thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 Schematic diagram of the data backup process shown in the embodiment of the present application Figure 1 ;

[0053] Figure 2 Schematic diagram of the data backup process shown in the embodiment of the present application Figure 2 ;

[0054] Figure 3 A schematic diagram of a data backup system shown in an embodiment of the present application;

[0055] Figure 4 A schematic diagram of the structure of a first device shown in an embodiment of the present application;

[0056] Figure 5A schematic diagram of the structure of a second device shown in an embodiment of the present application;

[0057] Figure 6 A schematic diagram of a minimum system shown in an embodiment of the present application;

[0058] Figure 7 The process diagram of the data backup method shown in the embodiment of the present application is as follows: Figure 1 ;

[0059] Figure 8 A schematic diagram of a first page shown in an embodiment of the present application;

[0060] Fig. 9 The second page shown in the embodiment of the present application is shown in FIG. Figure 1 ;

[0061] Fig.10 The process diagram of the data backup method shown in the embodiment of the present application is as follows: Figure 2 ;

[0062] Fig.11 A schematic diagram of a third page shown in an embodiment of the present application;

[0063] Fig.12 A schematic diagram of the fourth page shown in the embodiment of the present application;

[0064] Fig.13 The second page shown in the embodiment of the present application is shown in FIG. Figure 2 ;

[0065] Fig.14 This is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the differences. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0067] In addition, the business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0068] When users use electronic devices (such as mobile phones, tablets, etc.), they will generate application data such as pictures, documents, videos, audio, chat records, etc. When some software and hardware of the electronic device fails, these application data may be lost, thus affecting the user's experience.

[0069] Currently, a data backup method is usually adopted to back up application data in one electronic device (such as device A) to another electronic device (such as device B), so as to ensure that the application data in device A will not be lost when device A fails.

[0070] During data backup, see Figure 1 As shown, the user needs to perform a series of operations on the screen of device A, such as unlocking, selecting backup content, etc., so that device A responds to the user's operations on device A and sends the data to be backed up to device B to complete the data backup. However, if device A has a malfunction and the screen cannot be used at this time, data backup will also be unable to be performed, thereby affecting the user's experience.

[0071] Alternatively, see Figure 2 As shown, the user can also connect device A to a USB flash drive and transfer the data in device A to the USB flash drive. Afterwards, the USB flash drive can be connected to device B, so that the data in device A can be backed up to device B. However, in the process of data backup, additional devices such as USB flash drives are required, which not only causes unnecessary expenses, but also takes a lot of time to save the data to the USB flash drive and then back it up to device B when the amount of data to be backed up is large, thereby affecting the performance of data backup.

[0072] Based on the above content, an embodiment of the present application provides a data backup method. In the method, a first device is in a fault state and communicates with a second device, wherein the fault state includes that the screen of the first device is unavailable. The second device can send a data backup request to the first device, the first device receives the data backup request, and in response to the data backup request, determines the first backup data in the first device, and then the first device sends the first backup data to the second device.

[0073] The above method can achieve the purpose of backing up the data in the faulty first device to the second device. Among them, the fault state of the first device can indicate that the screen of the first device is unavailable. When the screen of the first device is unavailable, the user does not need to operate on the first device to complete the backup of the data on the first device. The first device can directly send the backup data to the second device according to the data backup request of the second device. In this way, when the screen of the first device is unavailable, the data backup on the first device can also be completed, which will not cause the data loss on the first device, and ensure the user experience.

[0074] In addition, the above method can realize data transmission between the first device and the second device without the need for additional devices such as USB flash drives, which can reduce unnecessary expenses or costs. Moreover, without using USB flash drives, the time between backing up data from the first device to the second device can also be reduced, thereby improving data backup performance.

[0075] The above data backup method can be applied to the data backup system. Figure 3As shown, the data backup system includes a first device 301 and a second device 302. The first device 301 represents a faulty device, that is, the first device 301 is in a faulty state; and the second device 302 is a normal device, that is, the second device 302 is in a normal operating state, and the software and hardware in the second device 302 are both fault-free.

[0076] In some embodiments, the fault state of the first device 301 may indicate that the screen of the first device 301 is unavailable, and the screen unavailability may be caused by a software failure in the first device 301 or by a hardware failure in the first device 301, which is not specifically limited in the embodiments of the present application.

[0077] In some embodiments, see Figure 4 As shown, the first device 301 may include a communication module 3011, a data backup module 3012, an authentication module 3013, a storage module 3014, and the like.

[0078] The communication module 3011 may receive a data backup request sent by the second device 302 , and send the first backup data in the first device 301 to the second device 302 .

[0079] The storage module 3014 can store data to be backed up in the first device 301 (such as data of various application software in the first device 301, user data, etc.).

[0080] The data backup module 3012 may determine the first backup data that needs to be backed up from the data stored in the storage module 3014 in response to the received data backup request.

[0081] Exemplarily, the communication module 3011 may also receive unlocking information sent by the second device 302. Furthermore, the authentication module 3013 compares the received unlocking information with the preset information in the first device 301. If the two match, the authentication is successful. In this case, the data backup module 3012 may determine the first backup data, and the communication module 3011 sends the first backup data to the second device 302.

[0082] Exemplarily, the communication module 3011 may also receive information of the data to be backed up selected by the user and sent by the second device 302. And, the data backup module 3012 determines the first backup data to be backed up from the data stored in the storage module 3014 according to the received information of the data to be backed up.

[0083] Exemplarily, the storage module 3014 may include a read-only memory (ROM) in the first device 301, or may include a ROM and a random access memory (RAM) in the first device 301, wherein the RAM may also be referred to as a memory buffer.

[0084] When the storage module 3014 includes a ROM, after determining the first backup data in the ROM, the data backup module 3012 can directly send the first backup data through the communication module 3011 .

[0085] When the storage module 3014 includes ROM and RAM, the data backup module 3012 can directly send the first backup data through the communication module 3011 after determining the first backup data in the ROM. Alternatively, the data backup module 3012 can also save the first backup data in the RAM after determining the first backup data in the ROM, and then the data backup module 3012 encrypts the first backup data in the RAM, and the communication module 3011 sends the encrypted first backup data.

[0086] The key used by the data backup module 3012 to encrypt the first backup data may be the encryption information received by the communication module 3011 from the second device 302 , or may be a preset key in the first device 301 .

[0087] Exemplarily, the communication module 3011 may also segment the first backup data (or the encrypted first backup data) in the RAM into at least one data segment, and send at least one data segment to the second device 302 in sequence.

[0088] In some embodiments, see Figure 5 As shown, the second device 302 may include a communication module 3021, a data recovery module 3022, a processing module 3023, a storage module 3024, and the like.

[0089] The communication module 3021 may send a data backup request to the first device 301, and receive the first backup data in the first device 301. And, the storage module 3024 is used to store the first backup data.

[0090] Exemplarily, the processing module 3023 may control the second device 302 to display a first page, wherein the first page is used to prompt the user to input unlock information of the first device. Afterwards, the processing module 3023 receives the user's operation of inputting unlock information on the first page, and sends a data backup request to the first device 301. The data backup request may include the unlock information input by the user, so that the first device 301 can receive the unlock information.

[0091] Exemplarily, the processing module 3023 may also control the second device 302 to display a second page, wherein the second page is used to display information of the data to be backed up on the first device. Afterwards, the processing module 3023 receives an operation of the user selecting the data to be backed up on the second page, and sends a data backup request to the first device 301. The data backup request may include information of the data to be backed up selected by the user, so that the first device 301 may receive information of the data to be backed up selected by the user.

[0092] Exemplarily, after receiving the unlock information, if the unlock information matches the preset information, the first device 301 may also send a notification message to the second device 302 through the communication module 3011. The communication module 3021 of the second device 302 receives the notification message, and the processing module 3023 may display the second page in response to the notification message.

[0093] The processing module 3023 may display the second page according to the preset information, wherein the preset information may include the type of data to be backed up, the creation time, the modification time, the data source, and the information of the data to be backed up. Alternatively, the notification message sent by the first device 301 may also include the information of the data to be backed up in the first device 301, so that the processing module 3023 may display the second page according to the received information of the data to be backed up.

[0094] Exemplarily, in addition to displaying the information of the data to be backed up on the first device, the second page may also prompt the user to enter encryption information for encrypting the first backup data. Afterwards, the processing module 3023 receives the user's operation of entering encryption information on the second page, and sends a data backup request to the first device 301. The data backup request may also include the encryption information entered by the user, so that the first device 301 can receive the encryption information. After receiving the encryption information, the data backup module 3012 of the first device 301 encrypts the first backup data using the encryption information.

[0095] Exemplarily, after receiving the encrypted first backup data, the second device 302 may decrypt the encrypted first backup data according to the encryption information to obtain the first backup data.

[0096] Exemplarily, after receiving the data backup request, the data backup module 3012 of the first device 301 may encrypt the first device data using a preset key to obtain the encrypted first backup data. Also, the first device 301 sends the encrypted first backup data and the preset key to the second device 302.

[0097] Exemplarily, after receiving the encrypted first backup data and the preset key, the second device 302 may decrypt the encrypted first backup data according to the preset key to obtain the first backup data.

[0098] In some embodiments, the second device 302 serves as a device for storing backup data and can also connect to a third device (such as a device in normal operating state with a usable screen) and send the saved backup data to the third device so that the third device can restore data based on the backup data, so that the user can use the data of the application software on the first device 301 or the user data on the first device 301 on the third device.

[0099] Alternatively, the second device 302 may also perform data recovery locally based on the backup data through the data recovery module 3022 .

[0100] The first device 301 in the above application scenario is in a faulty state, indicating that the screen of the first device 301 is unavailable. Wherein, when the screen of the first device 301 is unavailable, in order to ensure the normal communication between the first device 301 and the second device 302 and the normal progress of the data backup process, the "minimum system" in the first device 301 can operate normally. Wherein, the "minimum system" refers to a set of tailored software that can be run on the first device 301 (i.e., the faulty machine), and the hardware units in the "minimum system" that can support the normal operation of these software modules may include: central processing unit (CPU), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), universal flash storage (UFS) / embedded non-volatile memory (EMMC), universal serial bus (USB) / wireless fidelity (WIFI) module, security chip, etc. Other hardware units are turned off in the "minimum system" mode.

[0101] Exemplarily, the “minimum system” may include the communication module, data backup module, authentication module, storage module, etc. in the first device 301 described in the aforementioned embodiment.

[0102] The "minimum system" can ensure that the operating system state of the first device 301 (i.e., the faulty machine) is stable. The reason is that usually the software in the operating system is dependent on each other. When certain hardware failures cause the operating system to malfunction, the operating system will frequently crash and become very unstable. Running the above "minimum system" can shut down unnecessary hardware subsystems and not start the associated software, which will not introduce related disordered states, thereby eliminating the impact of other hardware failures on the stability of the operating system and ensuring that the data backup-related software modules can operate normally.

[0103] The "minimum system" can also reduce the power consumption of the operating system. The reason is that running the "minimum system" can shut down unnecessary components or services in the hardware subsystem, such as the graphics processing unit (GPU), modem, multimedia, touch screen, liquid crystal display (LCD), audio, etc., which can greatly reduce the power consumption of the operating system and is conducive to the long-term battery life of the first device 301 (i.e., the faulty device) during data backup.

[0104] The "minimal system" can also reduce RAM usage. The reason is that RAM is a valuable resource in the operating system. When running the "minimal system", only the necessary software modules are started to complete the data backup function, and other unnecessary components or services are not started, thereby reducing the RAM resource usage.

[0105] In some embodiments, see Figure 6 As shown, when the first device 301 runs with the above-mentioned "minimum system", a USB virtual serial port can be enumerated, such as a personal computer user interface (PCUI) port, etc. Afterwards, the second device 302 can input unlocking information, encryption information, etc. to the first device 301 through the PCUI port. When the first device 301 determines that the unlocking information matches the preset information, it can open an Android debug bridge (ADB) port (a type of USB port) to achieve the transmission of the first backup data through the ADB port.

[0106] Furthermore, in the above method, the communication protocol control can be completed through the PCUI port, and ADB only serves as a data transmission channel and works under the control of the communication protocol.

[0107] In some embodiments, the first device 301 and the second device 302 can communicate with each other through a preset connection method, and the preset connection method may include connection through a universal serial bus USB, connection through a lightning interface Lightning, connection through wireless fidelity WIFI technology, or connection through Bluetooth, etc. That is to say, the first device 301 and the second device 302 can be connected via a wired method or a wireless method, and there is no specific limitation on this in the embodiments of the present application.

[0108] In addition, the communication between the first device 301 and the second device 302 may be completed by a communication module in the first device 301 and a communication module in the second device 302 .

[0109] In some embodiments, the communication between the first device 301 and the second device 302 may adopt a communication protocol in TLV format. T, L, and V in the TLV format represent Type, Length, and Value, respectively, that is, as shown in Table 1 below, TLV includes three fields: Type, Length, and Value. Type represents the message type (or frame type) of the communication protocol in TLV format, Length represents the message length (or frame length), and Value represents the message content (or frame content).

[0110] Table 1

[0111] Type Length Value

[0112] Exemplarily, the above frame types may include authentication frames, data frames, control frames, etc.

[0113] The authentication frame includes an authentication request and an authentication response, wherein the second device 302 initiates an authentication request to the first device 301, and the authentication request may include unlocking information input by the user on the display page of the second device 302. In response to the authentication request, the first device 301 determines whether the unlocking information in the authentication request matches the preset information. If so, the first device 301 sends a data response (such as the above-mentioned notification message) to the second device 302 to inform the second device 302 that the data request can be initiated.

[0114] The data frame includes a data request and a data response, wherein the second device 302 initiates a data request (i.e., the aforementioned data backup request) to the first device 301, and the first device 301 responds to the data request, determines the size of the storage space occupied by the data to be backed up, and notifies the second device 302, i.e., sends a data response to the second device 302, so as to inform the second device 302 that it can perform a conditional judgment (such as whether the storage space size meets the requirements, etc.).

[0115] The control frame includes a control request and a control response. When the second device 302 determines that the conditions are met, the second device 302 initiates a control request to the first device 301. In response to the control request, the first device 301 sends the prepared data to be backed up to the second device 302, that is, sends a control response to the second device 302.

[0116] The above-mentioned data backup method in the embodiment of the present application can achieve the purpose of backing up the data in the faulty first device to the second device. Among them, the fault state of the first device can indicate that the screen of the first device is unavailable. When the screen of the first device is unavailable, the user does not need to operate on the first device to complete the backup of the data on the first device. The first device can directly send the backup data to the second device according to the data backup request of the second device. In this way, when the screen of the first device is unavailable, the data backup on the first device can also be completed, which will not cause the data loss on the first device, and ensure the user experience.

[0117] In addition, the above method can realize data transmission between the first device and the second device without the need for additional devices such as USB flash drives, which can reduce unnecessary expenses or costs. Moreover, without using USB flash drives, the time between backing up data from the first device to the second device can also be reduced, thereby improving data backup performance.

[0118] The first device and the second device mentioned above may be electronic devices such as a mobile phone, a laptop computer, a personal computer (PC), a tablet computer, etc.

[0119] See also Figure 7 As shown, the data backup method in the embodiment of the present application may include the following steps S701-S703.

[0120] S701. The second device sends a data backup request to the first device.

[0121] Before the second device sends a data backup request, the second device needs to be connected to the first device to ensure normal communication between the first device and the second device. The connection method may include wired connection (such as via USB connection), wireless connection (such as via WIFI connection), etc.

[0122] Furthermore, the second device may send a data backup request to the first device when the first device is in a fault state, wherein the fault state of the first device may include that the screen of the first device is unavailable.

[0123] In some embodiments, the first device may be provided with a lock screen function or a lock function to ensure the security of the data and information on the first device. In this case, in order to ensure that the second device can back up the data or information on the first device, the user needs to input the unlocking information (such as an unlocking code, unlocking string, unlocking gesture, unlocking fingerprint, unlocking voiceprint, etc.) used to unlock the first device on the second device, thereby releasing the lock screen function or the lock function of the first device, so that the data or information on the first device can be transmitted to the second device.

[0124] And, the second device may display the first page, wherein the first page may prompt to input unlock information of the first device. When the user inputs the unlock information on the first page, the second device sends a data backup request to the first device, thereby requesting to back up the data or information on the first device.

[0125] For example, see Figure 8 As shown, the first page may display an input box for inputting unlock information. The user may input the unlock information of the first device on the first page to unlock the first device so that the file system of the first device can be used. After the user inputs the unlock information on the first page, he clicks the "Confirm" control, and the second device may send a data backup request to the first device in response to the user inputting the unlock information.

[0126] In some embodiments, the second device may display the first page after connecting to the first device. Alternatively, the second device may provide a data backup function for the first device after connecting to the first device, and then display the first page in response to the user's selection operation for the data backup function.

[0127] In some embodiments, when the first device is not provided with a lock screen function or a lock function, the second device may send a data backup request to the first device after connecting with the first device. Alternatively, when the first device is not provided with a lock screen function or a lock function, the second device may also provide a data backup function for the first device after connecting with the first device, and then, in response to the user's selection operation for the data backup function, the second device sends a data backup request to the first device.

[0128] In some embodiments, the application software data and user data stored on the first device can be divided into different types according to attributes, sources, etc., such as picture data, text message data, contact data, call record data, video data, audio data, document data, application A data, etc., and each type of data also corresponds to the size of the storage space occupied by each type. When backing up data, the user can choose to back up some types of data according to actual needs, or choose to back up all types of data.

[0129] Furthermore, the second device may display a second page, wherein the second page may display information about different data types and / or occupied storage space waiting for backup data on the first device. When the user selects data to be backed up on the second page, the second device sends a data backup request to the first device, thereby requesting to back up the corresponding data on the first device.

[0130] For example, see Fig. 9 As shown, the second page can display the controls corresponding to different data types on the first device and information about the data to be backed up, such as the specific type name, the size of the storage space occupied, etc. The user can select the controls corresponding to the data to be backed up on the second page, such as selecting contact data, selecting controls corresponding to picture data, etc. After the selection is completed, the user can click the "Start Backup" control to send a data backup request to the first device. Exemplarily, when the control corresponding to the data to be backed up is not selected, it can be gray on the second page, and after being selected by the user, it can be blue in a prominent and obvious color to distinguish it from the unselected controls.

[0131] In some embodiments, the second device may display the second page after connecting to the first device. Alternatively, the second device may provide a data backup function for the first device after connecting to the first device, and then display the second page in response to the user's selection operation for the data backup function.

[0132] In some embodiments, the second device may be pre-configured with preset data type information, etc. After the second device is connected to the first device, it can display the second page according to the preset data type information, so that the user can select the data to be backed up on the first device on the second page. Alternatively, after the second device is connected to the first device, it can also obtain the information of the data to be backed up on the first device, so that the second device can display the second page according to the obtained information of the data to be backed up. In this way, since the information of the data to be backed up is obtained from the first device, the information of the data to be backed up can better reflect the real type of the data to be backed up on the first device and the real storage space occupied. Therefore, the information of the data to be backed up on the second page displayed by the second device can also be more accurate and more in line with the real situation of the data on the first device.

[0133] S702: The first device receives a data backup request, and determines first backup data in the first device in response to the data backup request.

[0134] In some embodiments, if the user enters unlocking information on the first page, the data backup request may include the unlocking information, so that the first device can unlock the first device according to the unlocking information in the data backup request.

[0135] Exemplarily, the first device may compare the unlock information in the data backup request with the preset information stored in the first device, and if the two match, continue to determine the first backup data that needs to be backed up on the second device. The unlock information matches the preset information, including that the unlock information is the same as the preset information, or that the similarity between the unlock information and the preset information is greater than or equal to the preset similarity, etc., and this is not specifically limited in the embodiments of the present application.

[0136] The above process of comparing the unlocking information with the preset information can also be called an authentication or verification process. When the unlocking information matches the preset information, it can be regarded as a successful authentication or verification. In this case, the first device allows the second device to back up the data on the first device, and the first device continues to determine the first backup data.

[0137] In some embodiments, if the first device is not provided with a lock screen function or a lock function, then after receiving the data backup request, the second device may directly respond to the data backup request and determine the first backup data.

[0138] The first backup data may be part or all of the application software data and user data stored in the first device.

[0139] In some embodiments, if the user selects data to be backed up on the second page above, the data backup request may include information about the data to be backed up selected by the user, such as the data type, etc., so that the first device can determine the first backup data in the first device based on the information about the data to be backed up in the data backup request.

[0140] Exemplarily, if the information of the data to be backed up in the data backup request indicates that the data to be backed up selected by the user is picture data, or the data type in the information of the data to be backed up is picture data, the first device may determine the picture data in the first device as the first backup data.

[0141] S703: The first device sends the first backup data to the second device.

[0142] In some embodiments, the application software data and user data in the first device can be stored in the ROM of the first device. When the first device sends the first backup data to the second device, the first backup data in the ROM can be directly sent to the second device. Alternatively, the first device can also save the first backup data in the ROM to a memory buffer such as RAM, and the first device then encrypts the first backup data in the RAM and sends the encrypted first backup data to the second device, thereby ensuring the security of data transmission between the first device and the second device and reducing the risk of leakage or tampering during the data transmission process. In this case, after the second device receives the encrypted first device data, it decrypts the data to obtain the first backup data.

[0143] In some embodiments, the first device may also process the first backup data in a memory buffer such as RAM in segments to obtain at least one data segment, and send at least one data segment to the second device in sequence. Alternatively, the first device may also process the encrypted first backup data in a memory buffer such as RAM in segments to obtain at least one data segment, and send at least one data segment to the second device in sequence. In this way, when the data of the first device is large and requires a long transmission time, the segmented processing of the data of the first device can achieve the purpose of data breakpoint resumption.

[0144] The above data backup method can achieve the purpose of backing up the data in the failed first device to the second device. Among them, the failure state of the first device can indicate that the screen of the first device is unavailable. When the screen of the first device is unavailable, the user does not need to operate on the first device to complete the backup of the data on the first device. The first device can directly send the backup data to the second device according to the data backup request of the second device. In this way, when the screen of the first device is unavailable, the data backup on the first device can also be completed, which will not cause the data loss on the first device, and ensure the user experience.

[0145] In addition, in some cases, if the ROM of the first device is used directly to read and encrypt the first backup data, the ROM may be required to provide additional storage space. When the amount of data of the first backup data is large, the additional storage space required to be provided by the ROM will also be relatively large. If the ROM space is insufficient, it is likely to affect the backup process of the first backup data and affect the user experience.

[0146] The above-mentioned data backup method in the embodiment of the present application can save the first backup data to a memory buffer such as RAM, which can reduce the occurrence of unsuccessful data backup due to insufficient ROM space in the first device. While ensuring user experience, no additional ROM space is required, and a purpose similar to zero space (such as ROM space) backup can be achieved.

[0147] In some embodiments, see Fig.10 As shown, the second device may also display the first page first, and in response to the user inputting unlock information on the first page, send unlock information to the first device. The first device performs an authentication or verification operation according to the unlock information, and when the unlock information matches the preset information, the first device sends a notification message to the second device to notify the second device that the data backup operation can be performed. The second device receives the notification message, and in response to the notification message, displays the second page, and in response to the user selecting the data to be backed up on the second page, sends a data backup request to the first device.

[0148] The specific displayed content and functions of the first page and the second page can be found in the above-mentioned embodiments, which will not be described in detail here.

[0149] And, in some embodiments, if the preset data type information is not configured on the second device, the first device may send information about the data to be backed up on the first device to the second device, and the information about the data to be backed up may be included in the notification message. Thus, the second device may display the second page according to the information about the data to be backed up in the notification message.

[0150] In some embodiments, after receiving a data backup request, or after the unlock information matches the preset information, the aforementioned first device can also "scan" the local data to be backed up, and then determine which data can be backed up locally. In some embodiments, the second device can directly display the above-mentioned second page after the data is "scanned", and the user can select the data to be backed up. In some embodiments, in order to provide users with a more intuitive data backup process, the second device can also present the "scanning" process of the first device to the user or prompt the user that the device is scanning data. During this process, the first device can provide the second device with the "scanning" progress of the data on the first device in real time, so that the second device can provide prompt information to the user in time. Afterwards, after the "scan" on the first device is completed, the second device displays the above-mentioned second page again.

[0151] For example, when the unlock information received by the first device matches the preset information, the first device may send a notification message to the second device. At the same time, the first device may start to "scan" the data to be backed up on the first device and periodically send scanning progress information to the second device during the "scanning" process. After receiving the notification message, the second device may first display the following in response to the notification message: Fig.11The third page is shown, wherein a prompt such as "Scanning" may be displayed on the third page, and after receiving the scanning progress information, the second device updates and displays the third page, such as updating the scanning progress to 20%, 80%, etc. When the scanning on the first device is completed, the second device may continue to display the second page.

[0152] Alternatively, after receiving the scanning progress information, the second device may also determine which type of data is currently scanned by the first device according to the scanning progress information, and display the scanning progress of the type of data at the control position of the corresponding type of data on the third page.

[0153] As another example, after receiving the data backup request, the first device may also first send a notification message to the second device. At the same time, the first device may start to "scan" the data to be backed up on the first device, and periodically send scanning progress information to the second device during the "scanning" process. After receiving the notification message, the second device may first display the following information in response to the notification message: Fig.11 As shown in the third page, after receiving the scanning progress information, the second device updates and displays the third page.

[0154] In some embodiments, the first device may also perform the "scan" of the data to be backed up passively. For example, after the second device is connected to the first device or after receiving the notification message sent by the first device, the second device may first display the following information: Fig.12 The fourth page shown. The second device can display the fourth page according to the aforementioned preset data type information, or display the fourth page according to the information of the data to be backed up in the notification message. In addition, the fourth page also displays a "scan" control that prompts the user to scan the data. If the user determines that a data backup operation is required, the user can click the "scan" control on the fourth page to control the first device to start scanning the data to be backed up. Afterwards, the second device can further display the above-mentioned third page, second page, etc. according to the scanning progress of the first device, which will not be repeated here.

[0155] In some embodiments, the encryption information used by the first device to encrypt the first backup data may be obtained from the second device.

[0156] Exemplarily, the second page may also prompt you to enter encryption information for encrypting the first backup data, see Fig.13 As shown, a text prompt and an input box for inputting encryption information may also be displayed on the second page, and the user may input encryption information for encrypting the first backup data on the second page. Afterwards, the second device may send a data backup request to the first device in response to the user inputting the encryption information, and the data backup request may include the encryption information.

[0157] After receiving the data backup request, the first device can obtain the encryption information from the data backup request, and then use the encryption information to encrypt the first backup data saved in the memory buffer such as RAM. Then, the first device sends the encrypted first backup data in the memory buffer to the second device. After the user inputs the encryption information, the second device can save the encryption information. When the second device receives the encrypted first backup data sent by the first device, it uses the saved encryption information to decrypt the received data, thereby obtaining the first backup data.

[0158] In this way, the first device encrypts the first backup data before sending it, which can ensure the security of the first backup data; the second device then uses the same encryption information to decrypt the received data to obtain accurate first backup data, thereby completing the data backup operation between the first device and the second device.

[0159] In some embodiments, the encryption information used by the first device to encrypt the first backup data may also be preset in the first device, such as a preset key. Exemplarily, the first device may use the preset key to encrypt the first backup data saved in a memory buffer such as RAM. Then, the first device sends the encrypted first backup data and the preset key in the memory buffer to the second device. After receiving the encrypted first backup data and the preset key, the second device decrypts the encrypted first backup data according to the preset key to obtain the first backup data.

[0160] In this way, the first device and the second device can also use the same preset key to encrypt and decrypt the first backup data, which can not only ensure the security of the first backup data, but also better complete the data backup operation between the first device and the second device.

[0161] In the above embodiment, since the first device fails, in order to avoid the loss of application software data, user data, etc. stored in the first device, the data in the first device can be backed up to the second device. After the second device obtains the first backup data, the operation of backing up the data on the first device is completed.

[0162] After that, if the user still wants to use the backed-up data, in some embodiments, the user can connect the second device to other electronic devices that can operate normally (such as a third device), so that the second device can send the data backed up from the first device (i.e., the first backup data) to the third device, and the third device performs a data recovery operation based on the first backup data. After the data recovery operation is completed, the user can use the first backup data on the third device, for example, view pictures backed up from the first device on the third device, listen to audio backed up from the first device, etc., or, if the third device has the same application software as the first device installed, when the user uses the application software on the third device, the user can view the history records, contacts, chat records, etc. when using the application software on the first device.

[0163] In some embodiments, after obtaining the first backup data, the second device can also perform a data recovery operation based on the first backup data when the user needs to use the backed-up data. After the data recovery operation is completed, the user can use the first backup data on the second device, for example, view pictures backed up from the first device, listen to audio backed up from the first device, etc. on the second device, or, if the second device has the same application software as the first device installed, when the user uses the application software on the second device, the user can view the history records, contacts, chat records, etc. when using the application software on the first device.

[0164] Exemplarily, the user can select the data recovery function on the third device (or the second device), and then control the third device to display the recovery page. Information about the data to be recovered can be displayed on the data recovery page, such as the control corresponding to the data to be recovered, the type of data to be recovered, the size of the storage space occupied, etc. Among them, the data to be recovered is the first backup data. The user can select the control corresponding to the data to be recovered on the data recovery page according to his own needs, and then select the data to be recovered. In this way, the third device can recover the corresponding data in response to the user's selection operation.

[0165] It can be seen that the above-mentioned data backup method in the embodiment of the present application can not only realize the data backup operation, but also realize the data recovery operation when the first device used by the user fails, thereby providing the user with a better user experience.

[0166] It is understandable that in the embodiments of the present application, the collection, storage, use, processing, transmission, provision and disclosure of user data involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals. For example, in the embodiments of the present application, the first device obtains user data, historical records, chat records, call records, etc. of the user's use of application software, which is done with the authorization of the user; the first device sends user data, historical records, chat records, call records, etc. to the second device, which is done with the authorization of the user; and the second device sends user data, historical records, chat records, call records, etc. to the third device, which is also done with the authorization of the user.

[0167] In some schemes, multiple embodiments of the present application can be combined, and the combined scheme can be implemented. Optionally, some operations in the process of each method embodiment are optionally combined, and / or the order of some operations is optionally changed. In addition, the execution order between the steps of each process is only exemplary and does not constitute a restriction on the execution order between the steps. There can also be other execution orders between the steps. It is not intended to show that the execution order is the only order in which these operations can be performed. A person of ordinary skill in the art will think of a variety of ways to reorder the operations described in the embodiments of the present application. In addition, it should be noted that the process details involved in a certain embodiment of the present application are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0168] In addition, some steps in the method embodiment may be equivalently replaced by other possible steps. Alternatively, some steps in the method embodiment may be optional and may be deleted in certain usage scenarios. Alternatively, other possible steps may be added to the method embodiment.

[0169] Furthermore, the various method embodiments may be implemented separately or in combination.

[0170] It is understandable that in order to implement the above functions, the aforementioned electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

[0171] In this embodiment, the electronic device can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0172] The present application also provides an electronic device, such as Fig.14 As shown, the electronic device may include one or more processors 1401 , a memory 1402 and a communication interface 1403 .

[0173] The memory 1402 and the communication interface 1403 are coupled to the processor 1401. For example, the memory 1402, the communication interface 1403 and the processor 1401 may be coupled together via a bus 1404.

[0174] The communication interface 1403 is used for data transmission with other devices. The memory 1402 stores computer program code. The computer program code includes computer instructions. When the computer instructions are executed by the processor 1401, the electronic device executes the data backup method in the embodiment of the present application.

[0175] Among them, the processor 1401 can be a processor or a controller, for example, it can be a central processing unit (CPU), a general processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the contents of the embodiments of the present application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0176] The bus 1404 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus 1404 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.14 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0177] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program code is stored. When the processor executes the computer program code, the electronic device executes the relevant method steps in the method embodiment.

[0178] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the relevant method steps in the above method embodiment.

[0179] Among them, the electronic device, computer storage medium or computer program product provided in this application is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0180] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0181] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0182] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0183] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0184] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0185] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data backup method, characterized in that: Applied to a data backup system, the data backup system includes a first device and a second device, the first device communicates with the second device, the first device is in a fault state, and the fault state includes a screen of the first device being unavailable; The method comprises: The second device sends a data backup request to the first device; The first device receives the data backup request, and determines first backup data in the first device in response to the data backup request; The first device sends the first backup data to the second device.

2. The method according to claim 1, characterized in that The second device sending a data backup request to the first device includes: The second device displays a first page, where the first page is used to prompt for input of unlocking information of the first device; In response to the user inputting the unlocking information on the first page, the second device sends the data backup request to the first device.

3. The method according to claim 2, characterized in that The data backup request includes the unlocking information; In response to the data backup request, the first device determines first backup data in the first device, including: When the unlocking information in the data backup request matches preset information, the first device determines the first backup data.

4. The method according to claim 1, wherein The second device sending a data backup request to the first device includes: The second device displays a second page, where the second page is used to display information about the data to be backed up on the first device; In response to the user selecting the data to be backed up on the second page, the second device sends the data backup request to the first device.

5. The method according to claim 4, characterized in that The data backup request includes information about the data to be backed up selected by the user; In response to the data backup request, the first device determines first backup data in the first device, including: The first device determines first backup data from the data to be backed up of the first device according to information of the data to be backed up selected by the user in the data backup request.

6. The method according to claim 1, wherein The second device sending a data backup request to the first device includes: The second device displays a first page, where the first page is used to prompt for input of unlocking information of the first device; In response to the user inputting the unlock information on the first page, the second device sending the unlock information to the first device; The second device receives a notification message sent by the first device, where the notification message is a message sent by the first device when the unlock information matches the preset information; In response to the notification message, the second device displays a second page, where the second page is used to display information about the data to be backed up on the first device; In response to the user selecting the data to be backed up on the second page, the second device sends the data backup request to the first device.

7. The method according to claim 6, characterized in that The data backup request includes information about the data to be backed up selected by the user; In response to the data backup request, the first device determines first backup data in the first device, including: The first device determines first backup data from the data to be backed up of the first device according to information of the data to be backed up selected by the user in the data backup request.

8. The method according to claim 6 or 7, characterized in that The notification message includes information about the data to be backed up on the first device; In response to the notification message, the second device displays a second page, including: The second device displays the second page according to the information of the data to be backed up in the notification message.

9. The method according to any one of claims 4 to 8, characterized in that The second page is further used to prompt for input of encryption information for encrypting the first backup data; the data backup request also includes the encryption information; and the first device sending the first backup data to the second device includes: The first device saves the first backup data to a memory buffer; The first device encrypts the first backup data in the memory buffer using the encryption information in the data backup request, and sends the encrypted first backup data to the second device.

10. The method according to claim 9, characterized in that The method further comprises: The second device receives the encrypted first backup data; The second device decrypts the encrypted first backup data according to the encryption information to obtain the first backup data.

11. The method according to any one of claims 1 to 8, characterized in that The first device sending the first backup data to the second device includes: The first device saves the first backup data to a memory buffer; The first device encrypts the first backup data in the memory buffer using a preset key, and sends the encrypted first backup data and the preset key to the second device.

12. The method according to claim 11, characterized in that The method further comprises: The second device receives the encrypted first backup data and the preset key; The second device decrypts the encrypted first backup data according to the preset key to obtain the first backup data.

13. The method according to any one of claims 9 to 12, characterized in that: The first device sending the encrypted first backup data to the second device includes: The first device processes the encrypted first backup data in the memory buffer into segments to obtain at least one data segment; The first device sends the at least one data segment to the second device in sequence.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: When the second device is connected to a third device, the second device sends the first backup data to the third device; The third device performs data recovery according to the first backup data.

15. The method according to any one of claims 1 to 14, characterized in that The first device communicates with the second device through a preset connection method, and the preset connection method includes connection through a universal serial bus USB, connection through a lightning interface Lightning, or connection through wireless fidelity WIFI technology.

16. A data backup method, characterized in that: A first device is applied to a data backup system, the data backup system further comprising a second device, the first device communicating with the second device, the first device being in a fault state, the fault state comprising an unavailable screen of the first device; the method comprising: receiving a data backup request sent by the second device; In response to the data backup request, determining first backup data in the first device; Send the first backup data to the second device.

17. The method according to claim 16, characterized in that The data backup request is sent by the second device in response to a user inputting unlocking information on a first page, where the first page is used to prompt the user to input the unlocking information of the first device.

18. The method according to claim 17, characterized in that The data backup request includes the unlocking information; The step of determining, in response to the data backup request, first backup data in the first device includes: When the unlocking information in the data backup request matches preset information, the first backup data is determined.

19. The method according to claim 16, wherein The data backup request is sent by the second device in response to a user selecting data to be backed up on a second page, where the second page is used to display information about the data to be backed up on the first device.

20. The method according to claim 19, characterized in that The data backup request includes information about the data to be backed up selected by the user; The step of determining, in response to the data backup request, first backup data in the first device includes: According to the information of the data to be backed up selected by the user in the data backup request, first backup data is determined in the data to be backed up of the first device.

21. The method according to claim 16, wherein The receiving the data backup request sent by the second device includes: receiving unlock information sent by the second device, where the unlock information is sent by the second device in response to a user inputting unlock information on a first page, where the first page is used to prompt for input of the unlock information for the first device; When the unlock information matches the preset information, sending a notification message to the second device; Receive a data backup request sent by the second device, where the data backup request is sent by the second device in response to a user selecting data to be backed up on a second page, the notification message is used to instruct the second device to display the second page, and the second page is used to display information about the data to be backed up on the first device.

22. The method according to claim 21, characterized in that The data backup request includes information about the data to be backed up selected by the user; The step of determining, in response to the data backup request, first backup data in the first device includes: According to the information of the data to be backed up selected by the user in the data backup request, first backup data is determined in the data to be backed up of the first device.

23. The method according to claim 21 or 22, characterized in that The notification message includes information about the data to be backed up on the first device; the notification message is used to instruct the second device to display the second page according to the information about the data to be backed up.

24. The method according to any one of claims 19 to 23, characterized in that The second page is further used to prompt for input of encryption information for encrypting the first backup data; the data backup request also includes the encryption information; and sending the first backup data to the second device includes: Saving the first backup data to a memory buffer; The first backup data in the memory buffer is encrypted using the encryption information in the data backup request, and the encrypted first backup data is sent to the second device.

25. The method according to any one of claims 16 to 23, characterized in that The sending the first backup data to the second device includes: Saving the first backup data to a memory buffer; The first backup data in the memory buffer is encrypted using a preset key, and the encrypted first backup data and the preset key are sent to the second device, where the preset key is used by the second device to decrypt the first backup data.

26. The method according to claim 24 or 25, characterized in that The sending the encrypted first backup data to the second device includes: Segmenting the encrypted first backup data in the memory buffer to obtain at least one data segment; The at least one data segment is sent to the second device in sequence.

27. The method according to any one of claims 16 to 26, characterized in that The first device communicates with the second device through a preset connection method, and the preset connection method includes connection through a universal serial bus USB, connection through a lightning interface Lightning, or connection through wireless fidelity WIFI technology.

28. A data backup system, characterized in that: The method comprises a first device and a second device, wherein the first device communicates with the second device, and the first device is in a fault state, wherein the fault state includes that a screen of the first device is unavailable; The second device is configured to send a data backup request to the first device; The first device is configured to receive the data backup request and determine first backup data in the first device in response to the data backup request; The first device is configured to send the first backup data to the second device.

29. An electronic device, characterized in that: It includes a memory and one or more processors; the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the data backup method as described in any one of claims 16 to 27.

30. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on an electronic device, enable the electronic device to execute the data backup method according to any one of claims 16 to 27.