Starting method of wearable device system

Abstract

The invention relates to the technical field of wearable device system operation, and discloses a starting method of a wearable device system. According to the method and the device, the back area for exception recovery and the update area for system upgrading are further divided in the wearable equipment system, so that the wearable equipment system can be automatically recovered when the starting exception occurs, normal starting of the wearable equipment system is ensured, free upgrading and updating of the wearable equipment system can be realized, and the user experience is improved. And the stability and the reliability of the wearable equipment system are effectively improved. Meanwhile, the system area is encrypted according to the chip ID of the wearable equipment system, and in the starting process of the wearable equipment system, it is ensured that only equipment passing matching verification can normally start the wearable equipment system, so that the safety and the anti-theft and anti-loss capacity of the wearable equipment system are effectively improved.

Description

Technical Field

[0001] The present invention relates to the technical field of wearable device system operation, and in particular to a method for starting a wearable device system. Background Art

[0002] The contents in this section merely provide background information related to the present invention and may not constitute prior art.

[0003] For wearable devices that use IoT embedded systems, during the long-term operation of the system, if the life of the internal storage partition of the chip expires, it will cause local probabilistic read and write anomalies, thereby affecting the reliability and stability of the system. However, the known wearable device system does not have an effective system backup and recovery mechanism, so that when an abnormality occurs in the internal storage partition of the chip, the system cannot be restored to a normal working state, resulting in the system being unable to start normally. Summary of the invention

[0004] In view of this, an object of the present invention is to provide a method for starting a wearable device system, in order to improve the stability and reliability of the wearable device system when starting.

[0005] The purpose of the present invention is achieved through the following technical solutions:

[0006] The present invention discloses a method for starting a wearable device system, wherein the wearable device system includes multiple partitions, including a trust area, a boot area, a system area, a back area, and an update area; the back area is a backup partition of the system area, and the update area is used to store upgrade update files;

[0007] The startup method comprises the following steps:

[0008] Step S1. Start the trust area and determine whether the boot area is available. If available, proceed to step S2.

[0009] Step S2. Start the boot area; the wearable device system determines whether to refresh the back area data within a predetermined delay judgment period, if so, proceed to step S3, if not, proceed to step S4;

[0010] Step S3. Write the data in the back area to the system area, clear the upgrade flag, and proceed to step S5;

[0011] Step S4. Determine whether the wearable device system needs to be upgraded; if so, read the upgrade file in the update area and write it to the system area to upgrade the wearable device system, and enter step S5 after the upgrade is completed; if not, directly enter step S5;

[0012] Step S5: Start the system area.

[0013] Furthermore, in step S5, starting the system area specifically includes:

[0014] Step S51. Before starting the system area, determine whether the wearable device system has been activated; if so, proceed to step S53; if not, proceed to step S52;

[0015] Step S52. Read the public key in the chip's internal storage address to match and verify the legitimacy of the public key; if the public key matches and is verified, read the chip ID, and derive the target private key corresponding to the public key according to the chip ID, and update and store the target private key to the location of the public key; then start the system area, or enter step S53;

[0016] Step S53: Read the chip ID of the current chip in the system when the wearable device system is turned on this time, and derive the current private key according to the chip ID of the current chip;

[0017] The pre-stored target private key is read, and the target private key is matched with the current private key; if the match is successful, the system area is started; if the match fails, the system area is not started.

[0018] Furthermore, in step S52 and step S53, before starting the system area, the process further includes:

[0019] Determine whether the system area is available; if the system area is available, jump to the system area and start the system area; if the system area is not available, set the wearable device system to enter a standby mode to wait for further operation by the user.

[0020] Furthermore, a flag for determining whether the boot area and the system area are available, a system startup flag for determining whether the wearable device system has been activated, the public key, and the target private key are all stored in the chip memory storage address.

[0021] Further, in step S52, after the target private key is updated and stored in the location of the public key, the system startup flag of the wearable device system is modified to an activated state.

[0022] Further, in step S2, it is determined whether the refreshing of the back area data is triggered by a button of the wearable device system.

[0023] Furthermore, after the wearable device system starts running, the upgrade program in the wearable device system downloads and updates the upgrade update files required for subsequent system upgrades to the update area, and then the wearable device system restarts.

[0024] Furthermore, the intervals between the start addresses of the system area, the back area, and the update area are larger than the volume occupied by the corresponding firmware image.

[0025] The technical solution of the embodiment of the present invention has at least the following advantages and beneficial effects:

[0026] 1. The startup method disclosed in the present invention further divides the wearable device system into a back area for abnormal recovery and an update area for system upgrade and update, so that the wearable device system can automatically recover when a startup abnormality occurs, thereby ensuring the normal startup of the wearable device system and realizing the free upgrade and update of the wearable device system, which effectively improves the stability and reliability of the wearable device system.

