Data processing method and device, wearable device, storage medium and program product

Abstract

The application relates to a data processing method and device, a wearable device, a computer readable storage medium and a computer program product. The method comprises the following steps: obtaining a data request of a target application running on a first system, sending the data request to a second system, and obtaining target data required by the target application by processing sensor data by the second system according to the data request. The data request of the target application is obtained, the data request is sent to the second system, and the target data required by the target application obtained by processing by the second system is obtained by the second system, so that the target application does not need to process by itself.

Description

Technical Field

[0001] This application relates to the field of computer application technology, and in particular to a data processing method, apparatus, wearable device, computer-readable storage medium, and computer program product. Background Technology

[0002] With the increasing popularity of wearable devices, more and more users are using them. Wearable devices can provide a variety of functions, such as sports data management and heart rate monitoring.

[0003] In traditional technologies, wearable devices collect and calculate sensor data in real time as needed. Summary of the Invention

[0004] This application provides a data processing method, apparatus, computer device, and computer-readable storage medium that eliminates the need for applications to process data themselves.

[0005] In a first aspect, this application provides a data processing method applied to a wearable device, the wearable device having a first system and a second system; the method includes:

[0006] Obtain the data request from the target application running on the first system and send the data request to the second system;

[0007] The second system obtains the target data required by the target application by processing the sensor data, as requested by the second system, according to the data request.

[0008] Secondly, this application also provides an application for a wearable device including a first system and a second system. The application includes a target software development kit corresponding to the wearable device. The target software development kit includes: a motion management interface and a data interface. The motion management interface is configured to control the motion or health monitoring process. The data interface includes one or more of a data reporting interface, a target trigger notification interface, and an abnormal event notification interface.

[0009] Thirdly, this application also provides a data processing apparatus for use in a wearable device, the wearable device having a first system and a second system; the apparatus includes:

[0010] The communication module is used to acquire data requests from the target application running on the first system and send the data requests to the second system.

[0011] The processing module is used, in the second system, to obtain the target data required by the target application obtained by the second system from the processing of sensor data according to the data request.

[0012] Fourthly, this application also provides a wearable device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method steps in the first aspect.

[0013] Fifthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method steps of the first aspect.

[0014] Sixthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the method of the first aspect.

[0015] The aforementioned data processing method, apparatus, electronic device, computer-readable storage medium, and computer program product acquire a data request from a target application running on a first system, send the data request to a second system, and acquire the target data required by the target application obtained by the second system from the sensor data processed by the second system. Therefore, the target application does not need to process the data itself. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of the internal structure of the wearable device in some embodiments;

[0018] Figure 2 This is a flowchart illustrating the data processing method in some embodiments;

[0019] Figure 3 This is a flowchart illustrating the data processing method in some other embodiments;

[0020] Figure 4 This is a schematic diagram of the architecture of a dual-core system in some embodiments;

[0021] Figure 5 This is a structural block diagram of the device in some embodiments. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0023] The data processing method provided in this application embodiment can be applied to, for example... Figure 1 The wearable device shown is a smartwatch, smart bracelet, head-mounted device, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc.

[0024] Wearable device 100 has a first system and a second system. The power consumption of the first system is greater than that of the second system. Both the first and second systems are independent operating systems. Wearable device 100 includes a first processor 110 corresponding to the first system and a second processor 120 corresponding to the second system. The power consumption of the first processor 110 is greater than that of the second processor 120. The first processor 110 and the second processor 120 can be configured with corresponding microprocessors according to actual applications, and there are no limitations on the first processor 110 and the second processor 120 here. For example, the first processor 110 can be a CPU (Central Processing Unit) processor, and the corresponding first system can be an Android system, an iOS system, a HarmonyOS system, a Windows Phone system, etc.; the second processor 120 can be an MCU (Microcontroller Unit) processor; and the corresponding second system can be an RTOS (Real-Time Operating System) system or other embedded systems.

[0025] For example, the wearable device 100 may include one or more of the following sensors: heart rate sensor 121, accelerometer + gyroscope 122, atmospheric pressure sensor 123, touch sensor 124, magnetic sensor 125, and micro-differential pressure sensor 126; the second processor 120 may be connected to the sensors included in the wearable device 100 to acquire data collected by the sensors; the second processor 120 may also be connected to the GPS (Global Positioning System) module 127 to acquire positioning data received by the GPS antenna.

[0026] The first processor 110 and the second processor 120 can be connected via SPI (Serial Peripheral Interface), UART (Universal Asynchronous Receiver / Transmitter), or USB (Universal Serial Bus) interface, allowing the first and second systems to transmit communication data via SPI bus, UART, or USB interface. The display screen 130 is connected to the first processor 110 and the second processor 120 via MIPI (Mobile Industry Processor Interface), displaying the data output by either the first processor 110 or the second processor 120. The first processor 110 or the second processor 120 may also include a sensor hub driver, which can be used to drive data acquisition and processing from various sensors.

[0027] In one exemplary embodiment, such as Figure 2 As shown, a data processing method is provided, which can be applied to... Figure 1 Taking a wearable device as an example, the wearable device has a first system and a second system; the data processing method includes steps 202 to 204. Wherein:

[0028] Step 202: Obtain the data request of the target application running on the first system and send the data request to the second system.

[0029] The first system and the second system are two independent operating systems. The first system can be a big-core system, and the second system can be a little-core system. The first system corresponds to the first processor, and the second system corresponds to the second processor. The power consumption of the first processor is greater than that of the second processor.

[0030] The first system contains one or more target applications. These target applications can be sports-related applications. Sports applications can include activities such as walking, running, skipping rope, and swimming. Sports applications are those primarily designed to promote physical exercise, improve athletic performance, and manage health. Sports applications can provide various functions, such as exercise recording, exercise planning, and social interaction. The exercise recording function uses the device's sensors to record the user's exercise data, including trajectory, distance, speed, and calories burned. Sports applications can integrate a sports SDK (Software Development Kit), which can directly utilize the exercise data provided by the wearable device. For example, the target application can be a third-party application.

[0031] Fitness apps can provide functions such as starting, pausing, stopping, and setting exercise goals. For example, when opening the TwoStep app on a wearable device, users first need to select the type of exercise they want to do, such as hiking, and then start exercising. During the exercise, users can choose to pause the current exercise or stop when they are not exercising. Before starting the exercise, users can set a goal for the exercise, such as a 5-kilometer reminder, which means that when the exercise distance reaches 5 kilometers, the user will be reminded by voice or vibration.

[0032] For example, in the first system, in response to a user triggering and launching the target application, the first system obtains a data request from the target application and sends the data request to the second system. A data request refers to a request from the target application that it needs to output and display corresponding data.

[0033] For example, the data request may carry a target period. The target period refers to the period at which the target application obtains the target data, such as once every 1 second, once every 3 seconds, etc., and is not limited to this.

[0034] Step 204: The second system obtains the target data required by the target application by processing the sensor data according to the data request.

[0035] The second system includes a sensor management module and a sports and health algorithm. The sensor management module can retrieve target data required by the target application by processing sensor data using the second system's sports and health algorithm based on data requests.

