Data collection system

Abstract

Provided is a data collection system that includes a vehicle having a vehicle control device, and a cloud, said vehicle control device having a trigger detection unit that monitors the occurrence of a start trigger and an end trigger and a data collection unit that collects collection data, wherein: the trigger detection unit has a start trigger monitoring algorithm for each start trigger condition that defines a start trigger, and has an end trigger monitoring algorithm for each end trigger condition that defines an end trigger; the data collection unit has a collection algorithm; the cloud transmits, to the vehicle, collection conditions expressed as a state machine that includes, as states, a start trigger monitoring state representing the monitoring of a start trigger and a data collection state representing the collection of collection data and the monitoring of an end trigger, and that defines state transitions using the start trigger conditions and the end trigger conditions; and the vehicle control device sets the trigger detection unit and the data collection unit so that collection data can be collected in accordance with the state machine. The state machine includes branches to different data collection states.

Description

Data Collection System

[0001] The present invention relates to a data collection system for collecting data from a vehicle.

[0002] A data collection device that collects vehicle-related data from an on-board device installed in a vehicle is known (see, for example, Patent Document 1). By using the technology described in Patent Document 1, information can be efficiently collected in response to changes in the vehicle's condition.

[0003] Japanese Patent Application Laid-Open No. 2020-71828

[0004] The data collection device described in Patent Document 1 distributes collection conditions in a file format, including various parameters such as the target vehicle, data type, collection trigger conditions, and collection period, in response to changes in vehicle-related data.

[0005] In the technology described in Patent Document 1, new collection conditions are transmitted after the data collection device detects a change in data, so there is a possibility that data that should be collected will not be collected by the time the vehicle receives the collection conditions. Furthermore, the technology does not take into consideration the combination of different types of data changes.

[0006] A representative example of the invention disclosed in the present application is as follows: That is, a data collection system including a vehicle having a vehicle control device and a cloud, the vehicle control device including a trigger detection unit that monitors the occurrence of a start trigger that starts collection of collected data to be collected and the occurrence of an end trigger that ends collection of the collected data, and a data collection unit that collects the collected data based on data collection conditions, the trigger detection unit including a start trigger monitoring algorithm for monitoring the occurrence of the start trigger for each start trigger condition that defines the start trigger, and an end trigger monitoring algorithm for monitoring the occurrence of the end trigger for each end trigger condition that defines the end trigger, the data collection unit including at least one collection algorithm for collecting the collected data based on the data collection conditions, the start trigger condition for each of the plurality of start trigger monitoring algorithms is different and the end trigger condition for each of the plurality of end trigger monitoring algorithms is different; the cloud transmits to the vehicle collection conditions for controlling the collection of the collected data, the collection conditions being expressed as a state machine that includes, as states, a start trigger monitoring state that represents monitoring of the start trigger and a data collection state that represents collection of the collected data and monitoring of the end trigger, and that defines transitions of the states by the start trigger condition and the end trigger condition; the vehicle control device sets the trigger detection unit and the data collection unit so that the collected data can be collected in accordance with the state machine; and the state machine transmitted by the cloud includes branches to the different data collection states.

[0007] According to one aspect of the present invention, a vehicle control device can collect data that can be used in various situations without communicating with an external device. Problems, configurations, and effects other than those described above will become clear from the following description of the embodiment.

[0008] 1 is a diagram illustrating an example of the configuration of a data collection system according to a first embodiment; FIG. 2 is a diagram illustrating an example of the functional configuration of a cloud according to the first embodiment; FIG. 3 is a diagram illustrating an example of the functional configuration of an ECU according to the first embodiment; FIG. 4 is a flowchart illustrating an example of a process executed by the cloud according to the first embodiment; FIG. 5 is a flowchart illustrating an example of a control process of data collection executed by the ECU according to the first embodiment; FIG. 6 is a diagram illustrating an example of collection conditions (state machine) transmitted from the cloud according to the first embodiment; FIG. 7 is a diagram illustrating an example of a setting method for a trigger detection unit and a data collection unit according to the first embodiment; FIG. 8 is a diagram illustrating an example of a setting method for a trigger detection unit and a data collection unit according to the first embodiment; FIG. 9 is a diagram illustrating an example of collection conditions (state machine) transmitted from the cloud according to the first embodiment; FIG. 10 is a diagram illustrating an example of a setting method for a trigger detection unit and a data collection unit according to the first embodiment; FIG. 10 is a diagram illustrating an example of a setting method for a trigger detection unit and a data collection unit according to a first embodiment. FIG. 11 is a diagram illustrating an example of a functional configuration of a cloud according to a second embodiment. FIG. 12 is a flowchart illustrating an example of a process executed by the cloud according to the second embodiment. FIG. 13 is a diagram illustrating an example of a functional configuration of an ECU according to a third embodiment. FIG. 14 is a diagram illustrating an example of a functional configuration of an ECU according to a fourth embodiment. FIG. 15 is a diagram illustrating an example of a functional configuration of an ECU according to a fifth embodiment.

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be changed within the scope of the idea or purpose of the present invention.

