VEHICLE SENSOR DATA PROCESSING METHOD AND SYSTEM

Abstract

A vehicle sensor data processing method and system are provided. The method includes: a vehicle sensor data processing system processes and fuses, by using a plurality of levels of control units, a signal sensed by a sensor, and a higher-level control unit makes a control decision based on received data of a plurality of types or a plurality of processing levels. In addition, a priority of a sensor may be further configured based on a vehicle function that needs to be implemented by the system, thereby implementing more stable and reliable vehicle control and ensuring safe driving while satisfying a delay requirement.

Claims

1. A vehicle sensor data processing system, wherein the system comprises a plurality of levels of control units, the plurality of levels of control units comprise one first control unit and at least one second control unit, and the first control unit is an upper-level control unit of the at least one second control unit; the at least one second control unit is configured to receive first data, and output second data to the first control unit, the first data is from a sensor connected to the at least one second control unit or is from a third control unit, and the third control unit is a lower-level control unit of the at least one second control unit; and the first control unit is configured to output first control information to a device based on the second data output from one or more second control units, and the first control information is used to control the device.

2. The system according to claim 1, wherein the at least one second control unit is further configured to process the first data based on a data processing mode being set to a multi-level processing mode, wherein the second data is data obtained by processing the first data.

3. The system according to claim 1, wherein the at least one second control unit is configured to output the second data based on the sensor that sends the first data being a sensor with a first priority.

4. The system according to claim 3, wherein the at least one second control unit is configured to determine a priority of the sensor based on configuration information of the sensor, wherein the configuration information of the sensor indicates the priority of the sensor.

5. The system according to claim 1, wherein the first control unit is configured to output the first control information to the device based on the second data from the one or more second control units and data from one or more first sensors, and a first sensor is a sensor connected to the first control unit.

6. The system according to claim 1, wherein the third control unit is configured to receive data from a fourth control unit or data from a second sensor, the second sensor is connected to the third control unit, and the fourth control unit is a lower-level control unit of the third control unit.

7. A vehicle sensor data processing method comprising: receiving, by a second control unit of a vehicle sensor data processing system, one or more pieces of first data, wherein the one or more pieces of first data are from one or more sensors connected to the second control unit, or the one or more pieces of first data are from a third control unit of the vehicle sensor data processing system, and the third control unit is a lower-level control unit of the second control unit; outputting, by the second control unit, second data to a first control unit of the vehicle sensor data processing system, wherein the first control unit is an upper-level control unit of the second control unit; determining, by the first control unit, first control information based on the second data; and outputting, by the first control unit, the first control information to a device.

8. The method according to claim 7, wherein the determining, by the first control unit, the first control information based on the second data comprises: determining, by the first control unit, the first control information based on the second data and data from one or more first sensors, wherein a first sensor is a sensor connected to the first control unit.

9. The method according to claim 7, further comprising: processing, by the second control unit, the first data based on a data processing mode being set to a multi-level processing mode, wherein the second data is data obtained by processing the first data.

10. A vehicle comprising a vehicle sensor data processing system, wherein the system comprises a plurality of levels of control units, the plurality of levels of control units comprise one first control unit and at least one second control unit, and the first control unit is an upper-level control unit of the at least one second control unit; the at least one second control unit is configured to receive first data, and output second data to the first control unit, the first data is from a sensor connected to the at least one second control unit or is from a third control unit, and the third control unit is a lower-level control unit of the at least one second control unit; and the first control unit is configured to output first control information to a device based on the second data output from one or more second control units, and the first control information is used to control the device.

11. The vehicle according to claim 10, wherein the at least one second control unit is configured to process the first data based on a data processing mode being set to a multi-level processing mode, wherein the second data is data obtained by processing the first data.

12. The vehicle according to claim 10, wherein the at least one second control unit is configured to output the second data based on the sensor that sends the first data being a sensor with a first priority; or the at least one second control unit is configured to output second control information to the device based on the sensor that sends the first data being a sensor with a second priority, wherein the second control information is used to control the device.

13. The vehicle according to claim 12, wherein the at least one second control unit is configured to determine a priority of the sensor based on configuration information of the sensor, wherein the configuration information of the sensor indicates the priority of the sensor; or the at least one second control unit is configured to determine a priority of the sensor based on a delay requirement of the sensor and a first threshold, wherein the sensor is with the first priority based on the delay requirement of the sensor being greater than or equal to the first threshold, or the sensor is with the second priority based on the delay requirement of the sensor being less than or equal to the first threshold.

