A data acquisition method, a terminal device, and a storage medium

Abstract

The application is suitable for the field of electronic technology, and provides a data collection method, a terminal device and a storage medium, wherein the data collection method comprises the following steps: if an interference event is monitored in a data collection process and the interference event is an interference event to be processed in real time, the collected data is saved, the interference event is accessed, and background data collection is started at the same time of accessing the interference event; and target collection data is obtained according to a data segment collected before the interference event is accessed and a data segment collected in the background. The application can start background continuous data collection while processing the interference event to be processed in real time, that is, the application can process the event to be processed in real time in time, continuously collect data, not affect a measurement process, ensure that effective information collected before the interference event occurs is not discarded, avoid the situation that some effective data is missed, effectively improve the reliability and availability of the collected data, and shorten the total time consumption of measurement.

Description

Technical Field

[0001] This application relates to the field of electronics, and more particularly to a data acquisition method, terminal device, and storage medium. Background Technology

[0002] With the rapid development of electronic technology, wearable devices are capable of performing an increasing number of functions, such as collecting various physiological data of the human body, including electrocardiogram (ECG) signals and blood oxygen saturation. Assisted by machine learning methods, multiple effective single measurements over a relatively long period can effectively help screen for paroxysmal cardiovascular diseases, such as atrial fibrillation and premature beats. Traditional wearable devices, when encountering interference such as call interference or data transmission interference during a single measurement, will directly block the interference and notify the user only after the measurement is completed. However, directly blocking interference can cause users to miss important information, resulting in some important data not being processed in a timely manner. To ensure timely processing of important information, existing wearable devices interrupt the measurement and restart it after the interference subsides. However, interrupting the measurement makes it difficult to accumulate a sufficient number of effective measurements over a long period of monitoring, easily missing paroxysmal symptoms, and restarting the measurement may also lead to the loss of some effective data.

[0003] It is evident that the traditional data collection process for wearable devices, while ensuring that important information is processed in a timely manner, is prone to missing some effective data, resulting in low reliability and usability of the collected data and long measurement time. Summary of the Invention

[0004] This application provides a data acquisition method, terminal device, and storage medium, which solves the problem that traditional wearable device data acquisition processes, while ensuring that important information is processed in a timely manner, are prone to missing some effective data, resulting in low reliability and usability of the acquired data and long measurement time.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a data acquisition method is provided, which may include:

[0007] If an interference event is detected during the data acquisition process and the interference event is an interference event that needs to be processed in real time, the acquired data is saved, the interference event is connected, and background data acquisition is started at the same time as the interference event is connected.

[0008] The target data is obtained by combining the data segments collected before the interference event and the data segments collected in the background.

[0009] Here, the data collected can be used to help screen for paroxysmal cardiovascular disease.

[0010] The data acquisition method provided in this application embodiment can continuously acquire data in the background while handling interference events that need to be processed in real time. After the interference ends, the data segments before the interference event and the data segments acquired in the background are spliced ​​together to obtain the target acquisition data. This method can handle events that need to be processed in real time in a timely manner, and can continuously acquire data without affecting the measurement process. It can also ensure that the valid information acquired before the interference arrives is not discarded, so that the measurement process for screening paroxysmal cardiovascular diseases can be carried out continuously. This effectively avoids the situation of missing some valid data, improves the accuracy of the analysis results of paroxysmal cardiovascular disease analysis based on the target acquisition data, effectively improves the reliability and availability of data, and shortens the total measurement time.

[0011] In one possible implementation of the first aspect, if an interference event is detected during data acquisition and the interference event is an interference event to be processed in real time, the acquired data is saved, and the interference event is accessed. After starting background data acquisition while accessing the interference event, the method further includes:

[0012] If there are interfering data segments in the data segments collected by the background, delete the interfering data segments to obtain valid data segments;

[0013] Accordingly, obtaining the target data based on the data segments collected before the interference event and the data segments collected in the background includes:

[0014] The data fragments collected before the interference event are connected are spliced ​​together with the valid data fragments to obtain the target collected data.

[0015] In the above implementation, since there may be interference with the collected data during the access interference event (such as mobile terminal devices), when there are interfering data segments in the data segments collected in the background, the interfering data segments are deleted, and then the saved data segments are spliced ​​with the valid data segments with the interfering data segments deleted to obtain the target collected data. This can effectively reduce data interference and improve the accuracy of the analysis results of paroxysmal cardiovascular disease analysis based on the target collected data.

[0016] In one possible implementation of the first aspect, before deleting interfering data segments from the data segments collected in the background to obtain valid data segments, the method further includes:

[0017] Collect motion data and determine the motion amplitude of the motion data based on the motion data;

[0018] Based on the motion amplitude of the motion data, determine the target data segment that satisfies the preset motion state from the data collected simultaneously with the motion data.

[0019] If the interference level of the target data segment exceeds the preset interference range, then the target data segment is determined to be an interfering data segment.

[0020] In the above implementation, combining motion data and target data segments can effectively determine whether there are interfering data segments in the data segments collected in the background.

[0021] In one possible implementation of the first aspect, obtaining the target collected data based on data segments collected before the interference event and data segments collected in the background includes:

[0022] The target collected data is obtained by splicing the data segments collected before the interference event and the data segments collected in the background.

[0023] In the above implementation, data segments are spliced ​​together based on the acquisition time to obtain a continuous collection of data, which is the target collection data used for subsequent data analysis.