[0010] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0011] FIG. 1 is a diagram illustrating an example of the configuration of a data collection system according to a first embodiment.

[0012] The data collection system 10 is composed of a vehicle 100 and a cloud 101. The vehicle 100 and the cloud 101 are connected via a wireless communication system. The system may be configured such that the vehicle 100 is connected to multiple clouds 101. Alternatively, the system may be configured such that multiple vehicles 100 are connected to one or multiple clouds 101.

[0013] The cloud 101 is composed of a plurality of computers. The vehicle 100 includes a sensor 110 and a vehicle control device (ECU: Electronic Control Unit) 111. The sensor 110 and the ECU 111 are connected using a high-speed communication protocol such as Ethernet (registered trademark, the same applies hereinafter).

[0014] The sensors 110 are, for example, cameras and LiDAR (Light Detecting and Ranging) that measure images and shapes, sensors that measure the surrounding environment such as temperature, and sensors that measure driving conditions such as speed and acceleration. In the following description, data output by the sensors 110 will be referred to as sensor data. Note that the types and number of sensors 110 mounted on the vehicle 100 are not limited.

[0015] The ECU 111 is, for example, a microcomputer having a central processing unit (CPU), a graphics processing unit (GPU), a read-only memory (ROM), a random access memory (RAM), and a communication interface (not shown).

[0016] The number of sensors 110 and ECUs 111 mounted on the vehicle 100 is not limited to one. For example, the number of sensors 110 and ECUs 111 may be two or more.

[0017] FIG. 2 is a diagram illustrating an example of the functional configuration of the cloud 101 according to the first embodiment.

[0018] The cloud 101 includes a receiving unit 201, a transmitting unit 202, a storage unit 203, and a UI (User Interaction) 204. The receiving unit 201, the transmitting unit 202, the storage unit 203, and the UI 204 are realized using the computational resources of the cloud 101.

[0019] 2, the cloud 101 has one functional unit, but this is not limiting. For example, the cloud 101 may have multiple storage units 203.

[0020] The receiving unit 201 receives data from an external device or system via a network. The transmitting unit 202 transmits data to an external device or system via a network. The memory unit 203 stores various data. For example, the memory unit 203 stores data and collection conditions collected by the vehicle 100. In the following description, the data collected by the vehicle 100 will be referred to as collected data. The UI 204 provides an interface for managing the cloud 101 and setting collection conditions, etc. Note that the configuration and implementation method of the interface are not limited.

[0021] The collection conditions in this embodiment include conditions regarding the type of data to be collected (type conditions), conditions defining the start trigger for data collection (start trigger conditions), conditions defining the end trigger for data collection (end trigger conditions), and the collection period.

[0022] In this embodiment, the receiving unit 201 receives collected data from the vehicle 100 and stores it in the storage unit 203. The UI 204 stores collection conditions set by the user in the storage unit 203. The transmitting unit 202 transmits the collection conditions to the vehicle 100.

[0023] Possible methods for managing data in the storage unit 203 include a method of centrally managing collected data from all vehicles 100, a method of classifying and managing data by vehicle 100 or by type of data, etc. The receiving unit 201 and the transmitting unit 202 can set a control method for transmitting and receiving data depending on the manufacturer, type, and driving area of ​​the vehicle 100, etc.

[0024] FIG. 3 is a diagram illustrating an example of a functional configuration of the ECU 111 according to the first embodiment.

[0025] The ECU 111 has a sensor receiving unit 301, a control unit 302, a verification unit 303, a memory unit 304, a trigger detection unit 305, a data collection unit 306, a data addition unit 307, a transmission determination unit 308, a transmission / reception unit 309, a collection condition memory unit 310, a collection condition management unit 311, and a vehicle information detection unit 312.

