CN115840409A

CN115840409A - Vehicle data acquisition method, domain controller and vehicle

Info

Publication number: CN115840409A
Application number: CN202310124830.4A
Authority: CN
Inventors: 郝松
Original assignee: Xiaomi Automobile Technology Co Ltd
Current assignee: Xiaomi Automobile Technology Co Ltd
Priority date: 2023-02-03
Filing date: 2023-02-03
Publication date: 2023-03-24

Abstract

The utility model relates to a vehicle data acquisition method, domain controller and vehicle belongs to the vehicle field, the method includes: acquiring internal signal data between internal functional units of a domain controller; and acquiring bus signal data on the CAN bus, and combining the bus signal data and the internal signal data to obtain full signal data. Through respectively obtaining the interactive internal signal data of the functional units in the domain controller and the bus signal data on the CAN bus, the full signal data of the vehicle comprising the internal signal data and the bus signal data is obtained, the signal data in the domain controller CAN be effectively collected, and the problem of incomprehensive data of data acquisition is avoided.

Description

Vehicle data acquisition method, domain controller and vehicle

Technical Field

The disclosure relates to the field of vehicles, and in particular relates to a vehicle data acquisition method, a domain controller and a vehicle.

Background

Automobile electronic systems are becoming more complex, and the operation data of the automobile electronic systems play an important role in automobile health state, fault analysis and accident analysis. The sources and types of data in the vehicle are very many, different data have different functions, and the data at the vehicle end must be collected as completely as possible for more accurate and faster analysis.

In the related art, data of a CAN bus is generally acquired to acquire vehicle end data, however, with the development of vehicle technology, vehicles adopting a domain controller scheme are more common, a plurality of functional units are integrated in a domain controller, signal interaction among the functional units does not adopt CAN communication, and further the problem that data acquisition in a traditional data acquisition mode is incomplete is caused.

Disclosure of Invention

To overcome the problems in the related art, the present disclosure provides a vehicle data acquisition method, a domain controller, and a vehicle.

According to a first aspect of embodiments of the present disclosure, there is provided a vehicle data acquisition method, the method including:

acquiring internal signal data between internal functional units of a domain controller; and the number of the first and second electrodes,

and acquiring bus signal data on the CAN bus, and combining the bus signal data and the internal signal data to obtain full signal data.

Optionally, the domain controller includes a first core and a second core, and a processing performance of the first core is greater than a processing performance of the second core;

an internal signal collection module is disposed within the second core, the internal signal collection module to collect the internal signal data and send the internal signal data to the first core.

Optionally, the domain controller includes a signal conversion module, and the signal conversion module is configured to convert the acquired CAN bus signal into the bus signal data, and send the bus signal data to the first core through an ethernet.

Optionally, the method comprises:

and screening the data of the full signal data to obtain screened target signal data, and uploading the target signal data to a target server.

Optionally, the method further comprises:

receiving a data screening rule;

the data screening of the full-scale signal data comprises:

and performing data screening on the full signal data according to the data screening rule.

According to a second aspect of the embodiments of the present disclosure, there is provided a domain controller of a vehicle, the domain controller including a full-signal-data receiving module;

the full-scale signal data receiving module is configured to:

an internal signal collection module is disposed within the second core, the internal signal collection module configured to collect the internal signal data and send the internal signal data to the first core.

Optionally, the domain controller comprises a data screening module;

the data screening module is configured to perform data screening on the full-scale signal data to obtain screened target signal data, and upload the target signal data to a target server.

Optionally, the domain controller further comprises:

a rule receiving module configured to receive a data screening rule;

the data screening module configured to:

According to a third aspect of the embodiments of the present disclosure, there is provided a vehicle including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

acquiring internal signal data between internal functional units of a domain controller; and the number of the first and second antennas is increased,

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: through respectively obtaining the interactive internal signal data of the functional units in the domain controller and the bus signal data on the CAN bus, the full signal data of the vehicle comprising the internal signal data and the bus signal data is obtained, the signal data in the domain controller CAN be effectively collected, and the problem of incomprehensive data of data acquisition is avoided.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a flow chart illustrating a vehicle data collection method according to an exemplary embodiment.

