Data display method, wearable device and electronic device

Abstract

The embodiment of the invention discloses a data display method, wearable equipment and electronic equipment, which can realize data interaction and data fusion between the wearable equipment and the electronic equipment, so that data displayed by the wearable equipment and the electronic equipment are consistent, and the accuracy of data display is improved. The method comprises the steps that the wearable device updates local data stored in a local data file based on collected motion incremental data; under the condition that a data acquisition instruction from the electronic equipment is received, feeding back the updated local data to the electronic equipment; under the condition that fusion data from the electronic equipment is received, the fusion data are displayed on a motion data interface of the wearable equipment, and the fusion data are obtained by the electronic equipment based on the updated local data and the obtained operation data.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a data display method, wearable device, and electronic device. Background Technology

[0002] With the increasing popularity of wearable devices, more and more users are inclined to leverage the connections between wearable devices (e.g., smartwatches) and electronic devices (e.g., smartphones, PCs) to obtain relevant data in different application scenarios. For example, users can use the connection between a smartwatch and a smartphone to obtain activity data (including activity calories, exercise duration, and activity hours) in a sports scenario. However, in practical applications, since an electronic device can typically be connected to multiple wearable devices, the data displayed by the electronic device is a fusion of data uploaded from multiple wearable devices. The data displayed by the wearable device, on the other hand, only reflects the locally acquired data, leading to inconsistencies between the data displayed by the electronic device and the wearable device. Summary of the Invention

[0003] This application provides a data display method, a wearable device, and an electronic device. Through data interaction and data fusion between the wearable device and the electronic device, the data displayed by the wearable device and the electronic device can be made consistent, thereby improving the accuracy of the displayed data.

[0004] Firstly, embodiments of this application provide a data display method applicable to wearable devices. The method includes: updating initial local data stored in a local data file to first local data based on collected incremental motion data; sending the first local data to an electronic device in response to a data acquisition command from the electronic device; receiving second fused data from the electronic device, the second fused data being obtained based on the first local data and motion data acquired by the electronic device; and displaying the second fused data on a first motion data interface. As can be seen, in this technical solution, the wearable device can interact with the electronic device, sending local data to the electronic device and receiving and displaying the second fused data sent by the electronic device, thereby achieving consistency between the data displayed by the wearable device and the electronic device and improving the accuracy of the displayed data.

[0005] In conjunction with the first aspect, in one possible approach, the above method further includes: updating the initial fused data stored in the fused data file to the first fused data based on the collected incremental motion data. It is evident that in wearable devices, local data and fused data are stored separately, and the wearable device can use incremental motion data to update the initial fused data, ensuring the accuracy of the fused data determined by the wearable device.

[0006] In conjunction with the first aspect, in one possible approach, the method further includes updating the fused data stored in the fused data file from the first fused data to the second fused data. Therefore, by using the received second fused data to update the fused data file, the wearable device ensures the accuracy of the fused data stored in the fused data file within the wearable device, thus improving the user experience.

[0007] In conjunction with the first aspect, in one possible approach, based on the collected incremental motion data, the initial local data stored in the local data file is updated to first local data. This includes: in response to the collected incremental motion data being greater than or equal to a storage threshold, updating the initial local data stored in the local data file to first local data; wherein, the first local data is the sum of the collected incremental motion data and the initial local data. It is evident that when the collected incremental motion data is greater than or equal to the storage threshold, the wearable device updates the local data stored in the local data file, which ensures the accuracy of the local data stored in the local data file and reduces resource consumption caused by frequent reading and writing of data files.

[0008] In conjunction with the first aspect, in one possible approach, the method further includes: displaying first fused data on a first motion data interface in response to the collected motion increment data being greater than or equal to a display threshold; wherein the first fused data is the sum of the collected motion increment data and the initial fused data. It is evident that when the collected motion increment data is greater than or equal to the display threshold, the wearable device can display the first fused data, allowing users to obtain the fused data in a timely manner, which improves the user experience. Simultaneously, it can reduce resource consumption caused by frequent updates of the fused data displayed in the first motion data interface.

[0009] In conjunction with the first aspect, in one possible approach, displaying the second fused data on the first motion data interface includes: displaying the second fused data on the first motion data interface in response to the second fused data being greater than the first fused data. In this way, the wearable device can display larger fused data on the first motion data interface, making the displayed fused data more accurate and improving the user experience.

[0010] Secondly, embodiments of this application provide another data display method applicable to electronic devices. This method includes: a wearable device sending a data acquisition instruction to acquire local data from the wearable device; receiving first local data from the wearable device; determining second fused data based on the first local data and the acquired motion data; sending the second fused data to the wearable device; and displaying the second fused data on a second motion data interface. As can be seen, the electronic device can perform data fusion based on the local data sent by the wearable device, determine the second fused data, and send the second fused data to the wearable device, ensuring consistency between the data displayed by the electronic device and the wearable device, thus guaranteeing the accuracy of the displayed data.

[0011] In conjunction with the second aspect, in one possible approach, the acquired motion data includes motion data collected by an electronic device and / or motion data received from a target device, which is a device other than the electronic device and the wearable device; the second fused data is the sum of the first local data and the acquired motion data. It is evident that the electronic device can be associated with multiple devices and perform data fusion based on the motion data sent by multiple devices, thereby obtaining more accurate fused data and improving the user experience.

