CN117707470A - Data processing methods, readable storage media, electronic equipment - Google Patents

Abstract

This application relates to the field of data processing technology and discloses a data processing method, a readable storage medium, and an electronic device. The data processing method of the present application is applied to at least one processor in an electronic device, and the electronic device includes a sensor; the method includes: the processor obtains the first data reported by the sensor, and the first data has the first frame number; the processor determines the When one frame is different from the target number of frames required by the processor to run the application, and the application has accuracy requirements for the speed of reporting the first data; the processor processes the first data into second data that is the same as the target number of frames, To meet the application implementation related functions. Through the method of this application, the processor can dynamically adjust the speed of data reported to the application program. When the application program needs to obtain data at a high-precision speed, the processor can ensure that the speed at which the application program obtains sensor data meets the target requirements.

Description

Data processing methods, readable storage media, electronic devices

Technical field

This application relates to the field of data processing technology, and in particular to a data processing method, a readable storage medium, and an electronic device.

Background technique

Nowadays, electronic devices such as smartphones and tablets are equipped with multiple sensors, such as acceleration sensors, gyroscopes, etc. These sensors can usually report the collected data to the processor through interrupts, and the processor runs the corresponding application program to realize the functions of the corresponding application program.

In some scenarios, applications have higher accuracy requirements for sensor data output rate (ODR). For example, in scenarios such as activity recognition of pedometers or compatibility test suite (CTS) of electronic devices, the ODR accuracy of the sensor needs to reach ±3%. Due to the characteristics of the sensor, for example, in the capacitance-resistance oscillation circuit of the sensor itself, there will be errors in the resistance and capacitance when transmitting data, which leads to a reduction in the accuracy of the ODR of the sensor itself. Moreover, the higher the ODR situation, the more obvious the ODR error of the sensor becomes.

Currently, most of the sensors on electronic devices such as mobile phones and tablets have the requirement to operate under high ODR. For example, the data output rate of a pedometer needs to be above 1000HZ. At this time, the ODR error of the sensor will become larger, and data loss will occur when the sensor transmits data. This results in substandard data transmission when the sensor is operated in a high ODR scenario, seriously affecting the accuracy of the corresponding functions of the sensor's corresponding application.

Contents of the invention

Embodiments of the present application provide a data processing method, a readable storage medium, and an electronic device.

In a first aspect, embodiments of the present application provide a data processing method, which is applied to at least one processor in an electronic device, and the electronic device includes a sensor; the method includes: acquiring first data reported by the sensor, and the first data has a first Number of frames; determine that the first number of frames satisfies the first condition, where the first condition includes that the first number of frames is different from the number of target reported frames; process the first data into second data, where the second number of frames of the second data The same as the target reporting frame number; perform functions related to the first data based on the second data.

It can be understood that in some embodiments of the present application, when the processor of the electronic device runs the relevant application program, it will send the target speed of the reported data to the sensor because there is an error in the speed of the sensor reporting data. Therefore, when the application has a first condition for the speed of data reporting by the sensor, the processor can adjust the first data reported by the sensor so that the number of frames of the first data meets the target number of frames reported by the application, so as to satisfy the application accurately. Implement related functions. For example, the first data may be acceleration data or sensor data in the following file that has not been adjusted by the processor, and the second data may be acceleration data or sensor data that has been adjusted by the processor in the file described below.

In a possible implementation of the above first aspect, the above method further includes: the first condition further includes at least one of the following: the speed at which the sensor reports the first data reaches the first speed; the speed accuracy at which the sensor reports the first data The requirement is first accuracy.

It can be understood that the first condition may include, for example, that the speed at which the sensor reports the first data reaches the first speed. The first speed may be, for example, the limit speed at which the sensor reports data, or is close to the limit speed, for example, 80% of the limit speed. In other embodiments, the first condition may also be that the application program has accuracy requirements for the speed at which the sensor reports the first data, for example, the sensor is required to accurately report data at the target reporting speed issued by the application program. It can be understood that the first speed may be the target reporting speed or the target ODR below.

In a possible implementation of the above first aspect, the above method further includes: processing the first data into second data, including: corresponding to the first frame number being less than the target reporting frame number, supplementing the first data with the third data , generate second data; corresponding to the number of first frames being greater than the number of target reported frames, delete the fourth data from the first data to generate second data.

It can be understood that in some embodiments of the present application, the processor may process the first data reported by the sensor by, for example, adding frames or deleting the number of frames to generate second data that satisfies the application program.

In a possible implementation of the above first aspect, the above method further includes: the first data includes a plurality of sensor data acquired by the sensor and a timestamp corresponding to each sensor data.

It can be understood that in some embodiments of the present application, the first data includes sensor data and the timestamp corresponding to the sensor data. The sensor reports the sensor data to the processor in order of the timestamps to ensure that the processor obtains the sensor data in order. accuracy.

In a possible implementation of the above first aspect, the above method further includes: corresponding to the first frame number being less than the target reporting frame number, supplementing the first data with third data, and generating the second data, including: according to the first data Sort the multiple sensor data according to the order of the timestamps of each sensor data; divide the sorted multiple sensor data into multiple sensor data subsets, where the number of sensor data subsets is equal to the number of frames of the third data The same, the number of sensor data in each sensor data subset is the same; data interpolation is inserted in the same position of different sensor data subsets to generate the second data.

It can be understood that the first data is divided into multiple sensor data subsets according to the order of timestamps, and the multiple sensor data subsets are also arranged in the order of timestamps. The number of sensor data subsets is related to the number of frames of the third data that need to be supplemented. same. The number of frames of sensor data is the same in each sensor data subset. When performing frame patching, data interpolation can be inserted at the same location in each sensor data subset to generate second data. For example, the first data is divided into 4 sensor data subsets in the order of time stamps, and each sensor data subset includes 3 frames of data. Then when performing frame complementation, data interpolation can be inserted between the 2nd and 3rd frames of each sensor data subset. In this way, the uniformity of supplementing the first data with the third data can be ensured. In other embodiments, the number of frames of sensor data in each sensor data subset may be different. For example, the difference in the number of frames of sensor data in two sensor data subsets is 1. This embodiment is due to the first The number of frames cannot be evenly divided into multiple sensor data subsets.

In a possible implementation of the above first aspect, the above method further includes: generating a data difference value in any one of the following ways: calculating an average of two sensor data at both ends of the sensor data subset as the sensor data subset. Data interpolation between the set and adjacent sensor data subsets; perform data fitting on at least two sensor data at both ends of the sensor data subset to obtain data interpolation between the sensor data subset and adjacent sensor data subsets.

It can be understood that when performing frame filling, the average value of two adjacent sensor data at the position of the filling frame can be obtained as supplementary sensor data. In other embodiments, the supplementary data may also be, for example, fitting multiple sensor data adjacent to the supplementary frame position, thereby obtaining the fitted sensor data at the supplementary frame position as the supplementary data. Obtaining the sensor data at the supplementary frame position through the above method can make the supplementary data more realistic and ensure the accuracy of the sensor data.