[0027] 2. The present invention realizes encryption of the system area according to the chip ID of the wearable device system. During the startup process of the wearable device system, it ensures that only devices that pass the matching verification can normally start the wearable device system, which effectively improves the security and anti-theft and anti-loss capabilities of the wearable device system. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic diagram of partitions of a wearable device system provided by an embodiment of the present invention;

[0029] Figure 2 A flowchart of a method for starting a wearable device system provided by an embodiment of the present invention;

[0030] Figure 3 A flowchart of starting a wearable device system provided by an embodiment of the present invention;

[0031] Figure 4 A flowchart of starting the system area provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described in conjunction with specific implementation methods below. The same figure marks in the accompanying drawings represent the same components. It should be noted that the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the described embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0033] Compared to the embodiments shown in the drawings, feasible embodiments within the scope of the present invention may have fewer components, other components not shown in the drawings, different components, differently arranged components, or differently connected components, etc. In addition, two or more components in the drawings may be implemented in a single component, or a single component shown in the drawings may be implemented as multiple separate components.

[0034] An embodiment of the present invention discloses a method for starting a wearable device system, which aims to provide an effective abnormal recovery and upgrade update mechanism for the wearable device system, thereby improving the stability and reliability of the wearable device system; at the same time, it is expected to improve the security and anti-theft and anti-loss capabilities of the wearable device system through an encryption mechanism.

[0035] In order to facilitate the description of the method disclosed in this embodiment, the partitions of the wearable device system in this embodiment are first introduced below. Among them, the partitions of the wearable device system are divided from the storage space of the wearable device system and are used to store corresponding image files.

[0036] like Figure 1 As shown, it shows a schematic diagram of the partitions of the wearable device system provided in this embodiment. Figure 1 In the wearable device system, the storage space is divided into six partitions, including trust area, boot area, system area, back area, update area and env area.

[0037] Among them, the trust area, boot area, system area, and env area are the partitions commonly possessed by wearable device systems known in the prior art. The cooperation of these four partitions is used to realize the basic startup function of the wearable device system.

[0038] Specifically, the trust area is the partition that is started first after the wearable device system is powered on. The trust partition is generally defined by the chip manufacturer (that is, the chip manufacturer) and can be used to store data that needs to be protected and has high security requirements, such as data related to the reliable startup of the chip, chip ID information, factory information, etc. Generally speaking, the trust area is controlled by the chip manufacturer, and user programs in the wearable device system do not involve modifications to the trust area. After the trust area is started, the system will jump to the boot area. Among them, the boot area is a partition that can control the jump, and the jump address of the boot can be set by the user. After the boot partition is started, the system will jump to the system area to start the wearable device system. The env area is used to store content such as configuration information and user settings required for system startup and operation.

[0039] On this basis, the wearable device system in this embodiment also provides a back area. The back area can be understood as a backup partition of the system area, that is, the back area stores image files that are substantially the same as the system area, so that the back area can complement the system area. When an abnormality occurs in the system area, the wearable device system can be started from the back area, or the image files stored in the back area can be copied to the system area to restore the system area, so that the wearable device system can still start normally when an abnormality occurs in the system area.

[0040] In addition, the wearable device system in this embodiment also provides an update area. The update area is used to store upgrade and update files related to system upgrade and update. During the boot phase of the wearable device system, if the system needs to be upgraded and updated, the boot area can control the upgrade and update files stored in the update area to be written to the system area to achieve system upgrade and update.

[0041] The determination of whether the system needs to be upgraded or updated can be made by the upgrade and update flag provided by the env area. Specifically, if the upgrade and update flag provided by the env area is 0, it means that the system does not need to be upgraded or updated; if the upgrade and update flag provided by the env area is 1, it means that the system needs to be upgraded or updated.

[0042] The boot method of the wearable device system disclosed in this embodiment will be described in detail below in conjunction with the accompanying drawings. The wearable device system includes the aforementioned multiple partitions, which are trust area, boot area, system area, back area, update area and env area.

[0043] Figure 2is a flowchart of a method for starting a wearable device system disclosed in this embodiment. Figure 3 FIG. 1 is a flowchart of starting the wearable device system disclosed in this embodiment. Figure 2 and Figure 3 As shown, the startup method disclosed in this embodiment may include the following steps:

[0044] Step S1. After the wearable device system is powered on, the trust area is started first. When the trust area is activated, it will detect whether the system version program of the wearable device system matches the chip. If it matches, the trust area reads the internal storage address flag of the chip to determine whether the boot area is available; if the boot area is available, it jumps directly to the boot area and enters step S2; if the boot area is not available, the wearable device system fails to start.