[0036] For example, the sports and health algorithm corresponding to the target data required by the target application can be configured on the second system. The second system obtains the target data required by the target application by processing the sensor data using the corresponding sports and health algorithm according to the data request. The target data may include one or more of the following: exercise distance, speed, calories, or heart rate.

[0037] For example, the second system acquires sensor data according to a target period, and then processes the acquired sensor data to obtain the target data required by the target application. The sensor data acquisition period is shorter than the target period; for example, the acquisition period is 1 millisecond per acquisition, and the target period is 3 milliseconds per acquisition. This ensures that the target application has sufficient data when acquiring data. If there are multiple target applications, the acquisition period is less than or equal to the smallest target period among the multiple target applications. For example, if the target period for target application A is 3 milliseconds per acquisition, and the target period for target application B is 5 milliseconds per acquisition, then the acquisition period is less than or equal to 3 milliseconds.

[0038] The second system obtains the target data required by the target application, which is obtained by processing the sensor data by the second system according to the data request. This can include the following two implementation methods:

[0039] In one implementation, the second system can periodically or in real-time process the acquired sensor data to obtain target data and store it. When the target application sends a data request, the processed target data can be sent to the first system according to the data request. This allows for faster acquisition of target data upon receiving a data request, but the power consumption is relatively higher.

[0040] In another implementation, the second system can acquire sensor data periodically or in real time, but may not process it or may process it only after a longer interval. Alternatively, it can process the sensor data to obtain the target data when it receives a data request from the target application, and then send the target data to the first system. This approach takes a longer time to acquire the target data upon receiving a data request, but consumes less power.

[0041] Both of the above implementation methods can be achieved, and there is no limitation on either. In addition, the sensor data can be sensor data from wearable devices, sensor data from other devices such as mobile phones and sports equipment, or a combination of sensor data collected from wearable devices and other devices.

[0042] The above data processing method obtains the data request of the target application through the first system, sends the data request to the second system, and obtains the target data required by the target application by processing the sensor data through the second system. Therefore, the target application does not need to process the data itself, which can reduce the power consumption of the wearable device and extend the battery life.

[0043] In some exemplary embodiments, the method further includes: the power consumption of the first system is greater than the power consumption of the second system. When the power consumption of the first system is greater than the power consumption of the second system, the second system acquires the target data obtained by processing the sensor data. Compared to the first system processing the data required by the target application, this saves more power and can extend the battery life of the wearable device.

[0044] In some exemplary embodiments, the method further includes: the first system converting the data request of the target application into a data request that conforms to the instructions and data structure for communication between the first system and the second system.

[0045] By transforming the target application's data requests into data requests that conform to the instructions and data structures for communication between the first and second systems, it facilitates interaction between the target application and the first system.

[0046] In some exemplary embodiments, sending the data request to the second system includes: sending the data request to the second system via a first service on the first system.

[0047] In some exemplary embodiments, the method further includes: transmitting the target data to the first system via the second system; and displaying the target data on the first system.

[0048] After the second system processes the target data, it can transmit it to the first system, which then controls the screen display of the target data. The first system can provide a UI (User Interface) for the target application, displaying the target data through this interface. The target application's UI under the first system can also provide further data display or interactive functions. The first and second systems communicate via a dual-system communication method. This method can be message queue or shared memory; for example, the second system can encapsulate the target data into a structured message and send it to the first system via a message queue.

[0049] For example, transmitting target data to the first system via the second system includes: a second service in the second system transmitting the target data to a first service in the first system.

[0050] The first system may include a first service and a first communication module, and the second system may include a second service and a second communication module. The second service in the second system transmits target data to the first communication module of the first system through the second communication module of the second system, and then transmits it to the first service in the first system through the first communication module.

[0051] Displaying target data in the first system may include: a first service in the first system transmitting the target data to a target application so that the target data is displayed in the user interface of the target application.

[0052] In this embodiment, the second system performs data acquisition and processing, while the target application on the first system is responsible for receiving, displaying, and storing the target data, which can reduce the power consumption of the device during the operation of the first system.

[0053] In some exemplary embodiments, the method further includes: transmitting the target data to the first system via the second system; and transmitting the target data to the target application via a first service in the first system, so that the target data is displayed in the user interface of the target application.

[0054] The second service in the second system transmits the target data to the first service in the first system. The first service in the first system transmits the target data to the target application, where it is displayed on the user interface of the target application, thus enabling the display of the required target data in the target application and meeting the data display needs of the target application.

[0055] In some exemplary embodiments, transmitting target data to the first system via the second system includes: a second service of the second system acquiring the target data, storing the target data, and reporting the target data to the first service via dual-core communication.

[0056] After the second service of the second system obtains the target data, it first stores the target data in the corresponding storage space of the second system, and then reports the target data to the first service through dual-core communication, so as to provide the target application with the target data.

[0057] In some exemplary embodiments, the target application includes a software development kit corresponding to the wearable device, the software development kit including an interface for data interfacing with the wearable device.

[0058] The target application integrates a Software Development Kit (SDK), which includes interfaces for data exchange with wearable devices. The SSD includes two types of interfaces: one is for activity management, including starting, pausing, stopping, and setting activity goals to control the entire activity process; the other is for data, including activity data reporting, activity goal triggering notification, and abnormal event notification. The abnormal event notification interface can include notifications for abnormal heart rate and fall detection.

[0059] In some exemplary embodiments, the method further includes: registering a callback function in a first running service using an interface provided by the target application's software development kit.

[0060] Different target applications' software development kits (SDKs) provide interfaces that register different callback functions in the first service. The first service records the mapping relationship between callback functions and target applications. When the first service obtains data, it calls the callback function according to the mapping relationship to transmit the data to the corresponding target application.

[0061] Different interfaces provided by the software development kit for the same target application can register the same or different callback functions in the first service.

[0062] Registering callback functions for the interfaces provided by the target application's software development kit in the first service allows the first service to easily report data to the target application via these callback functions. Furthermore, by providing unified application data access and control interfaces, applications can quickly and easily integrate with the system.

[0063] Accordingly, the first service in the first system transmits the target data to the target application, including: the first service in the first system transmits the target data to the target application through a callback function.

[0064] The callback function can transmit the target data to the target application, enabling data interaction between the first service of the first system and the target application.

[0065] In an exemplary embodiment, a first service in the first system transmits the target data to the target application via a callback function, including: the first service in the first system converts the target data into target data conforming to the format of the target application, and then transmits the target data conforming to the format of the target application to the target application via a callback function.

[0066] When the data format required by the target application is different from the data format of the target data received by the first system, the first service can convert the received target data into target data that conforms to the target application's format, and then transmit the target data that conforms to the target application's format to the target application through a callback function, so that the target application can display it.

[0067] In one exemplary embodiment, the data request may also carry configuration information, which may include at least one of target period, moving target triggering conditions, and abnormal event triggering conditions.

[0068] The above method also includes: the first service receiving configuration information issued by the target application and transmitting the configuration information to the second service of the second system.

[0069] If the configuration information includes a target period, the second service transmits the target data to the first service according to the target period.

