CN117749624A

CN117749624A - Configurable method for vehicle data acquisition

Info

Publication number: CN117749624A
Application number: CN202311740942.9A
Authority: CN
Inventors: 杜明明; 杨锋; 李江良; 陈碧丽; 张祖鹏; 施俊柏
Original assignee: Lianyou Zhilian Technology Co ltd
Current assignee: Lianyou Zhilian Technology Co ltd
Priority date: 2023-12-15
Filing date: 2023-12-15
Publication date: 2024-03-22

Abstract

The invention provides a configurable method for vehicle data acquisition, which comprises the following steps: s1, uploading a configuration file of a T-BOX end to a TSP platform; configuring a signal rule table containing signal information formulated according to a communication protocol and a signal matrix into a configuration file, transmitting the configuration file to an NAD terminal, and updating and storing the configuration file by the NAD terminal according to the latest configuration file issued by the TSP platform; s2, analyzing the configuration file according to the updated configuration file NAD terminal to obtain a signal rule table; the vehicle information can be flexibly collected, the time and the period of data collection can be flexibly configured, the data transmission load can be reduced, the data collection efficiency can be improved, the load rate can be reduced, and the real-time performance, the accuracy and the safety of data transmission can be greatly ensured.

Description

Configurable method for vehicle data acquisition

Technical Field

The invention relates to the technical field of vehicle data processing, in particular to a configurable method for vehicle data acquisition.

Background

The automobile data acquisition is to collect data such as the surrounding environment, the state and the driving behavior of the automobile through equipment such as sensors, cameras and radars carried on the automobile. Such data may include images, video, lidar scans, inertial Measurement Unit (IMU) data, GPS location information, and the like. The goal of automotive data collection is to provide real-time, accurate vehicle and environmental data as input to the autopilot system for perception, decision making and control. The existing data acquisition scheme is used for acquiring vehicle data through an acquisition function in a vehicle-mounted data acquisition terminal (T-BOX) firmware or an acquisition program written by the user. The vehicle body information collected by the collection program is often displayed as solidified on the vehicle-mounted terminal. Before the era of intelligent everything interconnection, the types of data to be acquired are small, and the load of the data can be borne even if the data are acquired in full quantity, so that the acquisition logic is feasible to use.

However, with the rapid development of the intelligent internet of vehicles technology, the whole vehicle network topology is more and more complex, and the current situation presented by the collected data is represented as follows: the data size of the data which can be acquired is larger and larger, the acquisition frequency of the data is changed from the second level to the millisecond level, the dimension of the data is also more and more, for example, bus signals, internal states of sensors, software embedded points, user behaviors, road and environment sensing data and the like, the data quality requirement is higher, and the problem that the service analysis data is seriously affected by loss, disorder, jump, delay and the like in the traditional mode is solved. Under traditional data acquisition mode, its mode that embodies data acquisition is fixed, can't change the data of gathering at all in a flexible way, and data acquisition volume is few, gathers and analysis cost is high, gathers the cycle length.

The body information has more and more data to collect, and if the total amount of data is collected, the collected data amount is too large, so that precious bandwidth resources are occupied.

The prior CAN bus data acquisition method with the patent number of CN115225422A is based on the data acquisition device integrated in the vehicle-mounted controller to acquire data, and is more focused on the realization of the acquisition method.

The prior patent number CN113459971A discloses a data acquisition method for acquiring vehicle data information, and focuses on a data acquisition method and transmission efficiency.

The prior patent number CN116224871A discloses a data acquisition device, by improving the hardware integration level, the redundancy of equipment and wiring harness arrangement are reduced, the cost is saved, the functions of data acquisition and writing are integrated into a single hardware system, the on-vehicle and off-line data writing are realized, the data of multiple channels can be subjected to deep fusion, and the data processing efficiency is greatly improved.

The prior patent number CN115107784A discloses a driving data acquisition and analysis method, which focuses on acquisition and analysis of driving data, thereby helping customers to pertinently improve existing bad habits and further enabling the behaviors of the customers to be more standard and economical.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a configurable vehicle data acquisition method for improving data acquisition efficiency and reducing load rate aiming at the defects of the technical scheme.

The invention provides a configurable method for vehicle data acquisition, which comprises the following steps:

s1, uploading a configuration file of a T-BOX end to a TSP platform; configuring a signal rule table containing signal information formulated according to a communication protocol and a signal matrix into a configuration file, transmitting the configuration file to an NAD terminal, and updating and storing the configuration file by the NAD terminal according to the latest configuration file issued by the TSP platform;

s2, analyzing the configuration file according to the updated configuration file NAD terminal to obtain a signal rule table;

s3, importing the DBC file into an Autosar BSW module at the MCU end, configuring the Autosar BSW module through a ZSAR Studio tool, verifying the configured Autosar BSW module, obtaining corresponding vehicle data information through a working mechanism of the ZSAR Studio by the verified Autosar BSW module, and finally generating an RTE interface capable of being called by an upper layer according to the corresponding vehicle data information; the method comprises the steps of carrying out a first treatment on the surface of the

S4, the MCU end carries out full detection on signals according to the generated RTE interface which can be called by the upper layer, and the NAD end synchronizes signal information contained in the signal rule table to the MCU end after signal detection according to the signal rule table analyzed in the step S2;

and S5, the MCU end distinguishes triggering and periodical signals according to signals synchronized by the NAD end, so that different functions are called to carry out data packaging, the MCU automatically sends the triggered related signals to the NAD end, the NAD end carries out abstract processing on the signals packaged by the MCU, and vehicle data information is uploaded to the TSP platform according to a formulated vehicle-mounted terminal communication protocol.

The configurable method for vehicle data acquisition comprises the following steps of; the signal rule table includes a signal transmission or reception period, a signal length, and a signal transmission type in the step S2.

The configurable method for vehicle data acquisition comprises the following steps of; in the step S3, the Autosar BSW module sends and receives signals to and from different vehicle-mounted ECUs in an SGW manner.

The configurable method for vehicle data acquisition comprises the following steps of; in the step S3, the Autosar BSW module includes a CAN layer, a CANIF layer, a PDUR layer, and a COM layer.

The configurable method for vehicle data acquisition comprises the following steps of; in the step S3, the CAN layer, the CANIF layer, the PDUR layer and the COM layer are configured from bottom to top through the ZSAR Studio tool, the configured CAN layer, CANIF layer, PDUR layer and COM layer are verified, the verified CAN layer, CANIF layer, PDUR layer and COM layer obtain corresponding vehicle data information through a working mechanism of the ZSAR Studio, and finally a RTE interface capable of being invoked by upper layers is generated according to the corresponding vehicle data information.

The configurable method for vehicle data acquisition comprises the following steps of; the step S6 includes the steps of:

s51, the MCU compares the signal information sent by the NAD terminal with the signal data information by calling a comparison function, and divides the signal function of the trigger type and the period type according to different RTE interface types.

The configurable method for vehicle data acquisition comprises the following steps of; the step S6 further includes the steps of:

s52, packaging the signal functions of the divided trigger type and the period type to form a signal data packet.

The configurable method for vehicle data acquisition comprises the following steps of; in step S6, the NAD end requests periodic data according to the fastest frequency in the signals contained in the configuration file.

The configurable method for vehicle data acquisition comprises the following steps of; in the step S5, the NAD terminal uploads the vehicle data information to the TSP platform through the 4G or 5G network according to the vehicle terminal communication protocol established by the national vehicle communication standard.

The configurable method for vehicle data acquisition can flexibly acquire vehicle information, flexibly configure time and period of data acquisition, reduce data transmission load, not only improve data acquisition efficiency, but also reduce load rate, and greatly ensure real-time, accuracy and safety of data transmission.

Drawings

FIG. 1 is a flow chart of an embodiment of a vehicle data acquisition configurable method of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The following are relevant terms and definitions of the invention:

T-BOX terminal: the intelligent terminal T-BOX (Telematics BOX) of the Internet of vehicles, also called as a remote information processing control unit (Telematics Control Unit, TCU), integrates functional modules such as a GPS, an external communication interface, an electronic processing unit, a microcontroller, a mobile communication unit, a memory and the like. The intelligent vehicle monitoring system has the main functions of vehicle data information collection, vehicle fault monitoring, vehicle condition report, remote unlocking of windows, remote starting and stopping of vehicles, remote switching of air conditioners, remote seat adjustment, information sharing, communication, safety theft prevention, vehicle diagnosis, remote upgrading and the like.

MCU: the micro control unit (Micro Controller Unit) is to integrate CPU, RAM, ROM, timer and multiple I/O interfaces of a computer on a chip along with the appearance and development of a large-scale integrated circuit to form a chip-level computer for different combination control for different application occasions.