[0012] Thirdly, this application provides a wearable device comprising: one or more processors, a display screen, and a memory; the memory is coupled to the one or more processors and is used to store computer program code including computer instructions, wherein the one or more processors invoke the computer instructions to cause the wearable device to perform the method described in the first aspect above.

[0013] Fourthly, this application provides an electronic device comprising: one or more processors, a display screen, and a memory; the memory is coupled to the one or more processors and is used to store computer program code including computer instructions, wherein the one or more processors invoke the computer instructions to cause the electronic device to perform the method described in the second aspect above.

[0014] Fifthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect above, or implements the method described in the second aspect above.

[0015] In a sixth aspect, this application provides a chip system coupled to a memory, the chip system being used to read and execute a computer program stored in the memory to implement the method described in the first aspect above, or to implement the method described in the second aspect above.

[0016] In a seventh aspect, this application provides a computer program product containing instructions that, when the computer program product is run on an electronic device, cause the electronic device to perform the method described in the first aspect, or to implement the method described in the second aspect above. Attached Figure Description

[0017] Figure 1A and Figure 1B This is a schematic diagram of a motion three-ring data display method provided in an embodiment of this application;

[0018] Figures 2A-2E This is a schematic diagram of a data display method in a motion scene provided in an embodiment of this application;

[0019] Figure 3 A flowchart illustrating a data display method provided in an embodiment of this application;

[0020] Figure 4 A flowchart illustrating another data display method provided in this application embodiment;

[0021] Figure 5 A flowchart illustrating yet another data display method provided in this application embodiment;

[0022] Figure 6 This is a schematic diagram of the software structure of a wearable device provided in an embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the hardware result of a wearable device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0025] The terms "first," "second," "third," etc., used in the embodiments of this application are to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, it may include a series of steps or units, or optionally, steps or units not listed, or other steps or units inherent to these processes, methods, products, or devices. The terms "one embodiment" or "some embodiments," etc., mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of the embodiments of this application, do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0026] In the embodiments of this application, the words "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.

[0027] Furthermore, "at least one" refers to one or more, while "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0028] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0029] Another term in the following embodiments of this application, "three-ring motion data," refers to data acquired by the electronic device during user activity to reflect the user's activity status. Three-ring motion data may include activity calorie data, exercise duration data, and activity hours; activity calorie data refers to the number of calories burned during activity, exercise duration refers to the time the user spends engaging in moderate to high-intensity exercise, and activity hours refer to the number of hours the user is active each day, reflecting the frequency and duration of the user's daily activities.

[0030] Devices used to display motion tri-ring data can include electronic devices and wearable devices. Electronic devices can be smartphones, personal computers, etc., while wearable devices are wearable smart devices such as smartwatches and smart bracelets. When displaying motion tri-ring data, wearable devices typically display the collected motion tri-ring data on their user interface, while electronic devices can acquire motion tri-ring data from one or more related wearable devices and comprehensively determine the motion tri-ring data displayed by the electronic device based on the acquired data. For an example, please refer to [link to example]. Figure 1A and Figure 1B , Figure 1A and Figure 1B This is a schematic diagram of a motion three-ring data display method provided in an embodiment of this application. Figure 1A As shown, the wearable device is a smartwatch, and the activity calorie data displayed by this wearable device is 50 kcal. Figure 1B As shown, the electronic device is a smartphone, and the activity calorie data displayed on the three-ring exercise data device is 60 kcal. Therefore, it can be concluded that the activity three-ring exercise data displayed by the wearable device and the electronic device are inconsistent.

[0031] Based on this, the data display method provided in this application can be applied to scenarios where the user interface displayed on different devices (such as smartphones and smartwatches) contains motion tri-ring data. The data display method provided in this application ensures that the motion tri-ring data displayed on different devices is consistent, improving the accuracy of the displayed data and making it easier for users to obtain accurate motion tri-ring data.

[0032] In this embodiment, smartphones, smartwatches, and other electronic devices or wearable devices can provide a "motion detection" function. This "motion detection" function can be used to acquire various physiological data and location information of the user during their daily activities, thereby determining the user's various movement data.

[0033] It is understood that "exercise detection" can also be referred to as "exercise health", "health detection", "exercise health monitoring" or other terms, and this application embodiment does not limit this.

[0034] The following uses activity calorie data from the three-ring exercise data as an example to illustrate the application scenarios of this application.

