JP7236842B2 - Data collection device, data collection system and data collection method - Google Patents

Description

The disclosed embodiments relate to data collection devices, data collection systems and data collection methods.

2. Description of the Related Art Conventionally, a data collection device is known that collects road information from an in-vehicle device mounted on each vehicle. Such a data collection device collects road information for a desired position by selecting vehicles for which road information is to be collected based on the position information of each vehicle (see, for example, Patent Document 1).

JP 2018-055581 A

However, the conventional technology described above has room for further improvement in terms of efficiently collecting information in response to changes in the state of the vehicle.

Specifically, in the conventional technology described above, a user connects to the center device via a terminal and arbitrarily designates collection conditions such as upload conditions from a user interface on the center device. However, since the state of the vehicle always changes, when the information desired by the user changes according to the change of the state, it is necessary to specify the collection conditions mentioned above each time.

One aspect of the embodiments is to provide a data collection device, a data collection system, and a data collection method capable of efficiently collecting information in response to changes in vehicle state. With the goal.

A data collection device according to an aspect of an embodiment includes a collection unit and a setting unit. The collection unit collects predetermined data about the vehicle from an in-vehicle device mounted in each vehicle. The setting unit sets conditions for collecting vehicle-related data to be collected from the in-vehicle device by the collecting unit according to changes in the predetermined data collected by the collecting unit. Further, the collection unit collects predetermined data from the vehicle-mounted device at predetermined intervals longer than the data collection period. Further, the setting unit sets an in-vehicle device as a data collection target based on the amount of change in the predetermined data in the predetermined period, and collects the data according to the result of comparison between the amount of change in the predetermined data and a predetermined threshold value. Set conditions. Further, a plurality of thresholds are provided according to the characteristics of the vehicle, and the setting unit determines the amount of change in the predetermined data collected from the in-vehicle device using the threshold corresponding to the characteristics of the vehicle equipped with the in-vehicle device. Compare and judge.

According to one aspect of the embodiment, it is possible to efficiently collect information in response to changes in the state of the vehicle.

FIG. 1A is a schematic explanatory diagram (part 1) of a data collection method according to an embodiment; FIG. 1B is a schematic explanatory diagram (part 2) of the data collection method according to the embodiment; FIG. 1C is a schematic explanatory diagram (part 3) of the data collection method according to the embodiment; FIG. 2 is a block diagram showing a configuration example of the data collection system according to the embodiment. FIG. 3A is a diagram (part 1) showing a specific example of setting information. FIG. 3B is a diagram (part 2) illustrating a specific example of setting information; FIG. 4 is a flowchart illustrating a processing procedure executed by the data collection system according to the embodiment;

Hereinafter, embodiments of a data collection device, a data collection system, and a data collection method disclosed in the present application will be described in detail with reference to the accompanying drawings. In addition, this invention is not limited by embodiment shown below.

First, an overview of the data collection method according to the embodiment will be described with reference to FIGS. 1A to 1C. 1A to 1C are schematic explanatory diagrams (Part 1) to (Part 3) of the data collection method according to the embodiment. 1A to 1C, the data collection system 1 to which the data collection method according to the embodiment is applied will be described as an example.

As shown in FIG. 1A, the data collection system 1 according to the embodiment includes a data collection device 10 and in-vehicle devices 100-1, 100-2 mounted on vehicles V-1, V-2, V-3, . , 100-3 . . . and the user terminal 200. In the following description, the vehicle in general is referred to as "vehicle V", and the in-vehicle device as a whole is referred to as "in-vehicle device 100".

The data collection device 10 is configured as a cloud server that provides a cloud service via a network N such as the Internet or a mobile phone network, for example. , collects vehicle data from each in-vehicle device 100 and provides it to data users.

The in-vehicle device 100 is, for example, a drive recorder having various sensors such as a camera, an acceleration sensor, and a GPS (Global Positioning System) sensor, a storage device, a microcomputer, and the like. Data is taken from vehicle V.

Also, the in-vehicle device 100 appropriately uploads the collected vehicle data to the data collection device 10 . By using the drive recorder as the in-vehicle device 100 in this way, the in-vehicle components mounted on the vehicle V can be made more efficient. It should be noted that the in-vehicle device 100 and the drive recorder may be configured separately without using them together.

