WO2022174718A1 - 一种数据备份方法和电子设备 - Google Patents

一种数据备份方法和电子设备 Download PDF

Info

Publication number
WO2022174718A1
WO2022174718A1 PCT/CN2022/073137 CN2022073137W WO2022174718A1 WO 2022174718 A1 WO2022174718 A1 WO 2022174718A1 CN 2022073137 W CN2022073137 W CN 2022073137W WO 2022174718 A1 WO2022174718 A1 WO 2022174718A1
Authority
WO
WIPO (PCT)
Prior art keywords
repair
authorization
data
proxy
electronic device
Prior art date
Application number
PCT/CN2022/073137
Other languages
English (en)
French (fr)
Inventor
王艳召
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022174718A1 publication Critical patent/WO2022174718A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • the present application relates to the computer field, and more particularly, to a data backup method and electronic device.
  • terminals such as mobile phones have become indispensable smart devices in people's daily life.
  • the device Once the device is abnormal and cannot be turned on, if the user has not completed the backup of the user data in advance, even if the system is repaired, the repaired system may be restored to the factory settings, which may cause all user data to be lost, resulting in serious user losses.
  • Embodiments of the present application provide a data backup method and electronic device, which reduce the probability of user data loss in a data partition in a restoration scenario, and reduce user losses.
  • an embodiment of the present application provides a data backup method, the method may include: a first device obtains a proxy repair authorization for a second device, and the proxy repair authorization is used for the first device to perform proxy repair on the second device , the second device is the device to be repaired and cannot be powered on; the first device backs up the user data in the data partition of the second device based on the proxy repair authorization; the first device completes the user data of the second device After the backup, perform proxy repair on the second device.
  • the first device first obtains the proxy repair authorization of the second device to be repaired, and based on the proxy repair authorization, the first device can back up the user data in the data partition of the second device in the proxy repair mode, and then Perform proxy repair on the second device. Therefore, the first device enters the proxy repair mode by obtaining the proxy repair authorization for the second device, and then completes the backup of the user data of the second device, which reduces the probability of user data loss during the repair process and reduces user losses.
  • the first device may obtain the proxy repair authorization of the second device to be repaired in the following manner, including: the first device obtains the proxy repair authorization of the second device to be repaired based on the trust relationship with the second device. .
  • the first device when the second device is in good condition, the first device can establish a trust relationship with the second device. After the trust relationship is established, the first device can obtain the authorization to repair the second device by proxy. Therefore, when the second device is damaged , the first device has obtained the proxy repair authorization for the second device, which can be used for the proxy repair of the second device.
  • the trust relationship between the first device and the second device may be established based on one of the following items: authorization information of the second device, power-on password of the second device, and associated accounts between the first device and the second device.
  • the first device and the second device establish a trust relationship through authorization information
  • the authorization information may be an authorization code generated by a user-defined password, or may be authorization information generated according to the hardware information of the device.
  • the first device may also establish a trust relationship with the second device through a power-on password.
  • the power-on password may be, for example, a face recognition password, a fingerprint recognition password, a digital password, or the like.
  • the first device may also establish a trust relationship through an account associated with the second device.
  • the first device and the second device may have associated accounts, or in other words, two devices with associated accounts.
  • the associated account for example, may be bound to the same account, or may be a main account and a sub-account, or the like.
  • the methods for establishing the trust relationship between the first device and the second device are simple and diverse, and are convenient for users to operate.
  • the first device may also obtain a proxy repair authorization for the second device to be repaired in the following manner: the first device applies to the server for a temporary proxy repair authorization for the second device.
  • the first device can also obtain a proxy repair authorization for the second device by applying for a temporary authorization to the server, so that the first device can Proxy repair for the second device.
  • the first device in response to the user's input operation, sends an access request for the data partition of the second device to the second device, where the access request carries an access password, and the access password is a password entered by the user and is used to access the first device.
  • the data partition of the second device is a password entered by the user and is used to access the first device.
  • the first device sends an access request for the data partition of the second device to the second device, thereby obtaining access rights to the data partition of the second device, which can be used by the first device to access the data partition of the second device. access.
  • the first device backs up the user data in the data partition of the second device, including the first device copying a data file from the data partition of the second device, where the data file contains user data.
  • the first device copies data files from the user partition of the second device, thereby completing the backup of user data, preventing user data loss during the restoration process, and reducing user losses.
  • the first device backs up the user data in the data partition of the second device, including: the first device copies a binary image of the data partition of the second device to back up the user data, and the binary image includes the second device.
  • the first device copies the binary image of the data partition of the second device for backup, so that even if the data file of the data partition is damaged, backup and recovery of user data can be completed by backing up the binary image.
  • performing proxy repair on the second device by the first device includes: the first device obtains an upgrade package; the first device sends the upgrade package to the second device; the first device triggers the second device to enter a repair mode, and the upgrade package Used for system repair in repair mode on the second device.
  • the first device obtains an upgrade package, which can be used for system repair of the second device, sends the upgrade package to the second device, and the first device triggers the second device to enter the repair mode, so that the second device completes the system repair, Reduced user losses.
  • performing proxy repair on the second device by the first device includes: the first device obtains an upgrade package, where the upgrade package is used for system repair of the second device; the first device parses the upgrade package to obtain a repair minimum system ; The first device mirrors the repaired minimum system to the second device; the first device triggers the second device to enter the proxy repair mode, and the repaired minimum system is used for the second device to perform system repair in the proxy repair mode.
  • the first device when the second device cannot enter the repair mode, in the proxy repair mode, the first device can complete the proxy repair of the second device, so that the second device can not enter the repair mode by itself.
  • the first device completes the system repair of the second device.
  • acquiring the upgrade package by the first device includes: the first device sending to the first server a proxy repair authorization application of the first device to the second device, and device information of the first device and device information of the second device, the The device information includes a version identifier and a device identifier to obtain an authorization file from the first server, the authorization file is used to instruct the first device to authorize the proxy repair of the second device; the first device, based on the authorization file and the device information, obtains an authorization file from the second server. Obtain the version file list, and the first device downloads the upgrade package from the third server based on the version file list.
  • the first device obtains the upgrade package from the third server based on the version file list, and this process reduces the risk that the downloaded upgrade package version does not match.
  • the first device downloads an authentication file from the second server based on the upgrade package, where the authentication file is used to authenticate the second device during system repair.
  • the first device obtains an authentication file from the second server based on the downloaded upgrade package, and the second server issues the authentication file to the first device.
  • the authentication file not only ensures the integrity of the upgrade package and the The correctness can be used for the authentication of the second device in the system repair, so as to carry out the system repair.
  • an embodiment of the present application provides a data backup method, including: a microcontroller unit (MCU) of a second device receives an access request from the first device, and the access request is used to request access to a The data partition, the access request carries the access password, the second device is the device to be repaired, and the second device cannot be turned on; the first device is the device used for proxy repair of the second device; the MCU of the second device The port between the application processors (AP) of the second device requests to read the password pre-stored in the security partition of the second device; the MCU of the second device verifies the access password based on the password in the security partition ; The MCU of the second device accepts the access request of the first device when the access password verification is successful.
  • MCU microcontroller unit
  • the MCU of the second device after the MCU of the second device receives the access request from the first device, it can read the password of the security partition of the second device through the port between the MCU and the AP, so as to verify the access request.
  • the second device can allow the first device to access, the first device obtains access rights, the port between the MCU and the AP realizes the communication connection between the two, and through the port, the MCU can access the AP security partition, so that the first device Gain access.
  • the present application provides a data backup apparatus, including a processor configured to execute the first aspect and the data backup method in any possible implementation manner of the first aspect.
  • the apparatus may also include a memory for storing instructions and data.
  • the memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the method described in the first aspect can be implemented.
  • the apparatus may also include a communication interface for the apparatus to communicate with other devices, for example, the communication interface may be a transceiver, circuit, bus, module or other type of communication interface.
  • the data backup device is an electronic device.
  • the data backup device is a chip or a chip system configured in an electronic device.
  • the present application provides a data backup device, including an application processor AP and a micro control unit MCU, where the MCU is configured to execute the data backup method described in the second aspect.
  • the data backup device is an electronic device.
  • the data backup device is a chip or a chip system configured in an electronic device.
  • the present application provides a data backup device for implementing the methods in the first to second aspects and any possible implementation manners of the first to second aspects.
  • the present application provides a computer-readable storage medium, comprising instructions that, when executed on a computer, enable the computer to implement the first to second aspects and any possible implementation manner of the first to second aspects.
  • the present application provides a computer program product, the computer program product comprising: a computer program (also referred to as code, or instructions) that, when the computer program is executed, causes a computer to execute the first aspect and The second aspect and the method in any possible implementation manner of the first to second aspects and the first to second aspects.
  • a computer program also referred to as code, or instructions
  • FIG. 1 is a schematic structural diagram of an electronic device applicable to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a specific structure of an electronic device applicable to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data backup method provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a communication connection of an electronic device of a data backup method provided by an embodiment of the present application
  • FIG. 5 is a schematic diagram of a communication connection of an electronic device of a data backup method provided by an embodiment of the present application
  • FIG. 6 is a schematic diagram of the connection of an electronic device provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a user operation provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a first device authorization check provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of backing up user data provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a first device application authorization file provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the first device acquiring an authentication file and downloading an upgrade package provided by an embodiment of the present application;
  • FIG. 12 is a schematic diagram of a second device data block device provided by an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of system repair provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a first device proxy repairing a second device according to an embodiment of the present application.
  • the methods provided in the embodiments of the present application can be applied to mobile phones, tablet computers, wearable devices, in-vehicle devices, augmented reality (AR)/virtual reality (VR) devices, netbooks, and personal digital assistants (personal digital assistants). , PDA), distributed equipment and other electronic equipment.
  • the embodiments of the present application do not limit any specific types of electronic devices.
  • the methods described in the embodiments of the present application can support an Android (Android) operating system (operating system, OS), a Harmony OS (Harmony OS), an Internet of Things operating system (such as a lightweight Internet of Things operating system (lite operating system) system, LiteOS)) and other operating environments.
  • Android Android
  • Harmony OS Harmony OS
  • Internet of Things operating system such as a lightweight Internet of Things operating system (lite operating system) system, LiteOS)
  • FIG. 1 shows a schematic structural diagram of an electronic device 100 .
  • the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, and a battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, key 190, motor 191, indicator 192, camera 193, a display screen 194, and a subscriber identification module (subscriber identification module, SIM) card interface 195 and the like.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.
  • the structures illustrated in this application do not constitute a specific limitation on the electronic device 100 .
  • the electronic device 100 may include more or fewer components than shown, or some components may be combined, or some components may be split, or a different arrangement 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, for example, the processor 110 may include an AP, an MCU, 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 (DSP), a baseband processor, and one or more of a neural-network processing unit (NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • the application processor outputs sound signals through the audio module 170 (such as the speaker 170A, etc.), or displays images or videos through the display screen 194 .
  • the controller may be the nerve center and command center of the electronic device 100 .
  • the controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.
  • the processor 110 can perform different operations by executing the instructions to achieve different functions.
  • the instruction may be an instruction pre-stored in the memory before the device leaves the factory, or may be an instruction read from the APP after the user installs a new application (application, APP) during use, which is not made in this embodiment of the present application. any restrictions.
  • the processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a secure digital input and output interface (secure digital input and output, SDIO), pulse code modulation (pulse code modulation) code modulation, PCM) interface, universal asynchronous receiver/transmitter (UART) interface, universal synchronous asynchronous receiver/transmitter (USART), mobile industry processor interface (mobile industry processor interface) , MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface and/or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • SDIO secure digital input and output interface
  • SDIO secure digital input and output interface
  • pulse code modulation pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous receiver/transmitter
  • the I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL).
  • the processor 110 may contain multiple sets of I2C buses.
  • the processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flash, the camera 193 and the like through different I2C bus interfaces.
  • the processor 110 may couple the touch sensor 180K through the I2C interface, so that the processor 110 and the touch sensor 180K communicate with each other through the I2C bus interface, so as to realize the touch function of the electronic device 100 .
  • the I2S interface can be used for audio communication.
  • the processor 110 may contain multiple sets of I2S buses.
  • the processor 110 may be coupled with the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 .
  • the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls through a Bluetooth headset.
  • the PCM interface can also be used for audio communications, sampling, quantizing and encoding analog signals.
  • the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.
  • the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.
  • the UART interface is a universal serial data bus used for asynchronous communication.
  • the bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication.
  • a UART interface is typically used to connect the processor 110 with the wireless communication module 160 .
  • the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function.
  • the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.
  • the MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 .
  • MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc.
  • the processor 110 communicates with the camera 193 through a CSI interface, so as to realize the photographing function of the electronic device 100 .
  • the processor 110 communicates with the display screen 194 through the DSI interface to implement the display function of the electronic device 100 .
  • the GPIO interface can be configured by software.
  • the GPIO interface can be configured as a control signal or as a data signal.
  • the GPIO interface may be used to connect the processor 110 with the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like.
  • the GPIO interface can also be configured as I2C interface, I2S interface, UART interface, MIPI interface, etc.
  • the USB interface 130 is an interface that conforms to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like.
  • the USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones.
  • the interface can also be used to connect other electronic devices, such as AR devices.
  • the interface connection relationship between the modules illustrated in this application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 .
  • the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • the charging management module 140 is used to receive charging input from the charger.
  • the charger may be a wireless charger or a wired charger.
  • the charging management module 140 may receive charging input from the wired charger through the USB interface 130 .
  • the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 charges the battery 142 , it can also supply power to the electronic device through the power management module 141 .
  • the power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 .
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, the wireless communication module 160, and the like.
  • the power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, battery health status (leakage, impedance).
  • the power management module 141 may also be provided in the processor 110 .
  • the power management module 141 and the charging management module 140 may also be provided 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, the modulation and demodulation processor, the baseband processor, and the like.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • the antenna 1 can be multiplexed as a diversity antenna of the 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 wireless communication solution including 2G/3G/4G/5G etc. applied on the electronic device 100.
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), and the like.
  • the mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then turn it into an electromagnetic wave for radiation through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .
  • the modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the low frequency baseband signal is processed by the baseband processor and passed to the application processor.
  • the application processor outputs sound signals through audio devices (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or videos through the display screen 194 .
  • the modem processor may be a stand-alone device.
  • the modem processor may be independent of the processor 110, and may be provided in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN), such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite Wireless communication solutions such as global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared technology (IR).
  • WLAN wireless local area networks
  • BT wireless fidelity
  • BT Bluetooth
  • GNSS global navigation satellite System
  • FM frequency modulation
  • NFC near field communication
  • IR infrared technology
  • the wireless communication module 160 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110 , perform frequency modulation on it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2 .
  • the antenna 1 of the electronic device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), fifth generation (5th generation, 5G) communication system, BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • CDMA code division multiple access
  • WCDMA broadband Code division multiple access
  • WCDMA wideband code division multiple access
  • time division code division multiple access time-division code division multiple access
  • TD-SCDMA time-division code division multiple access
  • LTE
  • the GNSS may include global positioning system (global positioning system, GPS), GNSS, BeiDou navigation satellite system (BeiDou navigation satellite system, BDS), quasi-zenith satellite system (quasi-zenith satellite system, QZSS) and/or satellite. based augmentation systems (satellite based augmentation systems, SBAS).
  • global positioning system global positioning system, GPS
  • GNSS BeiDou navigation satellite system
  • BDS BeiDou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the electronic device 100 may implement a display function 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 screen 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 alter display information.
  • the display screen 194 is used to display images, videos, and the like.
  • Display screen 194 includes a display panel.
  • the display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode, or an active matrix organic light emitting diode (active-matrix organic light).
  • electronic device 100 may include one or more display screens 194 .
  • the electronic device 100 may implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.
  • the ISP is used to process the data fed back by the camera 193 .
  • the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye.
  • ISP can also perform algorithm optimization on image noise, brightness, and skin tone.
  • ISP can also optimize the exposure, color temperature and other parameters of the shooting scene.
  • the ISP may be provided in the camera 193 .
  • Camera 193 is used to capture still images or video.
  • the object is projected through the lens to generate an optical image onto the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal.
  • the ISP outputs the digital image signal to the DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other formats of image signals.
  • the electronic device 100 may include one or more cameras 193 .
  • a digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy and so on.
  • Video codecs are used to compress or decompress digital video.
  • the electronic device 100 may support one or more video codecs.
  • the electronic device 100 can play or record videos in various encoding formats, such as: Moving Picture Experts Group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.
  • MPEG Moving Picture Experts Group
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100 .
  • the external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example to save files like music, video etc in external memory card.
  • Internal memory 121 may be used to store computer executable program code, which includes instructions.
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by executing the 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 can store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like.
  • the storage data area may store data (such as audio data, phone book, etc.) created during the use of the electronic device 100 and the like.
  • the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.
  • the electronic device 100 may implement audio functions through an audio module 170, such as a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor. Such as music playback, recording, etc.
  • an audio module 170 such as a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor.
  • the audio module 170 is used for converting digital audio information into analog audio signal output, and also for converting analog audio input into digital audio signal. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .
  • Speaker 170A also referred to as a "speaker" is used to convert audio electrical signals into sound signals.
  • the electronic device 100 can listen to music through the speaker 170A, or listen to a hands-free call.
  • the receiver 170B also referred to as "earpiece" is used to convert audio electrical signals into sound signals.
  • the voice can be answered by placing the receiver 170B close to the human ear.
  • the microphone 170C also called “microphone” or “microphone” is used to convert sound signals into electrical signals.
  • the user can make a sound by approaching the microphone 170C through a human mouth, and input the sound signal into 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, which can implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.
  • the earphone jack 170D is used to connect wired earphones.
  • the earphone interface 170D may be the USB interface 130, or may be a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.
  • OMTP open mobile terminal platform
  • CTIA cellular telecommunications industry association of the USA
  • the keys 190 include a power key (or a power key), a volume key, and the like.
  • the key 190 may be a mechanical key or a touch key.
  • the electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 .
  • the user can implement the functions of screen sleep and screen wakeup by pressing or touching the power-on key 190 .
  • Motor 191 can generate vibrating cues.
  • the motor 191 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback.
  • touch operations acting on different applications can correspond to different vibration feedback effects.
  • the motor 191 can also correspond to different vibration feedback effects for touch operations on different areas of the display screen 194 .
  • Different application scenarios for example: time reminder, receiving information, alarm clock, games, etc.
  • the touch vibration feedback effect can also support customization.
  • the indicator 192 can be an indicator light, which can be used to indicate the charging state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.
  • the SIM card interface 195 is used to connect a SIM card.
  • the SIM card can be contacted and separated from the electronic device 100 by inserting into the SIM card interface 195 or pulling out from the SIM card interface 195 .
  • the electronic device 100 may support one or more SIM card interfaces.
  • the SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card and so on. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different.
  • the SIM card interface 195 can also be compatible with different types of SIM cards.
  • the SIM card interface 195 is also compatible with external memory cards.
  • the electronic device 100 interacts with the network through the SIM card to implement functions such as call and data communication.
  • the electronic device 100 employs an eSIM, ie: 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 structures illustrated in this application do not constitute a specific limitation on the electronic device 100 .
  • the electronic device 100 may include more or fewer components than shown, or some components may be combined, or some components may be split, or a different arrangement of components.
  • the illustrated components may be implemented in hardware, software, or a combination of software and hardware.
  • the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture or a cloud architecture.
  • the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100 as an example.
  • this application does not limit the type of the operating system of the electronic device. For example, Android system, Hongmeng OS, etc.
  • the electronic device 200 may include an MCU, an AP, a main memory, a slave memory, a first port, a second port, a controller, a wireless communication module, such as a wireless fidelity (WIFI) module or Bluetooth module, and other peripheral modules.
  • the MCU and AP can realize the wired connection with the outside through the first port, and can also realize the wireless connection with the outside through the wireless communication module.
  • the MCU can realize the data communication with the AP through SDIO, GPIO, I2S or USART and other interfaces. and MCU can access main memory.
  • the MCU can be used as a slave processor, responsible for security verification, port management and main memory management in abnormal scenarios.
  • the MCU has the permission to read only the AP security partition.
  • the read-only AP security partition can be understood as follows: the security partition can be an area located in the main memory and can be used to store data that needs to be kept secret, such as power-on password, unlocking fingerprint data, unlocking face data, etc.
  • the security partition can usually be controlled by the AP.
  • the AP For example, when an application applies to use the data in the security partition, it can be controlled by the AP to read and write.
  • the read and write process requires the system to encrypt and decrypt.
  • the MCU has the right to read only the AP security partition, which may mean that the MCU can implement read-only access to the security partition through the AP.
  • descriptions of the same or similar situations are omitted for brevity.
  • the main memory can be used to store programs and data, and the MCU can be authorized to access the main memory, but only in the block device mode to obtain the remaining space of the user partition, and to read and write the remaining space at the tail of the block device.
  • a controller is further provided between the main memory and the MCU.
  • the controller can also be integrated in the MCU.
  • the slave memory can be used to store secure backup information such as AP dynamic encryption keys.
  • the first port is a shared port of the MCU and the AP, and the MCU and the AP communicate with the outside through the first port.
  • the second port is the communication port of the MCU and the AP, and is used to realize the communication connection between the two.
  • FIG. 2 can be applied to any electronic device of the first device and the second device described below. This embodiment of the present application does not limit this.
  • the AP can read data from main memory.
  • the main memory may include a system (system) partition, a boot (boot) partition, a recovery (recovery) partition, a data (data) partition, a miscellaneous (miscellaneous, misc) partition, and the like.
  • system system
  • boot boot
  • recovery recovery
  • data data
  • miscellaneous miscellaneous, misc
  • embodiments of the present application provide a data backup method.
  • the first device establishes a communication connection with the second device, and after the communication connection is established, the first device obtains a proxy repair authorization for the second device, and the proxy repair authorization is used for the first device to proxy the second device Repair, based on the proxy repair authorization, the first device backs up the user data in the data partition of the second device, and after the backup is completed, the first device starts the proxy repair of the second device, thereby completing the data partition of the second device Rescue backup of user data in .
  • the first device intact electronic devices, such as mobile phones, tablets, etc.
  • the first device may be configured to perform proxy repair on the second device in a proxy repair mode.
  • the second device an electronic device that cannot be turned on, or a bricked electronic device.
  • a bricked electronic device For example, mobile phones, tablets, etc.
  • the first port the shared port of MCU and AP.
  • the MCU and the AP in the same electronic device may share a first port, and one of the MCU and the AP may use the first port to communicate with an external device.
  • the first port needs to be triggered by a specific command when the AP is switched to be used by the MCU, or when the MCU is switched to be used by the AP.
  • this port can only be used for the connection between devices and devices (device2device, D2D), such as mobile phones, PCs, tablet computers and other electronic devices the connection between. And in non-R&D debugging scenarios, the command debugging window will not be opened.
  • the second port a port in a logical sense, used to realize the communication connection between the MCU and the AP.
  • the second port has the ability to force loading and debugging interaction.
  • the MCU can access the security partition of the AP through the second port.
  • Upgrade package In some operating systems, such as the Android system, the upgrade package can be used for system upgrade or repair.
  • the upgrade package is downloaded from a server, such as from an over the air technology (OTA) server.
  • OTA over the air technology
  • the terminal device When the terminal device needs to upgrade or repair the system, it can first enter the recovery mode, and then use the upgrade package to upgrade or repair the system.
  • an upgrade package may also be referred to as a repair package, a repair upgrade package, or the like. This application does not limit its naming.
  • FIG. 3 is a schematic flowchart of a data backup method provided by an embodiment of the present application. It should be understood that the method 300 shown in FIG. 3 can be performed under the condition that the first device and the second device establish a communication connection.
  • a possible situation is that when the AP of the second device can be identified with the external connection through the first port and can carry out normal data communication, or in other words, when the second device can carry out normal data communication, it can enter the fast startup ( fastboot) mode, but cannot enter repair mode.
  • the AP of the first device can be connected to the AP of the second device to implement the communication connection between the first device and the second device.
  • the AP of the first device may be connected to the port #2 of the second device (ie, the first port of the second device) through port #1 (ie, the first port of the first device), and further Communicate with the AP of the second device.
  • the AP of the first device can be connected to the MCU of the second device to implement the communication connection between the first device and the second device.
  • the fact that the first port on the AP side does not respond may specifically mean that the system partition supporting the operation of the AP side is damaged, the system on the AP side cannot operate normally, and cannot support functions such as normal monitoring and data transmission on the first port.
  • the AP of the first device may be connected to the port #2 of the second device (ie, the first port of the second device) through port #1 (ie, the first port of the first device), and further Communicate with the MCU of the second device. Communication between the MCU of the second device and the AP is through port #3 (ie, the second port of the second device).
  • the method 300 shown in FIG. 3 may include S301 to S306, and each step in FIG. 3 will be described in detail below. It should be understood that the actions performed by the first device in the flow shown in FIG. 3 may be performed, for example, by an AP in the first device.
  • the first device and the second device shown in FIG. 3 may satisfy at least one of the following: the first device and the second device are devices of the same brand, and the first device and the second device have the same operating system, such as the Android system , or Hongmeng system, etc.; and the first device and the second device are the same type of devices, such as mobile phones, tablet computers, etc.
  • the first device obtains a proxy repair authorization for the second device.
  • the first device may obtain access rights to the second device, so as to access the second device and perform proxy repair on the second device.
  • a possible situation is that the first device has obtained the proxy repair authorization when the second device is in good condition.
  • the second device when the second device is in good condition, it is connected to the first device and establishes a trust relationship with the first device.
  • the manner in which the second device is connected to the first device when it is intact may be a wireless connection or a wired connection.
  • the second device can be connected to the first device through a wireless connection such as WIFI and Bluetooth, or can be connected to the first device through a wired connection. This embodiment of the present application does not limit this.
  • FIG. 6 a) in FIG. 6 is a schematic diagram of a first device and a second device connected by a wireless connection.
  • the first device and the second device can respectively turn on the wireless communication module to realize the communication connection.
  • the first device and the second device establish a communication connection through a WIFI module.
  • the second device turns on the WIFI hotspot, and the first device is connected to the WIFI signal of the second device, so that the communication connection between the first device and the second device can be realized.
  • the first device and the second device can also turn on the Bluetooth modules respectively, and realize the communication connection by means of Bluetooth pairing.
  • FIG. 6 b) in FIG. 6 is a schematic diagram of the first device and the second device connected by a wired connection.
  • a communication connection is established between the first port of the second device and the first port of the first device through a wired connection.
  • the AP of the second device shown in b) in FIG. 6 cannot be connected to the external device through the first port.
  • the second device can be connected to the MCU of the first device through the first port, and the MCU can be connected to the MCU through the first port. Connect to the AP of the first device, thereby establishing a communication connection between the first device and the second device.
  • the connection relationship shown in b) in FIG. 6 is similar to the connection relationship shown in FIG. 5 , and details are not repeated here for brevity.
  • the first device and the second device can also realize the communication connection through the connection method described in FIG. 4 . .
  • the first device and the second device may establish a trust relationship after completing the connection.
  • the first device and the second device can respectively establish a trust relationship through "device mutual assistance".
  • the first device obtaining the proxy repair authorization from the second device as an example. It can be understood that, based on the same method described below, the second device can also obtain the proxy repair authorization of the first device.
  • the method of "device mutual assistance” may include, but is not limited to, the following:
  • Method 1 Establish a trust relationship through authorization information.
  • the authorization information may be, for example, an authorization code generated by a user-defined password, or may be authorization information generated according to hardware information of the device. This embodiment of the present application does not limit this.
  • the authorization code of the first device and the authorization code of the second device generated by the user-defined password can be stored in the slave memory of the first device and the slave memory of the second device in advance, respectively. After the first device shakes hands with the second device The authorization codes of the two devices can be matched, and if the match is successful, the authorization will be automatically performed.
  • the first device may shake hands with the second device based on hardware information such as a serial number (series number, SN) of the second device, and the first device may automatically authorize after shaking hands with the second device.
  • hardware information such as a serial number (series number, SN) of the second device
  • SN serial number
  • the hardware information may also be other information that can be used to uniquely identify a device.
  • the embodiments of the present application include but are not limited to this.
  • the MCU of the second device can read the serial number of the second device, and based on the connection relationship between the first device and the second device, the second device can send the serial number to the first device through the first port.
  • the second method is to establish a trust relationship through the power-on password.
  • the power-on password may be, for example, a face, a fingerprint, a digital password, or the like.
  • the user may input the power-on password of the second device to obtain authorization.
  • Method 3 Establish a trust relationship by associating accounts.
  • the first device and the second device may have associated accounts, or in other words, two devices with associated accounts.
  • the associated account for example, may be bound to the same account, or may be a main account and a sub-account, or the like.
  • the account here, for example, may be a device account, or a mobile phone number, and the like. This application is not limited to this.
  • the first device and the second device may be two devices with the same account; for another example, the account of the first device is the main account, and the account of the second device is a sub-account; for example, the account of the first device is a sub-account , the account of the second device is the primary account, and so on. For brevity, they are not listed here.
  • the first device can check whether it has an associated account with the second device, and if so, the second device can obtain authorization.
  • the first device obtains a proxy repair authorization when the second device is damaged.
  • the first device may apply to a server (eg, an authorization server) for a temporary proxy repair authorization for the second device.
  • a server eg, an authorization server
  • the first device may provide the authorization server with authentication information of the first device and the second device, etc., to request the authorization server to evaluate whether to grant the first device a temporary proxy repair authority to the second device.
  • the identity verification information may be, for example, information used for public key cryptography (public key infrastructure, PKI) verification, for example, including but not limited to, a public key, a digital certificate, a digital signature, and the like.
  • a possible implementation manner is that after the first device is connected to the second device, the first port of the first device (port #1 in FIG. 4 or FIG. 5 ) can detect the second device. Based on this, the first device may display a button of "authorization check" through a user interface (user interface, UI), as shown in FIG. 7 . The user can click this button to trigger the first device to perform authorization check. In response to the user's operation, the first device enters an authorization check.
  • UI user interface
  • FIG. 8 shows the specific process of the authorization check performed by the first device.
  • the first device may first determine whether a trust relationship has been established with the second device. If the second device has established a trust relationship with the first device, the authorization check can be passed, and the first device can obtain the proxy repair authorization for the second device. If the second device does not establish a trust relationship with the first device, the first device can establish a trust relationship with the second device by executing the method in the above "device mutual assistance", such as inputting the authorization information of the second device and inputting the second device.
  • the authorization check can be passed, and the first device can obtain the authorization to repair the agent of the second device; if the verification fails, the authorization check also fails, and the first device can Apply to the authorization server for a temporary proxy repair authorization. It can be understood that the establishment of a trust relationship by the first device with the second device through "device mutual assistance" needs to be performed when the second device can be powered on normally. If the second device fails to boot normally, it means that the verification fails and the authorization check fails, and the first device can directly apply to the authorization server for a temporary proxy repair authorization. If the server allows temporary authorization, the first device obtains proxy repair authorization for the second device.
  • the first device backs up the user data in the data partition of the second device based on the proxy repair authorization.
  • the second device may be decrypted in proxy repair mode to access the data partition of the second device.
  • the first device can obtain the access authority to the data partition of the second device, and then back up the user data for the data partition of the second device.
  • the access authority of the data partition of the second device may also be obtained by means of password verification.
  • the first device may prompt the user through the user interface to input a password for decrypting the data partition of the second device.
  • the password entered by the user may be sent to the second device through the connection relationship between the first device and the second device (see the connection relationship shown in FIG. 4 or FIG. 5 above).
  • the AP of the second device verifies the entered password; in the connection mode shown in FIG. 5 , the MCU of the second device can read the AP of the second device.
  • Security partition to verify the password entered by the user.
  • the first device can obtain the access right to the data partition of the second device; if the verification fails, the first device cannot obtain the access right to the data partition of the second device. Further, the first device may also prompt the user to input personal verification information through the user interface for verification of the second device.
  • the personal verification information may include, for example, a device personal password or a personal account number.
  • the first device in response to a user's input operation, sends an access request for the data partition of the second device to the second device, and the MCU of the second device receives the access request from the first device and communicates with the AP of the second device.
  • the second port between the two ports requests to read the password pre-stored in the security partition of the second device.
  • the MCU verifies the access password. If the verification is successful, the access request of the first device is accepted.
  • the access request sent by the first device to the second device carries an access password, where the access password is a password input by the user and is used to access the data partition of the second device.
  • the access password and the power-on password in establishing the trust relationship may be the same password or different passwords, which are not limited in this embodiment of the present application. If the passwords are the same, the power-on password can be entered in establishing the trust relationship to obtain access rights to the data partition of the second device, and the password can also be verified before backup, which is not limited in this embodiment of the present application.
  • the backup of the user data in the data partition of the second device by the first device can be implemented in the following two possible implementation manners:
  • a first possible implementation manner is that the first device may copy the data files from the data partition of the second device.
  • the data files described here may be, for example, pictures, music, videos, and other data files that are visible to the user. It should be understood that the file system may organize associated user data into files, and thus, the data file may include user data, or in other words, the data file is a form in which user data is presented to the user.
  • the second possible implementation manner is that the first device may copy the binary image of the data partition of the second device.
  • the binary image described here may refer to the binary image of the data partition of the second device, and the binary image not only includes data files visible to users, but also includes system files invisible to users. That is, the copy of the binary image of the data partition of the second device is a copy of the complete original binary data of the data partition of the second device.
  • the complete original binary data of the data partition here may specifically refer to a whole block of continuously stored binary data of the data partition.
  • the process in which the first device copies the binary image of the data partition of the second device to the local that is, stores an identical copy of the data partition of the second device in the storage area of the first device.
  • FIG. 9 is a schematic diagram of backing up user data according to an embodiment of the present application. It should be understood that, in FIG. 9 , for the convenience of distinction, the data in each partition in the first device is marked with A, and the data in each partition in the second device is marked with B.
  • the MCU of the second device may activate the data partition of the second device after completing the verification, and mount the data partition to the first device in a manner of an external storage device.
  • mounting the data partition to the first device in the form of an external storage device may mean that the data partition is connected to a folder of Linux, so as to associate the data partition with the directory, and the user only needs to access the This folder is equivalent to accessing the data partition.
  • the data partition of the second device is like a part of the first device. Thereby, the first device can access the data partition of the second device.
  • the user can copy the data files of the data partition of the second device to the first device by operating the first device to complete the backup of the user data of the second device.
  • This example may correspond to the first possible implementation of the user data backup described above.
  • the first device may read the data partition of the first device, copy the binary image of the data partition of the second device to the first device, and complete the verification to the user of the second device. backup of data. As shown in FIG. 9, the binary image of the data partition of the second device is copied into the storage area of the first device. This example may correspond to the second possible implementation of the user data backup described above.
  • the binary image is different from the file backup.
  • the binary image backup does not need to mount the data partition of the second device to the first device.
  • the binary image is a complete backup of the data partition of the second device.
  • the binary image of the data partition is copied to the first device, and the file system needs to process the binary image to form a file visible to the user. Therefore, even if the data partition of the second device is damaged, or in other words, the files of the data partition of the second device are missing, the user data can be backed up by means of binary mirroring. However, it is understandable that in the case of damaged data partitions, some user data may be lost, and these lost data may not be backed up.
  • the first device obtains an upgrade package, where the upgrade package is used to perform proxy repair on the second device.
  • the first device After the first device completes the user data backup of the second device, it may obtain an upgrade package from the server, and complete the proxy repair for the second device based on the upgrade package.
  • the first device acquiring the upgrade package may specifically include: the first device acquiring an authorization file, the first device acquiring a version file list (filelist), and the first device downloading the upgrade package and the authentication file.
  • the authorization file obtained by the first device is an authorization file used to perform proxy repair on the second device, and the authorization file can be used for subsequent acquisition of a version file list.
  • the version file list can be used to determine the version of the upgrade package that needs to be downloaded.
  • the upgrade package can be used to perform system repair on the second device.
  • the authentication file can be used for authentication in the repair process of the second device.
  • FIG. 10 is a schematic diagram of a first device application authorization file provided by an embodiment of the present application.
  • the first device may apply to an authorization server (ie, an example of the first server) for an authorization file.
  • the authorization server can be provided, for example, by a device manufacturer.
  • the first device can send an authorization server for the proxy repair authorization of the first device to the second device, as well as the device information of the first device and the data of the second device.
  • Device information so that the authorization server can conduct filing audit.
  • the device information may include, but is not limited to, a version identifier, a device identifier, and the like, for example.
  • the version identifier can be used to indicate the version of the device
  • the device identifier can be used to identify the device, for example, it can include but not limited to the serial number of the device.
  • the authorization server can perform public key cryptography (PKI) verification on the device information, and verify the validity of the proxy repair authorization application.
  • PKI public key cryptography
  • the authorization server can issue the authorization file to the first device after the verification is passed.
  • the authorization file is unique and may include device information of the first device and device information of the second device. Moreover, the authorization file is directional and is only used for the proxy repair of the second device by the first device.
  • FIG. 11 is a schematic diagram of a first device acquiring an authentication file and downloading an upgrade package provided by an embodiment of the present application.
  • the first device may obtain the authentication file from the package search server (ie, an example of the second server), and download the upgrade package from the OTA server (ie, an example of the third server).
  • the package search server and the OTA server are, for example, Can be provided by the equipment manufacturer.
  • the first device obtains the version file list from the package search server based on the authorization file and the device information of the second device. Specifically, the first device obtains the authorization file, that is, the first device obtains the proxy repair authorization for the second device. The first device can repair the authorization based on the proxy. The first device reads the device information of the second device, constructs a request message (for the convenience of distinction and description, for example, denoted as the first request message) and sends it to the packet search server, as shown in Figure 11. 1 shown.
  • a request message for the convenience of distinction and description, for example, denoted as the first request message
  • the first request message includes device information of the second device. Further optionally, the first request message further includes an authorization file obtained by the first device.
  • the device information of the second device may include, but is not limited to, a version identifier and a device identifier.
  • the package search server After receiving the first request message, the package search server verifies the device information of the second device, and finds that there is a version that can be upgraded by the second device after the verification, and the package search server can issue the version file list to the first device.
  • a device as shown in 2 in Figure 11.
  • the version file list records the OTA server address and the version information of the upgrade package, such as the package name, size, version number and other information of the upgrade package.
  • the first device can find the OTA server according to the OTA server address, and according to the upgrade package version information in the version file list, which can be, for example, a version identifier (version identifier, ID), construct a request message (for the convenience of distinction and description, for example, denoted as the first 2 request message), and send it to the OTA server, as shown in 3 in Figure 11.
  • the OTA server can deliver the corresponding upgrade package to the first device based on the second request message, as shown in 4 in FIG. 11 .
  • the first device may also send a request message (for example, a third request message) to the packet search server based on the upgrade package to request the packet search server to issue the authentication file of the second device.
  • the first device obtains an upgrade package for proxy repair of the second device.
  • the upgrade package downloaded by the first device from the OTA server may be one or more upgrade packages. This application does not limit the number of upgrade packages downloaded by the first device from the OTA server. Exemplarily, if the version file list received by the first device from the package search server includes multiple (such as three) version identifiers of upgrade packages, the first device can construct a Request message to download the corresponding upgrade package from the OTA server.
  • the authorization server, packet search server and OTA server used in the above process may be multiple independent physical devices, or may be integrated in one physical device, which is not limited in this application. It can be understood that the authorization server, the packet search server and the OTA server are only divided based on different functions, and should not constitute any limitation on the specific form of the device.
  • the name of each server is only an example, and should not constitute any limitation to this application. This application does not limit the specific name of each server.
  • an OTA server may also be referred to as a download server.
  • the method for the first device to obtain the upgrade package is not limited to the above.
  • the first device may submit the device information of the first device and the device information of the second device to the server, and the server sends the authentication file and the upgrade package matching the version of the second device according to the device information of the second device.
  • the first device can obtain an upgrade package for repairing the second device.
  • the upgrade package can be saved to facilitate subsequent proxy repair of the second device.
  • the first device may store the upgrade package locally in the first device or in the second device, which is not limited in this embodiment of the present application.
  • a possible situation is that the first device can access the data block device of the second device.
  • the first device may directly store the upgrade package in the data block device of the second device, for example, at the end of the data block device of the second device.
  • FIG. 12 is a schematic diagram of a second device data block device provided by an embodiment of the present application. As shown in FIG. 12 , the upgrade package and the authentication file can be stored in the tail of the data block device of the second device in binary form.
  • the first device may store the upgrade package in the storage device of the first device in a file format. For example, stored in the main memory of the first device.
  • the damage of the data partition of the second device is determined according to the header data of the data partition. Therefore, when the first device can access the data block device of the second device, even if the data partition of the second device is damaged, Placing the upgrade package at the end of the data block device can still ensure the storage of the upgrade package.
  • the first device performs proxy repair on the second device.
  • the first device may use the upgrade package obtained above to perform proxy repair on the second device. It should be noted that the proxy repair of the second device by the first device may be performed when the second device can enter the repair mode by itself, or may be performed when the second device cannot enter the repair mode by itself. This embodiment of the present application does not limit this.
  • the second device regardless of whether the second device can enter the repair mode by itself, the second device is in a state where it cannot be powered on normally.
  • the second device can enter repair mode on its own.
  • the system image of the second device is in a damaged state and needs to enter a repair mode to perform system repair.
  • the first device may trigger the second device to enter the repair mode in the proxy repair mode to perform system repair.
  • the first device may display a button of "agent repair" to the user through the user interface, and the user may click the agent repair button on the first device to trigger the second device to enter the repair mode.
  • the first device After the first device enters the proxy repair mode in response to the user operation, it can send an instruction to enter the repair mode to the second device through the connection relationship with the second device.
  • the second device enters a system repair mode based on the instruction.
  • FIG. 13 is a schematic flowchart of system repair provided by an embodiment of the present application.
  • the second device in response to the triggering of the first device, the second device starts to upgrade.
  • the second device parses the upgrade command.
  • the AP of the second device in response to the triggering of the first device, such as the above-mentioned instruction to enter the repair mode sent by the first device, can write an upgrade command to the misc partition, the second device restarts, and can start from the misc partition.
  • the partition reads and parses the upgrade command, entering repair mode.
  • the first device can send an instruction to the AP of the second device to make the AP of the second device directly enter the repair mode;
  • the first device can send an upgrade command to the MCU of the second device, and the LiteOS in the MCU can trigger the AP to enter the repair mode.
  • the second device After the parsing is completed, the second device starts authentication.
  • the second device may perform authentication based on a pre-acquired authentication file. If the authentication fails, the upgrade fails, and the second device cannot complete the repair; if the authentication passes, the upgrade package signature verification begins.
  • the signature verification of the upgrade package may include verification of the correctness and integrity of the upgrade package. check. If both the correctness check and the integrity check of the upgrade package pass, the signature verification is successful; if either the correctness check or the integrity check of the upgrade package fails, the signature verification is unsuccessful. If the signature verification is unsuccessful, the upgrade fails; if the signature verification is successful, the second device starts a version check to check whether the upgrade package version matches the second device. If the version check fails, the upgrade fails.
  • the second device processes the partition table and starts a binary upgrade.
  • Binary upgrade may include: parsing upgrade package data, sequentially writing partition images, and verifying partition images. After the binary upgrade is completed, the version number of the second device will be updated. After the update is completed, the upgrade of the second device is successful. At this point, the upgrade is completed. That is, the repair of the second device is completed.
  • the upgrade may specifically refer to an upgrade of a device from a version to a more advanced version, for example, from a basic version to a higher version.
  • the system repair in this embodiment of the present application may refer to upgrading the device from a damaged state to a normal state, and thus may also be referred to as an upgrade.
  • the process shown in FIG. 13 is only a possible implementation manner for the second device to perform system repair, and should not constitute any limitation to the present application.
  • the second device may, for example, perform system repair by performing some or all of the steps in FIG. 13 .
  • the second device can also implement system repair by executing a process other than that shown in FIG. 13 . This application does not limit this.
  • Another possible situation is that the second device cannot enter repair mode.
  • the first device performs proxy repair on the second device in the proxy repair mode.
  • FIG. 14 shows a specific process of the first device agent repairing the second device from the perspective of the device. As shown in FIG. 14 , in response to a user operation, the first device starts to perform the following steps.
  • Step 1401 the first device enters a proxy repair mode.
  • Step 1402 the first device triggers the AP of the second device to enter the forced loading mode through an instruction.
  • the first device may display a button of "agent repair" to the user through the user interface, and the user may click the agent repair button on the first device to trigger the second device to enter the forced loading mode.
  • the first device After the first device enters the proxy repair mode in response to the user operation, it can send an instruction to enter the forced loading mode to the second device through the connection relationship with the second device.
  • the AP of the second device may enter the forced loading mode based on the instruction.
  • Step 1403 the first device parses the upgrade package, and forces the loading and repairing of the minimum system image to the second device.
  • the repair minimal system may refer to an image upgrade package that can support the normal startup of the repair mode, and may specifically include the most basic modules that enable the repair mode to run.
  • the second device may enter a repair mode based on the repair minimal system.
  • the repair minimal system may include, but is not limited to, a preloader (preloader), a quick start module, a partition table (partition table, ptable), a repair module, and the like.
  • Step 1404 the first device triggers the second device to enter the proxy repair mode.
  • the first device may send an instruction to enter the proxy repair mode to the second device through the connection relationship with the second device, and the second device may enter the proxy repair mode based on the instruction.
  • Step 1405 the second device writes the upgrade package and the authentication file into the data block device.
  • the second device can obtain the upgrade package and the authentication file from the first device, and then write the data block device.
  • Step 1406 the second device enters the repair mode. It should be understood that, for operations performed by the second device entering the repair mode, reference may be made to the above related description in conjunction with FIG. 13 , or reference may also be made to other related processes in the prior art that can be used to implement system repair. For the sake of brevity, details are not repeated here.
  • the second device checks whether the data partition is complete.
  • the second device may check whether the repaired data partition of the second device is complete. It should be understood that data used to describe the partition information is set at the head of the data partition, and the partition information may be, for example, the partition size, the start address, the number of blocks, and the like.
  • the file system of the second device can read the data partition according to the partition information. Complete; if the reading is normal, it means that the data partition is complete and correct.
  • the second device does not need to acquire the backed up user data from the first device.
  • the second device may send a first message to the first device to notify the first device that the user data backed up does not need to be returned. Based on the first message, the first device can clear the locally saved backup user data.
  • S306 may be executed, and the second device may acquire the backed up user data through interaction with the first device.
  • the second device may send a second message to the first device to request to obtain the backed up user data, and the first device may return the backed up user data to the second device based on the second message.
  • the backup data may be files, such as pictures, music, documents, videos, etc., or may be binary images.
  • the backed up user data to the second device by the first device can also be implemented in the following two possible ways:
  • a first possible implementation manner is that, in the proxy repair mode, the first device copies the backed up files to the data partition of the second device to complete the return of the user data.
  • the second possible implementation is that in the proxy repair mode, the second device erases the data partition, the first device loads the backed up data partition image to the second device, and the second device starts a single image upgrade to complete the data partition. restoration.
  • first message and the second message listed above may be the same message, and the first device may use different instructions to determine whether the backed up user data needs to be returned; the first message and the second message may also be different message, which is not limited in this embodiment of the present application.
  • the first device obtains the proxy repair authorization of the second device to be repaired, and based on the proxy repair authorization, the first device can access the data of the second device regardless of whether the second device can be turned on or not. partition, so that the user data in the data partition of the second device can be backed up. Therefore, the probability of user data loss in the data partition in the repair scenario can be reduced; even if the data partition is damaged, the user data that is not lost can be backed up to reduce the loss of user data. Overall, user losses can be reduced.
  • each step of the above method may be implemented by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.
  • the present application also provides an electronic device, which may include: a memory and a processor.
  • the memory can be used to store computer programs; the processor can be used to call the computer programs in the memory, so that the electronic device executes the method executed by the first device or the method executed by the second device in the embodiment shown in FIG. 3 .
  • the present application also provides a computer program product, the computer program product includes: a computer program (also referred to as code, or instructions), when the computer program is executed, the electronic device is made to execute the embodiment shown in FIG. 3 .
  • a computer program also referred to as code, or instructions
  • the electronic device is made to execute the embodiment shown in FIG. 3 .
  • the present application also provides a computer-readable storage medium storing a computer program (also referred to as code, or instructions).
  • a computer program also referred to as code, or instructions.
  • the electronic device causes the electronic device to execute the method executed by the first device or the method executed by the second device in the embodiment shown in FIG. 3 .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or any other available processor. Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices, discrete gate or transistor logic devices, discrete hardware components discrete hardware components.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • unit may be used to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented in software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .
  • each functional module in each embodiment of the present application may be integrated into one processor, or may exist physically alone, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Telephone Function (AREA)

Abstract

一种数据备份方法和装置，该方法包括：第一设备获取对第二设备的代理修复授权，该代理修复授权用于第一设备对第二设备进行代理修复，该第二设备是待修复的设备，且第二设备无法开机；第一设备基于该代理修复授权，对第二设备的数据分区中的用户数据进行备份（S302），例如从第二设备的数据分区拷贝包含有用户数据的数据文件，或，拷贝数据分区的二进制镜像；第一设备在完成了对第二设备的用户数据的备份后，对第二设备进行代理修复（S304）。由此，可以降低修复场景下数据分区中用户数据丢失的概率；即便在数据分区损坏的情况下，也能够将未丢失的用户数据进行备份，减少用户数据的丢失，减小用户损失。

Description

一种数据备份方法和电子设备
本申请要求于2021年02月20日提交中国专利局、申请号为202110195341.9、申请名称为“一种数据备份方法和电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机领域，并且更具体地，涉及一种数据备份方法和电子设备。
背景技术
随着电子技术的不断发展，手机等终端已经成为人们日常生活中必不可少的智能设备。一旦设备异常，无法开机时，用户若没有预先完成用户数据的备份，即便进行了系统修复，但修复后的系统可能被恢复成出厂设置，这很可能造成用户数据全部丢失，导致用户损失严重。
因此，如何在手机无法开机时对用户数据(userdata)进行备份，是一项亟需解决的技术问题。
发明内容
本申请实施例提供了一种数据备份方法和电子设备，降低了修复场景下数据分区中用户数据丢失的概率，减少用户损失。
第一方面，本申请实施例提供了一种数据备份方法，该方法可以包括：第一设备获取对第二设备的代理修复授权，该代理修复授权用于第一设备对第二设备进行代理修复，第二设备是待修复的设备，且无法开机；第一设备基于该代理修复授权，对第二设备的数据分区中的用户数据进行备份；第一设备在完成了对第二设备的用户数据的备份后，对第二设备进行代理修复。
基于上述方案，第一设备先获取对待修复的第二设备的代理修复授权，基于该代理修复授权，第一设备可以代理修复模式下，对第二设备的数据分区中的用户数据进行备份，再对第二设备进行代理修复。因此，第一设备通过获取对第二设备的代理修复授权，进入代理修复模式，进而完成对第二设备的用户数据的备份，降低了修复过程中用户数据丢失的概率，减小用户损失。
可选地，第一设备可通过如下方式获取对待修复的第二设备的代理修复授权，包括：第一设备基于与第二设备之间的信赖关系，获取对待修复的第二设备的代理修复授权。
在上述过程中，第二设备完好时，第一设备可以与第二设备建立信赖关系，建立信赖关系后，即可获得第一设备对第二设备的代理修复授权，因此，第二设备损坏时，第一设备已经获取对第二设备的代理修复授权，可用于对第二设备的代理修复。
可选地，第一设备与第二设备的信赖关系可基于如下一项而建立：第二设备的授权信息、第二设备的开机密码、第一设备与第二设备的关联账号。
在上述过程中，第一设备与第二设备通过授权信息建立信赖关系，该授权信息例如可 以是由用户自定义口令生成授权码，也可以是根据设备的硬件信息生成的授权信息。或者，第一设备也可通过开机密码与第二设备建立信赖关系。该开机密码例如可以是人脸识别密码、指纹识别密码、数字密码等。又或者，第一设备还可通过与第二设备的关联账号建立信赖关系。第一设备与第二设备可以具有关联账号，或者说，是具有关联账号的两台设备。该关联账号，例如可以是绑定了同一账号，或者，是主账号与子账号等。第一设备与第二设备建立信赖关系的方法简单多样，而且便于用户操作。
可选地，第一设备还可通过如下方式获取对待修复的第二设备的代理修复授权，第一设备向服务器申请对第二设备的临时代理修复授权。
在上述过程中，第二设备损坏之前，没有与第一设备建立信赖关系，则第一设备也可通过向服务器申请临时授权的方法，获得对第二设备的代理修复授权，实现第一设备对第二设备的代理修复。
可选地，第一设备响应于用户的输入操作，向第二设备发送第二设备的数据分区的访问请求，该访问请求中携带访问密码，该访问密码为用户输入的密码，用于访问第二设备的数据分区。
在上述过程中，第一设备向第二设备发送第二设备的数据分区的访问请求，从而获得对第二设备的数据分区的访问权限，可以用于第一设备对第二设备的数据分区的访问。
可选地，第一设备对第二设备的数据分区中的用户数据进行备份，包括第一设备从第二设备的数据分区拷贝数据文件，该数据文件包含用户数据。
在上述过程中，第一设备从第二设备用户分区拷贝数据文件，从而完成对用户数据的备份，防止在修复过程中用户数据丢失，减小用户损失。
可选地，第一设备对第二设备的数据分区中的用户数据进行备份，包括：第一设备拷贝第二设备的数据分区的二进制镜像，以对用户数据进行备份，该二进制镜像包括第二设备数据分区的完整原始二进制数据。
在上述过程中，第一设备拷贝第二设备的数据分区的二进制镜像进行备份，从而即便数据分区数据文件损坏，也可通过备份二进制镜像的方法，完成用户数据的备份与恢复。
可选地，第一设备对第二设备进行代理修复，包括：第一设备获取升级包；第一设备向第二设备发送该升级包；第一设备触发第二设备进入修复模式，该升级包用于第二设备在修复模式下进行系统修复。
在上述过程中，第一设备获取升级包，可用于第二设备的系统修复，将该升级包发送给第二设备，第一设备触发第二设备进入修复模式，使得第二设备完成系统修复，减小了用户损失。
可选地，第一设备对所述第二设备进行代理修复，包括：第一设备获取升级包，该升级包用于第二设备的系统修复；第一设备解析升级包，以获取修复最小系统；第一设备将修复最小系统镜像到第二设备；第一设备触发第二设备进入代理修复模式，修复最小系统用于第二设备在代理修复模式下进行系统修复。
在上述过程中，第二设备无法进入修复模式时，在代理修复模式下，第一设备可以完成对第二设备的代理修复，使得第二设备在无法自行进入修复模式的情况下，也可通过第一设备完成第二设备的系统修复。
可选地，第一设备获取升级包，包括：第一设备向第一服务器发送第一设备对第二设 备的代理修复授权申请，以及第一设备的设备信息与第二设备的设备信息，该设备信息包括版本标识和设备标识，以从第一服务器获取授权文件，该授权文件用于指示第一设备对第二设备的代理修复授权；第一设备基于授权文件和设备信息，从第二服务器获取版本文件列表，第一设备基于版本文件列表，从第三服务器下载升级包。
在上述过程中，第一设备基于版本文件列表，从第三服务器获取升级包，该过程降低了下载的升级包版本不匹配的风险。
可选地，第一设备基于所述升级包，从第二服务器下载鉴权文件，鉴权文件用于在系统修复中对第二设备的鉴权。
在上述过程中，第一设备基于下载的升级包，向第二服务器获取鉴权文件，第二服务器将鉴权文件下发给第一设备，该鉴权文件既保证了升级包的完整性与正确性，又可用于在系统修复中对第二设备的鉴权，从而进行系统修复。
第二方面，本申请实施例提供了一种数据备份方法，包括：第二设备的微控制单元(microcontroller unit，MCU)接收来自第一设备的访问请求，访问请求用于请求访问第二设备的数据分区，访问请求中携带访问密码，该第二设备为待修复的设备，且第二设备无法开机；第一设备为用于对第二设备进行代理修复的设备；第二设备的MCU通过与第二设备的应用处理器(application processor，AP)之间的端口，请求读取预存在第二设备的安全分区中的密码；第二设备的MCU基于安全分区中的密码，对访问密码进行验证；第二设备的MCU在对访问密码验证成功的情况下，接受第一设备的访问请求。
基于上述方案，第二设备的MCU接收第一设备的访问请求后，可以通过MCU与AP之间的端口，读取第二设备的安全分区的密码，从而对访问请求进行验证，验证成功之后，第二设备可以允许第一设备访问，第一设备获得访问权限，MCU与AP之间的端口实现了两者之间的通信连接，通过该端口，MCU可以访问AP安全分区，从而使得第一设备获得访问权限。
第三方面，本申请提供了一种数据备份装置，包括处理器，所述处理器用于执行第一方面和第一方面任一种可能实现方式中的数据备份方法。
所述装置还可以包括存储器，用于存储指令和数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的指令时，可以实现上述第一方面描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。
可选地，所述数据备份装置为电子设备。
可选地，所述数据备份装置为配置在电子设备中的芯片或芯片系统。
第四方面，本申请提供了一种数据备份装置，包括应用处理器AP和微控制单元MCU，所述MCU用于执行第二方面中所述的数据备份方法。
可选地，所述数据备份装置为电子设备。
可选地，所述数据备份装置为配置在电子设备中的芯片或芯片系统。
第五方面，本申请提供了一种数据备份装置，用于实现第一至第二方面以及第一至第二方面任一种可能实现方式中的方法。
第六方面，本申请提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机实现第一至第二方面以及第一至第二方面任一种可能实现方式中的方法。
第七方面，本申请提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行第一方面和第二方面以及第一至第二方面以及第一至第二方面任一种可能实现方式中的方法。
附图说明
图1是适用于本申请实施例的电子设备的结构示意图；
图2是适用于本申请实施例的电子设备的具体结构示意图；
图3是本申请实施例提供的数据备份方法的示意性流程图；
图4是本申请实施例提供的数据备份方法的电子设备通信连接示意图；
图5是本申请实施例提供的数据备份方法的电子设备通信连接示意图；
图6是本申请实施例提供的电子设备连接示意图；
图7是本申请实施例提供的用户操作示意图；
图8是本申请实施例提供的第一设备授权检查示意性流程图；
图9是本申请实施例提供的对用户数据进行备份的示意图；
图10是本申请实施例提供的第一设备申请授权文件的示意图；
图11是本申请实施例提供的第一设备获取鉴权文件和下载升级包的示意图；
图12是本申请实施例提供的第二设备数据块设备的示意图；
图13是本申请实施例提供的系统修复的示意性流程图；
图14是本申请实施例提供的第一设备代理修复第二设备的示意性流程图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提供的方法可以应用于手机、平板电脑、可穿戴设备、车载设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、上网本、个人数字助理(personal digital assistant，PDA)、分布式设备等电子设备上。本申请实施例对电子设备的具体类型不作任何限定。
此外，本申请实施例中所述的方法可以支持安卓(Android)操作系统(operating system，OS)、鸿蒙操作系统(Harmony OS)、物联网操作系统(如轻量级物联网操作系统(lite operating system，LiteOS))等操作环境。本申请实施例对此不作任何限定。
示例性地，图1示出了电子设备100的结构示意图。如图1所示，该电子设备100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本申请示意的结构并不构成对电子设备100的具体限定。在另一些实 施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括AP、MCU、调制解调处理器、图形处理器(graphics processing unit，GPU)、图像信号处理器(image signal processor，ISP)、控制器、存储器、视频编解码器、数字信号处理器(digital signal processor，DSP)、基带处理器及神经网络处理器(neural-network processing unit，NPU)等中的一个或多个。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，应用处理器通过音频模块170(如扬声器170A等)输出声音信号，或通过显示屏194显示图像或视频。
控制器可以是电子设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
处理器110可以通过执行指令，执行不同的操作，以实现不同的功能。该指令例如可以是设备出厂前预先保存在存储器中的指令，也可以是用户在使用过程中安装新的应用(application，APP)之后从APP中读取到的指令，本申请实施例对此不作任何限定。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口、集成电路内置音频(inter-integrated circuit sound，I2S)接口、安全数字输入输出接口(secure digital input and output，SDIO)、脉冲编码调制(pulse code modulation，PCM)接口、通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口、通用同步异步收发传输器(universal synchronous asynchronous receiver/transmitter，USART)、移动产业处理器接口(mobile industry processor interface，MIPI)、通用输入输出(general-purpose input/output，GPIO)接口、用户标识模块(subscriber identity module，SIM)接口和/或通用串行总线(universal serial bus，USB)接口等。
I2C接口是一种双向同步串行总线，包括一根串行数据线(serial data line，SDA)和一根串行时钟线(derail clock line，SCL)。在一些实施例中，处理器110可以包含多组I2C总线。处理器110可以通过不同的I2C总线接口分别耦合触摸传感器180K，充电器，闪光灯，摄像头193等。例如：处理器110可以通过I2C接口耦合触摸传感器180K，使处理器110与触摸传感器180K通过I2C总线接口通信，实现电子设备100的触摸功能。
I2S接口可以用于音频通信。在一些实施例中，处理器110可以包含多组I2S总线。处理器110可以通过I2S总线与音频模块170耦合，实现处理器110与音频模块170之间的通信。在一些实施例中，音频模块170可以通过I2S接口向无线通信模块160传递音频信号，实现通过蓝牙耳机接听电话的功能。
PCM接口也可以用于音频通信，将模拟信号抽样，量化和编码。在一些实施例中，音频模块170与无线通信模块160可以通过PCM总线接口耦合。在一些实施例中，音频模块170也可以通过PCM接口向无线通信模块160传递音频信号，实现通过蓝牙耳机接听 电话的功能。所述I2S接口和所述PCM接口都可以用于音频通信。
UART接口是一种通用串行数据总线，用于异步通信。该总线可以为双向通信总线。它将要传输的数据在串行通信与并行通信之间转换。在一些实施例中，UART接口通常被用于连接处理器110与无线通信模块160。例如：处理器110通过UART接口与无线通信模块160中的蓝牙模块通信，实现蓝牙功能。在一些实施例中，音频模块170可以通过UART接口向无线通信模块160传递音频信号，实现通过蓝牙耳机播放音乐的功能。
MIPI接口可以被用于连接处理器110与显示屏194，摄像头193等外围器件。MIPI接口包括摄像头串行接口(camera serial interface，CSI)，显示屏串行接口(display serial interface，DSI)等。在一些实施例中，处理器110和摄像头193通过CSI接口通信，实现电子设备100的拍摄功能。处理器110和显示屏194通过DSI接口通信，实现电子设备100的显示功能。
GPIO接口可以通过软件配置。GPIO接口可以被配置为控制信号，也可被配置为数据信号。在一些实施例中，GPIO接口可以用于连接处理器110与摄像头193，显示屏194，无线通信模块160，音频模块170，传感器模块180等。GPIO接口还可以被配置为I2C接口，I2S接口，UART接口，MIPI接口等。
USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。USB接口130可以用于连接充电器为电子设备100充电，也可以用于电子设备100与外围设备之间传输数据。也可以用于连接耳机，通过耳机播放音频。该接口还可以用于连接其他电子设备，例如AR设备等。
可以理解的是，本申请示意的各模块间的接口连接关系，只是示意性说明，并不构成对电子设备100的结构限定。在另一些实施例中，电子设备100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。在一些有线充电的实施例中，充电管理模块140可以通过USB接口130接收有线充电器的充电输入。在一些无线充电的实施例中，充电管理模块140可以通过电子设备100的无线充电线圈接收无线充电输入。充电管理模块140为电池142充电的同时，还可以通过电源管理模块141为电子设备供电。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110、内部存储器121、外部存储器、显示屏194、摄像头193和无线通信模块160等供电。电源管理模块141还可以用于监测电池容量、电池循环次数、电池健康状态(漏电，阻抗)等参数。在其他一些实施例中，电源管理模块141也可以设置于处理器110中。在另一些实施例中，电源管理模块141和充电管理模块140也可以设置于同一个器件中。
电子设备100的无线通信功能可以通过天线1、天线2、移动通信模块150、无线通信模块160、调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。电子设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在电子设备100上的包括2G/3G/4G/5G等无线通信的 解决方案。移动通信模块150可以包括至少一个滤波器、开关、功率放大器、低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(不限于扬声器170A，受话器170B等)输出声音信号，或通过显示屏194显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以提供应用在电子设备100上的包括无线局域网(wireless local area networks，WLAN)，如无线保真(wireless fidelity，Wi-Fi)网络)、蓝牙(bluetooth，BT)、全球导航卫星系统(global navigation satellite system，GNSS)、调频(frequency modulation，FM)、近距离无线通信技术(near field communication，NFC)、红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，电子设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得电子设备100可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，第五代(5th generation，5G)通信系统，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。所述GNSS可以包括全球卫星定位系统(global positioning system，GPS)，GNSS，北斗卫星导航系统(BeiDou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
电子设备100可以通过GPU、显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏194用于显示图像、视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)、有机发光二极管(organic light-emitting diode，OLED)、有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting  diode，AMOLED)、柔性发光二极管(flex light-emitting diode，FLED)，迷你LED(Mini LED)、微Led(Micro LED)、微OLED(Micro-OLED)、量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，电子设备100可以包括一个或多个显示屏194。
电子设备100可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。
ISP用于处理摄像头193反馈的数据。例如，拍照时，打开快门，光线通过镜头被传递到摄像头感光元件上，光信号转换为电信号，摄像头感光元件将所述电信号传递给ISP处理，转化为肉眼可见的图像。ISP还可以对图像的噪点，亮度，肤色进行算法优化。ISP还可以对拍摄场景的曝光，色温等参数优化。在一些实施例中，ISP可以设置在摄像头193中。
摄像头193用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB、YUV等格式的图像信号。在一些实施例中，电子设备100可以包括一个或多个摄像头193。
数字信号处理器用于处理数字信号，除了可以处理数字图像信号，还可以处理其他数字信号。例如，当电子设备100在频点选择时，数字信号处理器用于对频点能量进行傅里叶变换等。
视频编解码器用于对数字视频压缩或解压缩。电子设备100可以支持一种或多种视频编解码器。这样，电子设备100可以播放或录制多种编码格式的视频，例如：动态图像专家组(moving picture experts group，MPEG)1、MPEG2、MPEG3、MPEG4等。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展电子设备100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行电子设备100的各种功能应用以及数据处理。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储电子设备100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
电子设备100可以通过音频模块170，如扬声器170A、受话器170B、麦克风170C和耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放、录音等。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。在一些实施例中，音频模块170可以设置于处理器110中，或将音频模块170的部分功能模块设置于处理器110中。
扬声器170A，也称“喇叭”，用于将音频电信号转换为声音信号。电子设备100可以通过扬声器170A收听音乐，或收听免提通话。
受话器170B，也称“听筒”，用于将音频电信号转换成声音信号。当电子设备100接听电话或语音信息时，可以通过将受话器170B靠近人耳接听语音。
麦克风170C，也称“话筒”，“传声器”，用于将声音信号转换为电信号。当拨打电话或发送语音信息时，用户可以通过人嘴靠近麦克风170C发声，将声音信号输入到麦克风170C。电子设备100可以设置至少一个麦克风170C。在另一些实施例中，电子设备100可以设置两个麦克风170C，除了采集声音信号，还可以实现降噪功能。在另一些实施例中，电子设备100还可以设置三个、四个或更多麦克风170C，实现采集声音信号，降噪，还可以识别声音来源，实现定向录音功能等。
耳机接口170D用于连接有线耳机。耳机接口170D可以是USB接口130，也可以是3.5mm的开放移动电子设备平台(open mobile terminal platform，OMTP)标准接口，美国蜂窝电信工业协会(cellular telecommunications industry association of the USA，CTIA)标准接口。
按键190包括开机键(或称电源键)、音量键等。按键190可以是机械按键，也可以是触摸式按键。电子设备100可以接收按键输入，产生与电子设备100的用户设置以及功能控制有关的键信号输入。例如在本申请实施例中，用户可通过对开机键190的按压或触摸，实现屏幕休眠和屏幕唤醒的功能。
马达191可以产生振动提示。马达191可以用于来电振动提示，也可以用于触摸振动反馈。例如，作用于不同应用(例如拍照，音频播放等)的触摸操作，可以对应不同的振动反馈效果。作用于显示屏194不同区域的触摸操作，马达191也可对应不同的振动反馈效果。不同的应用场景(例如：时间提醒，接收信息，闹钟，游戏等)也可以对应不同的振动反馈效果。触摸振动反馈效果还可以支持自定义。
指示器192可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息，未接来电，通知等。
SIM卡接口195用于连接SIM卡。SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现和电子设备100的接触和分离。电子设备100可以支持一个或多个SIM卡接口。SIM卡接口195可以支持Nano SIM卡、Micro SIM卡、SIM卡等。同一个SIM卡接口195可以同时插入多张卡。所述多张卡的类型可以相同，也可以不同。SIM卡接口195也可以兼容不同类型的SIM卡。SIM卡接口195也可以兼容外部存储卡。电子设备100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，电子设备100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在电子设备100中，不能和电子设备100分离。
可以理解的是，本申请示意的结构并不构成对电子设备100的具体限定。在另一些实施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
电子设备100的软件系统可以采用分层架构、事件驱动架构、微核架构、微服务架构或云架构。本申请以分层架构的Android系统为例，示例性说明电子设备100的软件结构。其中，本申请对电子设备的操作系统的类型不做限定。例如，Android系统、鸿蒙OS等。
为了更好地理解本申请实施例，下面首先结合图2对适用于本申请提供的数据备份方法的电子设备的结构做更详细地说明。
如图2所示，该电子设备200可以包括MCU、AP、主存储器、从存储器、第一端口、第二端口、控制器、无线通信模块，如包括无线保真(wireless fidelity，WIFI)模块或蓝牙模块，以及其他外设模块。其中，MCU和AP可以通过第一端口实现与外部的有线连接，也可以通过无线通信模块实现与外部的无线连接，MCU可以通过SDIO、GPIO、I2S或USART等接口实现与AP的数据通信，AP和MCU可以访问主存储器。
其中，MCU可作为从属处理器，负责异常场景下的安全校验、端口管理以及主存储器管理。此外，MCU具有只读AP安全分区的权限。
需要说明的是，只读AP安全分区可以这样理解：安全分区可以是位于主存储器的一块区域，可以用于存储需要保密的数据，比如开机密码、解锁指纹数据、解锁人脸数据等。安全分区通常可以由AP控制，例如在应用程序申请使用该安全分区中的数据时，可以由AP控制读取，读写过程需要系统进行加解密。在本申请实施例中，MCU具有只读AP安全分区的权限，可以是指，MCU可以通过AP实现对安全分区的只读。下文中为了简洁，省略对相同或相似情况的说明。
主存储器可用于存储程序和数据，MCU可以被授权访问主存储器，但仅限以块设备(block device)方式获取用户分区剩余空间大小、读写块设备尾部剩余空间。可选地，主存储器与MCU之间还设置有控制器。或者，控制器也可集成在MCU中。
从存储器可用于存放AP动态加密秘钥等安全备份信息。
第一端口是MCU和AP的共享端口，MCU和AP通过第一端口与外部实现通信连接。
第二端口是MCU和AP的通信端口，用于实现两者之间的通信连接。
应理解，图2所示的结构可适用于下文所述的第一设备和第二设备中的任意一个电子设备。本申请实施例对此不作限定。
正常情况下，AP可从主存储器中读取数据。该主存储器中可以包括系统(system)分区、启动(boot)分区、修复(recovery)分区、数据(data)分区、杂项(miscellaneous，misc)分区等。其中，一旦启动分区损坏，导致电子设备无法正常开机，就需要对该电子设备进行修复。然而修复后的系统可能被恢复成出厂设置，如果用户没有预先完成该电子设备中用户数据的备份，用户数据可能全部丢失，导致用户损失严重。
针对上述问题，本申请实施例提供了一种数据备份方法。响应于用户的操作，第一设备与第二设备建立通信连接，建立通信连接后，第一设备获取对第二设备的代理修复授权，该代理修复授权用于第一设备对第二设备的代理修复，基于该代理修复授权，第一设备对第二设备的数据分区中的用户数据进行备份，备份完成后，第一设备启动对第二设备的代理修复，从而完成对第二设备的数据分区中的用户数据的营救备份。
在介绍本申请实施例之前，首先对本申请中所涉及的术语进行说明。
1、第一设备：完好的电子设备，例如，手机，平板等。在本申请实施例中，第一设备可用于在代理修复模式下对第二设备进行代理修复。
2、第二设备：无法开机的电子设备，或者称，变砖的电子设备。例如，手机，平板等。
3、第一端口：MCU和AP的共享端口。具体而言，同一电子设备中的MCU和AP可 共享第一端口，MCU和AP中的一个可使用该第一端口与外部设备通信。第一端口由AP切换为MCU所使用，或者由MCU切换为AP所使用时，需要特定的命令触发。
需要说明的是，MCU使用第一端口与外部设备通信时需要严格管控，此端口原则上只能用于设备与设备(device2device，D2D)之间的连接，如手机、PC、平板电脑等电子设备之间的连接。且在非研发调试场景下不开放命令调试窗口。
4、第二端口：逻辑意义上的端口，用于实现MCU和AP之间的通信连接。第二端口具备强制加载与调试交互的能力。例如，MCU可以通过第二端口访问AP的安全分区。
5、升级包(update)：在有些操作系统中，如安卓系统中，升级包可用于系统升级或修复。升级包从服务器下载，如从空间下载技术(over the air technology，OTA)服务器下载。终端设备在需要进行系统升级或修复时，可先进入修复(recovery)模式，然后使用该升级包进行系统升级或修复。应理解，在有些情况下，升级包也可以称为修复包、修复升级包等。本申请对其命名不作限定。
下面结合附图，详细说明本申请实施例提供的数据备份方法。应理解，本申请实施例提供的数据备份方法不但可应用于第二设备无法开机的场景，也可以应用于第二设备可开机但无法进入修复模式的场景。本申请实施例对此不作限定。
图3为本申请实施例提供的数据备份方法的示意性流程图。应理解，图3所示的方法300可以在第一设备和第二设备建立通信连接的情况下执行。
一种可能的情况是，第二设备的AP通过第一端口与外部连接可以被识别且能够进行正常的数据通信时，或者说，第二设备能够进行正常的数据通信时，可以进入快速启动(fastboot)模式，但无法进入修复模式。第一设备的AP可连接至第二设备的AP，实现第一设备与第二设备之间的通信连接。
如图4所示，该第一设备的AP可通过端口#1(即，第一设备的第一端口)与第二设备的端口#2(即，第二设备的第一端口)连接，进而与第二设备的AP通信。
另一种可能的情况是，第二设备的AP侧第一端口不响应时，也无法进入快速启动模式，无法进入修复模式。第一设备的AP可连接至第二设备的MCU，实现第一设备与第二设备之间的通信连接。
应理解，AP侧的第一端口不响应，具体可以是指，支撑AP侧运行的系统分区受损，AP侧系统无法正常运行，无法支撑对第一端口进行正常监听以及数据传输等功能。
如图5所示，该第一设备的AP可通过端口#1(即，第一设备的第一端口)与第二设备的端口#2(即，第二设备的第一端口)连接，进而与第二设备的MCU通信。该第二设备的MCU与AP之间通过端口#3(即，第二设备的第二端口)通信。
图3所示的方法300可以包括S301至S306，下面对图3中的各个步骤做详细说明。应理解，图3所示的流程中第一设备所执行的动作例如可以由第一设备中的AP来执行。此外，图3所示的第一设备和第二设备可以满足如下至少一项：第一设备和第二设备是相同品牌的设备，第一设备和第二设备具有相同的操作系统，如安卓系统、或鸿蒙系统等；以及第一设备和第二设备为相同类型的设备，如手机、平板电脑等。
S301、第一设备获取对第二设备的代理修复授权。
应理解，第一设备可以在获得对第二设备的代理修复授权后，获得对第二设备的访问权限，以便访问第二设备，并对第二设备进行代理修复。
一种可能的情况是，第一设备在第二设备完好时已经获得代理修复授权。示例性地，第二设备完好时，与第一设备连接，并与第一设备建立信赖关系。
第二设备在完好时与第一设备连接的方式可以是无线连接，也可以是有线连接。第二设备可以通过WIFI、蓝牙等无线连接方式与第一设备连接，也可以通过有线连接的方式与第一设备连接。本申请实施例对此不作限定。
图6中的a)是通过无线连接方式连接的第一设备和第二设备的示意图。第二设备完好时，第一设备与第二设备可分别开启无线通信模块，实现通信连接。
示例性地，第一设备与第二设备通过WIFI模块建立通信连接。第二设备开启WIFI热点，第一设备连接上第二设备的WIFI信号，即可实现第一设备与第二设备的通信连接。
或者，第一设备与第二设备也可分别开启蓝牙模块，通过蓝牙配对的方式实现通信连接。
应理解，通过WIFI模块或蓝牙模块实现通信连接仅为两种可能的实现方式，不应对本申请构成任何限定。
图6中的b)是通过有线连接方式连接的第一设备和第二设备的示意图。第二设备的第一端口与第一设备的第一端口通过有线连接方式建立通信连接。
图6中的b)所示的第二设备的AP无法通过第一端口与外部设备连接，此情况下，第二设备可通过第一端口连接至第一设备的MCU，MCU可通过第一端口连接至第一设备的AP，从而建立起第一设备与第二设备的通信连接。应理解，图6中的b)所示的连接关系与图5所示的连接关系相似，为了简洁，此处不再赘述。
图6中虽未予以示出，但可以理解，第二设备的AP可通过第一端口与外部设备连接时，第一设备与第二设备也可以通过如图4所述的连接方式实现通信连接。
第一设备和第二设备可以在完成连接后建立信赖关系。第一设备和第二设备可分别通过“设备互助”来建立信赖关系。
为方便理解和说明，下文中以第一设备从第二设备获得代理修复授权为例来说明。可以理解的是，基于下文所述相同的方法，第二设备也可以获得第一设备的代理修复授权。
示例性地，“设备互助”的方法例如可以包括但不限于如下几种：
方法一、通过授权信息建立信赖关系。该授权信息例如可以是由用户自定义口令生成授权码，也可以是根据设备的硬件信息生成的授权信息。本申请实施例对此不作限定。
例如，用户自定义口令生成的第一设备的授权码和第二设备的授权码可以分别预先保存在第一设备的从存储器和第二设备的从存储器中，第一设备与第二设备握手后便可匹配两个设备的授权码，若匹配成功，则自动授权。
又例如，第一设备可以基于第二设备的序列号(series number，SN)等硬件信息与第二设备握手，第一设备在与第二设备握手后便可自动授权。应理解，SN仅为硬件信息的一例，该硬件信息还可以是其他可用于唯一标识一台设备的信息。本申请实施例包括但不限于此。
一示例，第二设备的MCU可以读取第二设备的序列号，基于第一设备与第二设备之间的连接关系，第二设备可以通过第一端口将序列号发送给第一设备。
方法二、通过开机密码建立信赖关系。该开机密码例如可以是人脸、指纹、数字密码等。
例如，用户可以在第一设备进入授权检查后，输入第二设备的开机密码，以便获得授权。
方法三、通过关联账号建立信赖关系。第一设备与第二设备可以具有关联账号，或者说，是具有关联账号的两台设备。所述关联账号，例如可以是绑定了同一账号，或者，是主账号与子账号等。这里的账号，例如可以是设备账号，或者，手机号等。本申请对此并不限定。比如，第一设备和第二设备可以是同一账号的两个设备；又比如，第一设备的账号是主账号，第二设备的账号是子账号；还比如，第一设备的账号是子账号，第二设备的账号是主账号，等等。为了简洁，此处不一一列举。第一设备可以检查是否与第二设备具有关联账号，若是，则第二设备可获得授权。
另一种可能的情况是，第一设备在第二设备损坏时获得代理修复授权。第一设备可以向服务器(如授权服务器)申请对第二设备的临时代理修复授权。
示例性地，第一设备可以向授权服务器提供第一设备、第二设备的身份验证信息等，以请求授权服务器评估是否授予该第一设备对第二设备的临时代理修复权限。该身份验证信息例如可以是用于公钥密码机制(public key infrastructure，PKI)校验的信息，例如包括但不限于，公钥、数字证书、数字签名等。
一种可能的实现方式是，第一设备可以在连接至第二设备后，第一设备的第一端口(如图4或图5中的端口#1)可检测到第二设备。基于此，第一设备可通过用户界面(user interface，UI)显示“授权检查”的按钮，如图7所示。用户可点击该按钮，触发该第一设备进行授权检查。响应于用户的操作，第一设备进入授权检查。
图8示出了第一设备进行授权检查的具体过程。如图8所示，第一设备首先可确定是否已与第二设备建立信赖关系。若第二设备已与第一设备建立信赖关系，则授权检查可通过，第一设备可以获得对第二设备的代理修复授权。若第二设备未与第一设备建立信赖关系，则第一设备可以通过执行上述“设备互助”中的方法来与第二设备建立信赖关系，如通过第二设备的授权信息、输入第二设备的开机密码等来校验，若校验通过，则授权检查可通过，第一设备可以获得对第二设备的代理修复授权；若校验不通过，则授权检查也不通过，第一设备可以向授权服务器申请临时代理修复授权。可以理解，第一设备通过“设备互助”来与第二设备建立信赖关系需要在第二设备可正常开机的情况下执行。若第二设备无法正常开机，则相当于校验不通过，授权检查也不通过，第一设备可以直接向授权服务器申请临时代理修复授权。若服务器允许临时授权，则第一设备获得对第二设备的代理修复授权。
S302、第一设备基于代理修复授权，对第二设备的数据分区中的用户数据进行备份。
可以在代理修复模式下解密第二设备，以访问第二设备的数据分区。
第一设备在获得代理修复授权后，可以获得对第二设备的数据分区的访问权限，进而对第二设备的数据分区进行用户数据的备份。
可选地，第二设备的数据分区的访问权限还可通过密码校验的方式来获得。比如，第一设备在获得代理修复授权后，可通过用户界面提示用户输入用于解密第二设备的数据分区的密码。用户输入的密码可通过第一设备与第二设备之间的连接关系(可参见上文图4或图5中所示的连接关系)被发送至第二设备。示例性地，在图4所示的连接关系下，第二设备的AP对输入的密码进行校验；在图5所示的连接方式下，第二设备的MCU可以 读取第二设备的AP安全分区，对用户输入的密码进行校验。若校验成功，则第一设备可以获得对第二设备的数据分区的访问权限；若校验失败，则第一设备无法获得对第二设备的数据分区的访问权限。进一步地，第一设备还可通过用户界面提示用户输入个人校验信息，以用于第二设备的校验。该个人校验信息例如可以包括设备个人密码或个人账号等。
示例性地，第一设备响应于用户的输入操作，向第二设备发送第二设备的数据分区的访问请求，第二设备的MCU接收来自第一设备的访问请求，通过与第二设备的AP之间的第二端口，请求读取预存在第二设备的安全分区中的密码，基于该密码，MCU对访问密码进行验证，验证成功，则接受第一设备的访问请求。
可以理解的是，第一设备向第二设备发送的访问请求中携带访问密码，该访问密码为用户输入的密码，用于访问第二设备的数据分区。
需要说明的是，该访问密码和建立信赖关系中的开机密码可以是相同的密码，也可以是不同的密码，本申请实施例对此不作限定。若是相同的密码，建立信赖关系中输入开机密码的同时可以获得对第二设备的数据分区的访问权限，也可以在备份之前再次进行密码的校验，本申请实施例对此不作限定。
第一设备对第二设备的数据分区中的用户数据的备份可以通过如下两种可能的实现方式来实现：
第一种可能的实现方式是，第一设备可以从第二设备的数据分区拷贝数据文件。这里所述的数据文件，例如可以是图片、音乐、视频等对用户可见的数据文件。应理解，文件系统可以把关联的用户数据组织成文件，因此，该数据文件可以包括用户数据，或者说，数据文件是用户数据呈现给用户的一种形式。
第二种可能的实现方式是，第一设备可以拷贝第二设备的数据分区的二进制镜像。这里所述的二进制镜像可以是指第二设备数据分区的二进制镜像，该二进制镜像不仅包含用户可见的数据文件，还包含用户不可见的系统文件。也就是说，对该第二设备的数据分区的二进制镜像的拷贝，也就是对第二设备的数据分区的完整原始二进制数据的拷贝。此处的数据分区的完整原始二进制数据具体可以是指数据分区的一整块连续存储的二进制数据。第一设备拷贝第二设备的数据分区的二进制镜像到本地的过程，也就是将第二设备的数据分区在第一设备的存储区中存一个完全相同的副本。
为便于区分和理解，下文结合图9来说明文件备份和二进制镜像备份这两种实现方式。图9是本申请实施例提供的对用户数据进行备份的示意图。应理解，图9中为便于区分，将第一设备中的各分区中的数据以A标识，将第二设备中的各分区中的数据以B标识。
一示例，第二设备的MCU可以在完成校验后激活第二设备的数据分区，将数据分区以外设存储设备的方式挂载到第一设备。应理解，将数据分区以外部存储设备的形式挂载到第一设备，可以是指，将该数据分区接到Linux的一个文件夹下，从而将该数据分区和该目录联系起来，用户只要访问该文件夹，就相当于访问该数据分区。如图9所示，第二设备的数据分区就好比是第一设备的一部分。由此，第一设备可以访问第二设备的数据分区。用户可通过对第一设备的操作，将第二设备数据分区的数据文件拷贝到第一设备，完成对第二设备用户数据的备份。该示例可对应于上文所述的用户数据备份的第一种可能的实现方式。
另一示例，第一设备可以在第二设备的MCU完成校验后，读取第一设备的数据分区， 将第二设备的数据分区的二进制镜像拷贝到第一设备，完成对第二设备用户数据的备份。如图9所示，第二设备的数据分区的二进制镜像被拷贝到第一设备的存储区中。该示例可对应于上文所述的用户数据备份的第二种可能的实现方式。
可以理解的是，二进制镜像不同于文件备份，二进制镜像备份不需要将第二设备的数据分区挂载到第一设备，二进制镜像是对第二设备的数据分区的完整的备份，将第二设备的数据分区的二进制镜像拷贝到第一设备，文件系统需要对二进制镜像进行处理，才能形成对用户可见的文件。因此，即使第二设备的数据分区损坏，或者说，第二设备的数据分区的文件缺失，也可以通过二进制镜像的方式来实现对用户数据的备份。但可以理解的是，在数据分区损坏的情况下，可能存在部分用户数据的丢失，这些丢失的数据可能无法进行备份。
S303、第一设备获取升级包，该升级包用于对第二设备进行代理修复。
第一设备完成对第二设备的用户数据备份后可以向服务器获取升级包，并基于升级包完成对第二设备的代理修复。
示例性地，第一设备获取升级包，具体可以包括：第一设备获取授权文件、第一设备获取版本文件列表(filelist)，以及第一设备下载升级包和鉴权文件。其中，第一设备获取授权文件是用于获得对第二设备进行代理修复的授权文件，该授权文件可用于后续获取版本文件列表。版本文件列表可用于确定需要下载的升级包的版本。升级包可用于对第二设备进行系统修复。鉴权文件可用于第二设备的修复过程中的鉴权。
下面将结合附图分别说明第一设备获取授权文件、获取版本文件列表和下载升级包、鉴权文件的过程。
图10是本申请实施例提供的第一设备申请授权文件的示意图。
示例性地，第一设备可以向授权服务器(即，第一服务器的一例)申请授权文件。该授权服务器例如可以由设备厂商提供。
如图10所示，第一设备在获得第二设备的代理修复授权后，可以向授权服务器发送第一设备对第二设备的代理修复授权申请，以及第一设备的设备信息与第二设备的设备信息，以便于授权服务器进行备案审核。其中，该设备信息例如可以包括但不限于，版本标识、设备标识等。应理解，版本标识可用于指示设备的版本，设备标识可用于标识设备，例如可以包括但不限于设备序列号。授权服务器可以对设备信息进行公钥密码机制(public key infrastructure，PKI)校验，并对代理修复授权申请进行合法性认证。若PKI校验通过，且合法性认证通过，则审核通过授权服务器可以向第一设备下发授权文件。该授权文件具有唯一性，可以包括第一设备的设备信息和第二设备的设备信息。且该授权文件区分方向性，只用于第一设备对第二设备的代理修复。
图11是本申请实施例提供的第一设备获取鉴权文件和下载升级包的示意图。
示例性地，第一设备可以从搜包服务器(即，第二服务器的一例)获取鉴权文件，并从OTA服务器(即，第三服务器的一例)下载升级包，搜包服务器和OTA服务器例如可以由设备厂商提供。
如图11所示，第一设备基于授权文件和第二设备的设备信息，从搜包服务器获取版本文件列表。具体而言，第一设备获得授权文件，也即获取到第一设备对第二设备的代理修复授权。第一设备可以基于该代理修复授权，第一设备读取第二设备的设备信息，构造请 求消息(为便于区分和说明，例如记为第一请求消息)发送给搜包服务器，如图11中的①所示。
可选地，该第一请求消息包含第二设备的设备信息。进一步可选地，该第一请求消息还包含第一设备获得的授权文件。其中，第二设备的设备信息可以包括但不限于版本标识和设备标识。
搜包服务器收到第一请求消息后，对该第二设备的设备信息进行校验，校验通过并发现有可供第二设备升级的版本，搜包服务器便可下发版本文件列表给第一设备，如图11中的②所示。示例性地，该版本文件列表中记载了OTA服务器地址和升级包的版本信息，例如升级包的包名、大小、版本号等信息。
第一设备可以根据OTA服务器地址找到OTA服务器，并根据版本文件列表中的升级包版本信息，例如可以是版本标识(version identifier，ID)，构造请求消息(为便于区分和说明，例如记为第二请求消息)，并发送给OTA服务器，如图11中的③所示。OTA服务器可基于该第二请求消息，下发对应的升级包给第一设备，如图11中的④所示。第一设备还可以基于该升级包，向搜包服务器发送请求消息(为便于区分和说明，例如记为第三请求消息)，以请求搜包服务器下发该第二设备的鉴权文件。
由此，第一设备获取到用于代理修复第二设备的升级包。
需要说明的是，该第一设备从OTA服务器下载的升级包可以为一个或多个升级包。本申请对于第一设备从OTA服务器下载的升级包的数量不作限定。示例性地，若第一设备从搜包服务器接收到的版本文件列表中包括多个(比如三个)升级包的版本标识，则该第一设备可以根据每个升级包的版本标识，构造一个请求消息，以从OTA服务器下载相应的升级包。
应理解，上述过程所用到的授权服务器、搜包服务器以及OTA服务器可以是相互独立的多台物理设备，也可以是集成在一台物理设备中的，本申请对此不构成任何限定。可以理解的是，授权服务器、搜包服务器和OTA服务器只是基于不同的功能而做出的划分，不应对设备的具体形态构成任何限定。另外，各服务器的名称仅为示例，不应对本申请构成任何限定。本申请对于各服务器的具体名称不作限定。例如，OTA服务器也可以称为下包服务器。
还应理解，第一设备获取升级包的方法不仅限于上文。示例性地，第一设备可以将第一设备的设备和第二设备的设备信息提交给服务器，服务器根据第二设备的设备信息，将鉴权文件以及与第二设备版本相匹配的升级包发送给第一设备，第一设备即可获得用于修复第二设备的升级包。
第一设备获得升级包后，可以保存该升级包，以便于后续对第二设备的代理修复。第一设备可以将该升级包存储在第一设备本地，也可以存储在第二设备中，本申请实施例对此不作限定。
一种可能的情况是，第一设备可以访问第二设备的数据块设备(data block device)。此情况下，第一设备可以直接将升级包存入第二设备的数据块设备中，比如放在第二设备的数据块设备的尾部。
图12是本申请实施例提供的第二设备数据块设备的示意图。如图12所示，升级包和鉴权文件可以二进制形式存放于第二设备的数据块设备尾部。
另一种可能的情况是，第一设备无法访问第二设备的数据块设备。此情况下，第一设备可以将升级包以文件格式存放在第一设备的存储设备中。比如，存放在第一设备的主存储器中。
可以理解的是，第二设备的数据分区损坏是依据数据分区头部数据来判断的，所以，当第一设备可以访问第二设备的数据块设备时，即使第二设备的数据分区损坏时，将升级包放在数据块设备尾部，依然可以保证升级包的存储。
S304、第一设备对第二设备进行代理修复。
第一设备可以使用上文所获取到的升级包，对第二设备进行代理修复。需要说明的是，第一设备对第二设备的代理修复可以是在第二设备可以自行进入修复模式的情况下执行，也可以是在第二设备无法自行进入修复模式的情况下执行。本申请实施例对此不作限定。
需要说明的是，无论第二设备是否可以自行进入修复模式，该第二设备都处于无法正常开机的状态。
一种可能的情况是，第二设备能够自行进入修复模式。例如，该第二设备的系统镜像处于受损状态，需要进入修复模式，以进行系统修复。此情况下，第一设备可以在代理修复模式下触发第二设备进入修复模式，进行系统修复。
示例性地，第一设备可通过用户界面向用户显示“代理修复”的按钮，用户可点击第一设备上的代理修复按钮来触发第二设备进入修复模式。第一设备响应于用户操作，进入代理修复模式后，可通过与第二设备之间的连接关系，向第二设备发送进入修复模式的指令。第二设备基于该指令，进入系统修复模式。
图13是本申请实施例提供的系统修复的示意性流程图。
如图13所示，响应于第一设备的触发，第二设备开始升级。
首先，第二设备解析升级命令。
示例性地，响应于第一设备的触发，如上文所述的第一设备发送的进入修复模式的指令，第二设备的AP可以向misc分区写升级命令，第二设备重启，并可以从misc分区读取和解析该升级命令，进入修复模式。
应理解，在第二设备的AP能够通过第一端口与外部通信的情况下，第一设备可以通过向第二设备的AP发送指令，使第二设备的AP直接进入修复模式；在第二设备的AP不能通过第一端口与外部通信的情况下，第一设备可以通过向第二设备的MCU发送升级命令，由MCU中的LiteOS触发AP进入修复模式。
解析完成后，第二设备开始鉴权。第二设备可以基于预先获取到的鉴权文件进行鉴权。若鉴权不通过，则升级失败，第二设备无法完成修复；若鉴权通过，则开始升级包验签，应理解，对升级包的验签可以包括对升级包的正确性和完整性的校验。若对升级包的正确性校验和完整性校验均通过，则验签成功；若对升级包的正确性校验或完整性校验中有一项未通过，则验签不成功。若验签不成功，则升级失败；若验签成功，则第二设备开始版本检查，以查验升级包版本是否与第二设备匹配。若版本检查不通过，则升级失败。若版本检查通过，则第二设备对分区表进行处理，启动二进制(binary)升级。二进制升级可以包括：解析升级包数据、按序写分区镜像以及分区镜像校验。二进制升级完成后，第二设备的版本号将进行更新，更新完成后，第二设备升级成功。至此，完成升级。也即，该第二设备的修复完成。
可以理解的是，升级具体可以是指设备从一个版本升级到一个更高级的版本，例如从基础版本升级到更高的版本。本申请实施例中的系统修复可以是指设备从受损状态升级到正常状态，因此也可以称为升级。
应理解，图13所示的流程仅为第二设备进行系统修复的一种可能的实现方式，不应对本申请构成任何限定。在具体实现中，第二设备例如可以通过执行图13中部分或全部步骤来实现系统修复。第二设备也可以通过执行除图13所示之外的流程来实现系统修复。本申请对此不作限定。关于第二设备进行系统修复的具体过程可参看现有技术，为了简洁，此处不作详述。
另一种可能的情况是，第二设备无法进入修复模式。此情况下，第一设备在代理修复模式下对第二设备进行代理修复。
图14从设备角度的角度示出了第一设备代理修复第二设备的具体流程。如图14所示，响应于用户操作，第一设备开始执行如下步骤。
步骤1401，第一设备进入代理修复模式。
步骤1402，第一设备通过指令触发第二设备的AP进入强制加载模式。
示例性地，第一设备可通过用户界面向用户显示“代理修复”的按钮，用户可点击第一设备上的代理修复按钮来触发第二设备进入强制加载模式。第一设备响应于用户操作，进入代理修复模式后，可通过与第二设备之间的连接关系，向第二设备发送进入强制加载模式的指令。第二设备的AP可基于该指令进入强制加载模式。
步骤1403，第一设备解析升级包，强制加载修复最小系统镜像到第二设备。其中，修复最小系统可以是指能够支撑修复模式正常启动的镜像升级包，具体可以包括能够使修复模式得以运行的最基本的模块。换言之，第二设备可以基于该修复最小系统进入修复模式。示例性地，该修复最小系统例如可以包括但不限于，预加载程序(preloader)、快速启动模块、分区表(partition table，ptable)和修复模块等。
步骤1404，第一设备触发第二设备进入代理修复模式。
示例性地，第一设备解析完升级包后，可通过与第二设备之间的连接关系，向第二设备发送进入代理修复模式的指令，第二设备可基于该指令进入代理修复模式。
步骤1405，第二设备将升级包和鉴权文件写入数据块设备。第二设备可以从第一设备获取升级包和鉴权文件，然后写入数据块设备。
步骤1406，第二设备进入修复模式。应理解，第二设备进入修复模式所执行的操作可以参看上文结合图13的相关描述，或者也可参看现有技术中其他可用于实现系统修复的相关流程。为了简洁，此处不做赘述。
S305、第二设备检查数据分区是否完整。
第一设备可以在对第二设备完成代理修复后，第二设备检查修复后的第二设备的数据分区是否完整。应理解，在数据分区的头部设置有用于描述分区信息的数据，该分区信息例如可以是分区大小、起始地址、块数量等。第一设备完成对第二设备的代理修复后，第二设备的文件系统可以根据该分区信息读取该数据分区，若读取错误，则表示该数据分区受损，或者说，该数据分区不完整；若读取正常，则表示该数据分区完整且正确。
若第二设备的数据分区完整，则第二设备无需再从第一设备获取备份的用户数据。可选地，第二设备可以向第一设备发送第一消息，以通知第一设备备份的用户数据不需要归 还。第一设备基于此第一消息，可以清除本地保存的备份的用户数据。若第二设备的数据分区不完整，则可执行S306，第二设备可以通过与第一设备的交互，获取备份的用户数据。示例性地，第二设备可以向第一设备发送第二消息，以请求获取备份的用户数据，第一设备可以基于该第二消息，将备份的用户数据归还给第二设备。
可以理解，基于上述对用户数据的备份方式的不同，该备份数据可以是文件，例如图片、音乐、文档、视频等，也可以是二进制镜像。第一设备将备份的用户数据归还给第二设备也可以通过如下两种可能的方式来实现：
第一种可能的实现方式是，第一设备在代理修复模式下，将备份的文件拷贝到第二设备的数据分区，则完成用户数据的归还。
第二种可能的实现方式是，在代理修复模式下，第二设备将数据分区擦除，第一设备将备份的数据分区镜像加载到第二设备，第二设备启动单镜像升级，完成数据分区的还原。
应理解，上文所列举的第一消息和第二消息可以是同一消息，第一设备可通过不同的指示来确定是否需要归还备份的用户数据；第一消息和第二消息也可以是不同的消息，本申请实施例对此不作限定。
本申请实施例提供的数据备份方法，第一设备获取对待修复的第二设备的代理修复授权，基于该代理修复授权，无论第二设备是否可以开机，第一设备都可以访问第二设备的数据分区，从而可以对第二设备的数据分区中的用户数据进行备份。因此，可以降低修复场景下数据分区中用户数据丢失的概率；即便在数据分区损坏的情况下，也能够将未丢失的用户数据进行备份，减少用户数据的丢失。整体而言，可以减小用户损失。
可以理解，上文结合多个附图描述了本申请实施例提供的数据备份方法的具体流程，这些附图仅为示例，图中的每一个步骤并不一定是必须要执行的，例如有些步骤是可以跳过的。并且，各个步骤的执行顺序也不是固定不变的，也不限于图中所示，各个步骤的执行顺序应以其功能和内在逻辑确定。
还应理解，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本申请还提供一种电子设备，该电子设备可以包括：存储器和处理器。其中，存储器可用于存储计算机程序；处理器可用于调用所述存储器中的计算机程序，以使得所述电子设备执行图3所示实施例中第一设备执行的方法或第二设备执行的方法。
本申请还提供一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得电子设备执行图3所示实施例中第一设备执行的方法或第二设备执行的方法。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)。所述计算机程序被计算机或处理器执行时，使得电子设备执行图3所示实施例中第一设备执行的方法或第二设备执行的方法。
应理解，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。 在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本说明书中使用的术语“单元”、“模块”等，可用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。在本申请所提供的几个实施例中，应该理解到，所揭露的装置、设备和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
应理解，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (27)

  1. 一种数据备份方法，其特征在于，包括：
    第一设备获取对第二设备的代理修复授权，所述代理修复授权用于所述第一设备对所述第二设备进行代理修复，所述第二设备是待修复的设备，且所述第二设备无法开机；
    所述第一设备基于所述代理修复授权，对所述第二设备的数据分区中的用户数据进行备份；
    所述第一设备对所述第二设备进行代理修复。
  2. 如权利要求1所述的方法，其特征在于，所述第一设备获取对待修复的第二设备的代理修复授权，包括：
    所述第一设备基于与所述第二设备之间的信赖关系，获取对所述待修复的第二设备的代理修复授权。
  3. 如权利要求2所述的方法，其特征在于，所述信赖关系基于如下一项而建立：所述第二设备的授权信息、所述第二设备的开机密码，以及所述第一设备与所述第二设备的关联账号。
  4. 如权利要求1所述的方法，其特征在于，所述第一设备获取对待修复的第二设备的代理修复授权，包括：
    所述第一设备向第一服务器申请对所述第二设备的临时代理修复授权。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备响应于用户的输入操作，向所述第二设备发送所述第二设备的数据分区的访问请求，所述访问请求中携带访问密码，所述访问密码为所述用户输入的密码，用于访问所述第二设备的数据分区。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一设备基于所述代理修复授权，对所述第二设备的数据分区中的用户数据进行备份，包括：
    所述第一设备基于所述代理修复授权，从所述第二设备的数据分区拷贝数据文件，以对所述用户数据进行备份，所述数据文件中包含所述用户数据。
  7. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一设备基于所述代理修复授权，对所述第二设备的数据分区中的用户数据进行备份，包括：
    所述第一设备基于所述代理修复授权，拷贝所述第二设备的数据分区的二进制镜像，以对所述用户数据进行备份，所述二进制镜像包括所述第二设备的数据分区的完整原始二进制数据。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，所述第一设备对所述第二设备进行代理修复，包括：
    所述第一设备获取升级包，所述升级包用于所述第二设备的系统修复；
    所述第一设备向所述第二设备发送所述升级包；
    所述第一设备触发所述第二设备进入修复模式，所述升级包用于所述第二设备在所述修复模式下进行系统修复。
  9. 如权利要求1至7中任一项所述的方法，其特征在于，所述第一设备对所述第二设备进行代理修复，包括：
    所述第一设备获取升级包，所述升级包用于所述第二设备的系统修复；
    所述第一设备解析所述升级包，以获取修复最小系统；
    所述第一设备将所述修复最小系统镜像到所述第二设备；
    所述第一设备触发所述第二设备进入代理修复模式，所述修复最小系统用于所述第二设备在所述代理修复模式下进行系统修复。
  10. 如权利要求8或9所述的方法，其特征在于，所述第一设备获取升级包，包括：
    所述第一设备向第一服务器发送所述第一设备对所述第二设备的代理修复授权申请，以及所述第一设备的设备信息与所述第二设备的设备信息，所述设备信息包括版本标识和设备标识，以从所述第一服务器获取授权文件，所述授权文件用于指示所述第一设备对所述第二设备的代理修复授权；
    所述第一设备基于所述授权文件和所述第二设备的设备信息，从第二服务器获取版本文件列表；
    所述第一设备基于所述版本文件列表，从第三服务器下载升级包。
  11. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第一设备基于所述升级包，从所述第二服务器下载鉴权文件，所述鉴权文件用于在所述系统修复中对所述第二设备的鉴权。
  12. 一种数据备份方法，其特征在于，包括：
    第二设备的微控制单元MCU接收来自第一设备的访问请求，所述访问请求用于请求访问所述第二设备的数据分区，所述访问请求中携带访问密码；所述第二设备为待修复的设备，且所述第二设备无法开机；所述第一设备为用于对所述第二设备进行代理修复的设备；
    所述第二设备的MCU通过与所述第二设备的应用处理器AP之间的端口，请求读取预存在所述第二设备的安全分区中的密码；
    所述第二设备的MCU基于所述安全分区中的密码，对所述访问密码进行验证；
    所述第二设备的MCU在对所述访问密码验证成功的情况下，接受所述第一设备的访问请求。
  13. 一种电子设备，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    获取对第二设备的代理修复授权，所述代理修复授权用于所述电子设备对所述第二设备进行代理修复，所述第二设备是待修复的设备，且所述第二设备无法开机；
    基于所述代理修复授权，对所述第二设备的数据分区中的用户数据进行备份；
    对所述第二设备进行代理修复。
  14. 如权利要求13所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    基于与所述第二设备之间的信赖关系，获取对所述第二设备的代理修复授权。
  15. 如权利要求14所述的电子设备，其特征在于，所述信赖关系基于如下一项而建立：所述第二设备的授权信息、所述第二设备的开机密码，以及所述电子设备与所述第二设备的关联账号。
  16. 如权利要求13所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    向第一服务器申请对所述第二设备的临时代理修复授权。
  17. 如权利要求13至16中任一项所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    响应于用户的输入操作，所述电子设备向所述第二设备发送所述第二设备的数据分区的访问请求，所述访问请求中携带访问密码，所述访问密码为所述用户输入的密码，用于访问所述第二设备的数据分区。
  18. 如权利要求13至17中任一项所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    从所述第二设备的数据分区拷贝数据文件，以对所述用户数据进行备份，所述数据文件中包含所述用户数据。
  19. 如权利要求13至17中任一项所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    拷贝所述第二设备的数据分区的二进制镜像，以对所述用户数据进行备份，所述二进制镜像包括所述第二设备的数据分区的完整原始二进制数据。
  20. 如权利要求13至19中任一项所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    获取升级包，所述升级包用于所述第二设备的系统修复；
    向所述第二设备发送所述升级包；
    触发所述第二设备进入修复模式，所述升级包用于所述第二设备在所述修复模式下进行系统修复。
  21. 如权利要求13至19中任一项所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    获取升级包，所述升级包用于所述第二设备的系统修复；
    解析所述升级包，以获取修复最小系统；
    将所述修复最小系统镜像到所述第二设备；
    触发所述第二设备进入代理修复模式，所述修复最小系统用于所述第二设备在所述代理修复模式下进行系统修复。
  22. 如权利要求20或21所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    向第一服务器发送所述电子设备对所述第二设备的代理修复授权申请，以及所述电子设备的设备信息与所述第二设备的设备信息，所述设备信息包括版本标识和设备标识，以从所述第一服务器获取授权文件，所述授权文件用于指示所述电子设备对所述第二设备的代理修复授权；
    基于所述授权文件和所述第二设备的设备信息，从第二服务器获取版本文件列表；
    基于所述版本文件列表，从第三服务器下载升级包。
  23. 如权利要求20或21所述的电子设备，其特征在于，所述至少一个处理器用于执行计算机程序，使得所述电子设备执行如下操作：
    基于所述升级包，从所述第二服务器下载鉴权文件，所述鉴权文件用于在所述系统修复中对所述第二设备的鉴权。
  24. 一种电子设备，其特征在于，包括应用处理器AP和微控制单元MCU；所述MCU用于执行计算机程序，以执行如下操作：
    接收来自第一设备的访问请求，所述访问请求用于请求访问所述电子设备的数据分区，所述访问请求中携带访问密码；所述电子设备为待修复的设备，所述第一设备为用于对所述电子设备进行代理修复的设备；
    通过与所述AP之间的端口，请求读取预存在所述电子设备的安全分区中的密码；
    基于所述安全分区中的密码，对所述访问密码进行验证；
    在对所述访问密码验证成功的情况下，接受所述第一设备的访问请求。
  25. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时，使得电子设备执行如权利要求1至12中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被运行时，使得所述计算机执行如权利要求1至12中任一项所述的方法。
  27. 一种程序产品，其特征在于，所述程序产品包括计算机程序，所述计算机程序存储在可读存储介质中，通信装置的至少一个处理器可以从所述可读存储介质读取所述计算机程序，所述至少一个处理器执行所述计算机程序使得通信装置实施如权利要求1‐11任意一项所述的方法或者如权利要求12任意一项所述的方法。