[0024] In one possible implementation of the first aspect, if an interference event is detected during data acquisition and the interference event is an interference event to be processed in real time, the acquired data is saved and the interference event is connected. Before starting background data acquisition while connecting the interference event, the method further includes:

[0025] Whether any interference events occur during the monitoring data collection process;

[0026] If an interference event occurs during data acquisition, it is determined whether the interference event is an interference event that needs to be processed in real time.

[0027] In the above implementation, by monitoring in real time whether interference events occur during the data acquisition process, and identifying whether the interference event is an interference event that needs to be processed in real time, the appropriate processing strategy can be selected according to the type of interference event. This enables continuous collection of data to help screen paroxysmal cardiovascular diseases, effectively improving the reliability and availability of the data and shortening the total time.

[0028] In one possible implementation of the first aspect, determining whether an interference event is one that needs to be processed in real time if an interference event occurs during data acquisition includes:

[0029] Obtain the priority of the interference event;

[0030] If the priority of the interference event is the first preset priority level, then the interference event is determined to be an interference event to be processed in real time.

[0031] If the priority of the interference event is the second preset priority level, then the interference event is determined to be an interference event that is not to be processed in real time.

[0032] In the above implementation, the priority of each interference event can be preset. When an interference event occurs, the priority of the interference event can be determined. Then, based on the priority of the interference event, the corresponding processing strategy can be selected to improve the reliability and availability of data acquisition during the data acquisition process and shorten the total time.

[0033] In one possible implementation of the first aspect, the data acquisition method further includes:

[0034] If an interference event is detected during the acquisition process and the interference event is not an interference event to be processed in real time, the interference event will be connected after the measurement is completed.

[0035] In the above implementation, during the data acquisition process, interference events that are not to be processed in real time can be temporarily ignored, and data acquisition can continue until the end of the current measurement without affecting the measurement process. Interference events are then connected after the measurement is completed, thereby ensuring that interference events can be processed in a timely manner and are not ignored.

[0036] Secondly, embodiments of this application provide a terminal device, including:

[0037] The first processing unit is configured to, if an interference event is detected during the data acquisition process and the interference event is an interference event that needs to be processed in real time, save the acquired data, access the interference event, and start background data acquisition at the same time as accessing the interference event.

[0038] The splicing unit is used to obtain target collected data based on the data segments collected before the interference event and the data segments collected after the interference event.

[0039] In one possible implementation of the second aspect, the terminal device further includes a deletion unit, which is used to delete interfering data segments if there are interfering data segments in the data segments collected in the background, thereby obtaining valid data segments. Correspondingly, the splicing unit is specifically used to splice the data segments collected before the interference event with the valid data segments to obtain the target collected data.

[0040] In one possible implementation of the second aspect, the terminal device further includes a first determining unit, a second determining unit, and a verification unit.

[0041] The first determining unit is used to collect motion data and determine the motion amplitude of the motion data based on the motion data.

[0042] The second determining unit described above is used to determine, based on the motion amplitude of the motion data, a target data segment that satisfies a preset motion state in the data collected simultaneously with the motion data.

[0043] The aforementioned verification unit is used to determine that the target data segment is an interfering data segment if the interference level of the target data segment exceeds a preset interference range.

[0044] In one possible implementation of the second aspect, the splicing unit is specifically used to splice data according to the acquisition time of the data segment collected before the interference event and the acquisition time of the data segment collected in the background, so as to obtain the target collected data.

[0045] In one possible implementation of the second aspect, the aforementioned terminal device further includes a monitoring unit and an identification unit.

[0046] The aforementioned monitoring unit is used to monitor whether any interference events occur during the data acquisition process.

[0047] The aforementioned identification unit is used to determine whether an interference event is an interference event that needs to be processed in real time if an interference event occurs during the data acquisition process.

[0048] In one possible implementation of the second aspect, the identification unit includes a priority acquisition unit and a judgment unit.

[0049] The priority acquisition unit is used to acquire the priority of the interference event.

[0050] The judgment unit is used to determine that if the priority of the interference event is a first preset priority level, the interference event is an interference event to be processed in real time; if the priority of the interference event is a second preset priority level, the interference event is determined to be an interference event not to be processed in real time.

[0051] In one possible implementation of the second aspect, the terminal device further includes a second processing unit, which is configured to access the interference event after the measurement is completed if an interference event is detected during the acquisition process and the interference event is not an interference event to be processed in real time.

[0052] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the data acquisition method as described in the first aspect above.

[0053] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the data acquisition method described in the first aspect above.

[0054] Fifthly, embodiments of this application provide a computer program product that, when run on a terminal device, causes the terminal device to execute the data acquisition method described in any one of the first aspects.

[0055] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0057] Figure 1 A schematic diagram of the hardware structure of a terminal device to which a data acquisition method provided in this application embodiment is applicable;

[0058] Figure 2 A structural block diagram of a data acquisition system provided in one embodiment of this application;

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

[0060] Figure 4 A schematic flowchart illustrating the process of identifying interference events to be processed in real time, provided for embodiments of this application;

[0061] Figure 5 A schematic diagram of the data structure of the target collected data obtained by splicing data segments collected before the access interference event and data segments collected in the background, as provided in an embodiment of this application;

[0062] Figure 6 This is a schematic diagram of the data structure of the target acquisition data obtained by splicing together data segments collected before the access interference event and valid data segments, as provided in an embodiment of this application.

