A vehicle data acquisition system, method and medium

Abstract

The application discloses a vehicle data collection system, method and medium. The system comprises a client configured to send a data collection request to a server; the server is configured to determine a target configuration file according to the data collection request and a pre-stored information structure tree, generate a target task according to the target configuration file, and send the target task to a vehicle terminal of at least one target vehicle; the information structure tree is determined according to vehicle functions and vehicle data; and the vehicle terminal is configured to determine target data according to the target task, and send the target data to the client through the server. The application can realize differentiated collection of demand data, and the effectiveness, comprehensiveness, timeliness and flexibility of data collection.

Description

Technical Field

[0001] This invention relates to the field of vehicle data acquisition technology, and in particular to a vehicle data acquisition system, method and medium. Background Technology

[0002] With the rapid development of the automotive industry and electronic technology, vehicle functions are becoming increasingly richer and user experience is continuously improving. However, this also makes the electronic architecture of automobiles increasingly complex. The dramatic increase in vehicle data and the complexity of the network environment have significantly increased the probability of vehicle malfunctions. The efficiency of vehicle problem diagnosis is strongly correlated with the acquisition of effective data before and after a problem occurs. Therefore, improving the effectiveness, timeliness, and flexibility of vehicle data acquisition is crucial for efficient vehicle problem diagnosis.

[0003] The relevant technologies mainly acquire vehicle data through data tracking, but this method requires determining the tracking data in advance before vehicle production, making it difficult to control the data range and resulting in missing valid data for troubleshooting. If changes to the tracking data are needed, the software needs to be updated and a series of processes need to be completed to release the software and display it on the vehicle, which is time-consuming and has poor timeliness. When the tracking function is running, it continuously uploads all tracking data, and the upload requirements cannot be flexibly configured, resulting in a large amount of uploaded data, excessive resource consumption, and low data validity. All of these factors greatly affect the efficiency of vehicle problem troubleshooting. Summary of the Invention

[0004] This invention provides a vehicle data acquisition system, method, and medium that can achieve differentiated acquisition of required data and ensure the effectiveness, comprehensiveness, timeliness, and flexibility of data acquisition.

[0005] According to one aspect of the present invention, a vehicle data acquisition system is provided, the system comprising a client, a server, and a vehicle terminal; wherein:

[0006] The server is connected to the client and the vehicle terminal respectively;

[0007] The client is used to send a data collection request to the server.

[0008] The server is configured to determine a target configuration file based on the data acquisition request and a pre-stored information structure tree, generate a target task based on the target configuration file, and send the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data.

[0009] The vehicle terminal is used to determine target data according to the target task and send the target data to the client through the server.

[0010] According to another aspect of the present invention, a vehicle data acquisition method is provided, the method comprising:

[0011] Send a data collection request to the server from the client;

[0012] The server determines the target configuration file based on the data acquisition request and the pre-stored information structure tree, generates a target task based on the target configuration file, and sends the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data.

[0013] The vehicle terminal determines target data based on the target task and sends the target data to the client through the server.

[0014] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the vehicle data acquisition method according to any embodiment of the present invention.

[0015] The technical solution of this invention includes a client, a server, and a vehicle terminal; wherein: the server is connected to the client and the vehicle terminal respectively; the client is used to send a data collection request to the server; the server is used to determine a target configuration file based on the data collection request and a pre-stored information structure tree, generate a target task based on the target configuration file, and send the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data; the vehicle terminal is used to determine target data based on the target task and send the target data to the client through the server. By implementing the solution provided by this invention, differentiated collection of demand data and the effectiveness, comprehensiveness, timeliness, and flexibility of data collection can be achieved.

[0016] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1This is a schematic diagram of the structure of a vehicle data acquisition system provided in an embodiment of the present invention;

[0019] Figure 2 This is a schematic diagram of the information structure tree provided in an embodiment of the present invention;

[0020] Figure 3 This is a flowchart of a vehicle data acquisition method provided in an embodiment of the present invention;

[0021] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the vehicle data acquisition method of this invention. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] It is understood that before using the technical solutions disclosed in the various embodiments of the present invention, users should be informed of the types, scope of application, and usage scenarios of the personal information involved in the present invention and their authorization should be obtained in accordance with relevant laws and regulations through appropriate means.

[0025] Figure 1 This is a schematic diagram of the vehicle data acquisition system provided in an embodiment of the present invention. Figure 1 As shown, the system includes: a client 11, a server 12, and a vehicle terminal 13; wherein:

[0026] Server 12 is connected to client 11 and vehicle terminal 13 respectively;

[0027] Client 11 is used to send data collection requests to server 12;

[0028] Server 12 is used to determine the target configuration file based on the data acquisition request and the pre-stored information structure tree, generate the target task based on the target configuration file, and send the target task to the vehicle terminal 13 of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data.

[0029] The vehicle terminal 13 is used to determine target data according to the target task and send the target data to the client 11 through the server 12.

[0030] In this system, users can send data collection requests to server 12 through a prompt interface on client 11. The prompt interface can include multi-level directories, and users can generate data collection requests by selecting information from each level of directory. The multi-level directories in the prompt interface correspond one-to-one with the directories in the information structure tree on server 12. The information structure tree is determined based on the vehicle's overall functions and data. Server 12 can determine the configuration file associated with the data collection request, i.e., the target configuration file, from the configuration files pre-stored in server 12's program library that are associated with the information structure tree, based on the data collection request and the pre-stored information structure tree. The target configuration file can include the data variable names for the vehicle data the user wants to collect. Server 12 can generate a target task based on the target configuration file and send the target task to the vehicle terminal 13 of at least one target vehicle via a communication module. Vehicle terminal 13 can determine the data corresponding to the data variable names in the target configuration file, i.e., the target data, based on the target task, and send the target data to client 11 via server 12.

[0031] It should be noted that the information structure tree in server 12 is not fixed and can be updated according to actual application needs, such as updates based on changes in vehicle functions and / or vehicle data.

[0032] The technical solution of this invention includes a client, a server, and a vehicle terminal; wherein: the server is connected to the client and the vehicle terminal respectively; the client is used to send a data collection request to the server; the server is used to determine a target configuration file based on the data collection request and a pre-stored information structure tree, generate a target task based on the target configuration file, and send the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data; the vehicle terminal is used to determine target data based on the target task and send the target data to the client through the server. By implementing the solution provided by this invention, differentiated collection of demand data and the effectiveness, comprehensiveness, timeliness, and flexibility of data collection can be achieved.

[0033] In this embodiment, optionally, the server 12 is specifically used to determine at least one vehicle function of the target vehicle; determine at least one control strategy associated with the vehicle function; determine associated data for implementing the control strategy; the associated data includes at least one of software data, hardware data, and communication data; and determine the information structure tree based on the vehicle function, the control function, and the associated data.

[0034] The information structure tree is a directory structure. The server-side 12 can define the first-level data directory of the information structure tree as vehicle functions. Vehicle functions are functions that can be broken down into parts of the vehicle, such as driving mode functions, cruise control, and automatic emergency braking (AEB). The second-level data directory of the information structure tree is defined as all system functions used to implement the vehicle functions, i.e., control strategies. Taking the vehicle driving mode function as an example, its implementation requires the vehicle instrument system (displaying the driving mode), the engine control system (executing the driving mode – adjusting power in different modes), the air suspension system (executing the driving mode – adjusting vehicle height in different modes), and the four-wheel drive system (executing the driving mode – adjusting drive mode in different modes). Therefore, the first-level data directory of the vehicle driving mode function definition contains four second-level data directories: instrument system, engine control system, air suspension system, and four-wheel drive system. The third-level data directory of the information structure tree is defined as the associated data for implementing the control strategy, including software data, hardware data, and communication data. For example, taking the engine control system as an example of a second-level data directory, this solution can define the software program implementing the engine control strategy, the hardware corresponding to all signals used in the engine control strategy (sensors, actuators, etc.), the engine itself and controller hardware, and communication-related content such as the communication methods, content, and protocols between the engine control system and other systems as three third-level data directories under the engine control system. This enables the construction of an information structure tree, providing a reliable data foundation for on-demand collection of vehicle data.

[0035] In this embodiment, optionally, the server 12 is further configured to determine data parameters associated with the associated data before determining the information structure tree based on the vehicle functions, control functions, and the associated data;

[0036] Server 12 is specifically used to determine the information structure tree based on the vehicle functions, control functions, associated data, and data parameters.

[0037] For the third-level data directory of the information structure tree, for example, taking the first-level data directory as vehicle driving mode function, the second-level data directory as air suspension system, and the third-level data directory as software data, this solution can also determine the set of data variables, i.e., data parameters, under the directory vehicle driving mode function → air suspension system → software data through the server-side 12 and the data lake. This serves as the fourth-level data directory of the information structure tree. This forms data groups corresponding to different needs (requirements) under each third-level data directory, thereby realizing the information structure tree of the entire vehicle data, such as... Figure 2 As shown in the diagram, the data lake includes all vehicle interaction signals and key data defined for status verification or troubleshooting of various functions or systems. It enables the construction of an information structure tree, providing a reliable data foundation for on-demand vehicle data collection.

[0038] In this embodiment, optionally, the data acquisition request includes verification data; the server 12 is further configured to perform a consistency check on the verification data before determining the target configuration file based on the data acquisition request and the pre-stored information structure tree; if the check passes, the target configuration file is determined based on the data acquisition request and the information structure tree.

[0039] When the server 12 receives a data collection request, it can verify the identity of the client 11 by performing consistency verification on the verification data in the data collection request through the security module. After successful verification, the task management module will classify, manage and parse the data collection request and call the corresponding configuration file in the program library as the necessary content of the task to send it to the vehicle terminal 13, which can ensure the security of the vehicle data collection process.

[0040] In one feasible implementation, optionally, the vehicle terminal 13 is also configured to display the target task before determining the target data based on the target task;

[0041] If an object is detected to have an authorized operation on the target task, the target task is downloaded and parsed, and the target data is determined based on the parsing result; the target task includes at least one of the following: target configuration file, task execution strategy, and task type.

[0042] In this solution, the target task can be displayed through the human-machine interaction module in the vehicle terminal 13. If the system detects that the object has permission to operate on the target task, the target task is downloaded through the vehicle terminal 13, and its format and validity are judged. If the conditions are met, the target task is saved to a specific area; otherwise, it is deleted. Simultaneously, the download result is fed back to the object. The vehicle terminal 13 can download multiple tasks simultaneously, but the task activation strategy must follow a predetermined strategy (e.g., execution in sequence). When a task is activated, the target task is parsed and executed according to the task execution strategy and task type in the target task content. Based on the parsing result of the target task, the target data associated with the data variables in the target configuration file in the target vehicle is determined.

[0043] In addition to the target configuration file, the target task may also include client information, target vehicle, task type (event-based and periodic), task execution strategy, and validation fields. The task execution strategy includes task start and end times, task triggering conditions (IG information), vehicle speed information, and periodic intervals. This can improve user experience.

[0044] In another feasible implementation, optionally, the server 12 is also used to store the target data to a storage location associated with the target vehicle.

[0045] Specifically, in this solution, after receiving the target data, the server 12 can store the target data in a storage location associated with the target vehicle within the database. The client 11 can retrieve the corresponding information from the database at any time. This enables the categorized storage of vehicle data, providing a reliable data foundation for subsequent on-demand retrieval of vehicle data.

[0046] In another feasible implementation, optionally, the data acquisition request may further include client information, data configuration information, target vehicle information, task type, and task execution strategy; the task type may be periodic or condition-triggered; the task execution strategy may include at least one of the following: task start and end time, task triggering condition, vehicle speed information, and execution cycle.

[0047] The client information can be the identification information of client 11. The target vehicle information can be the identification information of the target vehicle. The data configuration information can include the data variable names of vehicle data. The task type can be periodic or condition-triggered. The task execution strategy includes the task start time and end time, task triggering conditions - IG information, vehicle speed information, and period interval, etc.

[0048] In addition, server 12 also includes a vehicle model information database for storing and synchronizing vehicle data related to various vehicle models from the OEM. Vehicle terminal 13 has a pre-installed engine to parse the downloaded target task. Upon meeting specific conditions, it executes the target configuration file and has the maximum storage capacity to meet the configuration file's storage requirements. During execution, data is collected and stored according to the specific content of the task. After the task is completed, the status is synchronously fed back to the user. Different strategies are adopted depending on the task type (condition-triggered and periodic). For condition-triggered tasks, vehicle terminal 13 actively confirms the connection status with server 12. If the connection is normal, the stored data is uploaded to server 12. After the upload is complete, vehicle terminal 13 deletes the stored data and the task content. For periodic tasks, the data stored within the current period can be directly uploaded to server 12, and the corresponding stored data in vehicle terminal 13 can be deleted. Alternatively, when the task's validity period expires, all completed data can be uploaded to server 12 together. Then, similar to condition-triggered tasks, after the upload is complete, the data stored in vehicle terminal 13 and the task content are deleted.

[0049] Figure 3 This is a flowchart of a vehicle data acquisition method provided in an embodiment of the present invention. This embodiment is applicable to scenarios where required vehicle data is collected on demand. The vehicle data acquisition method can be executed by the vehicle data acquisition system provided in this embodiment. This vehicle data acquisition system can be implemented in software and / or hardware, and is generally integrated into an electronic device used for vehicle data acquisition. This vehicle data acquisition method and the vehicle data acquisition system provided in the above embodiments belong to the same disclosed concept. Details not described in detail in the method embodiment can be referred to the descriptions in the above embodiments.

[0050] like Figure 3 As shown, the vehicle data acquisition method in this embodiment of the invention may include:

[0051] S310: Sends a data collection request to the server via the client.

[0052] S320: The server determines the target configuration file based on the data acquisition request and the pre-stored information structure tree, generates a target task based on the target configuration file, and sends the target task to the vehicle terminal of at least one target vehicle.

[0053] The information structure tree is determined based on the vehicle's overall functions and data.

[0054] S330: The vehicle terminal determines the target data according to the target task and sends the target data to the client through the server.

[0055] In this embodiment, optionally, the process of determining the information structure tree includes: determining at least one vehicle function of the target vehicle through the server; determining at least one control strategy associated with the vehicle function; determining the associated data for implementing the control strategy; the associated data includes at least one of software data, hardware data, and communication data; and determining the information structure tree based on the vehicle function, the control function, and the associated data.

[0056] In one feasible implementation, optionally, before determining the information structure tree based on the vehicle functions, control functions, and the associated data, the method further includes: determining data parameters associated with the associated data via the server; determining the information structure tree based on the vehicle functions, control functions, and the associated data includes: determining the information structure tree based on the vehicle functions, control functions, the associated data, and the data parameters.

[0057] In this embodiment, optionally, the data acquisition request includes verification data; before determining the target configuration file based on the data acquisition request and the pre-stored information structure tree, the method further includes: performing a consistency verification on the verification data through the server; if the verification passes, then determining the target configuration file based on the data acquisition request and the information structure tree.

[0058] In this embodiment, optionally, before determining the target data based on the target task, the method further includes: displaying the target task through the vehicle terminal; if an object's allowed operation on the target task is detected, downloading the target task, parsing the target task, and determining the target data based on the parsing result; the target task includes at least one of a target configuration file, a task execution strategy, and a task type.

[0059] In another feasible implementation, optionally, after sending the target data to the client via the server, the method further includes: storing the target data to a storage location associated with the target vehicle via the server.

[0060] The technical solution provided by this invention involves a client sending a data collection request to a server; the server determining a target configuration file based on the data collection request and a pre-stored information structure tree, generating a target task based on the target configuration file, and sending the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and data; the vehicle terminal determines the target data based on the target task and sends the target data to the client via the server. By implementing the solution provided by this invention, differentiated collection of required data and the effectiveness, comprehensiveness, timeliness, and flexibility of data collection can be achieved.

[0061] Figure 4 A schematic diagram of an electronic device 40 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0062] like Figure 4 As shown, the electronic device 40 includes at least one processor 41 and a memory, such as a read-only memory (ROM) 42 or a random access memory (RAM) 43, communicatively connected to the at least one processor 41. The memory stores computer programs executable by the at least one processor. The processor 41 can perform various appropriate actions and processes based on the computer program stored in the ROM 42 or loaded into the RAM 43 from storage unit 48. The RAM 43 may also store various programs and data required for the operation of the electronic device 40. The processor 41, ROM 42, and RAM 43 are interconnected via a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0063] Multiple components in electronic device 40 are connected to I / O interface 45, including: input unit 46, such as keyboard, mouse, etc.; output unit 47, such as various types of monitors, speakers, etc.; storage unit 48, such as disk, optical disk, etc.; and communication unit 49, such as network card, modem, wireless transceiver, etc. Communication unit 49 allows electronic device 40 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0064] Processor 41 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 41 performs the various methods and processes described above, such as vehicle data acquisition methods.

[0065] In some embodiments, the vehicle data acquisition method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 40 via ROM 42 and / or communication unit 49. When the computer program is loaded into RAM 43 and executed by processor 41, one or more steps of the vehicle data acquisition method described above may be performed. Alternatively, in other embodiments, processor 41 may be configured to perform the vehicle data acquisition method by any other suitable means (e.g., by means of firmware).

[0066] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0067] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0068] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0069] To provide interaction with an object, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the object; and a keyboard and pointing device (e.g., a mouse or trackball) through which the object provides input to the electronic device. Other types of devices can also be used to provide interaction with the object; for example, feedback provided to the object can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the object can be received in any form (including sound input, voice input, or tactile input).

[0070] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., object computers with a graphical object interface or web browser through which objects can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0071] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0072] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0073] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A vehicle data acquisition system, characterized in that, This includes the client, server, and vehicle terminal; among which: The server is connected to the client and the vehicle terminal respectively; The client is used to send a data collection request to the server. The server is configured to determine a target configuration file based on the data acquisition request and a pre-stored information structure tree, generate a target task based on the target configuration file, and send the target task to the vehicle terminal of at least one target vehicle; the information structure tree is determined based on the vehicle's overall functions and vehicle data. The vehicle terminal is used to determine target data according to the target task and send the target data to the client through the server. The data acquisition request also includes client information, data configuration information, target vehicle information, task type, and task execution strategy; the task type includes periodic or condition-triggered; the task execution strategy includes at least one of the following: task start and end time, task triggering condition, vehicle speed information, and execution cycle; Sending a data collection request to the server includes: the client's prompt interface includes a multi-level directory, the data collection request is generated by selecting information under each level of the directory, and the data collection request is sent to the server through the client's prompt interface, wherein the multi-level directory in the client's prompt interface corresponds one-to-one with each level of the directory in the information structure tree of the server. The server-side is specifically configured to: determine at least one vehicle function of the target vehicle; determine at least one control strategy associated with the vehicle function; determine associated data for implementing the control strategy; the associated data includes at least one of software data, hardware data, and communication data; and determine the information structure tree based on the vehicle function, the control function, and the associated data. The server is further configured to: determine data parameters associated with the associated data before determining the information structure tree based on the vehicle functions, control functions, and the associated data; The server is specifically used to: determine the information structure tree based on the vehicle functions, control functions, associated data, and data parameters; The information structure tree is a directory structure, and it is updated based on changes in the vehicle's overall functions and / or overall vehicle data. The first-level data directory of the information structure tree is defined by the server as the overall vehicle functions, which are the functions that can be separated from the vehicle. The second-level data directory of the information structure tree is defined by the server as all system functions used to implement the overall vehicle functions, i.e., control strategies. The third-level data directory of the information structure tree is defined by the server as the associated data for implementing the control strategies, including software data, hardware data, and communication data. The fourth-level data directory of the information structure tree is defined by the server as a set of data variables under the associated data, i.e., data parameters.

2. The system according to claim 1, characterized in that, The data acquisition request includes verification data; The server is also used to perform consistency verification on the verification data before determining the target configuration file based on the data collection request and the pre-stored information structure tree. If the verification passes, the target configuration file is determined based on the data collection request and the information structure tree.

3. The system according to claim 1, characterized in that, The vehicle terminal is also used to display the target task before determining the target data based on the target task; If an object is detected to have an authorized operation on the target task, the target task is downloaded and parsed, and the target data is determined based on the parsing result; the target task includes at least one of the following: target configuration file, task execution strategy, and task type.

4. The system according to claim 3, characterized in that, The server is also used to store the target data in a storage location associated with the target vehicle.

5. A method for collecting vehicle data, characterized in that, include: Send a data collection request to the server from the client; The server determines the target configuration file based on the data acquisition request and the pre-stored information structure tree, generates a target task based on the target configuration file, and sends the target task to the vehicle terminal of at least one target vehicle. The information structure tree is determined based on the vehicle's overall functions and data. The vehicle terminal determines target data based on the target task and sends the target data to the client through the server. The process of determining the information structure tree includes: determining at least one vehicle function of the target vehicle through the server; determining at least one control strategy associated with the vehicle function; determining the associated data for implementing the control strategy; the associated data includes at least one of software data, hardware data, and communication data; and determining the information structure tree based on the vehicle function, the control function, and the associated data. Sending a data collection request to the server includes: the client's prompt interface includes a multi-level directory, the data collection request is generated by selecting information under each level of the directory, and the data collection request is sent to the server through the client's prompt interface, wherein the multi-level directory in the client's prompt interface corresponds one-to-one with each level of the directory in the information structure tree of the server. Before determining the information structure tree based on the vehicle functions, control functions, and associated data, the method further includes: determining data parameters associated with the associated data via the server. Determining the information structure tree based on the vehicle functions, control functions, and associated data includes: determining the information structure tree based on the vehicle functions, control functions, associated data, and data parameters; The data acquisition request also includes client information, data configuration information, target vehicle information, task type, and task execution strategy; the task type includes periodic or condition-triggered; the task execution strategy includes at least one of the following: task start and end time, task triggering condition, vehicle speed information, and execution cycle; The information structure tree is a directory structure, and it is updated based on changes in the vehicle's overall functions and / or overall vehicle data. The first-level data directory of the information structure tree is defined by the server as the overall vehicle functions, which are the functions that can be separated from the vehicle. The second-level data directory of the information structure tree is defined by the server as all system functions used to implement the overall vehicle functions, i.e., control strategies. The third-level data directory of the information structure tree is defined by the server as the associated data for implementing the control strategies, including software data, hardware data, and communication data. The fourth-level data directory of the information structure tree is defined by the server as a set of data variables under the associated data, i.e., data parameters.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the vehicle data acquisition method of claim 5.

Images