The user terminal 200 is a terminal used by a data user, and is for example a notebook PC (Personal Computer), a desktop PC, a tablet terminal, a PDA (Personal Digital Assistant), a smart phone, an eyeglass type, or a watch type information processing device. Examples include a wearable device, which is a terminal.

A data user is, for example, a developer who develops automatic driving technology based on vehicle data provided from the data collection device 10 . The data collection device 10 provides the data user with a user interface (hereinafter referred to as “UI”) screen that can be accessed via the user terminal 200 .

The data user designates vehicle data collection conditions via the UI screen, as shown in FIG. 1A (step S1). Then, the data collection device 10 that has received this distributes the collection conditions to each vehicle V, for example, in a file format (step S2).

The collection conditions include various parameters related to collection of vehicle data. Various parameters include, for example, "target vehicle", "data type", "collection trigger condition", and "collection period".

The "target vehicle" is the identifier of the vehicle V to be collected. "Data type" is the type of data to be collected, in other words, the type of data collected from various sensors. Examples include the accelerator opening, brake pressure, steering angle, SOH (States Of Health: deterioration state of the battery), etc. included in CAN (Controller Area Network) information, and images captured by a camera. The "collection trigger condition" is a condition that triggers collection, and is, for example, when the vehicle speed exceeds a predetermined speed.

Then, each in-vehicle device 100 appropriately uploads the vehicle data collected from each vehicle V to the data collection device 10 (step S3), and the data collection device 10 accumulates this (step S4). Then, the data user browses or downloads the vehicle data accumulated in the data collection device 10 via the aforementioned UI screen, for example (step S5), and uses it for analysis for development.

Although not shown in FIG. 1A, the vehicle data uploaded by the in-vehicle device 100 includes actual data and tag data having characteristics as index data used for searching the actual data and grasping an overview of the actual data.

The tag data has a very small data capacity compared to the actual data. Therefore, each in-vehicle device 100 constantly uploads such tag data to the data collection device 10, for example. Then, for example, the data user can view the tag data through the user terminal 200 and cause the in-vehicle device 100 to upload only the actual data determined to be necessary to the data collection device 10 . This makes it possible to reduce the communication load. It is preferable that the tag data and the actual data that have been uploaded to the data collection device 10 are sequentially deleted from the in-vehicle device 100 .

In the following description, it is assumed that the vehicle data uploaded by the in-vehicle device 100 to the data collection device 10 is actual data.

By the way, the state of the vehicle V always changes. Therefore, for the data user, if the state of the vehicle V changes, the desired information often changes.

Specifically, it is assumed that a data user identifies a vehicle whose battery deteriorates quickly and wants to collect vehicle data related to grasping the battery consumption of such vehicle.

FIG. 1B shows the case according to the data collection method according to the comparative example. A data user monitors, for example, the SOH in determining deterioration of the battery. In the case of the comparative example, as shown in FIG. It is necessary to compare the SOH at each collection cycle s.

Further, when long-term comparison with an interval equal to or longer than the collection period s is required, it is necessary to extract and compare vehicle data to be compared from past collected data one by one. For this reason, it has been very troublesome for data users.

Therefore, in the data collection method according to the embodiment, when detecting a change in the state of the vehicle V, the data collection device 10 collects only vehicle data necessary for detecting such a change at predetermined intervals. . Also, collection conditions according to changes in the state of the vehicle V obtained from vehicle data collected thereby are automatically distributed to the in-vehicle device 100 .

Next, it is assumed that it is desired to identify a vehicle whose battery deteriorates quickly and to collect vehicle data related to grasping the battery consumption of such vehicle. Specifically, as shown in FIG. 1C, in the data collection method according to the embodiment, first, the data collection device 10 causes the in-vehicle device 100 to upload only necessary data after a predetermined period of time T (step S11). Here, a case is shown in which only the SOH is uploaded only at the beginning of the month.

Then, the data collection device 10 compares the collected vehicle data for each vehicle V, and selects a vehicle V whose amount of change diff exceeds a predetermined threshold value (that is, a vehicle V whose battery is determined to deteriorate quickly). , the new collection condition #1 is delivered to the in-vehicle device 100 (step S12-1). Here, the collection condition #1 is, for example, "to collect only data necessary for understanding battery consumption in February" as shown in FIG. The "data necessary for grasping the battery consumption" is, for example, the accelerator opening rate, the frequency of braking, the temperature of the air conditioner, and the like.