In a possible implementation of the above first aspect, the above method further includes: corresponding to the first frame number being greater than the target reporting frame number, deleting the fourth data from the first data, and generating the second data, including: according to the first Sort the multiple sensor data according to the time stamp of each sensor data in the data; from the sorted multiple sensor data, obtain sensor data at intervals of the first number, where the number of acquired sensor data is equal to the number of the first number. The number of frames of the four data is the same; delete the acquired sensor data and generate the second data.

It can be understood that the first data can be arranged according to the order of time stamps, and when deleting the number of frames, the data can be obtained at intervals of the first number. The first number may be determined based on the number of frames of the deleted fourth data and the number of first frames of the first data. For example, the number of first frames is 12, and the number of target reported frames is 10, then the number of frames of the fourth data is 2, that is, 2 frames of data need to be deleted. Then the first number can be set to 5. That is, 1 frame of data is obtained every 5 frames of data, thereby obtaining the 6th frame of data and the 12th frame of data as the deleted data, and the remaining 10 frames of data are used as the second data.

In a possible implementation of the above first aspect, the above method further includes: determining the target reporting frame number based on the first time it takes for the sensor to report the first data and the target reporting speed of the processor.

It can be understood that after the processor sends the target reporting speed to the sensor, it can obtain the target reporting frame number based on the target reporting speed and the first time the sensor reports the first data. The target reporting frame number is the target reporting speed and the first time. product of .

In a second aspect, embodiments of the present application provide an electronic device, including at least one processor and a sensor; at least one processor is configured to: obtain the first data reported by the sensor, where the first data has a first frame number; determine the first frame Whether the number meets the first condition, where the first condition includes that the first frame number is different from the target reported frame number; corresponding to the first frame number meeting the first condition, the first data is processed into the second data, where the second data The second frame number is the same as the target reporting frame number; functions related to the first data are performed based on the second data.

It can be understood that when the processor runs an application to obtain sensor data, the target reporting speed of the sensor data will be sent to the sensor. The sensor needs to report data at the target reporting speed. When the sensor reports the first data at a speed that cannot reach the target reporting speed, the processor can adjust the first data to meet the needs of the application running the sensor, thereby ensuring that the application implements the corresponding Functional accuracy.

In a possible implementation of the second aspect, the method further includes: at least one processor including a first processor and a second processor, wherein the first processor is used to obtain the first data reported by the sensor; The processor determines that the first frame number meets the first condition and processes the first data into second data; the second processor is used to obtain the second data from the first processor and perform functions related to the first data.

It can be understood that in some embodiments of the present application, the second processor may be, for example, an application processor, used to run application programs, such as a pedometer, etc. The first processor may be, for example, a co-processor, used to obtain sensor data and adjust the sensor data. For example, if a pedometer application requires precision in the speed of sensor data reported by the sensor, the coprocessor will supplement or delete some data from the sensor data when obtaining the sensor data reported by the sensor, and then report it to the application for processing. , please refer to the following description for the process of supplementing or deleting data. When the application processor runs the pedometer application, it performs step counting calculations based on the sensor data reported by the coprocessor.

In a third aspect, embodiments of the present application provide a computer-readable storage medium. Instructions are stored on the readable storage medium. When the instructions are executed on a computer, they cause the computer to execute the above-mentioned first aspect and various possible implementations of the first aspect. Provided data processing methods.

Description of the drawings

Figure 1 shows a schematic structural diagram of an electronic device;

Figure 2 shows a timing diagram of a sensor transmitting data to a processor;

Figure 3a shows a schematic structural diagram of an electronic device according to some embodiments of the present application;

Figure 3b shows a timing diagram of a sensor transmitting data to a processor according to some embodiments of the present application;

Figure 4 shows an implementation flow chart of a sensor data processing method according to some embodiments of the present application;

Figure 5 shows an implementation flow chart of another sensor data processing method according to some embodiments of the present application;

Figure 6 shows an interactive flow chart of a sensor data processing process according to some embodiments of the present application;

Figure 7 shows a schematic structural diagram of an electronic device according to some embodiments of the present application;

Figure 8 shows a schematic block diagram of the system software architecture of a mobile phone according to some embodiments of the present application.

Detailed ways

Illustrative embodiments of the present application include, but are not limited to, data processing methods, readable storage media, and electronic devices.

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings and specific implementation modes.

Figure 1 shows a schematic structural diagram of an electronic device 100.

As shown in FIG. 1 , the electronic device 100 includes a processor 110 and a sensor module 180 . Among them, the sensor module 180 includes a memory 13 .

The processor 110 runs the application program and determines the function of the corresponding application program based on the acceleration data obtained from the sensor module 180 . For example, the processor 110 can run a pedometer application, and based on the acceleration data reported by the sensor module 180, implement the pedometer function by extracting gait features from the acceleration data through a pedometer algorithm.

The memory 13 is used to store data detected by the sensor module 180, such as acceleration data. In some embodiments, the memory 13 may store acceleration data through a first in first out (FIFO) queue, and the sensor module 180 may add the detected acceleration data to the FIFO frame by frame. When the data cached in the memory 13 reaches a preset data amount, for example, when a preset number of frames is reached, the sensor module 180 triggers an interrupt and transmits the data in the memory 13 to the processor 110 .

It can be understood that one frame of data may include acceleration data of the sensor module 180 and a timestamp corresponding to the acceleration data.

Since the length of time for the sensor module 180 to collect one frame of data is not fixed, the time required for the data in the memory 13 to be cached to the preset number of frames will also be different each time. That is to say, the interval at which the sensor module 180 triggers an interrupt is different. The ODR of sensor module 180 varies. In this way, if the ODR of the sensor module 180 changes greatly, that is, the accuracy of the ODR of the sensor module 180 is low, the number of frames of data reported by the sensor module 180 to the processor 110 within a unit time also changes greatly, which may cause the application to fail. The program functions abnormally.

For example, FIG. 2 shows a timing diagram in which the sensor module 180 transmits data to the processor 110 .

As shown in FIG. 2 , it is assumed that the sensor module 180 reports to the processor 110 every 20 frames of data cached, that is, an interrupt is triggered every 20 frames of data cached. Assume that the sensor module 180 starts transmitting data from t1=0ms, the first time the interrupt is triggered is t2=200ms, and the second time the interrupt is triggered is t3=440ms. That is to say, from t1 to t2, the ODR of the sensor module 180 is 20 frames/200ms×1000=100 frames/s, that is, 100 frames of data are reported per second. From t2 to t3, the ODR of the sensor module 180 is 20 frames/s. 240ms×1000=83 frames/s, that is, 83 frames of data are reported per second.

If the ODR required by the application is 100 frames/s, that is, the number of data frames that the sensor module 180 needs to report between 0 and t3 should be 440ms×100 frames/s=44 frames. The sensor module 180 actually has two interrupts between 0 and t3, and each interrupt reports 20 frames of data. Therefore, the data actually reported by the sensor module 180 is 40 frames, which is different from the amount of data required by the application, which may cause the step counting data obtained by the application to be inaccurate.

