CN117130826A

CN117130826A - Data backup method, electronic equipment, data backup system and storage medium

Info

Publication number: CN117130826A
Application number: CN202310228432.7A
Authority: CN
Inventors: 李创军
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-02-28
Filing date: 2023-02-28
Publication date: 2023-11-28

Abstract

The application provides a data backup method, electronic equipment, a data backup system and a storage medium, and relates to the technical field of equipment cloning, wherein the method can determine the compatibility of an application to be backed up in source equipment and target equipment by comparing version information of the application installed in the source equipment with system information and hardware information of the target equipment, and can download a version compatible with the application and the target equipment from a server aiming at the application of a version incompatible with the target equipment in the source equipment; by the method, the phenomenon of abnormal operation of the target equipment after data backup caused by compatibility problems can be reduced.

Description

Data backup method, electronic equipment, data backup system and storage medium

Technical Field

The embodiment of the application relates to the technical field of equipment cloning, in particular to a data backup method, electronic equipment, a data backup system and a storage medium.

Background

The user may change the electronic device during use of the electronic device for various reasons. As an example, during the use of an old mobile phone, a new mobile phone may be replaced for use due to damage to the old mobile phone or the need for an update. When a new mobile phone is replaced, the mobile phone cloning technology can be adopted to backup the application and user data in the old mobile phone to the new mobile phone.

Currently, after an application and user data in a source device are backed up to a target device, when the application backed up on the target device is used, a phenomenon that the application crashes (e.g., forcefully exits) or functions abnormally occurs.

Disclosure of Invention

The embodiment of the application provides a data backup method, electronic equipment, a data backup system and a storage medium, which can reduce the phenomenon of abnormality when using backup application on target equipment after data backup.

In order to achieve the above purpose, the application adopts the following technical scheme:

in a first aspect, an embodiment of the present application provides a data backup method, including:

the first equipment acquires configuration information of the second equipment;

the first device obtains compatibility information of an application of the first device and the second device based on configuration information of the second device, wherein the compatibility information comprises: an application identifier of a first type of application, which is compatible with the second device, and an application identifier of a second type of application, which is incompatible with the second device, of an application version in the application of the first device;

the first device sends backup data and the compatibility information to the second device, wherein the compatibility information is used for indicating the second device to backup the first type application based on an installation package of the first type application in the backup data, and downloading an installation package of an application version and a second type application compatible with the second device from a first server and installing the application version and the second type application compatible with the second device when networking.

In the application, the first device can determine the compatible information of the application in the first device and the second device based on the version information of the application in the first device (the application which needs to be backed up and is selected by the user) and the configuration information of the second device, and send the backup data of the first device and the compatible information to the second device together, and the second device can select different processing modes based on different types of applications in the compatible information, so that the application backed up to the second device is compatible with the second device, thereby reducing the abnormal phenomenon when the application backed up on the target device is used after data backup.

As an implementation manner of the first aspect, the obtaining, by the first device, compatibility information of an application of the first device and the second device based on configuration information of the second device includes:

the first device sends an application version of an application of the first device and configuration information of the second device to a second server;

the first device receives compatibility information of the application of the first device and the second device, which is sent by the second server, wherein the compatibility information is determined based on an application version of the application of the first device and configuration information of the second device.

According to the application, the characteristics of the matching relation of the compatibility between different application versions and different device configurations can be stored in a large quantity by using the server, and the compatibility analysis is carried out by the server, so that the power consumption of the electronic device can be reduced, and the storage space of the electronic device can be saved.

As an implementation manner of the first aspect, after the obtaining, by the first device, compatibility information of an application of the first device and the second device, the method further includes:

the first device sends out first prompt information, wherein the first prompt information is used for prompting a user that a second type of application incompatible with the second device exists in the application to be backed up;

the first equipment receives a backup instruction of a user, wherein the backup instruction is used for indicating that the user knows the risk of backing up the second type of application and agrees to continue data backup;

correspondingly, after the first device receives a backup instruction of a user, the first device sends backup data and the compatible information to the second device.

In the application, before the data backup is carried out, the risk of backing up the application version in the second equipment and the second type application incompatible with the second equipment can be informed to the user, and the user experience can be improved when the user is confirmed to know the risk and the same continuous backup is carried out on the data backup of the second type application.

As an implementation manner of the first aspect, the configuration information includes system information of the second device;

the second class of applications is applications in which the application version of the application of the first device is incompatible with the system of the second device.

In the embodiment of the application, the second device can download another version from the server to reduce the abnormal phenomenon of the application, and the application version and the system of the second device are required to be incompatible, otherwise, even if the application version is replaced, the second device is possibly incompatible.

As an implementation manner of the first aspect, the configuration information further includes: hardware information of the second device;

the compatibility information further includes: application identification of a third class of applications in the application of the first device that are incompatible with the hardware of the second device.

