Vehicle data acquisition method and system

Abstract

The embodiment of the invention provides a vehicle data acquisition method and system, the system comprises a cloud end and a vehicle, the vehicle comprises a micro-processing unit and at least one micro-control unit, and the cloud end issues a data acquisition control instruction to the micro-processing unit. The micro-processing unit obtains a collection script and a filtering script generated by the cloud according to the data collection task from the cloud, analyzes the filtering script, determines at least one target micro-control unit and sends the filtering script to each target micro-control unit, and each target micro-control unit analyzes the filtering script, generates a filtering instruction, obtains corresponding data according to the filtering instruction and sends the corresponding data to the cloud; the target micro-control units are used for acquiring data, the acquired data are sent to the micro-processing unit, and the micro-processing unit analyzes the acquisition script, generates an acquisition instruction, generates target data according to the acquisition instruction and the data sent by the target micro-control units, and sends the target data to the cloud. Therefore, the vehicle can realize comprehensive acquisition of the data of each micro-control unit according to the data acquisition control instruction and the related script.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of data collection, and particularly relates to a vehicle data collection method and system. BACKGROUND

[0002] In an automotive electronic system, a micro control unit (MCU) and a micro processor unit (MPU) are two commonly used processors. The MCU has high integration, simplifies circuit design, has good real-time performance, is suitable for tasks requiring fast response, has low energy consumption and cost, and is suitable for relatively simple control tasks. The MPU has higher processing capability and a more complex instruction set, is suitable for processing complex computing tasks, has strong multitasking capability, supports running of a complex operating system, has larger memory space and more abundant interfaces. The MCU and the MPU will generate a large amount of data in the use process of a vehicle. Currently, when a vehicle needs to be analyzed in terms of function, troubleshooting and the like, the data on the MCU side and the MPU side need to be acquired for subsequent processing.

[0003] At present, the existing data collection technology for the MCU side mainly collects service data on the MPU side to acquire relevant service data of the MCU in the MPU, which mainly depends on deploying a subscription SOA service for the MPU, so that a consumer subscribes to the SOA service on the MPU side, and relevant service data of the MCU and the MPU in data interaction is collected. This method has limitations. On the one hand, for acquisition of SOA service data, a consumer needs to be added for each subscription service, so as to realize subscription and data collection of the corresponding service, leading to complex configuration. On the other hand, only relevant service data of the MCU and the MPU in data interaction can be collected, the service data on the MCU side cannot be comprehensively collected, the acquisition of internal network data of the vehicle is limited, and more or relatively more comprehensive data in the vehicle cannot be acquired.

[0004] Therefore, the existing vehicle data collection method cannot solve the problem of acquiring more or relatively more comprehensive data on the MCU side. SUMMARY

[0005] The embodiment of the present application provides a vehicle data collection method and system, which directly generates data collection control instructions and related scripts based on a data collection task, triggers data collection of each micro control unit, so that the micro processing unit and the micro control unit do not need to be configured, and data collection of each micro control unit can be realized only according to the data collection control instructions and the related scripts, which makes data collection more convenient and efficient on the one hand, and enables more comprehensive data collection of each micro control unit based on the data collection task on the other hand.

[0006] To solve the above technical problems, in a first aspect, the embodiment of the present application provides a vehicle data collection method, which is applied to a vehicle data collection system, the vehicle data collection system comprising a cloud and a vehicle, the vehicle comprising a micro processing unit and at least one micro control unit, the method comprising: the cloud determining a data collection task, generating data collection control instructions and collection scripts according to the data collection task, and generating filtering scripts according to the collection scripts, and sending the data collection control instructions to the micro processing unit; the micro processing unit obtaining the collection scripts and the filtering scripts from the cloud according to the data collection control instructions, analyzing the filtering scripts, determining at least one target micro control unit, and sending the filtering scripts to each target micro control unit; each target micro control unit analyzes the received filtering scripts, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the micro processing unit; the micro processing unit analyzes the collection scripts, generates collection instructions, generates target data according to the collection instructions and the data sent by each target micro control unit, and sends the target data to the cloud.

[0007] By adopting the above technical solution, the cloud determines a data collection task, generates data collection control instructions, collection scripts and filtering scripts, so that the micro processing unit obtains the collection scripts and the filtering scripts from the cloud according to the data collection control instructions, analyzes the filtering scripts, determines the target micro control unit to be collected, sends the filtering scripts to the target micro control unit, each target micro control unit analyzes the received filtering scripts, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the micro processing unit, the micro processing unit analyzes the collection scripts, generates collection instructions, generates target data according to the collection instructions and the data sent by each target micro control unit, and sends the target data to the cloud. In this way, by determining the data collection control instructions, generating the collection scripts and the filtering scripts, each target micro control unit can collect data based on the filtering scripts and send the collected data to the micro processing unit, the micro processing unit can collect data of each target micro processing unit based on the collection scripts and generate target data and send the target data to the cloud, without configuring the micro processing unit and the micro control unit, which makes data collection more convenient and efficient on the one hand, and enables more comprehensive data collection of each micro control unit based on the data collection task, the collection scripts and the filtering scripts on the other hand.

[0008] In a possible implementation of the first aspect, the micro-processing unit comprises a data pool module, the micro-processing unit parses the collection script, generates the collection instruction, and generates the target data according to the collection instruction and the data sent by the micro-control units, and sends the target data to the cloud, comprising: the data pool module parses the collection script, determines the collection type corresponding to the collection script, and generates the collection instruction according to the collection type, wherein the collection type comprises periodic collection and event collection, if the collection type is periodic collection, the collection instruction comprises a collection period, if the collection type is event collection, the collection instruction comprises event information triggering collection; and if the collection type is periodic collection, the data sent by the target micro-control units is processed according to the collection period comprised in the collection instruction, the target data is generated, and the target data is sent to the cloud based on the HTTPS protocol; if the collection type is event collection, the data sent by the target micro-control units is processed according to the event information triggering collection comprised in the collection instruction, the target data is generated, and the target data is sent to the cloud based on the HTTPS protocol.

[0009] By adopting the above technical solution, the data pool module parses the collection script, determines the collection type corresponding to the collection script, generates the collection instruction according to the collection type, processes the data sent by the target micro-control units according to different collection instructions, generates the target data, and sends the target data to the cloud based on the HTTPS protocol. In this way, flexible collection of the data of the target micro-control units can be realized based on different collection types.

[0010] In a possible implementation of the first aspect, processing the data sent by the target micro-control units to generate the target data comprises: processing the data sent by the target micro-control units to generate a target data file, and the target data file comprises the target data.

[0011] By adopting the above technical solution, the data sent by the target micro-control units is processed to generate a target data file. In this way, the data of multiple different micro-control units can be uniformly processed to generate a target data file, which is uploaded to the cloud, and the cloud can conveniently manage and analyze the data of different micro-control units.

[0012] In a possible implementation of the first aspect, the micro-processing unit further comprises a controller module, and the micro-processing unit acquires the collection script and the filtering script from the cloud according to the data collection control instruction, parses the filtering script, determines the target micro-control unit, and sends the filtering script to each target micro-control unit, including: the controller module acquires the collection script and the filtering script from the cloud based on the hypertext transfer protocol secure (HTTPS) according to the data collection control instruction, and sends the collection script and the filtering script to the data pool module based on the cross-process communication protocol; the data pool module parses the filtering script, determines at least one target micro-control unit, and sends the filtering script to each target micro-control unit based on the Ethernet protocol or the user datagram protocol (UDP).

[0013] With the above technical solution, when the controller module receives the data collection control instruction, it indicates that data collection is required, and the collection script and the filtering script are downloaded from the cloud and sent to the data pool module, so that the data pool module parses the filtering script, determines the target micro-control unit, and sends the filtering script to each target micro-control unit based on the Ethernet protocol or the UDP, thereby realizing data collection of multiple target micro-control units.