14. The vehicle according to claim 10, wherein the first control unit is configured to output the first control information to the device based on the second data from the one or more second control units and data from one or more first sensors, and a first sensor is a sensor connected to the first control unit.

15. The vehicle according to claim 10, wherein the third control unit is configured to receive data from a fourth control unit or data from a second sensor, the second sensor is connected to the third control unit, and the fourth control unit is a lower-level control unit of the third control unit.

16. The system according to claim 1, wherein the at least one second control unit is configured to forward the first data based on a data processing mode being set to a non-multi-level processing mode, wherein the second data is the first data.

17. The system according to claim 1, wherein the at least one second control unit is configured to output second control information to the device based on the sensor that sends the first data being a sensor with a second priority, wherein the second control information is used to control the device.

18. The system according to claim 3, wherein the at least one second control unit is configured to determine a priority of the sensor based on a delay requirement of the sensor and a first threshold, wherein the sensor is with the first priority based on the delay requirement of the sensor being greater than or equal to the first threshold, or the sensor is with the second priority based on the delay requirement of the sensor being less than or equal to the first threshold.

19. The method according to claim 7, further comprising: forwarding, by the second control unit, the first data based on a data processing mode being set to a non-multi-level processing mode, wherein the second data is the first data.

20. The vehicle according to claim 10, wherein the at least one second control unit is configured to forward the first data based on a data processing mode being set to a non-multi-level processing mode, wherein the second data is the first data.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0039] FIG. 1 is a schematic diagram of a vehicle sensor data processing system applicable to an embodiment of this application;

[0040] FIG. 2 is a schematic flowchart of an example of a vehicle sensor data processing method according to an embodiment of this application; and

[0041] FIG. 3A and FIG. 3B are a schematic flowchart of an example of a vehicle sensor data processing method according to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

[0042] The following describes the technical solutions of this application with reference to the accompanying drawings.

[0043] The technical solutions in embodiments of this application may be applied to an autonomous driving scenario, for example, may be applied to various vehicles. With continuous development of autonomous driving technologies, cruise control, light control, airbag control, and the like all require a sensor to sense a change of an environment in which a vehicle is located, to provide data used for control decision-making to a control unit. As a quantity of sensors increases for implementation of various functions, how to process sensed data from a large quantity of sensors to make a timely and accurate control decision is a hot issue of ensuring safe driving. This application provides a method of fusing data from a plurality of sensors by using an architecture with a plurality of levels of control units to make a control decision. On the basis of guaranteeing a sensor data processing delay, this method can fuse data sensed by a plurality of sensors, to improve vehicle control reliability, and further improve vehicle driving safety.

[0044] A vehicle sensor data processing system according to this application includes a plurality of levels of control units and at least two sensors. The plurality of levels of control units include at least two levels of control units, for example, may include two levels of control units, or may include three levels of control units, four levels of control units, or five levels of control units. A specific quantity of levels of control units is not limited in this application. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application.

[0045] FIG. 1 is a schematic diagram of a vehicle sensor data processing system applicable to an embodiment of this application.

[0046] It should be noted that, to clearly describe the solutions of this application, an example in which three levels of control units are included in FIG. 1 is used for description. FIG. 1 is merely a schematic diagram of a structure of a system in this application, but this is not limited in this application. As shown in FIG. 1, the vehicle sensor data processing system 100 may include at least one multi-domain controller (multiple domain controller, MDC) and at least one electronic control unit (ECU), for example, an ECU 1 to an ECU 4 in FIG. 1, where each ECU is connected to at least one sensor. The vehicle sensor data processing system 100 may further include at least one domain control unit (DCU). The DCU may be an upper-level control unit of the ECU and a lower-level control unit of the MDC, and may fuse data from the lower-level ECU, and output control information, or transmit processed data to the MDC. The multi-domain controller may be a first control unit, and is directly connected to at least one second control unit (for example, an ECU or a DCU) and/or a sensor. In an implementation, if the vehicle sensor data processing system 100 includes two levels of control units, the second control unit is an ECU. In another implementation, if the vehicle sensor data processing system 100 includes three levels of control units, the second control unit may be a DCU or an ECU. The ECU connected to the DCU may be a third control unit, and the MDC may further be connected to at least one third control unit. The MDC may fuse data from the connected second control unit and/or sensor, and output control information to control an external device.

