Application protection method, device and wearable device

Abstract

The present disclosure relates to an application protection method, device and wearable device, wherein the method comprises: in the case that an application is downloaded to a wearable device for the first time, writing the application to an application area and a backup area respectively for the first time; in the case that the wearable device is powered on or reset, checking whether the application in the application area is valid, in the case that the application in the application area is invalid, writing the application in the backup area to the application area and covering the original application in the application area; and periodically checking whether the application in the backup area is valid, in the case that the application in the backup area is invalid and the application in the application area is valid, writing the application in the application area to the backup area and covering the original application in the backup area.

Description

Technical Field

[0001] This disclosure relates to application protection technology, and more specifically, to an application protection method, apparatus, and wearable device. Background Technology

[0002] Wearable devices are emerging electronic devices, such as smart rings. Due to their small size and lack of physical external interfaces, OTA (Over-The-Air) updates have become a key method for application updates and maintenance.

[0003] When an application is tampered with, such as by abnormally erasing the application, it may cause the device to fail to start or malfunction in OTA (Over-The-Air) functionality. Summary of the Invention

[0004] One objective of this invention is to provide a new technical solution for application protection methods.

[0005] According to a first aspect of the present invention, an application protection method is provided, comprising:

[0006] When the application is first downloaded to the wearable device, the application is written to both the application area and the backup area for the first time.

[0007] When the wearable device is powered on or reset, check if the applications in the application area are valid. If the applications in the application area are invalid, write the applications from the backup area to the application area, overwriting the original applications in the application area; and,

[0008] Periodically check whether the applications in the backup area are valid. If the applications in the backup area are invalid and the applications in the application area are valid, write the applications in the application area to the backup area and overwrite the original applications in the backup area.

[0009] Optionally, the method further includes:

[0010] In the case of upgrading the application via OTA, the latest version of the application is written to the backup area and overwrites the original application in the backup area;

[0011] If the application in the application area is determined to be valid, the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area. At the same time, the application in the application area is written to the backup area and overwrites the latest version of the application in the backup area.

[0012] Optionally, the method further includes:

[0013] If an application in the application area is determined to be invalid, the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, while the latest version of the application in the backup area is retained.

[0014] Optionally, writing the applications from the backup area to the application area and overwriting the original applications in the application area includes:

[0015] The bootloader is used to write the applications from the backup area into the application area and overwrite the original applications in the application area.

[0016] Optionally, the bootloader is configured with write-lock permissions.

[0017] Optionally, after the application is first written to the application area, after the application in the backup area is written to the application area and overwrites the original application in the application area, and after the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, the method further includes:

[0018] Write lock permissions are set for the application area.

[0019] Optionally, checking whether the application in the application area is valid includes:

[0020] The CRC algorithm is used to determine the actual checksum corresponding to the application in the application area;

[0021] Obtain the current version information of the applications in the application area, the correspondence between the pre-stored version information and the verification value;

[0022] Based on the current version information of the applications in the application area and the correspondence between the pre-stored version information and the verification value, the pre-stored verification value corresponding to the application in the application area is determined.

[0023] The validity of an application in the application area is determined based on the actual verification value corresponding to the application in the application area and the pre-stored verification value corresponding to the application in the application area.

[0024] Optionally, the periodic check of whether the application in the backup area is valid includes:

[0025] The CRC algorithm is used to determine the actual checksum corresponding to the application in the backup area;

[0026] Obtain the current version information of the applications in the backup area, the correspondence between the pre-stored version information and the verification value;

[0027] Based on the current version information of the applications in the backup area, the correspondence between the pre-stored version information and the verification value, the pre-stored verification value corresponding to the applications in the backup area is determined.

[0028] The validity of the application in the backup area is determined based on the actual verification value corresponding to the application in the backup area and the pre-stored verification value corresponding to the application in the backup area.

[0029] According to a second aspect of the present invention, an application protection device is provided, comprising:

[0030] The application writing module is used to write the application to the application area and the backup area respectively when the application is first downloaded to the wearable device;

[0031] The first checking and writing module is used to check whether the applications in the application area are valid when the wearable device is powered on or reset; if the applications in the application area are invalid, the applications in the backup area are written to the application area, overwriting the original applications in the application area; and,

[0032] The second checking and writing module is used to periodically check whether the applications in the backup area are valid. If the applications in the backup area are invalid and the applications in the application area are valid, the applications in the application area are written to the backup area, overwriting the original applications in the backup area.

[0033] According to a third aspect of the present invention, a wearable device is provided, including a memory and a processor, the memory storing a computer program for controlling the processor to operate in order to perform the method according to any one of the first aspects.