[0014] In a possible implementation of the first aspect, the controller module acquires the collection script and the filtering script from the cloud based on the HTTPS, and sends the collection script and the filtering script to the data pool module based on the cross-process communication protocol, including: the controller module acquires the collection script and the filtering script from the cloud based on the HTTPS, verifies the collection script and the filtering script, and sends the collection script and the filtering script to the data pool module based on the cross-process communication protocol if the verification is passed.

[0015] With the above technical solution, the controller module verifies the collection script and the filtering script, and sends the collection script and the filtering script to the data pool module based on the cross-process communication protocol if the verification is passed. In this way, the executability of the collection script and the filtering script can be ensured, and useless scripts can be avoided.

[0016] In a possible implementation of the first aspect, the vehicle further comprises at least one electronic control unit, each micro-control unit comprises a filtering task control module and a data filtering module, the target micro-control unit parses the received filtering script, generates a filtering instruction, acquires corresponding data according to the filtering instruction, and sends the acquired data to the micro-processing unit, including: the filtering task control module parses the received filtering script, generates a filtering instruction, and sends the filtering instruction to the data filtering module based on the cross-process communication protocol; and the data filtering module determines a target electronic control unit to be collected from the at least one electronic control unit according to the filtering instruction, acquires data interacting with the target electronic control unit, and sends the data to the data pool module based on the Ethernet protocol or the UDP.

[0017] Using the above technical solution, the filtering task control module parses the filtering script and generates filtering instructions. The data filtering module, based on these instructions, identifies the target electronic control unit (ECU) to be collected from at least one ECU, acquires the data interacting with the target ECU, and sends the data to the data pool module via Ethernet or User Datagram Protocol (UDP). This modular approach eliminates the need for script parsing in the data filtering module, accelerating the execution of filtering instructions. Furthermore, it allows for the determination of the target ECU's interaction data based on the filtering instructions, making data acquisition more flexible. Moreover, pre-filtering the microcontroller data based on the filtering script effectively reduces unnecessary data transmission and storage.

[0018] In one possible implementation of the first aspect described above, the microprocessor unit further includes a vehicle-to-cloud (V2X) interaction module. The method further includes: generating a script task status acquisition instruction in the cloud and sending the script task status acquisition instruction to the V2X interaction module based on a Hypertext Transfer Protocol (HTTP); the V2X interaction module sending the script task status acquisition instruction to a controller module based on the SOME / IP protocol; the controller module generating first script task status information based on the script task status acquisition instruction and sending the script task status acquisition instruction to a data pool module based on a cross-process communication protocol; the data pool module obtaining second script task status information based on the script task status acquisition instruction and sending the second script task status information to the controller module based on the cross-process communication protocol; the controller module sending the first and second script task status information to the V2X interaction module based on the SOME / IP protocol; and the V2X interaction module sending the first and second script task status information to the cloud based on the HTTP protocol.

[0019] By adopting the above technical solution, the cloud can proactively obtain the execution status of the script to obtain the execution status of the data collection task, and can monitor the entire life cycle of the script.

[0020] In one possible implementation of the first aspect above, the method further includes: the controller module sending the first script task status information to the vehicle-cloud interaction module based on a cross-process communication protocol according to a preset time period, and sending the script task status acquisition instruction to the data pool module; the data pool module obtaining the second script task status information according to the script task status acquisition instruction, and sending the second script task status information to the controller module based on the cross-process communication protocol; the controller module sending the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol; and the vehicle-cloud interaction module sending the first script task status information and the second script task status information to the cloud based on the Hypertext Transfer Security Protocol.

[0021] By adopting the above technical solution, the vehicle can proactively report the execution status of the script, so that the cloud can obtain the execution status of the data collection task and realize the monitoring of the entire life cycle of the script.

[0022] In one possible implementation of the first aspect above, the cloud sends data acquisition control commands to the microprocessor unit, including: the cloud sending the data acquisition control commands to the vehicle-cloud interaction module based on the Hypertext Transfer Security Protocol; the vehicle-cloud interaction module sending the data acquisition control commands to the controller module based on the SOME / IP protocol; and the controller module sending the data acquisition control commands to the data pool module based on the inter-process communication protocol.

[0023] By adopting the above technical solution, each module transmits instructions based on different protocols, which makes the communication between modules conform to the characteristics of each module. Transmission based on the adapted protocol can ensure the success rate and security of transmission.

[0024] In one possible implementation of the first aspect mentioned above, the data is object-oriented data, and the data acquisition task is obtained based on the user's data acquisition configuration according to the data acquisition requirements.

[0025] By adopting the above technical solution, data collection tasks are obtained by configuring data collection based on the user's data collection needs, which enables flexible collection of vehicle data and meets the user's vehicle data collection needs.

[0026] Secondly, this application also discloses a vehicle data acquisition system, which includes a cloud and a vehicle. The vehicle includes a microprocessor unit and at least one microcontroller unit. The cloud is used to determine the data acquisition task, generate data acquisition control instructions and an acquisition script based on the data acquisition task, and generate a filtering script based on the acquisition script. The cloud then sends the data acquisition control instructions to the microprocessor unit. The microprocessor unit is used to obtain the acquisition script and the filtering script from the cloud based on the data acquisition control instructions, parse the filtering script, determine at least one target microcontroller unit, and send the filtering script to each target microcontroller unit. Each target microcontroller unit is used to parse the received filtering script, generate filtering instructions, obtain corresponding data based on the filtering instructions, and send the obtained data to the microprocessor unit. The microprocessor unit is used to parse the acquisition script, generate acquisition instructions, generate target data based on the acquisition instructions and the data sent by each target microcontroller unit, and send the target data to the cloud.

[0027] Thirdly, this application also discloses a vehicle for implementing the vehicle data acquisition method provided by any of the implementation methods of the first aspect.

[0028] The relevant beneficial effects of the second and third aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0029] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0030] Figure 1 A schematic diagram of the structure of a vehicle data acquisition system provided in an embodiment of this application;

[0031] Figure 2 This is another schematic diagram of the vehicle data acquisition system provided in the embodiments of this application;

[0032] Figure 3 This is another schematic diagram of the vehicle data acquisition system provided in the embodiments of this application;

[0033] Figure 4 This is a schematic flowchart of a vehicle data acquisition method provided in an embodiment of this application;

[0034] Figure 5 This is a schematic diagram illustrating the principle of a vehicle data acquisition method provided in an embodiment of this application. Detailed Implementation

[0035] As mentioned earlier, MCUs and MPUs are two commonly used processors in automotive electronic systems. MCUs typically have high integration, simplifying circuit design, and offer good real-time performance, making them suitable for tasks requiring fast response. They also have lower power consumption and cost, making them suitable for simpler control tasks. MPUs, on the other hand, usually have higher processing power and more complex instruction sets, making them suitable for handling complex computational tasks. They have strong multitasking capabilities, support complex operating systems such as Linux or Android, can handle multiple tasks simultaneously, have larger memory capacity and richer interfaces, but consume more power than MCUs.

[0036] Both MCUs and MPUs generate a large amount of data during vehicle use. Currently, when performing functional analysis and troubleshooting on vehicles, it is necessary to acquire data from the MCU and MPU for subsequent processing.

[0037] Service-Oriented Architecture (SOA) is a common architectural style in vehicles. It allows different software components to interact over a network to provide flexible and scalable services. In automobiles, SOA services are primarily delivered via the SOME / IP (Scalable Service-Oriented Middleware IP services) protocol. These services are typically described and configured using ARXML files under the AUTOSAR (AUTomotive Open System Architecture) standard.