On the other hand, the data collection device 10 compares the collected vehicle data for each vehicle V, and as a result, for the vehicle V whose change amount diff is equal to or less than a predetermined threshold value (that is, it is determined that the battery does not deteriorate quickly). For the vehicle V), the new collection condition #2 is delivered to the in-vehicle device 100 (step S12-2). Here, the collection condition #2 is, for example, as shown in FIG. As a result, it is possible to efficiently collect the necessary vehicle data only from the vehicles V that are suitable as collection targets. Thus, "collection target/no" is also one of the collection conditions.

The processes of step S11, step S12-1 and step S12-2 can be executed based on setting information 12a (see FIG. 2) set in the data collecting device 10 in advance. A specific example of the setting information 12a will be described later with reference to FIGS. 3A and 3B.

As described above, in the data collection method according to the embodiment, when detecting a change in the state of the vehicle V, the data collection device 10 collects only the vehicle data necessary for detecting such a change at predetermined intervals. and Also, collection conditions according to changes in the state of the vehicle V obtained from vehicle data collected thereby are automatically distributed to the in-vehicle device 100 .

Therefore, according to the data collection method according to the embodiment, it is possible to save the time and effort of the data user and efficiently collect information according to the state change of the vehicle.

It should be noted that it is preferable that deletion of vehicle data for detecting changes in the state of the vehicle V is prohibited for a specific period longer than a predetermined period T at least after being collected. Referring to FIG. 1C, it is preferable that the SOH data at the beginning of each month is retained until at least the beginning of the next month after being collected. Note that the SOH data other than the beginning of the month may not be collected, for example, and may not be prohibited from being deleted even if it is collected.

Hereinafter, a configuration example of the data collection system 1 according to the embodiment will be described more specifically. FIG. 2 is a block diagram showing a configuration example of the data collection system 1 according to the embodiment. It should be noted that FIG. 2 shows only the constituent elements necessary for explaining the features of the embodiment, and omits the description of general constituent elements.

In other words, each component illustrated in FIG. 2 is functionally conceptual and does not necessarily need to be physically configured as illustrated. For example, the specific form of distribution/integration of each block is not limited to the one shown in the figure. It is possible to integrate and configure.

In addition, in the description using FIG. 2, the description of components that have already been described may be simplified or omitted.

As shown in FIG. 2 , the data collection system 1 according to the embodiment includes a data collection device 10 , an in-vehicle device 100 and a user terminal 200 .

First, the data collection device 10 will be described. The data collection device 10 includes a communication section 11 , a storage section 12 and a control section 13 .

The communication unit 11 is implemented by, for example, a NIC (Network Interface Card) or the like. The communication unit 11 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the in-vehicle device 100 and the user terminal 200 via the network N.

The storage unit 12 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. A collection data DB 12b and a collection condition information DB 12c are stored.

The setting information 12a is definition information relating to the execution of steps S11, S12-1, and S12-2 described above, and is set by the setting unit 13a, which receives setting contents from the user terminal 200, for example. A specific example of the setting information 12a will now be described with reference to FIGS. 3A and 3B. 3A and 3B are diagrams (Part 1) and (Part 2) showing specific examples of the setting information 12a.

As shown in FIG. 3A, the setting information 12a is, for example, preset information for each evaluation content desired by the data user, in which the evaluation period, collection data type, etc. are defined in advance for each evaluation content desired by the data user. be. Here, the desired content of evaluation may be rephrased as a change in the state of the vehicle V that is desired to be detected.

The setting information 12a includes, for example, an "evaluation content" item, an "evaluation period" item, a "collected data type" item, a "comparison condition" item, and a "delivery file" item.

The "evaluation content" item stores identification information indicating the evaluation content desired by the data user. Here, it is assumed that the "battery deterioration level" is stored according to the examples of FIGS. 1B and 1C.

The "evaluation period" item corresponds to the predetermined period T in FIG. 1C, and stores, for example, "beginning of the month". The "collected data type" item is the type of data collected at the beginning of the month. For example, FIG. 3A shows an example in which "SOH" is selected. The collection conditions corresponding to the "evaluation cycle" and "collection data type" are also reflected in the collection condition information DB 12c, which will be described later, by the setting unit 13a when setting the setting information 12a.