[0063] Figure 7 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0064] Figure 8 This is a schematic diagram of another terminal device provided in an embodiment of this application. Detailed Implementation

[0065] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0066] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0067] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0068] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0069] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0070] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0071] The data acquisition method provided in this application can be applied to terminal devices. Terminal devices can be wearable devices, mobile phones, tablets, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), and other mobile terminals. This application does not impose any restrictions on the specific type of terminal device.

[0072] For example, the terminal device may specifically be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, handheld communication device, handheld computing device and / or other device for network communication on a wireless system, as well as next-generation communication systems, such as mobile terminals in 5G networks or mobile terminals in future evolved Public Land Mobile Network (PLMN) networks.

[0073] As an example and not a limitation, when the terminal device is a wearable device, the term "wearable device" can also refer to any device that utilizes wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large sizes, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses. They also include devices focused on a specific application function that require interaction with other devices such as smartphones, such as smart bracelets and smart jewelry capable of collecting human physiological data, human movement data, and monitoring vital signs.

[0074] Please see Figure 1 , Figure 1 This is a schematic diagram of the hardware structure of a terminal device to which a data acquisition method provided in this application embodiment applies. For example... Figure 1 As shown, the terminal device 100 can be a wearable device, or a mobile terminal such as a mobile phone or tablet. Specifically, this application takes the aforementioned terminal device 100 as a wearable device as an example. The terminal device 100 may specifically include: a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a short-range wireless communication module 170, a processor 180, and a power supply 190, etc. Those skilled in the art will understand that... Figure 1 The structure of the terminal device 100 shown does not constitute a limitation on the terminal device. The terminal device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0075] The following is combined Figure 1 A detailed description of each component of the terminal device 100 is provided below:

[0076] RF circuit 110 can be used to send and receive information, or to receive and send signals during a call. Specifically, it receives downlink information from the base station and processes it with processor 180; additionally, it sends uplink data to the base station. Typically, RF circuitry includes, but is not limited to, antennas, at least one amplifier, transceiver, coupler, low-noise amplifier (LNA), duplexer, etc. Furthermore, RF circuit 110 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0077] The memory 120 can be used to store software programs and modules. The processor 180 executes various functional applications and data processing of the terminal device 100 by running the software programs and modules stored in the memory 120. The memory 120 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function (such as human physiological data analysis function, human motion data analysis function, etc.). The data storage area may store data created based on the use of the terminal device 100 (human physiological data, motion data of the collected human body parts, etc.). For example, when the terminal device 100 is a wearable device, the wearable device can store the data collected by sensors in its data storage area; when the terminal device 100 is a mobile terminal such as a mobile phone or tablet, the mobile terminal can receive data sent by the wearable device and store the data in the mobile terminal's data storage area. In addition, the memory 120 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0078] The input unit 130 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the terminal device 100. Specifically, the input unit 130 may include a touch panel 131 and other input devices 132. The touch panel 131, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 131), and drive the corresponding connection devices according to a pre-set program.

[0079] Display unit 140 can be used to display information input by the user or information provided to the user, as well as various menus of terminal device 100, such as outputting received electrocardiogram signals. Display unit 140 may include display panel 141, optionally configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar display panel 141. Further, touch panel 131 may cover display panel 141. When touch panel 131 detects a touch operation on or near it, it transmits the information to processor 180 to determine the type of touch event. Subsequently, processor 180 provides corresponding visual output on display panel 141 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 131 and the display panel 141 are two separate components to realize the input and output functions of the terminal device 100. However, in some embodiments, the touch panel 131 and the display panel 141 can be integrated to realize the input and output functions of the terminal device 100.

[0080] The terminal device 100 may also include at least one sensor 150. For example, when the mobile terminal 100 is a wearable device, the sensor 150 may include, for example, a motion sensor, an electrocardiogram sensor, etc. Specifically, as a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and when stationary, it can detect the magnitude and direction of gravity. It can be used for applications that identify the posture of the terminal device 100 (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. As for other sensors that may be configured on the terminal device 100, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described in detail here.

[0081] Audio circuit 160, speaker 161, and microphone 162 provide an audio interface between the user and terminal device 100. Audio circuit 160 converts received audio data into electrical signals and transmits them to speaker 161, where speaker 161 converts them into sound signals for output. On the other hand, microphone 162 converts collected sound signals into electrical signals, which are then received by audio circuit 160, converted into audio data, and then processed by processor 180 before being transmitted via RF circuit 110 to, for example, another terminal device 100, or the audio data can be output to memory 120 for further processing.

[0082] Terminal device 100 can communicate wirelessly with other devices through short-range wireless communication module 170. For example, short-range wireless communication module 170 can integrate at least one of near-field communication module, Bluetooth communication module, and Wireless Fidelity (WiFi) module. For example, when terminal device 100 is a wearable device, the wearable device can establish a wireless communication connection with mobile terminals such as mobile phones and tablets through the short-range wireless communication module, and send preset human physiological data and / or motion data of the collected human body parts collected by sensors to the mobile terminal; when terminal device 100 is a mobile terminal such as a mobile phone or tablet, the mobile terminal can establish a wireless communication connection with the wearable device through the short-range wireless communication module, and receive preset human physiological data and / or motion data of the collected human body parts sent by the wearable device.

[0083] Understandably, despite Figure 1 As not shown, terminal device 100 may further include a wired communication interface, such as a Universal Serial Bus (USB) interface. Terminal device 100 can establish a wired communication connection with other terminal devices 100 through the wired communication interface and conduct wired communication. For example, when terminal device 100 is a wearable device, the wearable device can establish a wired communication connection with mobile terminals such as mobile phones and tablets through the USB interface, and send preset human physiological data and / or motion data of the collected human body parts, etc., collected by sensors to the mobile terminal through the USB data cable; when terminal device 100 is a mobile terminal such as a mobile phone or tablet, the mobile terminal can receive preset human physiological data and / or motion data of the collected human body parts, etc., sent by the wearable device through the USB interface.

[0084] The processor 180 is the control center of the terminal device 100. It connects to various parts of the terminal device 100 via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 120, and by calling data stored in the memory 120, it performs various functions and processes data of the terminal device 100, thereby providing overall monitoring of the terminal device 100. Optionally, the processor 180 may include one or more processing units; preferably, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 180.

[0085] The terminal device 100 also includes a power supply 190 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 180 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0086] Please see Figure 2 , Figure 2 This is an exemplary structural block diagram of a data acquisition system provided in an embodiment of this application. The data acquired by the data acquisition system is mainly used to help screen for paroxysmal cardiovascular diseases, such as... Figure 2 As shown, the data acquisition system includes a mobile terminal 210 and a wearable device 220. The wearable device 220 can establish a wireless communication connection with the mobile terminal 210 via short-range wireless communication, or it can establish a wired communication connection with the mobile terminal 210 via wired communication. This embodiment does not limit the specific communication method between the wearable device 220 and the mobile terminal 210.

