Vehicle end data acquisition method and device, electronic equipment and medium

Through the distributed acquisition method of multi-domain controllers, the problem of limited data volume and speed in the vehicle-side data acquisition method is solved, efficient data acquisition and uploading is realized, and the acquisition frequency, vehicle-level data storage and cloud-based capabilities are improved. .

CN119094565APending Publication Date: 2024-12-06ZHEJIANG ZEEKR INTELLIGENT TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411261294.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-09
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing vehicle-side data acquisition methods are limited in data volume and speed due to the centralized acquisition of a single controller, which cannot meet the growth of data transmission demand in the big data era.

Method used

Using the multi-domain controller distributed acquisition method, by monitoring the acquisition tasks issued by the cloud, analyzing and assigning the target domain controller and acquisition strategy, triggering the data acquisition engine to collect and upload vehicle-side data according to the policy, and using multiple domain controllers to distribute it. Upload pressure to improve acquisition frequency and data storage efficiency.

Benefits of technology

It realizes efficient collection and upload of vehicle-side data, disperses the upload performance pressure, improves the acquisition frequency and vehicle-level data acquisition and storage and cloud access capabilities, and solves the problems of large data volume, high cost and long cycles.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094565A_ABST
    Figure CN119094565A_ABST
Patent Text Reader

Abstract

The invention provides a data acquisition method and device of a vehicle end, electronic equipment and a medium. The data acquisition method comprises the following steps: monitoring whether a first vehicle networking module receives an acquisition task issued by a cloud end or not; in response to the received collection task, the data collection management module is triggered to analyze the collection task to obtain a target domain controller and a collection strategy, and the target domain controller is at least one of the first controller and the second domain controller; calling a data acquisition management module, and sending an acquisition task to a target data acquisition engine in a target domain controller; and triggering the target data acquisition engine to acquire target vehicle end data according to the acquisition strategy and uploading the target vehicle end data to a cloud end through a target data exchange module in the target domain controller. And for each acquisition task, a matched target domain controller is confirmed from the plurality of domain controllers, target vehicle end data is acquired and uploaded based on the target domain controller, and each domain controller can realize cloud loading of the vehicle end data and disperse the cloud loading pressure of the vehicle end data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a vehicle-side data collection method, device, electronic equipment and medium. Background Art

[0002] With the development of the big data era, Internet of Vehicles technology has developed rapidly, data transmission needs have changed accordingly, and the demand for vehicle-side data has also increased.

[0003] The existing method for collecting vehicle-side data is usually to centrally collect and upload data through a single controller. Therefore, as the demand for data increases, the amount of data collected and the speed are limited.

[0004] Therefore, there is an urgent need for an efficient vehicle-side data collection method to solve the above technical problems. Summary of the invention

[0005] Based on this, it is necessary to provide a vehicle-side data collection method, device, electronic equipment and medium to address the above technical problems.

[0006] In a first aspect, the present application further provides a vehicle-side data collection method, wherein the vehicle-side includes a first vehicle connection module, a data collection management module, a first domain controller, and at least one second domain controller, wherein the method includes:

[0007] Monitor whether the first vehicle connection module receives the collection task sent by the cloud;

[0008] In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller;

[0009] Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller;

[0010] The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0011] In some embodiments, after calling the target data exchange module in the target domain controller to upload the target vehicle-side data to the cloud, the method further includes:

[0012] Monitor whether the data received successfully is received;

[0013] If the data reception success feedback is not received, the target vehicle-side data is marked with a data upload failure label and saved locally on the vehicle-side;

[0014] In response to detecting that the network is normal, the target data exchange module is called to upload the target vehicle-side data with the data upload failure label to the cloud.

[0015] In some embodiments, the collection strategy includes a periodic collection strategy, the periodic collection strategy includes a cloud upload frequency, a first data collection range, and a collection cycle, and the triggering of the target data collection engine to collect the target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes:

[0016] In response to parsing that the acquisition strategy is a periodic acquisition strategy, triggering the target data acquisition engine to acquire the first target vehicle-side data according to the original frequency,

[0017] Wherein, the first target vehicle-side data is the target vehicle-side data matching the first data collection range within the collection period;

[0018] The target data exchange module is called to upload the first target vehicle-side data to the cloud according to the cloud upload frequency.

[0019] In some embodiments, the collection strategy further includes an event collection strategy, the event collection strategy includes an event triggering condition, a second data collection range, and a collection duration, and the triggering of the target data collection engine to collect the target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes:

