Vehicle data collection device and vehicle data collection system

Abstract

To flexibly collect vehicle data before and after collection conditions for vehicle data are met, while suppressing oppression on communication and cost increase.SOLUTION: A vehicle data collection device 5 includes: a setting unit 40 for determining a collection setting which is setting information to each ECU in response to a collection request; a collection condition determination unit 51 that sets collection conditions based on the collection setting and determines whether or not the collection conditions are met: a collection data output unit 52 that sets collection data based on the collection setting and acquires the collection data from each ECU; a multi-stage retention unit 53 that holds the collection data before the collection conditions are met and the collection data after the collection conditions are met based on the collection setting; a transmission standby unit 60 that waits for transmission of the held collection data; and a transmission unit 31 that transmits the collection data that is on standby in transmission standby unit 60 to the request source. The collection request includes a set value related to the number of the held collection data in the multi-stage retention unit 53. The setting unit 40 determines the collection setting by changing the number of the held collection data by the multi-stage retention unit 53 from the set values.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a vehicle data collection device and a vehicle data collection system. [Background technology]

[0002] In recent years, vehicle data collection devices have been developed that collect data from post-sale vehicles and transmit it to a server device installed outside the vehicle. In response to a request from the server device, the vehicle data collection device collects vehicle data, such as control signals exchanged inside any electronic control units (hereinafter also referred to as "ECUs") installed in the vehicle, while the vehicle is traveling. The vehicle data collection device then transmits the collected vehicle data to the server device via a mobile phone communication network or the like.

[0003] The server device collects vehicle data from a large number of vehicles and uses it for various purposes. For example, the server device can use the collected sensor data from autonomous vehicles when near-misses occur to train AI (Artificial Intelligence). The server device can also use the collected software input / output data to verify software.

[0004] An example of a vehicle data collection system is disclosed in Patent Document 1. The server device of the system disclosed in Patent Document 1 determines the collection conditions for vehicle data, and when it detects that the collection conditions are met, requests the ECUs to transmit the vehicle data to be collected. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-132368 Summary of the Invention [Problem to be solved by the invention]

[0006] However, in the system disclosed in Patent Document 1, transmission of vehicle data is requested only after the satisfaction of the collection conditions is detected, and therefore vehicle data before the collection conditions are satisfied cannot be collected. For example, if vehicle data is collected from an autonomous vehicle that has experienced a near miss and you want to train an AI to suppress the occurrence of near misses, it is important to collect vehicle data obtained not only after the near miss occurs, but also in the process leading up to the near miss. The system disclosed in Patent Document 1 cannot collect vehicle data before the satisfaction of the collection conditions, and therefore cannot collect vehicle data obtained in the process leading up to the near miss.

[0007] In order to collect vehicle data before the collection condition is met, it is necessary to accumulate the vehicle data before the collection condition is met. For example, if a nonvolatile memory is provided in one of the ECUs to accumulate the vehicle data before the collection condition is met, the vehicle data must be frequently transmitted from the ECU that outputs the vehicle data to the ECU that includes the nonvolatile memory, which places a strain on communication. Furthermore, for example, if a nonvolatile memory is provided in each ECU, the strain on communication between ECUs can be avoided. However, the ECU that outputs the vehicle data is not determined until a request is received from the server device, and nonvolatile memory must be provided for all potential ECUs, resulting in increased costs. Furthermore, if a volatile memory provided in each ECU is used to accumulate vehicle data, the capacity of the volatile memory that can be allocated for storage varies from vehicle to vehicle. This means that a collection method that cannot collect data from vehicles with small storage capacities must be abandoned, or collection from vehicles with small storage capacities must be abandoned altogether, making it difficult to flexibly collect vehicle data.

[0008] The present invention has been made in view of the above, and aims to flexibly collect vehicle data before and after a vehicle data collection condition is met while suppressing communication congestion and cost increases. [Means for solving the problem]

[0009] a collection condition determination unit that sets collection conditions for the vehicle data based on the collection settings and determines whether the set collection conditions are met; a collected data output unit that sets collected data, which is the vehicle data to be collected, based on the collection settings and acquires and outputs the set collected data from the electronic control unit; a multi-stage storage unit that stores, based on the collection settings, the collected data that was output before the collection conditions were met and the collected data that was output after the collection conditions were met; a transmission standby unit that keeps the collected data stored in the multi-stage storage unit on hold for transmission to a source that made the collection request; and a transmission unit that transmits the collected data that has been waited in the transmission standby unit to the source of the request; [Effects of the Invention]

[0010] According to the present invention, vehicle data can be flexibly collected before and after a vehicle data collection condition is met while suppressing communication congestion and cost increases. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing a schematic configuration of a vehicle data collection system including a vehicle data collection device according to a first embodiment. [Figure 2] FIG. 2 is a diagram showing a schematic configuration of the vehicle shown in FIG. [Figure 3] FIG. 3 is a diagram showing the functional configuration of the vehicle data collection device shown in FIG. 2. [Figure 4] 4 is a flowchart of a communication program that constitutes the communication function shown in FIG. 3. [Figure 5] 4 is a flowchart of a setting program that constitutes the setting function shown in FIG. 3. [Figure 6] 4 is a flowchart of a determination program that constitutes the determination function shown in FIG. 3. [Figure 7] 4 is a flowchart of a collection program that constitutes the collection function shown in FIG. 3. [Figure 8] 4 is a flowchart of a standby program that constitutes the standby function shown in FIG. 3. [Figure 9] 4A to 4C are diagrams illustrating the operation of the multi-stage holding unit shown in FIG. 3. [Figure 10] 4 is a diagram for explaining the operation of the multi-stage holding unit when the setting unit shown in FIG. 3 determines the collection setting based on the front and rear priority. [Figure 11] 4 is a diagram for explaining the operation of the multi-stage holding unit when the setting unit shown in FIG. 3 determines the collection setting based on the condition priority. [Figure 12] 4 is a diagram for explaining the operation of the multi-stage holding unit when the setting unit shown in FIG. 3 determines the collection setting based on the format priority. [Figure 13] 4 is a diagram for explaining an example of the operation of the vehicle data collection device shown in FIG. 3. [Figure 14] 4 is a diagram for explaining an example of the operation of the vehicle data collection device shown in FIG. 3. [Figure 15] 4 is a diagram for explaining an example of the operation of the vehicle data collection device shown in FIG. 3. [Figure 16] FIG. 10 is a diagram showing a schematic configuration of a vehicle data collection device according to a second embodiment. [Figure 17] FIG. 10 is a diagram showing a schematic configuration of a vehicle data collection device according to a third embodiment. [Figure 18] FIG. 10 is a diagram showing the functional configuration of a vehicle data collection device according to a fourth embodiment. [Figure 19] 19 is a diagram showing an example of the operation of the vehicle data collection device shown in FIG. 18. [Figure 20] 10 is a timing chart illustrating the vehicle data collection device according to the fifth embodiment. [Figure 21] FIG. 13 is a diagram showing the functional configuration of a vehicle data collection device according to a sixth embodiment. [Figure 22] FIG. 13 is a diagram showing the functional configuration of a vehicle data collection device according to a seventh embodiment. [Figure 23] FIG. 13 is a diagram showing the functional configuration of a vehicle data collection device according to an eighth embodiment. [Figure 24] FIG. 13 is a diagram showing a schematic configuration of a vehicle data collection system according to a ninth embodiment. [Figure 25] FIG. 25 is a diagram showing the functional configuration of the vehicle data collection system shown in FIG. 24. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that components with the same reference numerals in each embodiment have the same functions in each embodiment unless otherwise specified, and description thereof will be omitted.

[0013] In the following embodiments, the present invention is applied to an ECU mounted on an electric vehicle having an automatic driving function. However, the present invention can also be applied to ECUs mounted on various vehicles, such as electric vehicles without an automatic driving function, hybrid vehicles, engine vehicles, or construction vehicles that travel on construction sites.

[0014] [Embodiment 1] The vehicle data collection device 5 of the first embodiment will be described with reference to FIGS.

[0015] Fig. 1 is a diagram showing a schematic configuration of a vehicle data collection system 1 having a vehicle data collection device 5 of embodiment 1. The dashed arrows shown in Fig. 1 indicate the flow of signals or data.

[0016] The vehicle data collection system 1 includes a terminal device 2 into which an administrator inputs administrator settings, a server device 3 connected to the terminal device 2 for wired or wireless communication, and a vehicle 4 connected to the server device 3 via a wireless communication network such as a mobile phone communication network.

[0017] The terminal device 2 is equipped with a user interface such as a display and a keyboard. The administrator can input administrator settings into the terminal device 2 via a GUI (Graphical User Interface). The administrator settings are settings for vehicle data collection input by the administrator, and include the range of vehicles from which vehicle data collection is attempted and requests to be transmitted to each vehicle. The terminal device 2 transmits the input administrator settings to the server device 3.

[0018] The server device 3 includes a central processing unit (CPU), a dynamic random access memory (DRAM), a hard disk drive, a network adapter, etc., and the CPU executes a server program to realize various functions of the server device 3.

[0019] The server device 3 includes a request unit 100 that generates a vehicle data collection request based on the administrator settings transmitted from the terminal device 2 and transmits the generated collection request to the vehicle 4. Specifically, the request unit 100 serializes the request included in the administrator settings transmitted from the terminal device 2 and calculates a request byte sequence. Furthermore, the request unit 100 selects multiple vehicles including the vehicle 4 based on the range included in the administrator settings and transmits the request byte sequence via a mobile phone communication network. This allows the server device 3 to transmit to the vehicle 4 a vehicle data collection request in accordance with the request included in the administrator settings for multiple vehicles corresponding to the range included in the administrator settings.

[0020] The range included in the administrator settings may be a range specified by vehicle type. This allows the server device 3 to transmit a vehicle data collection request only to vehicles 4 of a specific vehicle type. The range included in the administrator settings may be a range specified by vehicle class. This allows the server device 3 to transmit a vehicle data collection request only to vehicles 4 of a specific vehicle class. The range included in the administrator settings may be a range specified by the area in which the vehicle 4 is located. This allows the server device 3 to transmit a vehicle data collection request only to vehicles 4 located in a specific area, such as a specific city, town, village, specific road, or specific intersection. The range included in the administrator settings may be a range specified by a list of vehicle registration numbers. This allows the server device 3 to transmit a vehicle data collection request only to vehicles 4 with a specific vehicle registration number.

[0021] In response to a request from the server device 3, the vehicle 4 collects vehicle data from an ECU installed in the vehicle 4. The collected vehicle data is temporarily stored in the vehicle 4 until communication between the vehicle 4 and the server device 3 is established, and then serialized and converted into a waiting data byte sequence, which is then transmitted to the server device 3 via the mobile phone communication network. This allows the server device 3 to collect the vehicle data.