The "comparison condition" item includes, for example, "comparison object", "comparison time", and "threshold", which are items relating to comparison conditions for vehicle data collected at the beginning of the month. "Comparison target" relates to a comparison target of vehicle data, and includes, for example, "own vehicle only", "own vehicle + other vehicle", and "other vehicle only".

Here, "own vehicle only" compares the difference (measured value) in the state of the own vehicle V-1 at time t1 and time t2, as shown in FIG. 3B. value) and X2 (measured value at time t2) (X2-X1) is greater than the threshold value C (whether the state change is large), the next process is changed, that is, a new collection condition is set. determine whether or not to In other words, when the fluctuation amount is different from usual, it is determined that there is a possibility that some kind of abnormality has occurred.

In addition, as shown in FIG. 3B, "other vehicles only" indicates the difference in state between time t1 and time t2 of own vehicle V-1 (difference in measured values) and other vehicle V-2 (average of other vehicles, etc.). ) at time t3 and time t4 (the time interval is basically the same as time t1 to t2, but conversion is also possible). In this case, for example, the difference (X2-X1) between X1 (measured value at time t1) and X2 (measured value at t time t2) of own vehicle V-1 and Y3 (measured value at time t3) of other vehicle V-2 ) and the difference (Y4-Y3) between Y4 (measured value at time t4) ((Y4-Y3)-(X2-X1)) is greater than the threshold value D, that is, the state of the vehicle V-1 and the difference in the state of the other vehicle V-2 is large, the next processing will be changed. That is, when the amount of variation of the own vehicle V-1 is different from the amount of variation of the other vehicle V-2, it is determined that there is a possibility that some kind of abnormality has occurred. In consideration of the difference between vehicle models, conditions such as the same vehicle model and the same region may be added to the "other vehicle" to be compared.

For "own vehicle + other vehicle", the next process is changed depending on the OR condition of "own vehicle only" and "other vehicle only". In other words, if the amount of variation is different from usual, there is a possibility that something abnormal has occurred, or if the amount of variation of the subject vehicle V-1 is different from that of the other vehicle V-2, something abnormal has occurred. A judgment will be made as to whether it is possible.

Further, as shown in FIG. 3A, the "comparison time" indicates, for example, the effective range of time between vehicle data to be compared. It refers to being effective as a comparison target. It should be noted that this is merely an example, and does not limit the method of specifying the time-related condition.

The "threshold" is information about the threshold at the time of comparison, and stores, for example, a threshold condition for each "collected data type". As shown in FIG. 3A, when "SOH" is selected in the "collected data type", the column of SOH is referred to for the "threshold" and used to determine the amount of change diff (see FIG. 1C). Here, it is determined that the deterioration of the battery is early if the change amount diff is equal to or greater than a.

Also, although an example in which only one threshold condition for SOH is provided is shown here, different threshold conditions may be set for each type of vehicle, year of manufacture, and battery replacement time, for example. This makes it possible to detect a change in the state of the vehicle V according to the characteristics of the vehicle V and the battery.

The "distribution file" item is information relating to collection conditions distributed when the comparison condition is satisfied or when the condition is not satisfied. In FIG. 3A, only data types corresponding to the above-mentioned "data necessary for understanding battery consumption" including at least "accelerator opening rate", "brake frequency" and "air conditioner temperature" are included in "when condition is met". is selected. Further, an example is shown in which the data type corresponding to these "data necessary for grasping the battery consumption" is not selected for "when the condition is not met".

Based on the "distribution file" item, a distribution file of the collection condition "when the condition is satisfied" or "when the condition is not satisfied" is generated by the generation unit 13d, which will be described later.

Returning to the description of FIG. 2, the collected data DB 12b will be described. The collected data DB 12b accumulates collected data collected from each in-vehicle device 100 by a later-described collecting unit 13b. That is, the collected data DB 12b includes the past record of collected data. Collected data includes the aforementioned tag data and actual data.

The collection condition information DB 12c stores and accumulates distribution files including collection conditions specified by the setting unit 13a or the generation unit 13d. In other words, the collection condition information DB 12c includes past records regarding collection conditions.