[0047] The following describes in detail embodiments provided in this application with reference to the accompanying drawings.

[0048] FIG. 2 is a schematic flowchart of an example of a vehicle sensor data processing method according to an embodiment of this application.

[0049] Each control unit included in FIG. 2 corresponds to each control unit in the vehicle sensor data processing system 100 in FIG. 1. For a connection manner thereof, refer to FIG. 1. FIG. 2 may be a schematic flowchart of a vehicle sensor processing method for controlling a first vehicle function of a vehicle. For example, the first vehicle function may be cruising, route planning, or braking.

[0050] S201: Configure intelligent driving information.

[0051] The intelligent driving configuration information may be configured by a driver or another associated function. For example, the driver configures the intelligent driving information when enabling an autonomous driving function. For another example, autonomous driving information is configured due to a change of an engine control function. However, this is not limited in this application.

[0052] Optionally, the intelligent driving information may include data processing mode setting information.

[0053] For example, the data processing mode configuration information may set a data processing mode to a multi-level processing mode or a non-multi-level processing mode. The multi-level processing mode may be a data processing mode in which data from a plurality of sensors is processed and fused by a plurality of levels of control units and then a control decision is output according to this application.

[0054] Optionally, the intelligent driving information may be used to configure the first vehicle function. The system may predefine that the first vehicle function corresponds to one data processing mode. For example, if the first vehicle function corresponds to the multi-level processing mode, the control unit may determine, based on the first vehicle function, that the processing mode is the multi-level processing mode.

[0055] S202: An ECU receives data A (that is, an example of first data) from a connected sensor.

[0056] An ECU 1, an ECU 2, and an ECU 3 separately receive data sensed by sensors connected to the ECU 1, the ECU 2, and the ECU 3. For example, the ECU 1 receives data A1 sensed by a sensor 1, the ECU 2 receives data A2 sensed by a sensor 2, and the ECU 3 receives data A3 sensed by a sensor 3.

[0057] S202: The ECU determines data B based on the data from the sensor and the data processing mode setting information.

[0058] In an implementation, the ECU determines, based on the intelligent driving information, that the data processing mode is set to the multi-level processing mode. The multi-level processing mode is applicable to each ECU related to the first vehicle function. In this case, each ECU processes data received from a sensor, to obtain data B.

[0059] For example, the ECU 1, the ECU 2, and the ECU 3 determine, based on the intelligent driving information, that the data processing mode is the multi-level processing mode. In this case, the ECU 1 processes the data A1 from the sensor 1 to obtain data B1, the ECU 2 processes the data A2 from the sensor 2 to obtain data B2, and the ECU 3 processes the data A3 from the sensor 3 to obtain data B3.

[0060] In another implementation, the ECU determines, based on the intelligent driving information, that the data processing mode is set to the non-multi-level processing mode, and the ECU does not process the data A received from the sensor, but forwards the data A from the sensor to an upper-level control unit. That is, the data B is the data A. In other words, the ECU does not process the data A from the sensor and forwards the data A to the upper-level control unit for processing by the upper-level control unit.

[0061] For example, if the first vehicle function is a function requiring fusion of high-precision data from a plurality of sensors to make a control decision, the ECU transmits raw data from the sensors to the upper-level control unit, and the upper-level control unit makes a control decision after fusing the data from the plurality of sensors. However, this is not limited in this application.

[0062] In another implementation, the ECU determines, based on the intelligent driving information, that the data processing mode is set to the non-multi-level processing mode. The ECU processes the data A from the sensor, and determines control information B (that is, an example of second control information), where the control information B is used to control an external device.

[0063] For example, the first vehicle function is a function with a high emergency degree, for example, an anti-collision function. After receiving data from a sensor, the ECU processes the data from the sensor, and makes a control decision. However, this is not limited in this application.

[0064] In another implementation, each sensor may correspond to one data processing mode. In other words, the intelligent driving information may include information for separately configuring a data processing mode for a plurality of sensors, and the ECU determines, based on a data processing mode of a corresponding sensor, whether to process data from the sensor.