[0022] Fig. 2 is a diagram showing a schematic configuration of the vehicle 4 shown in Fig. 1. The dashed arrows shown in Fig. 2 indicate the flow of signals or data.

[0023] The vehicle 4 includes a motor 6 that drives the vehicle 4, a brake 7 that brakes the vehicle 4, a steering wheel 8 that steers the vehicle 4, a camera 9 that captures images ahead of the vehicle 4, a LiDAR (Light Detection And Ranging) 10 that measures the surroundings of the vehicle 4, a powertrain ECU 11 that commands the motor 6 to operate, a brake ECU 12 that commands the brake 7 to operate, a steering ECU 13 that commands the steering wheel 8 to operate, an autonomous driving ECU 14 that calculates autonomous driving command values ​​for the vehicle 4, a gateway ECU 15 that prevents unauthorized intrusion from outside the vehicle, and a telematics ECU 16 that communicates with the outside of the vehicle. The vehicle 4 also includes a vehicle data collection device 5 that collects vehicle data from the ECUs in response to a vehicle data collection request from the server device 3.

[0024] The motor 6 converts the electrical energy supplied to it into kinetic energy to generate power. The generated power is decelerated by a reducer and then transmitted to the drive wheels, providing the driving force for the vehicle 4. The brakes 7 generate friction by pressing brake pads against disc rotors that rotate with the wheels. This converts the kinetic energy of the rotating wheels into thermal energy, braking the vehicle 4. The steering wheel 8 can change the angle of the drive wheels to change the direction of travel and steer the vehicle 4. The camera 9 can capture images of the area ahead of the vehicle 4 by converting the intensity of light incident on the imaging element into an electric charge and output image data. The LiDAR 10 can measure the distance to the vehicle 4's surroundings by irradiating the vehicle 4 with a laser and detecting the reflected light, and output the measurement results as point cloud data.

[0025] The powertrain ECU 11 is configured to include a CPU, DRAM, etc., and the CPU executes a powertrain control program to calculate command values ​​for the motor 6. The brake ECU 12 is configured to include a CPU, DRAM, etc., and the CPU executes a brake control program to calculate command values ​​for the brakes 7. The steering ECU 13 is configured to include a CPU, DRAM, etc., and the CPU executes a steering control program to calculate command values ​​for the steering 8. This allows the vehicle 4 to control its own traveling, such as acceleration / deceleration and turning.

[0026] The autonomous driving ECU 14 is configured to include a CPU, DRAM, Flash memory, etc., and the CPU executes an autonomous driving control program to calculate an autonomous driving command value. At this time, the autonomous driving ECU 14 calculates the autonomous driving command value based on image data transmitted from the camera 9 or point cloud data transmitted from the LiDAR 10. Furthermore, as the CPU executes the autonomous driving control program, the autonomous driving ECU 14 transmits the calculated autonomous driving command value to the powertrain ECU 11, brake ECU 12, and steering ECU 13. This enables the vehicle 4 to drive autonomously.

[0027] The gateway ECU 15 includes a CPU, DRAM, etc., and the CPU executes a gateway control program to monitor communications with the outside of the vehicle and prevent unauthorized intrusion from outside the vehicle. The telematics ECU 16 includes a CPU, DRAM, a communication antenna, etc., and the CPU executes a communication program to communicate with the server device 3 via a mobile phone communication network.

[0028] FIG. 3 is a diagram showing the functional configuration of the vehicle data collection device 5 shown in FIG.

[0029] The vehicle data collection device 5 includes a communication function 20 that communicates with the request source of the vehicle data collection request (server device 3 in this embodiment), a setting function 21 that performs settings related to the collection of vehicle data for each ECU, and a determination function 22 that determines whether the vehicle data collection conditions are met. Furthermore, the vehicle data collection device 5 includes a collection function 23 that collects vehicle data, and a standby function 24 that waits for the vehicle data collected by the collection function 23 (hereinafter also referred to as "collected data") to be transmitted to the server device 3.

[0030] Each of the functions 20 to 24 of the vehicle data collection device 5 is implemented in each ECU. Each of the functions 20 to 24 of the vehicle data collection device 5 is configured by the hardware and software of each ECU. For example, the communication function 20 is implemented in the telematics ECU 16. The communication function 20 is configured by a CPU, memory, and communication program included in the telematics ECU 16. For example, the setting function 21 is implemented in the gateway ECU 15. The setting function 21 is configured by a CPU, memory, and setting program included in the gateway ECU 15. For example, the determination function 22 is implemented in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the autonomous driving ECU 14, or the gateway ECU 15. The determination function 22 is configured by a CPU, memory, and determination program included in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the autonomous driving ECU 14, or the gateway ECU 15. For example, the collection function 23 is implemented in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the automatic driving ECU 14, or the gateway ECU 15. The collection function 23 is configured by a CPU, memory, and collection program included in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the automatic driving ECU 14, or the gateway ECU 15. The standby function 24 is implemented in the automatic driving ECU 14. The standby function 24 is configured by a CPU, memory, and standby program included in the automatic driving ECU 14. Each of the functions 20 to 24 of the vehicle data collection device 5 is realized by the CPU of each ECU executing the program that constitutes each of the functions 20 to 24. The CPU of each ECU executes the program that constitutes each of the functions 20 to 24 in parallel with the control program of each ECU.

[0031] The communication function 20 includes a receiving unit 30 that receives a collection request from the server device 3 that is the requestor of the vehicle data. Furthermore, the communication function 20 includes a transmitting unit 31 that transmits the collected vehicle data (collected data) to the requestor server device 3. Details of the communication function 20 will be described later with reference to FIG. 4.

[0032] The setting function 21 includes a setting unit 40 that determines collection settings for each ECU based on a vehicle data collection request received by the receiving unit 30.

[0033] The collection setting is setting information for each ECU regarding the collection of vehicle data. The collection setting is setting information for each ECU in response to a received collection request. Specifically, the collection setting is setting information obtained by modifying the content of the received collection request according to each ECU constituting the collection function 23 (i.e., the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the autonomous driving ECU 14, and the gateway ECU 15) based on the specifications of the ECU so that the ECU can execute the collection program of the collection function 23. The collection request includes a setting value for the number of pieces of collected data to be held by the multi-stage holding unit 53. The setting unit 40 can determine the collection setting by modifying the number of pieces of collected data to be held by the multi-stage holding unit 53 from the setting value included in the collection request. Details of the setting function 21 will be described later using FIG. 5.

[0034] The determination function 22 includes a collection condition determination unit 51 that sets vehicle data collection conditions based on the collection settings determined by the setting unit 40 and determines whether the set collection conditions are met. The determination function 22 further includes a determination data output unit 50 that sets vehicle data to be determined when the collection condition determination unit 51 determines whether the collection conditions are met as determination data based on the collection settings, and acquires and outputs the set determination data from the ECU.

[0035] The collection condition determination unit 51 determines whether or not the set collection condition is satisfied based on the determination data output by the determination data output unit 50. If the collection condition determination unit 51 determines that the collection condition is satisfied, it transmits a satisfied condition indicating the satisfied collection condition to the multi-stage holding unit 53. Details of the determination function 22 will be described later with reference to FIG. 6.

[0036] The collection function 23 includes a collection data output unit 52 that sets the vehicle data to be collected as collection data based on the collection settings determined by the setting unit 40, and acquires and outputs the set collection data from the ECU. Furthermore, the collection function 23 includes a multi-stage holding unit 53 that holds, based on the collection settings, the collection data that was output before the collection conditions were met and the collection data that was output after the collection conditions were met.

[0037] The multistage retention unit 53 includes a memory included in the ECU constituting the collection function 23 and a portion of the collection program. The memory constituting the multistage retention unit 53 is a volatile memory, such as a ring buffer. Based on the collection settings set by the setting unit 40 and the satisfaction conditions transmitted from the collection condition determination unit 51, the multistage retention unit 53 deletes the retained collected data in chronological order for each predetermined operation cycle, and sequentially retains the collected data output from the collection data output unit 52. In this manner, the multistage retention unit 53 updates the collected data (hereinafter also referred to as "retained data") retained in the memory constituting the multistage retention unit 53 for each operation cycle. Furthermore, when a predetermined number of operation cycles have elapsed since the reception of the satisfaction conditions (i.e., since the collection conditions were satisfied), the multistage retention unit 53 stops updating the retained data and transmits the retained data of the multistage retention unit 53 to the transmission standby unit 60. Details of the collection function 23 will be described later with reference to FIG. 7.

[0038] The standby function 24 includes a transmission standby unit 60 that waits for transmission of collected data to the requestor. The transmission standby unit 60 includes a memory included in the ECU that configures the standby function 24, and a standby program. The memory that configures the transmission standby unit 60 is a non-volatile memory, such as a Flash memory. The transmission standby unit 60 stores the held data transmitted from the multi-stage holding unit 53 in the memory that configures the transmission standby unit 60, and waits until communication is established between the server device 3 that is the requestor and the vehicle 4. Once communication is established between the server device 3 and the vehicle 4, the held data (hereinafter also referred to as "standby data") stored in the memory that configures the transmission standby unit 60 will be transmitted by the transmitter 31 to the server device 3 that is the requestor. Details of the standby function 24 will be described later using FIG. 8.

[0039] Fig. 4 is a flowchart of a communication program constituting the communication function 20 shown in Fig. 3. The CPU of the ECU constituting the communication function 20 repeatedly executes the communication program shown in Fig. 4 at predetermined operation intervals while the power of the vehicle 4 is on.

[0040] In step S001, the receiving unit 30 of the communication function 20 determines whether or not a request byte sequence of a new collection request has been received from the server device 3. If it is determined that a new request byte sequence has been received, the receiving unit 30 proceeds to step S002. If it is determined that a new request byte sequence has not been received, the receiving unit 30 proceeds to step S003.

[0041] In step S002, the receiving unit 30 deserializes the received request byte sequence to restore the collection request. Deserialization is the inverse conversion of serialization. The restored collection request has the same content as the collection request sent from the server device 3. The receiving unit 30 sends the restored collection request to the setting unit 40, and when the sending is complete, the process proceeds to step S003.

[0042] In step S003, the transmitting unit 31 of the communication function 20 determines whether the transmission standby unit 60 has new standby data waiting. If it is determined that new standby data has been waiting, the transmitting unit 31 proceeds to step S004. If it is determined that new standby data has not been waiting, the transmitting unit 31 ends the communication program shown in FIG.

[0043] In step S004, the transmission unit 31 determines whether communication between the vehicle 4 and the server device 3 has been established. The vehicle 4 and the server device 3 are connected via a mobile phone communication network. The transmission unit 31 determines whether the communication has been established by exchanging confirmation packets between the vehicle 4 and the server device 3. If it is determined that the communication has been established, the transmission unit 31 proceeds to step S005. If it is determined that the communication has not been established, the transmission unit 31 terminates the communication program shown in FIG. 4.