[0035] like Figure 2A As shown, when the wearable device is powered on or the "motion detection" function in the wearable device is activated, the wearable device can obtain the initial fusion data stored in the fusion data file and display the initial fusion data on the first motion data interface of the wearable device (e.g., Figure 2A As shown, the initial fusion data was 0 kcal.

[0036] like Figure 2B As shown, the wearable device can obtain initial local data from a local data file and initial fused data from a fused data file. Based on the device's acquisition frequency, the wearable device periodically collects incremental motion data (e.g., once per second) based on the user's behavior. After each collection of incremental motion data, the wearable device uses the collected incremental motion data to cumulatively update the initial local data and also uses the collected incremental motion data to cumulatively update the initial fused data.

[0037] For example: the initial local data is 0 kcal, the initial fused data is 0 kcal, and the first collected motion increment data is 10 kcal. The wearable device adds the first collected motion increment data to the initial local data to obtain updated local data of 10 kcal, and adds the first collected motion increment data to the initial fused data to obtain updated fused data of 10 kcal. The second collected motion increment data is 5 kcal. The wearable device uses the second collected motion increment data to update the updated local data a second time, obtaining updated local data of 15 kcal; it also uses the second collected motion increment data to update the updated fused data a second time, obtaining updated fused data of 15 kcal. This process continues, collecting N motion increment data, and then using the collected motion increment data to cumulatively update the initial local data and initial fused data N times to obtain updated local data and updated fused data. All the updated local data, updated fused data, and each collected motion increment data involved in the above process are stored in the wearable device's memory.

[0038] When the collected motion increment data (which can be the motion increment data from a single collection or the sum of N collected motion increment data) is greater than or equal to the storage threshold, such as Figure 2B As shown, the wearable device can add the collected incremental motion data to the initial local data to obtain the first local data (or directly use the updated local data as the first local data), and update the initial local data stored in the local data file to the first local data. Similarly, the wearable device can add the collected incremental motion data to the initial fused data to obtain the first fused data (or directly use the updated fused data as the first fused data), and update the initial fused data stored in the fused data file to the first fused data. Based on the storage threshold, timely updates to the corresponding data files according to the local data and fused data can free up memory resources, improve the operating speed of the wearable device, and ensure the accuracy of the local data sent by the wearable device to the electronic device during data synchronization.

[0039] like Figure 2CAs shown, when the collected incremental motion data is greater than or equal to the display threshold, the wearable device can display the first fused data on the first motion data interface. When the display threshold is 1 kcal, the first fused data will be displayed on the first motion data interface when a single collected incremental motion data is greater than or equal to the display threshold, or when the sum of multiple collected incremental motion data is greater than or equal to the display threshold. This means that for every 1 kcal increase in calorie expenditure, the wearable device's display interface will show the fused data after the increase in calorie expenditure. In this way, the wearable device can fuse data immediately without waiting to synchronize with the electronic device, which helps users understand changes in motion data in a timely manner and improves the user experience.

[0040] After updating the local data stored in the local data file and the fused data stored in the fused data file (or after displaying the fused data on the first motion data interface), the wearable device can retrieve local data from the local data file again, retrieve fused data from the fused data file, and continue to periodically collect motion data increments, using the collected motion data increments to update the local data and fused data.

[0041] When the wearable device and the electronic device synchronize data, the electronic device can send a data acquisition command to the wearable device based on the data synchronization frequency (e.g., once per minute). The wearable device responds to the data acquisition command, acquires local data stored in a local data file, and sends this local data to the electronic device. The electronic device adds the local data sent by the wearable device to the motion data acquired by the electronic device to obtain second fused data. The motion data acquired by the electronic device includes motion data collected by the electronic device and / or motion data received by the electronic device from other devices. The electronic device sends the second fused data to the wearable device, and the electronic device can also display the second fused data on the second motion data interface. After receiving the second fused data from the electronic device, the wearable device displays the second fused data on the first motion interface. After the wearable device sends the first local data (35 kcal) to the electronic device, the electronic device determines the second fused data (50 kcal) based on the first local data and the acquired motion data (15 kcal). The electronic device can display the second fused data, such as... Figure 2D The electronic device sends the second fused data to the wearable device, which can also display the second fused data, such as... Figure 2E In this way, the fused data displayed by the electronic device is consistent with the second fused data displayed by the wearable device. After receiving the second fused data, the wearable device can also update the fused data stored in the fused data file with the second fused data, so that the wearable device can subsequently update the fused data stored in the fused data file based on the collected incremental motion data.

[0042] In this application, the wearable device stores a local data file and a fused data file, and updates the data in these two files using incremental motion data. When the wearable device synchronizes with an electronic device, the wearable device only sends the local data stored in the local data file to the electronic device, and stores the fused data sent by the electronic device in the fused data file. This achieves isolation between the wearable device's local data and fused data, avoiding data errors caused by the wearable device reporting fused data from the fused data file during subsequent data synchronization. For example, during the first data synchronization, the local data stored in the wearable device's local data file is 100, and the fused data stored in the fused data file is also 100. The wearable device sends the local data to the electronic device so that the electronic device can perform data fusion. The wearable device receives second fused data from the electronic device, which is 120. The wearable device displays this second fused data and updates the fused data stored in the fused data file to the second fused data (i.e., 120). During the second data synchronization, the local data stored in the wearable device's local data file is 150 (i.e., 100+50), and the fused data stored in the fused data file is 170 (i.e., 120+50). At this time, the wearable device sends the local data to the electronic device instead of the fused data, so that the electronic device can achieve correct data fusion. The wearable device receives the new second fused data from the electronic device, which is 190 (i.e., 150+40). The wearable device displays the new second fused data and updates the fused data stored in the fused data file to the new second fused data.

[0043] Figures 2A-2E An exemplary data display method for electronic devices and wearable devices is illustrated. The wearable device can collect incremental motion data and use this data to update local data in a local data file and fused data in a fused data file. During synchronization with the electronic device, the wearable device sends local data stored in its local data file to the electronic device and receives and displays the second fused data sent by the electronic device. This allows the electronic device to transmit the fused data to the wearable device without affecting the data reported by the wearable device to the electronic device, ensuring consistency between the fused data displayed by the electronic device and the wearable device. This improves the accuracy of the displayed data and enhances the user experience.

[0044] In one embodiment, when the wearable device and the electronic device synchronize data, a data transmission anomaly may occur (i.e., the wearable device fails to respond to the electronic device's data acquisition command and sends local data to the electronic device). In this case, the electronic device determines the second fused data based solely on the acquired motion data and sends it to the wearable device. When this happens, neither the first nor the second fused data stored in the wearable device's fused data file accurately represents the actual activity calorie data (actual activity calorie data = wearable device's local data + motion data acquired by the electronic device), and the second fused data may be less than or equal to the first fused data. Therefore, to ensure that the data displayed on the first motion data interface of the wearable device closely matches the actual activity calorie data in the event of an anomaly, the wearable device can compare the first and second fused data after receiving the second fused data. If the second fused data is greater than the first fused data, the second fused data is displayed on the first motion data interface of the wearable device; if the first fused data is greater than or equal to the second fused data, the first fused data is displayed on the first motion data interface of the wearable device. This method ensures that the data displayed by wearable devices and electronic devices are consistent under normal circumstances, which helps improve the accuracy of the displayed data. It also helps to make the data displayed by wearable devices as close as possible to the real data in the event of anomalies, which helps to reduce the decline in user experience caused by anomalies.

[0045] Based on the user interface and method described above, the data display method provided in the embodiments of this application is described below. Please refer to... Figure 3 , Figure 3 This is a flowchart illustrating a data display method provided in an embodiment of this application. This method can be applied to wearable devices and may include, but is not limited to, the following steps:

[0046] S301 periodically collects incremental motion data.

[0047] In this embodiment, the wearable device is equipped with various types of sensors to collect various types of sensor data, enabling the wearable device to perform "motion detection." When the wearable device is powered on or the "motion detection" function is activated, the wearable device can periodically determine incremental motion data based on the collection frequency and various types of sensor data. This incremental motion data can be used to generate motion three-ring data.

[0048] S302, based on the collected incremental motion data, periodically updates the initial local data stored in the local data file.

[0049] In this embodiment, the wearable device includes a local data file storing initial local data. During the periodic collection of incremental motion data, the collected incremental motion data is stored in the wearable device's memory. The wearable device can periodically accumulate and update the initial local data using each collected incremental motion data.

[0050] The wearable device may include a local data processing flow (executed by the local data processing module in the wearable device) and a fusion data processing flow (executed by the fusion data processing module in the wearable device). After the initial local data is updated by accumulating the collected motion increment data in the local data processing flow, the local data processing module can send the collected motion increment data to the fusion data processing module so that the fusion data processing module can execute the following step S303.

[0051] S303, based on the collected incremental motion data, periodically updates the initial fusion data stored in the fusion data file.

[0052] In this embodiment, the wearable device includes a fusion data file, which stores initial fusion data. The wearable device can periodically collect incremental motion data. When the fusion data processing module in the wearable device receives the collected incremental motion data, it can periodically accumulate and update the initial fusion data stored in the fusion data file using the collected incremental motion data.

[0053] S304, in response to the collected motion increment data being greater than or equal to the storage threshold, update the initial local data stored in the local data file to the first local data.

[0054] In this embodiment, when the incremental motion data collected in one instance (or the sum of multiple incremental motion data collected) is greater than or equal to the storage threshold, the wearable device can update the initial local data stored in the local data file with first local data, which is the sum of the collected incremental motion data and the initial local data. After updating the local data file, the local data stored in the wearable device's memory can be deleted, thereby freeing up device memory and improving the operating efficiency of the wearable device. At the same time, saving only after the storage condition is met (i.e., the collected incremental motion data is greater than or equal to the storage threshold) can reduce the resource consumption caused by frequent reading and writing of data files. In addition, timely updating the local data file according to the incremental motion data also helps to ensure the accuracy of the local data subsequently sent by the wearable device to the electronic device.

[0055] After the local data processing module updates the local data in the local data file to the first local data, the local data processing module can send a notification message to the fusion processing module so that the fusion data processing module can perform the following step S305.

[0056] In one embodiment, after updating the local data stored in the local data file to the first local data, the wearable device can continue to periodically collect motion increment data. When the newly collected motion increment data is greater than or equal to the motion threshold, the wearable device can update the first local data stored in the local data file to the sum of the first local data and the newly collected motion increment data.

[0057] S305, based on the collected incremental motion data, update the initial fusion data stored in the fusion data file to the first fusion data.

[0058] In this embodiment, when the fusion data processing module receives a notification from the local data processing module, it can update the initial fusion data stored in the fusion data file with first fusion data based on the collected motion increment data. The first fusion data is the sum of the collected motion increment data and the initial fusion data. This method allows for updating the fusion data stored in the fusion data file using motion increment data, resulting in more accurate updated fusion data.

[0059] In one embodiment, the data display method provided in this application further includes: displaying first fused data on a first motion data interface in response to the collected motion increment data being greater than or equal to a display threshold, wherein the first fused data is the sum of the collected motion increment data and the initial fused data. Since the frequency of data synchronization between wearable devices and electronic devices is low, while the frequency of wearable devices collecting motion increment data and updating data files is high, in order to ensure that users are promptly informed of changes in the three-ring motion data, the wearable device can display the first fused data on the first motion data interface in response to the collected motion increment data being greater than or equal to a display threshold. Both the display threshold and the aforementioned saving threshold can be adaptively adjusted according to different application scenarios and application requirements, and the values ​​of the display threshold and the saving threshold are not directly related. In some cases, when the saving threshold is greater than the display threshold, in response to the collected motion increment data being greater than or equal to the display threshold, the wearable device displays the sum of the initial fused data and the collected motion increment data on the first motion data interface. This method allows users to obtain fused data in a timely manner and understand the changes in the three motion rings data, which helps improve the user experience. At the same time, displaying data only after the display condition is met (i.e., the collected incremental motion data is greater than or equal to the display threshold) can also reduce the resource consumption caused by frequently updating the fused data displayed in the first motion data interface.

[0060] S306, in response to a data acquisition command from an electronic device, the first local data is sent to the electronic device.

[0061] In this embodiment, the wearable device can communicate with an electronic device and receive data acquisition instructions from the electronic device. In response to the data acquisition instructions, the wearable device can acquire first local data from a local data file and send the first local data to the electronic device, enabling the electronic device to perform data fusion using the first local data.

[0062] S307, Receive second fusion data from the electronic device.

[0063] In this embodiment of the application, the wearable device can receive second fused data from the electronic device. This second fused data is obtained based on the first local data and the motion data acquired by the electronic device, and has good accuracy.

[0064] S308, update the fusion data stored in the fusion data file from the first fusion data to the second fusion data.

[0065] In this embodiment, the wearable device can update the fused data stored in the fused data file from the first fused data to the second fused data, so that when the wearable device updates the fused data stored in the fused data file according to the newly collected motion increment data, it can obtain more accurate data.

[0066] S309, the second fused data is displayed on the first motion data interface.

[0067] In this embodiment, the wearable device can display the second fused data on the first motion data interface, and the electronic device can also display the second fused data, thereby making the data displayed by the electronic device and the wearable device consistent, which helps to improve the accuracy of the displayed data.

[0068] In one embodiment, the specific implementation of displaying the second fused data on the first motion data interface can be as follows: In response to the second fused data being greater than the first fused data, the second fused data is displayed on the first motion data interface. Under normal circumstances, the second fused data is the sum of the first local data and the motion data acquired by the electronic device; the first fused data is the sum of the initial fused data and the collected incremental motion data; and the first local data is the sum of the initial local data and the collected incremental motion data. Since the initial fused data and the initial local data are usually the same, it can be determined that the second fused data is usually greater than the first fused data. Displaying the second fused data on the first motion data interface in response to the second fused data being greater than the first fused data ensures consistency between the data displayed by the electronic device and the wearable device, guaranteeing the accuracy of the displayed data.

[0069] In abnormal situations (i.e., the wearable device does not respond to the data acquisition command and send local data to the electronic device, and the electronic device only determines the second fused data based on the motion data acquired by the electronic device), the actual data is the sum of the motion data acquired by the electronic device and the first local data. The second fused data is the motion data acquired by the electronic device, and the first fused data is the sum of the initial fused data and the collected incremental motion data. This means that both the second fused data determined by the electronic device and the first fused data stored in the wearable device are inaccurate, and the second fused data may be less than or equal to the first fused data. In this case, to ensure that the data displayed on the first motion data interface by the wearable device has a smaller discrepancy with the actual data, the first fused data can be displayed on the first motion data interface if the first fused data is greater than or equal to the second fused data. This method can ensure the consistency and accuracy of the data displayed by the electronic device and the wearable device under normal circumstances, and ensure that the data displayed by the wearable device has a smaller discrepancy with the actual data under abnormal circumstances, thus improving the user experience.

[0070] In one embodiment, excessively long data transmission and fusion times during data synchronization may result in the first fused data being greater than or equal to the second fused data. Specifically, the wearable device sends first local data to an electronic device, which then fuses the first local data with acquired motion data to obtain second fused data. During data transmission and fusion, the wearable device continues to periodically collect incremental motion data and uses this data to update the local data stored in the local data file and the fused data stored in the fused data file. If the data transmission and fusion take a long time, and the incremental motion data collected by the wearable device continues to increase, the second fused data may be less than or equal to the fused data stored in the fused data file when the wearable device receives it. In this case, neither the second fused data nor the fused data stored in the fused data file accurately represents the actual data. Therefore, to ensure that the data displayed by the wearable device is close to the actual data, the wearable device can display the larger of the second fused data and the fused data stored in the fused data file.

[0071] Please see Figure 4 , Figure 4 This application provides a flowchart illustrating another data display method, which can be applied to electronic devices and may include, but is not limited to, the following steps:

[0072] S401, Send a data acquisition instruction to the wearable device, the data acquisition instruction being used to acquire local data from the wearable device.

[0073] In this embodiment, the electronic device can be associated with one or more wearable devices. The electronic device is also equipped with various sensors for collecting various types of sensor data. The electronic device can also generate motion data based on this sensor data. The electronic device can send a data acquisition command to the wearable device associated with it based on a data synchronization frequency. This data acquisition command is used to acquire local data from the wearable device.

[0074] S402, Receive first local data from the wearable device.

[0075] In this embodiment of the application, the electronic device can receive first local data from the wearable device, which is determined by the wearable device based on the collected incremental motion data.

[0076] S403, based on the first local data and the acquired motion data, determine the second fused data.

[0077] In this embodiment, the electronic device can determine the second fused data based on the first local data and the acquired motion data. The acquired motion data has the same data type as the first local data; for example, if the first local data is activity calorie data, then the acquired motion data is also activity calorie data.

[0078] Optionally, the acquired motion data includes motion data collected by an electronic device and / or motion data received from a target device, where the target device is a device other than the electronic device and the wearable device. The second fused data is the sum of the first local data and the acquired motion data. The motion data collected by the electronic device can be collected by the electronic device according to its configured sensors, and the target device can be other smart devices associated with the electronic device. It should be noted that the process shown in steps S301-S309 above can also be performed in the target device, thereby making the data displayed by the electronic device, the target device, and the wearable device consistent.

[0079] S404, send the second fused data to the wearable device and display the second fused data on the second motion data interface.

[0080] In this embodiment of the application, after the electronic device determines the second fused data, it can send the second fused data to the wearable device and display the second fused data on the second motion data interface, thereby making the data displayed by the electronic device and the wearable device consistent.

[0081] Next, the data display method provided in this application will be introduced in conjunction with the internal modules of electronic devices and the interaction between the internal modules of wearable devices. For example... Figure 5 As shown, the steps may include, but are not limited to, the following:

[0082] S501 receives the command to enable the motion detection function.

[0083] The command to activate the motion detection function can be automatically generated by the wearable device when it is powered on, or it can be initiated by the user for a motion detection application. This activation command can be a voice command or a gesture. A voice command could be, for example, "Activate motion detection function," while a gesture could be, for example, clicking the icon of the motion detection application on the wearable device's home screen.

[0084] S502, in response to the start command, updates the initial local data stored in the local data file based on the collected incremental motion data.

[0085] In response to the start command, the device periodically collects incremental motion data based on the acquisition frequency. The local data processing module periodically updates the initial local data stored in the local data file based on the collected incremental motion data.

[0086] S503, the local data processing module sends the incremental motion data after cumulative update to the fusion data processing module.

[0087] The local data processing module can periodically send the collected incremental motion data to the fusion data processing module so as to update the fusion data stored in the fusion data file.

[0088] S504, based on the collected incremental motion data, the fusion data processing module updates the initial fusion data stored in the fusion data file.

[0089] The fusion data processing module accumulates and updates the initial fusion data based on the collected incremental motion data.

[0090] S505, in response to the collected motion increment data being greater than or equal to the storage threshold, the local data processing module updates the initial local data stored in the local data file to the first local data.

[0091] Here, the local data processing module stores the first local data in a local data file and deletes the initial local data stored in the memory of the transmittable device. The first local data is the sum of the acquired motion increment data and the initial local data.

[0092] S506, the local data processing module sends a notification message to the fused data processing module.

[0093] The local data processing module sends a notification message to the fused data processing module to enable the fused data processing module to update the fused data file.

[0094] S507, in response to the collected motion increment data being greater than or equal to the storage threshold, the fusion data processing module updates the initial fusion data stored in the fusion data file to the first fusion data.

[0095] The fusion data processing module stores the first fused data in a fused data file and deletes the initial fused data stored in the memory of the transmittable device. The first fused data is the sum of the initial fused data and the acquired motion increment data.

[0096] S508, in response to the collected motion increment data being greater than or equal to the display threshold, the fusion data processing module sends the first fusion data to the first display module.

[0097] When the collected motion increment data is greater than or equal to the display threshold, the fusion data processing module sends the first fusion data to the first display module and deletes the motion increment data stored in the memory of the transmittable device.

[0098] S509, the first display module displays the first fused data on the first motion data interface.

[0099] The first display module displays the first fused data on the first motion data interface.

[0100] S510, the second transmission module sends a data acquisition command to the first transmission module of the wearable device.

[0101] The data acquisition command sent by the second transmission module of the electronic device is used to acquire local data stored in the wearable device.

[0102] S511, in response to the data acquisition command, the first transmission module sends the first local data to the second transmission module.

[0103] The first transmission module of the wearable device obtains first local data from a local data file and sends the first local data to the second transmission module.

[0104] S512, the second transmission module sends the first local data to the data fusion module.

[0105] The second transmission module transmits the first local data to the data fusion module through its internal transmission channel for data fusion.

[0106] S513, the data fusion module of the electronic device determines the second fused data based on the first local data and the motion data acquired by the electronic device.

[0107] The second fused data determined by the data fusion module is the sum of the first local data and the motion data acquired by the electronic device. The motion data acquired by the electronic device includes motion data collected by the electronic device and / or motion data received from devices other than the electronic device and wearable device.

[0108] S514, the second display module of the electronic device displays the second fused data.

[0109] The data fusion module can send the second fused data to the second display module, which then displays the second fused data on the second motion data interface, so that the data displayed by subsequent electronic devices and wearable devices are consistent.

[0110] S515, the second transmission module sends the second fused data to the first transmission module.

[0111] The fusion data module sends the second fused data to the second transmission module. The second transmission module then sends the determined second fused data to the first transmission module of the wearable device.

[0112] S516, in response to the second fused data being greater than the first fused data, the fused data processing module updates the fused data stored in the fused data file to the second fused data.

[0113] Here, in response to the second fused data being greater than the first fused data, the fused data processing module updates the fused data stored in the fused data file from the first fused data to the second fused data, so that the wearable device can subsequently update the fused data based on the newly collected motion increment data.

[0114] Optionally, in response to the second fused data being less than or equal to the first fused data (which typically occurs when a data transmission anomaly occurs), the fused data processing module updates the fused data stored in the fused data file to the first fused data.

[0115] S517, the first display module displays the second fused data.

[0116] The first display module of the wearable device displays the second fused data, thereby making the data displayed by the electronic device and the wearable device consistent, which helps to improve the accuracy of the displayed data and also enhances the user experience.

[0117] The following is combined Figure 6 The provided software system architecture summarizes the process of displaying the above data.

[0118] like Figure 6 As shown, the layered architecture of wearable devices can be divided into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system, from top to bottom, consists of the application layer, framework layer, algorithm layer, and kernel layer, etc.

[0119] The application layer can include a series of application packages, which may include third-party JS applications (e.g., navigation applications, music applications, travel applications, etc.), communication applications (e.g., messaging, calling, contacts, etc.), system applications (e.g., compass, weather, alarm clock, watch, voice, etc.), interconnectivity applications (e.g., remote camera control, scene intelligence, etc.), health applications (e.g., heart rate monitoring, sleep monitoring, blood oxygen saturation, etc.), sports applications (e.g., professional sports, training status, activity records), device management applications (e.g., over-the-air (OTA) upgrades, power on / off, factory reset, etc.), and wallet applications (e.g., payment applications, access cards, public transport cards, etc.).

[0120] The framework layer can provide application programming interfaces (APIs), programming frameworks, and some application-related service capabilities for applications in the application layer.

[0121] The framework layer may include the ACE UI framework (a user interface development framework) for implementing the display engine of wearable devices. The framework layer also includes basic system capabilities (e.g., communication services, audio services), underlying software service capabilities (e.g., basic services (log services, file systems, etc.), and the functions of the DFX framework (data acquisition, simulation services, etc.)), sports and health service capabilities (e.g., sports services, heart health, etc.), hardware service capabilities (e.g., location services, NFC services, Bluetooth services, etc.), and communication service capabilities (e.g., emergency calls, data services, eSIM management, etc.).

[0122] When implementing the data display method provided in this application, wearable devices primarily utilize the file system, memory management, and communication service capabilities of the framework layer. Specifically, the wearable device can obtain local data files and fused data files from the file system and collect incremental motion data using sensors involved in the kernel layer. Based on the collected incremental motion data, the initial local data stored in the local data file is updated to first local data, and the initial fused data stored in the fused data file is updated to first fused data. The wearable device can also utilize the communication service capabilities in the framework layer to conduct two-device communication with an electronic device. The wearable device receives data acquisition instructions from the electronic device and sends the first local data to the electronic device through a two-device communication channel. The wearable device receives the second fused data sent by the electronic device through the two-device communication channel and displays the second fused data in the motion application of the application layer. The method provided in this application can effectively ensure the consistency of the data displayed by the wearable device and the electronic device, and can also improve the accuracy of the data displayed by different devices.

[0123] The algorithm layer includes algorithm libraries that implement service capabilities (such as liveness detection algorithms, sleep algorithms, motion algorithms, etc.), basic libraries (such as barcodes, secure storage, basic C libraries, etc.), and communication protocol stacks (such as traditional Bluetooth protocol stacks, HTTP / HTTPS protocol stacks, TCP / IP protocol stacks, etc.).

[0124] The kernel layer is the layer between hardware and software. It contains at least the operating system kernel, various drivers, and the Hardware Abstraction Layer (HAL). Located between the operating system and the hardware, the HAL abstracts the hardware, which can include buttons, NFC, various sensors (e.g., gyroscopes, magnetometers, barometers), virtual network cards, etc.

[0125] like Figure 6As shown in this embodiment, the electronic device may primarily include a sports and health application (e.g., an eSIM management application, a contact synchronization application, a device management application, etc.), Bluetooth, and an audio codec (used to implement communication functions such as device discovery and virtual linking). The sports and health application can interact with the Bluetooth and audio codec based on a proprietary Bluetooth protocol. The electronic device may also include third-party applications, music functions, wallet functions, etc. When the electronic device communicates with the wearable device, it can be through Bluetooth and the audio codec to achieve two-device communication, or it can be through a modem to achieve two-device communication between the electronic device and the wearable device.

[0126] It should be noted that the functional modules included in the above software structure are merely exemplary and do not constitute a specific limitation on the software architecture of the device involved in this application. In other embodiments, the functional modules included in the above software structure may be more or fewer, and this application does not impose any limitations on this. Although the embodiments of this application use the Android system as an example for illustration, its basic principles are equally applicable to electronic devices based on operating systems such as iOS or Windows.

[0127] It should be understood that, in the embodiments of this application, the electronic device may be a mobile phone, tablet computer, laptop computer, handheld computer, mobile internet device (MID), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, personal digital assistant (PDA), etc., and the embodiments of this application are not limited thereto.

[0128] For example, the hardware structure of the wearable device in the embodiments of this application will be described below.

[0129] like Figure 7As shown, the wearable device may include: a processor 110, external memory 120, internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a sensor module 180, buttons 190, a motor 191, an indicator 192, and a display screen 193, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer 180E, a proximity sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0130] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0131] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0132] The external memory 120 is used to store programs and data that the processor is not currently using, and the external memory can still retain data after power failure. In this embodiment, both the local data file and the fused data file can be stored in the external memory of the wearable device. When the wearable device implements the data display method provided in this application, the processor can obtain initial local data from the local data file and initial fused data from the fused data file, and process the initial local data and initial fused data using the collected motion increment data to obtain first local data and first fused data. The processor then writes the first local data into the local data file and the first fused data into the fused data file, thereby ensuring data security.