[0026] The storage unit 304 stores various data. The storage unit 304 has a capacity and an overwrite rule set so that it can store data for a certain period of time in order to acquire data generated before collection begins. The transmission / reception unit 309 receives data from an external device or system via the network, and transmits data to an external device or system via the network.

[0027] The sensor receiving unit 301 receives sensor data from the sensor 110. The sensor receiving unit 301 receives, for example, an image of the surroundings of the vehicle 100 as sensor data.

[0028] The control unit 302 uses the sensor data to generate and output control information for controlling actuators (not shown) and other components. The control information generated by the control unit 302 can realize, for example, autonomous driving. The control unit 302 stores the control information in the storage unit 304.

[0029] The verification unit 303 verifies the sensor data and stores it in the storage unit 304. Note that the ECU 111 does not necessarily have to include the verification unit 303. In this case, the control unit 302 stores the sensor data in the storage unit 304.

[0030] The trigger detection unit 305 monitors the occurrence of a trigger based on the start trigger condition and the end trigger condition, based on the collection condition and the data stored in the storage unit 304. The trigger detection unit 305 outputs data related to the detected trigger to the data collection unit 306 and the data addition unit 307.

[0031] The trigger detection unit 305 of this embodiment implements multiple monitoring algorithms (start trigger monitoring algorithms) that monitor the occurrence of a start trigger defined in a start trigger condition. The trigger detection unit 305 of this embodiment also implements multiple monitoring algorithms (end trigger monitoring algorithms) that monitor the occurrence of an end trigger defined in an end trigger condition. The monitoring algorithms can be implemented as software or hardware. The collection condition management unit 311 sets the operation control of the monitoring algorithms.

[0032] The data collection unit 306 collects data (collected data) based on the collection conditions and outputs the collected data to the data addition unit 307.

[0033] The data collection unit 306 of this embodiment implements at least one collection algorithm that realizes collection of data corresponding to the data type defined by the type condition. The collection algorithm can be implemented as software or hardware. The operation control of the collection algorithm is set by the collection condition management unit 311. In this embodiment, the collection cycle is set as a parameter of the collection algorithm.

[0034] The data collection unit 306 acquires data that matches the type condition from the data stored in the storage unit 304 in accordance with a collection period, and stores the acquired data in the storage unit 304. The data collection unit 306 may also store metadata of the acquired data in the storage unit 304.

[0035] The data addition unit 307 adds data to the collected data as necessary. For example, the data addition unit 307 adds data related to the detected trigger and vehicle information to the collected data. In the following description, the data added by the data addition unit 307 will be referred to as additional data. The data addition unit 307 stores the collected data to which the additional data has been added in the storage unit 304. Note that the additional data may be added to the collected data itself, or may be added to the name or tag information of the data.

[0036] The transmission determination unit 308 monitors the timing of transmission of collected data, and when the transmission timing is detected, transmits the collected data to the cloud 101 via the transmission / reception unit 309. For example, the transmission determination unit 308 checks the communication bandwidth, and transmits the collected data when there is sufficient communication bandwidth.

[0037] The collection condition storage unit 310 stores the collection conditions received from the cloud 101 via the transmission / reception unit 309. The collection condition storage unit 310 and the storage unit 304 may be realized as a single storage unit.

[0038] The collection condition management unit 311 sets operational control of the trigger detection unit 305 and the data collection unit 306 based on the collection conditions.

[0039] The vehicle information detection unit 312 acquires vehicle information. The vehicle information includes, for example, the type of the connected sensor 110, the version of the driving control software that realizes the control unit 302, and specification difference information such as the type of algorithm implemented in the trigger detection unit 305 and the data collection unit 306. The above-mentioned information is useful for setting collection conditions.

[0040] It should be noted that the ECU 111 is assumed to be an AD (Autonomous Driving) / ADAS (Advanced Driver Assistance System)-ECU that controls autonomous driving, but similar functions may be realized using other ECUs such as a Central-ECU or a Zone-ECU.

[0041] Note that functions may be distributed among multiple ECUs. For example, a combination of an ECU equipped with a data collection function and an ECU equipped with a trigger monitoring function may be considered. In this case, the ECUs may be connected to each other so that they can communicate with each other. Alternatively, an ECU dedicated to data collection may be installed.