[0070] If the configuration information includes motion target trigger conditions, and the wearable device is controlled by the first system, then the first service detects whether the target data meets the motion target trigger conditions. If the conditions are met, the first service outputs a motion target notification to indicate that the motion target has been reached. For example, if the motion target trigger condition is a distance of 5 kilometers, the user is notified that the motion target has been reached. The first service detects that the target data meets the 5-kilometer requirement and outputs a motion target notification. The motion target notification can be a voice prompt, vibration prompt, or light prompt, etc. By outputting the motion target notification through the first service of the first system, the first system has stronger performance and can provide richer information.

[0071] If the configuration information includes motion target triggering conditions, and the wearable device is controlled by a second system, then the second service detects whether the target data meets the motion target triggering conditions. If the conditions are met, the second service outputs a motion target notification to indicate that the motion target has been reached. For example, if the motion target triggering condition is a distance of 5 kilometers, the user is notified that the motion target has been reached. The second service detects that the target data meets the 5-kilometer requirement and outputs a motion target notification. The motion target notification can be a voice notification, vibration notification, or light notification, etc. By outputting the motion target notification through the second service of the second system, the first system does not need to be woken up, thus saving power consumption of the wearable device.

[0072] If the configuration information includes abnormal event triggering conditions, and the wearable device is controlled by the first system, then the first service detects whether the target data meets the abnormal event triggering conditions. If the conditions are met, the first service outputs an abnormal event notification to indicate the presence of an anomaly. Abnormal event notifications may include abnormal heart rate notifications or fall notifications, etc. By outputting abnormal event notifications through the first service of the first system, the first system exhibits stronger performance and can provide richer information.

[0073] If the configuration information includes abnormal event triggering conditions, and the wearable device is controlled by the second system, then the second service detects whether the target data meets the abnormal event triggering conditions. If the conditions are met, the second service outputs an abnormal event notification to indicate the presence of an anomaly. The abnormal event notification may include abnormal heart rate notifications or fall notifications, etc. By outputting abnormal event notifications through the second service of the second system, it is not necessary to wake up the first system, thereby saving power consumption of the wearable device.

[0074] In some exemplary embodiments, the method further includes displaying the target data through the second system.

[0075] The second system can provide a user interface for the target application. After processing the target data, the second system controls the screen and displays the target data through the user interface provided by the second system.

[0076] In this embodiment, the second system performs data acquisition and processing, and controls the display. The first system is not needed at all, and can be put into hibernation, thereby saving the power consumption of the first system and further saving power consumption, thus extending the battery life of the wearable device.

[0077] In some exemplary embodiments, the method further includes: determining a target operating system for controlling the screen of the wearable device based on at least one of the target application and device state; and, if the target operating system is determined to be a second system, performing the step of displaying the target data through the second system.

[0078] The second system can be configured to support certain applications and their display interfaces. When the target application is supported by the second system, its user interface can be displayed through the second system. Device status can include whether it is charging, whether there are incoming calls, etc.

[0079] Based on at least one of the target application and device status, the target operating system controlling the wearable device's screen can be determined. If the target operating system is determined to be a second system, the target data is displayed through the second system. If the target operating system is determined to be a first system, the target data is displayed through the first system.

[0080] Based on at least one of the target application and device status, the target operating system controlling the screen of the wearable device can be determined relatively accurately, enabling dynamic switching between the first system and the second system, thereby taking into account both the device performance and power consumption of the wearable device.

[0081] In some exemplary embodiments, determining the target operating system for controlling the screen of the wearable device based on at least one of the target application and the device state includes: if it is determined that the device state is not the target device state, determining whether the second system can support the target application; if it is determined that the second system can support the target application, determining that the target operating system for controlling the screen of the wearable device is the second system.

[0082] The target device status is a pre-configured device status, which may include charging status, incoming call status, call status, etc.

[0083] For example, the performance of the second system is lower than that of the first system. The second system provides fewer functional services than the first system. The second system is pre-configured with a set of applications that it can support. The second processor of the wearable device compares the target application with the configured set of applications that the second system can support. If the target application is in the application set, it is determined that the second system can support the target application; if the target application is not in the application set, it is determined that the second system cannot support the target application.

[0084] For example, the second processor compares the application package name of the target application with the application package names in the application set. If the application package name of the target application is the same as the application package name in the application set, it is determined that the second system can support the target application.

[0085] In some exemplary embodiments, determining the target operating system controlling the screen of the wearable device as the second system when it is determined that the second system can support the target application includes: determining whether the second system can support the first display interface currently displayed by the target application when it is determined that the second system can support the target application; and determining the target operating system controlling the screen of the wearable device as the second system when it is determined that the second system can support the first display interface currently displayed by the target application.

[0086] The second system is configured with a set of display interfaces that can be supported by the target application. A target application may have multiple different display interfaces. For example, the display interfaces of a two-step application may include a step count display interface, a route display interface, a pace display interface, etc. The set of display interfaces that the second system can support can be configured as needed. For example, if the configured support for display interfaces includes a step count display interface, then the route display interface and the pace display interface cannot be supported.

[0087] The second processor compares the first display interface currently displayed by the target application with the set of display interfaces supported by the second system. If the current display interface is in the set of display interfaces, it determines that the second system can support the first display interface currently displayed by the target application, and determines that the target operating system controlling the screen of the wearable device is the second system. If the first display interface is not in the set of display interfaces, it determines that the second system cannot support the first display interface currently displayed by the target application, and determines that the target operating system controlling the screen of the wearable device is the first system.

[0088] In some exemplary embodiments, determining the target operating system for controlling the screen of the wearable device based on at least one of the target application and the device state includes: if the device state is determined to be the target device state, determining the target operating system for controlling the screen of the wearable device to be a first system.

[0089] The target device state is a pre-configured device state, which may include charging status, incoming call status, and call status. When the wearable device is in the target device state, the target operating system controlling the wearable device's screen is determined to be the first system, which can provide more functions.

[0090] In some exemplary embodiments, the above method further includes: when it is determined that the screen control of the wearable device has been switched to the second system, transmitting part or all of the first interface data currently displayed by the target application in the first system to the second service of the second system through the first service; the second service transmitting part or all of the first interface data of the target application to the interface rendering engine in the second system, and the interface rendering engine obtaining the first display interface of the target application based on the part or all of the first interface data.

[0091] Understandably, due to performance differences between the first and second systems, some interface effects may run on the second system but not on the second system. Therefore, it may be sufficient to send only the portion of the first interface data that runs on the second system. Furthermore, for example, since the second system may already contain some first interface data, it may be possible to send only a portion of the currently displayed first interface data, such as current operating parameters, combined with some interface assets already stored on the second system to generate the corresponding interface that runs on the second system.

[0092] The interface rendering engine can be a JavaScript engine, etc. The first interface data is the data corresponding to the first display interface. By transmitting part or all of the first interface data currently displayed by the target application in the first system to the second service of the second system, the interface rendering engine can render the first display interface based on part or all of the first interface data. This allows the user interface of the target application in the first and second systems to be the same, enabling switching between the first and second systems while keeping the displayed user interface of the target application unchanged. This achieves seamless switching of the user interface and improves the user experience.