FIG. 2 is a schematic diagram illustrating a domain controller according to an exemplary embodiment.

FIG. 3 is a schematic diagram illustrating a vehicle data collection system according to an exemplary embodiment.

FIG. 4 is a functional block diagram schematic of a vehicle shown in accordance with an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

It should be noted that all actions of acquiring signals, information or data in the present application are performed under the premise of complying with the corresponding data protection regulation policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.

FIG. 1 is a flow chart illustrating a method of vehicle data collection, as shown in FIG. 1, according to an exemplary embodiment, the method comprising:

s101, internal signal data among internal functional units of the domain controller are obtained.

It is noted that the vehicle may be provided with a plurality of domain controllers, for example, a body domain controller, a driving assistance domain controller, a power transmission domain controller, and the like.

In some embodiments, the internal signal data may be signal data generated upon interaction between functional units within the domain control.

The internal functional units inside the domain controller may have a communication link therebetween for signal interaction, where the communication link may be, for example, interprocess communication or ethernet communication, which is not limited in this disclosure. In addition, in some embodiments, the internal functional unit may further determine, through signal interaction, a signal that needs to be sent to the CAN bus, and send the signal to the CAN bus after a series of processing, for example, processing the signal using an AutoSAR (automotive open System Architecture) component.

S102, bus signal data on the CAN bus are obtained, and the total signal data are obtained by combining the bus signal data and the internal signal data.

The obtaining sequence of the internal signal data and the bus signal data in the above steps S101 and S102 is not particularly limited in this disclosure, for example, in some examples, the bus signal data may be obtained first and then the internal signal data is obtained, or the obtaining of the internal signal data and the obtaining of the bus signal data may be performed simultaneously. In addition, the above steps S101 and S102 may be periodically performed according to a preset period. Alternatively, the domain controller may be executed in response to an instruction of an external device, and illustratively, the domain controller starts execution of steps S101 and S102 in response to a data acquisition instruction of the T-BOX (telematics BOX).

In the embodiment of the disclosure, the internal signal data interacted with the functional units in the domain controller and the bus signal data on the CAN bus are respectively obtained, so that the full-scale signal data of the vehicle comprising the internal signal data and the bus signal data is obtained, the signal data in the domain controller CAN be effectively collected, and the problem of incomplete data acquisition is avoided.

In some optional embodiments, the domain controller comprises a first core and a second core, the processing performance of the first core being greater than the processing performance of the second core;

The internal signal data may include only internal signal data between the functional units in the second core, or may also include internal signal data between the first core and the functional units in the second core. That is, the internal functional unit may be a functional unit in the first core or a functional unit in the second core.

Alternatively, the steps of the method shown in fig. 1 may be specifically executed by the first core in the domain controller.

It is to be understood that the internal signal collection module may serve as a functional unit in the second core. The first core and the second core may exchange information through Inter-core communication, for example, an Inter-Platform communication framework (IPCF), an Inter-process communication (IPC), or the like.

Wherein the first core may be a core of a Cortex-A hardware platform, in which an operating system may be deployed; the second core is the core of the Cortex-M hardware platform, in which the AutoSar component is deployed. The operating system may be, for example, a Linux system or a Unix system, and the AutoSar component may be an AutoSar AP component or an AutoSar CP component, which is not specifically limited in this disclosure.

In one example, each functional unit of the second core may be, for example, a software component (SWC), and one software component may be composed of a plurality of atomic components as a minimum logical unit, and the minimum logical unit may be, for example, two types of application programs and sensors/actuators.

Further, the first core may be a device that obtains bus signal data and internal signal data through an SOA (Service-oriented architecture) Service pre-deployed in the operating system, for example, an external device such as a T-BOX may obtain bus signal data on a CAN bus by calling a first SOA Service in the first core and obtain internal signal data between software components in a second core by calling a second SOA Service, or obtain both bus signal data and internal signal data by calling a third SOA Service. The second core may send the internal signal data to the first core, and the first core returns the internal signal data and/or the bus signal data as a return parameter of the SOA service to the external device.