[0020] In response to parsing that the collection strategy is an event collection strategy, monitoring whether there is an event corresponding to the event triggering condition;

[0021] In response to monitoring an event corresponding to the event triggering condition, triggering the target data acquisition engine to collect the second target vehicle-side data according to the original frequency,

[0022] The second target vehicle-side data is the target vehicle-side data within the collection time period and matching the data collection range;

[0023] The target data exchange module is called to upload the second target vehicle-side data to the cloud according to the original frequency.

[0024] In some embodiments, the collection strategy further includes a historical data collection strategy, the historical data collection strategy includes a historical data time period and a third data collection range, and the triggering of the target data collection engine to collect the target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes:

[0025] In response to parsing that the acquisition strategy is a historical data acquisition strategy, triggering the target data acquisition engine to transfer the third target vehicle-side data to the target data exchange module,

[0026] Wherein, the third target vehicle-side data is the vehicle-side data collected within the historical time period and matching the third data collection range;

[0027] The target data exchange module is called to upload the third target vehicle-side data to the cloud.

[0028] In some embodiments, the vehicle terminal further includes a data acquisition client, and the method further includes:

[0029] Call the data collection client to collect the payload of the SOA signal in real time to generate and store SOA data;

[0030] In response to the collection task sent by the cloud being an SOA signal collection task, triggering the target data collection engine to read the SOA data in the data collection client;

[0031] Calling the target data acquisition engine to transfer the SOA data to the target data exchange module;

[0032] The target data exchange module is called to upload the SOA data to the cloud.

[0033] In a second aspect, the present application further provides a vehicle-side data collection device, which is used to implement the vehicle-side data collection method disclosed in the first aspect, and the device includes:

[0034] a first domain controller and at least one second domain controller;

[0035] The first domain controller includes a first data acquisition engine, a first data exchange module, a data acquisition management module and a first vehicle connection module;

[0036] The second domain controller includes a second data acquisition engine and a second data exchange module in communication with the second data acquisition engine;

[0037] The first data exchange module is in communication connection with the first data acquisition engine;

[0038] The first vehicle connection module and the second data acquisition engine are both in communication connection with the data acquisition management module;

[0039] The first data exchange module, the second data exchange module and the first vehicle connection module are all connected to the cloud for communication.

[0040] In a third aspect, the present application further provides a vehicle, comprising the vehicle-side data acquisition device disclosed in the second aspect.

[0041] In a fourth aspect, the present application further provides an electronic device, including a computer program, characterized in that when the computer program is executed by a processor, the steps of the method described below are implemented:

[0042] Monitor whether the first vehicle connection module receives the collection task sent by the cloud;

[0043] In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller;

[0044] Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller;

[0045] The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0046] In a fifth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program enables a computer to perform the following operations:

[0047] Monitor whether the first vehicle connection module receives the collection task sent by the cloud;

[0048] In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller;

[0049] Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller;

[0050] The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0051] The beneficial effects achieved by this application are:

[0052] The present application provides a vehicle-side data collection method, including monitoring whether the first vehicle connection module receives a collection task issued by the cloud; in response to the received collection task, triggering the data collection management module to parse the collection task to obtain the target domain controller and the collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller; calling the data collection management module to send the collection task to the target data collection engine in the target domain controller; triggering the target data collection engine to collect the target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller. For each collection task, the present application confirms a matching target domain controller from multiple domain controllers, and collects and uploads the target vehicle-side data based on the target domain controller, and each domain controller can realize the cloud upload of the vehicle-side data, disperse the upload performance pressure faced by the vehicle-side data on the cloud, increase the collection frequency, and further realize the whole vehicle-level data collection, storage and cloud upload. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0054] Figure 1 This is a flow chart of a vehicle-side data collection method provided in an embodiment of the present application;

[0055] Figure 2 It is a schematic diagram of a vehicle-side data acquisition device provided in an embodiment of the present application;

[0056] Figure 3 This is a schematic diagram of a vehicle-side time series database setting provided in an embodiment of the present application;

[0057] Figure 4 It is a schematic diagram of a cloud data collection device provided in an embodiment of the present application;

[0058] Figure 5 It is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0060] It should be understood that in the description of the present application, unless the context clearly requires otherwise, words such as "include", "comprises", and the like in the entire specification and claims should be interpreted as inclusive rather than exclusive or exhaustive; that is, the meaning of "including but not limited to".

[0061] It should also be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, "plurality" means two or more.