The control unit 13 is a controller, and various programs stored in a storage device inside the data collection device 10 are stored in the RAM as a work area by, for example, a CPU (Central Processing Unit) or MPU (Micro Processing Unit). It is realized by executing as Also, the control unit 13 can be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 13 has a setting unit 13a, and the setting unit 13a has a collection unit 13b, a determination unit 13c, a generation unit 13d, and a distribution unit 13e. Realize or perform an action.

The setting unit 13a receives setting contents specified by the data user from the user terminal 200 via the communication unit 11, and sets them in the setting information 12a. In addition, the setting unit 13a generates a distribution file reflecting the content corresponding to the collection condition among the setting contents specified by the data user, and stores the distribution file in the collection condition information DB 12c.

The collection unit 13b collects the vehicle data uploaded from the in-vehicle device 100 via the communication unit 11 and accumulates them in the collected data DB 12b.

The determination unit 13c refers to the setting information 12a, extracts and compares vehicle data to be compared for detecting the state of the vehicle V for each vehicle V from the data stored in the collected data DB 12b. Further, the determination unit 13c notifies the generation unit 13d of a determination result indicating whether or not the comparison condition is established as a result of the comparison, that is, whether or not a desired change in the state of the vehicle V is detected. The determination result includes the contents of the "distribution file" item shown in FIG. 3A.

The generation unit 13d generates a distribution file including collection conditions according to the change in the state of the vehicle V based on the determination result of the determination unit 13c, and stores it in the collection condition information DB 12c.

The distribution unit 13e distributes the distribution file including the collection conditions stored in the collection condition information DB 12c to the vehicle V, which is the target vehicle, via the communication unit 11. FIG.

Next, the in-vehicle device 100 will be described. The in-vehicle device 100 includes a communication section 101 , a storage section 102 and a control section 103 . In addition, as described above, the in-vehicle device 100 is connected to various sensors 150 such as a camera, an acceleration sensor, and a GPS sensor.

Like the communication unit 11, the communication unit 101 is implemented by, for example, a NIC. The communication unit 101 is wirelessly connected to the network N, and transmits and receives information to and from the data collection device 10 via the network N. The communication unit 101 also receives output data from various sensors 150 .

The storage unit 102, like the storage unit 12, is realized by, for example, a semiconductor memory device such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk. Data information 102b is stored.

The collection condition information 102a is information including the collection conditions distributed from the data collection device 10. FIG. The vehicle data information 102b is information including vehicle data collected by the collecting unit 103c, which will be described later. Vehicle data includes the aforementioned tag data and actual data.

Like the control unit 13, the control unit 103 is a controller, and is realized by, for example, executing various programs stored in a storage device inside the in-vehicle device 100 using a RAM as a work area by a CPU, MPU, or the like. be done. Also, the control unit 103 can be realized by an integrated circuit such as an ASIC or FPGA, for example.

The control unit 103 includes an acquisition unit 103a, a detection unit 103b, a collection unit 103c, and an upload unit 103d, and implements or executes information processing functions and actions described below.

The acquisition unit 103a acquires the collection conditions distributed from the data collection device 10 and stores them in the collection condition information 102a. The detection unit 103b monitors the output data from the various sensors 150 and detects the occurrence of an event that serves as a trigger under the collection conditions.

For example, the detection unit 103b causes the collection unit 103c to collect vehicle data when detecting the occurrence of an event that triggers collection of vehicle data under the collection condition. Further, for example, the detection unit 103b causes the upload unit 103d to upload the vehicle data when detecting the occurrence of an event that serves as a trigger for uploading the vehicle data to the data collection device 10 under the collection conditions.

The collecting unit 103c collects vehicle data based on the output data of the various sensors 150 and stores the vehicle data in the vehicle data information 102b when the detection unit 103b detects the occurrence of a trigger for collecting vehicle data. Further, the collection unit 103c stops collection of vehicle data when the detection unit 103b detects generation of a trigger for stopping collection of vehicle data.

The upload unit 103d uploads the vehicle data stored in the vehicle data information 102b to the data collection device 10 when the detection unit 103b detects the occurrence of a trigger for uploading the vehicle data.

Next, a processing procedure executed by the data collection system 1 according to the embodiment will be described with reference to FIG. 4 . FIG. 4 is a flow chart showing a processing procedure executed by the data collection system 1 according to the embodiment.