In the application, a third type of application incompatible with the hardware of the second device can exist in the application to be backed up to the second device, and the application needs to be independently set, and can not be processed according to the first type of application and the second type of application, but can not be backed up any more, thereby further reducing the abnormal phenomenon of the application backed up in the second device.

As an implementation manner of the first aspect, the first prompting information is further used for prompting a user that a third type of application incompatible with the second device exists in the applications to be backed up.

As an implementation manner of the first aspect, the backup data does not include: an application installation package of a second type of application, an application installation package of a third type of application, and user data corresponding to the third type of application, wherein the application version of the second type of application is incompatible with a system of the second device;

the backup data includes: and user data corresponding to the second type of application.

In the application, in order to reduce the waste of network resources between the first device and the second device, the first device may not send an application installation package of a second type of application, which is not needed by the second device in the first device during backup, and an application installation package of a third type of application and user data to the second device, but because the second device can acquire the application version and the second type of application compatible with the second device through other ways, the user data corresponding to the second type of application also needs to be transmitted to the second device, thereby avoiding the loss of the user data.

In a second aspect, an embodiment of the present application provides a data backup method, including:

the second equipment receives first information sent by the first equipment;

if the first information comprises backup data and compatible information, the second device backs up a first type of application in the backup data based on an application identifier of the first type of application in the compatible information received from the first device, wherein the first type of application is an application version in the application of the first device and an application compatible with the second device;

the second device downloads an installation package of an application version and a second type application compatible with the second device from a first server based on an identification of the second type application in the compatibility information received from the second device, and installs the application version downloaded from the first server and the second type application compatible with the second device, wherein the second type application is an application of which the application version in the application of the first device and the second device are incompatible.

As an implementation manner of the second aspect, after the second device receives the first information sent by the first device, the method further includes:

if the first information includes the backup data and version information and the first information does not include the compatible information, the second device sends the version information and configuration information of the second device to a second server, wherein the version information is an application version of an application installation package included in the backup data;

The second device receives compatibility information sent by the second server, where the compatibility information includes: application identifiers of first-class applications compatible with the second equipment and application versions in the backup data and application identifiers of second-class applications incompatible with the second equipment;

the second device backs up the first type of application in the backup data based on the application identification of the first type of application in the compatibility information received from the second server;

the second device downloads an installation package of an application version and a second type application compatible with the second device from a first server based on an identification of the second type application in the compatibility information received from the second server, and installs the application version downloaded from the first server and the second type application compatible with the second device.

In the application, the source device for backing up the data to the second device may not have the function corresponding to the data backup method provided by the application, so that the first device backed up to the second device cannot obtain the application in the first device and the compatible information of the second device, in this case, the second device may send the application version corresponding to the installation package of each application contained in the backup data and the configuration information of the second device to the server to obtain the compatible information, so that the second device serving as the target device may reduce the abnormal phenomenon of the backed up application even if the first device does not have the function corresponding to the data backup method provided by the application.

As an implementation manner of the second aspect, before the second device downloads, from the first server, an installation package of an application version and a second type of application compatible with the second device, the method further includes:

the second device determines that the second device has been networked.

As an implementation manner of the second aspect, the method further includes:

and if the second device is not networked, the second device generates icons of the second type of applications in the backup data on a system desktop of the second device.

As an implementation manner of the second aspect, after the second device generates the icon of the second type of application in the backup data by using a system desktop of the second device, the method further includes:

the second equipment receives clicking operation of icons of the second type of applications displayed on the system desktop;

and responding to clicking operation of the icon of the second type application, sending second prompt information by the second device, wherein the second prompt information is used for prompting a user to network the second device so as to download an application version and an installation package of the second type application compatible with the second device from the first server after the second device is networked.

In the present application, since some new machines may not be initially connected to the wireless lan, in order to enable the second device to download a compatible version of the second type of application, an icon may be generated on the system desktop of the second device, and the icon may be used as a link, and after networking, the second device compatible version of the second type of application is downloaded from the server.

and the second device downloads an installation package of a second type of application compatible with the second device from the first server under the condition that the second device is detected to be networked.

In order to better improve user experience, an installation package of a second type application compatible with the second device and an application version can be automatically downloaded under the condition that the second device is connected with the network, and the installation package is installed, and after the installation package is installed, user data corresponding to the second type application in the backup data can be imported into the second type application.

If the backup data comprises the installation package of the second type application, the second device deletes the installation package of the second type application in the backup data;

and if the backup data comprises the installation package of the third-class application and the user data corresponding to the third-class application, deleting the installation package of the third-class application and the user data corresponding to the third-class application in the backup data by the second equipment.

According to the application, some information which is useless for the second device in the backup data can be deleted, so that the occupation of the storage space of the second device is avoided.

In a third aspect, there is provided an electronic device comprising a processor for executing a computer program stored in a memory, implementing the method of any one of the first aspects of the application.