[0062] It should be noted that the terms "S1", "S2", etc. are only used for the purpose of describing the steps, and do not specifically refer to the order or sequence, nor are they used to limit the present application. They are only for the convenience of describing the method of the present application, and cannot be understood as indicating the order of the steps. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by the present application.

[0063] As the background technology shows, with the development of smart cars, the demand for data transmission is also changing rapidly. The demand for vehicle-side data by car companies is also increasing. The application scenarios of vehicle-side data are diversified, such as after-sales service, product development, quality assessment, user experience, etc. However, the existing methods for collecting vehicle-side data have problems such as small maximum data volume, high collection cost and long cycle.

[0064] Embodiment 1

[0065] The present application also provides a vehicle-side data collection method, which is applied to the vehicle-side, and the vehicle-side includes a first vehicle connection module, a data collection management module, a first domain controller, and at least one second domain controller. The data collection method disclosed in this embodiment is used to collect vehicle-side data and upload it to the cloud. Figure 1 The flowchart shown specifically includes:

[0066] S1. Monitor whether the first vehicle connection module receives a collection task issued by the cloud, and when monitoring the issued collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller.

[0067] Specifically, the cloud provides a web page, and users of the business department can configure collection tasks on the web page. After the collection task is configured, the cloud uses the second vehicle connection module to send it to the first vehicle connection module on the vehicle side, thereby realizing vehicle-cloud interaction. The method disclosed in the embodiment of the present application monitors whether the first vehicle connection module deployed on the vehicle side receives the collection task sent by the cloud, and triggers the data collection management module to parse the collection task to obtain the target domain controller and collection strategy. The above-mentioned collection task includes at least a target domain controller and a collection strategy, wherein the target domain controller is used to determine the specific target of the collection task, and the collection strategy is used to determine the data collection method specified by the collection task; the above-mentioned collection strategy specifically includes periodic collection strategy, event collection strategy and historical collection strategy, and these strategies are designed and configured by users on the cloud.

[0068] In addition, the data acquisition management module under the first domain controller also uses the first vehicle connection module to subscribe to the cloud configuration, and distributes the specific configuration goals to the data acquisition engines under the relevant domain controllers or keeps (the configuration of the data acquisition management module) for itself. If the configuration is the configuration of the data acquisition management module itself, after the data acquisition management module completes the configuration loading or update, it will feedback the configuration deployment results to the cloud through the interaction between the first vehicle connection module and the second vehicle connection module; if it is the configuration of other domain controllers, the data acquisition engines of other domain controllers need to report the configuration results to the data acquisition management module, and the data acquisition management module reports the corresponding configuration deployment results to the cloud.

[0069] S2. Call the data collection management module and send the collection task to the target data collection engine in the target domain controller.

[0070] After the data acquisition management module is used to parse the acquisition task, one or more domain controllers are selected from the first domain controller and the second domain controller according to the parsed target domain controller, and the selected one or more domain controllers are defined as the target domain controller. For ease of understanding, the data acquisition engine deployed in the target domain controller is the target data acquisition engine, and the data exchange module is the target data exchange module.

[0071] S3, triggering the target data collection engine to collect the target vehicle data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0072] Specifically, since the startup of the domain controller is generally slower than that of some simple components, it may cause the loss of some signal data that are started first. Therefore, the present application proposes to deploy data acquisition clients on some key business nodes to achieve the purpose of temporary caching of signal data, and the caching time can be flexibly defined according to the startup speed of the ECU; further, the above-mentioned target data acquisition engine can also control the data acquisition client according to the acquisition strategy to realize the collection of data on specific key business nodes.

[0073] Preferably, in a specific implementation scenario, the triggering target data collection engine collects the target vehicle-side data according to the collection strategy and uploads it to the cloud through the target data exchange module in the target domain controller, including:

[0074] In response to parsing that the collection strategy is a periodic collection strategy, the target data collection engine is triggered to collect the first target vehicle-side data according to the original frequency, wherein the first target vehicle-side data is the target vehicle-side data that matches the first data collection range within the collection period; the target data exchange module is called to upload the first target vehicle-side data to the cloud according to the cloud upload frequency.

[0075] Specifically, when the periodic collection strategy is configured in the cloud, the user configures the cloud upload frequency, collection period, and first data collection range when configuring the specific periodic collection strategy; the cloud upload frequency is the frequency of uploading the collected first target data to the cloud, the collection period is the period range of the collected vehicle-side data, and the first data collection range is the type of target vehicle-side data corresponding to the periodic collection strategy; the above original frequency is the original frequency of the vehicle-side data collected locally. The above periodic collection strategy is suitable for scenarios with low requirements for the frequency of cloud upload data, large data width, and stable and long-term data requirements.