PCT/CN2022/073137 2021-02-20 2022-01-21 一种数据备份方法和电子设备 WO2022174718A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110195341.9 2021-02-20
CN202110195341.9A CN114968657A (zh) 2021-02-20 2021-02-20 一种数据备份方法和电子设备

Publications (1)

Publication Number Publication Date
WO2022174718A1 true WO2022174718A1 (zh) 2022-08-25

Family

ID=82931192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/073137 WO2022174718A1 (zh) 2021-02-20 2022-01-21 一种数据备份方法和电子设备

Country Status (2)

Country Link
CN (1) CN114968657A (zh)
WO (1) WO2022174718A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117234811B (zh) * 2023-11-14 2024-02-20 苏州元脑智能科技有限公司 数据备份方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104199677A (zh) * 2014-07-25 2014-12-10 小米科技有限责任公司 刷机方法、装置及相应设备
CN106375350A (zh) * 2016-11-29 2017-02-01 北京小米移动软件有限公司 刷机验证方法和装置
CN106791124A (zh) * 2016-12-27 2017-05-31 北京奇虎科技有限公司 移动终端的刷机方法和刷机装置
CN106804035A (zh) * 2015-11-26 2017-06-06 东莞酷派软件技术有限公司 一种电子设备刷机控制方法及系统
US20180343309A1 (en) * 2017-05-23 2018-11-29 Bank Of America Corporation Migrating sessions using a private cloud - cloud technology

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104199677A (zh) * 2014-07-25 2014-12-10 小米科技有限责任公司 刷机方法、装置及相应设备
CN106804035A (zh) * 2015-11-26 2017-06-06 东莞酷派软件技术有限公司 一种电子设备刷机控制方法及系统
CN106375350A (zh) * 2016-11-29 2017-02-01 北京小米移动软件有限公司 刷机验证方法和装置
CN106791124A (zh) * 2016-12-27 2017-05-31 北京奇虎科技有限公司 移动终端的刷机方法和刷机装置
US20180343309A1 (en) * 2017-05-23 2018-11-29 Bank Of America Corporation Migrating sessions using a private cloud - cloud technology