[0093] In some exemplary embodiments, the method further includes: determining a target operating system for controlling the screen of the wearable device based on at least one of a target application and a device state; if the target operating system is determined to be a second system, then determining that the screen control of the wearable device is switched to the second system.

[0094] The target operating system for controlling the screen of the wearable device is determined based on at least one of the target application and device status, as previously described and will not be repeated here.

[0095] In some exemplary embodiments, the method further includes: controlling the first system to hibernate after determining that the screen control of the wearable device has switched to the second system. Controlling the first system to hibernate can further save power consumption of the wearable device.

[0096] In some exemplary embodiments, the method further includes: a second service in the second system acquiring new target data required by the target application, the new target data being obtained by processing newly acquired sensor data; the new target data being displayed on a first display interface of the target application in the second system; when it is determined that the screen control of the wearable device has switched to the first system, the second service transmitting part or all of the second interface data currently displayed by the second system and / or the new target data to the first service; the first service transmitting the part or all of the second interface data to the target application, the target application obtaining a second display interface based on the part or all of the second interface data; and displaying the new target data on the second display interface.

[0097] In some embodiments, the first display interface of the target application displayed by the second system is the same as the first display interface of the target application displayed by the first system; this makes the switching of screen control imperceptible to the user.

[0098] In some embodiments, due to the performance of the second system, the first display interface of the target application displayed by the second system differs from the first display interface of the target application displayed by the first system, for example, the dynamic display changes to the static display.

[0099] After the wearable device's screen control switches to the second system and the first system goes into sleep mode, the sensor management service in the second system can continue to control the sensors to collect sensor data. The sports and health algorithm processes the collected sensor data to obtain new target data, which is then transmitted to the second service. The second service obtains the new target data required by the target application and then displays the new target data on the target application's first display interface in the second system.

[0100] After switching to the second system, the new target data required by the target application can continue to be displayed without waking up the first system, saving power consumption and still meeting the user's need to obtain the data required by the target application.

[0101] The second display interface can be the same as the first display interface, or it can be a different display interface.

[0102] After the first display interface is displayed in the second system, it may receive a user-triggered action to switch to the second display interface. The data in the second interface corresponds to the data in the second display interface.

[0103] When the screen control of the wearable device is switched to the first system, part or all of the second interface data of the target application currently displayed in the second system is transmitted to the first service of the first system, and then transmitted to the target application by the first service. The target application obtains the second display interface based on part or all of the second interface data. This can make the user interface of the target application in the first system and the second system similar or the same, realize the switching between the first system and the second system, but the user interface of the displayed target application remains unchanged, realize the seamless switching of the user interface, and improve the user experience.

[0104] For example, selecting a portion of the second interface data could be because the first system already stores some of the second system's materials, so it's unnecessary to transfer all of them; only the currently changing data needs to be transferred. Another example is based on the performance differences between the two systems; for instance, some data that doesn't need to be displayed on the first system doesn't need to be transferred.

[0105] In some exemplary embodiments, the above method further includes: when a preset number of target applications have been opened and other target applications are triggered to be opened, outputting a reminder to first close one or more of the already opened target applications and then open the other target applications.

[0106] The preset number can be set as needed. For example, the preset number can be 1 or 2, determined by the parallel processing algorithm supported by the second system. For instance, if the algorithm only supports calculating one type of motion data simultaneously, the preset number is 1. Alternatively, the preset number can be determined based on the maximum number of applications the wearable device can support running simultaneously. The preset number is less than or equal to the maximum number. When the wearable device detects that the user has already opened the preset number of target applications and triggers the opening of other target applications, it outputs a reminder to first close one or more already opened target applications before opening the others. This reminds the user to close unnecessary applications and open necessary ones, achieving concurrent control and processing of multiple target applications and improving processing efficiency.

[0107] Alternatively, in some exemplary embodiments, the above method further includes: when a target application is already open and other target applications are triggered to be opened, determining whether the application to be opened is the same type of target application as the already opened target application; if they are not the same type of target application, when the number of opened types meets the threshold, outputting a reminder to first close one or more types of already opened target applications and then open the other target applications.

[0108] For example, the number of different types that can be opened simultaneously can be one or two, depending on the parallel processing algorithms of different types that the second system can support. For instance, if the algorithm only supports simultaneous calculation of two types of motion data, then the threshold is 2. For example, applications can be pre-classified as needed. When the wearable device detects that the user has already opened a target application (which can be one or more), and obtains information that the user has triggered the opening of other target applications, it determines whether the application to be opened is the same type as the already opened target application. If they are not the same type, and the number of opened types meets the threshold, it outputs a reminder to first close one or more types of already opened target applications, and then open the other target applications. This provides reminders to the user when different types of applications are opened, making it convenient for the user to close applications in a timely manner and open the required applications. It also enables concurrent control and processing of multiple target applications, improving processing efficiency.

[0109] It is understandable that different types of target applications require different target data, and the processing performance of the second system is limited. Therefore, when the types of target applications that need to obtain target data exceed the processing performance of the second system, it will be unable to process the data and thus fail to obtain the corresponding target data. Therefore, it is recommended that users close one or more target applications when the number of target application types exceeds the preset number to avoid affecting the acquisition of target data.

[0110] In some exemplary embodiments, the method further includes: the second service transmitting new target data to the first service according to a target period; and the first service transmitting the new target data to the target application.

[0111] The target period can be set by the user as needed, or configured by the target application's developer. The target application obtains the target period and sends it to the first service, which then transmits the target period to the second service.

[0112] When the screen of the wearable device is controlled by the second system and the first system is in sleep mode, new target data can be transmitted to the first service according to the target cycle.

[0113] In some embodiments, when the electronic device meets preset conditions, the second system takes over screen control. These preset conditions may be conditions where the first system meets the requirements for screen-off or screen-off display. For example, no user operation is detected within a preset time and the first system can enter sleep mode. For example, the first system can enter sleep mode when it has no business to process. When the second system takes over screen control, the second service notifies the corresponding application of the second system to start and display the target data.

[0114] In some exemplary embodiments, the method further includes: determining a target operating system for controlling the screen of the wearable device based on at least one of a target application and a device state; if the target operating system is determined to be a first system, then determining that the screen control of the wearable device is switched to the first system.

[0115] In some exemplary embodiments, the above method further includes: if the screen-off condition is met, controlling the wearable device to be in a screen-off state and the first system to hibernate, continuing to acquire the collected sensor data under the second system, and processing the sensor data to obtain new target data required by the target application.

[0116] Screen-off conditions can be configured as needed. These conditions may include detecting a user-triggered screen-off operation, or automatically turning off the screen after a preset period of inactivity. In the second system, the sensor management module continues to acquire collected sensor data and transmits it to the sports and health algorithm module. The sports and health algorithm module processes the collected sensor data to obtain new target data required by the target application and transmits this new target data to the second service. The second service then transmits it to the interface rendering engine, which displays the new target data on either the first or second display interface of the target application.