[0076] Preferably, in a specific implementation scenario, the triggering target data collection engine collects the target vehicle-side data according to the collection strategy and uploads it to the cloud through the target data exchange module in the target domain controller, and also includes:

[0077] In response to parsing that the collection strategy is an event collection strategy, monitor whether there is an event corresponding to the event trigger condition; in response to monitoring the event corresponding to the event trigger condition, trigger the target data collection engine to collect the second target vehicle-side data at the original frequency, wherein the second target vehicle-side data is the target vehicle-side data within the collection duration that matches the data collection range; call the target data exchange module to upload the second target vehicle-side data to the cloud at the original frequency.

[0078] Specifically, when the event collection strategy is configured in the cloud, the user configures the event triggering condition, the collection duration, and the second data collection scope when configuring the specific event collection strategy; wherein, the event triggering condition is the event that triggers the target vehicle-side data collection, the collection duration is the duration of collecting vehicle-side data, and the second data collection scope is the type of target vehicle-side data collected by the event collection strategy. After parsing that the collection strategy is an event collection strategy, the vehicle side needs to monitor whether there are events corresponding to the event triggering condition. When an event corresponding to the event triggering condition is monitored, the target data collection engine is triggered to collect the second target vehicle-side data at the original frequency and upload the collected data to the cloud through the target data interaction module in real time; in addition, an event judgment model is constructed to determine the trigger for data collection. The above event judgment model can be implemented by the user uploading a specific algorithm in the modeling configuration center. The above event collection strategy is aimed at the data needs of scenarios with high frequency of cloud access and occasional events.

[0079] Preferably, in a specific implementation scenario, the triggering target data collection engine collects the target vehicle-side data according to the collection strategy and uploads it to the cloud through the target data exchange module in the target domain controller, and also includes:

[0080] In response to parsing that the collection strategy is a historical data collection strategy, the target data collection engine is triggered to transfer the third target vehicle-side data to the target data exchange module, wherein the third target vehicle-side data is the vehicle-side data collected within the historical time period and matches the third data collection range; the target data exchange module is called to upload the third target vehicle-side data to the cloud. Specifically, in order to realize data backup for a specific historical time period, the embodiment of the present application also proposes a historical data collection strategy, and when configuring the collection task in the cloud, the corresponding historical data time period and the third data collection range are configured, and the third data collection range is the type of target vehicle-side data collected by the historical data collection strategy.

[0081] Preferably, in a specific implementation scenario, after calling the target data exchange module in the target domain controller to upload the target vehicle-side data to the cloud, the above method also includes: monitoring whether the data reception success feedback generated by the cloud is received; if the data reception success feedback is not received, the target vehicle-side data is marked with a data upload failure label and saved locally on the vehicle side; in response to detecting that the network is normal, calling the target data exchange module to upload the target vehicle-side data with the data upload failure label to the cloud. If the local vehicle side does not receive the callback of successful cloud reception, it indicates that the target vehicle-side data collected in a weak network or no network environment failed to be uploaded to the cloud. At this time, the target vehicle-side data that failed to be uploaded is marked with a data upload failure label and reissued after the network is restored; the reissue mechanism is added to solve the problem of data loss that may be caused by network anomalies, and further solve the problem of data failure to be uploaded to the cloud.

[0082] Preferably, in a specific implementation scenario, the method further includes: calling a data acquisition client to collect the payload of a SOA (Service-Oriented Architecture) signal in real time to generate and store SOA data; in response to the collection task issued by the cloud being a SOA signal collection task, triggering the target data acquisition engine to read the SOA data in the data acquisition client; calling the target data acquisition engine to transfer the SOA data to the target data exchange module; calling the target data exchange module to upload the SOA data to the cloud. Specifically, the SOA service signals to be collected in each domain controller need to be integrated with a data acquisition client, and the signals sent or received are all passed through the data acquisition client, and the SOA signals are collected through the data acquisition client and forwarded to the cloud for storage; in this embodiment, the data acquisition client only records the payload part of the signal, which greatly reduces the amount of data; although the log can also be printed, the log is hard-coded in the code, and the log will not upload info-level data to the cloud at a certain frequency. The amount of data is too large, and it is pulled through the cloud when needed, which does not have real-time and flexibility. The real-time upload of SOA data is achieved, and only key information is uploaded, the data volume is small and convenient for cloud parsing.