In a fourth aspect, there is provided an electronic device comprising a processor for executing a computer program stored in a memory, implementing the method of any of the second aspects of the application.

In a fifth aspect, a data backup system is provided, including the electronic device of the third aspect and the electronic device of the fourth aspect.

In a sixth aspect, there is provided a system on a chip comprising a processor coupled to a memory, the processor executing a computer program stored in the memory to implement the method of any one of the first aspect and/or the method of any one of the second aspect of the application.

In a seventh aspect, there is provided a computer readable storage medium storing a computer program which when executed by one or more processors performs the method of any one of the first aspect and/or the method of any one of the second aspect of the application.

In an eighth aspect, embodiments of the present application provide a computer program product which, when run on a device, causes the device to perform the method of any one of the first aspect and/or the method of any one of the second aspect of the present application.

It will be appreciated that the advantages of the third to eighth aspects may be found in the relevant description of the first and second aspects, and are not described here again.

Drawings

Fig. 1 is a schematic hardware structure of an electronic device to which a data backup method according to an embodiment of the present application is applied;

FIG. 2 is a schematic flow chart of a data backup method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a device a in a data backup method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an interface of a first prompt message according to an embodiment of the present application;

fig. 5 is a schematic flow chart of the execution of the device B in the data backup method according to the embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that in embodiments of the present application, "one or more" means one, two, or more than two; "and/or", describes an association relationship of the association object, indicating that three relationships may exist; for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Furthermore, in the description of the present specification and the appended claims, the terms "first," "second," "third," "fourth," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

The data backup method provided by the embodiment of the application can be applied to the following electronic equipment. The electronic device may be a tablet computer, a cell phone, a wearable device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA), or the like. The embodiment of the application does not limit the specific type of the electronic equipment.

Fig. 1 shows a schematic structural diagram of an electronic device (which may be the first device in the subsequent embodiment or the second device in the subsequent embodiment). The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include, among other things, a pressure sensor 180A, a touch sensor 180K, an ambient light sensor 180L, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a coprocessor (sensor coprocessor, SCP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), or the like. Wherein the different processing units may be separate devices or may be integrated in one or more processors. For example, the processor 110 is configured to perform a data backup method in an embodiment of the present application.