First, the collection unit 13b acquires vehicle data (step S101). The vehicle data referred to here is vehicle data for detecting the state of the vehicle V, which is set in the setting information 12a.

Then, the determination unit 13c compares the vehicle data based on the setting information 12a (step S102). As a result, when the comparison condition is satisfied (step S103, Yes), the generation unit 13d generates a collection condition file when the condition is satisfied for the corresponding vehicle V (step S104).

On the other hand, if the comparison condition is not satisfied (step S103, No), the generation unit 13d generates a collection condition file for when the condition is not satisfied for the corresponding vehicle V (step S105).

Then, the distribution unit 13e distributes the corresponding collection condition file for each vehicle V (step S106), and ends the process.

As described above, the data collection device 10 according to the embodiment includes the collection unit 13b and the setting unit 13a. The collecting unit 13b collects predetermined data about the vehicle V from the in-vehicle device 100 mounted on each vehicle V. FIG. The setting unit 13a sets conditions for collecting data about the vehicle V to be collected from the in-vehicle device 100 by the collection unit 13b in accordance with changes in the predetermined data collected by the collection unit 13b.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to efficiently collect information according to the state change of the vehicle V. FIG.

Further, the setting unit 13a generates a collection condition corresponding to each in-vehicle device 100 according to a change in the predetermined data collected by the collection unit 13b, and distributes it to each in-vehicle device 100. FIG.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to individually distribute the collection conditions according to the state change of the vehicle V to each of the in-vehicle devices 100 . That is, it is possible to collect information efficiently according to the state change of the vehicle V. FIG. In addition, it is possible to automate the setting of the collection conditions according to the state change of the vehicle V, so that the burden on the setting person can be reduced.

In addition, the collecting unit 13b collects predetermined data from the in-vehicle device 100 with a predetermined period T longer than the data collection cycle, and the setting unit 13a collects the data based on the amount of change diff of the predetermined data in the predetermined period T. The in-vehicle device 100 to be collected is set.

Therefore, according to the data collection device 10 according to the embodiment, the amount of change diff can be easily determined based on the collected data after the predetermined period T without depending on the vehicle data for each collection period, and the data can be collected. The in-vehicle device 100 can be configured.

Further, the setting unit 13a sets the data collection condition according to the comparison result between the change amount diff of the predetermined data and a predetermined threshold value.

Therefore, according to the data collection device 10 according to the embodiment, it is also possible to set a collection condition that unnecessary data collection is not performed for unnecessary vehicles V according to the result of comparison with a predetermined threshold value. , which can contribute to the reduction of the communication load.

A plurality of thresholds are provided according to the characteristics of the vehicle V, and the setting unit 13a sets the amount of change diff of the predetermined data collected from the vehicle-mounted device 100 to the characteristics of the vehicle V equipped with the vehicle-mounted device 100. Determination is made using the above threshold.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to detect changes in the state of the vehicle V according to the characteristics of the vehicle V. FIG.

Further, the setting unit 13a sets the vehicle V-1 (corresponding to an example of "one vehicle") to the other vehicle V-2 (corresponding to an example of "another vehicle other than the one vehicle"). A threshold is set according to the amount of data change.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to judge that there is a possibility that some kind of abnormality has occurred according to the comparison result with the other vehicle V-2.

In the above-described embodiment, as an example of detecting the state of the vehicle V, the example of detecting that the battery is deteriorating quickly was given, but this is only an example, and the detection of the state of the vehicle V is not limited. .

For example, if it is desired to detect a change in the state of the vehicle V when driving is rough as a driving characteristic of the driver, the accelerator opening rate, brake pressure, number of brakes, steering angle, etc. are collected as vehicle data, and the rate of change of these is calculated. is steeper than a predetermined threshold, it may be determined that the driving is rough. On the other hand, it may be determined that the driving is calm when it is equal to or less than the threshold. Of course, in such a case as well, the threshold conditions may be varied for each type of vehicle V, for example.

Further, in the above-described embodiment, the data user is assumed to be a developer of automatic driving technology, etc., but it is an example of a user, such as a corporate user such as a service provider, or a general individual user. good too.

Further effects and modifications can be easily derived by those skilled in the art. Therefore, the broader aspects of the invention are not limited to the specific details and representative embodiments so shown and described. Accordingly, various changes may be made without departing from the spirit or scope of the general inventive concept defined by the appended claims and equivalents thereof.