[0038] In the object-oriented service architecture of vehicles, the MCU and MPU play different roles. The MCU typically acts as a provider of simple services, offering services to consumers, or as a consumer of simple services, subscribing to them. The MPU, on the other hand, acts as a service gateway or manager of complex services, managing these services. In other words, the MCU is better suited for real-time, low-complexity SOA services and SOME / IP communication, typically used for basic vehicle control functions. The MPU, however, is suitable for scenarios requiring high performance and complex service management, such as infotainment and advanced driver assistance systems. The MPU performs better in meeting the flexible configuration and expansion requirements of SOA services, and is better able to support dynamically changing service interactions and vehicle-to-cloud communication.

[0039] Current data acquisition technologies primarily focus on collecting service data from the MPU side. This relies mainly on deploying SOA (Service-Oriented Architecture) services to the MPU, allowing consumers to subscribe to these services and collect service data from the MPU. This service data includes data related to data interaction between the MCU and the MPU. This approach has limitations. Firstly, acquiring SOA service data requires adding a consumer for each subscribed service, leading to complex configuration and preventing full data collection. Secondly, it only collects service data from the MCU side, which communicates with the MPU, hindering the comprehensive collection and monitoring of MCU-side service interaction data and limiting the visualization and analysis of in-vehicle network data.

[0040] Therefore, current data acquisition technologies mainly collect service data from the MPU side by deploying and subscribing to SOA services. This requires adding a consumer for each service that needs to be collected, and it cannot collect all services or all service interaction data from the MCU side.

[0041] Based on this, the data acquisition method and system for the MCU side provided in this application determine the data acquisition task by the cloud, generate data acquisition control instructions and acquisition scripts according to the data acquisition task, and generate filtering scripts according to the acquisition scripts. The data acquisition control instructions are sent to the vehicle's microprocessor unit (MCU). The vehicle's MCU retrieves the acquisition scripts and filtering scripts from the cloud according to the data acquisition control instructions, parses the filtering scripts, identifies at least one target MCU, and sends the filtering scripts to the target MCUs. Each target MCU parses the received filtering scripts, generates filtering instructions, acquires corresponding data according to the filtering instructions, and sends the acquired data to the MCU. The MCU parses the acquisition scripts, generates acquisition instructions, and generates target data according to the acquisition instructions and the data sent by each target MCU, and sends the target data to the cloud. In this way, by generating corresponding acquisition scripts and filtering scripts through data acquisition tasks, comprehensive monitoring and acquisition of data from the vehicle's internal MCU can be achieved. No service consumer configuration is required, making data acquisition simpler and more efficient, and enabling more comprehensive data acquisition from the MCU. Furthermore, based on the collection script and filtering script, the collection range can be flexibly configured, and the data can be uploaded to the cloud through the vehicle-cloud channel, so that the value of the data can be fully explored.

[0042] The following section provides a detailed description of the vehicle data collection method and system provided in this application.

[0043] like Figure 1 As shown, the vehicle data acquisition system provided in this application includes a cloud and a vehicle, the vehicle including a microprocessor unit and at least one microcontroller unit.

[0044] The cloud is used to determine data acquisition tasks, generate data acquisition control instructions and acquisition scripts based on the data acquisition tasks, generate filtering scripts based on the acquisition scripts, and send the data acquisition control instructions to the microprocessor unit.

[0045] For example, the cloud provides a front-end user interface, and the user configures the data collection based on the data collection needs through the front-end user interface to obtain the data collection task.

[0046] The microprocessor unit is used to obtain the acquisition script and filtering script from the cloud according to the data acquisition control command, parse the filtering script, determine at least one target microcontroller unit, and send the filtering script to each target microcontroller unit.

[0047] Each target microcontroller unit is used to parse the received filtering script, generate filtering instructions, obtain corresponding data according to the filtering instructions, and send the obtained data to the microprocessor unit.

[0048] The microprocessor unit is used to parse the acquisition script, generate acquisition instructions, and generate target data based on the acquisition instructions and the data sent by each target microcontroller unit, and then send the target data to the cloud.

[0049] In the implementation of this application, the software architecture of each MCU includes SWC, PDUR, SOME / IP communication protocol, SOAD, and ETHIF.

[0050] Software components (SWCs) are application-layer modules that perform specific functions. They communicate through standardized interfaces defined in the AUTOSAR architecture. SWCs are used to implement specific application logic, such as sensor data processing and vehicle control algorithms.

[0051] A PDU router (PDU Router, or PDUR for short) is a communication service layer module in the AUTOSAR architecture. It is responsible for routing Protocol Data Units (PDUs) between different communication interfaces. The PDUR is used to pass messages between different communication stacks (such as CAN, LIN, and Ethernet), ensuring that the correct modules receive data.

[0052] SOME / IP (Scalable Service-Oriented Middleware over IP) is a middleware protocol for in-vehicle Ethernet communication. It supports service discovery, service provision, and service consumption. SOME / IP is used to implement service-oriented communication within the vehicle's Ethernet network, supporting complex data interaction and functional extensions such as remote updates and diagnostics.

[0053] Socket Adapter (SOAD) is a module in AUTOSAR used for handling IP-based communication. It provides adaptation between the application layer and the transport layer (such as the TCP / IP protocol stack). SOAD is used to manage and adapt the communication interface from higher-level applications (such as SOME / IP) to the transport layer, providing applications with a flexible interface to network sockets.

[0054] The Ethernet Interface (EthIF) is a module in the AUTOSAR architecture, located in the communication stack, responsible for sending and receiving Ethernet data. The EthIF handles the data link layer operations of Ethernet frames, ensuring that data is transmitted and received according to the specified Ethernet protocol.

[0055] In this application, such as Figure 2 As shown, a dynamic data acquisition cloud node is deployed in the cloud, which is used for configuring data acquisition tasks, issuing data acquisition tasks, collecting and storing the acquired data, etc.

[0056] The microprocessor unit deploys a data acquisition master node. There is only one master node, which is used for control command interaction, data uploading, distribution of scripts related to data acquisition tasks, and collection of data from the microcontroller unit side.

[0057] Each microcontroller unit has a corresponding data acquisition slave node. There are multiple slave nodes, corresponding to the number of microcontroller units. These slave nodes are used to filter the service data on the MCU side according to the filtering script and transmit the acquired data to the data acquisition master node.

[0058] In this implementation, the data collected by the MCU is SOA service data.

[0059] Furthermore, such as Figure 3 As shown in the illustration, in the implementation of this application, a microcontroller is used as an example. The vehicle also includes at least one electronic control unit (ECU). The microprocessor unit includes a vehicle-to-cloud interaction module, a controller module, and a data pool module. The microcontroller unit includes a filtering task control module and a data filtering module.

[0060] In the implementation of this application, the vehicle-cloud interaction module is used to receive data acquisition and control commands issued by the cloud and send the data acquisition and control commands to the controller module.

[0061] Specifically, the cloud sends data acquisition control commands to the vehicle-cloud interaction module based on the Hypertext Transfer Protocol, the vehicle-cloud interaction module sends data acquisition control commands to the controller module based on the SOME / IP protocol, and the controller module sends data acquisition control commands to the data pool module based on the cross-process communication protocol.

[0062] The controller module is used to implement the vehicle-to-cloud interaction business during data acquisition, mainly including the synchronization of vehicle-to-cloud script tasks, the synchronization of configuration files (i.e., scripts), and the interaction with control commands in the cloud.

[0063] In other words, the controller module is used to send data acquisition control commands to the data pool module based on an inter-process communication protocol, and download acquisition and filtering scripts from the cloud according to the data acquisition control commands and based on the Hypertext Transfer Protocol, and then send the acquisition and filtering scripts to the data pool module based on the inter-process communication protocol. It is also used to send script task status information to the data pool module based on the inter-process communication protocol when it receives a script task status acquisition command from the cloud, and to send the script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol when it receives script task status information from the data pool module. Furthermore, it is used to send script task status acquisition commands to the data pool module according to a preset time period based on the inter-process communication protocol, and to send script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol when it receives script task status information from the data pool module.