The controller may be a neural hub and a command center of the electronic device 100, among others. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it may be called directly from memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and a peripheral device.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and is not meant to limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also employ different interfacing manners in the above embodiments, or a combination of multiple interfacing manners.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer-executable program code that includes instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store application programs (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system.

In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like.

In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio signals to analog audio signal outputs and also to convert analog audio inputs to digital audio signals. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to listening to voice information. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc. The earphone interface 170D is used to connect a wired earphone. The earphone interface 170D may be a USB interface 130 or a 3.5mm open electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A.

The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The embodiment of the present application is not particularly limited to a specific structure of an execution body of a data backup method, as long as communication can be performed with a data backup method provided according to the embodiment of the present application by running codes recorded with the data backup method of the embodiment of the present application. For example, the execution body of a data backup method provided in the embodiment of the present application may be a functional module in an electronic device that can call a program and execute the program, or a communication device, such as a chip, applied to the electronic device.

During use of an electronic device (e.g., device a), a user may replace the electronic device with another electronic device (e.g., device B) due to damage to the electronic device or the need for a user to update. As an example, the old cell phone used by the user is eliminated, the new cell phone will be replaced, or the old tablet computer used by the user is eliminated, the new tablet computer will be replaced.

When the old electronic equipment used by the user is replaced, a data backup technology can be adopted to backup the application and the user data in the old electronic equipment to the new electronic equipment.

It should be noted that, the embodiment of the present application does not limit the situations of the old electronic device and the new electronic device, where "new" and "old" do not indicate the degree of new and old of the electronic device itself, and "old electronic device" does not indicate that the electronic device is necessarily eliminated. An "old electronic device" is an electronic device where application and user data were originally located, and a "new electronic device" is an electronic device where application and user data are to be backed up.

As an example, the user uses the device a originally, and purchases the device B for use later, and the user needs to back up the application and the user data in the device a to the device B, so that in the backup process, the device a is an old electronic device, and the device B is a new electronic device. After the user uses the device B for a period of time, the user wants to replace the original device a, and needs to back up the application and the user data in the device B to the device a, so that in the backup process, the device B is an old electronic device, and the device a is a new electronic device.

At present, after an application and user data on an old electronic device are backed up to a new electronic device, when the application backed up on the new electronic device is used, a phenomenon of application crash or abnormal function often occurs.

This may be due to differences in the operating systems and/or hardware used, etc., of the old and new electronic devices, resulting in incompatibility of the applications in the old and new electronic devices backed up on the new electronic device.

In order to solve the problem, the embodiment of the application provides a data backup method, which is used for determining whether an application needing to be backed up to a new electronic device is compatible with the new electronic device or not by analyzing the compatibility of an application version of the application in the old electronic device and configuration information (such as system information and hardware information) of the new electronic device, and downloading another application version of the application which can be compatible from a server by the new electronic device under the condition that an incompatible application exists in the application needing to be backed up; of course, the user may also be prompted to back up the risk of some applications for which the new electronic device is incompatible.

Referring to fig. 2, a flow chart of a data backup method according to an embodiment of the present application is shown. Wherein, device A is the old electronic device and device B is the new electronic device. The data backup method comprises the following steps:

and step A1, the device A and the device B establish communication connection.

In the embodiment of the present application, the communication connection established between the device a and the device B may be a wired connection or a wireless connection, where the wireless connection may be a bluetooth connection, a WLAN connection, or the like. Of course, for convenience and to increase the data transmission speed, the communication connection may be a WIAN direct connection. The communication connection is for transmitting data between device a and device B.

As an example of establishing the wireless connection, the device a may send a connection request to the device B, and the device B may establish a communication connection with the device a after receiving the request, or the device B may send a connection request to the device a, and the device a may establish a communication connection with the device B after receiving the request.

Of course, in the current data backup process, the communication connection needs to be established between the device a and the device B, so the process of establishing the communication connection may refer to the process in the current data backup process, which is not limited in the embodiment of the present application.

In step A2, the device B transmits configuration information (e.g., system information and hardware information) of the device B to the device a.

In the embodiment of the application, after detecting that the communication connection between the device A and the device B is established, the device B sends the system information and the hardware information of the device B to the device A.

In practical application, after detecting that the communication connection between the device a and the device B is established, the device a may send a configuration information acquisition request to the device B, where the configuration information acquisition request is used to instruct the device B to send the system information and the hardware information of the device B to the device a.

The system information may be a version of an operating system currently adopted by the device B, and the hardware information may be a brand of the device B, a model of the device B, and the like, from which the hardware information of the device B (for example, a chip model adopted, a model of a camera, and the like) may be determined.

Steps A1 and A2 may be shown with reference to (a) in fig. 2.

And A3, after receiving the configuration information of the equipment B, the equipment A sends the version information of the application in the equipment A and the configuration information of the equipment B to a second server.

In the embodiment of the application, the device a may send the version information of all the applications in the device a to the second server, or may send the version information of the application to be backed up selected by the user to the second server.

If the equipment A sends the version information of the application to be backed up selected by the user to the second server, the equipment A needs to be executed after the user selects the application to be backed up;

if the device a transmits version information of all applications in the device a to the second server, it may be performed after receiving configuration information of the device B.

And A4, after receiving the version information of the application of the equipment A and the configuration information of the equipment B, the second server compares the version information of the application of the equipment A with the configuration information of the equipment B to obtain application compatibility information.

In the embodiment of the application, the application compatibility information comprises the following three types of application lists:

the first type of application list includes an identifier of an application (specifically, an application corresponding to a compatible application version) that can be directly compatible by the device B in the applications of the device a.

A second type of application list, which contains an identification of applications of the device a that are not compatible for system reasons (in particular applications corresponding to incompatible application versions), but which can be downloaded from the application market to another version of the application that is compatible with the device B.

And a third type of application list, wherein the list comprises identifications of applications (particularly applications corresponding to incompatible application versions) which cannot be compatible due to hardware reasons of the equipment B in the applications of the equipment A, namely that the hardware conditions of the equipment B cannot meet the normal operation of the applications in any version.

As an example, in a practical application, an application a.a (a version a of the application a), an application b.b (a version B of the application B), and an application C.c (a version C of the application C) are installed and run in the device a. Wherein, application a.a, application b.b and application C.c can all run normally on device a.

After comparing the configuration information of the three applications and the device B, the second server determines that the application a.a is compatible with the device B, that is, after the application a.a is backed up from the device a to the device B, theoretically, the application a.a can normally run on the device B, and in this case, the application a.a is a first type of application.

The second server determines that the systems of the application b.b and the device B are not compatible after comparing the configuration information of the three applications and the device B, that is, the application b.b may not operate normally on the device B after the application b.b is backed up from the device a to the device B. Often, an application developer will develop multiple versions that are compatible with different system versions for the same application, so if the second type of application is incompatible because of the system version, it will typically be possible to download the compatible application version from the application market. For example, there may be an application b.d (d version of application B) in the application marketplace that is compatible with the system version of device B. In this case, application b is a second type of application.

The second server determines that the hardware of the application C.c and the device B are not compatible after comparing the configuration information of the three applications and the device B, that is, the application C.c cannot normally run on the device B after the application C.c is backed up from the device a to the device B. Typically, the third type of application that is incompatible for hardware reasons is that device B cannot meet the hardware requirements of the application, in which case there is typically no version of the application that is compatible with device B. For example, normal use of application C requires a high refresh rate based on the display screen on the electronic device, however, the refresh rate of the display screen of device B cannot reach the refresh rate required by application C. In this case, device B cannot be downloaded to application C compatible with device B via the application market, and it is possible that none of the versions of application C are compatible with device B. I.e. device B cannot normally use application C, in which case application C.c is a third type of application.

The above examples represent one or more applications only in the form of a list, and in practical applications, the classification may not be performed in the form of a list. For example, a category identifier to which each application belongs is set for the identifier of the application.

And step A5, the second server sends the application compatibility information to the device A.

Steps A3 to A5 may be shown with reference to (b) in fig. 2.

Step A6, the device a transmits backup data and application compatibility information to the device B.

In the embodiment of the present application, the backup data sent by the device a to the device B includes the installation package of the application that needs to be backed up and related data (for example, corresponding user data in the application, file data in the memory of the device a, etc.) determined by the user.

Of course, device a may also send device B a list of applications that need to be backed up. The list may include application identifications and application versions that need to be backed up.

As an embodiment of the present application, the backup data sent by the device a to the device B includes an installation package of each type of application and corresponding user data (for example, chat records in the instant messaging application).

As an embodiment of the present application, the backup data sent by the device a to the device B includes an installation package of the first type of application and corresponding user data, and also user data of the second type of application.

The reason why the installation package of the second type of application is not included in the backup data is that: the subsequent device B needs to re-download the installation package of another application version compatible with the device B of the second type application from the first server, so that the problem that the device a transmits the installation package of the second type application in the device a to the device B to cause invalid transmission or waste of network resources can be avoided.

The reason why the backup data includes the user data corresponding to the second type of application is that: after the device B downloads the installation package of another application version compatible with the device B of the second type application from the first server and installs the installation package on the device B, the device may import the user data corresponding to the second type application into the second type application of another compatible version installed by the device B, so as to avoid loss of the user data.

The reason why the backup data does not include the installation package of the second type of application and the corresponding user data is that: since the third type application cannot be normally run in the device B, both the installation package and the user data of the third type application are useless data for the device B. The transmission procedure from device a to device B may cause problems of invalid transmission or waste of network resources.

And step A7, after the equipment B receives the backup data and the application compatibility information, the data is backed up in the equipment B based on the application compatibility information.

As an example, for a first type application in the first type application list, the device B may directly obtain an installation package of the first type application from the backup data to install the first type application, and after the installation, import user data corresponding to the first type application in the installed first type application.

For the second type application in the second type application list, the device B may download an installation package of another version of the second type application compatible with the device B from the first server (for example, connect the first server through an application market application installed by the device B) to install the second type application, and import user data corresponding to the second type application in the installed second type application of another version after the installation.

For the third-class application in the third-class application list, the hardware of the device B cannot install the third-class application, so that the installation package of the third-class application and the corresponding user data can be stored in a specific storage space for future backup from the device B to other devices possibly compatible with the third-class application, and of course, the installation package of the third-class application and the corresponding user data can also be deleted from the device B, which is not limited by the embodiment of the present application.

Of course, in the above embodiment, in the processing manner in the case where the backup data includes the installation packages of the various applications and the corresponding user data, in the actual application, the backup data does not necessarily include information such as the installation packages of the second type of application, the installation packages of the third type of application, and the like.

Step A6 and step A7 may be described with reference to (c) in fig. 2.

It should be noted that, when the data in the device a is backed up to the device B, the application compatibility information may include three types of application lists, or may include one type or two types of application lists, for example, in a case where all application versions of the applications in the device a are compatible with the device B, only the application list of the first type of applications may be included. Specifically, the application list containing several categories is related to compatibility of the application in the device a and the configuration of the device B, and is also related to backup data sent by the first device (for example, an installation package of the second type of application and the third type of application is not sent).

In addition, the communication connection between the device a and the device B requires transmission of configuration information of the device B transmitted from the device B to the device a, backup data transmitted from the device a to the device B, and the like.

The communication connection between the device a and the second server requires transmission of the application list (version information) in the device a and the configuration information of the device B, which the device a transmits to the second server, and the application compatibility information, which the second server transmits to the device a.

If the communication connection between the device a and the device B and the communication connection between the device a and the second server depend on the same communication module in the device a, and both communication connections cannot exist at the same time, the communication connection between the device a and the second server needs to be disconnected when communication is required between the device a and the device B. When communication is required between the device a and the second server, the communication connection between the device a and the device B needs to be disconnected. Therefore, the communication connection between the device a and the device B in (B) in fig. 2 is in a disconnected state.

The execution flow inside each of the device a and the device B will be described in detail below.

Referring to fig. 3, a schematic flow chart of an internal implementation of a device a in a data backup method according to an embodiment of the present application is shown.

From the perspective of device a:

s101, communication connection is established between the device A and the device B.

S102, the device A acquires configuration information of the device B.

S103, the device a transmits the application list of the device a (including version information of the application) and the configuration information of the device B to the second server.

And S104, the equipment A receives the application compatibility information sent by the second server.

Step S101 to step S104 may refer to the related descriptions in step A1 and step A4, and are not described herein.

S105, the device A sends out prompt information (which can be first prompt information).

In the embodiment of the application, the device a may display the prompt information through the display screen of the device a, where the prompt information may prompt the user that there is information (for example, an icon, a name of a third type of application) of an application that is incompatible with the device B due to the hardware of the device B in the application of the device a (or the application selected by the user).

Of course, in practical applications, the prompt information may also prompt the user that there is information (e.g., icons, names of applications of the second type) in the application of the device a (or the application selected by the user as backup) that the device B is not compatible with, but that other versions of the application (that are compatible with the device B) may be downloaded from the first server.

Of course, in practical applications, the prompt information may also prompt the user to have information (such as an icon and a name) of an application (or a backup application selected by the user) of the device a, which the device B may be compatible with.

As an example of the hint information, referring to fig. 4, an interface schematic diagram of the hint information sent for the device a includes an icon and a name of an application that cannot be compatible with the device B due to hardware of the device B, and an abnormality that may be caused if backup is continued.

The interface also includes a "continue" control and a "cancel" control, where the "continue" control is used to indicate that the user has knowledge of the risk of continuing the backup and continues the backup of the application presented in the prompt. The "cancel" control is used to indicate that the user has knowledge of the risk of continuing the backup and to cancel the backup of the application presented in the hint information.

It should be noted that the interface may be presented as a floating interface over other interfaces, and the content in the interface may also be displayed in a separate non-floating interface. The embodiment of the application does not limit the interface form.

And S106, the device A receives the authorization instruction and transmits an application list (containing version information), backup data and application compatibility information to the device B.

In the embodiment of the application, the authorization instruction can be an instruction for triggering the control to continue. The backup data may include an installation package of the application selected by the user for backup (an installation package of a version of the application a in the device a) and user data corresponding to the application (e.g., chat records in some instant chat applications, etc.), and may also include other user data selected by the user (e.g., files stored in a memory, etc.). The information sent by device a to device B also needs to include application compatibility information, and of course may also include a list of applications in the backup data transmitted by device a to device B.

In practical applications, the process of backing up application and user data in an old electronic device to a new electronic device includes a data transmission phase and a data recovery phase.

The data transmission stage is a process of migrating the application installation package and the user data from the old electronic device to the new electronic device. The data recovery phase is a process of migrating an application and user data into a new electronic device (e.g., installing the application and importing the user data of the application into the application).

As an example, in the data transfer phase, application installation packages and user data in the old electronic device may be transferred to the new electronic device in the form of data packages.

However, the application installation package and the different user data are stored differently on the new electronic device, and therefore, in the data recovery phase, these user data (e.g., pictures) need to be imported into the same storage space as the old electronic device. Still other user data are data of an application, and in the data recovery stage, some user data (e.g., chat logs, etc.) of the application need to be installed in a new electronic device and imported in the application based on an installation package of the application.

Referring to fig. 5, a schematic flow chart of an internal implementation of a device B in a data backup method according to an embodiment of the present application is shown.

From the perspective of device B:

s201, device B receives the information transmitted by device a.

S202, the device B determines whether there is application-compatible information in the information.

In practical applications, the information received by the device B and sent by the device a generally includes a list of applications to be backed up (including version information), an installation package, corresponding user data, and application compatibility information. The method for providing data backup according to the embodiment of the present application may be set in the device B, however, the method for providing data backup according to the embodiment of the present application may not be set in the device a, so that the information sent by the device a and received by the device B does not necessarily include application compatible information.

If the information sent by the device a and received by the device B includes application compatibility information, executing different steps according to different types of applications in the application compatibility information, and executing step S203 if the application compatibility information includes a first type of application list as an example; executing step S204 in the case that the second class of applications is contained in the application compatibility information; step S209 is performed in the case where the third type of application is included in the application compatibility information.

If the information sent by the device a and received by the device B does not include the application compatible information, step S301 is executed.

In the following, the information sent by the device a and received by the device B will be taken as an example.

S203, when the information sent by the equipment A and received by the equipment B contains the application compatibility information and the application compatibility information contains the first type application list, the equipment B acquires an installation package of the first type application from the backup data based on the application compatibility information, installs the first type application in the equipment B, and imports user data corresponding to the first type application.

In the embodiment of the application, aiming at the first type application compatible with the equipment B, the installation package of the first type application can be acquired from the backup data to be installed and the user data corresponding to the first type application can be imported.

Taking application a.a as an example of the first type of application, the system and hardware of application a.a and device a are compatible, i.e. application a.a may run normally on device a. Meanwhile, according to the version information of the application A.a and the configuration information of the equipment B, the system and hardware of the application A.a and the equipment B installed on the equipment A are determined to be compatible, namely, the application A.a can normally run on the equipment B in theory.

S204, in the case where the information sent by the device a and received by the device B includes application compatibility information and the application compatibility information includes the second class application list, the device B determines whether the device B is already networked.

In the embodiment of the present application, whether the device B is networked indicates whether the device B has been connected to the internet in any way.

S205, in the case where it is determined that networking has been performed, the device B downloads an installation package of an application version, for which the second type of application is compatible with the device B, from the first server.

In the embodiment of the application, even if the equipment B is a new machine, the equipment B usually contains the application market APP, so that the equipment B can be connected with a first server through the application market APP in the equipment B, and an installation package of an application version of which the second type of application is compatible with the equipment B is acquired from the first server.

Of course, the backup data received by the device B may also include an installation package of the second type of application, and the device B may delete the installation package of the second type of application in the backup data and an application version incompatible with the device B.

In addition, the information sent by the device a to the device B may only include the installation package of the first type of application, and the embodiment of the present application does not limit the type of the application installation package included in the information sent by the device a to the device B.

Taking application B as one example of the second type of application, application B installed in device a is application B. The systems and hardware of the application b.b and the device a are compatible, i.e. the application b.b can run normally on the device a. However, it is determined from the version information of the application b.b and the configuration information of the device B that the systems of the application b.b and the device B are not compatible, but the developer of the application B has a corresponding software version application b.d for the system development of the device B, so the version application b.d of the application B compatible with the device B can be downloaded in the application market in general, and theoretically, the application b.d can run normally on the device B.

And S206, the device B backups the application icons and the user data of the first type of application under the condition that the device B is not networked, and generates shortcut icons of the second type of application on a system desktop, wherein the shortcut icons are used for indicating the downloading of installation packages of application versions compatible with the second type of application and the device B from the first server.

S207, the device B downloads an installation package of an application version compatible with the device B of the second type application from the first server under the condition that networking is detected, or prompts a user to download the installation package of the application version compatible with the device B of the second type application in a networking mode under the condition that clicking of a shortcut icon of the second type application is detected.

And S208, after the device B downloads an installation package of the application version compatible with the device B of the second type of application, installing the second type of application in the device B, and importing user data of the second type of application.

In the embodiment of the present application, no matter step S205 or step S206 to step S207, the installation package of the application version compatible with the device B of the second type of application needs to be downloaded from the first server through the application market.

After device B obtains an installation package of an application version of the second type of application that is compatible with device B, the second type of application (and the version that device B is adapted to) may be installed and the corresponding user data imported in the second type of application.

As previously mentioned, applications that require backup may also include a third class of applications.

S209, in the case where the device B receives the information sent by the device a, the information includes application compatibility information, the application compatibility information includes a third type application list, and the backup data includes an installation package of the third type application and corresponding user data, the device B deletes the installation package of the third type application and the corresponding user data.

In the embodiment of the present application, the device a may not send the installation package of the third-class application and the corresponding user data in the application compatibility information acquired from the second server to the device B, so that when the backup data does not include the installation package of the third-class application and the corresponding user data, it is not necessary to execute deletion of the installation package and the corresponding user data for the third-class application.

Taking application C.c as one example of a third class of applications, application C.c is compatible with the system and hardware of device a, however, application C.c is not compatible with the hardware of device B, e.g., each version of application C is not compatible with the hardware of device B, so the installation package of application C in device B and the corresponding user data need to be deleted.

As another embodiment of the present application, after the device B determines in step S202 whether there is application compatible information in the received information sent by the device a, the method further includes:

in step S301, when the received device a transmission information does not include the application compatibility information, the device B transmits, to the second server, the application list to be backed up in the backup information and the configuration information of the device B.

In the embodiment of the present application, if the data backup method provided by the embodiment of the present application is set in the device B, and the data backup method provided by the embodiment of the present application is not set in the device a, no application compatible information exists in the information sent by the device a and received by the device B.

And the equipment B can send the related data to a second server so as to acquire the application version corresponding to the installation package in the backup data sent by the application A and the compatibility information of the equipment B.

In step S302, the device B receives the application compatibility information sent by the second server.

After the device B obtains the application-compatible information from the first server, the same action may be performed after determining that the application-compatible information exists in the obtained information transmitted by the device a from the device B. I.e. different steps may also be performed for different classes of applications for different classes of application lists.

As can be understood from the above examples, step S203 is performed for the first type of application; steps S204 to S208 are performed for the second type of application, and step S209 is performed for the third type of application.

In practical applications, the device B may execute, for each application in turn, a step corresponding to a category of the application based on the category corresponding to the application according to an order of the applications in the received application list.

The steps corresponding to each type of application may also be performed for such applications for applications in each type of application list.

The embodiment of the application does not limit the specific implementation mode.

As another embodiment of the present application, an embodiment of the present application provides a data backup method, applied to a first device, including:

the first equipment acquires configuration information of the second equipment;

In the present application, the first device is the device a in the above embodiment. The second device is device B in the above-described embodiment.

As another embodiment of the present application, the obtaining, by the first device, compatibility information of an application of the first device and the second device based on configuration information of the second device includes:

As another embodiment of the present application, after the first device obtains the compatibility information of the application of the first device and the second device, the method further includes:

As another embodiment of the present application, the configuration information includes system information (e.g., a system version) of the second device;

As another embodiment of the present application, the configuration information further includes: hardware information (e.g., vendor and model) of the second device;

In another embodiment of the present application, the first prompting information is further used to prompt a user that a third type of application incompatible with the second device exists in the applications to be backed up.

As another embodiment of the present application, the backup data does not include: an application installation package of a second type of application, an application installation package of a third type of application, and user data corresponding to the third type of application, wherein the application version of the second type of application is incompatible with a system of the second device;

As another embodiment of the present application, applied to a second device, the data backup method includes:

The second equipment receives first information sent by the first equipment;

As another embodiment of the present application, after the second device receives the first information sent by the first device, the method further includes:

As another embodiment of the present application, before the second device downloads the installation package of the application version and the second class of application compatible with the second device from the first server, the method further includes:

the second device determines that the second device has been networked.

As another embodiment of the present application, the method further includes:

As another embodiment of the present application, after the second device generates the icon of the second type of application in the backup data by using the system desktop of the second device, the method further includes:

and if the backup data comprises an installation package of a third type of application and user data corresponding to the third type of application, deleting the installation package of the third type of application and the user data corresponding to the third type of application in the backup data by the second device, wherein the third type of application is an application incompatible with the hardware of the second device in the backup data.

The application also provides a data backup system, which comprises the equipment A and the equipment B in the embodiment. The device a is used for executing the step in which the device a is the execution subject in the data backup method in the above embodiment, and the device B is used for executing the step in which the device a is the execution subject in the data backup method in the above embodiment.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.

The embodiments of the present application also provide a computer readable storage medium storing a computer program, which when executed by a processor, implements the steps of the above-described method embodiments.

Embodiments of the present application also provide a computer program product enabling a first device to carry out the steps of the method embodiments described above, when the computer program product is run on the first device.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above-described embodiments, and may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a first device, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

The embodiment of the application also provides a chip system, which comprises a processor, wherein the processor is coupled with the memory, and the processor executes a computer program stored in the memory to realize the steps of any method embodiment of the application. The chip system can be a single chip or a chip module composed of a plurality of chips.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the elements and method steps of the examples described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or as a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A method of data backup, comprising:

the first equipment acquires configuration information of the second equipment;

2. The method of claim 1, wherein the first device obtains compatibility information for the application of the first device and the second device based on configuration information of the second device, comprising:

3. The method of claim 1 or 2, wherein after the first device obtains the compatibility information of the application of the first device and the second device, further comprising:

4. The method of claim 3, wherein the configuration information comprises system information of the second device;

5. The method of claim 4, wherein the configuration information further comprises: hardware information of the second device;

6. The method of claim 5, wherein the first hint information is further used to hint a user that a third class of applications exist in the applications to be backed up that are incompatible with the second device.

7. The method of claim 5 or 6, wherein the backup data does not include: an application installation package of a second type of application, an application installation package of a third type of application, and user data corresponding to the third type of application, wherein the application version of the second type of application is incompatible with a system of the second device;

8. A method of data backup, comprising:

the second equipment receives first information sent by the first equipment;

9. The method of claim 8, wherein after the second device receives the first information sent by the first device, the method further comprises:

10. The method of claim 8 or 9, wherein before the second device downloads from the first server an installation package of an application version and a second class of applications that the second device is compatible with, the method further comprises:

the second device determines that the second device has been networked.

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

12. The method of claim 11, wherein the second device, after the system desktop of the second device generates the icon for the second type of application in the backup data, the method further comprises:

13. The method of claim 11, wherein the second device, after the system desktop of the second device generates the icon for the second type of application in the backup data, the method further comprises:

14. The method of claim 9, wherein after the second device receives the first information sent by the first device, the method further comprises:

15. An electronic device comprising a processor for executing a computer program stored in a memory to cause the electronic device to implement the method of any one of claims 1 to 7.

16. An electronic device comprising a processor for executing a computer program stored in a memory to cause the electronic device to implement the method of any one of claims 8 to 14.

17. A data backup system comprising an electronic device as claimed in claim 15 and an electronic device as claimed in claim 16.

18. A computer readable storage medium, characterized in that it stores a computer program which, when executed by one or more processors, implements the method of any one of claims 1 to 7, or any one of claims 8 to 14.