[0044] In step S005, the transmitting unit 31 serializes the standby data in the transmission standby unit 60 and calculates a standby data byte string.

[0045] In step S006, the transmitting unit 31 transmits the calculated standby data byte sequence to the server device 3. This enables the server device 3 to collect vehicle data. After step S006, the transmitting unit 31 ends the communication program shown in FIG.

[0046] Fig. 5 is a flowchart of a setting program constituting the setting function 21 shown in Fig. 3. The CPU of the ECU constituting the setting function 21 repeatedly executes the setting program shown in Fig. 5 at predetermined operation intervals while the power of the vehicle 4 is on.

[0047] In step S101, the setting unit 40 of the setting function 21 determines whether or not a new collection request has been received from the receiving unit 30. If it is determined that a new collection request has been received, the setting unit 40 proceeds to step S102. If it is determined that a new collection request has not been received, the setting unit 40 ends the setting program shown in FIG.

[0048] In step S102, the setting unit 40 calculates and determines collection settings based on the received collection request. If the memory capacity of the multi-stage storage unit 53 is insufficient, the setting unit 40 determines the collection settings by changing the number of collected data items stored in the multi-stage storage unit 53 from the setting value included in the collection request. The setting unit 40 transmits the determined collection settings to the judgment data output unit 50, the collection condition determination unit 51, the collected data output unit 52, and the multi-stage storage unit 53. This enables the vehicle data collection device 5 to execute the collection program of the collection function 23 while minimizing communication loads and cost increases, even if the specifications (particularly the specifications of each ECU) of multiple vehicles selected based on the range included in the administrator settings are different. Therefore, the vehicle data collection device 5 can flexibly collect vehicle data before and after the collection conditions are met while minimizing communication loads and cost increases. After step S102, the setting unit 40 terminates the setting program shown in FIG. 5.

[0049] Fig. 6 is a flowchart of a determination program constituting the determination function 22 shown in Fig. 3. The CPU of the ECU constituting the determination function 22 repeatedly executes the determination program shown in Fig. 6 at predetermined operation intervals while the power of the vehicle 4 is on.

[0050] In step S201, the determination data output unit 50 of the determination function 22 determines whether or not a new collection setting has been received from the setting unit 40. If it is determined that a new collection setting has been received, the determination data output unit 50 proceeds to step S202. If it is determined that a new collection setting has not been received, the determination data output unit 50 proceeds to step S204.

[0051] In step S202, the determination data output unit 50 sets the determination data based on the received collection setting. Specifically, the determination data output unit 50 identifies a control signal that matches the collection setting among the control signals of the ECU that constitutes the determination function 22. Then, the determination data output unit 50 sets the identified control signal as the determination data as vehicle data that is to be determined when the collection condition determination unit 51 determines whether the collection condition is satisfied.

[0052] In step S203, the collection condition determination unit 51 of the determination function 22 sets collection conditions based on the received collection settings. Specifically, the collection condition determination unit 51 identifies a determination condition expression of the determination data that matches the collection settings, and sets the identified determination condition expression as the collection condition.

[0053] In step S204, the judgment data output unit 50 acquires judgment data from the ECU and outputs it to the collection condition judgment unit 51. Specifically, the judgment data output unit 50 acquires a control signal that matches the set judgment data from the control signals of the ECU that constitutes the judgment function 22. Then, the judgment data output unit 50 outputs the acquired control signal to the collection condition judgment unit 51 as judgment data.

[0054] In step S205, the collection condition determination unit 51 determines whether the set collection conditions are met. Specifically, the collection condition determination unit 51 determines whether the collection conditions are met by determining whether the determination data output from the determination data output unit 50 satisfies the specified determination condition formula. If it is determined that the collection conditions are met, the collection condition determination unit 51 proceeds to step S206. If it is determined that the collection conditions are not met, the collection condition determination unit 51 terminates the determination program shown in FIG. 6. Note that multiple collection conditions may be set. In this case, if it is determined that any of the set collection conditions are met, the collection condition determination unit 51 proceeds to step S206, and if it is determined that none of the set collection conditions are met, the collection condition determination unit 51 terminates the determination program shown in FIG. 6.

[0055] In step S206, the collection condition determination unit 51 transmits a condition indicating the established collection condition to the multi-stage holding unit 53. After step S206, the collection condition determination unit 51 ends the determination program shown in FIG.

[0056] Fig. 7 is a flowchart of a collection program constituting the collection function 23 shown in Fig. 3. The CPU of the ECU constituting the collection function 23 repeatedly executes the collection program shown in Fig. 7 at predetermined operation intervals while the power of the vehicle 4 is on.

[0057] In step S301, the collected data output unit 52 of the collection function 23 determines whether or not a new collection setting has been received from the setting unit 40. If it is determined that a new collection setting has been received, the collected data output unit 52 proceeds to step S302. If it is determined that a new collection setting has not been received, the collected data output unit 52 proceeds to step S304.

[0058] In step S302, the collected data output unit 52 sets collected data based on the received collection setting. Specifically, the collected data output unit 52 identifies control signals that match the collection setting among the control signals of the ECUs that constitute the collection function 23. Then, the collected data output unit 52 sets the identified control signals as collected data as vehicle data to be collected.

[0059] In step S303, the multistage holding unit 53 of the collection function 23 sets the holding operation of the multistage holding unit 53 for holding the set collected data based on the received collection setting. Specifically, the multistage holding unit 53 sets the number of collected data to be held in the multistage holding unit 53 based on the received collection setting. The number of collected data to be held in the multistage holding unit 53 is the sum of the number of collected data output before the collection condition is met and held in the multistage holding unit 53, and the number of collected data output after the collection condition is met and held in the multistage holding unit 53.

[0060] The collection request sent from the receiving unit 30 includes a first setting value regarding the number of collected data output before the collection condition is met to be held in the multi-stage holding unit 53, and a second setting value regarding the number of collected data output after the collection condition is met to be held in the multi-stage holding unit 53.

[0061] The number of collected data items output before the collection condition is satisfied that are to be retained in the multi-stage retention unit 53 is determined by the number of operating cycles of the CPU of the ECU constituting the collection function 23 going back from the time the collection condition is satisfied (when the satisfaction condition is received) that the multi-stage retention unit 53 is to retain the collected data items output up to. Similarly, the number of collected data items output after the collection condition is satisfied that are to be retained in the multi-stage retention unit 53 is determined by the number of operating cycles of the CPU of the ECU constituting the collection function 23 that have elapsed since the time the collection condition is satisfied (when the satisfaction condition is received) that the multi-stage retention unit 53 is to retain the collected data items output up to. Therefore, a first setting value included in the collection request specifies the number of operating cycles that should elapse from the time the collection condition is satisfied (when the satisfaction condition is received). Similarly, a second setting value included in the collection request specifies the number of operating cycles that should elapse from the time the collection condition is satisfied (when the satisfaction condition is received).

[0062] When the capacity of the memory constituting the multistage holding unit 53 is insufficient, the setting unit 40 determines the collection setting by changing the number of collected data items held by the multistage holding unit 53 from the first setting value and the second setting value included in the collection request, and transmits the determined collection setting to the multistage holding unit 53. Based on the received collection setting, the multistage holding unit 53 sets the number of collected data items corresponding to the number of operating cycles indicated by the changed first setting value to the number of collected data items that were output before the collection condition was met, and sets the number of collected data items corresponding to the number of operating cycles indicated by the changed second setting value to the number of collected data items that were output after the collection condition was met to the number of collected data items that were held.

[0063] In step S304, the multistage holding unit 53 determines whether the number of operating periods set based on the second set value has elapsed since receiving a new satisfaction condition from the collection condition determination unit 51. If it is determined that the number of operating periods set based on the second set value has elapsed since receiving the new satisfaction condition, the multistage holding unit 53 proceeds to step S305. If it is determined that the new satisfaction condition has not been received or that the number of operating periods set based on the second set value has not elapsed since receiving the new satisfaction condition, the multistage holding unit 53 proceeds to step S306.

[0064] In step S305, the multistage holding unit 53 transmits the held data to the transmission standby unit 60 with low priority. When the held data is transmitted from the multistage holding unit 53 to the transmission standby unit 60 via a Control Area Network (CAN), the multistage holding unit 53 assigns an ID (Identifier) ​​with a lower priority than other messages to the held data. When the held data is transmitted from the multistage holding unit 53 to the transmission standby unit 60 via a Time-Sensitive Networking (TSN), the multistage holding unit 53 transmits the held data in a low-priority window. This allows the multistage holding unit 53 to transmit the held data to the transmission standby unit 60 without interfering with other communications.

[0065] In step S306, the collected data output unit 52 acquires the collected data from the ECU and outputs it to the multi-stage holding unit 53. Specifically, the collected data output unit 52 acquires a control signal that matches the set collected data from the control signals of the ECU that constitutes the collection function 23. Then, the collected data output unit 52 outputs the acquired control signal to the multi-stage holding unit 53 as collected data.

[0066] In step S307, the multistage holding unit 53 updates the data held in the multistage holding unit 53. Specifically, the multistage holding unit 53 deletes the held collected data in chronological order, and sequentially holds the collected data output from the collected data output unit 52. After step S307, the multistage holding unit 53 ends the collection program shown in FIG.

[0067] Fig. 8 is a flowchart of a standby program constituting the standby function 24 shown in Fig. 3. The CPU of the ECU constituting the standby function 24 repeatedly executes the standby program shown in Fig. 8 at predetermined operation intervals while the power supply of the vehicle 4 is on.

[0068] In step S401, the transmission standby unit 60 of the standby function 24 determines whether new held data has been received from the multi-stage holding unit 53. If it is determined that new held data has been received, the transmission standby unit 60 proceeds to step S402. If it is determined that new held data has not been received, the transmission standby unit 60 ends the standby program shown in FIG.

[0069] In step S402, the transmission standby unit 60 stores the received retained data in a memory constituting the transmission standby unit 60, and keeps the data on standby as standby data until communication is established between the server device 3 that is the request source and the vehicle 4. After step S402, the transmission standby unit 60 ends the standby program shown in FIG.

[0070] Fig. 9 is a diagram for explaining the operation of the multi-stage holding unit 53 shown in Fig. 3. Fig. 9 shows an example in which only one type of vehicle data is collected as collected data, and the volatile memory of the ECU constituting the collection function 23 has the capacity necessary to execute the collection request.

[0071] As described above, the number of collected data items held by the multi-stage holding unit 53 is determined by the first setting value B1 and the second setting value A1 included in the collection request. The setting unit 40 determines the collection setting based on the first setting value B1 and the second setting value A1. In this embodiment, the number of operation cycles indicated by the first setting value B1 is set to "B1," and the number of operation cycles indicated by the second setting value A1 is set to "A1."