By adopting the scheme, each functional unit is deployed in the second core, the internal signal collection module is deployed to collect the internal signal data interacted among the functional modules, and the internal signal data is sent to the first core with stronger processing capability through the internal signal collection module to further process the internal signal data, so that the integrity of the collection of the internal signal data and the reliability of data processing can be effectively ensured.

In some optional embodiments, the domain controller includes a signal conversion module, and the signal conversion module is configured to convert the collected CAN bus signal into the bus signal data, and send the bus signal data to the first core through an ethernet.

The signal conversion module CAN convert CAN signals collected by the CAN transceiver into bus signal data, and CAN convert the signal data which are required to be sent to the CAN bus by the second core into CAN signals and send the CAN signals to the CAN bus through the CAN transceiver.

In addition, before the bus signal data is sent to the first core through the ethernet, a timestamp may be further stamped on the bus signal data through the hardware accelerator, where the timestamp may be a corresponding time when the CAN transceiver receives the bus signal data.

By adopting the scheme, the signal conversion module is arranged, the CAN signal CAN be effectively converted into the bus signal data which is convenient for Ethernet transmission, so that the first core CAN reliably and comprehensively obtain the bus signal data on the CAN bus, and the integrity of bus signal data acquisition is further ensured.

In further optional embodiments, the method comprises:

and carrying out data screening on the full-scale signal data to obtain screened target signal data, and uploading the target signal data to a target server.

The data filtering may include, for example, deduplication processing, time filtering, processing invalid values and missing values, and the like.

In addition, the target server may be, for example, a car networking platform, or may be a TSP (telematics service Provider), and the target server may further analyze the target signal data uploaded by the domain controller. Specifically, the target signal data is uploaded to the target server, and the target signal data may be sent to the T-BOX on the vehicle and then sent to the target server by the T-BOX.

Alternatively, the data filtering step may be implemented by a data filtering module in the first core, and the uploading the target signal data to the target server may be implemented by a service management and uploading module in the first core, where the data filtering module and the service management and uploading module may be application programs deployed in the first core operating system.

It can be understood that the data volume of the acquired full-scale signal data is large, by adopting the scheme, invalid values and missing values in the full-scale signal data can be cleaned through data screening, unnecessary data can be screened according to actual requirements, and target signal data which more meet requirements can be acquired under the condition of ensuring the integrity of the signal data.

In further optional embodiments, the method further comprises:

receiving a data screening rule;

the data screening of the full-scale signal data comprises:

The data screening rule may be sent by the target server according to the data analysis requirement, and the vehicle may receive the data screening rule sent by the target server through the T-BOX and send the data screening rule to the domain controller. The data filtering rules may include, for example, time thresholds for time filtering, threshold parameters for handling invalid and missing values, and so on.

Optionally, the data filtering rule may further include keyword information, for example, the target server may send a data acquisition request carrying a keyword to the domain controller through the T-BOX according to a data analysis requirement of the target server, and the domain controller may filter the full-scale signal data according to the keyword after acquiring the full-scale signal data, so as to obtain the target signal data including the keyword, which is requested by the target server.

By adopting the scheme, the target signal data which better meets the requirements of the target server can be obtained by receiving the data screening rule and screening the full-scale signal data according to the data screening rule.

Based on the same inventive concept, fig. 2 is a schematic diagram illustrating a domain controller of a vehicle according to an exemplary embodiment, as shown in fig. 2, a domain controller 20 includes:

a full-signal-data receiving module 21 configured to:

acquiring internal signal data between internal functional units of the domain controller 20; and the number of the first and second electrodes,

Optionally, the domain controller 20 includes a first core and a second core, and the processing performance of the first core is greater than that of the second core;

In some alternative embodiments, the full signal data reception module 21 may be deployed within the first core.

Optionally, the domain controller 20 includes a signal conversion module, and the signal conversion module is configured to convert the collected CAN bus signal into the bus signal data, and send the bus signal data to the first core through an ethernet.