[0065] For example, when the vehicle performs the first vehicle function, the control decision has different precision requirements on the sensor data. Therefore, corresponding data processing modes are configured for different sensors. The ECU determines, based on the data processing mode of the corresponding sensor, whether to process the data from the sensor. However, this is not limited in this application.

[0066] S203: The ECU 1 and the ECU 2 separately output the data B1 and the data B2 to a DCU.

[0067] It should be noted that S203 is an optional step. When the system includes more than three levels of control units, S203 may be performed. During specific implementation, the structure may be two levels of control units, and the two levels of control units do not include a DCU. Therefore, S203 is not performed.

[0068] S204: The DCU fuses the data B1 and the data B2 to obtain data C (that is, an example of second data).

[0069] The DCU fuses the data B1 and the data B2 to obtain the data C, where the data C includes data obtained after the DCU fuses the data B1 and the data B2. The data C may further include decision information determined by the DCU based on the data B1 and the data B2, and the decision information may be used as a decision reference by an upper-level control unit.

[0070] For example, after data from two sensors with similar sensing tasks is processed by the ECU, the DCU may perform data fusion to obtain fused data or preliminary decision information for the sensing task. For example, the sensing task may be obstacle sensing, and the sensor 1 and the sensor 2 are configured to sense an obstacle. After data from the two sensors is separately processed by the ECU 1 and the ECU 2, the DCU fuses the data to obtain the data C, and the data C includes obstacle-related fusion information and a preliminary decision made by the DCU. Then the data C is transmitted to an MDC in S205 for reference by the MDC during decision-making.

[0071] S205: The DCU outputs the data C to the MDC.

[0072] S206: A sensor 4 outputs data A4 to the MDC.

[0073] The sensor can be directly connected to the MDC to provide accurate sensing data for the MDC.

[0074] S207: The ECU 3 outputs the data B3 to the MDC.

[0075] The MDC may further be connected to a control unit (for example, the ECU 3) that is connected to a sensor, and the ECU 3 may output the data B2 to the MDC.

[0076] S208: The MDC fuses received data to determine first control information.

[0077] The MDC receives data obtained after data from the plurality of sensors undergoes processing of different levels, fuses the received data of different levels or different types, and determines the first control information, that is, a control decision made by the MDC. Then the MDC outputs the first control information to an external device in S209, where the first control information is used to control the external device.

[0078] For example, the first vehicle function is a function of automatic reversing into parking space, and precision of processing levels of data from sensors at various locations that is required by the MDC to finally make a decision to continue reversing is different. Therefore, after receiving data of different processing levels, the MDC performs data fusion, and makes a decision to continue reversing. The external device may be a rotating shaft of vehicle tires, and the first control information controls the rotating shaft of the vehicle tires to continue rotating.

[0079] According to the solution of this application, different levels of processing and fusion are performed on sensor data by using the plurality of levels of control units, to improve accuracy of a control decision, and improve driving safety of a vehicle.

[0080] FIG. 3A and FIG. 3B are a schematic flowchart of an example of a vehicle sensor data processing method according to an embodiment of this application.

[0081] Each control unit included in FIG. 3A and FIG. 3B corresponds to each control unit in the vehicle sensor data processing system 100 in FIG. 1. For a connection manner thereof, refer to FIG. 1. FIG. 3A and FIG. 3B may be a schematic flowchart of a vehicle sensor data processing method for controlling a first vehicle function of a vehicle. For example, the first vehicle function may be cruising, route planning, or braking.

[0082] S301: Configure intelligent driving information.

[0083] The intelligent driving configuration information may include configuration information of a sensor, and the configuration information of the sensor may be used to configure a priority of each sensor when the first vehicle function is performed.

[0084] In an implementation, the configuration information of the sensor directly indicates the priority of the sensor.

[0085] Optionally, the configuration information of the sensor indicates that a priority of the sensor is a priority A (that is, an example of a first priority) or a priority B (that is, an example of a second priority). After receiving the data from the sensor with the priority A, an ECU processes the data from the sensor and outputs obtained data B. After receiving the data from the sensor with the priority B, the ECU makes a control decision based on the data from the sensor. That is, the ECU processes the data from the sensor and outputs control information B (that is, an example of second control information), where the control information B is used to control an external device.

[0086] Optionally, the priority that is of the sensor and that is indicated by the configuration information of the sensor includes three levels, for example, priority A, priority A, and priority C.