[0083] In addition, the embodiment of the present application also proposes to implement vehicle-side edge computing, effectively filter accurate data to the cloud, and reduce cloud storage costs. Specifically, the algorithm script or configuration file sent from the cloud is sent to the edge computing engine through the data acquisition engine; the edge computing engine parses the algorithm script or configuration file and stores the parsed trigger conditions; the edge computing engine subscribes to the trigger condition signal to the data acquisition engine; when the signal parameter value received by the edge computing engine meets the trigger condition, the data acquisition engine is triggered to read the data to the cloud.

[0084] This application uses multiple domain controllers to collect and upload target vehicle-side data in a distributed manner, and matches the corresponding domain controller for each collection task to collect data, thereby dispersing the upload performance pressure faced by the vehicle-side data on the cloud, further improving the collection frequency, expanding the data collection scope (LIN / CAN / CANFD / ETH / LVDS / A2B and other bus signals, SOA (Service-Oriented Architecture) service signal data in each domain) and dimension (structured data and unstructured data), collecting higher-precision vehicle-side data, and realizing vehicle-level data collection, storage and cloud. In addition, this application can also use a custom TCP protocol for data transmission within the vehicle to solve problems such as data transmission loss, disorder, jump, delay, etc. in the vehicle. In addition, the vehicle side also adds a data retransmission function to solve the problem of data failure on the cloud.

[0085] Embodiment 2

[0086] The present application embodiment provides a vehicle-side data acquisition device, specifically, Figure 2 As shown, the data acquisition device 200 includes:

[0087] A first domain controller 210 and at least one second domain controller 220, wherein the number of the second domain controllers 220 matches the number of the business subsystems; the first domain controller 210 includes a first data acquisition engine 211, a first data exchange module 212, a data acquisition management module 213 and a first vehicle connection module 214; the second domain controller 220 includes a second data acquisition engine 221 and a second data exchange module 222 that is communicatively connected to the second data acquisition engine 221; the first data exchange module 213 is communicatively connected to the first data acquisition engine 211; the first vehicle connection module 214 and the second data acquisition engine 221 are both communicatively connected to the data acquisition management module 213; the first data exchange module 212, the second data exchange module 222 and the first vehicle connection module 214 are all communicatively connected to the cloud

[0088] In a specific embodiment, the first domain controller 210 can be an S32G microcontroller or any other high-performance automotive-grade microcontroller; the second domain controller 220 can be a domain controller used in a subsystem related to vehicle-side services such as an 8295 system and an Orin system, and its specific number is consistent with the number of specific subsystems. Among them, the first domain controller 210 is responsible for the signal collection, packaging, uploading and re-issuing storage of ECUs such as the vehicle body, chassis, and new energy; the second domain controller 220 is responsible for the signal collection, packaging, uploading and re-issuing storage sent and received by itself, and reduces the vehicle-side network load by collecting vehicle-side data nearby, while balancing performance. The first vehicle connection module 213 and the second vehicle connection module are vehicle abstraction layers, or vehicle-cloud integrated architecture modules. The connection between the vehicle-side and the cloud is realized through the connection between the first vehicle connection module 214 and the second vehicle connection module, and further realizes the cloud-side sending of collection tasks to the vehicle-side.

[0089] Among them, the data collection management module (Data Collect Manager) is deployed in the first domain controller 210, for example, it can be deployed under the A core subsystem of the S32G microcontroller, and there is only one running instance in the vehicle end during operation. The DataCollect Engine (data collection engine) is deployed in the first domain controller 210 and the second domain controller 220 at the same time. During operation, one instance runs under each domain controller. In order to facilitate distinction, the data collection engine deployed in the first domain controller 210 is defined as the first data collection engine 211, and the data collection engine deployed in the second domain controller 220 is defined as the second data collection engine 221 in this application. The data collection engine under each domain controller (including the first data collection engine under the first domain controller and the second data collection engine under the second domain controller) is connected to the data collection management module 213 in communication to realize the allocation and feedback of collection tasks. Furthermore, the data acquisition engine in each domain controller is communicatively connected to the data exchange module under the same domain controller. For example, the first data acquisition engine 211 in the first domain controller 210 is communicatively connected to the first data exchange module 212, and the second data acquisition engine 221 in the second domain controller is communicatively connected to the second data exchange module 222, so as to realize the uploading of the vehicle-side data collected by the data acquisition engine.