[0072] If no new satisfaction condition has been received from the collection condition determination unit 51, or if A1 operation cycles have not elapsed since the new satisfaction condition was received, the multistage holding unit 53, upon receiving new collected data, deletes collected data older than the collected data for (B1+A1) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data to update the held data. The multistage holding unit 53 holds collected data from the past to the present for (B1+A1) operation cycles.

[0073] When A1 operating cycles have elapsed since receiving a new satisfaction condition from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data before receiving the satisfaction condition for B1 operating cycles and the collected data after receiving the satisfaction condition for A1 operating cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data output before the collection condition is satisfied for B1 operating cycles and collect the collected data output after the collection condition is satisfied for A1 operating cycles.

[0074] Fig. 10 is a diagram illustrating the operation of the multi-stage holding unit 53 when the setting unit 40 shown in Fig. 3 determines the collection setting based on the front and rear priority. Fig. 10 shows an example in which only one type of vehicle data is collected as the collected data, and the volatile memory of the ECU constituting the collection function 23 does not have the capacity necessary to execute the collection request.

[0075] The collection request includes a first set value B2, a second set value A2, and a front-to-back priority. The front-to-back priority is information that determines whether the multi-stage holding unit 53 should hold the collected data output before the collection condition is met or the collected data output after the collection condition is met.

[0076] The front-rear priority includes forward priority, backward priority, and equal ratio. Forward priority is information that sets collected data output before the collection condition is met to be held with priority over collected data output after the collection condition is met. Later priority is information that sets collected data output after the collection condition is met to be held with priority over collected data output before the collection condition is met. Equal ratio is information that sets no priority relationship between collected data output before the collection condition is met and collected data output after the collection condition is met.

[0077] The front-rear priority is set according to the purpose of collecting vehicle data. For example, if sensor data collected from an autonomous vehicle when a near-miss occurs is used for AI learning, the process leading up to the near-miss occurrence is important, so the front-rear priority can be set to give priority to the front.

[0078] The setting unit 40 determines the collection setting to change the number of collected data held by the multi-stage holding unit 53 by changing at least one of the first setting value B2 and the second setting value A2 based on the memory capacity of the ECU that constitutes the multi-stage holding unit 53 and the front / rear priority.

[0079] For example, if the capacity of the memory constituting the multi-stage holding unit 53 is insufficient to hold collected data for (B2+A2) operation cycles and the front-rear priority included in the collection request is rear priority, the setting unit 40 changes the first setting value to B2', which is less than B2, and determines the collection setting.

[0080] If no new satisfaction condition has been received from the collection condition determination unit 51, or if A2 operation cycles have not elapsed since the new satisfaction condition was received, the multistage holding unit 53, upon receiving new collected data, deletes collected data older than the collected data for (B2'+A2) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data to update the held data. The multistage holding unit 53 holds collected data from the past to the present for (B2'+A2) operation cycles.

[0081] When A2 operation cycles have elapsed since receiving a new satisfaction condition from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data before receiving the satisfaction condition for B2' operation cycles and the collected data after receiving the satisfaction condition for A2 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data output before the collection condition is satisfied for B2' operation cycles and collect the collected data output after the collection condition is satisfied for A2 operation cycles.

[0082] Also, for example, if the capacity of the memory constituting the multi-stage holding unit 53 is insufficient to hold collected data for (B2+A2) operation cycles and the forward / backward priority included in the collection request is forward priority, the setting unit 40 changes the second setting value to A2' which is less than A2, and determines the collection setting.