[0045] Step S2. Start the boot area. After starting the boot area, the wearable device system determines whether it is necessary to refresh the back area data within a predetermined delay judgment period, that is, whether it is necessary to copy the image file stored in the back area to the system area. If so, go to step S3, if not, go to step S4.

[0046] Among them, the predetermined delay judgment period can be set as needed, for example, the predetermined delay judgment period can be 3s. At the same time, the judgment of whether the back area data needs to be refreshed can be triggered by the button of the wearable device system. For example, whether the button of the wearable device system is pressed continuously for a predetermined number of times (for example, 3 times) can be used as a condition for judging whether the back area data needs to be refreshed. For example, within the predetermined delay judgment period, if the number of times the button of the wearable device is pressed continuously reaches the predetermined number of times, it means that the back area data needs to be refreshed; conversely, within the predetermined delay judgment period, if the number of times the button of the wearable device is pressed continuously does not reach the predetermined number of times, it means that the back area data does not need to be refreshed.

[0047] Step S3. The data in the back area is written to the system area through the boot area, that is, the image file stored in the back area is read through the boot area and written to the system area; at the same time, the upgrade and update flag provided by the env area can be cleared, that is, the upgrade and update flag provided by the env area is set to 0, and then step S5 is entered.

[0048] It is worth noting that, if it is determined in step S2 that the back area data needs to be flushed within the predetermined delay judgment period, it means that there may be an abnormality in the system area and the wearable device system cannot be started normally. By reading the image file stored in the back area and flushing it back to the system area, the abnormality in the system area can be repaired. Correspondingly, clearing the upgrade and update flag provided by the env area indicates that the system does not need to be upgraded and updated at this time, and can directly enter the system area to start the system.

[0049] Step S4. Determine whether the wearable device system needs to be upgraded or updated based on the upgrade flag provided by the env area; if so, the boot area reads the upgrade file stored in the update area and writes it to the system area to upgrade the wearable device system, and enters step S5 after the upgrade is completed; if not, directly enter step S5.

[0050] Step S5: Start the system area to start the wearable device system.

[0051] It can be seen that the method provided in this embodiment, by further dividing the wearable device system into a back area for abnormal recovery and an update area for system upgrade and update, enables the wearable device system to automatically recover when a startup abnormality occurs, thereby ensuring the normal startup of the wearable device system and realizing the free upgrade and update of the wearable device system, effectively improving the stability and reliability of the wearable device system.

[0052] Further, see Figure 4 As shown, in step S5, starting the system area specifically includes:

[0053] Step S51. Before starting the system area, determine whether the wearable device system has been activated; if so, proceed to step S53; if not, proceed to step S52.

[0054] Among them, judging whether the wearable device system has been activated can be understood as judging whether the wearable device system is started for the first time. Specifically, if the wearable device system is started for the first time, the wearable device system will be in an inactive state, and conversely, if the wearable device system is not started for the first time, the wearable device system will be in an activated state.

[0055] Among them, to determine whether the wearable device system has been activated, the system startup flag in the chip internal storage address can be read through the boot area, and the wearable device system can be determined based on the obtained system startup flag. For example, if the system startup flag read from the boot area is 0, it means that the wearable device system is not activated; conversely, if the system startup flag read from the boot area is 1, it means that the wearable device system is activated.

[0056] Step S52. The boot area reads the public key in the internal storage address of the chip to match and verify the legitimacy of the public key; if the public key matching verification is passed, the boot area reads the chip ID, and derives the target private key corresponding to the public key based on the chip ID, and updates the target private key to the location of the public key; then the system area can be directly started to start the wearable device system, or enter step S53.

[0057] Among them, after the target private key is updated and stored in the public key location, the system startup flag of the wearable device system should also be changed to an activated state, for example, the system startup flag is changed from 0 to 1.

[0058] Step S53. The boot area reads the chip ID of the current chip in the system when the wearable device system is turned on this time, and derives the current private key according to the chip ID of the current chip;

[0059] On this basis, the boot area reads the pre-stored target private key (that is, the target private key derived in step S52), and matches the target private key with the current private key; if the match is successful, it means that the current chip matches the wearable device system, and then the system area is started to start the wearable device system; if the match fails, it means that the current chip does not match the wearable device system, and the wearable device system may be in a stolen state. At this time, the system area is not started, and the wearable device system fails to start.