[0064] Furthermore, the controller module, based on the Hypertext Transfer Security Protocol, downloads the acquisition script and filtering script from the cloud and then verifies them. If the verification is successful, the acquisition script and filtering script are sent to the data pool module based on the cross-process communication protocol.

[0065] In this application, Hypertext Transfer Protocol Secure (HTTPS), an HTTP-based encryption protocol, ensures data transmission security by adding SSL / TLS encryption between the transport layer (TCP) and the application layer (HTTP). It provides not only data encryption but also authentication and data integrity verification mechanisms. In this application, the interaction between the vehicle and the cloud is primarily conducted via HTTPS, offering several advantages. Firstly, security is paramount; the self-developed encryption methods (such as SSL / TLS) maximize the security of transmitted data, preventing third-party attacks and data theft. Furthermore, the TCP-based HTTPS protocol ensures reliable data transmission, making it suitable for current scenarios. It also boasts strong compatibility and flexibility, supporting various types of data transmission, including control commands, task status synchronization, and script files.

[0066] The SOME / IP protocol is a communication protocol specifically designed for automotive electronic systems, aiming to provide efficient and reliable real-time communication services. It is based on UDP multicast or unicast communication and incorporates a Quality of Service (QoS) control mechanism. In this application, the vehicle-side controller module actually communicates with the vehicle-cloud interaction module via the SOME / IP protocol, and the vehicle-cloud interaction module then performs communication conversion. By defining SOA services, scalable interface configuration is achieved, facilitating the implementation of vehicle-side software. Furthermore, SOME / IP provides a low-latency message passing mechanism, suitable for in-vehicle communication with high real-time requirements. Its support for dynamic service discovery allows newly accessed services to be quickly identified and integrated. Even though SOME / IP is based on connectionless UDP, it can still implement message acknowledgment and retransmission mechanisms, ensuring reliable transmission of critical information. It also supports multiple message types and service-oriented architectures, facilitating expansion and maintenance.

[0067] X Platform Connectivity (XPC) is a high-efficiency inter-process communication protocol primarily used for communication between different processes on the same computing platform. It allows different processes to share memory space for high-speed data transmission. In this application, most communication between software modules within the same MPU is conducted using the XPC protocol, which improves communication performance. XPC achieves inter-process communication through shared memory, providing extremely low latency and high throughput, and strong real-time performance, making it suitable for real-time applications requiring rapid response, such as control command issuance and status synchronization in vehicle control systems. Furthermore, because it does not require additional network stack overhead, XPC is more lightweight, saving system resources.

[0068] The data pool module parses the filtering script, identifies at least one target microcontroller unit (MCU), and sends the filtering script to each MCU via Ethernet or User Datagram Protocol (UDP). It also parses the acquisition script upon receiving data from each MCU, determines the acquisition type, and generates acquisition instructions based on the acquisition type. Acquisition types include periodic acquisition and event acquisition. For periodic acquisition, the acquisition instruction includes the acquisition period; for event acquisition, it includes the event information that triggered the acquisition. Furthermore, if the acquisition type is periodic, and the acquisition period specified in the acquisition instruction has arrived, the module processes the data from each MCU to generate target data and sends it to the cloud via Hypertext Transfer Protocol (HTTP). If the acquisition type is event acquisition, and the event information specified in the acquisition instruction has been triggered, the module processes the data from each MCU to generate target data and sends it to the cloud via HTTP. It is also used to obtain script task status information based on the script task status acquisition instruction when a script task status acquisition instruction is received, and send the script task status information to the controller module based on the cross-process communication protocol.

[0069] The data pool module receives data from each target microcontroller unit, processes the data accordingly, and generates a target data file, which includes the target data.

[0070] The filtering task control module is used to parse the received filtering script, generate filtering instructions, and send the filtering instructions to the data filtering module based on the cross-process communication protocol.

[0071] The data filtering module is used to determine at least one target electronic control unit to be collected from at least one electronic control unit according to the filtering instructions, obtain the data interacted with each target electronic control unit, and send the data to the data pool module based on the Ethernet protocol or the User Datagram Protocol.

[0072] Ethernet (ETH protocol, also known as the Ethereum protocol) is a MAC address-based local area network (LAN) communication protocol. It boasts flexible bandwidth scalability, easily handling high-throughput data transmission scenarios. For filtering script distribution and batch transmission of filtered service data, Ethernet's high bandwidth avoids data backlog and provides high-speed data transmission capabilities. This application utilizes ETH for packet and script transmission, offering even faster data transfer rates.

[0073] User Datagram Protocol (UDP) is a connectionless transport layer protocol. While it does not guarantee reliable message delivery, it provides fast data transmission capabilities and is typically used in applications requiring high throughput rather than reliability. The parts of this application involving packet and script transmission use UDP. UDP eliminates the overhead of connection establishment and maintenance, thus providing a faster data transmission rate. Furthermore, UDP does not require maintaining connection state, reducing the complexity of the communication process. For the distribution of filtering scripts and the transmission of filtered service data, this "one-off" data transmission is more suitable for UDP because it reduces communication latency. Additionally, scripts and data have their own independent integrity verification methods, so even if some packets are occasionally lost, it will not have a serious impact on the system.

[0074] Furthermore, in the implementation of this application, the microcontroller interacts with the corresponding electronic control units based on SOA services, and data transmission is carried out based on the SOME / IP protocol.

[0075] Furthermore, the vehicle-cloud interaction module is also used to receive script task status acquisition instructions from the cloud and send the script task status acquisition instructions to the controller module.

[0076] For example, the cloud generates a script task status acquisition instruction and sends it to the vehicle-cloud interaction module based on the Hypertext Transfer Protocol. The vehicle-cloud interaction module then sends the script task status acquisition instruction to the controller module based on the SOME / IP protocol. The controller module generates first script task status information based on the script task status acquisition instruction and sends it to the data pool module based on the inter-process communication protocol. The data pool module obtains second script task status information based on the script task status acquisition instruction and sends it to the controller module based on the inter-process communication protocol. The controller module then sends the first and second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol. Finally, the vehicle-cloud interaction module sends the first and second script task status information to the cloud based on the Hypertext Transfer Protocol.

[0077] In another implementation, the vehicle-cloud interaction module is also used to receive script task status information sent by the controller module and send the script task status information to the cloud.

[0078] For example, the controller module sends a script task status acquisition instruction to the data pool module based on a cross-process communication protocol according to a preset time period. The data pool module obtains the script task status information based on the script task status acquisition instruction and sends the script task status information to the controller module based on the cross-process communication protocol. The controller module sends the first script task status information and the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol. The vehicle-cloud interaction module sends the script task status information to the cloud based on the Hypertext Transfer Security Protocol.

[0079] In other words, in this application, the cloud (data acquisition cloud) and the MPU's vehicle-cloud interaction module use HTTPS protocol for control command interaction and script task status synchronization; the cloud and the MPU's controller module use HTTPS protocol for downloading acquisition scripts and filtering scripts; the cloud and the MPU's data pool module use HTTPS protocol for uploading acquired service data; the MPU's vehicle-cloud interaction module and the controller module use SOME / IP protocol for control command interaction and script task status synchronization; the controller module and the data pool module use XPC protocol for control command distribution, script task status synchronization, acquisition script and filtering script distribution; the data pool module and the MCU's filtering task control module use ETH / UDP for filtering script distribution; the MCU's filtering task control module and the MCU's data filtering module use XPC for filtering command distribution; and the MCU's data filtering module and the MPU's data pool module use ETH / UDP for transmitting filtered service data.