[0087] The priority A (that is, an example of the first priority) indicates that the data from the sensor is processed by an MCU to make a control decision.

[0088] For example, if an ECU 1 determines, based on the configuration information, that a priority of a sensor 1 is the priority A, the ECU 1 receives data from the sensor 1, processes the data, and outputs data B1 to a DCU. Similarly, if an ECU 2 determines that a priority of a sensor 2 is the priority A, the ECU 2 receives data from the sensor 2, processes the data, and outputs data B2 to the DCU. The DCU receives the data B1 and the data B2. In S305, priorities of sensors are determined. The priorities of the two sensors are determined as A. The received data is fused and data C is output to the MCU, and the MCU makes a control decision based on the data from the two sensors.

[0089] The priority B (that is, an example of the second control information) indicates that the data from the sensor is processed by the ECU to make a control decision.

[0090] The priority C (that is, another example of the first priority) indicates that the data from the sensor is processed by the DCU to make a control decision. That is, data from sensors with the priority A and the priority C needs to be fused with other data, and then the MCU or the DCU makes the control decision.

[0091] For example, if the priorities of the sensor 1 and the sensor 2 are the priority C, after the DCU receives the data B1 and the data B2 that are obtained through processing by the ECU 1 and the ECU 2, the DCU fuses the data and makes a control decision in S305, and outputs the control decision, that is, control information C, to an external device in S306.

[0092] In another implementation, the intelligent driving configuration information includes configuration information of a processing delay requirement of sensor data and configuration information of a processing delay threshold of a control unit (an ECU and/or a DCU).

[0093] The ECU and/or the DCU determine/determines a priority of the sensor based on the delay requirement of the sensor data and the threshold. When the delay requirement of the sensor is greater than or equal to the threshold, the sensor is a sensor with the first priority, that is, the first priority indicates that the control unit processes the data from the sensor and then outputs the obtained data (data B or data C). Alternatively, when the delay requirement of the sensor is less than or equal to the threshold, the sensor is a sensor with the second priority, that is, the second priority indicates that the control unit makes a control decision based on the data from the sensor, and outputs control information to an external device. In specific implementation, when the delay requirement is equal to the threshold, the sensor may be determined as a sensor with the first priority or a sensor with the second priority. This is not limited in this application.

[0094] According to the foregoing solution, on a basis of ensuring the processing delay requirement of the sensor data, different levels of processing and fusion are performed on the sensor data by using the plurality of levels of control units, to improve accuracy of a control decision, and improve driving safety of a vehicle.

[0095] S302: An ECU determines, based on a priority of a sensor, to send the data B or the control information B.

[0096] After each ECU determines, based on the intelligent driving configuration information, a priority of a sensor connected to the ECU, the ECU determines, based on the priority of the sensor, to send the data B or the control information B.

[0097] For example, if sensors connected to the ECU 1 and the ECU 2 are sensors with the first priority, for example, the sensor 1 and the sensor 2 are sensors with the priority A, or delay requirements of the sensor 1 and the sensor 2 are greater than or equal to the threshold, the ECU 1 and the ECU 2 process data from the sensors and obtain the data B1 and the data B2, and then output the data B1 and the data B2 to the DCU in S304.

[0098] For another example, if the sensor 3 connected to the ECU 3 is a sensor with the second priority, for example, the sensor 3 is a sensor with the priority C, or a delay requirement of the sensor 3 is greater than or equal to the threshold, the ECU 3 makes a control decision based on the data from the sensor, and outputs control information B3 to an external device in S303.

[0099] S305: The DCU determines, based on the priority of the sensor, to send the data C or the control information C.

[0100] The DCU determines a priority of a lower-level sensor of the DCU based on the intelligent driving configuration information, to determine to send the data C or the control information C after receiving sensor data that is processed and output by the ECU or after receiving data from the sensor.

[0101] For example, if the DCU determines that the priorities of the lower-level sensor 1 and the lower-level sensor 2 are the first priority, after receiving the data B1 and the data B2, the DCU processes the data and obtains the data C, where the data C may include data obtained after the data B1 and the data B2 are fused and/or decision information of the DCU for reference by the MCU. In S306, the DCU outputs the data C to the MDC.