NAD end: and the network access equipment (Network Access Device) is responsible for connecting the terminal with the base station, ensures that the base station can be connected with one device, receives data packed by the MCU and uploads the data to the base station through the network.

AUTOSAR: the automobile open system architecture (AUTomotive Open System Architecture) aims to solve the complex diversity of the current automobile electronic and electric architecture and the same automobile electronic architecture standard. The whole product life cycle can be maintained, the software can be continuously updated and upgraded in the whole life cycle of the vehicle, the software and the hardware can be separated, the development is flexible, the basic software can be reused, the reusability can cover the whole network node, and even different whole vehicle factories can be crossed.

And (3) ECU: an electronic controller unit (Electronic Control Unit) is provided for controlling the running state of the vehicle and for performing various functions thereof. The method mainly uses various sensors and buses for data acquisition and exchange to judge the state of the vehicle and the intention of a driver and controls the automobile through an actuator.

TSP platform: an automotive remote service provider (Telematics Service Provider) is a service provider that provides automotive intelligent services based on the internet and communication networks. The system mainly relates to functions of vehicle safety, vehicle monitoring, navigation, communication, infotainment, driving behavior analysis and the like.

DBC file: the (Data Base CAN) file is imported into an AUTOSAR project and is used for describing information of each logic node in the CAN network, and the running states of all logic nodes in the CAN network CAN be monitored and analyzed according to the file.

Autosar BSW: a base software layer (Basic Software Layer), at the bottom layer in the AUTOSAR three-layer architecture, the BSW primarily serves the software modules.

Can layer: the controller area network (Controller Area Network) mainly performs access to hardware, and provides an API to the upper layer that is independent of the hardware, i.e. only the Can layer Can access the Can module, and when the Can module initiates a transmission, a callback function of the Can module is called to notify an event, independent of the hardware.

CanIf layer: can Interface layer (Can Interface) this module will provide a unique Interface to manage different Can hardware, such as Can controller and Can transceiver, can if meets the control flow and data flow requirements of the upper communication module of the pdu and AUTOSAR COM stack.

PduR layer: protocol data unit routing (Protocol Data Unit Router), the main functional class of the module is that the PDU receives a local module: receiving network protocol data units of the I-PDU (Interaction Layer Protocol Data) protocol layer from the bottom layer module and transmitting the network protocol data units to one or more upper layer modules; transmitting the PDU from the local module: delivering the I-PDU to one or more underlying modules according to the request of the upper module; PDU gateway: 1) Receiving the I-PDU from the interface module and immediately transmitting the I-PDU through the same or other communication interface module; 2) The I-PDU is received from a transport protocol module and transmitted through the same or other transport protocol module.

Com layer: a Communication module (Communication) which has a main function of managing the transmission and reception of PDUs, transmitting PDUs from one ECU to another, and processing the encapsulation and decapsulation of PDUs; the module can provide signal level processing, such as signal packaging and unpacking, signal conversion, signal filtering and other functions; the method is responsible for managing communication connection between ECUs, and establishing and maintaining the communication connection; it may also provide diagnostic support functions including transmission of fault codes and processing of diagnostic messages. The unified communication environment is provided for the application software of the automobile control unit, a common software communication interface and a common behavior are defined for internal and external communication, and portability of the application software module is enhanced.

RTE interface: the real-time running environment (Runtime Environment) is a core part in the AUTOSAR architecture, realizes communication between upper application software and lower base software, encapsulates communication and services of the base software layer, provides standardized base software and communication interfaces for software components of the application layer, and enables the application layer to call services of the base software through API functions.

FIG. 1 is a flow chart of an embodiment of a vehicle data collection configurable method of the present invention. There is provided a method of vehicle data acquisition configurability comprising the steps of:

in step S1, uploading a configuration file of a T-BOX end to a TSP platform; configuring a signal rule table containing signal information formulated according to a communication protocol and a signal matrix into a configuration file, transmitting the configuration file to an NAD terminal, and updating and storing the configuration file by the NAD terminal according to the latest configuration file issued by the TSP platform;

in step S2, analyzing the configuration file according to the updated configuration file NAD terminal to obtain a signal rule table;