[0080] HTTPS offers the highest level of security, suitable for scenarios involving sensitive information or remote operation, while UDP and SOME / IP typically do not provide encryption. HTTPS and XPC provide reliable data transmission mechanisms, suitable for applications requiring data integrity, while UDP itself does not guarantee reliable message transmission, but reliability can be achieved through the application layer in specific scenarios. SOME / IP and UDP are well-suited for real-time applications due to their low latency and high transmission rates, while HTTPS and XPC can also be used for real-time applications, but their design prioritizes versatility and security. XPC performs best in terms of resource consumption because it directly utilizes the shared memory mechanism provided by the operating system; HTTPS, due to its encryption and decryption processes, typically consumes more CPU resources.

[0081] In this implementation, the vehicle-cloud interaction module is responsible for converting the communication protocols used for interaction between the vehicle and the cloud, enabling the mutual conversion between SOME / IP and HTTPS interaction messages. The controller module is responsible for the business implementation of the vehicle-cloud interaction part in SOA data acquisition, mainly including the synchronization of vehicle-cloud tasks, the synchronization of configuration files (scripts), and the interaction of control commands with the cloud. The data pool module is responsible for parsing the data acquisition task script, distributing the filter script configuration file, collecting SOA service data filtered by each MCU, packaging the data according to the acquisition script, compressing the acquired data file, and uploading it to the cloud. The filter task control module receives the filter script distributed by the Master node, parses it into filter commands, and the service data filter module receives the filter commands, monitors the SOA service interaction between the MCU and other ECUs, collects the corresponding service data according to the filter commands, and transmits the data to the data pool module.

[0082] It should be noted that the modules included in the MPU and MCU in this application are software modules implemented based on code.

[0083] like Figure 4 As shown, based on the vehicle data acquisition system provided in this application, the vehicle data acquisition method of this application includes the following steps.

[0084] The S100 determines the data acquisition task in the cloud, generates data acquisition control instructions and acquisition scripts based on the data acquisition task, generates a filtering script based on the acquisition scripts, and sends the data acquisition control instructions to the microprocessor unit.

[0085] S200: The microprocessor unit obtains the acquisition script and filtering script from the cloud according to the data acquisition control command, parses the filtering script, determines the target microcontroller unit, and sends the filtering script to the target microcontroller unit.

[0086] S300: Each target microcontroller unit parses the received filtering script, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the microprocessor unit.

[0087] The S400 microprocessor unit parses the acquisition script, generates acquisition instructions, and generates target data based on the acquisition instructions and the data sent by each target microcontroller unit, and then sends the target data to the cloud.

[0088] In the implementation of this application, the data is object-oriented service data, that is, SOA interaction data between the microcontroller and its corresponding electronic control units.

[0089] Furthermore, the data acquisition task is obtained by the user through data acquisition configuration based on their data acquisition needs.

[0090] For example, users configure data acquisition based on their data acquisition needs through a cloud-provided front-end user interface to generate data acquisition tasks. For instance, users can configure SOA data acquisition tasks by accessing the front-end interface of the data acquisition cloud, selecting the SOA services to be acquired, the acquisition method, the acquisition period, the event information that triggers the acquisition, the DataID list, and the target electronic control unit to be acquired, among other information. In this application, DataIDs are used to distinguish specific services, instances, and the input / output direction of interface parameters.

[0091] The cloud-based system generates data acquisition control commands based on the data acquisition task and sends these commands to the vehicle's microprocessor unit. Furthermore, it generates an acquisition script based on the data acquisition task. This acquisition script includes information such as the script file version number, target ECU, acquisition type, and a list of DataIDs.

[0092] In the implementation method of this application, the collection type includes two types: MCU service data periodic collection and MCU service data event collection. The sampling period, upload period, and collection range can be flexibly adjusted based on the user's data collection needs. If the collection type is periodic collection, the collection script is shown in Table 1. If the collection type is event collection, the collection script is shown in Table 2.

[0093] Table 1. Acquisition scripts for periodic acquisition types.

[0094] Field name Type Content Version number String Version number of the script file Target MPU Integer Indicates the MPU that executes this configuration file Acquisition type Integer MCU SOME / IP periodic acquisition Data ID list List Contains all service data flags that need to be acquired in this script

[0095] Table 2. Event Collection Scripts for Event Collection Types

[0096] Field name Type Content Version number String Version number of the script file Target MPU Integer Indicates the MPU that executes this configuration file Acquisition type Integer Event acquisition Event list List List of events used to trigger acquisition Data ID list List List of service data flags acquired after triggering

[0097] As shown in Table 1, the acquisition script includes a version number, which is a string and contains the version number of the acquisition script file; the target MPU is an integer and contains the MPU that executes this configuration file (i.e., the acquisition script); the acquisition type is an integer and contains the periodic acquisition of data from the MCU based on the SOME / IP protocol; the DataID list is a list and contains all the service data flags that need to be acquired in this acquisition script.

[0098] As shown in Table 2, the collection script includes a version number, which is a string and contains the version number of the collection script file; the target MPU is an integer and contains the MPU that executes this configuration file (i.e., the collection script); the collection type is an integer and contains the event collection; the event list is a list and contains the list of events used to trigger the collection; and the DataID list is a list and contains all the service data flags that need to be collected in this collection script.

[0099] It should be noted that MPU and MCU can also be two units of the same ECU. That is, the target MPU in the acquisition script can also be the target ECU, which represents the ECU used to execute the configuration file of this acquisition script.

[0100] Furthermore, a filtering script is generated based on the acquisition script. For example, after summarizing and deduplicating the DataIDs in the DataID list, the deduplicated DataIDs, the target MCU, and the acquisition type are filled into the initial filtering script to obtain the filtering script. In the implementation of this application, as shown in Table 3, the filtering script includes the version number, the target ECU, the acquisition type, and the DataID list.

[0101] Table 3 Filtering Scripts

[0102] Field name Type Content Version number String Version number of the script file Target ECU uint8 Acquisition type Integer SOA service data filtering Data ID list uint16 All Data IDs filtered by SOA

[0103] As shown in Table 3, the version number is of type String and contains the version number of the filtering script file. The target ECU is of type uint8 and contains the identification information of the target ECU. When the content is empty, the interaction data of all ECUs is collected based on the DataID list. The collection type is integer and contains the filtering of SOA service data. The DataID list is of type uint16 and contains all the DataIDs filtered by SOA.

[0104] It should be noted that the target ECU is at least one of multiple electronic control units that interact with the MCU. The SOA data of the target ECU interacting with the MCU is filtered based on the DataID list in order to transmit the filtered data to the MPU.

[0105] It should be noted that the DataIDs in the DataID list can be either DataIDs that need to be collected or DataIDs that do not need to be collected.

[0106] In this implementation, the cloud sends data acquisition control commands to the microprocessor unit, including: the cloud sending the data acquisition control commands to the vehicle-cloud interaction module based on the Hypertext Transfer Security Protocol; the vehicle-cloud interaction module sending the data acquisition control commands to the controller module based on the SOME / IP protocol; and the controller module sending the data acquisition control commands to the data pool module based on the cross-process communication protocol.

[0107] For example, the data acquisition control command carries the vehicle identification information of the vehicle to be acquired, and the cloud sends the data acquisition control command to the vehicle-to-cloud interaction module of the vehicle to be acquired based on the Hypertext Transfer Security Protocol.

[0108] Furthermore, the microprocessor unit obtains the acquisition script and filtering script from the cloud according to the data acquisition control command, parses the filtering script, determines the target microcontroller unit, and sends the filtering script to the target microcontroller unit.