[0042] FIG. 4 is a flowchart illustrating an example of processing executed by the cloud 101 according to the first embodiment.

[0043] The UI 204 of the cloud 101 accepts collection conditions set by the user (step S401).

[0044] In this embodiment, the collection conditions are set as a state machine that defines the transitions between the monitoring state and the collection state. The state transitions are specified by the collection trigger conditions (start trigger condition and end trigger condition). The collection state is specified by the data type and collection period.

[0045] The UI 204 of the cloud 101 converts the data format of the collection conditions and stores the data in the storage unit 203 (step S402). The data format may be changed depending on the vehicle 100.

[0046] The transmission unit 202 of the cloud 101 transmits the collection conditions stored in the storage unit 203 to the vehicle 100 (step S403). The timing of transmitting the collection conditions is not limited. For example, the transmission unit 202 checks the network bandwidth and transmits the collection conditions when there is sufficient bandwidth. Furthermore, the transmission unit 202 transmits the collection conditions when a transmission request is received from the vehicle 100.

[0047] 5 is a flowchart illustrating an example of a control process for data collection executed by the ECU 111 according to the first embodiment. It is assumed here that collection conditions are stored in the collection condition storage unit 310.

[0048] The collection condition management unit 311 of the ECU 111 acquires the collection conditions from the collection condition storage unit 310 when the ECU 111 is started (step S501).

[0049] The timing for acquiring the collection conditions is merely an example and is not limited to this. For example, when new collection conditions are received while the vehicle 100 is traveling, the collection condition storage unit 310 stores the new collection conditions, and the collection condition management unit 311 acquires the collection conditions during a period when data collection is not required, such as when the vehicle is parked or stopped.

[0050] The collection condition management unit 311 of the ECU 111 sets the operation control of the trigger detection unit 305 and the data collection unit 306 based on the state machine representing the collection conditions (step S502). The operation control setting means setting the ON / OFF of the monitoring algorithm, the ON / OFF of the collection algorithm, the call relationship between the monitoring algorithm and the collection algorithm, and the parameters used by each algorithm. Note that the processing of step S502 does not update the algorithms themselves.

[0051] The trigger detection unit 305 of the ECU 111 starts monitoring the collection triggers (start trigger and end trigger) based on the monitoring algorithm corresponding to the set start trigger condition and end trigger condition (step S503).

[0052] The trigger detection unit 305 of the ECU 111 determines whether to start data collection based on the monitoring result regarding the start trigger (step S504).

[0053] If data collection is not started, the trigger detection unit 305 of the ECU 111 continues to monitor the collection trigger.

[0054] When data collection is started, the data collection unit 306 of the ECU 111 collects data based on a collection algorithm corresponding to the set type condition (step S505).

[0055] The trigger detection unit 305 of the ECU 111 determines whether or not to end the data collection based on the monitoring result regarding the end trigger (step S506).

[0056] If the data collection is not to be ended, the data collection unit 306 of the ECU 111 continues to collect data.

[0057] If data collection is to be ended, the data collection unit 306 of the ECU 111 ends data collection. Thereafter, the trigger detection unit 305 of the ECU 111 determines whether to end monitoring of the collection trigger (step S507). For example, when the vehicle 100 is stopped or parked, or the engine is stopped, or when a stop instruction is received, the trigger detection unit 305 of the ECU 111 ends monitoring of the collection trigger.

[0058] If the monitoring of the collection trigger is not terminated, the trigger detection unit 305 of the ECU 111 continues to monitor the collection trigger.

[0059] Next, the state machine and the setting of the ECU 111 based on the collection trigger conditions and the data collection conditions will be described.

[0060] 6, 9, 11, 13A, 13B, and 15 are diagrams illustrating examples of collection conditions (state machines) transmitted from the cloud 101 according to the first embodiment. 7, 8, 10, 12, 14, and 16 are diagrams illustrating examples of setting methods for the trigger detection unit 305 and the data collection unit 306 according to the first embodiment.

[0061] The user inputs, via the UI 204 of the cloud 101, a state machine 600 in which "Trigger02.Start" is set as the start trigger condition, "Trigger11.End" is set as the end trigger condition, and "Data03" is set as the type condition.

[0062] The states of the state machine include a "start trigger monitoring" state that monitors the occurrence of a start trigger, and a "data collection" state that collects data and monitors the occurrence of an end trigger. The start trigger condition and the end trigger condition are set as state transition conditions.