[0087] Specifically, when a user wears the wearable device 220 and activates its data acquisition function, the wearable device 220 can collect data from the user through its built-in sensors. The data can be configured according to actual needs; for example, the data can be the user's electrocardiogram signal, acceleration motion data (to help identify interference data), etc.

[0088] Wearable device 220 can upload sensor data to mobile terminal 210. For example, wearable device 220 can establish a communication connection with mobile terminal 210 via short-range wireless communication or wired communication, and upload sensor data to mobile terminal 210. Mobile terminal 210 can store the sensor data from wearable device 220. Here, mobile terminal 210 can serve as a device for data processing, data analysis, and measurement result display. Wearable device 220 can send the collected data to mobile terminal 210, which processes the data (e.g., performs rectangular filtering, smoothing and noise reduction, interference data removal, data stitching, etc.), and analyzes whether the user has paroxysmal cardiovascular disease based on existing machine learning methods. The measurement results are then displayed through the display unit of mobile terminal 210 or through a speaker for voice notification. It should be noted that the above is only an example of how to display measurement results and is not intended to limit this application. Other methods can also be used to display measurement results in this embodiment, and this embodiment does not particularly limit this.

[0089] Furthermore, the aforementioned mobile terminal 210 can also function solely as a device for verifying the wearable device 220. The wearable device is authenticated using the mobile terminal 210, and once logged in, it is bound to the mobile terminal 210. The bound wearable device can then receive call notifications, SMS notifications, instant messaging notifications, and other information from the mobile device. Here, the aforementioned data collection, data processing, data analysis, and measurement result display are implemented by the wearable device 220. Specifically, when the wearable device bound to the mobile terminal 210 activates its measurement function (i.e., begins data collection), it can collect data to help screen for paroxysmal cardiovascular diseases. The collected data is then processed (e.g., rectangular filtering, smoothing and denoising, removing interfering data, data splicing, etc.). Based on existing machine learning methods, the processed data is analyzed to determine whether the user has paroxysmal cardiovascular diseases. The measurement results are then displayed through the display unit of the wearable device 220 or via a speaker for voice notification. It should be noted that the above is merely an example illustrating the method of displaying measurement results and is not intended to limit this application. Other methods can be used to display measurement results in this embodiment, and this embodiment does not impose any particular limitation on this method.

[0090] Furthermore, the wearable device 220 can also process the data it collects and then upload the processed data to the mobile terminal 210 for data analysis. After data analysis, the mobile terminal 210 can display the measurement results. Understandably, the mobile terminal 210 can also send the analyzed measurement results to the wearable device 220 for display.

[0091] It is understood that the above data acquisition system may also include only wearable device 220, which can realize call function and information sending and receiving function, and at the same time, wearable device 220 also has data acquisition function, data processing function, data analysis function and measurement result display function.

[0092] The following embodiments will use terminal device 100 as an example to illustrate the data acquisition method provided in the embodiments of this application.

[0093] Please see Figure 3 , Figure 3 This is a schematic flowchart illustrating a data acquisition method provided in an embodiment of this application. In this embodiment, the execution subject of the process is a terminal device, which is used as an example and not as a limitation. The terminal device can be, for example, a terminal device with the following characteristics. Figure 2 The wearable device 220 can also be as follows: Figure 2 The mobile terminal 210.

[0094] like Figure 3 As shown, the data acquisition method provided in this embodiment specifically includes S110 to S190, which are detailed below:

[0095] S110: Start the data acquisition function.

[0096] In this embodiment, when the terminal device is a wearable device, i.e., the entity executing the process is a wearable device, the user can activate the wearable device's data acquisition function after wearing it. Once activated, the wearable device can collect physiological data (such as electrocardiogram signals) from its built-in sensors. The user can initiate the measurement function by sending a command to the wearable device via a mobile terminal, or directly through the device's activation mechanism, such as pressing a button or control to generate a corresponding activation command. Furthermore, in addition to collecting physiological data, the measurement function can also collect motion data from specific locations on the body. This motion data can be used to assist in detecting whether the user is moving the wearable device and whether the motion amplitude meets a preset motion state (such as answering a phone call).