[0133] The wireless communication function of wearable devices can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0134] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in a wearable device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0135] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in wearable devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0136] The wireless communication module 160 can provide solutions for wireless communication applications in wearable devices, including wireless local area networks (WLAN) (such as WiFi), Bluetooth (BT), BLE broadcasting, global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR). The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0137] Wearable devices achieve two-way communication with electronic devices through mobile communication module 150, wireless communication module 160, modem processor, and baseband processor. Wearable devices can send local data stored in local data files to electronic devices, and electronic devices can send fused data to wearable devices.

[0138] Wearable devices implement display functions through a display screen 193 and an application processor, etc. The display screen 193 is used to display images, videos, etc. The display screen 193 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 (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the wearable device may include one or N displays 193, where N is a positive integer greater than 1. In this embodiment, the display screen 193 can be used to display... Figure 1A , Figure 2A , Figure 2C and Figure 2E The user interface shown.

[0139] Touch sensor 180K, also known as a "touch panel," can be located on display screen 193. The touch sensor 180K and display screen 193 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. Touch sensor 180K can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 193. In other embodiments, touch sensor 180K may also be located on the surface of the wearable device, in a different position than display screen 193. In this embodiment, touch sensor 180K can be used to detect user-triggered motion detection, and the wearable device can display fused data in response to this operation.

[0140] The hardware architecture of electronic devices that synchronize data with wearable devices can be... Figure 7 The hardware structures shown are similar. Furthermore, to achieve the corresponding functions, the hardware structure of the electronic device can be... Figure 7 Based on the hardware structure shown, functional modules can be added or removed as appropriate (e.g., adding SIM card interface, camera, headphone jack, etc.).

[0141] It is understood that the structures illustrated in this embodiment do not constitute a specific limitation on wearable devices and electronic devices. In other embodiments, wearable devices and electronic devices may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0142] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive).