[0109] For example, the controller module downloads the acquisition script and filtering script from the cloud based on the Hypertext Transfer Protocol according to the data acquisition control command, and sends the acquisition script and filtering script to the data pool module based on the cross-process communication protocol.

[0110] In this implementation, the controller module downloads the collection script and filtering script from the cloud based on the Hypertext Transfer Protocol, and sends the collection script and filtering script to the data pool module based on the inter-process communication protocol. The implementation includes: the controller module downloads the collection script and filtering script from the cloud based on the Hypertext Transfer Protocol, verifies the collection script and filtering script, and if the verification is successful, sends the collection script and filtering script to the data pool module based on the inter-process communication protocol.

[0111] For example, after the acquisition script and the filtering script are successfully downloaded, the controller module will perform a preliminary verification of the script content to verify the validity and completeness of each script. If the verification is successful, the parsed script will be transmitted to the data pool module.

[0112] Furthermore, the data pool module parses the filtering script, determines the target microcontroller unit, and sends the filtering script to each target microcontroller unit based on Ethernet protocol or User Datagram Protocol.

[0113] For example, the data pool module parses the target ECU in the filtering script, determines the target microcontroller unit that needs to be acquired based on the correspondence table between ECU and MCU, and transmits the filtering script to each target microcontroller unit based on Ethernet protocol or User Datagram Protocol.

[0114] Furthermore, each target microcontroller unit parses the received filtering script, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the microprocessor unit.

[0115] In this implementation, each target microcontroller parses the received filtering script, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the microprocessor unit. This includes: the filtering task control module parses the received filtering script, generates filtering instructions, sends the filtering instructions to the data filtering module based on the cross-process communication protocol, the data filtering module determines the target electronic control unit to be collected from at least one electronic control unit according to the filtering instructions, obtains the data interacting with the target electronic control unit, and sends the data to the data pool module based on the Ethernet protocol or the User Datagram Protocol.

[0116] For example, when the filtering task control module receives the filtering script, it immediately parses the script content, converts the filtering script into specific filtering instructions, and sends the filtering instructions to the data filtering module. The data filtering module identifies the services, instances and interfaces that need to be collected based on the DataID included in the filtering instructions, filters out the SOME / IP message data of the MCU interacting with other ECUs, and continuously transmits the filtered data to the MPU's data pool module in the form of ETH / UDP messages according to the set frequency.

[0117] Furthermore, this application can also transmit the collected event information in the form of ETH / UDP packets to the MPU's data pool module when the event is triggered, based on the pre-defined trigger event information.

[0118] In this implementation, multiple different MCUs execute unified filtering logic based on the same filtering script. This design simplifies script management and distribution, while ensuring the consistency of data acquisition. Furthermore, the data from each MCU is transmitted to the MPU's data pool module, which processes the data uniformly. This approach effectively avoids the increased complexity caused by the increase in the amount of MCU data, ensuring the efficiency and integrity of data transmission.

[0119] In this application, the data collected by the data filtering module is SOA interaction data of the MCU interacting with other target electronic control units.

[0120] In the implementation method of this application, data is pre-screened by filtering script, which can effectively reduce unnecessary data transmission and storage, reduce the computing and storage resource consumption of the MCU, and only the required data needs to be collected. This avoids data redundancy and ensures the efficient acquisition of key data. This method is particularly suitable for resource-constrained embedded devices (such as MCUs) and helps to improve operating efficiency.

[0121] Furthermore, multiple MCUs can share the same filtering script and perform data collection and filtering according to unified filtering rules, ensuring the consistency and accuracy of cross-module data collection. It also supports the centralized transmission of filtering results from multiple MCUs to the same main processing unit (MPU), thereby realizing unified data processing and analysis and improving the overall collaborative efficiency of the entire system.

[0122] In the implementation of this application, the data pool module parses the acquisition script, generates acquisition instructions, and generates target data based on the acquisition instructions and the data sent by each microcontroller unit, and sends the target data to the cloud. This includes: the data pool module parses the acquisition script, determines the acquisition type corresponding to the acquisition script, and generates acquisition instructions based on the acquisition type.

[0123] The acquisition types include periodic acquisition and event acquisition. If the acquisition type is periodic acquisition, the acquisition instruction includes the acquisition period. If the acquisition type is event acquisition, the acquisition instruction includes the event information that triggered the acquisition.

[0124] If the acquisition type is periodic acquisition, then when it is determined that the acquisition period included in the acquisition command has been reached, the data sent by each microcontroller unit is processed accordingly to generate target data, and the target data is sent to the cloud based on the Hypertext Transfer Security Protocol.

[0125] For example, the data pool module collects, packages, and compresses the SOA service data received from different target MCUs according to the sampling period and other information included in the collection script to generate target data files, and uploads the compressed target data files to the cloud via the HTTPS protocol when the collection period has expired.

[0126] If the acquisition type is event acquisition, then when the event information that triggers the acquisition is determined to be included in the acquisition instruction, the data sent by each microcontroller unit is processed accordingly to generate target data, and the target data is sent to the cloud based on the Hypertext Transfer Security Protocol.

[0127] For example, the data pool module collects, packages, and compresses the SOA service data received from different target MCUs according to the information such as the event information that triggers the collection included in the collection script, and generates a target data file. When the event is triggered, the compressed target data file is uploaded to the cloud via the HTTPS protocol.

[0128] That is, in the implementation of this application, the data sent by each microcontroller unit is processed accordingly to generate target data, including: processing the data sent by each microcontroller unit to generate a target data file, wherein the target data file includes target data.

[0129] Furthermore, in the implementation of this application, the method further includes: generating a script task status acquisition instruction in the cloud, sending the script task status acquisition instruction to the vehicle-cloud interaction module based on the Hypertext Transfer Security Protocol, the vehicle-cloud interaction module sending the script task status acquisition instruction to the controller module based on the SOME / IP protocol, the controller module generating first script task status information according to the script task status acquisition instruction, and sending the script task status acquisition instruction to the data pool module based on the cross-process communication protocol.

[0130] The data pool module obtains the second script task status information based on the script task status acquisition instruction, and sends the second script task status information to the controller module based on the cross-process communication protocol. The controller module sends the first script task status information and the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol. The vehicle-cloud interaction module sends the first script task status information and the second script task status information to the cloud based on the Hypertext Transfer Security Protocol.

[0131] For example, each script has its own task status after generation and distribution. As part of script lifecycle management, the vehicle-side software determines different processing methods based on the script's task status, such as loading, executing, pausing, or deleting the script. The cloud can proactively query the task status of the vehicle-side scripts. If there are any gaps in the vehicle-side tasks, the cloud will push download instructions for the collection script or filtering script. After receiving the instructions, the vehicle-side software will provide feedback on the script download status to ensure that the cloud can accurately understand the execution progress of the collection task.

[0132] For example, the cloud proactively sends a script task status retrieval command. When the controller module receives this command, if it determines that the corresponding acquisition script and filtering script have been downloaded, it generates a first script task status information indicating that the script has been downloaded and sends it to the vehicle-cloud interaction module. If it also determines that the acquisition script and filtering script have been sent to the data pool module, it sends the script task status retrieval command to the data pool module. Based on this command, the data pool module determines whether the filtering script has been downloaded or not, and generates a second script task status information indicating that the script has not been executed. This second script task status information is then sent to the control module, which in turn sends it to the vehicle-cloud interaction module. Furthermore, if the controller module determines that the acquisition script and filtering script have not been sent to the data pool module, it does not need to send a script task status retrieval command to the data pool module; it directly generates the second script task status information indicating that the script has not been executed.

[0133] The vehicle-cloud interaction module sends the received status information of the first and second script tasks to the cloud.