[0097] In this embodiment, the sensor can be a sensor installed in a wearable device. The specific type of data can be set according to actual needs and is not limited here. For example, when it is necessary to detect a preset physiological characteristic of the human body, the data can include human physiological data that can characterize the preset physiological characteristic. For instance, when it is necessary to detect the activity characteristics of the human heart, the data can include electrocardiogram (ECG) signals that can characterize the activity characteristics of the human heart; or, when it is necessary to detect the motion state of the human body, the data can also include motion data that can characterize the motion state of the human body, such as human acceleration.

[0098] In practical applications, different sensors corresponding to different data can be configured in wearable devices. For example, when the data includes human electrocardiogram (ECG) signals, an ECG sensor can be configured in the wearable device to collect these signals. This ECG sensor can include, but is not limited to, a photoplethysmograph (PPG) sensor or an electrocardiogram (ECG) sensor. Specifically, as an example and not a limitation, when the wearable device is an electronic device such as a wristband or watch that can directly contact the user's skin, and the ECG sensor is a PPG sensor, the PPG sensor can be located in the area near the back of the wristband or watch face. This allows the PPG sensor to collect the user's ECG signals based on changes in blood volume at the wearing site when the user wears the wristband or watch, thus bringing the back of the watch face into contact with the user's skin. Furthermore, when collecting electrocardiogram (ECG) signals from the human body, if the data also includes motion data of the body part being collected, motion sensors for collecting human motion data can be configured in the wearable device. These motion sensors can include, but are not limited to, accelerometers. The body part being collected from is the part of the body where the wearable device is worn.

[0099] In this embodiment, when a user wears a wearable device and activates its data acquisition function, the wearable device can control corresponding sensors to collect data specific to the user. For example, when the data includes the user's electrocardiogram (ECG) signal, the user can activate the wearable device's ECG signal acquisition function. When the wearable device detects that the user has activated the ECG signal acquisition function, it controls the ECG sensor to collect the user's ECG signal. The ECG signal collected by the sensor is the data to be collected in this application. When the data also includes motion data of the body part being collected, the user can activate the wearable device's motion data acquisition function. When the wearable device detects that the user has activated the motion data acquisition function, it controls the motion sensor to collect the motion data of the user's body part being collected.

[0100] In this embodiment, when the terminal device is a mobile terminal such as a mobile phone or tablet, that is, when the execution subject of the process is a mobile terminal such as a mobile phone or tablet, the above-mentioned start data collection function can be achieved by sending a command to the wearable device to start the data collection function through the mobile terminal.

[0101] In this embodiment, once the data acquisition function is activated, the terminal device can perform relevant data acquisition, and the terminal device can also store the acquired data in local storage.

[0102] In this embodiment, when the terminal device is a wearable device, i.e., the entity executing the process is a wearable device, the wearable device can store the data from the sensors in its local memory. Based on this, when performing data analysis based on the collected data, the wearable device can retrieve the data from its local memory. In another possible implementation of this embodiment, when the terminal device is a mobile terminal such as a mobile phone or tablet, i.e., the entity executing the process is a mobile terminal such as a mobile phone or tablet, the wearable device can upload the data from the sensors to the mobile terminal. The mobile terminal can store the data sent by the wearable device in its local memory. Based on this, when performing data analysis based on the collected data, the mobile terminal can retrieve the data from its local memory.

[0103] S120: Monitor whether any interference events occur during the data acquisition process; if an interference event occurs during the data acquisition process, execute S130; otherwise, continue monitoring until the measurement ends.

[0104] In this embodiment, because the measurement process takes a relatively long time, interference events are prone to occur during the measurement process. Therefore, during data acquisition, the terminal device will also monitor for interference events in real time. It is understood that some of the aforementioned interference events require the user to handle them promptly to avoid missing important information, such as real-time call events; some interference events can be handled after the measurement is completed, such as message receiving events; and some interference events are caused by the user moving the terminal device significantly, such as interference events caused by the user answering a phone call.

[0105] In this embodiment, whether an interference event occurs during the mobile terminal's monitoring data collection process can be divided into the following two situations:

[0106] 1. Monitor for any significant interference events.

[0107] Here, the terminal device can clearly identify the type of interference event, such as a real-time call event, a text message retrieval event, an instant messaging message retrieval event, or a push notification event from the terminal device's application. For these interference events, the terminal device can directly determine which specific type of interference event it is. For example, when a phone call comes in (i.e., a real-time call event occurs), the terminal device will receive a corresponding message notification requesting a real-time call, thus confirming that the interference event is a real-time call event. That is, when the terminal device receives a message notification requesting a real-time call, it can determine that a real-time call event has occurred as an interference event during data collection. Similarly, when the terminal device receives a text message, it will receive a corresponding message notification indicating that the interference event is a text message retrieval event. That is, when the terminal device receives a message notification indicating that a text message retrieval event has occurred as an interference event during data collection.

[0108] When monitoring for significant interference events, it is only necessary to monitor whether a corresponding message alert is received. If a corresponding message alert is received, it indicates that an interference event corresponding to that message alert has been detected.

[0109] 2. Monitor for any insignificant interference events.