[0063] Here, the type condition is a condition that specifies the type of data to be collected, such as camera data, LiDAR data, map information, speed history information, object detection information, driving trajectory information, etc. The start trigger condition and end trigger condition are trigger conditions that specify the timing and period of collection. For example, they can be defined as a determination process based on the results of comparison of surrounding information, road information, driving information, etc. with the information itself or numerical parameters, and can be expressed using equal and inequality expressions, such as "road currently being driven = expressway" or "speed > 50 km / h."

[0064] In addition to the transition conditions of the state machine, by setting parameters for determining the conditions, the transition conditions can be used in a general purpose manner. As a specific example, when the verification unit 303 is equipped with a behavior prediction AI and is made to evaluate the trajectory prediction of other vehicles, the start trigger condition can be "difference between actual measurement and prediction > threshold", the end trigger condition can be "30 seconds before and after the occurrence of the start trigger", and the type conditions can be "actually measured values ​​of the behavior trajectories of other vehicles and actual vehicles" and "predicted values ​​of the behavior trajectories of other vehicles".

[0065] 7, the trigger detection unit 305 has a plurality of start trigger monitoring algorithms and a plurality of end trigger monitoring algorithms, and the data collection unit 306 has a plurality of collection algorithms.

[0066] Based on the state machine 600, the collection condition management unit 311 sets the algorithms of the trigger detection unit 305 and the data collection unit 306 so that when the start trigger condition "Trigger02.Start" is met, data is collected according to the type condition "Data03", and when the end trigger condition "Trigger11.End" is met, data collection is terminated.

[0067] In FIG. 7, for ease of explanation, the state machine-based settings are expressed as connections between a start trigger monitoring algorithm, an end trigger monitoring algorithm, and a collection algorithm, but the setting method is not limited to hardwired connections.

[0068] In Fig. 7, the trigger detection unit 305 inputs input data to all supervisory algorithms, performs calculations for each supervisory algorithm, and controls the state machine to use only the output of the supervisory algorithm specified by the state machine. In this case, calculations for unused supervisory algorithms are also performed, resulting in waste of computational resources and power. Therefore, it is possible to set the input to the supervisory algorithms to be limited, as shown in Fig. 8.

[0069] As shown in Fig. 9, for a state machine 900 including a state transition in which a plurality of start trigger conditions are combined with an AND condition, the setting shown in Fig. 10 is possible. For a state machine 1100 that realizes time-series processing as shown in Fig. 11, the setting shown in Fig. 12 is possible. In the case in which a plurality of state machines 1300, 1301 as shown in Fig. 13A and Fig. 13B are combined with an OR condition, the setting shown in Fig. 14 is possible.

[0070] In particular, the state machine 1100 shown in Fig. 11 is one of the complex state machines that is difficult to realize by simple switching alone. As a specific example of the state machine shown in Fig. 11, by defining trigger conditions such as "another vehicle is traveling in the lane next to the host vehicle," "another vehicle has moved into the host vehicle's lane," and "another vehicle is traveling in the same lane as the host vehicle" in chronological order, it is possible to detect the occurrence of anticipated scenes.

[0071] With conventional technology, in order to achieve the above-mentioned scene control, it is necessary to develop and combine individual monitoring algorithms, such as "cut-in," according to the expected scene. Furthermore, operation must be verified before implementation.

[0072] On the other hand, in the first embodiment, a general-purpose algorithm is implemented in advance, and the algorithm is set using a state machine, thereby enabling support for various scenarios such as conditional branching, time series, etc. In particular, by generating a state machine including branches to different data collection states, the ECU 111 does not need to communicate with the cloud 101 to switch the control of data collection, and therefore can collect all data to be collected.

[0073] The cloud 101 may transmit, along with the verified new algorithm, collection conditions including conditions related to the algorithm. The state machine 1500 shown in FIG. 15 includes a new start trigger condition "Trigger21.Start." As shown in FIG. 16, a monitoring algorithm corresponding to the new start trigger condition "Trigger21.Start" is added. Since it is only necessary to verify the new algorithm, the cost required for implementation can be reduced. In this way, the implementation of the new algorithm and the setting based on the state machine can be realized.

[0074] The cloud 101 may not only add algorithms but also update the algorithms.

[0075] By pre-installing various algorithms in the ECU 111 and combining the algorithms based on a state machine, data collection that can be adapted to various scenarios can be realized without communicating with the cloud 101. By changing the state machine, various data can be collected. Therefore, the implementation cost of data collection can be reduced.