[0102] For another example, the DCU is further connected to a sensor 7 (not shown in the figure), and the sensor 7 is a sensor with the second priority. For example, if a delay requirement of the sensor is less than or equal to the threshold, the DCU makes a control decision based on data from the sensor to obtain control information C, and sends the control information C to an external device in S306, where the control information is used to control the external device.

[0103] S307: The sensor 4 outputs data A4 to the MDC.

[0104] S308: The MDC fuses the received data to determine first control information.

[0105] S309: The MDC outputs the first control information to an external device.

[0106] S307, S308, and S309 are respectively the same as or similar to S207, S208, and S209 in FIG. 2. For specific implementations, refer to the foregoing descriptions of S207, S208, and S209 in FIG. 2. For brevity, details are not described again.

[0107] According to the foregoing solution, on a basis of ensuring the processing delay requirement of the sensor data, different levels of processing and fusion are performed on the sensor data by using the plurality of levels of control units, to improve accuracy of vehicle control, and improve driving safety of a vehicle.

[0108] The methods provided in embodiments of this application are described above in detail with reference to FIG. 2 and FIG. 3A and FIG. 3B. The following describes in detail a vehicle sensor data processing system according to an embodiment of this application.

[0109] The vehicle sensor data processing system includes a plurality of levels of control units and at least two sensors, where the plurality of levels of control units include a first control unit and at least one second control unit, and the first control unit is an upper-level control unit of the second control unit.

[0110] The second control unit is configured to receive first data, and output second data to the first control unit, where the first data is from a sensor connected to the second control unit or is from a third control unit. The first control unit is configured to output first control information to an external device based on the second data from the one or more second control units, where the first control information is used to control the external device.

[0111] For example, the first control unit is an MCU. When the vehicle sensor data processing system includes three levels of control units, the second control unit may be a DCU or an ECU, and the third control unit may be an ECU connected to a DCU. When the vehicle sensor data processing system includes two levels of control units, the second control unit may be an ECU.

[0112] Optionally, when a data processing mode is set to a multi-level processing mode, the second control unit determines to process the first data, where the second data is data obtained by processing the first data. Alternatively, when the data processing mode is set to a non-multi-level processing mode, the second control unit determines to forward the first data, where the second data is the first data.

[0113] For the data processing mode, refer to the description of the data processing mode in FIG. 2. For brevity, details are not described again.

[0114] Optionally, when a sensor that sends the first data is a sensor of a first priority, the second control unit outputs the second data. Alternatively, when the sensor that sends the first data is a sensor of a second priority, the second control unit outputs second control information to an external device, where the second control information is used to control the external device.

[0115] The second control unit may determine the priority of the sensor based on configuration information of the sensor, where the configuration information of the sensor is used to indicate the priority of the sensor. Alternatively, the second control unit may determine the priority of the sensor based on a delay requirement of the sensor and a first threshold, where the sensor is a sensor of the first priority when the delay requirement of the sensor is greater than or equal to the first threshold, or the sensor is a sensor of the second priority when the delay requirement of the sensor is less than or equal to the first threshold.

[0116] For a specific implementation of the priority of the sensor, refer to the priority of the sensor in FIG. 3A and FIG. 3B. For brevity, details are not described again.

[0117] Optionally, the first control unit is specifically configured to output the first control information to the external device based on the second data from the one or more second control units and data from the one or more first sensors, where the first sensor is a sensor connected to the first control unit.

[0118] Optionally, the third control unit is configured to receive data from a fourth control unit or data from a second sensor, the second sensor connects to the third control unit, and the fourth control unit is a lower-level control unit of the third control unit.

[0119] This application provides a vehicle sensor data processing apparatus. The vehicle sensor data processing apparatus may include units configured to perform the method 200 in FIG. 2 and the method 300 in FIG. 3A and FIG. 3B.

[0120] This application further provides a vehicle sensor data processing apparatus, including at least one processor. The at least one processor is coupled to a memory, and may be configured to perform the method 200 in FIG. 2 and the method 300 in FIG. 3A and FIG. 3B. Optionally, a communications apparatus further includes a memory. Optionally, the vehicle sensor data processing apparatus further includes a communications interface, and the processor is coupled to the communications interface. The communications interface may be an input/output interface. The input/output interface may be an input/output circuit.

[0121] This application further provides a processor, including an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal by using the input circuit, and transmit a signal by using the output circuit, so that the processor can be configured to perform the method 200 in FIG. 2 and the method 300 in FIG. 3A and FIG. 3B.