Also Published As

Publication number Publication date
CN114968657A (zh) 2022-08-30

Similar Documents

Publication Publication Date Title
WO2021147745A1 (zh) 蓝牙连接方法、系统和电子设备
WO2020015259A1 (zh) 一种数据备份方法及终端
WO2020098664A1 (zh) 一种删除安全业务的方法及电子设备
WO2021104114A1 (zh) 一种提供无线保真WiFi网络接入服务的方法及电子设备
CN111373713B (zh) 一种消息传输方法及设备
CN113408016B (zh) 保存密文的方法和装置
WO2021093855A1 (zh) 一种移动设备管理方法及设备
WO2021104448A1 (zh) 一种密钥信息的同步方法、系统及设备
WO2021057982A1 (zh) 应用程序的处理方法及相关产品
WO2022143156A1 (zh) 一种加密通话方法、装置、终端及存储介质
WO2022111469A1 (zh) 一种文件共享方法、装置及电子设备
WO2022199673A1 (zh) 一种登录认证的方法和电子设备
WO2021143168A1 (zh) 可信执行环境操作系统崩溃处理方法及电子设备
WO2022166502A1 (zh) 数据保护方法、系统、介质及电子设备
WO2022174718A1 (zh) 一种数据备份方法和电子设备
WO2024037500A1 (zh) 通信方法及相关装置
RU2809740C2 (ru) Способ обработки файла, хранящегося во внешней памяти
WO2023207758A1 (zh) 数据处理方法及装置
WO2022188812A1 (zh) 设备之间同步软件特性的方法及电子设备
WO2021051964A1 (zh) 配对方法及设备
WO2024037040A1 (zh) 数据处理方法及电子设备
WO2023025059A1 (zh) 一种通信系统及通信方法
WO2024002137A1 (zh) 通信方法、通信系统及电子设备
CN115884140A (zh) 跨设备连接方法、电子设备及存储介质
CN118233118A (zh) 一种登录应用的方法及相关装置

Legal Events

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

Ref document number: 22755491

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22755491

Country of ref document: EP

Kind code of ref document: A1