in step S3, importing the DBC file into an Autosar BSW module at the MCU end, configuring the Autosar BSW module through a ZSAR Studio tool, verifying the configured Autosar BSW module, obtaining corresponding vehicle data information through a working mechanism of the ZSAR Studio by the verified Autosar BSW module, and finally generating an RTE interface capable of being invoked by an upper layer according to the corresponding vehicle data information; the method comprises the steps of carrying out a first treatment on the surface of the

In step S4, the MCU end carries out full detection on signals according to the generated RTE interface which can be called by an upper layer, and the NAD end synchronizes signal information contained in the signal rule table to the MCU end after signal detection according to the signal rule table analyzed in step S2;

in step S5, the MCU end distinguishes the triggering and periodic signals according to the signals synchronized by the NAD end, so as to invoke different functions to perform data packaging, and simultaneously, the MCU automatically sends the triggered related signals to the NAD end, and the NAD end performs abstract processing on the signals packaged by the MCU, and uploads the vehicle data information to the TSP platform according to the formulated vehicle terminal communication protocol.

In one embodiment, the signal rule table in the step S2 includes a signal transmission or reception period, a signal length, and a signal transmission type.

In an embodiment, in the step S3, the CAN layer, the canf layer, the PDUR layer and the COM layer are configured from bottom to top through a ZSAR Studio tool, the configured CAN layer, canf layer, PDUR layer and COM layer are verified, the verified CAN layer, canf layer, PDUR layer and COM layer obtain corresponding vehicle data information through a working mechanism of the ZSAR Studio, and finally an RTE interface capable of being invoked by an upper layer is generated according to the corresponding vehicle data information. MCU uses ZSAR Studio tool to manually configure CAN layer, CANIF layer, PDUR layer and COM layer from bottom to top according to imported DBC file, through verifying configuration project, corresponding.c and.h files are generated for the project after verification according to the working mechanism of ZSAR Studio, and RTE interface capable of being invoked by upper layer is generated according to the corresponding.c and.h files.

In one embodiment, the step S6 includes the steps of:

s51, the MCU compares the signal information sent by the NAD terminal with the signal data information by calling a comparison function, and divides the signal function of the trigger type and the period type according to different RTE interface types. The method aims at defining each byte of the signal according to a communication protocol between MCU and NAD, and writing each defined signal into a corresponding function to form a signal data packet.

In an embodiment, the step S6 further includes the steps of:

In one embodiment, in step S6 the NAD end requests periodic data according to the fastest frequency in the signal contained in the configuration file. The NAD end requests the periodic data according to the fastest frequency, such as 1ms, 5ms, 10ms, 50ms, etc., in the signals contained in the configuration file, because the data uploading frequency is different due to the different periodic signals, and signals with different periods can be sequentially requested and overlapped.

In one embodiment, in the step S5, the NAD end uploads the vehicle data information to the TSP platform through the 4G or 5G network according to the vehicle terminal communication protocol established by the national vehicle communication standard.

The whole logic architecture of the MCU side is realized from bottom to top in a layering way, and one or more ECUs interact with a BSW module in the upper AUTOSAR architecture in an SGW mode.

The DBC file manufactured according to the CAN matrix is imported into ZSAR engineering, the CAN layer, the CANIF layer, the PDUR layer and the COM layer are configured through a Zsar tool, signals contained in the DBC file are mapped one by one, and finally RTE interfaces are generated for an application layer to call.

When the T-BOX logs in, uploading a configuration file to the TSP platform; the DBC file is imported into an Autosar BSW module in the MCU end, because the DBC is a database file of the CAN, the definition of signal information of CAN communication is very complete, the communication of the CAN network is carried out according to the standard file, standard information is provided for signals to be transmitted, and meanwhile, a signal comparison basis is provided for a signal rule table in the step S2;

and the NAD terminal reads various CAN data from the MCU terminal according to a communication protocol between the NAD and the MCU, and then uploads the read data to the TSP platform through a 4G/5G channel.

In the traditional data uploading logic, the whole vehicle data is uploaded every 10S as a period (the period can be changed in the background), and the whole vehicle data is uploaded immediately after the alarm signal support triggers the uploading and the remote control; in this application, whether a single signal is uploaded can be configured, an upload period can be configured by a single signal, a part of signals can trigger uploading, a background configuration can be supported for uploading signal quantity, and the like.

With the development of intelligent internet of vehicles technology, the data volume generated by vehicles is greatly increased, and the data generated by vehicles contains a large amount of environmental information collected by batteries, motors, energy management and various sensors. The large-scale data generated by the vehicles are required to be collected, transmitted, stored and analyzed, and the purpose of the large-scale data is to meet the requirements of vehicle control, performance optimization, safety guarantee and the like;