Optionally, the domain controller 20 includes:

and the data screening module is configured to perform data screening on the full-scale signal data to obtain screened target signal data, and upload the target signal data to a target server.

Optionally, the domain controller 20 includes:

a rule receiving module configured to receive a data screening rule;

a data screening module configured to:

With regard to the domain controller 20 in the above-described embodiment, the specific manner in which the respective modules perform operations has been described in detail in the embodiment related to the method, and will not be elaborated here.

The domain controller 20 is an Integrated Circuit (IC) or a chip, wherein the IC may be one IC or a collection of ICs; the chip may include, but is not limited to, the following categories: a GPU (Graphics Processing Unit), a CPU (Central Processing Unit), an FPGA (Field Programmable Gate Array), a DSP (Digital Signal Processor), an ASIC (Application Specific integrated circuit), an SOC (System on Chip, or System on Chip), and the like. The integrated circuit or chip can be used for executing executable instructions (or codes) to realize the vehicle data acquisition method. Where the executable instructions may be stored in the integrated circuit or chip or may be retrieved from another device or apparatus, for example, where the integrated circuit or chip includes a processor, a memory, and an interface for communicating with other devices. The executable instructions may be stored in the memory, and when executed by the processor, implement the data processing method described above; alternatively, the integrated circuit or chip may receive the executable instructions through the interface and transmit the executable instructions to the processor for execution, so as to implement the vehicle data acquisition method.

In order to make the technical solutions provided by the present disclosure more comprehensible, the present disclosure also provides a schematic diagram of a vehicle data acquisition system as shown in fig. 3 according to an exemplary embodiment, as shown in fig. 3, the system includes a target domain controller 300, a T-BOX330, and a TSP 340, the target domain controller 300 includes a first core 310 and a second core 320, the target domain controller 300 is connected with the T-BOX330 and a CAN bus, the ECU 1, the ECU 2 to the ECU N are connected to the CAN bus, and the T-BOX330 is communicatively connected with the TSP 340.

The second core 320 is disposed with a plurality of function units 322 and an internal signal collection module 321, the plurality of function units 322 have different functions, the plurality of function units 322 may also determine signal data that needs to be sent to the CAN bus, and send the signal data to the hardware accelerator 350, and then send the signal data to the CAN bus through the hardware accelerator 350 and the CAN transceiver 360, and the internal signal collection module 321 is configured to collect internal signal data when the plurality of function units 322 interact with each other, and send the internal signal data to the internal signal receiving module 311 in the first core 310.

In addition, the CAN transceiver 360 is further configured to acquire a CAN signal on the CAN bus, convert the CAN signal into bus signal data through the hardware accelerator 350, stamp the bus signal data with a timestamp, and send the bus signal data to the full signal data acquisition module 312 through the ethernet, the full signal data acquisition module 312 is further configured to acquire internal signal data received by the internal signal receiving module 311, combine the internal signal data and the bus signal data, and send the combined internal signal data and the bus signal data to the data screening module 313, the data screening module 313 is configured to perform data screening on the combined full signal data and send the data to the service management and upload module 314, so that the service management and upload module 314 sends the screened target signal data to the TSP 340 through the T-BOX330, and further, the TSP 340 CAN acquire the operation data of the screened full vehicle, and further process and analyze the acquired data.

It should be understood by those skilled in the art that, in the implementation, the vehicle data collecting system shown in fig. 3 may further include other functional modules and other connections, and fig. 3 only shows one possible implementation, and the other possible functional modules and connections are not shown.

For example, the target domain controller 300 may further include a rule receiving module, which is configured to receive the data screening rule sent by the TSP 340 through the T-BOX330, and send the data screening rule to the data screening module 313, so that the data screening module 313 performs data screening according to the data screening rule.

Additionally, in some optional embodiments, the second core 320 may also be connected with the CAN transceiver 360 to enable the functional unit 322 to acquire signals on the CAN bus.