[0034] This disclosure provides an application protection method. When an application is first downloaded to a wearable device, it is initially written to both the application area and the backup area. If the application in the application area is invalid, the application in the backup area is written to the application area, overwriting the original application. This ensures that if the application in the application area malfunctions, a version rollback can be performed, guaranteeing the normal operation of the application. Additionally, the validity of the application in the backup area is periodically checked, acting as a safeguard for the applications in the backup area. If the application in the backup area is invalid while the application in the application area is valid, the application in the application area is written to the backup area, overwriting the original application. This ensures that the application in the backup area is valid, and when the application in the application area becomes invalid, a valid version can be provided to the application area.

[0035] The features and advantages of the embodiments of this specification will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of this specification and, together with their description, serve to explain the principles of these embodiments.

[0037] Figure 1 This is a flowchart illustrating an application protection method according to an embodiment of the present invention.

[0038] Figure 2 This is a schematic diagram of a storage area according to an embodiment of the present invention.

[0039] Figure 3 This is a schematic diagram of an application protection method according to an embodiment of the present invention.

[0040] Figure 4 This is a schematic diagram of an application protection method according to an embodiment of the present invention.

[0041] Figure 5 This is a schematic block diagram of an application protection device according to an embodiment of the present invention.

[0042] Figure 6 This is a schematic diagram of the structure of a wearable device according to an embodiment of the present invention. Detailed Implementation

[0043] Various exemplary embodiments of this specification will now be described in detail with reference to the accompanying drawings.

[0044] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the embodiments of this specification or their application or use.

[0045] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0046] To address the aforementioned technical problems, this disclosure provides an application protection method. When an application is first downloaded to a wearable device, it is initially written to both the application area and the backup area. If the application in the application area is invalid, the application in the backup area is written to the application area, overwriting the original application. This ensures that if the application in the application area malfunctions, a version rollback can be performed, guaranteeing the normal operation of the application. Furthermore, the validity of the application in the backup area is periodically checked, acting as a safeguard for the applications in the backup area. If the application in the backup area is invalid while the application in the application area is valid, the application in the application area is written to the backup area, overwriting the original application. This ensures that the application in the backup area is valid, and when the application in the application area becomes invalid, a valid version can be provided to the application area.

[0047] In one embodiment of the present invention, an application protection method is provided. Figure 1 As shown, the application protection method of this embodiment includes the following steps S110 to S130.

[0048] Step S110: When the application is downloaded to the wearable device for the first time, the application is written to the application area and the backup area for the first time.

[0049] Applications written to the application area and applications written to the backup area are both valid applications.

[0050] When the application runs, the application in the application area is executed.

[0051] Step S120: When the wearable device is powered on or reset, check whether the applications in the application area are valid. If the applications in the application area are invalid, write the applications in the backup area into the application area and overwrite the original applications in the application area.

[0052] In some embodiments, checking whether an application in the application area is valid specifically includes: using a CRC algorithm to determine the actual checksum corresponding to the application in the application area; obtaining the current version information of the application in the application area, the correspondence between the pre-stored version information and the checksum; determining the pre-stored checksum corresponding to the application in the application area based on the current version information of the application in the application area, the correspondence between the pre-stored version information and the checksum; and determining whether the application in the application area is valid based on the actual checksum corresponding to the application in the application area and the pre-stored checksum corresponding to the application in the application area.

[0053] The CRC (Cyclic Redundancy Check) algorithm can be either CRC-16 or CRC-32. This algorithm is used to detect whether an application has encountered errors or been tampered with. Specifically, using either the CRC-16 or CRC-32 algorithm, a polynomial division operation is performed on the application to generate a fixed-length checksum, which serves as the actual check value for the application.

[0054] The application's pre-stored checksum is based on the CRC algorithm and is determined according to the corresponding version of the application.

[0055] If the actual verification value corresponding to an application in the application area matches the pre-stored verification value, the application in the application area is considered valid. If the actual verification value corresponding to an application in the application area does not match the pre-stored verification value, the application in the application area is considered invalid, indicating a potential risk of tampering.

[0056] If an application in the application area is invalid, the application in the backup area is written to the application area and overwrites the original application in the application area. This ensures that if the application in the application area is abnormal, version rollback can be performed to ensure the normal operation of the application.

[0057] In some embodiments, a bootloader is used to write applications from the backup area to the application area and overwrite the original applications in the application area.

[0058] The bootloader is a program used to guide the installation or updating of applications.

[0059] In this embodiment, the bootloader is configured with write-lock permissions. This prevents the bootloader from being tampered with, thereby avoiding the inability to perform the transfer operation of writing the application from the backup area to the application area after an application upgrade based on OTA due to bootloader tampering.

[0060] Step S130: Periodically check whether the applications in the backup area are valid. If the applications in the backup area are invalid and the applications in the application area are valid, write the applications in the application area to the backup area and overwrite the original applications in the backup area.

[0061] In some embodiments, the CRC algorithm is used to determine the actual checksum corresponding to the application in the backup area; the current version information of the application in the backup area, the correspondence between the pre-stored version information and the checksum are obtained; the pre-stored checksum corresponding to the application in the backup area is determined based on the current version information of the application in the backup area, the correspondence between the pre-stored version information and the checksum; and the validity of the application in the backup area is determined based on the actual checksum corresponding to the application in the backup area and the pre-stored checksum corresponding to the application in the backup area.

[0062] If the actual checksum of the application in the backup area matches the pre-stored checksum, the application in the backup area is considered valid. If the actual checksum of the application in the backup area does not match the pre-stored checksum, the application in the backup area is considered invalid, indicating a potential risk of tampering.

[0063] The system periodically checks the validity of applications in the backup area, acting as a safeguard for these applications. If an application in the backup area is invalid while the application in the application area is valid, the application in the application area is written to the backup area, overwriting the original application in the backup area. This ensures that the application in the backup area is valid, and when an application in the application area becomes invalid, a valid version can be provided to the application area.

[0064] In some embodiments, the method further includes: when upgrading an application based on OTA, writing the latest version of the application to the backup area and overwriting the original application in the backup area; when it is determined that the application in the application area is valid, writing the latest version of the application in the backup area to the application area and overwriting the original application in the application area, while simultaneously writing the application in the application area to the backup area and overwriting the latest version of the application in the backup area.

[0065] When upgrading applications via OTA, if the application in the application area is confirmed to be valid, the latest version of the application in the backup area is swapped with the original application in the application area. This achieves the upgrade of the application in the application area, and ensures that the application in the backup area is valid after the swap, so that a valid version can be provided to the application area when the application in the application area is invalid.

[0066] In this embodiment, the method further includes: if it is determined that the application in the application area is invalid, writing the latest version of the application in the backup area into the application area and overwriting the original application in the application area, while retaining the latest version of the application in the backup area.

[0067] When upgrading applications via OTA, if an application in the application zone is determined to be invalid, the latest version of the application in the backup zone is swapped with the original application in the application zone. This achieves the upgrade of the application in the application zone, and because the application in the application zone is invalid, the application in the application zone is no longer written to the backup zone and overwritten with the latest version of the application in the backup zone. Instead, the latest version of the application in the backup zone is retained, ensuring that the application in the backup zone is valid. When an application in the application zone is invalid, a valid version can be provided to the application zone.

[0068] In some embodiments, after the application is first written to the application area, after the application in the backup area is written to the application area and overwrites the original application in the application area, and after the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, the method further includes setting write locking permissions for the application area. This prevents the application in the application area from being tampered with.

[0069] When writing to the application area is required, unlock the write access to the application area to allow write operations. After the write operation to the application area is completed, re-lock the write access to the application area.

[0070] Figure 2 A schematic diagram of a storage area according to an embodiment of the present invention is shown. Figure 2 As shown, the storage area is divided into a bootloader storage partition, an app storage partition, and an mcuboot_secodary storage partition. The bootloader storage partition stores the bootloader program. The app storage partition is the application area involved in any of the above embodiments. The mcuboot_secodary storage partition is the backup area involved in any of the above embodiments.

[0071] Combination Figure 2 As shown, the application protection method provided by the present invention will be described below with two specific embodiments.

[0072] One embodiment of the application protection method includes the following steps S301 to S305.

[0073] Step S301: When the application is downloaded to the wearable device for the first time, the application is written to the app storage partition and the mcuboot_secodary storage partition for the first time.

[0074] Step S302: After completing the first write to the app storage partition, set write lock permissions for the app storage partition.

[0075] Step S303: When the wearable device is powered on or reset, check whether the application in the app storage partition is valid. If it is invalid, unlock the write lock permission of the app storage partition, and then write the application in the mcuboot_secodary storage partition to the app storage partition and overwrite the original application in the app storage partition.

[0076] Step S304: After completing the rewriting of the app storage partition, set write lock permissions for the app storage partition.

[0077] Step S305: Periodically check whether the application in the mcuboot_secodary storage partition is valid. If the application in the mcuboot_secodary storage partition is invalid and the application in the application area is valid, write the application in the app storage partition to the mcuboot_secodary storage partition and overwrite the original application in the mcuboot_secodary storage partition.

[0078] Another embodiment of the application protection method includes the following steps S401 to S404.

[0079] Step S401: When the application is downloaded to the wearable device for the first time, the application is written to the app storage partition and the mcuboot_secodary storage partition for the first time.

[0080] Step S402: After completing the first write to the app storage partition, set write lock permissions for the app storage partition.

[0081] Step S403: In the case of upgrading the application based on OTA, the latest version of the application is written to the mcuboot_secodary storage partition and overwrites the original application in the mcuboot_secodary storage partition.

[0082] Step S404: If the application in the app storage partition is determined to be valid, unlock the write lock permission of the app storage partition, then write the latest version of the application in the mcuboot_secodary storage partition to the app storage partition and overwrite the original application in the app storage partition. At the same time, write the application in the app storage partition to the mcuboot_secodary storage partition and overwrite the latest version of the application in the mcuboot_secodary storage partition.

[0083] Step S405: If it is determined that the application in the app storage partition is invalid, the write lock permission of the app storage partition is unlocked, and then the latest version of the application in the mcuboot_secodary storage partition is written to the app storage partition and overwrites the original application in the app storage partition, while retaining the latest version of the application in the mcuboot_secodary storage partition.

[0084] An embodiment of the present invention also provides an application protection device. According to... Figure 5 As shown, the application protection device 500 includes an application writing module 510, a first checking and writing module 520, and a second checking and writing module 530.

[0085] The application writing module 510 is used to write the application to the application area and the backup area for the first time when the application is first downloaded to the wearable device.

[0086] The first checking and writing module 520 is used to check whether the application in the application area is valid when the wearable device is powered on or reset. If the application in the application area is invalid, the application in the backup area is written to the application area and the original application in the application area is overwritten.

[0087] The second checking and writing module 530 is used to periodically check whether the application in the backup area is valid. If the application in the backup area is invalid and the application in the application area is valid, the application in the application area is written to the backup area and the original application in the backup area is overwritten.

[0088] In some embodiments, the application protection device 500 further includes an upgrade writing module. The upgrade writing module is used to write the latest version of the application to the backup area and overwrite the original application in the backup area when the application is upgraded via OTA; and when the application in the application area is determined to be valid, to write the latest version of the application in the backup area to the application area and overwrite the original application in the application area, while simultaneously writing the application in the application area to the backup area and overwriting the latest version of the application in the backup area.

[0089] In this embodiment, the upgrade writing module is also used to write the latest version of the application from the backup area to the application area and overwrite the original application in the application area when it is determined that the application in the application area is invalid, while retaining the latest version of the application in the backup area.

[0090] In some embodiments, the first checking and writing module 520 is further configured to use the bootloader to write the application in the backup area to the application area and overwrite the original application in the application area.

[0091] The bootloader is configured with write-lock permissions.

[0092] In some embodiments, after the application is first written to the application area, after the application in the backup area is written to the application area and overwrites the original application in the application area, and after the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, the device further includes a permission setting module. The permission setting module is used to set write locking permissions for the application area.

[0093] In some embodiments, the first checking and writing module 520 is used to determine the actual check value corresponding to the application in the application area using the CRC algorithm; obtain the current version information of the application in the application area, the correspondence between the pre-stored version information and the check value; determine the pre-stored check value corresponding to the application in the application area based on the current version information of the application in the application area, the correspondence between the pre-stored version information and the check value; and determine whether the application in the application area is valid based on the actual check value corresponding to the application in the application area and the pre-stored check value corresponding to the application in the application area.

[0094] In some embodiments, the second checking and writing module 530 is further configured to use a CRC algorithm to determine the actual checksum corresponding to the application in the backup area; obtain the current version information of the application in the backup area, the correspondence between the pre-stored version information and the checksum; determine the pre-stored checksum corresponding to the application in the backup area based on the current version information of the application in the backup area, the correspondence between the pre-stored version information and the checksum; and determine whether the application in the backup area is valid based on the actual checksum corresponding to the application in the backup area and the pre-stored checksum corresponding to the application in the backup area.

[0095] An embodiment of the present invention also provides a wearable device, such as Figure 6 As shown. Wearable device 600 includes memory 620 and processor 610. Memory 620 stores computer programs for controlling processor 610 to operate and execute the application protection method provided according to any of the above embodiments.

[0096] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

[0097] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0098] Embodiments of this specification may be systems, methods, and / or computer program products. A computer program product may include a computer-readable storage medium having computer instructions stored thereon for causing a processor to implement various aspects of the embodiments of this specification.

[0099] Computer-readable storage media can be tangible devices capable of holding and storing computer instructions for use by computer instruction execution devices. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing computer instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0100] The computer instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper cables, fiber optic cables, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer instructions from the network and forwards them to computer-readable storage media within the respective computing / processing device.

[0101] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this specification. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of computer instructions, which contains one or more executable computer instructions for implementing a specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation using a combination of software and hardware are equivalent.

[0102] Various embodiments of this specification have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. An application protection method, characterized in that, include: When the application is first downloaded to the wearable device, the application is written to both the application area and the backup area for the first time. When the wearable device is powered on or reset, check whether the applications in the application area are valid. If the applications in the application area are invalid, write the applications in the backup area into the application area and overwrite the original applications in the application area. as well as, Periodically check whether the applications in the backup area are valid. If the applications in the backup area are invalid and the applications in the application area are valid, write the applications in the application area to the backup area and overwrite the original applications in the backup area to protect the applications in the backup area and ensure that the applications in the backup area are valid. The method further includes: In the case of upgrading the application via OTA, the latest version of the application is written to the backup area and overwrites the original application in the backup area; If the application in the application area is determined to be valid, the latest version of the application in the backup area is swapped with the original application in the application area. The latest version of the application in the backup area is written into the application area and overwrites the original application in the application area. At the same time, the application in the application area is written into the backup area and overwrites the latest version of the application in the backup area. If an application in the application area is determined to be invalid, the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, while the latest version of the application in the backup area is retained.

2. The method according to claim 1, characterized in that, The step of writing the application from the backup area to the application area and overwriting the original application in the application area includes: The bootloader is used to write the applications from the backup area into the application area and overwrite the original applications in the application area.

3. The method according to claim 2, characterized in that, The bootloader is configured with write-lock permissions.

4. The method according to claim 1, characterized in that, After the application is first written to the application area, after the application in the backup area is written to the application area and overwrites the original application in the application area, and after the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, the method further includes: Write lock permissions are set for the application area.

5. The method according to any one of claims 1-4, characterized in that, The step of checking whether the application in the application area is valid includes: The CRC algorithm is used to determine the actual checksum corresponding to the application in the application area; Obtain the current version information of the applications in the application area, the correspondence between the pre-stored version information and the verification value; Based on the current version information of the applications in the application area and the correspondence between the pre-stored version information and the verification value, the pre-stored verification value corresponding to the application in the application area is determined. The validity of an application in the application area is determined based on the actual verification value corresponding to the application in the application area and the pre-stored verification value corresponding to the application in the application area.

6. The method according to any one of claims 1-4, characterized in that, The periodic check of whether the applications in the backup area are valid includes: The CRC algorithm is used to determine the actual checksum corresponding to the application in the backup area; Obtain the current version information of the applications in the backup area, the correspondence between the pre-stored version information and the verification value; Based on the current version information of the applications in the backup area, the correspondence between the pre-stored version information and the verification value, the pre-stored verification value corresponding to the applications in the backup area is determined. The validity of the application in the backup area is determined based on the actual verification value corresponding to the application in the backup area and the pre-stored verification value corresponding to the application in the backup area.

7. An application protection device, characterized in that, include: The application writing module is used to write the application to the application area and the backup area respectively when the application is first downloaded to the wearable device; The first checking and writing module is used to check whether the application in the application area is valid when the wearable device is powered on or reset. If the application in the application area is invalid, the application in the backup area is written to the application area and the original application in the application area is overwritten. as well as, The second checking and writing module is used to periodically check whether the applications in the backup area are valid. If the applications in the backup area are invalid and the applications in the application area are valid, the applications in the application area are written to the backup area and the original applications in the backup area are overwritten, so as to protect the applications in the backup area and ensure that the applications in the backup area are valid. The application protection device also includes an upgrade writing module, which is used to write the latest version of the application to the backup area and overwrite the original application in the backup area when the application is upgraded based on OTA; when the application in the application area is determined to be valid, the latest version of the application in the backup area is exchanged with the original application in the application area, the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, and at the same time the application in the application area is written to the backup area and overwrites the latest version of the application in the backup area. If an application in the application area is determined to be invalid, the latest version of the application in the backup area is written to the application area and overwrites the original application in the application area, while the latest version of the application in the backup area is retained.

8. A wearable device, characterized in that, It includes a memory and a processor, the memory storing a computer program for controlling the processor to operate in order to perform the method according to any one of claims 1 to 6.

Images