[0060] It can be understood that through the above operations, the system area is encrypted according to the chip ID of the wearable device system. During the startup process of the wearable device system, it is ensured that only devices that have passed the matching verification can start the wearable device system normally, which effectively improves the security of the wearable device system and its anti-theft and anti-loss capabilities.

[0061] Furthermore, in step S52 and step S53, before starting the system area, it also includes: determining whether the system area is available; if the system area is available, jumping to the system area and starting the system area; if the system area is not available, the wearable device system fails to start, and the wearable device system is set in the boot area to enter standby mode to wait for further user operations.

[0062] Furthermore, the flag used to determine whether the boot area and the system area are available, the system startup flag used to determine whether the wearable device system has been activated, the public key, the target private key, etc. can all be stored in the chip memory storage address, such as in the env area.

[0063] Furthermore, after the wearable device system starts and runs normally, the upgrade program in the wearable device system can download and update the upgrade files (including new firmware and / or user programs) required for subsequent system upgrades to the update area. Moreover, after the upgrade program downloads and updates the upgrade files to the update area, the wearable device system will restart to facilitate the wearable device system to perform upgrade and update operations in a timely manner.

[0064] Furthermore, the boot partition, system area and back area can be partitions that are directly burned before leaving the factory. In addition, the back area cannot be modified by default to ensure that the wearable device system has a reliable recovery point when a problem occurs.

[0065] Further, see Figure 1 As shown, the starting address of the boot area can be at the front of the chip memory at 0x8000000, the starting address of the system area can be at 0x8020000, the starting address of the back area can be at 0x8060000, the starting address of the update area can be at 0x80a0000, and the starting address of the env area can be at 0x80e0000. Among them, the interval between the starting addresses of the system area, the back area, and the update area should be larger than the volume occupied by the corresponding firmware image (that is, the image file that the corresponding partition needs to store) to ensure that each partition can successfully store the corresponding image file.

[0066] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for starting a wearable device system, characterized in that: The wearable device system includes multiple partitions, including a trust area, a boot area, a system area, a back area, and an update area; the back area is a backup partition of the system area, and the update area is used to store upgrade update files; The startup method comprises the following steps: Step S1. Start the trust area and determine whether the boot area is available. If available, proceed to step S2. Step S2. Start the boot area; the wearable device system determines whether to refresh the back area data within a predetermined delay judgment period, if so, proceed to step S3, if not, proceed to step S4; Step S3. Write the data in the back area to the system area, clear the upgrade flag, and proceed to step S5; Step S4. Determine whether the wearable device system needs to be upgraded; if so, read the upgrade file in the update area and write it to the system area to upgrade the wearable device system, and enter step S5 after the upgrade is completed; if not, directly enter step S5; Step S5: Start the system area.

2. The method for starting a wearable device system according to claim 1, characterized in that: In step S5, starting the system area specifically includes: Step S51. Before starting the system area, determine whether the wearable device system has been activated; if so, proceed to step S53; if not, proceed to step S52; Step S52. Read the public key in the chip's internal storage address to match and verify the legitimacy of the public key; if the public key matches and is verified, read the chip ID, and derive the target private key corresponding to the public key according to the chip ID, and update and store the target private key to the location of the public key; then start the system area, or enter step S53; Step S53: Read the chip ID of the current chip in the system when the wearable device system is turned on this time, and derive the current private key according to the chip ID of the current chip; The pre-stored target private key is read, and the target private key is matched with the current private key; if the match is successful, the system area is started; if the match fails, the system area is not started.

3. The method for starting a wearable device system according to claim 2, characterized in that: In step S52 and step S53, before starting the system area, the process further includes: Determine whether the system area is available; if the system area is available, jump to the system area and start the system area; if the system area is not available, set the wearable device system to enter a standby mode to wait for further operation by the user.

4. The method for starting a wearable device system according to claim 2, characterized in that: A flag for determining whether the boot area and the system area are available, a system startup flag for determining whether the wearable device system has been activated, the public key, and the target private key are all stored in the chip memory storage address.

5. The method for starting a wearable device system according to claim 2, characterized in that: In step S52, after the target private key is updated and stored in the location of the public key, the system startup flag of the wearable device system is modified to an activated state.

6. The method for starting a wearable device system according to claim 1, characterized in that: In step S2, it is determined whether the refreshing of the back area data is triggered by a button of the wearable device system.

7. The method for starting a wearable device system according to claim 1, characterized in that: After the wearable device system starts running, the upgrade program in the wearable device system downloads and updates the upgrade and update files required for subsequent system upgrades to the update area, and then the wearable device system restarts.

8. The method for starting a wearable device system according to claim 1, characterized in that: The intervals between the start addresses of the system area, the back area, and the update area are larger than the volume occupied by the corresponding firmware image.

Images