[0134] Furthermore, in the implementation of this application, the method further includes: the controller module sending a script task status acquisition instruction to the data pool module based on a preset time period and an inter-process communication protocol; the data pool module obtaining second script task status information based on the script task status acquisition instruction and sending the script task status information to the controller module based on the inter-process communication protocol; the controller module sending the first script task status information and the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol; and the vehicle-cloud interaction module sending the first script task status information and the second script task status information to the cloud based on the Hypertext Transfer Security Protocol.

[0135] For example, the controller module periodically collects the task status of all scripts and reports it to the cloud at predetermined time intervals.

[0136] For example, the controller module determines the script task status information of the acquisition script and the filtering script based on a preset time period. If it determines that the corresponding acquisition script and filtering script have been downloaded, it generates a first script task status information indicating that the script has been downloaded and sends it to the vehicle-cloud interaction module. If it determines that the acquisition script and filtering script have been sent to the data pool module, it sends a script task status retrieval command to the data pool module. Based on the script task status retrieval command, the data pool module, if it determines that the filtering script has been distributed, generates a second script task status information indicating that the script has been executed; if it determines that the filtering script has not been distributed, it generates a second script task status information indicating that the script has not been executed and sends this second script task status information to the control module. The controller module then sends this second script task status information to the vehicle-cloud interaction module. Furthermore, if the controller module determines that the acquisition script and filtering script have not been sent to the data pool module, it does not need to send a script task status retrieval command to the data pool module and directly generates the second script task status information indicating that the script has not been executed.

[0137] In this way, managing the script lifecycle allows for real-time monitoring of the status of data collection task scripts, covering the entire lifecycle from generation and distribution to execution completion. This mechanism enables the cloud to adjust collection strategies promptly, such as automatically pushing new scripts when tasks are not available, ensuring the continuity and stability of data collection.

[0138] The vehicle-cloud interaction module sends the received status information of the first and second script tasks to the cloud.

[0139] In the implementation of this application, when the cloud actively sends information to the vehicle, it needs to go through the vehicle-cloud interaction module in order to better determine the target vehicle to which the instruction needs to be sent. When the vehicle actively sends information to the cloud, such as downloading a script or uploading a target data file, since there is only one cloud, it is easier to locate and can bypass the vehicle-cloud interaction module, thereby improving the transmission rate.

[0140] In this implementation, data acquisition on the MCU side is mainly divided into vehicle-cloud control interaction, vehicle-side data transmission, and data upload. SOA service data to be collected is transmitted to the vehicle side via acquisition scripts and filtering scripts. Figure 5 As shown, the process of vehicle data collection based on acquisition scripts and filtering scripts in this application is as follows: The user configures data collection based on the cloud-based data acquisition front-end user interface, generates a data acquisition task, the cloud generates data acquisition control instructions and acquisition scripts according to the data acquisition task, and generates filtering scripts according to the acquisition scripts. The data acquisition control instructions are sent to the controller module of the MPU. The controller module downloads the acquisition scripts and filtering scripts from the cloud and distributes them to the data pool module of the MPU. The data pool module distributes the filtering scripts to the filtering task control module of the MCU. The filtering task control module parses the filtering scripts, generates filtering instructions, and sends the filtering instructions to the service data filtering module of the MCU. The service data filtering module obtains the corresponding data according to the filtering instructions and transmits the collected data to the data pool module. The data pool module parses the acquisition scripts, generates acquisition instructions, processes the received data according to the acquisition instructions to obtain the target data, and uploads the target data to the cloud.

[0141] It should be noted that the data pool module can parse the acquisition script synchronously with the sending filter script, or it can parse the acquisition script after receiving the data sent by each target microcontroller unit.

[0142] The vehicle data acquisition method provided in this application is a dynamic acquisition method for service data in a service-oriented architecture (SOA) on the MCU side. Users dynamically configure data acquisition tasks via a cloud interface, enabling the cloud to update acquisition and filtering scripts in real time based on the user-configured tasks, dynamically adjusting data acquisition targets and strategies. Through script distribution and parsing, the MCU can flexibly configure the services, instances, interfaces, and sampling frequencies to be acquired according to different acquisition needs. Data acquisition for all SOA services can be achieved without adding a separate consumer for each service, simplifying system configuration complexity, avoiding the inconvenience of hard-coding, significantly improving the MCU's functional adaptability and upgrade efficiency, and reducing maintenance difficulty. Furthermore, through effective data acquisition management strategies, excessive resource consumption on the MCU side is avoided, ensuring the vehicle system operates efficiently while maintaining low power consumption. The decoupling of script distribution, parsing, and execution from specific business logic is achieved, modularizing the data acquisition function. Different tasks only require different scripts to be distributed, without modifying the underlying MCU acquisition logic, thus achieving high system scalability and facilitating rapid iteration and functional expansion. Moreover, real-time distribution of new script configuration files improves the vehicle system's response speed and adaptability.

[0143] Furthermore, the use of filtering scripts to accurately identify and extract target data ensures high-quality uploaded data. Data undergoes preliminary screening and optimization before being transmitted to the MPU, reducing bandwidth consumption and network load. Simultaneously, different communication protocols are used in different transmission scenarios to match the varying needs of the same data acquisition system. This approach is particularly suitable for multi-node collaborative scenarios in vehicular networks, effectively improving data transmission efficiency.

[0144] The vehicle data collection method provided in this application can be applied to fields such as vehicle operation status monitoring, remote diagnostics, and vehicle data analysis. Through precise collection and flexible adjustment, it can meet the diverse data collection needs of different scenarios, providing a solid data foundation for vehicle-cloud interaction and subsequent intelligent services.

[0145] In this application, if the controller module fails to download the script, it can retry multiple times. If data acquisition fails, the data acquisition task is re-executed. Furthermore, communication between the cloud and the vehicle requires successful authentication, and the transmitted script and uploaded target data file are encrypted to ensure data security. Thus, by uploading data via HTTPS and configuring security mechanisms at the script distribution and transmission levels, encryption and authentication mechanisms for data communication are added, ensuring the security and integrity of data transmission and preventing potential security threats. In addition, combined with the retransmission mechanism, the system can automatically retry incomplete upload tasks in case of network anomalies or failures, significantly improving the reliability of data acquisition. The vehicle data acquisition system of this application is compatible with existing vehicle systems, ensuring seamless integration of the vehicle data acquisition method into current in-vehicle electronic architecture, reducing implementation time and cost.

[0146] In this implementation, the MPU can also collect its own SOA service data based on the collection script, and upload its own data and the data received from each MCU to the cloud based on the collection script.

[0147] The vehicle data acquisition method provided in this application is applied to a vehicle, which includes a vehicle data acquisition system for executing the vehicle data acquisition method provided in the above implementation.

[0148] This application also provides a chip for executing instructions, which is used to execute the vehicle data acquisition method described in the above embodiments.

[0149] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a vehicle's processor, cause the vehicle's processor to perform the vehicle data acquisition method described in the above embodiments.

[0150] In some possible implementations, various aspects of the methods provided in this application can also be implemented as a program product, which includes program code. When the program product is run on the processor of a vehicle, the program code is used to cause the processor of the vehicle to perform the steps of the methods according to the various exemplary implementations of this application described above. For example, the vehicle can perform the vehicle data acquisition method described in the embodiments of this application.

[0151] The program product may take the form of any combination of one or more readable media. A readable medium may be a readable data medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CDROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0152] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the vehicle data acquisition method in the above embodiments.