meanwhile, with the rapid development of new energy automobiles and automatic driving technologies, various new data types are introduced. Such as electric vehicles, require battery status and performance data to be collected in order to optimize battery and charging strategies in real time. An autonomous vehicle needs to collect context awareness data, vehicle state data, and behavior data in order to support decision-making autonomy and travel control. The method can enlarge the acquisition of diversified data to a certain extent;

the application supports data security and privacy protection, and with the increase of the vehicle data information quantity, the data security and privacy protection become more and more important problems. Such as the specific location of the vehicle, driving behavior, vehicle performance, etc. The vehicle data information acquisition system needs to take corresponding security measures to protect confidentiality and integrity of data and prevent data leakage and abuse.

In the traditional mode, the data acquisition always has a delay problem, and for an automatic driving vehicle, the requirement for real-time data is more urgent. Such as vehicles, require real-time acquisition and processing of ambient data acquired by sensors in order to make autonomous decisions and drive control of the surrounding environment. Therefore, the application has the capability of quickly and efficiently collecting data, and the real-time requirement is further enhanced.

With the development of new energy automobiles and automatic driving technologies, the problems that the acquired data quality is uneven, the accuracy cannot meet the requirements and the like can be faced in the data acquisition process. Errors, faults and the like of the sensor can cause inaccuracy or incompleteness of the acquired data, so that the data acquisition accuracy is higher, the time delay is lower and the data acquisition is more reliable.

Based on the original architecture, a set of method capable of configuring vehicle data information is developed based on the architecture, the configuration function is updated based on the traditional uploading and collecting of the vehicle data information, the TSP platform is supported to configure the whole vehicle data to the T-BOX, the method comprises the steps of uploading a data uploading period, whether individual data is uploaded, whether partial data is configured to trigger uploading, and then the T-BOX responds to the TSP platform to configure the whole vehicle data; the support T-BOX sends a data configurable validation report to the TSP platform, the TSP platform responds to the T-BOX data configurable validation report, etc.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.

Therefore, the above description is only a preferred embodiment of the present invention, and the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention should be covered by the scope of the present invention, which is defined by the claims.

Claims

1. A method for configurability of vehicle data acquisition, the method comprising the steps of:

s3, importing the DBC file into an Autosar BSW module at the MCU end, configuring the Autosar BSW module through a ZSAR Studio tool, verifying the configured Autosar BSW module, obtaining corresponding vehicle data information through a working mechanism of the ZSAR Studio by the verified Autosar BSW module, and finally generating an RTE interface capable of being called by an upper layer according to the corresponding vehicle data information;

2. The vehicle data collection configurable method according to claim 1, wherein in said step S2 said signal rule table comprises a signal transmission or reception period, a signal length and a signal transmission type.

3. The method according to claim 2, wherein in the step S3, the Autosar BSW module transmits and receives signals to and from ECUs on different vehicles by SGW.

4. A vehicle data acquisition configurable method according to claim 3, wherein in said step S3 said Autosar BSW module comprises a CAN layer, a CANIF layer, a PDUR layer and a COM layer.

5. The configurable vehicle data acquisition method according to claim 4, wherein in the step S3, the CAN layer, the CANIF layer, the PDUR layer and the COM layer are configured from bottom to top by using a ZSAR Studio tool, the configured CAN layer, the CANIF layer, the PDUR layer and the COM layer are verified, the verified CAN layer, the CANIF layer, the PDUR layer and the COM layer obtain corresponding vehicle data information through a working mechanism of the ZSAR Studio, and finally an RTE interface capable of being invoked by an upper layer is generated according to the corresponding vehicle data information.

6. The method of configurable vehicle data collection according to claim 5, wherein said step S5 comprises the steps of:

7. The vehicle data collection configurable method of claim 6, wherein said step S5 further comprises the steps of:

8. The configurable vehicle data collection method of claim 7, wherein in step S5 the NAD-side requests periodic data based on the fastest frequency in the signal contained in the configuration file.

9. The configurable vehicle data collection method of claim 8, wherein in step S5 the NAD side uploads the vehicle data information to the TSP platform via the 4G or 5G network in accordance with an in-vehicle terminal communication protocol established by the national in-vehicle communication standard.