[0117] When the wearable device is in a screen-off state, the first system is put into hibernation, while the second system continues to acquire the target data required by the target application obtained by processing the sensor data by the second system. This enables the target application to continue to provide the data required by the target application during the screen-off period, and the first system enters a hibernation state, which reduces the power consumption of the device generated by the operation of the first system, further saving the power consumption of the wearable device and extending the battery life of the wearable device.

[0118] In an exemplary embodiment, the method further includes: when the wearable device is in a screen-off state and the first system is in sleep mode, a second service of the second system transmits new target data to a first service of the first system according to a target period; the first service transmits the new target data to the target application. Reporting the acquired new target data to the first service according to the target period while the screen is off ensures the synchronization of target data between the first and second systems.

[0119] In some exemplary embodiments, when the wearable device is in a screen-off state, the above method further includes: if the screen-on condition is met, controlling the wearable device to be in a screen-on state through a second system, and displaying new target data in the second system.

[0120] The screen-on conditions can be configured as needed, such as turning on the screen when a hand is detected being lifted, or when a user triggers a screen-on operation.

[0121] When the screen-on condition is met, the second system controls the wearable device's screen to be on without waking up the first system. This avoids the power consumption introduced by frequently switching between the first system and the screen-on state during exercise. The target data is displayed under the second system, which can reduce the power consumption of the first system, save the wearable device's power consumption, and extend the wearable device's battery life.

[0122] In some exemplary embodiments, the method further includes: in the event of an upgrade of the target application, synchronously updating the user interface of the target application supported by the first system and the second system.

[0123] For example, the user interface of the target application can be developed using JavaScript, allowing the user interface of the target application supported in the second system to be updated synchronously with the target application. The upgrade package of the user interface of the target application supported in the second system can be integrated with the APK (Android application package) of the target application in the first system and then released together. After the user downloads the application APK through an app store, the upgrade package for the second system is transmitted to the second system via dual-core communication, thus updating the functionality of the second system.

[0124] When the target application is upgraded, the user interface of the target application supported by the second system is updated synchronously. This ensures that the second system can still support the display of the target application's user interface after the target application is updated, so that the data required by the target application can be displayed without the first system. This reduces the power consumption of the first system and extends the battery life of the wearable device.

[0125] In some exemplary embodiments, the above method further includes: the power consumption of the first system is greater than the power consumption of the second system; and / or, the target data is output in a voice manner through the second system.

[0126] If the target application has a voice broadcast function during operation, the voice playback processing logic can be configured in the second system. The target data can be output by voice through the second system, thereby reducing the frequent wake-up of the first system during voice playback and saving power consumption of the wearable device.

[0127] For example, when the wearable device is controlled by either the first system or the second system, the target data can be output via voice through the second system.

[0128] For example, the target data can be output via voice at a pre-configured frequency, such as once per minute or once every three minutes. The second system then plays the target data via voice at the target output frequency. By setting the output frequency, user needs can be met, and power consumption can be saved.

[0129] In some exemplary embodiments, the method further includes: if the screen-off condition is met, controlling the wearable device to be in a screen-off state and the first system to hibernate, while the second service in the second system continues to acquire new target data required by the target application, the new target data being obtained by processing newly acquired sensor data; and outputting the new target data via voice in the second system. In the screen-off state, outputting new target data via voice in the second system eliminates the need to wake up the first system or turn on the screen, thus saving power consumption of the wearable device.

[0130] In some exemplary embodiments, the method further includes: when the wearable device is under the control of a first system, outputting target data via voice through the first system.

[0131] When the wearable device is under the control of the first system, the first system is equipped with a voice broadcast module, which can output the target data by voice.

[0132] In some exemplary embodiments, the method further includes: when the second system takes over screen control, a second service of the second system notifies the corresponding application of the second system to draw the target data. When the second system takes over screen control of the wearable device, the second service of the second system notifies the corresponding application in the second system to draw the target data, thereby enabling the second system to display the target data and meeting the user's need to obtain data.

[0133] In some embodiments, when the second system takes over screen control, the first system is in a state of shutdown, hibernation, or running in the background.

[0134] In some exemplary embodiments, the method further includes: when a near-field communication link is established between the wearable device and the mobile device, the wearable device transmits data to the mobile device, and the mobile device sends data.

[0135] Mobile devices can be smartphones, smart glasses, personal computers, in-vehicle devices, etc.

[0136] For example, a near-field communication link can be a Bluetooth communication link. Wearable devices and mobile devices establish a communication connection via Bluetooth pairing.

[0137] For example, when the second system controls the wearable device, it cannot communicate directly with the server. The second processor corresponding to the second system communicates with the mobile device through a near-field communication module (such as a Bluetooth communication module, an NFC (Near Field Communication) module, etc.), and then the mobile device communicates with other devices (such as the server).

[0138] After the wearable device establishes a near-field communication link with the mobile device, it can communicate with other devices through the mobile device under the control of the second system, reducing the need to wake up the first system, saving power consumption, and improving the battery life of the wearable device.

[0139] In some exemplary embodiments, the method further includes: when the target data includes networked data and the wearable device is controlled by a first system, transmitting the networked data to a server via the cellular network corresponding to the first system. The networked data may be real-time location data or motion data of members within a group in the target application. Members within the group may be individuals participating in a sports team competition.

[0140] In some exemplary embodiments, the above method further includes: the target data includes network data, and when the wearable device is controlled by a second system, the second system transmits the network data to the mobile device via a Bluetooth communication link, and the mobile device transmits the network data to the server.

[0141] In some exemplary embodiments, such as Figure 3 As shown, a data processing method includes steps 302 to 318.

[0142] Step 302: Obtain the data request from the target application running on the first system and send the data request to the second system.

[0143] Step 304: The second system obtains the target data required by the target application by processing the sensor data, according to the data request.

[0144] Step 306: The second service in the second system acquires the target data and transmits the target data to the first service in the first system.

[0145] Step 308: In the first system, the first service converts the target data into target data that conforms to the target application format, and then sends the target data in the first service to the target application through a callback function, and displays the target data in the user interface of the target application.

[0146] Step 310: If the screen-off condition is met, control the wearable device to be in a screen-off state and the first system to hibernate. Transmit part or all of the first interface data currently displayed by the target application in the first system to the second service of the second system through the first service. The second service transmits part or all of the first interface data of the target application to the interface rendering engine in the second system. The interface rendering engine obtains the first display interface of the target application based on part or all of the first interface data.

[0147] Step 312: The second service in the second system acquires the new target data required by the target application. The new target data is obtained by processing the newly collected sensor data. The new target data is output in voice mode in the second system.

[0148] The second service transmits new target data to the first service according to the target cycle; the first service then transmits the new target data to the target application.

[0149] Step 314: If the screen-on condition is met, control the wearable device to be in screen-on state through the second system, and display the target data under the second system.

[0150] Step 316: When it is determined that the screen control of the wearable device has been switched to the first system, the second service transmits part or all of the second interface data of the target application currently displayed in the second system to the first service; the first service transmits part or all of the second interface data to the target application, and the target application obtains the second display interface based on part or all of the second interface data; the new target data is displayed in the second display interface.

[0151] Step 318: In the event of an upgrade to the target application, the user interface of the target application supported by the first system and the second system is updated synchronously.