[0090] Preferably, in some implementation scenarios, the first domain controller 210 in the data collection device 200 further includes at least one first data collection client 215 that is communicatively connected to the first data collection engine 211, wherein the number of the first data collection client 215 matches the number of key business nodes in the first domain controller 210; the second domain controller 220 further includes at least one second data collection client 223 that is communicatively connected to the second data collection engine 221, wherein the number of the second data collection client 223 matches the number of key business nodes in the second domain controller 220. The first data collection client 215 and the second data collection client 223, i.e., Data Collect Client, are integrated in the form of a library by the application software (i.e., key business nodes) under the first domain controller 210 and the second domain controller 220. Multiple application software under each domain controller can integrate and use Data Collect Client according to business needs. There is only one Data Collect Client instance in each application software during operation. The specific setting of the key business node can be set by the user, and this application does not restrict it. Each data collection client interacts with the data collection engine under the same domain controller; the data collection client responds to the deployed collection tasks and further realizes the collection of vehicle-side data.

[0091] like Figure 3 As shown, in some implementation scenarios, in the vehicle-side data acquisition device 200 disclosed in the embodiment of the present application, the data acquisition engine under each domain controller can access the original data frame from software, bus and Ethernet, parse the data format and compress it, obtain the data items after compression and cache them in the vehicle-side time series database according to the time sequence of the compressed files, thereby solving the problems of disordered data storage and low query efficiency on the vehicle side and saving storage costs.

[0092] Embodiment 3

[0093] Corresponding to the above-mentioned embodiment 1 and embodiment 2, as Figure 4 As shown, the embodiment of the present application also provides a cloud data collection device 400, specifically comprising

[0094] The data storage platform 410 is used to receive the target vehicle-side data uploaded by the first data exchange module and / or the second data exchange module deployed in the vehicle-side. Specifically, the data storage platform 410 can be a storage platform composed of an object storage system (OSS, Object Storage Service), or can be composed of other storage systems, which is not limited in this application.

[0095] The data collection platform 420 is used to configure collection tasks, and analyze and store the target vehicle-side data transmitted by the data storage platform 410. Specifically, the data collection cloud platform 420 also includes a database 421 and a collection configuration center 422. Among them, the collection configuration center 422 provides multiple services such as user management, authority management, configuration management, and data management. Users of the business department need to register on the platform and be granted relevant permissions such as configuration creation / deployment / update, deployment approval, and data notification / viewing; the database 421 is used to store basic information (including users and permissions, configuration, and vehicle lists), data item configuration file deployment (with FOTA updates or direct cloud issuance), task issuance and update results, and collection task status.

[0096] Preferably, in some implementation scenarios, the above-mentioned cloud-based data acquisition device also includes a second vehicle-connected module 430, and the second vehicle-connected module 430 is used to send the acquisition tasks configured on the data acquisition cloud platform 420 to the first vehicle-connected module deployed in the vehicle.

[0097] The target vehicle-side data uploaded by the vehicle-side is stored in Kafka under the second vehicle-connected module 430 after passing through the data storage platform. The above-mentioned data collection platform 420 also includes a data analysis service module 423, which consumes the data uploaded by the vehicle-side from Kafka and classifies and records it (such as using a database to record data record information received by different tasks and different vehicles, including generation time, upload time, data content or data storage path, etc.), so that business personnel can retrieve and export data from the Web front-end page. The collection configuration center 422 also deploys the collection task configuration designed by the user to the specific vehicle-side with the help of the second vehicle-connected module 430, and the deployment results can also be obtained from the vehicle-side feedback with the help of the second vehicle-connected module 430.

[0098] In some implementation scenarios, the data collection platform 420 also includes a modeling configuration center 424 for configuring the event determination model.

[0099] Embodiment 4

[0100] Corresponding to all the above embodiments, the present application also provides a vehicle, including the vehicle-side data acquisition device disclosed in Embodiment 2, whose specific structure is consistent with the content disclosed in Embodiment 1, and the embodiments of the present application will not be repeated here.

[0101] Embodiment 5

[0102] Corresponding to all the above embodiments, an embodiment of the present application provides an electronic device, including: one or more processors; and a memory associated with the one or more processors, the memory is used to store program instructions, and when the program instructions are read and executed by the one or more processors, the following operations are performed:

[0103] Monitor whether the first vehicle connection module receives the collection task sent by the cloud;

[0104] In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller;

[0105] Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller;

[0106] The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0107] In some embodiments, when the program instructions are read and executed by one or more processors, the program instructions further perform the following operations:

[0108] Monitor whether the data received successfully is received;

[0109] If the data reception success feedback is not received, the target vehicle-side data is marked with a data upload failure label and saved locally on the vehicle-side;

[0110] In response to detecting that the network is normal, the target data exchange module is called to upload the target vehicle-side data with the data upload failure label to the cloud.

[0111] In some embodiments, when the program instructions are read and executed by one or more processors, the program instructions further perform the following operations:

[0112] In response to parsing that the acquisition strategy is a periodic acquisition strategy, triggering the target data acquisition engine to acquire the first target vehicle-side data according to the original frequency,

[0113] Wherein, the first target vehicle-side data is the target vehicle-side data matching the first data collection range within the collection period;

[0114] The target data exchange module is called to upload the first target vehicle-side data to the cloud according to the cloud upload frequency.

[0115] In some embodiments, when the program instructions are read and executed by one or more processors, the program instructions further perform the following operations:

[0116] In response to parsing that the collection strategy is an event collection strategy, monitoring whether there is an event corresponding to the event triggering condition;

[0117] In response to monitoring an event corresponding to the event triggering condition, triggering the target data acquisition engine to collect the second target vehicle-side data according to the original frequency,

[0118] The second target vehicle-side data is the target vehicle-side data within the collection time period and matching the data collection range;

[0119] The target data exchange module is called to upload the second target vehicle-side data to the cloud according to the original frequency.

[0120] In some embodiments, when the program instructions are read and executed by one or more processors, the program instructions further perform the following operations:

[0121] In response to parsing that the acquisition strategy is a historical data acquisition strategy, triggering the target data acquisition engine to transfer the third target vehicle-side data to the target data exchange module,

[0122] Wherein, the third target vehicle-side data is the vehicle-side data collected within the historical time period and matching the third data collection range;

[0123] The target data exchange module is called to upload the third target vehicle-side data to the cloud.

[0124] In some embodiments, when the program instructions are read and executed by one or more processors, the program instructions further perform the following operations:

[0125] Call the data collection client to collect the payload of the SOA signal in real time to generate and store SOA data;

[0126] In response to the collection task sent by the cloud being an SOA signal collection task, triggering the target data collection engine to read the SOA data in the data collection client;

[0127] Calling the target data acquisition engine to transfer the SOA data to the target data exchange module;

[0128] The target data exchange module is called to upload the SOA data to the cloud.

[0129] The target data exchange module in the target domain controller is uploaded to the cloud.

[0130] in, Figure 5 The architecture of the electronic device is shown as an example, which may include a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, and a memory 520. The processor 510, the video display adapter 511, the disk drive 512, the input / output interface 513, the network interface 514, and the memory 520 may be communicatively connected via a bus 530.

[0131] Among them, the processor 510 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided in this application.

[0132] The memory 520 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 520 can store an operating system 521 for controlling the execution of the electronic device 500, and a basic input and output system (BIOS) 522 for controlling the low-level operations of the electronic device 500. In addition, a web browser 523, a data storage management system 524, and an icon font processing system 525, etc. can also be stored. The above-mentioned icon font processing system 525 can be an application program that specifically implements the operations of the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided in the present application is implemented by software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510.

[0133] The input / output interface 513 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0134] The network interface 514 is used to connect to a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0135] The bus 530 comprises a pathway for transmitting information between the various components of the device (eg, the processor 510, the video display adapter 511, the disk drive 512, the input / output interface 513, the network interface 514, and the memory 520).

[0136] In addition, the electronic device 500 can also obtain information on specific collection conditions from the virtual resource object collection condition information database for use in condition judgment, etc.

[0137] It should be noted that, although the above device only shows a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, a memory 520, a bus 530, etc., in the specific implementation process, the device may also include other components necessary for normal execution. In addition, it can be understood by those skilled in the art that the above device may also only include components necessary for implementing the solution of the present application, and does not necessarily include all the components shown in the figure.

[0138] It can be seen from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., including several instructions for a computer device (which can be a personal computer, a cloud service end, or a network device, etc.) to execute the methods of various embodiments of the present application or certain parts of the embodiments.

[0139] Embodiment 6

[0140] Corresponding to all the above embodiments, the embodiments of the present application further provide a computer-readable storage medium, characterized in that it stores a computer program, and the computer program enables a computer to perform the following operations:

[0141] Monitor whether the first vehicle connection module receives the collection task sent by the cloud;

[0142] In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller;

[0143] Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller;

[0144] The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