[0076] In the second embodiment, the collection conditions are evaluated by a user who operates the cloud 101. The second embodiment will be described below, focusing on the differences from the first embodiment.

[0077] 17 is a diagram illustrating an example of the functional configuration of the cloud 101 according to the second embodiment. In the second embodiment, the UI 204 provides an interface for evaluating the collection conditions.

[0078] The user uses the interface provided by the UI 204 to search for collected data collected based on the collection conditions to be evaluated, and evaluates the collection conditions using the searched collected data. For example, the number and periodicity of collected data, the validity of the collected data itself, the validity of the collection period, and the validity of the data to be collected are evaluated.

[0079] The user may evaluate the collection conditions by referring not only to the collected data but also to the results of monitoring the collection trigger and additional data such as vehicle information added to the collected data. For example, it is conceivable to evaluate the collection conditions based on the differences in the specifications of the connected devices and the installed software.

[0080] Evaluation rules may be set in advance, and the cloud 101 may automatically evaluate the collection conditions based on the evaluation rules. In this case, the collection condition evaluation function may be built into the UI 204 or may be provided separately. The timing for evaluating the data may be periodic or after the collected data is received.

[0081] In the following description, it is assumed that the cloud 101 has an evaluation function. Fig. 18 is a flowchart illustrating an example of processing executed by the cloud 101 according to the second embodiment.

[0082] The evaluation function of the cloud 101 evaluates the collection conditions (step S1801), and updates the collection conditions based on the evaluation results (step S1802).

[0083] For example, if the collection period is not appropriate, the evaluation function updates the collection period based on a ratio calculated from the number of collected data and a threshold. The method for updating the collection conditions is not limited to the above. By defining update rules in advance, transition conditions, monitoring conditions, collection conditions, etc. can be updated. This makes it possible to obtain desired collected data, reduce data capacity and transfer volume, and resolve data shortages, etc.

[0084] The evaluation function of the cloud 101 converts the data format of the collection conditions and stores the data in the storage unit 203 (step S1803). The data format may be changed depending on the vehicle 100.

[0085] The transmission unit 202 of the cloud 101 transmits the collection conditions stored in the storage unit 203 to the vehicle 100 (step S1804). Note that the collection conditions may be transmitted either while the ECU 111 is collecting the collected data or after the collection.

[0086] By evaluating the collection conditions and reviewing them based on the evaluation results, the collection conditions can be optimized.

[0087] In the third embodiment, the collection conditions are evaluated by the ECU 111. The third embodiment will be described below, focusing on the differences from the first embodiment.

[0088] 19 is a diagram illustrating an example of the functional configuration of the ECU 111 according to the third embodiment. The ECU 111 according to the third embodiment newly includes a collection condition evaluation unit 1901. The collection condition evaluation unit 1901 evaluates the collection conditions based on the collection results of the collected data. The collection condition evaluation unit 1901 may evaluate the collection conditions taking vehicle information into consideration.

[0089] The transmission determination unit 308 of the third embodiment transmits the collected data and the evaluation result of the collection conditions to the cloud 101 via the transmitting / receiving unit 309. The cloud 101 can present the evaluation result of the collection conditions together with the collected data.

[0090] In the case of the cloud 101 having the evaluation function described in the second embodiment, the cloud may update the collection conditions using the evaluation results. Also, the cloud 101 may evaluate the collection conditions using the collected data and compare two evaluation results.

[0091] By evaluating the collection conditions and reviewing them based on the evaluation results, the collection conditions can be optimized.

[0092] In the fourth embodiment, the ECU 111 evaluates the collection conditions and updates the collection conditions based on the evaluation results. The fourth embodiment will be described below, focusing on the differences from the first embodiment.

[0093] 20 is a diagram illustrating an example of the functional configuration of the ECU 111 according to the fourth embodiment. The ECU 111 according to the fourth embodiment newly includes a collection condition evaluation unit 2001. The collection condition evaluation unit 2001 evaluates the collection conditions based on the collection results of the collected data and updates the collection conditions based on the evaluation results. The collection condition evaluation unit 2001 may evaluate the collection conditions taking vehicle information into consideration.