[0083] If no new satisfaction condition has been received from the collection condition determination unit 51, or if A2' operation cycles have not yet elapsed since the new satisfaction condition was received, the multistage holding unit 53, upon receiving new collected data, deletes collected data older than the collected data for (B2+A2') operation cycles held in the multistage holding unit 53, and sequentially holds new collected data to update the held data. The multistage holding unit 53 holds collected data from the past to the present for (B2+A2') operation cycles.

[0084] When A2' operation cycles have elapsed since a new satisfaction condition was received from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data before receiving the satisfaction condition for B2 operation cycles and the collected data after receiving the satisfaction condition for A2' operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data output before the collection condition was satisfied for B2 operation cycles and collect the collected data output after the collection condition was satisfied for A2' operation cycles.

[0085] Also, for example, if the capacity of the memory constituting the multi-stage holding unit 53 is insufficient to hold collected data for (B2+A2) operation cycles and the previous and next priorities included in the collection requests are the same, the setting unit 40 changes the first setting value to B2'' which is less than B2, changes the second setting value to A2'' which is less than A2, and determines the collection settings.

[0086] If no new satisfaction condition has been received from the collection condition determination unit 51, or if A2'' operation cycles have not elapsed since the new satisfaction condition was received, the multistage holding unit 53, upon receiving new collected data, deletes collected data older than (B2''+A2'') operation cycles of collected data held in the multistage holding unit 53, and sequentially holds new collected data to update the held data. The multistage holding unit 53 will hold collected data from the past to the present for (B2''+A2'') operation cycles (B2''=A2'').

[0087] When A2'' operation cycles have elapsed since a new satisfaction condition was received from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data before receiving the satisfaction condition for B2'' operation cycles and the collected data after receiving the satisfaction condition for A2'' operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data to the transmission standby unit 60 with low priority. This allows the vehicle data collection device 5 to collect the collected data that was output before the collection condition was satisfied for B2'' operation cycles and collect the collected data that was output after the collection condition was satisfied for A2'' operation cycles.

[0088] In this way, the vehicle data collection request can include a front-to-rear priority according to the purpose of collecting the vehicle data. This allows the vehicle data collection device 5 to change the content of the collection request and determine the collection settings so that the collection program of the collection function 23 can be executed even if the specifications of the multiple vehicles selected according to the range included in the administrator setting are different and the memory capacity of the multi-stage storage unit 53 is insufficient. Therefore, the vehicle data collection device 5 can flexibly collect vehicle data before and after the collection condition is met while suppressing communication congestion and cost increases.

[0089] Fig. 11 is a diagram illustrating the operation of the multi-stage holding unit 53 when the setting unit 40 shown in Fig. 3 determines the collection setting based on the condition priority. Fig. 11 shows an example in which collected data D31 is output when the collection condition C31 is satisfied and the satisfied condition C31 is received, collected data D32 is output when the collection condition C32 is satisfied and the satisfied condition C32 is received, and the volatile memory of the ECU constituting the collection function 23 does not have the capacity necessary to execute the collection request.

[0090] The collection request includes a first set value B31, a second set value A31, and a previous or next priority for the collected data D31, and a first set value B32, a second set value A32, and a previous or next priority for the collected data D32. The collection request also includes a condition priority. The condition priority is information that sets which of multiple collection conditions is to be given priority in the multi-stage holding unit 53 when holding the collected data.

[0091] The condition priority is set according to the purpose of collecting vehicle data. For example, if the occurrence frequency of the fulfillment condition C31 is lower than that of the fulfillment condition C32, the condition priority may be set to give priority to the fulfillment condition C31.

[0092] The setting unit 40 determines the collection setting to change the number of collected data D31, D32 held by the multi-stage holding unit 53 by changing at least one of the first setting values ​​B31, B32 and the second setting values ​​A31, A32 based on the capacity of the memory constituting the multi-stage holding unit 53 and the condition priority.

[0093] For example, if the capacity of the memory constituting the multistage holding unit 53 is insufficient to hold the collected data D31 for (B31+A31) operating cycles and the collected data D32 for (B32+A32) operating cycles, and the condition priority included in the collection request is the fulfillment condition C31, and the previous / next priority for the collected data D32 is backward priority, the setting unit 40 changes the first setting value for the collected data D32 to B32' which is less than B32, and determines the collection setting. Note that the setting unit 40 leaves the second setting value for the collected data D32 unchanged at A32, leaves the first setting value for the collected data D31 unchanged at B31, and leaves the second setting value for the collected data D31 unchanged at A31, and determines the collection setting.

[0094] If a new satisfaction condition C31 has not been received from the collection condition determination unit 51, or if A31 operation cycles have not elapsed since the new satisfaction condition C31 was received, the multistage holding unit 53, upon receiving new collected data D31, deletes collected data D31 that is older than the collected data D31 for (B31+A31) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data D31 to update the held data. The multistage holding unit 53 holds collected data D31 from the past to the present for (B31+A31) operation cycles.

[0095] When A31 operation cycles have elapsed since receiving a new satisfaction condition C31 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D31 before receiving the satisfaction condition C31 for B31 operation cycles and the collected data D31 after receiving the satisfaction condition C31 for A31 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data D31 output before the collection condition C31 is satisfied for B31 operation cycles and collect the collected data D31 output after the collection condition C31 is satisfied for A31 operation cycles.

[0096] On the other hand, if a new satisfaction condition C32 has not been received from the collection condition determination unit 51, or if A32 operation cycles have not yet elapsed since the new satisfaction condition C32 was received, the multistage holding unit 53, upon receiving new collected data D32, deletes collected data D32 that is older than the collected data D32 for (B32'+A32) operation cycles that has been held in the multistage holding unit 53, and sequentially holds new collected data D32 to update the held data. The multistage holding unit 53 holds collected data D32 from the past to the present for (B32'+A32) operation cycles.

[0097] When A32 operation cycles have elapsed since receiving a new satisfaction condition C32 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D32 before receiving the satisfaction condition C32 for B32' operation cycles and the collected data D32 after receiving the satisfaction condition C32 for A32 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data D32 output before the collection condition C32 is satisfied for B32' operation cycles and collect the collected data D32 output after the collection condition C32 is satisfied for A32 operation cycles.

[0098] Furthermore, for example, when the capacity of the memory constituting the multistage holding unit 53 is insufficient to hold the collected data D31 for (B31+A31) operation cycles and the collected data D32 for (B32+A32) operation cycles, and the condition priority included in the collection request is the fulfillment condition C32, and the forward / backward priority for the collected data D31 is forward priority, the setting unit 40 changes the second setting value for the collected data D31 to A31' which is less than A31, and determines the collection setting. Note that the setting unit 40 determines the collection setting without changing the first setting value for the collected data D31 to B31, without changing the first setting value for the collected data D32 to B32, and without changing the second setting value for the collected data D32 to A32.

[0099] If a new satisfaction condition C31 has not been received from the collection condition determination unit 51, or if A31 operation cycles have not elapsed since the new satisfaction condition C31 was received, the multistage holding unit 53, upon receiving new collected data D31, deletes collected data D31 that is older than the collected data D31 for (B31+A31') operation cycles held in the multistage holding unit 53, and sequentially holds new collected data D31 to update the held data. The multistage holding unit 53 holds collected data D31 from the past to the present for (B31+A31') operation cycles.

[0100] When A31' operation cycles have elapsed since receiving a new satisfaction condition C31 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D31 before receiving the satisfaction condition C31 for B31 operation cycles and the collected data D31 after receiving the satisfaction condition C31 for A31' operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data D31 output before the collection condition C31 is satisfied for B31 operation cycles and collect the collected data D31 output after the collection condition C31 is satisfied for A31' operation cycles.

[0101] On the other hand, if a new satisfaction condition C32 has not been received from the collection condition determination unit 51, or if A32 operation cycles have not yet elapsed since the new satisfaction condition C32 was received, the multistage holding unit 53, upon receiving new collected data D32, deletes collected data D32 that is older than the collected data D32 for (B32+A32) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data D32 to update the held data. The multistage holding unit 53 holds collected data D32 from the past to the present for (B32+A32) operation cycles.

[0102] When A32 operation cycles have elapsed since receiving a new satisfaction condition C32 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D32 before receiving the satisfaction condition C32 for B32 operation cycles and the collected data D32 after receiving the satisfaction condition C32 for A32 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data D32 that was output before the collection condition C32 was satisfied for B32 operation cycles and collect the collected data D32 that was output after the collection condition C32 was satisfied for A32 operation cycles.

[0103] In this way, the vehicle data collection request can include condition priorities according to the purpose of collecting the vehicle data. This allows the vehicle data collection device 5 to determine collection settings by changing the content of the collection request so that the collection program of the collection function 23 can be executed, even if the specifications of the multiple vehicles selected according to the range included in the administrator settings are different and the memory capacity of the multi-stage storage unit 53 is insufficient. Therefore, the vehicle data collection device 5 can flexibly collect vehicle data before and after the collection conditions are met while suppressing communication congestion and cost increases.

[0104] Fig. 12 is a diagram illustrating the operation of the multi-stage holding unit 53 when the setting unit 40 shown in Fig. 3 determines the collection setting based on the format priority. Fig. 12 shows an example in which collected data D31 is output when the collection condition C31 is satisfied and the satisfied condition C31 is received, collected data D32 is output when the collection condition C32 is satisfied and the satisfied condition C32 is received, and the volatile memory of the ECU constituting the collection function 23 does not have the capacity necessary to execute the collection request.

[0105] The collection request includes, for the collected data D31, a first set value B31, a second set value A31, a previous / next priority, and a format priority, and for the collected data D32, a first set value B32, a second set value A32, a previous / next priority, and a format priority. Furthermore, the collection request includes a condition priority. The format priority is information that sets whether or not the multi-stage storage unit 53 prioritizes maintaining the storage format of the collected data set by the first set value and the second set value.

[0106] The format priority includes format priority and format non-priority. Format priority is information that sets priority to maintaining the storage format of collected data set by the first setting value and the second setting value. Format non-priority is information that sets priority not to maintaining the storage format of collected data set by the first setting value and the second setting value.

[0107] The format priority is set according to the purpose of collecting vehicle data. For example, when vehicle data is used for AI learning, it is often desirable to collect vehicle data in a predetermined format, so the format priority can be set to prioritize format. For example, when vehicle data is used for software verification, it is often desirable to collect all vehicle data when collection conditions are met, so the format priority can be set to non-prioritize format.

[0108] The setting unit 40 determines the collection setting to change the number of pieces of collected data D31, D32 held by the multistage holding unit 53 by changing at least one of the first setting values ​​B31, B32 and the second setting values ​​A31, A32 based on the capacity of the memory constituting the multistage holding unit 53 and the format priority. At this time, if the format priority is format priority and it is difficult to maintain the holding format of the collected data D31, D32 set by the first setting values ​​B31, B32 and the second setting values ​​A31, A32, the setting unit 40 determines the collection setting to exclude the collected data D31, D32 from the collection targets.

[0109] For example, if the capacity of the memory constituting the multistage holding unit 53 is insufficient to hold the collected data D31 for (B31+A31) operating cycles and the collected data D32 for (B32+A32) operating cycles, and the condition priority included in the collection request is the fulfillment condition C31, the forward / backward priority for the collected data D32 is backward priority, and the format priority for the collected data D32 is format non-priority, the setting unit 40 changes the first setting value for the collected data D32 to B32' which is less than B32, and determines the collection setting. Note that the setting unit 40 leaves the second setting value for the collected data D32 unchanged at A32, the first setting value for the collected data D31 unchanged at B31, and the second setting value for the collected data D31 unchanged at A31, and determines the collection setting.

[0110] If a new satisfaction condition C31 has not been received from the collection condition determination unit 51, or if A31 operation cycles have not elapsed since the new satisfaction condition C31 was received, the multistage holding unit 53, upon receiving new collected data D31, deletes collected data D31 that is older than the collected data D31 for (B31+A31) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data D31 to update the held data. The multistage holding unit 53 holds collected data D31 from the past to the present for (B31+A31) operation cycles.

[0111] When A31 operation cycles have elapsed since receiving a new satisfaction condition C31 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D31 before receiving the satisfaction condition C31 for B31 operation cycles and the collected data D31 after receiving the satisfaction condition C31 for A31 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data with low priority to the transmission standby unit 60. This allows the vehicle data collection device 5 to collect the collected data D31 output before the collection condition C31 is satisfied for B31 operation cycles and collect the collected data D31 output after the collection condition C31 is satisfied for A31 operation cycles.

[0112] On the other hand, if a new satisfaction condition C32 has not been received from the collection condition determination unit 51, or if A32 operation cycles have not yet elapsed since the new satisfaction condition C32 was received, the multistage holding unit 53, upon receiving new collected data D32, deletes collected data D32 that is older than the collected data D32 for (B32'+A32) operation cycles that has been held in the multistage holding unit 53, and sequentially holds new collected data D32 to update the held data. The multistage holding unit 53 holds collected data D32 from the past to the present for (B32'+A32) operation cycles.

[0113] When A32 operation cycles have elapsed since receiving a new satisfaction condition C32 from the collection condition determination unit 51, the multistage holding unit 53 will hold the collected data D32 before receiving the satisfaction condition C32 for B32' operation cycles and the collected data D32 after receiving the satisfaction condition C32 for A32 operation cycles. The multistage holding unit 53 stops updating the held data and transmits the held data to the transmission standby unit 60 with low priority. This allows the vehicle data collection device 5 to collect the collected data D32 output before the satisfaction of the collection condition C32 for B32' operation cycles and collect the collected data D32 output after the satisfaction of the collection condition C32 for A32 operation cycles. By setting the format priority to format non-priority, the vehicle data collection device 5 can collect all vehicle data when the collection conditions are satisfied.

[0114] Furthermore, for example, if the capacity of the memory constituting the multistage holding unit 53 is insufficient to hold the collected data D31 for (B31+A31) operating cycles and the collected data D32 for (B32+A32) operating cycles, and the condition priority included in the collection request is the fulfillment condition C31, the previous / next priority for the collected data D32 is "backward priority," and the format priority for the collected data D32 is "format priority," it is difficult to maintain the holding format of the collected data D32 set by the first setting value B32 for the collected data D32. Therefore, the setting unit 40 determines the collection setting to exclude the collected data D32 from the collection targets and to collect only the collected data D31 based on the first setting value B31 and the second setting value A31.

[0115] If a new satisfaction condition C31 has not been received from the collection condition determination unit 51, or if A31 operation cycles have not elapsed since the new satisfaction condition C31 was received, the multistage holding unit 53, upon receiving new collected data D31, deletes collected data D31 that is older than the collected data D31 for (B31+A31) operation cycles held in the multistage holding unit 53, and sequentially holds new collected data D31 to update the held data. The multistage holding unit 53 holds collected data D31 from the past to the present for (B31+A31) operation cycles.

[0116] When A31 operation cycles have elapsed since receiving a new satisfaction condition C31 from the collection condition determination unit 51, the multistage retention unit 53 retains the collected data D31 before receiving the satisfaction condition C31 for B31 operation cycles and the collected data D31 after receiving the satisfaction condition C31 for A31 operation cycles. The multistage retention unit 53 stops updating the retained data and transmits the retained data to the transmission standby unit 60 with low priority. This allows the vehicle data collection device 5 to collect the collected data D31 output before the satisfaction of the collection condition C31 for B31 operation cycles and collect the collected data D31 output after the satisfaction of the collection condition C31 for A31 operation cycles. By setting the format priority to format priority, the vehicle data collection device 5 can collect vehicle data only if it can be collected in a predetermined format. This prevents unnecessary strain on the volatile memory capacity of the ECU constituting the collection function 23 and unnecessary strain on communication between the ECU and other ECUs.

[0117] In this way, the vehicle data collection request can include a format priority according to the purpose of collecting the vehicle data. This allows the vehicle data collection device 5 to change the content of the collection request and determine the collection settings so that the collection program of the collection function 23 can be executed, even if the specifications of the multiple vehicles selected according to the range included in the administrator settings are different and the memory capacity of the multi-stage storage unit 53 is insufficient. Therefore, the vehicle data collection device 5 can flexibly collect vehicle data before and after the collection conditions are met while suppressing communication congestion and cost increases.

[0118] Fig. 13 is a diagram illustrating an example of the operation of the vehicle data collection device 5 shown in Fig. 3. Fig. 13 shows an example of collecting image data received from the camera 9 when a near miss occurs, such as excessive approach to a pedestrian, in order to use the vehicle data for learning the image recognition AI.

[0119] The determination data output unit 50 implemented in the autonomous driving ECU 14 sets the distance to the pedestrian as determination data (step S202). The collection condition determination unit 51 implemented in the autonomous driving ECU 14 sets the collection conditions so that if the distance to the pedestrian becomes equal to or shorter than a predetermined distance, it is determined that excessive approach to a pedestrian has occurred (step S203). The collected data output unit 52 implemented in the autonomous driving ECU 14 sets image data received from the camera 9 as collected data (step S302). This allows the vehicle data collection device 5 shown in FIG. 13 to collect image data when a near miss occurs, such as excessive approach to a pedestrian.

[0120] Fig. 14 is a diagram illustrating an example of the operation of the vehicle data collection device 5 shown in Fig. 3. Fig. 14 shows an example of a case where, in order to use vehicle data for verifying software that controls the brakes 7, when a near miss occurs in which the vehicle comes too close to a pedestrian, the target hydraulic pressure and actual hydraulic pressure of the brakes 7, which are input to the software, and the control voltage of the hydraulic cylinder control motor, which is output from the software, are collected.

[0121] The determination data output unit 50 implemented in the autonomous driving ECU 14 sets the distance to the pedestrian as determination data (step S202). The collection condition determination unit 51 implemented in the autonomous driving ECU 14 sets the collection condition so that excessive approach to the pedestrian occurs when the distance to the pedestrian is equal to or shorter than a predetermined distance (step S203). The collected data output unit 52 implemented in the brake ECU 12 sets the target hydraulic pressure and actual hydraulic pressure of the brake 7 and the control voltage of the hydraulic cylinder control motor as collected data (step S302). This allows the vehicle data collection device 5 shown in FIG. 14 to collect the target hydraulic pressure, actual hydraulic pressure, and control voltage when a near-miss occurs, such as excessive approach to a pedestrian. Note that the vehicle data collection device 5 may simultaneously implement the example shown in FIG. 13 and the example shown in FIG. 14. This allows the vehicle data collection device 5 to simultaneously collect the target hydraulic pressure, actual hydraulic pressure, and control voltage when a near-miss occurs, such as excessive approach to a pedestrian, as well as image data.

[0122] Fig. 15 is a diagram illustrating an example of the operation of the vehicle data collection device 5 shown in Fig. 3. This example shows a case where, in order to strengthen the security of the vehicle 4, external signal data transmitted from outside the vehicle 4 to the vehicle 4 is collected when unauthorized access is suspected.

[0123] The determination data output unit 50 implemented in the gateway ECU 15 sets the external signal data transmitted from the telematics ECU 16 to the gateway ECU 15 as the determination data (step S202). The collection condition determination unit 51 implemented in the gateway ECU 15 sets the collection condition so that it determines that a suspicion of unauthorized access has occurred when the signature of the external signal data matches the unauthorized signature (step S203). The collected data output unit 52 implemented in the gateway ECU 15 sets the external signal data transmitted from the telematics ECU 16 to the gateway ECU 15 as the collected data (step S302). This allows the vehicle data collection device 5 shown in FIG. 15 to collect external signal data when a suspicion of unauthorized access has occurred.

[0124] As described above, the vehicle data collection device 5 of the first embodiment includes the setting unit 40 that determines collection settings, which are setting information for each ECU in response to a collection request; the collection condition determination unit 51 that sets collection conditions for vehicle data based on the collection settings and determines whether the set collection conditions are met; the collected data output unit 52 that sets collected data, which is vehicle data to be collected, based on the collection settings and acquires and outputs the set collected data from each ECU; the multi-stage holding unit 53 that holds, based on the collection settings, collected data output before the collection conditions are met and collected data output after the collection conditions are met; the transmission standby unit 60 that causes the collected data held in the multi-stage holding unit 53 to wait for transmission to the request source; and the transmission unit 31 that transmits the collected data waited in the transmission standby unit 60 to the request source. The collection request includes a setting value for the number of pieces of collected data held in the multi-stage holding unit 53. The setting unit 40 changes the number of pieces of collected data held in the multi-stage holding unit 53 from the setting value to determine the collection settings.

[0125] As a result, the vehicle data collection device 5 of the first embodiment can include a function for storing collected data in the multi-stage storage unit 53 including a volatile memory, separate from the transmission standby unit 60 including a non-volatile memory. Therefore, the vehicle data collection device 5 of the first embodiment does not need to frequently transmit collected data from the collected data output unit 52 to the transmission standby unit 60, and does not need to provide non-volatile memory for every ECU that can output collected data. Additionally, the vehicle data collection device 5 of the first embodiment can change the number of collected data items stored in the multi-stage storage unit 53 from a setting value included in the collection request, depending on each ECU. Therefore, the vehicle data collection device 5 of the first embodiment can store collected data items before and after the collection condition is satisfied, depending on the capacity of the memory included in the multi-stage storage unit 53. Therefore, the vehicle data collection device 5 of the first embodiment can collect vehicle data items before and after the collection condition is satisfied, while minimizing communication congestion and cost increases, even when the specifications of multiple vehicles selected according to the range included in the administrator settings are different. Therefore, the vehicle data collection device 5 can flexibly collect vehicle data before and after the collection condition is met while suppressing communication congestion and cost increases.

[0126] Furthermore, in the vehicle data collection device 5 of the first embodiment, the multistage holding unit 53 deletes the held collected data in chronological order at each predetermined operation cycle and sequentially holds the collected data output from the collected data output unit 52, thereby updating the held data, which is the collected data held in the multistage holding unit 53, at each operation cycle. When a predetermined number of operation cycles have elapsed since the collection condition was met, the multistage holding unit 53 stops updating the held data and transmits the held data to the transmission standby unit 60. The transmission standby unit 60 stores the held data transmitted from the multistage holding unit 53 and waits until communication with the request source is established. When communication with the request source is established, the transmitter 31 transmits the held data stored in the transmission standby unit 60, which is the held data stored in the transmission standby unit 60, to the request source.

[0127] As a result, the vehicle data collection device 5 of embodiment 1 can configure the multi-stage storage unit 53 using existing volatile memory and programs, thereby further suppressing cost increases. In addition, the vehicle data collection device 5 of embodiment 1 can suppress the occurrence of communication errors with the request source, thereby further suppressing communication congestion. Therefore, the vehicle data collection device 5 of embodiment 1 can further suppress communication congestion and cost increases, and can flexibly and easily collect vehicle data before and after the collection condition is met.

[0128] Furthermore, in the vehicle data collection device 5 of the first embodiment, the collection request includes a first setting value related to the number of collected data items output before the collection condition is met to be held in the multi-stage holding unit 53, and a second setting value related to the number of collected data items output after the collection condition is met to be held in the multi-stage holding unit 53. The setting unit 40 determines the collection setting by changing the number of collected data items to be held in the multi-stage holding unit 53 from the first setting value and the second setting value.

[0129] As a result, the vehicle data collection device 5 of the first embodiment can flexibly and easily change the number of collected data items output before the collection condition is met and stored in the multi-stage storage unit 53, and the number of collected data items output after the collection condition is met and stored in the multi-stage storage unit 53. Therefore, the vehicle data collection device 5 of the first embodiment can more flexibly and easily collect vehicle data before and after the collection condition is met, while suppressing communication congestion and cost increases.

[0130] The vehicle data collecting device 5 of the first embodiment may be initially set to collect vehicle data that assists in the use of an EDR (Event Data Recorder) or a drive recorder, such as the distance from a preceding vehicle, before the setting unit 40 determines the collection setting. This allows the vehicle data collecting device 5 of the first embodiment to effectively utilize its own functions even before the collection setting is determined.

[0131] [Embodiment 2] The vehicle data collection device 5 of the second embodiment will be described with reference to Fig. 16. In the vehicle data collection device 5 of the second embodiment, the description of the same configuration and operation as those of the first embodiment will be omitted.

[0132] Fig. 16 is a diagram showing a schematic configuration of a vehicle data collection device 5 of embodiment 2. The dashed arrows shown in Fig. 16 indicate the flow of signals or data.

[0133] In the vehicle data collection device 5 of the second embodiment, the source of the vehicle data collection request is the recording device 110 connected to the vehicle 4. That is, in the vehicle data collection system 1 of the second embodiment, the request unit 100 is provided in the recording device 110, not in the server device 3.

[0134] The recording device 110 is connected by wire to the gateway ECU 15. The recording device 110 includes a CPU, a DRAM, a flash memory, etc., and the CPU executes a recording device control program to realize the functions of the request unit 100.

[0135] In the vehicle data collecting device 5 of the second embodiment, a receiving unit 30 of the communication function 20 implemented in the gateway ECU 15 receives a vehicle data collection request transmitted from the recording device 110 and transmits the request to a setting unit 40 of the setting function 21 implemented in the gateway ECU 15. In the vehicle data collecting device 5 of the second embodiment, a determining function 22 implemented in the autonomous driving ECU 14 sets determination data and collection conditions based on the collection settings, and a collecting function 23 implemented in the autonomous driving ECU 14 sets and stores collected data based on the collection settings. In the vehicle data collecting device 5 of the second embodiment, a transmission standby unit 60 of a standby function 24 implemented in the autonomous driving ECU 14 causes the stored collected data to wait. In the vehicle data collecting device 5 of the second embodiment, a transmitting unit 31 of the communication function 20 implemented in the gateway ECU 15 transmits the collected data waited for by the transmission standby unit 60 to the recording device 110.

[0136] As a result, the vehicle data collection device 5 of the second embodiment can collect vehicle data in the recording device 110 even when the vehicle 4 does not communicate with the server device 3 or when communication between the vehicle 4 and the server device 3 is not established. Therefore, even when the vehicle 4 does not communicate with the server device 3 or when communication between the vehicle 4 and the server device 3 is not established, the vehicle data collection device 5 of the second embodiment can flexibly collect vehicle data before and after the collection condition is met while suppressing communication congestion and cost increases.

[0137] [Embodiment 3] The vehicle data collection device 5 of the third embodiment will be described with reference to Fig. 17. In the vehicle data collection device 5 of the third embodiment, the description of the same configuration and operation as those of the first embodiment will be omitted.

[0138] Fig. 17 is a diagram showing a schematic configuration of a vehicle data collection device 5 of embodiment 3. The dashed arrows shown in Fig. 17 indicate the flow of signals or data.

[0139] In the vehicle data collection device 5 of the third embodiment, the source of a request to collect vehicle data is an IVI (In-Vehicle Infotainment) ECU 120, which is an ECU mounted on a vehicle. That is, in the vehicle data collection system 1 of the third embodiment, the request unit 100 is provided in the IVI ECU 120, not in the server device 3.

[0140] The IVIECU 120 is connected by wire to the gateway ECU 15. The recording device 110 includes a CPU, a DRAM, a flash memory, and the like, and the CPU executes an IVI control program to realize the function of the request unit 100.

[0141] In the vehicle data collecting device 5 of the third embodiment, the receiving unit 30 of the communication function 20 implemented in the gateway ECU 15 receives a vehicle data collection request transmitted from the IVIECU 120 and transmits the request to the setting unit 40 of the setting function 21 implemented in the gateway ECU 15. In the vehicle data collecting device 5 of the third embodiment, the determination function 22 implemented in the autonomous driving ECU 14 sets determination data and collection conditions based on the collection settings, and the collection function 23 implemented in the autonomous driving ECU 14 sets and stores collected data based on the collection settings. In the vehicle data collecting device 5 of the third embodiment, the transmission standby unit 60 of the standby function 24 implemented in the autonomous driving ECU 14 causes the stored collected data to wait. In the vehicle data collecting device 5 of the third embodiment, the transmitting unit 31 of the communication function 20 implemented in the gateway ECU 15 transmits the collected data waited for by the transmission standby unit 60 to the IVIECU 120.

[0142] As a result, the vehicle data collection device 5 of the third embodiment can collect vehicle data using another ECU mounted on the vehicle 4 even if no new device is provided outside the vehicle 4. Therefore, the vehicle data collection device 5 of the third embodiment can flexibly collect vehicle data before and after the collection condition is met while suppressing communication congestion and cost increases, even if no new device is provided outside the vehicle 4.

[0143] [Embodiment 4] The vehicle data collection device 5 of the fourth embodiment will be described with reference to Figures 18 and 19. In the vehicle data collection device 5 of the fourth embodiment, the description of the same configuration and operation as in the first embodiment will be omitted.

[0144] FIG. 18 is a diagram showing the functional configuration of the vehicle data collection device 5 according to the fourth embodiment.

[0145] The vehicle data collection device 5 of the fourth embodiment further includes a primary determination function 300 that determines, prior to the determination function 22, whether the primary vehicle data collection condition is met.

[0146] The primary determination function 300 is implemented in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the autonomous driving ECU 14, or the gateway ECU 15. The primary determination function 300 is configured by a CPU, a memory, and a primary determination program included in the powertrain ECU 11, the brake ECU 12, the steering ECU 13, the autonomous driving ECU 14, or the gateway ECU 15.

[0147] The primary determination function 300 includes a primary collection condition determination unit 302 that sets primary collection conditions for vehicle data based on the collection settings determined by the setting unit 40 and determines whether the set primary collection conditions are met prior to the determination by the collection condition determination unit 51. Furthermore, the primary determination function 300 includes a primary determination data output unit 301 that sets vehicle data to be determined when the primary collection condition determination unit 302 determines whether the primary collection conditions are met as primary determination data based on the collection settings, and acquires and outputs the set primary determination data from the ECU.

[0148] The primary collection condition determination unit 302 determines whether or not the set primary collection conditions are met for the primary judgment data output by the primary judgment data output unit 301. If the primary collection condition determination unit 302 determines that the primary collection conditions are met, it transmits a primary met condition indicating the met primary collection condition to the collection condition determination unit 51. Upon receiving the primary met condition, the collection condition determination unit 51 starts to determine whether or not the collection conditions are met.

[0149] Fig. 19 is a diagram showing an example of the operation of the vehicle data collection device 5 shown in Fig. 18. Fig. 19 shows an example of collecting image data received from the camera 9 when a deterioration in electricity efficiency occurs at a red light in order to improve the efficiency of autonomous driving.

[0150] The primary judgment data output unit 301 implemented in the autonomous driving ECU 14 sets the signal color as the primary judgment data. The primary collection condition determination unit 302 implemented in the autonomous driving ECU 14 sets the primary collection condition so that when the signal color turns red, it is determined that the signal is a red light. The judgment data output unit 50 implemented in the powertrain ECU 11 sets the power consumption of the motor 6 as the judgment data. The collection condition determination unit 51 implemented in the powertrain ECU 11 sets the collection condition so that when the power consumption of the motor 6 reaches a predetermined level or more, it determines that a deterioration in electricity efficiency has occurred, and also sets the collection condition so that when a red light is received, a determination of the power consumption is started as a primary satisfaction condition. The collected data output unit 52 implemented in the autonomous driving ECU 14 sets image data received from the camera 9 as the collected data. As a result, the vehicle data collection device 5 shown in FIG. 19 can collect image data when a deterioration in electricity efficiency occurs at a red light.

[0151] As described above, the vehicle data collection device 5 of the fourth embodiment further includes a primary determination function 300 that determines whether the primary collection condition for vehicle data is satisfied prior to the determination function 22. As a result, even when the determination data required to determine whether the collection condition is satisfied spans multiple ECUs, the vehicle data collection device 5 of the fourth embodiment can reliably determine whether the collection condition is satisfied without transmitting or receiving the determination data itself between ECUs. Therefore, the vehicle data collection device 5 of the fourth embodiment can flexibly and reliably collect vehicle data before and after the collection condition is satisfied while suppressing communication congestion and cost increases.

[0152] [Embodiment 5] The vehicle data collection device 5 of the fifth embodiment will be described with reference to Fig. 20. In the vehicle data collection device 5 of the fifth embodiment, the description of the same configuration and operation as those of the first embodiment will be omitted.

[0153] FIG. 20 is a timing chart illustrating the vehicle data collection device 5 of the fifth embodiment.

[0154] Even if the vehicle data collection device 5 of the fifth embodiment receives a new collection request R2 from another server device while collecting vehicle data based on a collection request R1 from the server device 3, the vehicle data collection device 5 does not respond to the new collection request R2 and rejects the collection request R2. Then, when the vehicle data collection device 5 of the fifth embodiment receives a new collection request R3 after receiving a cancellation of the collection request R1, the vehicle data collection device 5 starts collecting vehicle data based on the collection request R3. That is, after receiving a notification of the cancellation of the collection request R1 from the request source, the setting unit 40 of the vehicle data collection device 5 of the fifth embodiment determines new collection settings so as to collect vehicle data in accordance with the new collection request R3.

[0155] As a result, the vehicle data collection device 5 of the fifth embodiment can prevent the collection settings from being overwritten without the knowledge of the administrator. Therefore, the vehicle data collection device 5 of the fifth embodiment can flexibly and reliably collect vehicle data before and after the collection condition is satisfied while suppressing communication congestion and cost increases.

[0156] [Embodiment 6] The vehicle data collection device 5 of the sixth embodiment will be described with reference to Fig. 21. In the vehicle data collection device 5 of the sixth embodiment, the description of the same configuration and operation as those of the first embodiment will be omitted.

[0157] FIG. 21 is a diagram showing the functional configuration of the vehicle data collection device 5 of the sixth embodiment.

[0158] In the vehicle data collection device 5 of the sixth embodiment, the collection function 23 further includes a transmission in progress determination unit 400 and a power supply unit 401 in addition to the collected data output unit 52 and the multistage holding unit 53. The transmission in progress determination unit 400 determines whether the collected data (held data) held in the multistage holding unit 53 is being transmitted to the transmission standby unit 60, and transmits the determination result to the power supply unit 401. The power supply unit 401 supplies power to the memory constituting the multistage holding unit 53. When the power supply unit 401 receives from the transmission in progress determination unit 400 a determination result indicating that the collected data held in the multistage holding unit 53 is being transmitted to the transmission standby unit 60 (hereinafter also referred to as "transmission in progress determination"), the power supply unit 401 continues to supply power to the memory constituting the multistage holding unit 53.

[0159] As a result, even if the power supply to the vehicle 4 is turned off before the transmission of the collected data stored in the multi-stage storage unit 53 including a volatile memory is completed, the vehicle data collection device 5 of the sixth embodiment can prevent the collected data from being lost due to a cutoff in the power supply to the multi-stage storage unit 53. Therefore, the vehicle data collection device 5 of the sixth embodiment can flexibly and reliably collect vehicle data before and after the collection condition is satisfied while suppressing communication congestion and cost increases.

[0160] [Embodiment 7] The vehicle data collection device 5 of the seventh embodiment will be described with reference to Fig. 22. In the vehicle data collection device 5 of the seventh embodiment, the description of the same configuration and operation as in the first embodiment will be omitted.

[0161] FIG. 22 is a diagram showing the functional configuration of the vehicle data collection device 5 of the seventh embodiment.

[0162] The vehicle data collection device 5 of the seventh embodiment further includes another multi-stage holding unit different from the multi-stage holding unit 53. The collected data output unit 52 of the seventh embodiment transmits collected data to the other multi-stage holding unit when the capacity of the memory constituting the multi-stage holding unit 53 is insufficient.

[0163] 22 shows an example in which the collection function 23 is implemented in the autonomous driving ECU 14 and the powertrain ECU 11, and the memory capacity of the multi-stage storage unit 53 implemented in the autonomous driving ECU 14 is insufficient for the capacity required to execute a collection request. In this case, in the vehicle data collection device 5 of the seventh embodiment, the collected data output unit 52 implemented in the autonomous driving ECU 14 can transmit collected data to the multi-stage storage unit 53 implemented in the powertrain ECU 11.

[0164] As a result, the vehicle data collection device 5 of the seventh embodiment can reliably hold and collect vehicle data even when there is insufficient capacity in the memory constituting the multi-stage holding unit 53. Therefore, the vehicle data collection device 5 of the seventh embodiment can flexibly and reliably collect vehicle data before and after the collection condition is satisfied while suppressing communication congestion and cost increases.

[0165] [Embodiment 8] The vehicle data collection device 5 of the eighth embodiment will be described with reference to Fig. 23. In the vehicle data collection device 5 of the eighth embodiment, the description of the same configuration and operation as in the first embodiment will be omitted.

[0166] FIG. 23 is a diagram showing the functional configuration of the vehicle data collection device 5 according to the eighth embodiment.

[0167] In the vehicle data collection device 5 of the eighth embodiment, the collected data output unit 52 transmits collected data to the transmission standby unit 60 when the capacity of the memory constituting the multi-stage holding unit 53 is insufficient.

[0168] 23 shows an example in which the collection function 23 is implemented in the autonomous driving ECU 14, and the memory capacity of the multi-stage holding unit 53 implemented in the autonomous driving ECU 14 is insufficient for the capacity required to execute the collection request. In this case, in the vehicle data collection device 5 of the eighth embodiment, the collected data output unit 52 implemented in the autonomous driving ECU 14 can transmit the collected data to the transmission standby unit 60.

[0169] As a result, the vehicle data collecting device 5 of embodiment 8 can reliably transmit and collect vehicle data to the transmission standby unit 60 even when the capacity of the memory constituting the multi-stage holding unit 53 is insufficient. Therefore, the vehicle data collecting device 5 of embodiment 7 can flexibly and reliably collect vehicle data before and after the collection condition is met while suppressing communication congestion and cost increases.

[0170] [Embodiment 9] The vehicle data collection system 1 of the ninth embodiment will be described with reference to Figures 24 and 25. In the vehicle data collection system 1 of the ninth embodiment, the description of the same configuration and operation as in the first embodiment will be omitted.

[0171] Fig. 24 is a diagram showing a schematic configuration of a vehicle data collection system 1 of embodiment 9. The dashed arrows shown in Fig. 24 indicate the flow of signals or data.

[0172] The vehicle data collection device 5 of the ninth embodiment serializes the collection settings determined by the setting unit 40 to calculate a collection setting byte sequence and transmits the same to the server device 3 via a mobile phone communication network. The server device 3 deserializes each of the multiple collection setting byte sequences received from multiple vehicles including the vehicle 4 to restore the multiple collection settings. The server device 3 then performs statistical processing on the multiple collection settings and transmits the statistical processing results to the terminal device 2. The terminal device 2 visualizes the statistical processing results transmitted from the server device 3 and displays them on the display of the terminal device 2.

[0173] FIG. 25 is a diagram showing the functional configuration of the vehicle data collection system 1 shown in FIG.

[0174] The vehicle data collection device 5 of embodiment 9 further includes, as the communication function 20, a collection setting transmission unit 500 that transmits the collection setting determined by the setting unit 40 to the server device 3. The server device 3 of embodiment 9 further includes a collection setting reception unit 501 that receives a plurality of collection settings transmitted from the vehicle data collection devices 5 mounted on a plurality of vehicles, a statistical processing unit 502 that performs statistical processing on the plurality of collection settings, and a statistical processing result transmission unit 503 that transmits the statistical processing result of the statistical processing unit 502 to the terminal device 2.

[0175] As a result, even if the vehicle data collection system 1 of the ninth embodiment determines collection settings by changing the content of the collection request so that the vehicle data collection device 5 can execute the collection program of the collection function 23, the vehicle data collection system 1 can make the administrator aware of the multiple collection settings whose content has been changed in multiple vehicles including the vehicle 4 before the collection of vehicle data is completed. Therefore, the vehicle data collection system 1 of the ninth embodiment can flexibly collect vehicle data before and after the collection conditions are met while suppressing communication congestion and cost increases, and can improve user convenience.

[0176] 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, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0177] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely realized by hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be realized by software, in which a processor interprets and executes a program that realizes each function. Information such as the program, tape, and file that realizes each function can be stored in a memory, a recording device such as a hard disk or solid state drive (SSD), or a recording medium such as an IC card, SD card, or DVD.