1 data collection system 10 data collection device 12a setting information 12b collection data DB
12c Collection condition information DB
13a setting unit 13b collection unit 13c determination unit 13d generation unit 13e distribution unit 100 in-vehicle device 102a collection condition information 102b vehicle data information 103a acquisition unit 103b detection unit 103c collection unit 103d upload unit 150 various sensors 200 user terminal V vehicle

Claims (7)

a collection unit that collects predetermined data about the vehicle from an in-vehicle device mounted in each vehicle;
a setting unit that sets collection conditions for vehicle-related data to be collected by the collection unit from an in-vehicle device according to changes in the predetermined data collected by the collection unit ;
The collection unit is
collecting predetermined data from the in-vehicle device at predetermined intervals longer than the data collection cycle;
The setting unit
setting an in-vehicle device as a data collection target based on the amount of change in predetermined data in a predetermined period;
setting data collection conditions according to a result of comparison between the amount of change in predetermined data and a predetermined threshold;
The threshold is
Multiple are provided according to the characteristics of the vehicle,
The setting unit
The amount of change in the predetermined data collected from the in-vehicle device is compared and determined using the threshold corresponding to the characteristics of the vehicle equipped with the in-vehicle device.
A data collection device characterized by: a collection unit that collects predetermined data about the vehicle from an in-vehicle device mounted in each vehicle;
a setting unit that sets conditions for collecting vehicle-related data to be collected from an in-vehicle device by the collecting unit according to changes in the predetermined data collected by the collecting unit;
with
The collection unit is
collecting predetermined data from the in-vehicle device at predetermined intervals longer than the data collection cycle;
The setting unit
setting an in-vehicle device as a data collection target based on the amount of change in predetermined data in a predetermined period;
setting data collection conditions according to a result of comparison between the amount of change in predetermined data and a predetermined threshold;
For one vehicle, the threshold is set according to the amount of change in predetermined data in vehicles other than the one vehicle.
A data collection device characterized by: The setting unit
3. The data collection according to claim 1 or 2 , wherein a collection condition corresponding to each in-vehicle device is generated according to a change in the predetermined data collected by the collection unit, and distributed to each in-vehicle device. Device. A data collection device according to any one of claims 1 to 3 ;
A data collection system comprising: the in-vehicle device; A computer implemented data collection method comprising:
a collecting step of collecting predetermined data about the vehicle from an in-vehicle device mounted on each vehicle;
a setting step of setting conditions for collecting vehicle-related data to be collected from an in-vehicle device by the collecting step according to changes in the predetermined data collected by the collecting step ;
The collection step includes:
collecting predetermined data from the in-vehicle device at predetermined intervals longer than the data collection cycle;
The setting step includes:
setting an in-vehicle device as a data collection target based on the amount of change in predetermined data in a predetermined period;
setting data collection conditions according to a result of comparison between the amount of change in predetermined data and a predetermined threshold;
The threshold is
Multiple are provided according to the characteristics of the vehicle,
The setting step includes:
The amount of change in the predetermined data collected from the in-vehicle device is compared and determined using the threshold corresponding to the characteristics of the vehicle equipped with the in-vehicle device.
A data collection method characterized by: A computer implemented data collection method comprising:
a collecting step of collecting predetermined data about the vehicle from an in-vehicle device mounted on each vehicle;
a setting step of setting conditions for collecting vehicle-related data to be collected from an in-vehicle device by the collecting step according to a change in the predetermined data collected by the collecting step;
including
The collection step includes:
collecting predetermined data from the in-vehicle device at predetermined intervals longer than the data collection cycle;
The setting step includes:
setting an in-vehicle device as a data collection target based on the amount of change in predetermined data in a predetermined period;
setting data collection conditions according to a result of comparison between the amount of change in predetermined data and a predetermined threshold;
For one vehicle, the threshold is set according to the amount of change in predetermined data in vehicles other than the one vehicle.
A data collection method characterized by: The setting step includes:
According to the change of the predetermined data collected by the collecting step, a collection condition corresponding to each in-vehicle device is generated and distributed to each in-vehicle device.
7. The data collection method according to claim 5 or 6, characterized in that:

Images