[0152] In this embodiment, the second system collects and processes the data required by the target application, allowing the first system to remain in a dormant state. This reduces the power consumption of the first system during operation. Software development tools are provided to enable capabilities such as starting, stopping, pausing, setting targets, monitoring anomalies, and reporting motion data, meeting the rapid requirements of third-party applications. Screen switching control during operation allows dynamic switching of screen control between the two systems, satisfying user requirements while reducing power consumption. The user interface of the target application provided by the second system is updated synchronously with target application upgrades, ensuring that the second system can still provide the corresponding user interface display function even when the target application is updated. This allows the second system to display target data without waking up the first system, thus saving power. The second system can output target data via voice, reducing the need to frequently wake up the first system for voice-based data playback, further saving power.

[0153] The data processing method of this application can be applied to data processing in third-party motion applications. In related technologies, taking a wearable device running the Android system as an example, third-party motion applications on the Android system are used for data registration, collection, and reception. These applications interact with the sensor service by calling the standard sensor interface provided by the Android system, registering the data to be collected and the data collection frequency with the sensor. Then, the sensor management service and sensor driver interact to complete the data collection and distribution processing. However, the frequency of sensor data collection and reporting during motion is mostly required to be at the millimeter level. Therefore, during the operation of a third-party motion application, the sensor collects and reports a large amount of data to the registered and receiving applications. This prevents the Android system from sleeping during the entire motion process. Even when the device screen is off, the Android system needs to continuously collect and report various sensor data to keep up with the user's motion data collection, resulting in very high power consumption for the wearable device. The data processing method provided in this application allows the sensor data collection and processing to run in a low-power second system, reducing the operation of the high-power first system and saving power.

[0154] This application also provides an application for a wearable device including a first system and a second system. The application includes a target software development kit corresponding to the wearable device. The target software development kit includes: a motion management interface and a data interface. The motion management interface is configured to control the motion or health monitoring process. The data interface includes one or more of a data reporting interface, a target trigger notification interface, and an abnormal event notification interface.

[0155] The exercise management interface includes functions for starting, pausing, stopping, and setting exercise goals, used to control the entire exercise process, i.e., controlling the exercise or health monitoring process. Exercise monitoring can include monitoring data from activities such as walking, running, swimming, and hiking. Exercise data can include distance, speed, and trajectory. Health monitoring can monitor heart rate, blood pressure, etc., during exercise. Data interfaces include data reporting interfaces, goal-triggered notification interfaces, and abnormal event notification interfaces. The data reporting interface is used to report various types of data to the application. The goal-triggered notification interface is used to send notifications when a goal is achieved. The abnormal event notification interface can include notifications for abnormal heart rate, fall detection, etc.

[0156] In some exemplary embodiments, the application can query the motion capabilities of the wearable device through the software development kit. The motion capabilities include the types of motion that the wearable device can detect and the motion data related to those types.

[0157] The type of exercise can be configured as needed. Exercise types can include walking, running, swimming, hiking, etc., and the related exercise data can include exercise distance, exercise speed, exercise trajectory, exercise ranking, etc.

[0158] Taking the wearable device provided in this application, with its first system being a large-core system and its second system being a small-core system, as an example, the architecture and working process of a wearable device containing a dual-core system are explained. Figure 4As shown, the large-core system includes a sports application, a first service, a large-core dual-core communication module, and a large-core system switching module. The sports application integrates a sports SDK, allowing direct use of system-provided sports data. The first service, also known as the sports and health service, provides capabilities such as sports application registration management, sports data reception, storage, and distribution. The large-core dual-core communication module facilitates the interactive transmission of data and control commands between the large-core and small-core systems. The large-core system switching module manages the switching of the device screen between the two systems during the operation of the sports application. The small-core system includes a sports application rendering module, a JS engine (i.e., a UI rendering engine), a second service, a small-core dual-core communication module, a small-core system switching module, a sports and health algorithm module, and a sensor management module. The sports application rendering module renders part of the user interface of the sports application on the small-core system. The small-core system integrates a JS engine, and the user interface rendering is implemented using JavaScript, allowing for dynamic upgrades. The small-core system switching module and the large-core system switching module cooperate through a dual-core communication module (large-core dual-core communication module and small-core dual-core communication module) to jointly manage the switching of the device screen between the two systems. The sensor management module is used for the collection, distribution, and processing of sensor data during exercise. The sports health algorithm module receives data reported by the sensor management module, analyzes and processes it, and outputs target data. Target data can include various sports data and physiological data. Sports data can include one or more of the following: distance, speed, calories burned, etc. Physiological data can include one or more of the following: heart rate, blood oxygen data, blood pressure data, etc.

[0159] The integration and data processing processes for sports applications include:

[0160] (1) Sports applications integrate a sports SDK. The sports SDK contains two types of interfaces: one is a sports management interface, including sports start, pause, stop, and sports goal setting, which is used to control the entire sports process; the other is a data interface, including sports data reporting interface, sports goal trigger notification interface, and abnormal event notification interface, such as abnormal heart rate notification and fall detection notification. Sports applications start the required sports type through the interfaces provided by the sports SDK, set the data reporting period, and register a callback function to receive the sports data reported by the first service.

[0161] (2) The first service, namely the sports and health service, is the core service of sports data processing. It receives the interface calls of sports applications and transforms them into instructions and data structures for internal communication between the big and small core systems, and sends them to the small core system for execution. At the same time, the sports and health service also provides sports ability query, sports data storage and third-party application data distribution processing, multi-sports start-up and concurrent control processing, etc.

[0162] (3) The system switching module includes a big-core system switching module and a small-core system switching module. The two work together to control the switching of the device screen between big-core and small-core systems during the operation of motion applications. The system switching module determines whether to control the target operating system of the current device screen as a big-core system or a small-core system by judging the name of the currently running application package, the currently displayed motion interface, and other system states, such as whether it is charging or receiving a call.

[0163] (4) The dual-core communication module includes a large-core dual-core communication module and a small-core dual-core communication module, which together complete the data and control command transmission between the large and small core systems. For example, the command to start the movement is sent from the large core to the small core, and the movement data such as distance and calories during the movement are reported from the small core to the large core.

[0164] (5) The sensor management module, the sports and health algorithm module, and the second service jointly complete the collection, processing, storage, transmission, and distribution of sports data under the small core system. The sports and health algorithm module activates the corresponding sensor according to the type of sports and the required sports data. The sensor collects and reports data to the sports and health algorithm module according to the set period. The sports and health algorithm module filters and processes the raw sensor data and outputs sports data such as distance, heart rate, speed, and calories. The second service receives the data output by the sports and health algorithm module, stores the data, and reports the data to the first service of the big core through dual-core communication according to the configured frequency. When the small core system takes over the screen display, the second service notifies the sports application drawing module of the small core system to display the data.

[0165] (6) The JS engine and the motion application rendering module work together to realize the small core system taking over screen control during the motion process, and then the small core motion data display and processing. The user interface of the application is developed using JavaScript, which can make the small core motion interface update and upgrade synchronously with the motion application.