[0143] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0144] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0145] The modules in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0146] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: flash drive, ROM, RAM, disk or optical disk, etc.

[0147] The above-disclosed embodiments are merely one preferred embodiment of this application and only a part of the embodiments of this application. They should not be construed as limiting the scope of the claims of this application.

Claims

1. A data display method, characterized in that, The method is applied to wearable devices, and the method includes: Based on the collected incremental motion data, the initial local data stored in the local data file is updated to the first local data; In response to a data acquisition command from an electronic device, the first local data is sent to the electronic device; Receive second fused data from the electronic device, the second fused data being obtained based on the first local data and motion data acquired by the electronic device; The second fused data is displayed on the first motion data interface.

2. The method as described in claim 1, characterized in that, The method further includes: Based on the collected incremental motion data, the initial fusion data stored in the fusion data file is updated to the first fusion data.

3. The method as described in claim 2, characterized in that, The method further includes: The fused data stored in the fused data file is updated from the first fused data to the second fused data.

4. The method according to any one of claims 1-3, characterized in that, The process of updating the initial local data stored in the local data file to the first local data based on the collected incremental motion data includes: In response to the collected incremental motion data being greater than or equal to the storage threshold, the initial local data stored in the local data file is updated to the first local data; Wherein, the first local data is the sum of the collected motion increment data and the initial local data.