[0110] During data collection, unintentional actions such as a user raising their hand or trembling during the data acquisition process are not easily identifiable as interference events for the wearable device. These are meaningless interference events. For such events, auxiliary data from the device's sensors (e.g., accelerometers) and existing motion posture algorithms can be used to identify whether an interference event has occurred.

[0111] S130: Determine whether the interference event is an interference event to be processed in real time; if the interference event is an interference event to be processed in real time, execute S140; otherwise, execute S200.

[0112] In this embodiment, when an interference event is detected during data acquisition, the terminal device can determine the type of interference event and then determine whether it is an interference event requiring real-time processing. In this embodiment, the aforementioned interference event requiring real-time processing refers to an event that needs to be processed by the user in real time. Here, the priorities of various interference events can be preset, and then the priority of the interference event can be used to determine whether it is an interference event requiring real-time processing.

[0113] In addition, interference events sent by specific users can be designated as interference events requiring real-time processing. Examples include phone calls and messages (including but not limited to SMS and instant messaging) from specific users. It should be noted that there can be one or more specific users; this is not limited here. A specific user list can be set up, adding specific users to this list. Whenever the terminal device receives an interference event, it retrieves the user who initiated the event and determines whether that user is a specific user. If the user is a specific user (in the specific user list), the interference event is determined to be an interference event requiring real-time processing. If the user is not a specific user (not in the specific user list), the priority of the interference event can be further determined, and then the priority of the interference event can be used to determine whether it is an interference event requiring real-time processing. The aforementioned specific user list can be defined by the user, who adds users they consider important to this list. This list can include user identifiers (such as phone numbers, names, nicknames, etc.). The user identifier is used to determine whether the user who initiated the interference event is in the specific user list; this will not be elaborated further.

[0114] Please see Figure 4 As one implementation of this embodiment, the process of identifying whether an interference event is an interference event to be processed in real time may specifically include the following steps:

[0115] S131: Obtain the priority of the interference event.

[0116] S132: If the priority of the interference event is a first preset priority level, then the interference event is determined to be an interference event to be processed in real time; if the priority of the interference event is a second preset priority level, then the interference event is determined to be an interference event not to be processed in real time.

[0117] In practical applications, the priorities of various interference event types can be preset. Interference events can be pre-categorized into three types: the first type requires real-time processing; the second type can be processed after measurement; and the third type is motion interference. The priority of the first type of interference event is set to the first preset priority level, the priority of the second type is set to the second preset priority level, and the priority of the third type is set to the third preset priority level. When the terminal device detects an interference event, by determining its priority, the corresponding processing strategy can be adopted to handle the interference event.

[0118] It should be noted that the first, second, and third preset priority levels mentioned above are pre-set to distinguish various types of interference events. Users can pre-set which interference events are included in each type of interference event according to actual application needs, and can also pre-set the priority order of each preset priority level. Here, the priority of the first preset priority level can be set to be higher than that of the second preset priority level. Similarly, the priority of the first preset priority level can also be set to be lower than that of the second preset priority level; there is no restriction on this.

[0119] S140: Save the collected data and access the interference event. Simultaneously with accessing the interference event, start background data collection.

[0120] In this embodiment, when it is determined that the interference event is a real-time interference event requiring real-time processing, the already collected data is first saved, for example, by storing the collected data in the terminal device's memory. After the collected data is saved, the interference event requiring real-time processing is accessed, such as a real-time call event. At the same time, the background data collection of the terminal device is started to continue, ensuring that the data collection process is not interrupted.

[0121] S150: Collect motion data and determine the motion amplitude of the motion data based on the motion data.

[0122] S160: Based on the motion amplitude of the motion data, determine the target data segment that satisfies the preset motion state from the data collected simultaneously with the motion data.

[0123] S170: If the interference level of the target data segment exceeds the preset interference range, then the target data segment is determined to be an interference data segment.

[0124] In this embodiment, during data acquisition, the movement of wearable devices or mobile terminals (such as raising a hand or picking up a phone when answering a call) can interfere with the acquired data, resulting in interfering information. By simultaneously acquiring target data (i.e., physiological data used to analyze cardiovascular diseases) and motion data based on motion sensors, target data segments that meet preset motion states are determined based on the motion amplitude of the motion data. The degree of signal interference in the target data segment is then used to determine whether it is an interfering data segment. Since some motion interference has a relatively small impact on the acquired data, it is necessary to further determine whether a target data segment is an interfering data segment based on its signal interference level. Only when the interference level of a target data segment exceeds a preset interference range is it identified as an interfering data segment, preserving as much valid data as possible. Interfering data is deleted during background data saving to avoid its impact on the analysis results and improve the accuracy of the measurement results.

[0125] It should be noted that satisfying the preset motion state means that the motion amplitude of the motion data is greater than a certain preset amplitude threshold. The preset amplitude threshold can be set according to actual needs and is not limited here. It should also be noted that the interference level can be determined based on the signal-to-noise ratio of the collected data. The preset interference range can be set according to actual conditions and is not limited here.

[0126] S180: If there are interfering data segments in the data segments collected by the background, delete the interfering data segments to obtain valid data segments.

[0127] In this case, if interfering data segments are identified in the data segments collected in the background, in order to avoid the influence of interfering data on the analysis results and to improve the accuracy of the measurement results, the interfering data segments can be deleted from the data segments collected in the background, so as to obtain valid data segments without interference.

[0128] S190: Based on the data segments collected before the interference event and the data segments collected in the background, the target data is obtained.

[0129] In this embodiment, the terminal device can splice the data segments collected before the interference event and the data segments collected in the background based on the collection time of each data segment to obtain the target collected data.