[0145] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0146] The above are only preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A vehicle-side data collection method, the vehicle-side comprising a first vehicle connection module, a data collection management module, a first domain controller and at least one second domain controller, characterized in that: The method comprises: Monitor whether the first vehicle connection module receives the collection task sent by the cloud; In response to the received collection task, trigger the data collection management module to parse the collection task to obtain a target domain controller and a collection strategy, wherein the target domain controller is at least one of the first controller and the second domain controller; Calling a data collection management module to send the collection task to a target data collection engine in the target domain controller; The target data acquisition engine is triggered to collect the target vehicle-side data according to the acquisition strategy and upload it to the cloud through the target data exchange module in the target domain controller.

2. The method according to claim 1, characterized in that After calling the target data exchange module in the target domain controller to upload the target vehicle-side data to the cloud, the method further includes: Monitor whether the data received successfully is received; If the data reception success feedback is not received, the target vehicle-side data is marked with a data upload failure label and saved locally on the vehicle-side; In response to detecting that the network is normal, the target data exchange module is called to upload the target vehicle-side data with the data upload failure label to the cloud.

3. The method according to claim 2, characterized in that The collection strategy includes a periodic collection strategy, and the periodic collection strategy includes a cloud upload frequency, a first data collection range, and a collection cycle. The triggering of the target data collection engine to collect target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes: In response to parsing that the acquisition strategy is a periodic acquisition strategy, triggering the target data acquisition engine to acquire the first target vehicle-side data according to the original frequency, Wherein, the first target vehicle-side data is the target vehicle-side data matching the first data collection range within the collection period; The target data exchange module is called to upload the first target vehicle-side data to the cloud according to the cloud upload frequency.

4. The method according to claim 3, characterized in that The collection strategy also includes an event collection strategy, which includes an event triggering condition, a second data collection range, and a collection duration. The triggering of the target data collection engine to collect the target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes: In response to parsing that the collection strategy is an event collection strategy, monitoring whether there is an event corresponding to the event triggering condition; In response to monitoring an event corresponding to the event triggering condition, triggering the target data acquisition engine to collect the second target vehicle-side data according to the original frequency, The second target vehicle-side data is the target vehicle-side data within the collection time period and matching the data collection range; The target data exchange module is called to upload the second target vehicle-side data to the cloud according to the original frequency.

5. The method according to claim 4, characterized in that The collection strategy also includes a historical data collection strategy, which includes a historical data time period and a third data collection range, and the triggering of the target data collection engine to collect target vehicle-side data according to the collection strategy and upload it to the cloud through the target data exchange module in the target domain controller includes: In response to parsing that the acquisition strategy is a historical data acquisition strategy, triggering the target data acquisition engine to transfer the third target vehicle-side data to the target data exchange module, Wherein, the third target vehicle-side data is the vehicle-side data collected within the historical time period and matching the third data collection range; The target data exchange module is called to upload the third target vehicle-side data to the cloud.

6. The method according to any one of claims 1 to 5, characterized in that: The vehicle end also includes a data acquisition client, and the method further includes: Call the data collection client to collect the payload of the SOA signal in real time to generate and store SOA data; In response to the collection task sent by the cloud being an SOA signal collection task, triggering the target data collection engine to read the SOA data in the data collection client; Calling the target data acquisition engine to transfer the SOA data to the target data exchange module; The target data exchange module is called to upload the SOA data to the cloud.

7. A vehicle-side data acquisition device, implementing the method according to any one of claims 1 to 6, characterized in that: The device comprises: a first domain controller and at least one second domain controller; The first domain controller includes a first data acquisition engine, a first data exchange module, a data acquisition management module and a first vehicle connection module; Wherein, the first data exchange module is connected to the first data acquisition engine for communication, and the first vehicle connection module is connected to the data acquisition management module for communication; Wherein, the first vehicle connection module is communicatively connected to the second vehicle connection module deployed in the cloud, and the first data exchange module is communicatively connected to the cloud; The second domain controller includes a second data acquisition engine and a second data exchange module in communication with the second data acquisition engine; The second data acquisition engine is communicatively connected to the data acquisition management module, and the second data exchange module is communicatively connected to the cloud.

8. A vehicle, characterized in that: The vehicle includes the vehicle-side data acquisition device described in claim 7.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; And a memory associated with the one or more processors, the memory is used to store program instructions, and when the program instructions are read and executed by the one or more processors, the method according to any one of claims 1-6 is executed.

10. A computer-readable storage medium, characterized in that: The computer program stores a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 6.