5. The method as described in claim 2 or 3, characterized in that, The method further includes: In response to the collected motion increment data being greater than or equal to the display threshold, the first fused data is displayed on the first motion data interface; The first fused data is the sum of the collected motion increment data and the initial fused data.

6. The method as described in claim 2 or 3, characterized in that, The display of the second fused data on the first motion data interface includes: In response to the second fused data being greater than the first fused data, the second fused data is displayed on the first motion data interface.

7. A data display method, characterized in that, The method is applied to an electronic device, and the method includes: Send a data acquisition instruction to the wearable device, the data acquisition instruction being used to acquire local data from the wearable device; Receive first local data from the wearable device; Based on the first local data and the acquired motion data, the second fused data is determined; The second fused data is sent to the wearable device and displayed on the second motion data interface.

8. The method as described in claim 7, characterized in that, The acquired motion data includes motion data collected by the electronic device and / or motion data received from a target device, wherein the target device is a device other than the electronic device and the wearable device; the second fused data is the sum of the first local data and the acquired motion data.

9. A wearable device, characterized in that, The wearable device includes: one or more processors, a memory, and a touchscreen; the memory is used to store program code; the processor is used to run the program code, such that the wearable device implements the method as described in any one of claims 1-6.

10. An electronic device, characterized in that, The electronic device includes: one or more processors, a memory, and a touch screen; the memory is used to store program code; the processor is used to run the program code, causing the electronic device to implement the method as described in any one of claims 7 or 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-6, or the method as described in any one of claims 7 or 8.

12. A chip system, characterized in that, The chip system is coupled to a memory, and the chip system is used to read and execute a computer program stored in the memory to implement the method as described in any one of claims 1-6, or to implement the method as described in any one of claims 7 or 8.

Images