[0130] Please see Figure 5DP1 is the data segment collected before the access interference event, and DP2 is the data segment collected in the background. Based on the collection time of the data segment before the access interference event and the collection time of the data segment collected in the background, the terminal device can splice DP1 and DP2 in the order from early to late to obtain the target collected data 1.

[0131] Please see Figure 6 As one possible implementation of this embodiment, if there is an interfering data segment DP3 in the data segment DP2 collected in the background, the interfering data segment DP3 can be deleted from the data segment DP2 collected in the background to obtain the remaining valid data segment DP4. Then, the data segment DP1 collected before the interference event is connected to the valid data segment DP4 and the data segment is spliced ​​together to obtain the target collected data 2.

[0132] It should be noted that the terminal device can first splice the data segments collected before the interference event with the data segments collected in the background, then filter out the interference data segments in the spliced ​​data, and then delete the interference data segments from the spliced ​​data to obtain the target data segment.

[0133] It should also be noted that the data segments collected in the background may contain no interfering data segments, or may contain only one interfering data segment, or may contain multiple interfering data segments; there are no restrictions here. If multiple interfering data segments exist in the data segments collected in the background, deleting these interfering data segments will result in multiple valid data segments. At this point, simply splicing the data according to the collection time of each valid data segment in ascending order will yield a continuous collection of data. This continuous collection of data is the target collection data used for data analysis.

[0134] S200: The interference event is connected after the measurement is completed.

[0135] In this embodiment, if the interference event is determined to be a non-real-time interference event that does not require real-time processing, it can be temporarily ignored during data acquisition. The terminal device can continue acquiring data until the end of the measurement, ensuring that the interference event does not affect the measurement process. The interference event is then received after the measurement is completed, thus guaranteeing timely processing and preventing it from being ignored. For example, a short message notification, instant messaging notification, or application push notification can be displayed after the measurement is finished.

[0136] The data acquisition method provided in this application can simultaneously handle interference events requiring real-time processing while continuously acquiring data in the background. After the interference ends, the data segment before the interference event and the data segment acquired in the background are spliced ​​together to obtain the target acquired data. This method can promptly handle events requiring real-time processing while continuously acquiring data without affecting the measurement process. It also ensures that valid information acquired before the interference occurs is not discarded, avoiding the omission of some valid data. This effectively improves the reliability and availability of the acquired data and shortens the total measurement time. During the data acquisition process, interference events that do not require real-time processing can be temporarily ignored, and data acquisition can continue until the end of the current measurement without affecting the measurement process. Interference events are then integrated after the measurement ends, ensuring that interference events are handled promptly and not ignored. Different processing strategies are adopted for interference events of different priority levels, thereby improving the efficiency of data acquisition while ensuring that important information is not missed. This effectively solves the problem that traditional wearable device data acquisition processes, while ensuring timely processing of important information, are prone to missing some valid data, resulting in low reliability and availability of acquired data and long measurement time.

[0137] Corresponding to the data acquisition method described in the above embodiments, Figure 7 This diagram illustrates a structural block diagram of a terminal device according to an embodiment of this application. The terminal device includes units used to perform the steps described in the above embodiments. For details, please refer to the relevant descriptions in the above embodiments. For ease of explanation, only the parts relevant to the embodiments of this application are shown. In practical applications, this terminal device can be a wearable device, or a mobile terminal such as a mobile phone or tablet. Please refer to... Figure 7 The terminal device 100 includes a first processing unit 110 and a splicing unit 120. Wherein:

[0138] The first processing unit 110 is used to save the collected data and access the interference event if an interference event is detected during the data acquisition process and the interference event is an interference event to be processed in real time. At the same time as accessing the interference event, background data acquisition is started.

[0139] The splicing unit 120 is used to obtain target data based on the data segments collected before the interference event and the data segments collected after the interference event.

[0140] In one embodiment of this application, the terminal device further includes a deletion unit, which is used to delete interfering data segments if there are interfering data segments in the data segments collected in the background, thereby obtaining valid data segments. Correspondingly, the splicing unit is specifically used to splice the data segments collected before the interference event with the valid data segments to obtain the target collected data.

[0141] In one embodiment of this application, the terminal device further includes a first determining unit, a second determining unit, and a verification unit. Wherein:

[0142] The first determining unit is used to collect motion data and determine the motion amplitude of the motion data based on the motion data.

[0143] The second determining unit is used to determine, based on the motion amplitude of the motion data, a target data segment that satisfies a preset motion state from the data collected simultaneously with the motion data.

[0144] The verification unit is used to determine that the target data segment is an interfering data segment if the interference level of the target data segment exceeds a preset interference range.

[0145] In one embodiment of this application, the splicing unit is specifically used to splice data according to the acquisition time of the data segment collected before the interference event and the acquisition time of the data segment collected in the background, so as to obtain the target collected data.

[0146] In one embodiment of this application, the terminal device further includes a monitoring unit and an identification unit. Wherein:

[0147] The monitoring unit is used to monitor whether any interference events occur during the data acquisition process.

[0148] The identification unit is used to determine whether an interference event is an interference event that needs to be processed in real time if an interference event occurs during the data acquisition process.

[0149] In one embodiment of this application, the identification unit includes a priority acquisition unit and a judgment unit. Wherein:

[0150] The priority acquisition unit is used to acquire the priority of the interference event.