[0122] In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, or the like. An input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver. A signal output by the output circuit may be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be a same circuit, where the circuit is used as the input circuit and the output circuit at different moments. Specific implementations of the processor and the circuits are not limited in embodiments of this application.

[0123] It should be understood that a related data exchange process, for example, sending data or information may be a process of outputting data or information from the processor, and receiving data or information may be a process of receiving input data or information by the processor. Specifically, data output by the processor may be output to the transmitter, and input data received by the processor may be from the receiver. The transmitter and the receiver may be collectively referred to as a transceiver.

[0124] The processor may be a chip. The processor may be implemented by using hardware, or may be implemented by using software. When implemented by using the hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented by using the software, the processor may be a general-purpose processor, and is implemented by reading software code stored in a memory. The memory may be integrated into the processor, or may be located outside the processor and exist independently.

[0125] This application further provides a computer program product. The computer program product includes a computer program (which may also be referred to as code or instructions). When the computer program is run, a computer is enabled to perform the method 200 in FIG. 2 and the method 300 in FIG. 3A and FIG. 3B.

[0126] This application further provides a computer-readable medium. The computer-readable medium stores a computer program (which may also be referred to as code or instructions). When the computer program is run on a computer, the computer is enabled to perform the method 200 in FIG. 2 and the method 300 in FIG. 3A and FIG. 3B.

[0127] An embodiment of this application further provides a processing apparatus, including a processor and an interface. The processor is configured to perform the method in any one of the foregoing method embodiments.

[0128] It should be understood that the processing apparatus may be one or more chips. For example, the processing apparatus may be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or another integrated chip.

[0129] In an implementation process, steps in the foregoing methods may be completed by using an integrated logic circuit of hardware in the processor or by using instructions in a form of software. Steps of the methods disclosed with reference to embodiments of this application may be directly executed and accomplished by a hardware processor, or may be executed and accomplished by using a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and a processor reads information in the memory and completes the steps of the foregoing method in combination with hardware of the processor. To avoid repetition, details are not described herein again.

[0130] It should be noted that, the processor in embodiments of this application may be an integrated circuit chip, and has a signal processing capability. In an implementation process, steps in the foregoing method embodiments may be completed by using an integrated logic circuit of hardware in the processor or by using instructions in a form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component. The processor may implement or execute the methods, steps, and logical block diagrams disclosed in embodiments of this application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. Steps of the methods disclosed with reference to embodiments of this application may be directly executed and accomplished by using a hardware decoding processor, or may be executed and accomplished by using a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and a processor reads information in the memory and completes the steps of the foregoing method in combination with hardware of the processor.

[0131] It may be understood that the memory in embodiments of this application may be a volatile memory or a non-volatile memory, or may include a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) that is used as an external cache. Through example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that, the memory of the systems and methods described in this specification includes but is not limited to these and any other memories of appropriate types.

[0132] All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented entirely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or some of the procedures or functions according to embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, for example, a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk drive, or a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), a semiconductor medium (for example, a solid-state drive (solid-state disc, SSD)), or the like.

[0133] Terms such as “component”, “module”, and “system” used in this specification indicate computer-related entities, hardware, firmware, combinations of hardware and software, software, or software being executed. For example, a component may be, but is not limited to, a process that runs on a processor, a processor, an object, an executable file, an execution thread, a program, and/or a computer. As illustrated by using figures, both a computing device and an application that runs on the computing device may be components. One or more components may reside within a process and/or a thread of execution, and a component may be located on one computer and/or distributed between two or more computers. In addition, these components may be executed from various computer-readable media that store various data structures. For example, the components may communicate by using a local and/or remote process and based on, for example, a signal having one or more data packets (for example, data from two components interacting with another component in a local system, a distributed system, and/or across a network such as the Internet interacting with other systems by using the signal).

[0134] A person of ordinary skill in the art may be aware that, in combination with the examples described in embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0135] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[0136] In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiment is merely an example. For example, division into units is merely logical function division and may be other division in an actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0137] The units described as separate components may or may not be physically separate, and components displayed as units may or may not be physical units. To be specific, the components may be located at one position, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions in embodiments.

[0138] In addition, functional units in embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit.

[0139] The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.