[0178] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0179] 1...vehicle data collection system, 2...terminal device, 3...server device, 4...vehicle, 5...vehicle data collection device, 31...transmission unit, 40...setting unit, 50...judgment data output unit, 51...collection condition judgment unit, 52...collection data output unit, 53...multistage holding unit, 60...transmission standby unit, 100...request unit, 110...recording device, 120...IVIECU, 301...primary judgment data output unit, 302...primary collection condition judgment unit, 400...transmission in progress judgment unit, 401...power supply unit, 500...collection setting transmission unit, 501...collection setting reception unit, 502...statistical processing unit, 503...statistical processing result transmission unit

Claims

1. A vehicle data collection device that collects vehicle data from an electronic control unit in response to a vehicle data collection request, a setting unit that determines collection settings, which are setting information for the electronic control device in response to the collection request; a collection condition determination unit that sets a collection condition for the vehicle data based on the collection setting and determines whether the set collection condition is met; a collected data output unit that sets collected data, which is the vehicle data to be collected, based on the collection setting, and acquires and outputs the set collected data from the electronic control unit; a multi-stage storage unit that stores the collected data output before the collection condition is met and the collected data output after the collection condition is met, based on the collection setting; a transmission standby unit that waits for transmission of the collected data held in the multistage holding unit to a source of the collection request; a transmission unit that transmits the collected data that has been queued in the transmission queue unit to the request source, The collection request: The setting value relating to the number of collected data to be held in the multi-stage holding unit includes a first setting value relating to the number of collected data to be held in the multi-stage holding unit that is output before the collection condition is met, and a second setting value relating to the number of collected data to be held in the multi-stage holding unit that is output after the collection condition is met, a front-to-back priority setting for setting which of the collected data output before the establishment of the collection condition and the collected data output after the establishment of the collection condition is to be held with priority in the multi-stage holding unit; The setting unit determines the collection setting so as to change the number of data held by the multi-stage holding unit by changing at least one of the first setting value and the second setting value based on the capacity of a memory constituting the multi-stage holding unit and the front-to-back priority. A vehicle data collection device characterized by:

2. A vehicle data collection device that collects vehicle data from an electronic control unit in response to a request to collect the vehicle data, a setting unit that determines collection settings, which are setting information for the electronic control device in response to the collection request; a collection condition determination unit that sets a collection condition for the vehicle data based on the collection setting and determines whether the set collection condition is met; a collected data output unit that sets collected data, which is the vehicle data to be collected, based on the collection setting, and acquires and outputs the set collected data from the electronic control unit; a multi-stage storage unit that stores the collected data output before the collection condition is met and the collected data output after the collection condition is met, based on the collection setting; a transmission standby unit that waits for transmission of the collected data held in the multistage holding unit to a source of the collection request; a transmission unit that transmits the collected data that has been queued in the transmission queue unit to the request source, The collection request: The setting value relating to the number of collected data to be held in the multi-stage holding unit includes a first setting value relating to the number of collected data to be held in the multi-stage holding unit that is output before the collection condition is met, and a second setting value relating to the number of collected data to be held in the multi-stage holding unit that is output after the collection condition is met, the multi-stage storage unit includes a format priority setting whether to prioritize maintaining the storage format of the collected data set by the first setting value and the second setting value; The setting unit determines the collection setting so as to change the number of data held by the multi-stage holding unit by changing at least one of the first setting value and the second setting value based on the capacity of a memory constituting the multi-stage holding unit and the format priority. A vehicle data collection device characterized by:

3. the format priority includes a format priority that prioritizes maintaining the storage format of the collected data set by the first setting value and the second setting value, and a format non-priority that does not prioritize maintaining the storage format of the collected data set by the first setting value and the second setting value, When the format priority is the format priority and it is difficult to maintain the storage format of the collected data set by the first setting value and the second setting value, the setting unit determines the collection setting to exclude the collected data from collection targets.

3. The vehicle data collection device according to claim 2.

4. The multi-stage holding portion includes: the collected data output unit outputs the collected data to the storage unit, and the stored collected data is updated every predetermined operation cycle by deleting the stored collected data in order from the oldest collected data and sequentially storing the collected data output from the storage unit, and When a predetermined number of operation cycles have elapsed since the collection condition was met, the update of the held data is stopped and the held data is transmitted to the transmission standby unit; the transmission standby unit stores the held data transmitted from the multistage holding unit and waits until communication with the request source is established; When communication with the request source is established, the transmission unit transmits the standby data of the transmission standby unit, which is the held data stored in the transmission standby unit, to the request source.

3. The vehicle data collection device according to claim 1 or 2.

5. the collection condition determination unit is capable of determining whether each of the plurality of collection conditions is satisfied; the collection request includes a condition priority that sets which of the plurality of collection conditions is to be given priority in order to store the collected data in the multi-stage storage unit; The setting unit determines the collection setting so as to change the number of data held by the multi-stage holding unit by changing at least one of the first setting value and the second setting value based on the capacity of a memory constituting the multi-stage holding unit and the condition priority.

3. The vehicle data collection device according to claim 1 or 2.

6. a primary collection condition determination unit that sets a primary collection condition for the vehicle data based on the collection setting and determines whether the set primary collection condition is met prior to a determination by the collection condition determination unit; The collection condition determination unit starts determining whether the collection condition is satisfied when the primary collection condition determination unit determines that the primary collection condition is satisfied.

3. The vehicle data collection device according to claim 1 or 2.

7. The setting unit determines new collection settings so as to collect the vehicle data in response to a new collection request after the request source notifies the cancellation of the collection request.

3. The vehicle data collection device according to claim 1 or 2.

8. a transmission determination unit that determines whether the collected data held in the multistage holding unit is being transmitted to the transmission standby unit; a power supply unit that supplies power to the memory that constitutes the multi-stage holding unit, The power supply unit continues to supply power to the memory when it is determined that the collected data held in the multi-stage holding unit is being transmitted to the transmission standby unit.

3. The vehicle data collection device according to claim 1 or 2.

9. When the capacity of the memory constituting the multistage holding unit is insufficient, the collected data output unit transmits the collected data to another multistage holding unit different from the multistage holding unit.

3. The vehicle data collection device according to claim 1 or 2.

10. The collected data output unit transmits the collected data to the transmission standby unit when the capacity of the memory constituting the multi-stage holding unit is insufficient.

3. The vehicle data collection device according to claim 1 or 2.

11. The request source is at least one of a server device provided outside the vehicle in which the electronic control device is mounted, a recording device connected to the vehicle, and another electronic control device mounted in the vehicle and different from the electronic control device.

3. The vehicle data collection device according to claim 1 or 2.

12. A vehicle data collection system including: a server device that requests a vehicle to collect vehicle data; and a vehicle that collects the vehicle data from an electronic control unit of the vehicle in response to a request from the server device, The server device a request unit that generates a collection request for the vehicle data and transmits the generated collection request to the vehicle; The vehicle is a setting unit that determines collection settings, which are setting information for the electronic control device in response to the collection request; a collection condition determination unit that sets a collection condition for the vehicle data based on the collection setting and determines whether the set collection condition is met; a collected data output unit that sets collected data, which is the vehicle data to be collected, based on the collection setting, and acquires and outputs the set collected data from the electronic control unit; a multi-stage storage unit that stores the collected data output before the collection condition is met and the collected data output after the collection condition is met, based on the collection setting; a transmission standby unit that waits for transmission of the collected data held in the multistage holding unit to a source of the collection request; a transmission unit that transmits the collected data that has been queued in the transmission queue unit to the request source, The collection request: The setting value relating to the number of collected data to be held in the multi-stage holding unit includes a first setting value relating to the number of collected data to be held in the multi-stage holding unit that is output before the collection condition is met, and a second setting value relating to the number of collected data to be held in the multi-stage holding unit that is output after the collection condition is met, a front-to-back priority setting for setting which of the collected data output before the establishment of the collection condition and the collected data output after the establishment of the collection condition is to be held with priority in the multi-stage holding unit; The setting unit determines the collection setting so as to change the number of data held by the multi-stage holding unit by changing at least one of the first setting value and the second setting value based on the capacity of a memory constituting the multi-stage holding unit and the front-to-back priority. A vehicle data collection system comprising:

13. A vehicle data collection system having a server device that requests a vehicle to collect vehicle data, and a vehicle that collects the vehicle data from an electronic control unit of the vehicle in response to a request from the server device, The server device a request unit that generates a collection request for the vehicle data and transmits the generated collection request to the vehicle; The vehicle is a setting unit that determines collection settings, which are setting information for the electronic control device in response to the collection request; a collection condition determination unit that sets a collection condition for the vehicle data based on the collection setting and determines whether the set collection condition is met; a collected data output unit that sets collected data, which is the vehicle data to be collected, based on the collection setting, and acquires and outputs the set collected data from the electronic control unit; a multi-stage storage unit that stores the collected data output before the collection condition is met and the collected data output after the collection condition is met, based on the collection setting; a transmission standby unit that waits for transmission of the collected data held in the multistage holding unit to a source of the collection request; a transmission unit that transmits the collected data that has been queued in the transmission queue unit to the request source, The collection request: The setting value relating to the number of collected data to be held in the multi-stage holding unit includes a first setting value relating to the number of collected data to be held in the multi-stage holding unit that is output before the collection condition is met, and a second setting value relating to the number of collected data to be held in the multi-stage holding unit that is output after the collection condition is met, the multi-stage storage unit includes a format priority setting whether to prioritize maintaining the storage format of the collected data set by the first setting value and the second setting value; The setting unit determines the collection setting so as to change the number of data held in the multi-stage holding unit by changing at least one of the first setting value and the second setting value based on the capacity of a memory constituting the multi-stage holding unit and the format priority. A vehicle data collection system comprising:

14. The system further includes a terminal device communicably connected to the server device, the vehicle further includes a collection setting transmission unit that transmits the collection setting to the server device; The server device a collection setting receiving unit that receives the plurality of collection settings transmitted from the plurality of vehicles; a statistical processing unit that performs statistical processing on the plurality of collection settings; a statistical processing result transmission unit that transmits the statistical processing result of the statistical processing unit to the terminal device, The terminal device displays the statistical processing result transmitted from the server device.

14. The vehicle data collection system according to claim 12 or 13.

Images