[0151] The judgment unit is used to determine that if the priority of the interference event is a first preset priority level, the interference event is an interference event to be processed in real time; if the priority of the interference event is a second preset priority level, the interference event is determined to be an interference event not to be processed in real time.

[0152] In one embodiment of this application, the terminal device further includes a second processing unit, which is used to access the interference event after the measurement is completed if an interference event is detected during the acquisition process and the interference event is not an interference event to be processed in real time.

[0153] As can be seen from the above, the terminal device provided in this application embodiment can start continuous background data collection while processing interference events to be processed in real time. After the interference ends, the data segments before the interference event and the data segments collected in the background are spliced ​​together to obtain the target data. This means that it can process events that need to be processed in real time in a timely manner, collect data continuously without affecting the measurement process, and ensure that the valid information collected before the interference arrives is not discarded, avoiding the situation of missing some valid data. This effectively improves the reliability and availability of the collected data and shortens the total measurement time.

[0154] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a terminal device provided in another embodiment of this application. For example... Figure 8 As shown, the terminal device 100 of this embodiment includes: at least one processor 80 ( Figure 8 (Only one is shown in the diagram), memory 81, and computer program 82 stored in the memory 81 and executable on the at least one processor 80, wherein the processor 80 executes the computer program 82 to implement the steps in any of the above-described data acquisition method embodiments.

[0155] The terminal device 100 may be a desktop computer, laptop, handheld computer, or cloud server, etc. This terminal device may include, but is not limited to, a processor 80 and a memory 81. Those skilled in the art will understand that... Figure 8 This is merely an example of terminal device 100 and does not constitute a limitation on terminal device 100. It may include more or fewer components than shown in the figure, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0156] The processor 80 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0157] In some embodiments, the memory 81 may be an internal storage unit of the terminal device 100, such as a hard disk or memory of the terminal device 100. In other embodiments, the memory 81 may be an external storage device of the terminal device 100, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device 100. Furthermore, the memory 81 may include both internal and external storage units of the terminal device 100. The memory 81 is used to store the operating system, applications, boot loader, data, and other programs, such as the program code of the computer program. The memory 81 can also be used to temporarily store data that has been output or will be output.

[0158] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0159] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0160] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the above-described data acquisition method.

[0161] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to perform the steps in the above-described data acquisition method.

[0162] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0163] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0164] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0165] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0166] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0167] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data acquisition method, characterized in that, The data acquisition method is applied to a wearable device, which is used to collect physiological data. The data acquisition method includes: After the data acquisition function is started, monitor whether any interference events occur during the data acquisition process. The interference events are those that interfere with the data acquisition function. If the aforementioned interference event occurs during data acquisition, it is determined whether the interference event is an interference event that needs to be processed in real time. If the interference event is detected during the data acquisition process and the interference event is an interference event that needs to be processed in real time, then the acquired data is saved, the interference event is processed, and background data acquisition is started while the interference event is being processed. The target collected data is obtained by splicing the data segments collected before the interference event is processed and the data segments collected in the background.

2. The data acquisition method according to claim 1, characterized in that, If an interference event is detected during data acquisition and the interference event is one that requires real-time processing, then the acquired data is saved, and the interference event is processed. After starting background data acquisition while processing the interference event, the process further includes: If there are interfering data segments in the data segments collected by the background, delete the interfering data segments to obtain valid data segments; Accordingly, the step of splicing data based on the acquisition time of the data segment collected before processing the interference event and the acquisition time of the data segment collected in the background to obtain the target acquired data includes: The data fragments collected before the interference event are processed are combined with the valid data fragments to obtain the target collected data.

3. The data acquisition method according to claim 2, characterized in that, Before deleting interfering data segments from the data collected in the background to obtain valid data segments, the process also includes: Collect motion data and determine the motion amplitude of the motion data based on the motion data; Based on the motion amplitude of the motion data, determine the target data segment that satisfies the preset motion state from the data collected simultaneously with the motion data. If the interference level of the target data segment exceeds the preset interference range, then the target data segment is determined to be an interfering data segment.

4. The data acquisition method according to claim 1, characterized in that, If an interference event occurs during data acquisition, determining whether the interference event is one that needs to be processed in real time includes: Obtain the priority of the interference event; If the priority of the interference event is the first preset priority level, then the interference event is determined to be an interference event to be processed in real time. If the priority of the interference event is the second preset priority level, then the interference event is determined to be an interference event that is not to be processed in real time.

5. The data acquisition method according to any one of claims 1 to 4, characterized in that, The data acquisition method further includes: If an interference event is detected during the acquisition process and the interference event is not to be processed in real time, the interference event will be processed after the measurement is completed.

6. A terminal device, characterized in that, The terminal device is a wearable device, which is used to collect physiological data. The wearable device includes: The detection unit is used to monitor whether any interference events occur during the data acquisition process after the data acquisition function is started. The interference events are events that interfere with the data acquisition function. The identification unit is used to determine whether the interference event is an interference event that needs to be processed in real time if the interference event occurs during the data acquisition process. The first processing unit is configured to, if an interference event is detected during the data acquisition process and the interference event is an interference event that needs to be processed in real time, save the acquired data, process the interference event, and start background data acquisition while processing the interference event. The splicing unit is used to splice data according to the acquisition time of the data segment collected before processing the interference event and the acquisition time of the data segment collected in the background to obtain the target acquired data.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the data acquisition method as described in any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the data acquisition method as described in any one of claims 1 to 5.

Images