[0094] For example, if the collection frequency is lower than the threshold, the collection condition evaluation unit 2001 deletes the collection condition and relaxes the judgment parameters, and if the collection frequency is higher than the threshold, adds constraints by changing the judgment parameters, etc.

[0095] The timing for reflecting the settings based on the updated collection conditions may be during a period when collected data is not being collected, while the vehicle is running, while the vehicle is stopped, when the engine is next started, etc. Furthermore, the results of updating the collection conditions may be added to the collected data and transmitted to the cloud 101.

[0096] The collection conditions can be optimized by evaluating the collection conditions and reviewing them based on the evaluation results. The collection conditions can be updated instantly without going through the cloud 101.

[0097] In the fifth embodiment, the ECU 111 evaluates a plurality of collection conditions. The fifth embodiment will be described below, focusing on the differences from the first embodiment.

[0098] 21 is a diagram illustrating an example of the functional configuration of the ECU 111 according to the fifth embodiment. The ECU 111 according to the fifth embodiment includes a collection condition evaluation unit 2101 and a plurality of trigger detection units 305.

[0099] In the fifth embodiment, the cloud 101 transmits two collection conditions having different start and end trigger conditions to the ECU 111. The ECU 111 performs control so that collected data can be collected under each collection condition. The collection condition evaluation unit 2101 evaluates the collection conditions based on the collection results under the two collection conditions.

[0100] By evaluating two collection conditions with different trigger conditions, more accurate collection conditions can be applied.

[0101] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, with respect to part of the configuration of each embodiment, addition, deletion, or substitution of other configurations can be applied alone or in combination.

Claims

1. A data collection system including a vehicle having a vehicle control device and a cloud, wherein the vehicle control device has: a trigger detection unit that monitors the occurrence of a start trigger that starts collection of collected data to be collected and the occurrence of an end trigger that ends collection of the collected data; and a data collection unit that collects the collected data based on data collection conditions, wherein the trigger detection unit has a start trigger monitoring algorithm for monitoring the occurrence of the start trigger for each start trigger condition that defines the start trigger, and an end trigger monitoring algorithm for monitoring the occurrence of the end trigger for each end trigger condition that defines the end trigger, the data collection unit has at least one collection algorithm for collecting the collected data based on the data collection conditions, wherein the start trigger condition of each of the multiple start trigger monitoring algorithms is different, and the end trigger condition of each of the multiple end trigger monitoring algorithms is different, and the cloud transmits to the vehicle collection conditions for controlling collection of the collected data, the collection conditions being expressed as a state machine that includes, as states, a start trigger monitoring state that indicates monitoring of the start trigger, and a data collection state that indicates collection of the collected data and monitoring of the end trigger, and that defines transition of the states by the start trigger condition and the end trigger condition, The vehicle control device configures the trigger detection unit and the data collection unit so that the collected data can be collected according to the state machine, and the state machine transmitted by the cloud includes branches to different data collection states.

2. A data collection system as described in claim 1, wherein the vehicle control device sets the start trigger monitoring algorithm and the end trigger monitoring algorithm to be used by the trigger detection unit, sets the collection algorithm to be used by the data collection unit, and sets the call relationship between the start trigger monitoring algorithm, the end trigger monitoring algorithm, and the collection algorithm.

3. A data collection system as described in claim 1, wherein the vehicle control device transmits the collected data to the cloud, and the cloud evaluates the collection conditions based on the collection results of the collected data, modifies the collection conditions based on the results of the evaluation, and transmits the modified collection data to the vehicle.

4. A data collection system as described in claim 3, characterized in that the vehicle control device transmits the collected data and at least one of data related to the collection of the collected data and data related to the vehicle to the cloud.

5. A data collection system as described in claim 1, wherein the vehicle control device evaluates the collection conditions based on the collection results of the collected data, and transmits the collected data and the results of the evaluation to the cloud.

6. A data collection system according to claim 1, wherein the vehicle control device evaluates the collection conditions based on the collection results of the collected data, and modifies the collection conditions based on the results of the evaluation.

7. A data collection system as described in claim 1, wherein the cloud transmits a plurality of the state machines corresponding to different collection conditions, and the vehicle control device configures the trigger detection unit and the data collection unit so as to realize collection of the collected data corresponding to each of the plurality of collection conditions based on the plurality of state machines, performs a comparative evaluation of the plurality of collection conditions based on the collection results of the collected data based on the plurality of collection conditions, and transmits the results of the comparative evaluation to the cloud.

Images