In order to solve the above problems, this application provides a sensor data processing method. When the processor in the electronic device obtains the sensor data required by the application program from the sensor module 180, it can report the data reporting requirements of the application program (such as target ODR, whether When the adjustment conditions are met (high-precision reporting, etc.), the number of data frames reported by the sensor after each interrupt trigger is adjusted to be consistent with the number of data frames corresponding to the target ODR (hereinafter referred to as the target number of reported frames), and then transmitted to the application.

For example, the adjustment condition is when the target ODR reaches a preset value, for example, reaches 80% of the limit ODR of the sensor module 180 . Or the application requires high-precision ODR to report sensor data. After the adjustment conditions are met, the processor adjusts the ODR of the data reported by the sensor, thereby transmitting the sensor data to the application program with the target ODR.

The adjustment method is, for example, when the number of data frames when the sensor reporting interrupt is triggered (hereinafter referred to as the number of cached frames) is less than the target reporting frame number, the processor can supplement the number of data frames reported by the sensor to the target reporting frame by padding frames. The data is then sent to the application. The frame-filling method may be, for example, by performing fitting interpolation based on the frame number data at the frame-filling position.

For another example, the adjustment method is that data overflow occurs in the sensor, that is, the number of frames reported when the sensor triggers an interrupt is greater than the target number of frames reported. The processor can delete some of the frames reported by the sensor to make the number of data frames reported equal to the target number of frames reported, and then transmit it to the application.

Through the data processing method provided by this application, when the data reporting requirements of the application meet the adjustment conditions, the ODR of the data obtained by the application can be the same as the target ODR. This ensures that applications can obtain accurate amounts of data and implement corresponding functions.

In addition, when the application's requirements for the sensor ODR meet the adjustment conditions, the processor starts the above-mentioned adjustment scheme (hereinafter referred to as the ODR adjustment scheme) to ensure the accuracy of the sensor ODR, thereby ensuring the accuracy of the corresponding application function. When the application program's requirements for the ODR of the sensor do not meet the adjustment conditions, the processor turns off the ODR adjustment scheme to ensure the accuracy of the sensor data and meet the application program's requirements for sensor data accuracy.

It should be understood that the number of frames reported by the target can be determined based on the target ODR and the time interval DT between the data reported by the sensor and the data reported last time by the sensor. For example, the target reporting frame number may be the product of the target ODR and DT. For example, assuming that the target ODR is 100 frames/second and DT=200ms, the target number of frames reported is 100 frames/second × 200ms = 20 frames.

Specifically, FIG. 3a shows a schematic structural diagram of an electronic device 100 according to an embodiment of the present application.

As shown in Figure 3a, the electronic device 100 includes a processor 110 and a sensor module 180. The processor 110 includes an application processor 14 and a co-processor 15 , and the sensor module 180 includes a memory 13 .

The memory 13 is used to store sensor data detected by the sensor module 180 . When the data cached in the memory 13 reaches a preset data amount, for example, when a preset number of frames is reached. The sensor module 180 triggers an interrupt and transmits the data in the memory 13 to the coprocessor 15 .

The coprocessor 15 is used to obtain acceleration data from the sensor module 180 and adjust the acceleration data so that the ODR of the sensor module 180 meets the target ODR of the application program. For example, the coprocessor 15 can initiate an ODR adjustment plan to supplement or delete the acceleration data reported by the sensor module 180 so that the ODR of the sensor module 180 meets the target ODR. and report the adjusted sensor data to the application processor 14 .

The application processor 14 is used to run the application program and determine the function of the corresponding application program based on the acceleration data obtained from the coprocessor 15 . For example, the application processor 14 can run a pedometer application program, and based on the acceleration data reported by the coprocessor 15, implement the pedometer function by extracting gait features from the acceleration data through a pedometer algorithm.

Through the electronic device of this embodiment, when the application program has requirements for the ODR accuracy of the sensor module 180, the coprocessor 15 can start the ODR adjustment scheme, thereby adjusting the data reported by the sensor module 180, so that the application processor 14 can obtain the data. The ODR meets the application's target ODR.

FIG. 3b shows a timing diagram in which the sensor module 180 transmits data to the coprocessor 15 according to an embodiment of the present application.

As shown in Figure 3b, assume that the target ODR of the sensor module 180 is 100 frames/second, the target ODR is greater than the preset ODR, and the sensor module 180 triggers an interrupt every 20 frames of data cached, and reports the cached data to the coprocessor 15.

Referring to Figure 3b, the time when the sensor module 180 starts to cache data for the first time is t1=0ms, and the time when it caches 20 frames of data is t2=200ms. That is, the sensor module 180 triggers an interrupt at the 200ms and reports the cached data to Coprocessor 15. At this time, the actual ODR = 20 frames/200ms = 100 frames/second, which is consistent with the target ODR. The coprocessor 15 does not need to process the data and directly transmits it to the application program.

Continuing to refer to Figure 3b, the time when the sensor module 180 triggers the interrupt for the second time is t3=410ms, DT=t3-t2=210ms. At this time, the actual ODR=20 frames/210ms=95.2 frames/second, which is smaller than the target ODR. That is to say, the time for the sensor module 180 to cache 20 frames of data becomes longer, the actual ODR of the sensor module 180 cannot reach the target ODR, and the coprocessor 15 needs to frame the data reported by the sensor module 180 . At this time, the target number of frames to be reported is 100 frames/second × 210ms = 21 frames. The coprocessor 15 can insert one frame of data into the data reported by the sensor module 180 and then report it to the application processor 14. The application processor 14 runs the application. The program enables the application to receive 21 frames of data within 210ms, thereby ensuring that the ODR of the application's data acquisition is the same as the target ODR.

For example, the coprocessor 15 can insert the 30th frame data after the 30th frame in the supplementary frame between the 21st frame and the 40th frame, that is, insert a frame in the middle part of the data reported by the sensor module 180 data.

It should be understood that in other embodiments, the coprocessor 15 can also insert a frame of data at the head or tail of the data reported by the sensor module 180 .

Continuing to refer to Figure 3b, the time when the sensor module 180 triggers the interrupt for the third time is t4=580ms, DT=t4-t3=170ms. At this time, the actual ODR=20 frames/170ms=117.6 frames/second, which is greater than the target ODR. That is to say, the time for the sensor module 180 to cache 20 frames of data becomes shorter, the actual ODR of the sensor module 180 exceeds the target ODR, and the coprocessor 15 needs to delete the data reported by the sensor module 180 . At this time, the target number of frames to be reported is 100 frames/second × 170ms = 17 frames. Therefore, the coprocessor 15 can delete three frames of data from the third interrupt triggered reporting data of the sensor module 180 to ensure the accuracy of the data obtained by the application program. The ODR is the same as the target ODR. For example, the coprocessor 15 can delete the data of the 41st frame, the 50th frame and the 60th frame, so that the application program only obtains 17 frames of data within 170ms.

In this way, it can be guaranteed that the speed at which the application obtains sensor data is the same as the target ODR, thus ensuring the accuracy of the application in implementing the corresponding functions.

Figure 4 shows an implementation flow chart of a sensor data processing method according to an embodiment of the present application.

It can be understood that the sensor data processing method provided by the embodiment of the present application is applied to electronic devices. The electronic devices may include but are not limited to: mobile phones, tablets, computers, smart watches, car-machine conference terminals, desktops, laptops, Handheld computers, netbooks, as well as augmented reality (AR)/virtual reality (VR) devices, smart TVs, smart watches and other wearable devices, servers, portable game consoles, portable music players, reader devices, One or more processors or other electronic devices including sensors are embedded or coupled therein.

It should be understood that the execution subject of each of the following steps may be a co-processor in the electronic device for processing sensor data, such as the co-processor 15 of the aforementioned electronic device 100 . When introducing each step below, the execution subject of each step will not be introduced.

401. Send the target ODR of the application to the sensor.

For example, when the application processor 14 needs to obtain sensor data when running an application program, it will issue a target ODR to the coprocessor 15 , where the target ODR is the speed at which the application program obtains sensor data. The coprocessor 15 sends the target ODR to the sensor, and the sensor transmits the collected sensor data to the coprocessor 15 according to the target ODR.

402, determine whether the target ODR reaches the limit ODR of the sensor.

For example, the sensor itself has extreme ODR data. When the sensor transmits data under the extreme ODR, the ODR will have a large error, and the data transmitted by the sensor needs to be processed. Therefore, when the coprocessor 15 obtains the data reported by the sensor, it needs to determine whether the target ODR reaches the limit ODR. It should be understood that the sensor can only transmit data at the limit ODR. When the target ODR is greater than the limit ODR, the sensor transmits data at the limit ODR.

If the judgment result is yes, for example, the coprocessor 15 detects that the target ODR is greater than the limit ODR and the sensor needs to transmit data with the limit ODR, which will cause a large error, then step 404 is executed to determine whether the target ODR is greater than the actual ODR of the sensor. In order to adjust the ODR of the sensor.

If the judgment result is no, for example, the coprocessor 15 detects that the target ODR does not reach the limit ODR and the error of the sensor when transmitting data is within the allowable range of the application, then step 403 is executed to determine whether the application has turned on high-precision subscription.

403, determine whether the application enables high-precision subscription.

For example, in some embodiments, the application has accuracy requirements for the ODR of the sensor. Therefore, when acquiring sensor data for such applications, it is necessary to ensure the accuracy of the sensor ODR. For example, a whitelist can be stored in the electronic device, so that the coprocessor 15 can determine whether the application program enables high-precision subscription based on the whitelist. For example, when an application obtains sensor data, the coprocessor 15 can determine whether to adjust the data when reporting the data to the application processor 14 by determining whether the corresponding application is in the whitelist.

If the judgment result is yes, for example, the application is in the whitelist, the application has requirements for the ODR accuracy of the sensor. Then execute step 404 to determine whether the target ODR is greater than the actual ODR of the sensor.

If the judgment result is no, for example, the application is not in the whitelist, the application has no special requirements for the ODR accuracy of the sensor, and the error when the sensor transmits data is within the allowable range of the application, then step 407 is executed to report the data.

In other embodiments, high-precision subscriptions may be determined based on a voting mechanism. Taking the acceleration sensor as an example, if the first application, the second application and the third application all need to use the data of the acceleration sensor. The first application and the third application have no accuracy requirements for the ODR of the acceleration sensor, and the target ODR of the first application and the third application do not reach the limit ODR of the acceleration sensor. The second application has accuracy requirements for the ODR of the acceleration sensor. Then, after acquiring the data reported by the acceleration sensor, the coprocessor 15 needs to start the ODR adjustment scheme and adjust the ODR of the acceleration sensor. It should be understood that the voting mechanism may be, for example, that the sensor selects the ODR with the highest accuracy requirement among multiple applications to report sensor data.

In other embodiments, the voting mechanism for high-precision subscriptions can also be set according to the target ODR size of the application. For example, the first application, the second application, and the third application all need to obtain acceleration data from the acceleration sensor. Among them, the first application has the highest target ODR, reaching 1000 Hz. Then the acceleration sensor needs to transmit data at the highest target ODR, that is, transmit data at a speed of 1000Hz. If the sensor's limit ODR is 1000Hz, the coprocessor 15 needs to enable the ODR adjustment scheme to ensure that the speed at which the coprocessor 15 reports data to the application processor 14 is stable at 1000Hz. It should be understood that the voting mechanism may be, for example, that the sensor reports sensor data according to the ODR with the largest target ODR among multiple applications.

It can be understood that in another embodiment, the judgment step of 402 may be reversed from the step of 403. That is, first determine whether the application has turned on high-precision subscription, and then determine whether the application's target ODR reaches the sensor's limit ODR. The numbering sequence and description sequence of each step in this embodiment do not specifically limit the execution order of the steps.

404, determine whether the target ODR is greater than the actual ODR of the sensor.

For example, the sensor caches the collected data into an internal memory. When the data in the memory reaches a preset value, the sensor triggers an interrupt and reports the data cached in the memory to the coprocessor 15 . Each time the sensor triggers an interrupt, it will record the timestamp of the interrupt. The coprocessor 15 can obtain the cache time of each time the sensor caches preset data based on the interrupt timestamp. For example, subtracting the timestamp of the current interrupt triggering from the timestamp of the last triggering interrupt is the cache time of the last time the memory cached a preset amount of data (hereinafter referred to as the actual cache time, also known as the aforementioned DT). If the actual cache time is greater than the cache time of the sensor under the target ODR (hereinafter referred to as the target cache time), it can be determined that the actual ODR of the sensor is less than the target ODR. Similarly, if the coprocessor 15 detects that the actual cache time of the sensor is less than the target cache time, it can mean that the actual ODR of the sensor is greater than the target ODR.

If the judgment result is yes, for example, the coprocessor 15 detects that the actual cache time of the sensor is greater than the target cache time, indicating that the target ODR is greater than the actual ODR, step 406 is executed to frame the sensor data.

If the judgment result is no, for example, the coprocessor 15 detects that the actual cache time of the sensor is less than the target cache time, indicating that the target ODR is less than the actual ODR, step 405 is executed to delete part of the sensor data.

405, delete some sensor data.

For example, when the actual ODR of the sensor is greater than the target ODR, the time for each interrupt triggered by the sensor will be shortened. Therefore, the coprocessor 15 can delete some data from the data reported by the sensor to ensure that the number of frames reported to the application processor 14 is consistent with the target number of frames reported.

For example, for the situation shown in Figure 3 mentioned above, the target ODR is 100 frames/s, and the memory in the sensor triggers an interrupt every 20 frames of data cached, then the target cache time is 200ms. However, it takes 170ms for the sensor to transmit 20 frames of data. At this time, the actual ODR of the sensor is 20 frames/170ms = 118 frames/second, which is greater than the target ODR. At this time, the target number of frames reported is 100 frames/second × 170ms = 17 frames. Therefore, the number of frames actually reported by the sensor is 20 frames - 17 frames = 3 frames more than the number of frames reported by the target. Therefore, the coprocessor 15 needs to delete 3 frames of data from the data reported by the sensor.

For example, the way the coprocessor 15 deletes the frame number data may be to divide the 20 frames of data into two regions, and delete the corresponding data at the endpoint of each region. In other embodiments, the position of the deleted data can also be set according to the timestamp of each frame of data. For example, among 20 frames of data, select 3 groups of data with the shortest timestamps of two adjacent frames of data, and select one frame of data in each group of data to delete. In this way, 3 frames of data can be deleted, so that the remaining 17 frames of data can be deleted. The distribution is more even. It can be understood that this solution does not specifically limit the position where the number of frames is deleted, and the number of frames can be deleted at the corresponding position according to specific needs.

406. Frame complement the sensor data.

For example, when the actual ODR of the sensor is less than the target ODR, the time of each interruption of the sensor will be extended. Therefore, the coprocessor 15 needs to supplement some data to ensure that the speed of reporting data to the application processor 14 meets the target ODR.

For example, if the target ODR is 100 frames/second, the sensor will trigger an interrupt every 20 frames of data cached in the memory 13, that is, the sensor needs to trigger an interrupt every 200ms. However, it takes 240ms for the sensor to transmit 20 frames of data. The actual ODR of the sensor is 20 frames/240ms = 83 frames/second, which is smaller than the target ODR. At this time, the target number of frames reported is 100 frames/second × 240ms = 24 frames. Therefore, the data actually reported by the sensor is 24 frames - 20 frames = 4 frames less than the data reported by the target. Therefore, the coprocessor 15 needs to supplement the data reported by the sensor with 4 frames of data.

The method of supplementing frames can be, for example, dividing 20 frames of data into three regions, and supplementing corresponding data at the endpoints of each region. In other embodiments, the position of the supplementary frame can also be set according to the timestamp of each frame of data, for example, the supplementary frame is performed on the four nodes with the longest timestamps of two adjacent needles. It can be understood that this solution does not specifically limit the position of the supplementary frame, and the supplementary frame can be performed at the corresponding position according to specific needs. The data size of the supplementary frame number may be determined based on data near the supplementary frame position, for example. For example, the coprocessor 15 takes the average of two data adjacent to the complementary frame position as the data of the complementary frame. In other embodiments, the coprocessor 15 can also fit the 20 frames of data to a curve with time as the horizontal axis and the values collected by the sensor as the vertical axis. Then select the value corresponding to the time point of the frame on the curve as the data of the frame, or use the nearest neighbor method, linear interpolation and other methods to complement the frame.

407, report data.

For example, after adjusting the sensor data, the coprocessor 15 can report the sensor data to the application processor 14. The application processor 14 runs the application program and implements corresponding functions based on the sensor data reported by the coprocessor 15. It can be understood that if the sensor data does not need to be adjusted, the coprocessor 15 can directly report the acquired sensor data to the application processor 14 .

In the embodiment of the present application, when the coprocessor 15 needs to obtain sensor data, the ODR adjustment scheme can be enabled according to the needs of the application program. For example, when the target ODR of the application reaches the limit ODR of the sensor, or when the application has accuracy requirements for the ODR of the sensor, the coprocessor 15 starts the ODR adjustment scheme. To ensure that the application can obtain sensor data with the target ODR and implement the corresponding functions. When some applications have no requirements for the ODR of the sensor, the coprocessor 15 can turn off the ODR adjustment scheme, and there is no need to supplement the sensor data or delete the number of frames, thereby ensuring the accuracy of the sensor data.

It should be understood that in some embodiments, some or all of the aforementioned steps 401 to 407 may also be executed by the application processor 14 or a micro controller unit (MCU) provided outside the processor 110. This is not limited.

Figure 5 shows an implementation flow chart of another sensor data processing method according to some embodiments of the present application.

It can be understood that the execution subject of each step of the process shown in Figure 5 can be the co-processor 15 in the electronic device that processes sensor data, and there is no limitation here. In order to simplify the description, when introducing each step of the process shown in Figure 5 below, the execution subject of each step will not be repeatedly introduced.

As shown in Figure 5, the method includes the following processes:

501, determine whether the target ODR reaches the sensor's limit ODR.

For example, when the application processor 14 runs an application program and needs to obtain sensor data, it will issue the target ODR of the application program to the coprocessor 15, and the coprocessor 15 will then issue the target ODR to the sensor, and the sensor will issue the target ODR according to the target ODR. Transfer the collected data. The sensor itself has extreme ODR data. When the sensor transmits data under extreme ODR, there will be a large error in the data transmission speed, and the data transmitted by the sensor needs to be processed. Therefore, the coprocessor 15 needs to determine whether the target ODR reaches the limit ODR.

If the judgment result is yes, for example, the target ODR exceeds the limit ODR, the sensor will transmit data with the limit ODR and there will be a large error. Then perform step 503 to determine that the actual ODR of the sensor is less than the target ODR, resulting in data loss. Or perform step 506 to determine that the actual ODR of the sensor is greater than the target ODR, causing data overflow.

If the judgment result is no, for example, the target ODR is less than the limit ODR and the error of the sensor when transmitting data is within the allowable range, then step 502 is executed to determine whether the application has turned on high-precision subscription.

502, determine whether the application enables high-precision subscription.

For example, in some embodiments, the application has accuracy requirements for the ODR of the sensor. Therefore, when the application processor 14 runs this type of application program to obtain sensor data, it needs to ensure the accuracy of the data transmission speed. For example, a whitelist can be stored in the electronic device, so that the coprocessor 15 can determine whether the application program enables high-precision subscription based on the whitelist. For example, when an application obtains sensor data, the coprocessor 15 can determine whether to adjust the data when reporting the data to the application processor 14 by determining whether the corresponding application is in the whitelist.

If the judgment result is yes, for example, the application is in the whitelist and has requirements for the ODR accuracy of the sensor. Then perform step 503 to determine that the actual ODR of the sensor is less than the target ODR, resulting in data loss. Or perform step 506 to determine that the actual ODR of the sensor is greater than the target ODR, causing data overflow.

If the judgment result is negative, for example, the application is not in the whitelist, there are no special requirements for the ODR accuracy of the sensor, and the error of the sensor when transmitting data is within the allowable range, then step 507 is executed to report the data.

It can be understood that in another embodiment, the judgment step of 501 may be reversed from the step of 502. That is, the coprocessor 15 first determines whether the application program has enabled high-precision subscription, and then determines whether the target ODR of the application program reaches the limit ODR of the sensor. The order in which the process steps are described in this application does not place any restrictions on the specific implementation order of the process.

503, it is determined that the actual ODR of the sensor is less than the target ODR, resulting in data loss.

For example, the sensor caches the collected data into an internal memory. When the data in the memory reaches a preset value, the sensor triggers an interrupt and reports the cached data to the coprocessor 15 . Each time the sensor triggers an interrupt, the timestamp of the interrupt is recorded. The coprocessor 15 can obtain the cache time of each time the sensor caches preset data based on the sensor interrupt timestamp. For example, the timestamp of the current interrupt triggered by the sensor is subtracted from the timestamp of the last triggered interrupt, which is the actual cache time of the currently reported data, that is, DT. If the cache time is greater than the target cache time of the target ODR, it can be determined that the actual ODR of the sensor is less than the target ODR. Therefore, the amount of data reported by the sensor within a certain period of time cannot meet the requirements, that is, part of the data is missing. When the coprocessor 15 reports the sensor data to the application processor 14, it will cause the functions implemented by the application program to be accurate enough.

504. Obtain the complementary frame position from the data reported by the sensor and calculate the slope.

For example, the coprocessor 15 can generate the target frame number according to the target ODR and the actual cache time DT when supplementing the frame, and can supplement the data reported by the sensor to the target frame number when supplementing the frame. For example, the determination of the position of the complementary frame may refer to step 406 in the embodiment of FIG. 4 . When performing frame filling, the coprocessor 15 can obtain the slope of the sensor data at the position of the frame filling, and generate frame number data that needs to be supplemented based on the slope. For example, the sensor data of two adjacent frames at the complementary frame position are averaged as the sensor data at the complementary frame position.

505. Complement the lost data.

For example, after the coprocessor 15 obtains the frame-filling position and the frame-filling data, the frame-filling can be performed on the data reported by the sensor to ensure that the data transmission speed reported to the application processor 14 meets the target ODR.

506. It is determined that the actual ODR of the sensor is greater than the target ODR, causing data overflow.

For example, if the actual cache time of the data reported by the sensor is less than the cache time of the target ODR, it can be determined that the actual ODR of the sensor is greater than the target ODR. In this way, within a certain period of time, the data reported by the sensor will exceed the data reported when the sensor is the target ODR. When the coprocessor 15 reports the sensor data to the application processor 14, the function of the application program will also be inaccurate.

507, delete the overflow data.

For example, when the actual ODR of the sensor is greater than the target ODR, the time for each interrupt triggered by the sensor will be shortened. Therefore, the coprocessor 15 needs to delete some data from the data reported by the sensor to ensure that the number of frames reported to the application processor 14 is consistent with the target number of frames reported. For the method of deleting the number of frames, refer to step 405 in the embodiment of FIG. 4 .

508, report data.

For example, after obtaining the data reported by the sensor, the coprocessor 15 adjusts the sensor data based on the ODR adjustment plan. Then, the coprocessor 15 reports the adjusted sensor data to the application processor 14 . The application processor 14 runs an application program to implement the functions of the application program. It can be understood that if the sensor data does not need to be adjusted, the coprocessor 15 can directly report the acquired sensor data to the application processor 14 .

It can be understood that through the embodiments of the present application, the coprocessor 15 can dynamically enable the ODR adjustment scheme so that the speed of reporting data meets the needs of the application program.

Further, FIG. 6 shows an interactive flow chart of a sensor data processing process according to an embodiment of the present application.

For example, the flow chart shown in FIG. 6 shows the flow charts of three applications for obtaining sensor data respectively. For example, application 611a is an application that needs to transmit data under high ODR. Application 611b is an application with high accuracy requirements for ODR. Application program 611c is a standard application program, allowing certain errors in ODR transmission.

The interacting subjects in the sensor data processing process may be, for example, the application processor 14 and the sensor hub 620 . Sensor hub 620 may be provided in coprocessor 15 .

The application processor 14 is used to run an application program 611 and a sensor HAL 612 in a hardware abstraction layer (HAL). The hardware abstraction layer encapsulates the hardware driver and provides a unified universal interface for hardware capabilities to the upper layer.

The sensor hub 620 may be provided in the coprocessor 15 for running the sensor driver 621, other algorithms 622, and the step counting algorithm 623. The sensor driver 621 is used to transmit sensor data and implement the sensor data processing method in any of the above embodiments. Other algorithms 622 are used to process sensor data in other ways. The pedometer algorithm 623 is used to generate the data required by the pedometer based on the sensor data.

Specifically, as shown in Figure 5, the interaction process of application 611a includes the following steps:

S611, the application 611a activates the sensor HAL 512.

For example, when the application program 611a obtains the data of the corresponding sensor, it needs to activate the HAL 612 of the corresponding sensor in the HAL layer of the operating system of the electronic device 100 .

S612, the application program 611a sends the target ODR to the sensor HAL 612.

For example, when the application program 611a obtains sensor data, it will issue the target ODR to the sensor HAL 612. The sensor driver 612 is caused to transmit the sensor data at the target ODR.

S613, the sensor HAL 612 determines that the target ODR is equal to the limit ODR.

For example, the sensor output data error is high under extreme ODR. Therefore, the data transmitted by the sensor driver 621 needs to be processed through the sensor data processing method in the embodiment of FIG. 4 . When the sensor HAL 612 determines that the target ODR is equal to the limit ODR, the sensor driver 621 starts the ODR adjustment scheme.

It can be understood that the target ODR does not necessarily need to be strictly greater than the limit ODR or equal to the limit ODR before starting the ODR adjustment plan. In other embodiments, the ODR adjustment scheme may also be enabled if the target ODR is close to the limit ODR of the sensor. For example, when the target ODR reaches 80% of the limit ODR, the ODR adjustment plan needs to be enabled.

S614, the sensor driver 621 returns sensor data to the sensor HAL 612.

For example, the sensor driver 621 transmits the processed sensor data to the application program 611a through the sensor HAL 612. The processing of the sensor data may be, for example: when the sensor driver 621 detects that the ODR of the reported data is less than the target ODR, frame-filling is performed on the reported data to ensure that the data transmission rate of the reported sensor data is equal to the target ODR. When the sensor driver 621 detects that the actual ODR when the sensor reports data is greater than the target ODR, the data reported by the sensor is deleted. It is ensured that the data transmission rate of sensor data reported by the sensor driver 621 to the application program 611a is equal to the target ODR, thereby ensuring the accuracy of the speed at which the application program 611a obtains sensor data.

It should be understood that the process of adding frames and deleting the number of frames can refer to steps 405 and 406 in the embodiment of FIG. 4 .

S615, the application 611a turns off the sensor HAL 612.

For example, there may be multiple applications 611a that require high ODR to transmit data. When each application 611a finishes acquiring sensor data, it will continue to determine whether the target ODR of the next application 611a reaches the limit ODR. After determining When the target ODR of an application 611a is less than the limit ODR, the ODR adjustment scheme can be turned off so that the sensor driver 612 outputs raw sensor data.

Continuing to refer to Figure 6, the interaction process of the application 611b includes the following steps:

S621, the application program 611b activates the sensor HAL 612.

For example, when the application program 611b obtains the data of the corresponding sensor, it needs to activate the HAL 612 of the corresponding sensor in the HAL layer of the operating system of the electronic device 100 .

S622, the application 611b sends the target ODR to the sensor HAL 612.

For example, when acquiring sensor data, the application program 611b will send the target ODR to the sensor HAL 612. The sensor driver 612 is caused to transmit the sensor data at the target ODR.

S623, the sensor HAL 612 adds a high-precision subscription count to the sensor driver 621.

For example, when the application program 611b has requirements for the accuracy of the ODR, the sensor HAL 612 will perform high-precision subscription counting to the sensor driver 621. The high-precision subscription count is used to record the number of applications 611b, that is, the number of applications 611 that have high-precision requirements for ODR.

It should be understood that applications that perform high-precision subscriptions have higher accuracy requirements for sensor ODR. When the sensor reports data to the application, it needs to enable the ODR adjustment scheme to ensure the accuracy of the sensor ODR.

It can be understood that, for example, there may be multiple applications 611b with high ODR accuracy requirements. Each time an application 611b with high ODR accuracy requirements performs a high-precision subscription, the sensor HAL 612 will increase the count of high-precision subscriptions.

When the sensor driver 621 has a high-precision subscription, it means that the current application 611b has requirements for the ODR accuracy of the sensor. Therefore, it is necessary to start the ODR adjustment plan and process the data transmitted by the sensor driver 621 through the data processing method in the embodiment of Figure 4. for processing.

S624, the sensor driver 621 returns sensor data to the sensor HAL 612.

For example, the sensor driver 621 transmits the sensor data processed by the ODR adjustment scheme to the application program 611b through the sensor HAL 612.

For example, the processing of sensor data can be: when the sensor driver 621 detects that the actual ODR of the reported data is less than the target ODR when the sensor interrupt is triggered, the sensor driver 621 performs supplementary frames on the reported sensor data to ensure that the data transmission rate of the reported sensor data is equal to the target. ODR. When the sensor driver 621 detects that the ODR when the sensor interrupt is triggered is greater than the target ODR, it deletes the data reported by the sensor to ensure that the data transmission rate of the sensor data reported by the sensor driver 621 is equal to the target ODR. It should be understood that the process of adding frames and deleting the number of frames can refer to steps 405 and 406 in the embodiment of FIG. 4 .

S625, the application 611b turns off the sensor HAL 612.

For example, every time the application 611b ends acquiring sensor data, the count of the high-precision subscription is reduced. When the count of the high-precision subscription is reduced to 0, it means that no application 611b needs high ODR precision output data, and the sensor driver 621 can turn off the ODR adjustment scheme and report raw sensor data.

In other embodiments, the sensor hub 620 also includes a step counting algorithm 623. The step counting algorithm 623 requires the sensor driver 621 to output data with high-precision ODR. When the sensor driver 621 turns on the ODR adjustment scheme, the pedometer algorithm 623 sends a resampling request to the sensor driver 621, and then the sensor driver 621 returns the adjusted sensor data to the pedometer algorithm 623 to meet the calculation requirements of the pedometer algorithm 623.

Continuing to refer to Figure 6, the interaction process of application 611c includes the following steps:

S631, the application 611c activates the sensor HAL 612.

For example, when the application program 611c obtains the data of the corresponding sensor, it needs to activate the HAL 612 of the corresponding sensor in the HAL layer of the operating system of the electronic device 100 .

S632, the application 611c sends the target ODR to the sensor HAL 612.

For example, when acquiring sensor data, the application program 611c will send the target ODR to the sensor HAL 612. The sensor driver 612 is caused to transmit the sensor data at the target ODR.

S633, the sensor HAL 612 sets the sensor driver 621 to transmit data with the target ODR.

It can be understood that the standard application 611c may be an application 611c that has no accuracy requirements for sensor ODR and has a low target ODR. When the target ODR is low, the sensor ODR error is low, and within the allowable range of the application 611c, the sensor driver 621 does not need to turn on the ODR adjustment scheme to ensure the accuracy of the sensor data. At this time, the ODR adjustment scheme is turned off.

S634, the sensor driver 621 returns sensor data to the sensor HAL 612.

For example, when the sensor driver 621 determines that the ODR adjustment scheme does not need to be enabled, the original sensor data can be directly transmitted to the application program 611c through the sensor HAL 612.

It can be understood that when the ODR adjustment scheme is turned off, other algorithms 622 in the sensor hub 620 may issue a resampling request to the sensor driver 621. At this time, the sensor driver 621 can transmit the sensor data to other algorithms 622 and process the sensor data based on the other algorithms 622 .

S635, the application 611c turns off the sensor HAL 612.

For example, there may be multiple standard applications 611c. When each application 611c ends acquiring sensor data, it will continue to determine whether the target ODR of the next application 611c reaches the limit ODR. After determining the target ODR of the next application 611c, When the target ODR is less than the limit ODR, the ODR adjustment scheme can be kept in a closed state so that the sensor driver 612 outputs original sensor data.

Through this embodiment, the sensor driver 621 can dynamically start the ODR adjustment scheme. For example, if the application 611a transmits data under high ODR, a large error will occur in the ODR, and the sensor driver 621 will initiate an ODR adjustment plan. Or when the application 611b has high accuracy requirements for ODR, the sensor driver 621 will also start the ODR adjustment plan. In this way, various applications 611 meet the sensor ODR requirements. When the application program 611 has no requirements for the sensor ODR, for example, the application program 611c allows the sensor ODR to have a certain error stored, then the sensor driver 621 turns off the ODR adjustment scheme. In this way, the sensor driver 621 can avoid adding frames or deleting the number of frames to the sensor data, thereby ensuring the accuracy of the sensor data transmitted by the sensor driver 621 .

Taking a mobile phone as an example, the electronic devices involved in some embodiments of the present invention are introduced in detail below.

Figure 7 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), an image signal processor ( image signal processor (ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or Universal serial bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can respectively couple the touch sensor 180K, the acceleration sensor 180E, etc. through different I2C bus interfaces to obtain corresponding sensor data and adjust the ODR of the sensor.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as display screens and cameras. MIPI interfaces include camera serial interface (CSI), display serial interface (display serial interface, DSI), etc.

The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with a camera, a display screen, a wireless communication module 160, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that complies with USB standard specifications, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other electronic devices, such as AR devices, etc.

It can be understood that the interface connection relationships between the modules illustrated in the embodiment of the present invention are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the electronic device 100 . While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140 to provide power to the processor 110, internal memory 121, display screen, camera, wireless communication module 160, etc. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellite system. (global navigation satellite system, GNSS), frequency modulation (FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor may include at least two parallel plates of conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is performed on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position based on the detection signal of the pressure sensor 180A.

The gyro sensor 180B may be used to determine the motion posture of the electronic device 100 .

Air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

The magnetic sensor 180D may include a Hall sensor, for example.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices and be used in horizontal and vertical screen switching, pedometer and other applications.

Distance sensor 180F for measuring distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may utilize the distance sensor 180F to measure distance to achieve fast focusing.

Proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outwardly through the light emitting diode. Electronic device 100 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100 . When insufficient reflected light is detected, the electronic device 100 may determine that there is no object near the electronic device 100 . The electronic device 100 can use the proximity light sensor 180G to detect when the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to save power.

The ambient light sensor 180L is used to sense ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket to prevent accidental touching.

Fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access to application locks, fingerprint photography, fingerprint answering of incoming calls, etc.

Temperature sensor 180J is used to detect temperature.

Touch sensor 180K, also known as "touch device". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a location different from that of the display screen 194 .

Bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human body's vocal part. The bone conduction sensor 180M can also contact the human body's pulse and receive blood pressure beating signals.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .

FIG. 8 shows a schematic block diagram of the system software architecture of a mobile phone 100 according to an embodiment of the present application.

The software system of mobile phone 100 can adopt layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. The embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the mobile phone 100 .

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime (android runtime) and system libraries, and kernel layer.

As shown in Figure 8, the application layer can include a series of application packages.

Application packages can include camera, gallery, calendar, calling, map, navigation, WLAN, Bluetooth, music, video, SMS and other applications.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

The application framework layer can include window management service (WMS), view system (view system), graphics system (graphics system), display synthesis (surface flinger), display engine service (display engine service), resource manager , notification manager, etc.

WMS, used to manage window programs. WMS can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can consist of one or more views.

The graphics system is a general programming software package in the system. It is composed of graphics I/O devices. Its basic functions are primitive generation, attribute setting, etc.

Surface Flinger can also be called interface synthesis. The function of Surface Flinger is to accept the graphic display data provided by WMS, synthesize them, and input them to the display device for display. Surface Flinger can use the open graphics library (OpenGL) hardware composer (HWC) to synthesize the interface (surface).

The display engine service can call the hardware capabilities provided by the ambient light sensor 180L in the hardware abstraction layer to obtain the illumination intensity of the ambient light.

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the electronic device vibrates, the indicator light flashes, etc.

Android Runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system. The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media library (media libraries), 3D graphics processing library (such as: Open Graphics Library (OpenGL), or open graphics library for embedded systems (open graphics library for embedded systems, OpenGL ES) )), 2D graphics engine (for example: Skia graphics library (SGL)), etc. It is understandable that Android applications can call the SGL or OpenGL ES interface to draw and render the UI interface.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

It is understandable that graphics drawing in Android applications is divided into two types: 2D and 3D. 2D can be implemented by Skia, and Skia can also call some OpenGL ES content to achieve simple 3D effects.

The hardware abstraction layer, or HAL layer, encapsulates the hardware driver and provides a unified universal interface for hardware capabilities for the upper layer. As shown in Figure 8, the hardware abstraction layer includes CPU HAL, GPU HAL, sensor HAL, display HAL, camera HAL, etc.

The kernel layer is the layer between hardware and software. The kernel layer includes at least CPU driver, GPU driver, display driver, sensor driver, camera driver, etc.

The kernel layer may also include an ODR correction module, for example. The ODR correction module can execute any sensor data processing method proposed in the embodiments of this application to obtain a set of sensor data, and then provide the sensor data to the application in the application layer. For example, the ODR correction module can obtain a set of acceleration data by executing any of the sensor data processing methods proposed in the embodiments of this application, and provide the acceleration data to the pedometer application.

For details, reference may be made to the relevant content of the sensor data processing method shown in FIG. 4 , which will not be described again here. It should be noted that the ODR correction module can also be at the application framework layer or system library. The embodiment of the present application does not limit the location of the ODR correction module in the software framework.

In the drawings, some structural or methodological features may be shown in specific arrangements and/or orders. However, it should be understood that such specific arrangement and/or ordering may not be required. Rather, in some embodiments, the features may be arranged in a different manner and/or order than shown in the illustrative figures. Additionally, the inclusion of structural or methodological features in a particular figure is not meant to imply that such features are required in all embodiments, and in some embodiments these features may not be included or may be combined with other features.

It should be noted that each unit/module mentioned in each device embodiment of this application is a logical unit/module. Physically, a logical unit/module can be a physical unit/module, or it can be a physical unit/module. Part of the module can also be implemented as a combination of multiple physical units/modules. The physical implementation of these logical units/modules is not the most important. The combination of functions implemented by these logical units/modules is what solves the problem of this application. Key technical issues raised. In addition, in order to highlight the innovative part of this application, the above-mentioned equipment embodiments of this application do not introduce units/modules that are not closely related to solving the technical problems raised by this application. This does not mean that the above-mentioned equipment embodiments do not exist. Other units/modules.

It should be noted that in the examples and descriptions of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply There is no such actual relationship or sequence between these entities or operations. Furthermore, the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a" does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

Although the present application has been illustrated and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes may be made in form and detail without departing from the present invention. The spirit and scope of the application.

Claims (11)

1. A data processing method, characterized in that it is applied to at least one processor in an electronic device, and the electronic device includes a sensor; The methods include: Obtain the first data reported by the sensor, where the first data has a first frame number; Determine that the first frame number satisfies a first condition, wherein the first condition includes that the first frame number is different from the target reported frame number; Process the first data into second data, wherein the second frame number of the second data is the same as the target reporting frame number; Performing a function related to the first data based on the second data. 2. The method of claim 1, wherein the first condition further includes at least one of the following: The speed at which the sensor reports the first data reaches the first speed; The speed accuracy requirement of the first data reported by the sensor is the first accuracy. 3. The method according to claim 1, characterized in that processing the first data into second data includes: Corresponding to the first frame number being less than the target reporting frame number, supplementing the first data with third data to generate the second data; Corresponding to the fact that the first frame number is greater than the target reporting frame number, fourth data is deleted from the first data to generate the second data. 4. The method according to claim 3, wherein the first data includes a plurality of sensor data obtained by the sensor and a timestamp corresponding to each sensor data. 5. The method according to claim 4, characterized in that when the number of frames corresponding to the first frame is less than the number of target reporting frames, third data is supplemented to the first data to generate the second data. ,include: Sorting the plurality of sensor data according to the order of the timestamps of each sensor data in the first data; Divide the sorted plurality of sensor data into multiple sensor data subsets, wherein the number of the sensor data subsets is the same as the number of frames of the third data, and each of the sensor data subsets The number of sensor data is the same; Data interpolation is inserted at the same location in different sensor data subsets to generate the second data. 6. The method according to claim 5, characterized in that the data difference is generated in any one of the following ways: Calculate the average of the two sensor data at both ends of the sensor data subset as a data interpolation between the sensor data subset and an adjacent sensor data subset; Perform data fitting on at least two sensor data at both ends of the sensor data subset to obtain data interpolation between the sensor data subset and adjacent sensor data subsets. 7. The method according to claim 4, characterized in that, corresponding to the first frame number being greater than the target reporting frame number, fourth data is deleted from the first data to generate the third 2. Data, including: Sorting the plurality of sensor data according to the order of the timestamps of each sensor data in the first data; From the sorted plurality of sensor data, acquire the sensor data at intervals of a first number, wherein the number of acquired sensor data is the same as the number of frames of the fourth data; The acquired sensor data is deleted and the second data is generated. 8. The method according to any one of claims 1 to 7, further comprising: The target reporting frame number is determined based on the first time it takes for the sensor to report the first data and the target reporting speed of the processor. 9. An electronic device, characterized by including at least one processor and a sensor; The at least one processor is used for: Obtain the first data reported by the sensor, where the first data has a first frame number; Determine whether the first frame number satisfies a first condition, wherein the first condition includes that the first frame number is different from the target reported frame number; Corresponding to the first frame number satisfying the first condition, the first data is processed into second data, wherein the second frame number of the second data is the same as the target reporting frame number; Performing a function related to the first data based on the second data. 10. The electronic device of claim 9, wherein the at least one processor includes a first processor and a second processor, wherein, The first processor is configured to obtain the first data reported by the sensor and determine whether the first number of frames meets a first condition, and, When the first frame number meets the first condition, process the first data into second data; The second processor is configured to obtain the second data from the first processor and perform functions related to the first data. 11. A computer-readable storage medium, characterized in that instructions are stored on the readable storage medium, and when the instructions are executed on a computer, they cause the computer to execute any one of claims 1 to 8. data processing methods.