[0153] It should be noted that, in addition to the specific embodiments described above, those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Although the description of this application is presented in conjunction with preferred embodiments, this does not mean that the features of this application are limited to this implementation. On the contrary, the purpose of describing the application in conjunction with the implementation is to cover other options or modifications that may be derived from this application. To provide a thorough understanding of this application, many specific details are included in the above description, and this application may also be implemented without using these details. Furthermore, to avoid confusion or obscuring the focus of this application, some specific details will be omitted in the description. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0154] It should be noted that in this specification, similar reference numerals and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0155] It should be noted that the terms "first" and "second" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0156] It should be noted that some structural or methodological features may be shown in the accompanying drawings in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, including structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0157] Although this application has been illustrated and described with reference to certain preferred embodiments, those skilled in the art should understand that the above description is a further detailed explanation of the application in conjunction with specific implementations, and should not be construed as limiting the specific implementation of the application to these descriptions. Those skilled in the art can make various changes in form and detail, including some simple deductions or substitutions, without departing from the spirit and scope of this application.

Claims

1. A method for collecting vehicle data, characterized in that, The method is applied to a vehicle data acquisition system, the vehicle data acquisition system including a cloud and a vehicle, the vehicle including a microprocessor unit and at least one microcontroller unit, the method comprising: The cloud determines the data acquisition task, generates data acquisition control instructions and acquisition scripts according to the data acquisition task, generates a filtering script according to the acquisition scripts, and sends the data acquisition control instructions to the microprocessor unit. The microprocessor unit obtains the acquisition script and the filtering script from the cloud according to the data acquisition control command, parses the filtering script, determines at least one target microcontroller unit, and sends the filtering script to each of the target microcontroller units. Each of the target microcontroller units parses the received filtering script, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the microprocessor unit; The microprocessor unit parses the acquisition script, generates acquisition instructions, and generates target data based on the acquisition instructions and the data sent by each of the target microcontroller units, and sends the target data to the cloud.

2. The vehicle data acquisition method according to claim 1, characterized in that, The microprocessor unit includes a data pool module. The microprocessor unit parses the acquisition script, generates acquisition instructions, and generates target data based on the acquisition instructions and the data sent from each of the target microcontroller units. The target data is then sent to the cloud, including: The data pool module parses the acquisition script, determines the acquisition type corresponding to the acquisition script, and generates acquisition instructions based on the acquisition type. The acquisition type includes periodic acquisition and event acquisition. If the acquisition type is periodic acquisition, the acquisition instructions include the acquisition period; if the acquisition type is event acquisition, the acquisition instructions include the event information that triggered the acquisition. If the acquisition type is the periodic acquisition, then when it is determined that the acquisition period included in the acquisition instruction has been reached, the data sent by each of the target microcontroller units is processed accordingly to generate target data, and the target data is sent to the cloud based on the Hypertext Transfer Security Protocol. If the acquisition type is event acquisition, then when it is determined that the event information for triggering acquisition included in the acquisition instruction is triggered, the data sent by each of the target microcontroller units is processed accordingly to generate target data, and the target data is sent to the cloud based on the hypertext transfer security protocol.

3. The vehicle data acquisition method according to claim 2, characterized in that, The data sent from each of the target microcontroller units is processed accordingly to generate target data, including: The data sent from each of the target microcontroller units is processed accordingly to generate a target data file, which includes the target data.

4. The vehicle data acquisition method according to claim 3, characterized in that, The microprocessor unit further includes a controller module. The microprocessor unit retrieves the acquisition script and filtering script from the cloud according to the data acquisition control command, parses the filtering script, identifies at least one target microcontroller unit, and sends the filtering script to each of the target microcontroller units, including: According to the data acquisition control command, the controller module downloads the acquisition script and the filtering script from the cloud based on the Hypertext Transfer Security Protocol, and sends the acquisition script and the filtering script to the data pool module based on the cross-process communication protocol. The data pool module parses the filtering script, identifies at least one target microcontroller unit, and sends the filtering script to each target microcontroller unit based on Ethernet protocol or User Datagram Protocol.

5. The vehicle data acquisition method according to claim 4, characterized in that, The controller module, based on the Hypertext Transfer Protocol Secure (HTTP), downloads the acquisition script and the filtering script from the cloud, and sends the acquisition script and the filtering script to the data pool module based on an inter-process communication protocol, including: The controller module downloads the acquisition script and the filtering script from the cloud based on the Hypertext Transfer Security Protocol, verifies the acquisition script and the filtering script, and if the verification is successful, sends the acquisition script and the filtering script to the data pool module based on the cross-process communication protocol.

6. The vehicle data acquisition method according to claim 5, characterized in that, The vehicle further includes at least one electronic control unit, each of the microcontrollers including a filtering task control module and a data filtering module. The target microcontroller parses the received filtering script, generates filtering instructions, obtains corresponding data according to the filtering instructions, and sends the obtained data to the microprocessor unit, including: The filtering task control module parses the received filtering script, generates filtering instructions, and sends the filtering instructions to the data filtering module based on the cross-process communication protocol. The data filtering module determines the target electronic control unit to be collected from the at least one electronic control unit according to the filtering instruction, obtains the data interacting with the target electronic control unit, and sends the data to the data pool module based on Ethernet protocol or User Datagram Protocol.

7. The vehicle data acquisition method according to claim 6, characterized in that, The microprocessor unit also includes a vehicle-to-cloud interaction module. The method further includes: The cloud-generated script task status acquisition instruction is sent to the vehicle-cloud interaction module based on the Hypertext Transfer Security Protocol. The vehicle-cloud interaction module, based on the SOME / IP protocol, sends the script task status acquisition command to the controller module; The controller module generates first script task status information based on the script task status acquisition instruction, and sends the script task status acquisition instruction to the data pool module based on the cross-process communication protocol. The data pool module obtains the second script task status information according to the script task status acquisition instruction, and sends the second script task status information to the controller module based on the cross-process communication protocol. The controller module sends the first script task status information and the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol; The vehicle-to-cloud interaction module, based on the Hypertext Transfer Protocol, sends the first script task status information and the second script task status information to the cloud; or The method further includes: The controller module sends the script task status acquisition instruction to the data pool module according to the cross-process communication protocol based on a preset time period; The data pool module obtains the second script task status information according to the script task status acquisition instruction, and sends the second script task status information to the controller module based on the cross-process communication protocol. The controller module sends the first script task status information and the second script task status information to the vehicle-cloud interaction module based on the SOME / IP protocol; The vehicle-cloud interaction module sends the first script task status information and the second script task status information to the cloud based on the Hypertext Transfer Security Protocol.

8. The vehicle data acquisition method according to claim 7, characterized in that, The cloud sends the data acquisition control command to the microprocessor unit, including: The cloud platform sends the data acquisition control commands to the vehicle-cloud interaction module based on the Hypertext Transfer Security Protocol. The vehicle-cloud interaction module, based on the SOME / IP protocol, sends the data acquisition control commands to the controller module. The controller module sends the data acquisition control command to the data pool module based on the cross-process communication protocol.

9. The vehicle data acquisition method according to claim 8, characterized in that, The data is object-oriented service data, and the data collection task is obtained based on the user's data collection configuration according to the data collection requirements.

10. A vehicle data acquisition system, characterized in that, The vehicle data acquisition system includes a cloud platform and a vehicle, wherein the vehicle includes a microprocessor unit and at least one microcontroller unit. The cloud is used to determine data acquisition tasks, generate data acquisition control instructions and acquisition scripts according to the data acquisition tasks, generate filtering scripts according to the acquisition scripts, and send the data acquisition control instructions to the microprocessor unit. The microprocessor unit is used to obtain the acquisition script and the filtering script from the cloud according to the data acquisition control command, parse the filtering script, determine at least one target microcontroller unit, and send the filtering script to each of the target microcontroller units. Each of the target microcontroller units is used to parse the received filtering script, generate filtering instructions, obtain corresponding data according to the filtering instructions, and send the obtained data to the microprocessor unit; The microprocessor unit is used to parse the acquisition script, generate acquisition instructions, generate target data according to the acquisition instructions and the data sent by each of the target microcontroller units, and send the target data to the cloud.

Images