The full signal data acquisition module 312 shown in fig. 3 may be equivalent to the full signal data receiving module 21 shown in fig. 2. The modules described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a module does not in some cases constitute a limitation of the module itself, for example, a full-signal-data collection module may also be described as a "module for collecting full-signal data", or the like.

FIG. 4 is a block diagram illustrating a vehicle 400 according to an exemplary embodiment. For example, the vehicle 400 may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other type of vehicle. Vehicle 400 may be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

Referring to fig. 4, a vehicle 400 may include various subsystems such as an infotainment system 410, a perception system 420, a decision control system 430, a drive system 440, and a computing platform 450. The vehicle 400 may also include more or fewer subsystems, and each subsystem may include multiple components, among others. In addition, the interconnection between each subsystem and each component of the vehicle 400 may be achieved by wire or wirelessly.

In some embodiments, the infotainment system 410 may include a communication system, an entertainment system, a navigation system, and the like.

The sensing system 420 may include several sensors for sensing information about the environment surrounding the vehicle 400. For example, the sensing system 420 may include a global positioning system (the global positioning system may be a GPS system, a beidou system, or other positioning system), an Inertial Measurement Unit (IMU), a laser radar, a millimeter-wave radar, an ultrasonic radar, and a camera.

Decision control system 430 may include a computing system, a vehicle control unit, a steering system, a throttle, and a braking system.

The drive system 440 may include components that provide powered movement to the vehicle 400. In one embodiment, the drive system 440 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engine, electric motor, air compression engine. The engine is capable of converting energy provided by the energy source into mechanical energy.

Some or all of the functions of the vehicle 400 are controlled by the computing platform 450. Computing platform 450 may include at least one processor 451 and memory 452, where processor 451 may execute instructions 453 stored in memory 452.

The processor 451 may be any conventional processor, such as a commercially available CPU. The processor may also include, for example, a Graphics Processor Unit (GPU), a Field Programmable Gate Array (FPGA), a System On Chip (SOC), an Application Specific Integrated Circuit (ASIC), or a combination thereof. The processor 451 may also be the domain controller provided by the above embodiments.

The memory 452 may be implemented by any type or combination of volatile or non-volatile storage devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

In addition to instructions 453, memory 452 may store data such as road maps, route information, vehicle position, direction, speed, etc. The data stored by memory 452 may be used by computing platform 450.

In the disclosed embodiment, the processor 451 may execute the instructions 453 to perform all or a portion of the steps of the vehicle data collection method described above.

In another exemplary embodiment, a computer program product is also provided, which comprises a computer program executable by a programmable device, the computer program having code portions for performing the above-mentioned vehicle data acquisition method when executed by the programmable device.

The present disclosure also provides a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the vehicle data acquisition method provided by the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice in the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A vehicle data collection method, the method comprising:

2. The method of claim 1, wherein the domain controller comprises a first core and a second core, wherein a processing performance of the first core is greater than a processing performance of the second core;

3. The method of claim 2, wherein the domain controller comprises a signal conversion module configured to convert the collected CAN bus signal into the bus signal data and send the bus signal data to the first core via an Ethernet.

4. A method according to any of claims 1-3, characterized in that the method comprises:

5. The method of claim 4, further comprising:

receiving a data screening rule;

the data screening of the full-scale signal data comprises:

6. A domain controller of a vehicle, characterized in that the domain controller comprises a full-signal data receiving module;

the full-scale signal data receiving module is configured to:

7. The domain controller of claim 6, wherein the domain controller comprises a first core and a second core, the processing performance of the first core being greater than the processing performance of the second core;

8. The domain controller according to claim 7, wherein the domain controller comprises a signal conversion module configured to convert the collected CAN bus signals into the bus signal data and to transmit the bus signal data to the first core via an Ethernet network.

9. Domain controller according to any of the claims 6-8, characterized in that the domain controller comprises a data screening module;

10. The domain controller according to claim 9, wherein the domain controller further comprises:

a rule receiving module configured to receive a data screening rule;

the data screening module configured to:

11. A vehicle, characterized by comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to: