Data acquisition method, data receiving end, data acquisition device, and data acquisition system

Abstract

A data acquisition method, a data receiving end, a data acquisition device, and a data acquisition system. The data acquisition method applied to the data receiving end comprises: receiving a data acquisition rule configuration instruction, and generating a data acquisition rule file on the basis of the data acquisition rule configuration instruction; issuing the rule file to a data acquisition device of a vehicle, so that the data acquisition device parses the rule file, and acquires corresponding target data according to a data acquisition rule obtained by parsing; and receiving target data uploaded by the data acquisition device. According to the technical solution disclosed in the present application, the data receiving end configures and generates the data acquisition rule file, and issues the file to the data acquisition device of the vehicle end, so that on the basis of the received file, the data acquisition device of the vehicle end can dynamically acquire in-vehicle data according to requirements, thereby reducing the data traffic consumed by uploading acquired data, the storage space occupied by storing acquired data, and the costs, and improving the data acquisition efficiency and flexibility.

Description

Data acquisition method, data receiving terminal, data acquisition device and system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202311620890.1, filed on November 29, 2023, entitled “Data Acquisition Method, Data Receiving Terminal, Data Acquisition Device and System,” the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of vehicle-to-cloud technology, and specifically to a data acquisition method, a data receiving terminal, a data acquisition device, and a system. Background Art

[0004] With the popularization of intelligent, electrified and networked vehicles, vehicle data can be collected remotely to meet the demand for remote vehicle data analysis.

[0005] Currently, two methods are commonly used for vehicle data collection: 1) Fully collecting in-vehicle data and uploading it to the receiving end, which then filters out the data that meets the required conditions from the full data; 2) Pre-programming the required data and trigger conditions, and then pre-deploying the programmed program into the vehicle-side data collection device so that the vehicle-side data collection device collects data according to the pre-programmed program. The first data collection method consumes relatively large data transmission traffic and storage costs, while the second data collection method has low data collection flexibility. When the collected data and / or trigger conditions need to be modified, the code needs to be modified, recompiled, and tested, and then remotely updated to the vehicle-side data collection device via OTA (Over-the-Air Technology). This results in a long deployment cycle and low efficiency.

[0006] Summary of the Invention

[0007] In view of the above problems, the present application provides a data acquisition method, a data receiving end, a data acquisition device and a data acquisition system, which are used to reduce the traffic and storage costs consumed by data acquisition and improve the flexibility and efficiency of data acquisition.

[0008] In the first aspect, the present application provides a data collection method, which is applied to a data receiving end, including: receiving a data collection rule configuration instruction, generating a data collection rule file according to the data collection rule configuration instruction; sending the data collection rule file to a data collection device in a vehicle, and the data collection device parsing the data collection rule file and collecting corresponding target data according to the data collection rules obtained by the parsing; and receiving the target data uploaded by the data collection device.

[0009] The technical solution disclosed in the embodiment of the present application generates a data collection rule file by configuring the data receiving end and sends the file to the vehicle-side data collection device, so that the vehicle-side data collection device can realize dynamic on-demand collection of in-vehicle data based on the received file, without the need to collect all in-vehicle data. Therefore, it can reduce the data traffic consumed by uploading the collected data and the storage space and cost of storing the collected data. In addition, the above-mentioned data collection method does not require tedious programming, testing, OTA and other processes, and can collect data remotely on demand at any time, thereby improving the efficiency and flexibility of data collection.

[0010] In some embodiments, before receiving the data collection rule configuration instruction, the method further includes: pre-configuring data collection parameters; the data collection parameters include collection object parameters, and at least one of collection method parameters, collection period parameters, and upload method parameters;

[0011] Receiving a data collection rule configuration instruction includes: receiving the data collection rule configuration instruction corresponding to the data collection parameter;

[0012] Correspondingly, the data collection rule file and the data collection rule both include a collection object and at least one of a collection method, a collection period, and an upload method.

[0013] By pre-configuring data collection parameters, the convenience of user operation and user experience is improved, and the convenience of generating data collection rule configuration files and data collection rule files is improved, and the data collection device can dynamically collect in-vehicle data on demand according to data collection rules, reducing data collection costs and improving data collection flexibility and efficiency.

[0014] In some embodiments, the collection object includes at least one of signal data, event data, fault data and log data; wherein, the event data includes an event and a first target signal data combination when the event occurs, and the fault data includes a fault and a second target signal data combination when the fault occurs.

[0015] By making the collection object include at least one of signal data, event data, fault data and log data, it is convenient for the data collection device to collect the corresponding type of data on demand.

[0016] In some embodiments, the acquisition method includes a periodic acquisition method and / or a triggered acquisition method, and the triggered acquisition method includes a trigger acquisition condition, and the trigger acquisition condition includes at least one of the conditions for the occurrence of the event, the conditions for the occurrence of the fault, and a custom condition.

[0017] By setting the collection method, the data collection device can collect the corresponding target data according to the collection method, thereby improving the data collection performance and meeting the business analysis needs.

[0018] In some embodiments, when the data collection rule includes an upload method, receiving the target data uploaded by the data collection device includes: receiving the target data uploaded by the data collection device according to the upload method.

[0019] The target data collected is uploaded by the data collection device in an uploading manner to better meet the data collection needs and facilitate better business analysis.

[0020] In some embodiments, the uploading method includes real-time uploading and / or cache uploading.

[0021] By setting a specific upload method, the flexibility of uploading collected data is improved, and it is easier for the data receiving end to perform better business analysis.

[0022] In some embodiments, generating a data collection rule file according to the data collection rule configuration instruction includes: generating the data collection rule file according to the data collection rule configuration instruction in a format pre-agreed with the data collection device.

[0023] By generating the data collection rule file according to a pre-agreed format, the data collection device can quickly and smoothly parse the data collection rule file, thereby improving the reliability of data collection.

[0024] In some embodiments, after receiving the target data uploaded by the data acquisition device, the method further includes: parsing the received target data.

[0025] Better meet business analysis needs by parsing target data.

[0026] In the second aspect, the present application provides a data acquisition method, which is applied to a data acquisition device, including: receiving a data acquisition rule file sent by a data receiving end; the data acquisition rule file is generated by the data receiving end according to the received data acquisition rule configuration instruction; parsing the data acquisition rule file to obtain data acquisition rules; collecting corresponding target data according to the data acquisition rules, and uploading the collected target data to the data receiving end.

[0027] The technical solution disclosed in the embodiment of the present application generates a data collection rule file by configuring the data receiving end and sends the file to the vehicle-side data collection device, so that the vehicle-side data collection device can realize dynamic on-demand collection of in-vehicle data based on the received file, without the need to collect all in-vehicle data. Therefore, it can reduce the data traffic consumed by uploading the collected data and the storage space and cost of storing the collected data. In addition, the above-mentioned data collection method does not require tedious programming, testing, OTA and other processes, and can collect data remotely on demand at any time, thereby improving the efficiency and flexibility of data collection.

[0028] In some embodiments, the data collection rule file includes a collection object and at least one of a collection method, a collection period, and an upload method.

[0029] By including the above content in the data collection rule file, the data collection device can dynamically collect in-vehicle data on demand, thereby reducing data collection costs and improving data collection flexibility and efficiency.

[0030] In some embodiments, when the data collection rule includes the collection mode and the collection mode includes a trigger collection mode, the data collection rule file is parsed to obtain the data collection rule, including: caching signal data on the in-vehicle bus corresponding to the collection object and the signal included in the collection mode to generate a signal cache list; generating a condition tree according to the trigger collection conditions included in the trigger collection mode;

[0031] Collecting the corresponding target data according to the data collection rules includes: judging the signal data corresponding to the trigger collection condition in the signal cache list according to the condition tree; if the judgment result is true, collecting the corresponding target data according to the signal data corresponding to the collection object in the signal cache list.

[0032] By setting up a signal cache list, we can try to avoid missing the target data we want to collect. By generating a condition tree based on the trigger collection conditions, the data acquisition device can intuitively and clearly judge whether the corresponding signal data meets the trigger collection conditions, so as to improve the efficiency and accuracy of rule judgment.

[0033] In some embodiments, when the data collection rule file includes a collection period, the signal data on the in-vehicle bus corresponding to the signal included in the collection object and the collection method is cached to generate a signal cache list, including: according to the collection period, the signal data on the in-vehicle bus corresponding to the signal included in the collection object and the collection method is cached to generate the signal cache list.

[0034] By setting the collection period, the data collection device can collect data according to the set collection period, so as to improve the accuracy of data collection and better meet the data collection needs, thereby facilitating better business analysis.

[0035] In some embodiments, when the data collection rule file includes an upload method, uploading the collected target data to the data receiving end includes: uploading the collected target data according to the upload method.

[0036] By setting the upload method and allowing the data acquisition device to upload according to the upload method, data acquisition needs can be better met and business analysis can be better performed.

[0037] In the third aspect, the present application provides a data receiving end, including: a generation module, used to receive data acquisition rule configuration instructions, and generate a data acquisition rule file according to the data acquisition rule configuration instructions; a sending module, used to send the data acquisition rule file to the data acquisition device in the vehicle, and the data acquisition device parses the data acquisition rule file and collects corresponding target data according to the data acquisition rules obtained by the analysis; a receiving and collecting data module, used to receive the target data uploaded by the data acquisition device.

[0038] In a fourth aspect, the present application provides a data acquisition device, comprising: a rule file receiving module for receiving a data acquisition rule file sent by a data receiving end; the data acquisition rule file is generated by the data receiving end according to the received data acquisition rule configuration instruction; a file parsing module for parsing the data acquisition rule file to obtain data acquisition rules; and an acquisition upload module for collecting corresponding target data according to the data acquisition rules, and uploading the collected target data to the data receiving end.

[0039] In the fifth aspect, the present application provides a data acquisition system, including a data receiving end and a data acquisition device located in a vehicle, wherein: the data receiving end is used to receive data acquisition rule configuration instructions, and generate a data acquisition rule file according to the data acquisition rule configuration instructions; the data acquisition rule file is sent to the data acquisition device; the data acquisition device is used to parse the data acquisition rule file to obtain data acquisition rules; the corresponding target data is collected according to the data acquisition rules, and the collected target data is uploaded to the data receiving end.

[0040] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present application. The same reference numerals are used throughout the drawings to represent the same components. In the drawings:

[0042] FIG1 is a flow chart of a data collection method applied to a data receiving end in some embodiments of the present application;

[0043] FIG2 is a flow chart of a data collection method according to some embodiments of the present application;

[0044] FIG3 is a flow chart of a data acquisition method applied to a data acquisition device in a vehicle according to some embodiments of the present application;

[0045] FIG4 is a flow chart of the data collection device from receiving a data collection rule file to collecting target data in some embodiments of the present application;

[0046] FIG5 is a schematic structural diagram of a data receiving terminal according to some embodiments of the present application;

[0047] FIG6 is a schematic structural diagram of a data acquisition device according to some embodiments of the present application. DETAILED DESCRIPTION

[0048] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0049] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.

[0050] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.

[0051] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0052] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0053] In the description of the embodiments of the present application, the term "multiple" refers to more than two (including two). Similarly, "multiple groups" refers to more than two groups (including two groups), and "multiple pieces" refers to more than two pieces (including two pieces).

[0054] With the increasing prevalence of intelligent, electrified, and connected vehicles, remote vehicle data collection has become essential. Deploying data collection devices on vehicles allows for remote issuance of collection tasks, enabling the start and stop of vehicle data collection. Collected data can then be transmitted to the cloud via wireless networks, enabling remote vehicle data analysis.

[0055] At present, the following two methods are generally used to collect vehicle data: 1) The data acquisition device collects all the data in the vehicle and uploads it to the receiving end. The receiving end then filters out the data with the required conditions from the full amount of data. However, due to the large number of types of in-vehicle data and the high update frequency of some in-vehicle data, this data acquisition method consumes a large amount of data traffic when uploading data, and the receiving end needs to consume a large amount of storage space and storage costs to store this data. 2) The data to be collected and the trigger conditions for data collection are programmed in advance at the receiving end, and the pre-programmed data acquisition code is then pre-deployed on the vehicle-side data acquisition device to realize the remote start and stop vehicle data collection task. This data acquisition method has low flexibility. If the collected data and / or trigger conditions need to be modified, the code needs to be modified, recompiled, tested, and then updated to the vehicle-side data acquisition device through OTA remote upgrade. Therefore, the deployment cycle is long and the collection efficiency is low.

[0056] To this end, the applicant proposes a data collection method, which generates a data collection rule file by configuring the data receiving end and sends the file to the data collection device on the vehicle side. The data collection device on the vehicle side realizes dynamic on-demand collection of in-vehicle data based on the received file, without the need to collect all the in-vehicle data. Therefore, the data traffic consumed by uploading the collected data and the storage space and cost occupied by storing the collected data can be reduced. In addition, the data collection method of the present application can remotely collect data on demand at any time without the need for tedious programming, testing, OTA and other processes. Therefore, the flexibility and efficiency of data collection can be improved.

[0057] For details, please refer to Figures 1 and 2, where Figure 1 is a flow chart of a data collection method applied to a data receiving end in some embodiments of the present application, and Figure 2 is a flow chart of a data collection method in some embodiments of the present application. The data collection method of this embodiment may include:

[0058] S11: Receive a data collection rule configuration instruction, and generate a data collection rule file according to the data collection rule configuration instruction.

[0059] When in-vehicle data collection is required, users on the data receiving end can send data collection rule configuration instructions to the data receiving end based on data collection requirements and vehicle operation scenarios. For example, the data collection rule configuration instructions can include data collection rules such as the target data to be collected and the trigger conditions for data collection. Specifically, users can send data collection rule configuration instructions to the data receiving end through the human-computer interface on the data receiving end using voice input, keyboard input, touch screen input, etc. It should be noted that the data receiving end can specifically be a cloud server, computer, mobile phone, or other device.

[0060] Accordingly, the data receiving end may receive the data collection rule configuration instruction sent by the user, and then may generate a data collection rule file according to the received data collection rule configuration instruction, and the data collection rule file may specifically include the data collection rules.

[0061] S12: Sending the data collection rule file to the data collection device in the vehicle, the data collection device parses the data collection rule file and collects the corresponding target data according to the data collection rules obtained from the parsing.

[0062] After generating a data collection rule file based on the data collection rule configuration instructions, the data receiving end can distribute the data collection rule file to the vehicle's data collection device via a wireless network. The data receiving end can distribute the data collection rule file to a specific vehicle's data collection device or to data collection devices in a specific number of vehicles based on business needs or user settings. Furthermore, the data receiving end can directly distribute the generated data collection rule file to the vehicle's data collection device, or it can first encrypt the generated data collection rule file and then distribute the encrypted data collection rule file to the vehicle's data collection device.

[0063] After receiving the data collection rule file sent by the data receiving end, the data collection device in the vehicle can perform a full-text scan and analysis of the data collection rule file to obtain the data collection rules. Then, the target data in the vehicle can be collected according to the data collection rules obtained by the analysis, wherein the target data is the target data to be collected contained in the data collection rules. That is, the data collection device in the vehicle can receive the data collection rule file generated by the data receiving end, parse the data collection rule file to obtain the data collection rules, and realize on-demand collection of in-vehicle data according to the data collection rules, without the need to collect all in-vehicle data, nor the need to pre-program the data collection code at the data receiving end and pre-deploy it in the data collection device to collect in-vehicle data. Therefore, the cost of data collection can be reduced, and the efficiency and flexibility of data collection can be improved.

[0064] S13: Receive target data uploaded by the data acquisition device.

[0065] After collecting the target data according to the analyzed data collection rules, the data collection device in the vehicle can upload the collected target data to the data receiving end via a wireless network. The data receiving end can then receive the target data uploaded by the data collection device, perform business analysis based on the received target data, and allow users on the data receiving end to remotely access the target data in the vehicle.

[0066] As can be seen from the above, the data acquisition device can realize on-demand collection of in-vehicle data according to the data acquisition rule configuration file, and only upload the collected target data to the data receiving end. Therefore, the data traffic consumed by uploading the collected data to the data receiving end can be reduced, and the storage space and storage cost consumed by storing the collected data at the data receiving end can be reduced. In addition, the above-mentioned data acquisition does not require the pre-writing of data acquisition code, compilation, testing, pre-deployment and other processes. It only needs to receive the data acquisition rule configuration instructions and generate the data acquisition rule file according to the instructions, and then send it to the data acquisition device. Even if the collected data needs to be modified, the user on the data receiving end only needs to send the data acquisition rule modification instruction to the data receiving end. Then, the data receiving end modifies the initial data acquisition rule file according to the data acquisition rule modification instruction or generates a new data acquisition rule file and sends it to the data acquisition device in the vehicle. Remote on-demand data collection can be realized at any time without modifying the code, recompiling, testing, OTA and other processes. Therefore, the flexibility of data acquisition is relatively high and the deployment cycle of data acquisition is relatively short.

[0067] The technical solution disclosed in the embodiment of the present application generates a data collection rule file by configuring the data receiving end and sends the file to the vehicle-side data collection device, so that the vehicle-side data collection device can realize dynamic on-demand collection of in-vehicle data based on the received file, without the need to collect all in-vehicle data. Therefore, it can reduce the data traffic consumed by uploading the collected data and the storage space and cost of storing the collected data. In addition, the above-mentioned data collection method does not require tedious programming, testing, OTA and other processes, and can collect data remotely on demand at any time, thereby improving the efficiency and flexibility of data collection.

[0068] According to some embodiments of the present application, before receiving the data collection rule configuration instruction, the following steps may also be included:

[0069] Pre-configure data collection parameters; the data collection parameters may include collection object parameters, and may also include at least one of collection method parameters, collection period parameters, and upload method parameters;

[0070] Receive data collection rule configuration instructions, which may include:

[0071] receiving a data collection rule configuration instruction corresponding to the data collection parameters;

[0072] Accordingly, both the data collection rule file and the data collection rule may include a collection object, and may also include at least one of a collection method, a collection period, and an upload method.

[0073] Before receiving the data collection rule configuration instructions, the data receiving end can also pre-configure data collection parameters so that the user on the data receiving end can send data collection rule configuration instructions according to the data collection parameters pre-configured by the data receiving end, thereby improving the convenience of user operation and user experience, and improving the convenience of generating data collection rule configuration files and data collection rule files.

[0074] The data collection parameters may specifically include collection object parameters, and may also include at least one of collection method parameters, collection period parameters, and upload method parameters. Collection object parameters refer to the parameters corresponding to the target data to be collected; collection method parameters refer to the parameters corresponding to the collection mechanism of the target data; collection period parameters refer to the parameters corresponding to the desired collection time of the target data, for example, you can specify that data can be collected every Monday to Sunday according to the data collection rules, or specify that data can be collected according to the data collection rules within the start and end time points; upload method parameters refer to the parameters corresponding to how the collected target data is uploaded.

[0075] Each parameter in the data collection parameters can be regarded as a variable or field. The user on the data receiving end can set specific content under the corresponding data collection parameters as needed, so that the user can send a data collection rule configuration instruction corresponding to the data collection parameters to the data receiving end. That is, the data collection rule configuration instruction can include the data collection content corresponding to the data collection parameters. For example, when the data collection parameters include a collection object parameter, the data collection rule configuration instruction can include the collection object corresponding to the collection object parameter (that is, the collection object can be regarded as the specific content of the collection object parameter). It should be noted that when the data receiving end includes at least two data collection parameters, the user on the data receiving end can also set corresponding content under some or all of the data collection parameters according to data collection needs. For example, when the data collection parameters include a collection object parameter, a collection method parameter, a collection period parameter, and an upload method parameter, the user on the data receiving end can set the collection object corresponding to the collection object parameter and the collection method corresponding to the collection method parameter according to data collection needs, or can set the collection object corresponding to the collection object parameter, the collection method corresponding to the collection method parameter, the collection period corresponding to the collection period parameter, and the upload method corresponding to the upload method parameter.

[0076] On the basis of the above, the data collection rule configuration instructions received by the data receiving end, the data collection rule file generated according to the data collection rule configuration instructions, and the data collection rules obtained by parsing the data collection device in the vehicle can all include the collection objects corresponding to the collection object parameters, and can also include the collection methods corresponding to the collection method parameters, the collection time periods corresponding to the collection time period parameters, and the upload methods corresponding to the upload method parameters, so that the data collection device can dynamically collect the in-vehicle data on demand according to the above rule content contained in the data collection rules, thereby reducing the data collection cost and improving the flexibility and efficiency of data collection.

[0077] According to some embodiments of the present application, the collection object may include at least one of signal data, event data, fault data, and log data;

[0078] The event data may include an event and a first target signal data combination when the event occurs, and the fault data may include a fault and a second target signal data combination when the fault occurs.

[0079] The collection objects in the data collection rule file generated by the data receiving end and the data collection rules parsed by the data collection device may specifically include at least one of signal data, event data, fault data and log data, that is, the collection objects may specifically include at least one of the aforementioned types of data, so that the data collection device can collect the corresponding type of data on demand (that is, the collection object is the target data to be collected by the data collection device).

[0080] The signal data refers to the signals on the communication bus such as CAN (Controller Area Network) / LIN (Local Interconnect Network) in the vehicle. Any one or more signals can be specified as the signal data of the collection object.

[0081] The event data may specifically include the event itself and the first target signal data combination when the event occurs. Among them, the event mentioned here may be an event predefined in the data receiving end, such as sudden deceleration, sharp turn, etc., and when the event is predefined in the data receiving end, the first target signal data combination corresponding to the event may also be preconfigured. Taking the predefined sudden deceleration event as an example, it may be specifically defined as the vehicle speed dropping from more than 80 km / h to 5 km / h within 2 seconds, and the brake pedal is continuously pressed within 2 seconds. The first target signal data combination corresponding to the event may be the battery voltage, battery current, and battery temperature, etc. By predefining events in the data receiving end, it is convenient for users to directly select the corresponding event according to their needs when sending data collection rule configuration instructions. Of course, users can also define events themselves when sending data collection rule configuration instructions.

[0082] Fault data may specifically include the fault itself and the second target signal data combination at the time the fault occurred. The fault and corresponding second target signal data combination may also be predefined on the data receiving end for user selection. Of course, the user may also configure the fault and second target signal data combination when sending a data collection rule configuration instruction.

[0083] Log data may include communication bus original log (log), application print log, etc., wherein the communication bus original log is, for example, CAN log, Ethernet log, etc.; event data may include the event itself and the first target signal combination when the event occurs.

[0084] According to some embodiments of the present application, the collection mode may include a periodic collection mode and / or a triggered collection mode. The triggered collection mode may include a trigger collection condition. The trigger collection condition may include at least one of an event occurrence condition, a fault occurrence condition, and a custom condition.

[0085] The data collection rule file generated by the data receiving end and the data collection rule parsed by the data collection device may include a collection method, and the collection method may include a periodic collection method and / or a triggered collection method, so that the data collection device can collect the corresponding target data according to the collection method, thereby improving the data collection performance and facilitating the satisfaction of business analysis needs. Among them, the "and / or" mentioned here means that in the case of collecting multiple target data, all target data may be collected using a periodic collection method, or all target data may be collected using a triggered collection method, or a part of the target collection data may be collected using a periodic collection method and another part of the target collection data may be collected using a triggered collection method. It should be noted that the subsequent "and / or" has a similar meaning to the "and / or" here, and will not be repeated in detail.

[0086] Among them, the periodic collection method refers to collecting corresponding target data according to a fixed frequency period, such as collecting corresponding target data at 50 milliseconds, 1 second, 5 seconds, and 10 seconds. The specific collection period size can be set according to needs.

[0087] The trigger acquisition mode includes trigger acquisition conditions, which refer to the acquisition of target data when the corresponding signal data meets the trigger acquisition conditions. Specifically, when the acquisition mode is triggered, the data acquisition device first determines the rules according to the trigger acquisition conditions when acquiring target data. When the corresponding signal data meets the trigger acquisition conditions, the target data is acquired on demand. The trigger acquisition conditions can specifically include at least one of the following: event occurrence conditions, fault occurrence conditions, and custom conditions.

[0088] The event conditions are the signals used to define the event and the conditions that the signals meet. When the collection object includes event data, the collection method includes the event conditions, which can be specifically obtained from the events included in the event data. When the corresponding signal data within the vehicle meets the event conditions, it indicates that the event has occurred, triggering data collection. The target data collected is the first target signal data combination in the event data.

[0089] The conditions for the occurrence of a fault specifically refer to the signals used to define the fault and the conditions satisfied by the signals. When the acquisition object includes fault data, the acquisition method includes the conditions for the occurrence of the fault, and the conditions for the occurrence of the fault can be obtained from the fault contained in the fault data. When the corresponding signal data in the vehicle meets the conditions for the occurrence of the fault, it indicates that the fault has occurred. At this time, data acquisition is triggered, and the target data collected is the second target signal data combination in the fault data.

[0090] Custom conditions are user-defined triggering conditions for collecting target data when sending data collection rule configuration instructions. For example, custom conditions may include: 1) single-signal logical comparison, where the logical comparison can be greater than, greater than or equal to, less than, less than or equal to, or not equal to, such as vehicle speed > 100 km / h; 2) logical comparison after a mathematical operation (such as +-× / ) on multiple signals, such as (voltage U / current I) > 3 ohms; 3) sudden change within a specified signal time window reaching a specified threshold; 4) change before and after a specified signal reaching a specified threshold, such as from 0 to 1, 1 to 0, or abs(signal data at time 1 - signal data at time 2) > 3; 5) a combination of multiple conditions (AND, OR, NOT, etc.).

[0091] When the collection mode is triggered and the trigger conditions are met, you can specify the target data to be collected a certain number of seconds before and after the trigger conditions are met, so that the data receiver can obtain more information from the collected target data. Of course, you can also specify the target data to be collected a certain number of seconds after the trigger conditions are met.

[0092] According to some embodiments of the present application, when the data collection rule includes an upload method, receiving the target data uploaded by the data collection device may include:

[0093] Receive target data uploaded by the data acquisition device in an uploading manner.

[0094] When the vehicle-side data collection device parses the data collection rule file and obtains data collection rules that include an upload method, the vehicle-side data collection device can upload the collected target data to the data receiving end using the upload method, thereby increasing the flexibility of data upload. Accordingly, the data receiving end can receive the target data uploaded by the data collection device using the upload method, thereby better meeting data collection needs and facilitating better business analysis.

[0095] According to some embodiments of the present application, the uploading method may include real-time uploading and / or cache uploading.

[0096] The upload methods contained in the data collection rule file and in the data collection rules may specifically include real-time upload and / or cache upload. Among them, real-time upload means that the data collection device uploads the target data to the data receiving end immediately after collecting it. Cache upload means that the data collection device can cache the target data in a local file after collecting it, and then choose a suitable time to upload it according to the local storage space and network connection conditions. For example, the local file with the cached target data can be uploaded to the data receiving end when the local storage space is not greater than a preset threshold (the size of which can be set according to the situation) and / or the network connection is good.

[0097] The above settings can improve the flexibility of uploading collected data and facilitate better business analysis at the data receiving end.

[0098] According to some embodiments of the present application, generating a data collection rule file according to a data collection rule configuration instruction may include:

[0099] Generate a data collection rule file according to the data collection rule configuration instructions in a format pre-agreed with the data collection device.

[0100] The data receiving end can pre-agree on the communication format (i.e., pre-agree on the protocol) with the data acquisition device in the vehicle. When the data receiving end generates the data acquisition rule file according to the data acquisition rule configuration instruction, the data acquisition rule file can be generated according to the data acquisition rule configuration instruction in accordance with the format pre-agreement with the data acquisition device, so that the data acquisition device in the vehicle can quickly and smoothly parse the data acquisition rule file according to the format pre-agreement with the data receiving end, thereby improving the reliability of data acquisition.

[0101] According to some embodiments of the present application, after receiving the target data uploaded by the data acquisition device, the following steps may also be included:

[0102] Parse the received target data.

[0103] After receiving the target data uploaded by the data acquisition device, the data receiving end can also parse the received target data in accordance with the format pre-agreed with the data acquisition device at any time or when the received target data meets certain conditions (for example, the amount of target data reaches a certain value) to better meet business analysis needs.

[0104] The present application also provides a data acquisition method for a data acquisition device in a vehicle. Specifically, see FIG3 , which is a flow chart of the data acquisition method for a data acquisition device in a vehicle according to some embodiments of the present application. The method may include:

[0105] S31: receiving a data collection rule file sent by a data receiving terminal; the data collection rule file is generated by the data receiving terminal according to the received data collection rule configuration instruction.

[0106] The data receiving end can receive the data collection rule configuration instructions sent by the user on the data receiving end side, and then, can generate a data collection rule file according to the received data collection rule configuration instructions, and send the data collection rule file to the data collection device in the vehicle, so that the data collection device can realize dynamic on-demand collection of in-vehicle data according to the data collection rule file.

[0107] S32: Parse the data collection rule file to obtain data collection rules.

[0108] After receiving the data collection rule file sent by the data receiving end, the data collection device can scan and parse the data collection rule file in full to obtain data collection rules, wherein the data collection rules may include target data to be collected, trigger conditions for data collection, etc.

[0109] S33: Collect the corresponding target data according to the data collection rules, and upload the collected target data to the data receiving end.

[0110] After parsing the data collection rules, the data collection device can collect target data from the vehicle according to the data collection rules, where the target data is the target data to be collected contained in the data collection rules. The collected target data can then be uploaded to the data receiving terminal via a wireless network.

[0111] As can be seen from the above, the data acquisition device can realize on-demand collection of in-vehicle data according to the data acquisition rule configuration file, and only upload the collected target data to the data receiving end. Therefore, the data traffic consumed by uploading the collected data to the data receiving end can be reduced, and the storage space and storage cost consumed by storing the collected data at the data receiving end can be reduced. In addition, the above data acquisition does not require pre-writing data acquisition code, compilation, testing, pre-deployment and other processes. It only needs to receive the data acquisition rule configuration instruction and generate the data acquisition rule file according to the instruction and then send it to the data acquisition device. Even if the collected data needs to be modified, the user on the data receiving end only needs to send the data acquisition rule modification instruction to the data receiving end. Then, according to the data receiving end, the initial data acquisition rule file is modified according to the data acquisition rule modification instruction or a new data acquisition rule file is generated and sent to the data acquisition device in the vehicle. Remote on-demand data collection can be realized at any time without modifying the code, recompiling, testing, OTA and other processes. Therefore, the flexibility and efficiency of data acquisition can be improved.

[0112] According to some embodiments of the present application, the data collection rule file may include a collection object, and may also include at least one of a collection method, a collection period, and an upload method.

[0113] The data receiving end can pre-configure data collection parameters, which can specifically include collection object parameters, and of course, at least one of collection method parameters, collection period parameters, and upload method parameters. Accordingly, the user on the data receiving end can set specific content under the corresponding data collection parameters as needed to generate data collection rule configuration instructions corresponding to the data collection parameters and send them to the data receiving end.

[0114] On the basis of the above, the data collection rule file generated by the data receiving end according to the data collection rule configuration instruction may include the collection object corresponding to the collection object parameter, and may also include the collection method corresponding to the collection method parameter, the collection period corresponding to the collection period parameter, and the upload method corresponding to the upload method parameter, so that the data collection device can dynamically collect the in-vehicle data on demand according to the above rule content contained in the data collection rule, thereby reducing the data collection cost and improving the flexibility and efficiency of data collection.

[0115] For details, please refer to Figure 4, which is a flow chart of the data collection device in some embodiments of the present application from receiving a data collection rule file to collecting target data. According to some embodiments of the present application, when the data collection rule includes a collection method and the collection method includes a trigger collection method, the data collection rule file is parsed to obtain the data collection rule, which may include:

[0116] Cache the signal data on the in-vehicle bus corresponding to the signals included in the acquisition object and acquisition method, and generate a signal cache list;

[0117] Generate a condition tree according to the trigger collection conditions included in the trigger collection method;

[0118] Collect the corresponding target data according to the data collection rules, which may include:

[0119] Judge the signal data corresponding to the trigger acquisition conditions in the signal buffer list according to the condition tree;

[0120] If the judgment result is true, the corresponding target data is collected according to the signal data corresponding to the collection object in the signal buffer list.

[0121] The data collection rule file generated by the data receiving end may include a collection method. When the collection method is a trigger collection method (the trigger collection method includes trigger collection conditions), the data collection device parses the data collection rule file to obtain the data collection rules. Specifically, the process may be as follows:

[0122] 1) Considering that signal data on the in-vehicle bus is constantly updated and changing, in order to minimize missing target data to be collected and improve data collection performance, signal data corresponding to signals included in the data collection rules transmitted on the in-vehicle bus can be cached into a signal cache list. Subsequently, target data can be collected based on the signal cache list. Specifically, the data collection rule file can be fully scanned to obtain all signals included in the collection objects and collection methods (specifically, the trigger collection conditions in the trigger collection method). The signal data transmitted on the in-vehicle bus can then be filtered (specifically, real-time filtering can be performed) based on the signals included in the collection objects and collection methods to obtain signal data corresponding to the signals included in the collection objects and collection methods. The signal data corresponding to the signals included in the collection objects and collection methods can then be cached to generate a signal cache list. The signal data corresponding to the signals included in the collection objects and collection methods can be cached in a single signal cache list, which indicates which signal data corresponds to the collection objects and which signal data corresponds to the signals included in the collection methods. Alternatively, the signal data corresponding to the collection objects can be cached in a first signal cache list, and the signal data corresponding to the signals included in the collection methods can be cached in a second signal cache list.

[0123] 2) The trigger acquisition conditions contained in the trigger acquisition method are expanded into a condition tree according to the agreed grammatical structure. Among them, the condition tree is a data structure that combines conditions and operations. It can be used to represent complex logical relationships and perform different operations according to different conditions. The agreed grammatical structure mentioned above can specifically be the operator symbol (such as AND, OR, +, -, etc.) in the trigger acquisition condition as the parent node, the signal involved in the operation as the leaf node of the parent node, and the lowest node in the condition tree is the leaf node that cannot be decomposed into sub-conditions, which serves as the input for the next rule judgment. Of course, other grammatical structures can also be used to expand the trigger acquisition conditions in the trigger acquisition method into a condition tree. By expanding the trigger acquisition conditions in the trigger acquisition method into a condition tree, it is convenient for the data acquisition device to intuitively and clearly judge whether the corresponding signal data meets the trigger acquisition conditions, so as to improve the efficiency and accuracy of rule judgment.

[0124] There is no restriction on the execution order between the above 1) and 2), and they can be executed simultaneously, or 1) can be executed first and then 2), or 2) can be executed first and then 1).

[0125] On the basis of the above, when the data acquisition device collects the corresponding target data according to the data acquisition rules, it can first make a rule judgment and then collect data on demand, that is, it can make a judgment according to the trigger collection conditions in the data acquisition rules, and collect data on demand when the trigger collection conditions are met. Specifically, the data acquisition device can judge the signal data corresponding to the trigger collection conditions in the signal cache list according to the generated condition tree. If the judgment result is true, it indicates that the corresponding signal data meets the trigger collection conditions. At this time, the data acquisition device can collect the corresponding target data according to the signal data corresponding to the collection object in the signal cache list. Specifically, it can determine the time when the trigger collection conditions are met, and collect target data several seconds before and after the corresponding time from the signal cache list according to the collection object to improve the accuracy of data collection. If the judgment result is false, it indicates that the corresponding signal data does not meet the trigger collection conditions. At this time, data collection is not triggered, and the subsequent frame signal data on the vehicle bus is waited for and the judgment according to the condition tree is continued.

[0126] As shown in Figure 4, the rule judgment illustrates a condition tree obtained by expanding the trigger acquisition conditions according to the agreed grammatical format. The signal data corresponding to the trigger acquisition conditions and the signal data corresponding to the acquisition object are filtered out from the signal data transmitted on the in-vehicle bus. The signals appearing in the trigger acquisition conditions are expanded into a condition tree. Based on the condition tree, the signal data corresponding to the filtered trigger acquisition conditions are judged. If the trigger acquisition conditions are met, the corresponding target data is collected.

[0127] According to some embodiments of the present application, when the data collection rule file includes a collection period, signal data corresponding to the signals included in the collection object and collection mode on the vehicle bus is cached to generate a signal cache list, which may include:

[0128] According to the collection period, signal data corresponding to the collection object and the signal included in the collection method on the vehicle bus are cached to generate a signal cache list.

[0129] When the data collection rule file generated by the data receiving end includes a collection period, the data collection device can specifically cache the signal data corresponding to the signals included in the collection object and collection method on the vehicle bus according to the set collection period to generate a corresponding signal cache list, thereby improving the accuracy of data collection and better meeting data collection needs, thereby facilitating better business analysis.

[0130] According to some embodiments of the present application, when the data collection rule file includes an upload method, uploading the collected data to the data receiving end may include:

[0131] Upload the collected target data according to the upload method.

[0132] When the data collection rules generated by the data receiving end include an upload method, the data collection device can upload the collected target data to the data receiving end according to the upload method to better meet the data collection needs and facilitate better business analysis.

[0133] The present application also provides a data receiving terminal. For details, see FIG5 , which is a schematic diagram of the structure of a data receiving terminal in some embodiments of the present application. The data receiving terminal 50 may include: a generation module 51, a delivery module 52, and a data acquisition receiving module 53. The generation module 51 is configured to receive a data acquisition rule configuration instruction and generate a data acquisition rule file based on the data acquisition rule configuration instruction; the delivery module 52 is configured to deliver the data acquisition rule file to a data acquisition device in the vehicle, which then parses the data acquisition rule file and acquires corresponding target data according to the parsed data acquisition rules; and the data acquisition receiving module 53 is configured to receive target data uploaded by the data acquisition device.

[0134] According to some embodiments of the present application, the data receiving end 50 may further include: a pre-configuration module, which is used to pre-configure data collection parameters before receiving the data collection rule configuration instruction; the data collection parameters may include collection object parameters, and may also include at least one of collection method parameters, collection period parameters, and upload method parameters;

[0135] The generating module 51 receives a data collection rule configuration instruction, specifically for receiving a data collection rule configuration instruction corresponding to the data collection parameters;

[0136] Accordingly, both the data collection rule file and the data collection rule may include a collection object, and may also include at least one of a collection method, a collection period, and an upload method.

[0137] According to some embodiments of the present application, the collection object may include at least one of signal data, event data, fault data, and log data;

[0138] The event data may include an event and a first target signal data combination when the event occurs, and the fault data may include a fault and a second target signal data combination when the fault occurs.

[0139] According to some embodiments of the present application, the collection mode may include a periodic collection mode and / or a triggered collection mode. The triggered collection mode may include a trigger collection condition. The trigger collection condition may include at least one of an event occurrence condition, a fault occurrence condition, and a custom condition.

[0140] According to some embodiments of the present application, when the data collection rule includes an upload method, the data collection receiving module 53 receives the target data uploaded by the data collection device, specifically for receiving the target data uploaded by the data collection device according to the upload method.

[0141] According to some embodiments of the present application, the uploading method may include real-time uploading and / or cache uploading.

[0142] According to some embodiments of the present application, the generation module 51 generates a data collection rule file according to the data collection rule configuration instruction, specifically for generating the data collection rule file according to the data collection rule configuration instruction in a format pre-agreed with the data collection device.

[0143] According to some embodiments of the present application, the data receiving end 50 may further include: a data parsing module, which is used to parse the received target data after receiving the target data uploaded by the data acquisition device.

[0144] The present application also provides a data acquisition device. For details, see FIG6 , which is a schematic diagram of the structure of a data acquisition device according to some embodiments of the present application. The data acquisition device 60 may include: a rule file receiving module 61, a file parsing module 62, and a collection and upload module 63. The rule file receiving module 61 is configured to receive a data collection rule file sent by a data receiving terminal; the data collection rule file is generated by the data receiving terminal based on a received data collection rule configuration instruction; the file parsing module 62 is configured to parse the data collection rule file to obtain data collection rules; and the collection and upload module 63 is configured to collect corresponding target data according to the data collection rules and upload the collected target data to the data receiving terminal.

[0145] According to some embodiments of the present application, the data collection rule file may include a collection object, and may also include at least one of a collection method, a collection period, and an upload method.

[0146] According to some embodiments of the present application, when the data collection rule includes a collection mode and the collection mode includes a trigger collection mode, the file parsing module 62 parses the data collection rule file to obtain data collection rules specifically for caching signal data on the in-vehicle bus corresponding to the collection object and the signal included in the collection mode, generating a signal cache list, and generating a condition tree based on the trigger collection conditions included in the trigger collection mode;

[0147] The collection and upload module 63 collects the corresponding target data according to the data collection rules, and is specifically used to judge the signal data corresponding to the trigger collection conditions in the signal cache list according to the condition tree; if the judgment result is true, the corresponding target data is collected according to the collection objects in the signal cache list.

[0148] According to some embodiments of the present application, when the data acquisition rule file includes an acquisition period, the file parsing module 62 caches the signal data on the in-vehicle bus corresponding to the signals included in the acquisition object and the acquisition method, and generates a signal cache list, which is specifically used to cache the signal data on the in-vehicle bus corresponding to the signals included in the acquisition object and the acquisition method according to the acquisition period, and generate a signal cache list.

[0149] According to some embodiments of the present application, when the data collection rule file includes an upload method, the collection and upload module 63 uploads the collected data to the data receiving end, specifically for uploading the collected target data according to the upload method.

[0150] The present application also provides a data acquisition system, which may include a data receiving terminal and a data acquisition device located within a vehicle. The data receiving terminal is configured to receive data acquisition rule configuration instructions, generate a data acquisition rule file based on the data acquisition rule configuration instructions, and send the data acquisition rule file to the data acquisition device. The data acquisition device is configured to parse the data acquisition rule file to obtain data acquisition rules, collect corresponding target data according to the data acquisition rules, and upload the collected target data to the data receiving terminal.

[0151] According to some embodiments of the present application, the data receiving end is further configured to pre-configure data collection parameters before receiving the data collection rule configuration instruction; the data collection parameters may include collection object parameters, and may also include at least one of collection method parameters, collection period parameters, and upload method parameters;

[0152] The data receiving end receives the data collection rule configuration instruction, specifically for receiving the data collection rule configuration instruction corresponding to the data collection parameters;

[0153] Accordingly, both the data collection rule file and the data collection rule may include a collection object, and may also include at least one of a collection method, a collection period, and an upload method.

[0154] According to some embodiments of the present application, the collection object may include at least one of signal data, event data, fault data, and log data;

[0155] The event data may include an event and a first target signal data combination when the event occurs, and the fault data may include a fault and a second target signal data combination when the fault occurs.

[0156] According to some embodiments of the present application, the collection mode may include a periodic collection mode and / or a triggered collection mode. The triggered collection mode may include a trigger collection condition. The trigger collection condition may include at least one of an event occurrence condition, a fault occurrence condition, and a custom condition.

[0157] According to some embodiments of the present application, when the data acquisition rules include an acquisition method and the acquisition method includes a trigger acquisition method, the data acquisition device parses the data acquisition rule file to obtain the data acquisition rules, which are specifically used to cache the signal data corresponding to the acquisition object and the signal included in the acquisition method on the vehicle bus, and generate a signal cache list; a condition tree is generated according to the trigger acquisition conditions included in the trigger acquisition method; the data acquisition device collects the corresponding target data according to the data acquisition rules, and is specifically used to judge the signal data corresponding to the trigger acquisition conditions in the signal cache list according to the condition tree; if the judgment result is true, the corresponding target data is collected according to the acquisition object in the signal cache list.

[0158] According to some embodiments of the present application, when the data acquisition rule file includes an acquisition period, the data acquisition device caches the signal data on the in-vehicle bus corresponding to the signals included in the acquisition object and the acquisition method, and generates a signal cache list, which is specifically used to cache the signal data on the in-vehicle bus corresponding to the signals included in the acquisition object and the acquisition method according to the acquisition period, and generate a signal cache list.

[0159] According to some embodiments of the present application, when the data collection rule file includes an upload method, the data collection device uploads the collected data to the data receiving end, specifically for uploading the collected target data according to the upload method.

[0160] According to some embodiments of the present application, the uploading method may include real-time uploading and / or cache uploading.

[0161] According to some embodiments of the present application, the data receiving end generates a data collection rule file according to the data collection rule configuration instruction, specifically for generating the data collection rule file according to the data collection rule configuration instruction in a format pre-agreed with the data collection device.

[0162] According to some embodiments of the present application, the data receiving end is further configured to parse the received target data after receiving the target data uploaded by the data acquisition device.

[0163] For the description of the relevant parts of the data acquisition method, data receiving end, data acquisition device and data acquisition system provided in this application, please refer to the detailed description of the corresponding parts of the data acquisition method applied to the data receiving end provided in this application, and will not be repeated here.

[0164] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application, and they should all be included in the scope of the claims and specification of the present application. In particular, as long as there is no structural conflict, the various technical features mentioned in the various embodiments can be combined in any way. The present application is not limited to the specific embodiments disclosed herein, but includes all technical solutions that fall within the scope of the claims.

Claims

1. A data collection method, characterized in that: Applied to the data receiving end, including: Receiving a data collection rule configuration instruction, and generating a data collection rule file according to the data collection rule configuration instruction; The data collection rule file is sent to a data collection device in the vehicle, and the data collection device parses the data collection rule file and collects corresponding target data according to the data collection rule obtained by parsing; Receive the target data uploaded by the data acquisition device.

2. The data collection method according to claim 1, characterized in that: Before receiving the data collection rule configuration instruction, it also includes: Pre-configure data collection parameters; the data collection parameters include collection object parameters, and at least one of collection method parameters, collection period parameters and upload method parameters; Receive data collection rule configuration instructions, including: receiving the data collection rule configuration instruction corresponding to the data collection parameter; Correspondingly, the data collection rule file and the data collection rule both include a collection object, and both include at least one of a collection method, a collection period, and an upload method.

3. The data collection method according to claim 2, characterized in that: The collection object includes at least one of signal data, event data, fault data and log data; The event data includes an event and a first target signal data combination when the event occurs, and the fault data includes a fault and a second target signal data combination when the fault occurs.

4. The data collection method according to claim 3, characterized in that: The collection mode includes a periodic collection mode and / or a triggered collection mode. The triggered collection mode includes a triggered collection condition. The triggered collection condition includes at least one of a condition for occurrence of the event, a condition for occurrence of the fault, and a custom condition.

5. The data collection method according to claim 2, characterized in that: When the data collection rule includes an upload method, receiving the target data uploaded by the data collection device includes: Receive the target data uploaded by the data acquisition device according to the uploading method.

6. The data collection method according to claim 5, characterized in that: The uploading method includes real-time uploading and / or cache uploading.

7. The data collection method according to any one of claims 1 to 6, characterized in that: Generating a data collection rule file according to the data collection rule configuration instruction includes: The data collection rule file is generated according to the data collection rule configuration instruction in a format pre-agreed with the data collection device.

8. The data collection method according to any one of claims 1 to 6, characterized in that: After receiving the target data uploaded by the data acquisition device, the method further includes: Parse the received target data.

9. A data collection method, characterized in that: Applicable to data acquisition devices, including: Receiving a data collection rule file sent by a data receiving end; the data collection rule file is generated by the data receiving end according to the received data collection rule configuration instruction; Parsing the data collection rule file to obtain data collection rules; The corresponding target data is collected according to the data collection rules, and the collected target data is uploaded to the data receiving end.

10. The data collection method according to claim 9, characterized in that: The data collection rule file includes a collection object and at least one of a collection method, a collection period and an upload method.

11. The data collection method according to claim 10, characterized in that: When the data collection rule includes the collection method and the collection method includes a trigger collection method, the data collection rule file is parsed to obtain the data collection rule, including: Cache the signal data on the in-vehicle bus corresponding to the acquisition object and the signal included in the acquisition method to generate a signal cache list; Generate a condition tree according to the trigger collection conditions included in the trigger collection method; Collecting corresponding target data according to the data collection rules includes: Judging the signal data corresponding to the trigger collection condition in the signal buffer list according to the condition tree; If the judgment result is true, the corresponding target data is collected according to the signal data corresponding to the collection object in the signal cache list.

12. The data collection method according to claim 11, characterized in that: When the data collection rule file includes a collection period, signal data corresponding to the collection object and the signal included in the collection method on the in-vehicle bus is cached to generate a signal cache list, including: According to the collection period, signal data corresponding to the collection object and the signal included in the collection method on the in-vehicle bus is cached to generate the signal cache list.

13. The data collection method according to any one of claims 10 to 12, characterized in that: When the data collection rule file includes an upload method, uploading the collected target data to the data receiving end includes: Upload the collected target data according to the uploading method.

14. A data receiving end, characterized in that: include: A generating module, used for receiving a data collection rule configuration instruction, and generating a data collection rule file according to the data collection rule configuration instruction; A sending module, used for sending the data collection rule file to a data collection device in a vehicle, and the data collection device parses the data collection rule file and collects corresponding target data according to the data collection rule obtained by parsing; The module for receiving and collecting data is used to receive the target data uploaded by the data collection device.

15. A data acquisition device, characterized in that: include: A receiving rule file module is used to receive a data collection rule file sent by a data receiving end; The data collection rule file is generated by the data receiving end according to the received data collection rule configuration instruction; A file parsing module, used to parse the data collection rule file to obtain data collection rules; The collection and uploading module is used to collect the corresponding target data according to the data collection rules, and upload the collected target data to the data receiving end.

16. A data acquisition system, characterized in that: It includes a data receiving end and a data acquisition device located in a vehicle, wherein: The data receiving end is used to receive a data collection rule configuration instruction, generate a data collection rule file according to the data collection rule configuration instruction, and send the data collection rule file to the data collection device; The data acquisition device is used to parse the data acquisition rule file to obtain data acquisition rules; collect corresponding target data according to the data acquisition rules, and upload the collected target data to the data receiving end.

Images