[0166] By integrating the motion SDK, the sensor management module in the small-core system controls the sensors to collect data. Motion applications do not need to collect sensor data in real time, so the large-core system is in a dormant state most of the time during the operation of the motion application, reducing the power consumption of the device. Through screen switching control and the user interface rendering function of the motion application provided by the small-core system, the user can view real-time data without waking up the large-core system. The display of motion data is implemented by the small-core system, reducing the frequent waking of the large-core system during exercise and further improving the battery life of wearable devices. The motion interface rendering under the small-core system is implemented by JavaScript, enabling dynamic updates of the user interface of the application under the small-core system, and updating along with the motion application upgrade package.

[0167] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0168] Based on the same inventive concept, this application also provides a device information processing apparatus for implementing the device information processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations of one or more device information processing apparatus embodiments provided below can be found in the limitations of the device information processing method described above, and will not be repeated here.

[0169] In some exemplary embodiments, such as Figure 5 As shown, a data processing device is applied to a wearable device, which has a first system and a second system, wherein the power consumption of the first system is greater than that of the second system; the device includes a communication module 510 and a processing module 520.

[0170] The communication module 510 is used to obtain data requests from the target application running on the first system and send the data requests to the second system.

[0171] The processing module 520 is used in the second system to obtain the target data required by the target application, which is obtained by the second system from the processing of sensor data, according to the data request.

[0172] The aforementioned data processing device obtains the data request from the target application through the first system, sends the data request to the second system, and obtains the target data required by the target application by processing the sensor data through the second system, without requiring the target application to process the data itself.

[0173] In some exemplary embodiments, the communication module 510 is also configured to send a data request to the second system via a first service on the first system.

[0174] In some exemplary embodiments, the above-described apparatus further includes a first display module. The communication module is used to transmit target data to the first system via the second system; the first display module is used to display the target data via the first system.

[0175] In some exemplary embodiments, the above-described apparatus further includes a first service module and a first display module located in the first system. The communication module is used to transmit target data to the first system via the second system. The first service module is used to transmit the target data to a target application. The first display module is used to display the target data on the user interface of the target application.

[0176] In some exemplary embodiments, the above-described apparatus further includes a second service module located in the second system. The second service module acquires the target data, stores the target data, and reports the target data to the first service module via dual-core communication.

[0177] In some exemplary embodiments, the above-described apparatus further includes a second service module located in the second system. When the second system takes over screen control, the second service module of the second system notifies the corresponding application of the second system to draw target data.

[0178] In some exemplary embodiments, the target application includes a software development kit (SDK) corresponding to the wearable device, and the SSD includes an interface for data interfacing with the wearable device.

[0179] In some exemplary embodiments, the above apparatus further includes a registration module. The registration module is used to register callback functions of the interfaces provided by the software development kit (SDK) of the target application in a first runtime service. The first service module is further used to transmit target data to the target application via the callback functions.

[0180] In some exemplary embodiments, the first service module is further configured to convert the target data into target data conforming to the target application format, and then transmit the target data conforming to the target application format to the target application through a callback function.

[0181] In some exemplary embodiments, the above-described apparatus further includes a second service module and an interface rendering engine located in the second system. When it is determined that screen control of the wearable device has switched to the second system, the first service module is further configured to transmit part or all of the first interface data currently displayed by the target application in the first system to the second service module of the second system via a communication module.

[0182] The second service module is also used to transmit part or all of the first interface data of the target application to the interface rendering engine in the second system. The interface rendering engine is used to obtain the first display interface of the target application based on part or all of the first interface data.

[0183] In some exemplary embodiments, the above-described apparatus further includes a second display module located in the second system. The second service module is also configured to acquire new target data required by the target application, the new target data being obtained by processing newly acquired sensor data;

[0184] The second display module is used to display new target data on the first display interface of the target application in the second system.

[0185] When it is determined that the screen control of the wearable device has been switched to the first system, the second service module is used to transfer part or all of the second interface data and / or new target data of the target application currently displayed by the second system to the first service module.

[0186] The first service module is used to transmit part or all of the second interface data to the target application, and the target application obtains the second display interface based on part or all of the second interface data.

[0187] The first display module is used to display new target data in the second display interface.

[0188] In some exemplary embodiments, the above-described apparatus further includes a reminder module. The reminder module is used to output a reminder, when a preset number of target applications are already open, and the opening of other target applications is triggered, to first close one or more of the already open target applications, and then open the other target applications. Alternatively,

[0189] The reminder module is used to determine whether the application to be opened is the same type of target application as the already opened target application when the target application is already opened and other target applications are triggered to open. If they are not the same type of target application, when the number of opened types meets the threshold, a reminder is output to first close one or more types of target applications that are already opened, and then open other target applications.

[0190] In some exemplary embodiments, the second service module is further configured to transmit new target data to the first service module according to the target period;

[0191] The first service module is also used to transfer new target data to the target application.

[0192] In some exemplary embodiments, when the wearable device is in a screen-off state and the first system is in sleep mode, the second service module is further configured to transmit new target data to the first service of the first system according to a target period; the first service module is further configured to transmit new target data to the target application.

[0193] In some exemplary embodiments, when it is determined that the screen control of the wearable device has switched to the first system, the second service module is further configured to transmit part or all of the second interface data of the target application currently displayed by the second system to the first service module.

[0194] The first service module is also used to transmit part or all of the second interface data to the target application, and the target application obtains the second display interface based on part or all of the second interface data.

[0195] The first display module is also used to display new target data in the second display interface.

[0196] For example, in some embodiments, new target data can also be transmitted to the first service module via the second service module. This embodiment can be combined and substituted with other embodiments without conflict, and there are no limitations thereon.

[0197] In some exemplary embodiments, the first service module is further configured to receive configuration information issued by the target application and transmit the configuration information to the second service module of the second system.

[0198] If the configuration information includes a target period, the second service module is also used to transmit the target data to the first service module according to the target period.

[0199] If the configuration information includes motion target triggering conditions, and the wearable device is controlled by the first system, the first service module is also used to detect whether the target data meets the motion target triggering conditions. If the motion target triggering conditions are met, the first service module outputs a motion target notification, which is used to prompt that the motion target has been reached.

[0200] If the configuration information includes motion target triggering conditions, and the wearable device is controlled by the second system, the second service module is also used to detect whether the target data meets the motion target triggering conditions. If the motion target triggering conditions are met, the second service module is also used to output a motion target notification, which is used to prompt that the motion target has been reached.

[0201] If the configuration information includes abnormal event triggering conditions, and the wearable device is controlled by the first system, the first service module is also used to detect whether the target data meets the abnormal event triggering conditions. If the abnormal event triggering conditions are met, the first service module is also used to output an abnormal event notification, which is used to indicate that an abnormality exists.

[0202] If the configuration information includes abnormal event triggering conditions, and the wearable device is controlled by the second system, the second service module is also used to detect whether the target data meets the abnormal event triggering conditions. If the abnormal event triggering conditions are met, the second service module is also used to output an abnormal event notification, which is used to indicate that an abnormality exists.

[0203] In some exemplary embodiments, the second display module is also used to display target data in the second system.

[0204] In some exemplary embodiments, the above-described apparatus further includes a determining module.

[0205] The determination module is used to determine the target operating system for controlling the screen of the wearable device based on at least one of the target application and device status;

[0206] The second display module is also used to display target data through the second system when the target operating system is determined to be the second system.

[0207] In some exemplary embodiments, the determining module is further configured to determine whether the second system can support the target application if the device state is not the target device state; and to determine the target operating system controlling the screen of the wearable device as the second system if the second system can support the target application.

[0208] In some exemplary embodiments, the determining module is further configured to, if it is determined that the second system can support the target application, determine whether the second system can support the first display interface currently displayed by the target application; and if it is determined that the second system can support the first display interface currently displayed by the target application, determine that the target operating system controlling the screen of the wearable device is the second system.

[0209] In some exemplary embodiments, the determining module is further configured to determine, when the device state is determined to be the target device state, the target operating system controlling the screen of the wearable device as the first system.

[0210] The determining module is further configured to determine the target operating system controlling the screen of the wearable device based on at least one of the target application and device status; if the target operating system is determined to be a second system, then the screen control of the wearable device is switched to the second system; if the target operating system is determined to be a first system, then the screen control of the wearable device is switched to the first system.

[0211] In some exemplary embodiments, the device further includes a sleep module. The sleep module is used to control the first system to sleep after determining that the screen control of the wearable device has switched to the second system.

[0212] In some exemplary embodiments, the above-described device further includes an always-on display module and a sleep module.

[0213] The screen-off module controls the wearable device to enter a screen-off state if the screen-off conditions are met. The sleep module controls the first system to enter sleep mode if the screen-off conditions are met. The processing module is also used to continue acquiring collected sensor data in the second system, and to process the sensor data to obtain the target data required by the target application.

[0214] In some exemplary embodiments, the above-described device further includes a screen-on module. The screen-on module is used to control the wearable device to be in a screen-on state via a second system, and to display target data under the second system, if the screen-on conditions are met.

[0215] In some exemplary embodiments, the above-described apparatus further includes an update module. The update module is used to synchronously update the user interface of the target application supported by the first system and the second system in the event of an upgrade of the target application.

[0216] In some exemplary embodiments, the above-described apparatus further includes a broadcasting module. The broadcasting module is used to output target data in a voice manner through a second system.

[0217] In some exemplary embodiments, the screen-off module is further configured to control the wearable device to be in a screen-off state if the screen-off conditions are met. The hibernation module is configured to control the first system to hibernate if the screen-off conditions are met; the second service module is further configured to continue acquiring new target data required by the target application, wherein the new target data is obtained by processing newly acquired sensor data; and the broadcast module is further configured to output the new target data in a voice manner in the second system.

[0218] It is understood that the communication module, processing module, first service module, second service module, first display module, second display module, determination module, screen-off module, sleep module, screen-on module, broadcast module, update module, reminder module, etc. in the above device can all be freely combined to achieve the corresponding functions.

[0219] Each module in the aforementioned data processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the electronic device in hardware form or independent of it, or stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to each module.

[0220] In one exemplary embodiment, a wearable device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the method described above.

[0221] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the method described above.

[0222] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the method described above.

[0223] In some or all of the embodiments or implementations of this application, the target application may be an application developed by other parties, or an application developed by a non-wearable device developer, such as a third-party application. It is understood that wearable devices can run applications developed by the wearable device manufacturer itself, as well as some applications not developed by the wearable device manufacturer itself, such as third-party applications. Users can download these applications from the network, or the device manufacturer can pre-install them before shipping; there are no restrictions on this.

[0224] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0225] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0226] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0227] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A data processing method, characterized in that, Applied to a wearable device, the wearable device having a first system and a second system, the method includes: Obtain the data request from the target application running on the first system and send the data request to the second system; The second system obtains the target data required by the target application by processing the sensor data, as requested by the second system, according to the data request.

2. The method according to claim 1, characterized in that, Sending the data request to the second system includes: sending the data request to the second system through a first service on the first system.

3. The method according to claim 1, characterized in that, The method further includes: The target data is transmitted to the first system through the second system; The first service in the first system transmits the target data to the target application so that the target data is displayed in the user interface of the target application.

4. The method according to claim 3, characterized in that, The step of transmitting the target data to the first system through the second system includes: the second service of the second system acquiring the target data, storing the target data, and reporting the target data to the first service through dual-core communication.

5. The method according to claim 1, characterized in that, The target application includes a software development kit corresponding to the wearable device, and the software development kit includes an interface for data interoperation with the wearable device.

6. The method according to claim 2, characterized in that, The method further includes: When it is determined that the screen control of the wearable device has been switched to the second system, part or all of the first interface data currently displayed by the target application in the first system is transmitted to the second service of the second system through the first service; The second service transmits part or all of the first interface data of the target application to the interface rendering engine in the second system, and the interface rendering engine obtains the first display interface of the target application based on the part or all of the first interface data.

7. The method according to claim 6, characterized in that, The method further includes: In the second system, the second service acquires new target data required by the target application, which is obtained by processing newly acquired sensor data; The new target data is displayed on the first display interface of the target application in the second system. When it is determined that the screen control of the wearable device has been switched to the first system, the second service transmits part or all of the second interface data of the target application currently displayed by the second system and / or the new target data to the first service. The first service transmits part or all of the second interface data to the target application, and the target application obtains a second display interface based on the part or all of the second interface data; The new target data is displayed in the second display interface.

8. The method according to claim 1, characterized in that, The method further includes: when a preset number of target applications are already open, and the opening of other target applications is triggered, outputting a reminder to first close one or more of the already open target applications, and then open the other target applications; or, If a target application is already open and another target application is triggered to open, it is determined whether the application to be opened is the same type of target application as the already opened target application. If they are not the same type of target application, and the number of already opened types meets the threshold, a reminder is output to first close one or more types of target applications that are already open, and then open the other target applications.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: In the event of an upgrade to the target application, the user interface of the target application supported by the first system and the second system is updated synchronously.

10. The method according to any one of claims 1 to 8, characterized in that, The power consumption of the first system is greater than that of the second system; and / or, the method further includes: The target data is output via voice through the second system.

11. The method according to claim 1, characterized in that, The method includes: when the second system takes over screen control, a second service of the second system notifies the corresponding application of the second system to draw the target data.

12. An application, characterized in that, The application is applied to a wearable device including a first system and a second system. The application includes a target software development kit corresponding to the wearable device. The target software development kit includes: a motion management interface and a data interface. The motion management interface is configured to control the motion or health monitoring process. The data interface includes one or more of a data reporting interface, a target trigger notification interface, and an abnormal event notification interface.

13. The application program according to claim 12, characterized in that, The application can query the sports capabilities of the wearable device through the software development kit. The sports capabilities include: the types of sports that the wearable device can detect and the sports data related to the sports types.

14. A data processing apparatus, characterized in that, Applied to wearable devices, the wearable devices having a first system and a second system; the device includes: The communication module is used to acquire data requests from the target application running on the first system and send the data requests to the second system. The processing module is used, in the second system, to obtain the target data required by the target application obtained by the second system from the processing of sensor data according to the data request.

15. A wearable device comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 11.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 11.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 11.

Images