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

Description

The present invention relates to a data collection device, data collection system and data collection method.

Conventionally, there is a data collection device that collects road information from an in-vehicle device mounted on each vehicle. Such a data collection device collects road information of 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-55581 A

Moreover, in recent years, it is required to quickly collect a wide variety of data other than road information from on-vehicle devices. However, collecting a wide variety of data from a large number of in-vehicle devices may cause congestion on communication lines, and may take a long time to provide data.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a data collection device, a data collection system, and a data collection method capable of quickly collecting data.

In order to solve the above problems and achieve the object, the data collection device according to the embodiment includes a reception unit, a selection unit, a selection request transmission unit, and a transmission request transmission unit. The reception unit receives a collection request including collection conditions for target data to be collected. The selection unit selects a vehicle that satisfies the collection condition received by the reception unit. The sorting request transmission unit transmits a sorting request for the data type specified by the collection condition to the in-vehicle device mounted on the vehicle selected by the selection unit. The transmission request transmitting unit transmits a transmission request for the data selected based on the selection request.

According to the present invention, data can be collected quickly.

FIG. 1 is a diagram showing an overview of the data collection method. FIG. 2 is a system schematic diagram of the data collection system. FIG. 3 is a block diagram of the data collection device. FIG. 4 is a diagram showing an example of a vehicle information table. FIG. 5 is a diagram showing an example of a collection condition table. FIG. 6 is a diagram showing an example of a reception screen. FIG. 7 is a block diagram of an in-vehicle device. FIG. 8 is a diagram showing an example of a collection condition file. FIG. 9 is a flow chart showing a processing procedure executed by the data collection device. FIG. 10 is a flow chart showing a processing procedure executed by the in-vehicle device.

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

First, the outline of the data collection method according to the embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an overview of the data collection method. This data collection method is realized by performing data communication between the data collection device 1 and the in-vehicle device 50 shown in FIG.

The data collection device 1 is a data collection server that receives data collection requests from data users and collects data from the in-vehicle device 50 based on the received collection requests.

Moreover, the data collection device 1 provides each user with the collected data. In the example shown in FIG. 1, users are service providers, developers, and users. That is, the data collection device 1 collects the data desired by the user on behalf of the user and provides the collected data.

Specifically, as shown in FIG. 1, the data collection device 1 first receives a collection request from a user (step S1). Such a collection request includes collection conditions specified by each user. The collection conditions also include information about data types, information about vehicles to be collected, and the like. Collection conditions may include collection period, upper limit of collection amount, and collection area.

Subsequently, the data collection device 1 selects a vehicle C that satisfies the collection conditions (step S2). The data collection device 1, for example, holds information on each vehicle as a database, and can select a vehicle that satisfies the above collection conditions from this database.

Subsequently, the data collection device 1 transmits a data type selection request that satisfies the collection condition to the in-vehicle device 50 of the vehicle C selected in step S2 (step S3). Accordingly, the in-vehicle device 50 can select the data type that satisfies the collection condition based on the selection request (step S4). Note that the in-vehicle device 50 can also start recording data of the data type specified by this sorting request.

Thereafter, when the data collection device 1 acquires an arbitrary trigger such as a data provision request to the in-vehicle device 50 that has transmitted the selection request, it transmits a transmission request for the data (group) selected in step S4. (Step S5).

As a result, the in-vehicle device 50 transmits the selected data to the data collection device 1 (step S6). That is, the data collection device 1 can reduce the communication load between the data collection device 1 and each in-vehicle device 50 by collecting only desired data from each in-vehicle device 50 .

This enables the data collection device 1 to collect data quickly. Then, the data collection device 1 provides the collected data to each user (step S7).

As described above, the data collection device 1 according to the embodiment collects only the data desired by the user from each in-vehicle device 50, thereby reducing the communication capacity of the data transmitted from each in-vehicle device 50. Become.

Therefore, according to the data collection device 1 according to the embodiment, it is possible to quickly collect data desired by the user from each vehicle-mounted device 50 . Therefore, the data collection device 1 according to the embodiment can provide data quickly.

In addition, the data collection device 1 according to the embodiment can transmit a transmission request of tag information according to collection conditions to each in-vehicle device 50 in advance, and can request transmission of actual data based on the tag information. However, this point will be described later.

Next, the configuration of the data collection system according to the embodiment will be described using FIG. FIG. 2 is a diagram showing a configuration example of a data collection system. As shown in FIG. 2 , the data collection system S includes a data collection device 1 , multiple user terminals 10 , and multiple in-vehicle devices 50 .

The data collection device 1, the user terminal 10 and the in-vehicle device 50 are connected via a network N. The data collection device 1 collects data from each in-vehicle device 50 based on a collection request received from the user terminal 10 and provides the data to the user terminal 10 .

The user terminal 10 is a terminal operated by a user, and may be a mobile phone such as a smart phone, a tablet terminal, a PDA, a desktop PC, a notebook PC, or the like. The user can operate the user terminal 10 and transmit the collection request to the data collection device 1 . The user terminal 10 can also present data provided by the data collection device 1 to the user. In addition, it is also possible to use the in-vehicle device 50 as the user terminal 10 .

The in-vehicle device 50 is a communication device mounted in each vehicle. The in-vehicle device 50 stores the data specified by the sorting request, such as vehicle travel information, in an internal storage medium, and transmits the data to the data collection device 1 based on the transmission request transmitted from the data collection device 1 .

Next, a configuration example of the data collection device 1 according to the embodiment will be described with reference to FIG. FIG. 3 is a block diagram of the data collection device 1. As shown in FIG. As shown in FIG. 3 , the data collection device 1 includes a communication section 2 , a control section 3 and a storage section 4 .

The communication unit 2 is a communication interface that transmits and receives information to and from the network N. FIG. The control unit 3 can transmit and receive various types of information to and from the communication unit 2 and the network N via each.

The control unit 3 includes a reception unit 31 , a selection unit 32 , a selection request transmission unit 33 , a transmission request transmission unit 34 and a provision unit 35 . The control unit 3 includes, for example, a computer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), input/output ports, and various circuits.

The CPU of the computer functions as the reception unit 31, the selection unit 32, the selection request transmission unit 33, the transmission request transmission unit 34, and the provision unit 35 of the control unit 3 by reading and executing programs stored in the ROM, for example. do.

At least one or all of the reception unit 31, the selection unit 32, the selection request transmission unit 33, the transmission request transmission unit 34, and the provision unit 35 of the control unit 3 may be implemented as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable). Gate Array) can also be configured by hardware.

Also, the storage unit 4 corresponds to, for example, a RAM or an HDD. The RAM and HDD include a vehicle information database 41, a collection condition database 42, a tag information database 43, and an actual data database 44. Note that the data collection device 1 may acquire the above-described programs and various types of information via other computers or portable recording media connected via a wired or wireless network.

The vehicle information database 41 has a vehicle information table for each vehicle. FIG. 4 is a diagram showing an example of a vehicle information table. As shown in FIG. 4, the vehicle information table 41a is information in which "in-vehicle device ID", "owner information", "vehicle type information", "in-vehicle equipment" and the like are associated with each other.

“In-vehicle device ID” is an identifier for identifying each in-vehicle device 50 . “Owner information” is information about the owner of the vehicle in which the in-vehicle device 50 is mounted. In the example shown in FIG. 4, the name of the owner is shown as the owner information, but the owner information may include the sex, age, address, occupation, and the like of the owner.

The "vehicle model information" is information related to the vehicle model, such as the vehicle model name and model year. "In-vehicle equipment" is information about the equipment of the vehicle. For example, vehicle information includes information indicating the presence or absence of a camera, the type of camera, and the like.

Returning to the description of FIG. 3, the collection condition database 42 will be described. The collection condition database 42 has a collection condition table regarding collection conditions received from the user terminal 10 . FIG. 5 is a diagram showing an example of a collection condition table.

As shown in FIG. 5, the collection condition table 42a is information in which "user ID", "request ID" and "collection condition" are associated with each other. "User ID" is an identifier that identifies a user.

"Request ID" is an identifier for identifying a collection request. "Collecting conditions" is information indicating the conditions for collecting actual data. For example, the collection conditions include "object vehicle conditions", "recording trigger", "collection content", and the like.

The “target vehicle condition” indicates the condition of the vehicle to be collected, and the “recording trigger” indicates the trigger for starting recording of actual data in the in-vehicle device 50 . The “recorded content” is information indicating actual data to be recorded in the in-vehicle device 50 .

In the example shown in FIG. 5, the target vehicle with the request ID "001" is a vehicle manufactured by "○○ company", the recording trigger is acceleration (>○○G), and the collected contents are position information and acceleration (front and rear 3 seconds and minutes).

In this case, when the in-vehicle device 50 detects that the acceleration exceeds OO G, the vehicle-mounted device 50 records the acceleration data for 3 seconds before and after the time when the acceleration exceeds OO G together with the position information. become.

Also, the target vehicle with the request ID "002" is a user in their 60s or older, the recording trigger is brake pressure (>○○ psi), and the time when the acceleration exceeds ○○ psi is used as a reference (5 seconds before and after ).

In this case, when the in-vehicle device 50 detects that the brake pressure exceeds XX psi, the vehicle-mounted device 50 records brake pressure data for 5 seconds before and after the time when the acceleration exceeds XX G along with position information. will do.

Also, as indicated by the request ID "003", it is possible to select all vehicles as the target vehicle. Also, as indicated by the request ID "003", it is possible to eliminate the recording trigger and perform constant recording.

Returning to the description of FIG. 3, the tag information database 43 will be described. The tag information database 43 is a database that stores tag information transmitted from each in-vehicle device 50 . For example, in the tag information database 43, the tag information is stored with information about time, tag information ID, in-vehicle device ID, etc. added to the tag information for each request ID. Note that the tag information database 43 is an example of a tag information storage unit.

The actual data database 44 is a database that stores actual data collected from each in-vehicle device 50 based on tag information. Information stored in the tag information database 43 and the actual data database 44 is appropriately provided to the user by the providing unit 35 .

Next, each configuration of the control unit 3 will be described. The reception unit 31 of the control unit 3 receives from the user terminal 10 a collection request including collection conditions for target data to be collected. Upon receiving the collection condition, the reception unit 31 adds the request ID to the collection condition and registers it in the collection condition database 42 .

Further, the reception unit 31 functions as a tag information reception unit. The reception unit 31 receives the tag update information of the tag information from the in-vehicle device 50 and updates the storage content of the tag information database 43 with the received tag update information, thereby updating the tag information and the tag stored in the in-vehicle device 50 . The tag information stored in the information database 43 can be synchronized.

Also, the reception unit 31 functions as an actual data reception unit. When the receiving unit 31 receives actual data from the in-vehicle device 50 , the receiving unit 31 registers the actual data in the actual data database 44 .

The receiving unit 31 can also receive designation of target data for which a transmission request is to be transmitted from the user terminal 10 . Upon receiving the designation of the target data, the reception unit 31 notifies the transmission request transmission unit 34 of the reception.

The selection unit 32 selects vehicles that satisfy the collection conditions. The selection unit 32 refers to the vehicle information database 41 and selects a vehicle that satisfies the collection conditions registered in the collection condition database 42 . At this time, when one vehicle satisfies multiple collection conditions, multiple collection conditions are applied to one vehicle.

Then, the selection unit 32 generates a collection condition file indicating collection conditions for each vehicle, and notifies the selection request transmission unit 33 of it. The selection unit 32 can also update each collection condition when the collection condition database 42 is updated.

At this time, the selection unit 32 can also select a vehicle that satisfies the collection condition based on the in-vehicle equipment in the vehicle information table 41a (see FIG. 4). Specifically, when a camera image is included in the collection condition, the selection unit 32 can determine that a vehicle that does not include a camera as an in-vehicle equipment does not satisfy the collection condition.

The sorting request transmitting unit 33 transmits a sorting request for the data type specified by the collection condition to the in-vehicle device 50 mounted on the vehicle selected by the selecting unit 32 . Specifically, the sorting request transmission unit 33 transmits the collection condition file generated by the selection unit 32 to each in-vehicle device 50 .

Further, when the collection condition file for each in-vehicle device 50 is updated by the selection unit 32, the sorting request transmission unit 33 may transmit a collection condition file update command to the in-vehicle device 50 together with the updated collection condition file. can.

In other words, the sorting request transmission unit 33 synchronizes the collection condition file generated by the selection unit 32 with the collection condition file of each in-vehicle device 50 . This makes it possible to synchronize the collection condition file stored in each in-vehicle device 50 with the latest collection condition file. Therefore, it is possible to collect only the target data required by each user (actual data: acquired data not converted into tag information), and to avoid collecting unnecessary target data.

The transmission request transmission unit 34 transmits a transmission request for data sorted and collected based on the sorting request. Specifically, the transmission request transmitting unit 34 can transmit a transmission request for data corresponding to tag information specified by the user.

In this case, the user can select which target data to collect based on the tag information provided by the providing unit 35 . Then, the transmission request transmission unit 34 transmits a transmission request for target data corresponding to the specified tag information to the in-vehicle device 50 that has transmitted the tag information specified by the user.

As a result, the in-vehicle device 50 transmits target data corresponding to the tag information to the data collection device 1 . Therefore, the data collection device 1 can collect only the target data desired by the user, so that the communication load between the data collection device 1 and each in-vehicle device 50 can be suppressed.

The providing unit 35 provides tag information and actual data to the user terminal 10 . First, the case where the providing unit 35 provides tag information will be described. In this case, the providing unit 35 displays information for selecting the target data near the selection button on the reception screen for designating the target data for which the transmission request is to be made to each user terminal 10. to provide tag information.

FIG. 6 is a diagram showing an example of a reception screen. As shown in FIG. 6, it is possible to receive designations of "place", "time" and "detailed settings" from the user on the reception screen.

For example, when the user selects a location, the user can specify the location where the tag information was generated (the location where the trigger (the data collection condition is satisfied)). Location selection items include, for example, "select from map" (not shown). For example, when the user selects "select from map", the tag information is displayed on the user terminal 10 in association with the position where the tag information is generated on the map image.

That is, the providing unit 35 can map the tag information on the map and provide it. Thereby, the user can easily grasp the position information of the tag information. By selecting tag information mapped on the map, the user can specify tag information for collecting actual data.

Also, the user can specify the time when the tag information was generated by selecting the time shown in FIG. Also, when the user selects the detailed settings shown in FIG. 6, for example, it is possible to select collection requests for other actual data. In the above example, the location and time are pinpointed, but it is also possible to specify a range such as area specification and time zone specification.

The transmission request transmitting unit 34 described above transmits a transmission request requesting provision of actual data to the in-vehicle device 50 that has provided the tag information specified by the user.

After that, the providing unit 35 provides each user terminal 10 with the actual data transmitted from each in-vehicle device 50 based on the transmission request transmitted by the transmission request transmission unit 34 .

Thus, the data collection device 1 collects tag information in advance and collects actual data of the tag information provided by the user. Therefore, only the actual data desired by the user can be collected and provided to the user. This makes it possible to quickly provide data desired by the user.

Although the case where the user designates the tag information to which the transmission request is to be transmitted has been described here, it is also possible for the data collecting apparatus 1 to make such selection. For example, it is assumed that the user is the driver of the vehicle and the camera image of a certain point is provided to the driver. In this case, the data collection device 1 collects location information in advance as tag information from each vehicle-mounted device 50, and selects a vehicle located near a point specified by the driver. The data collection device 1 can then collect the camera video from the corresponding in-vehicle device 50 and provide it to the driver.

Next, a configuration example of the in-vehicle device 50 will be described with reference to FIG. FIG. 7 is a block diagram of the in-vehicle device 50. As shown in FIG. 7, a vehicle speed sensor 91 for detecting the vehicle speed, a steering angle sensor 92 for detecting the steering angle of the vehicle, a G sensor 93 for detecting the acceleration of the vehicle, a camera 94 for imaging the surroundings of the vehicle, and a A position detection device 95 for detecting the position is also shown.

These vehicle speed sensor 91, steering angle sensor 92, G sensor 93, camera 94, and position detection device 95 are connected to the in-vehicle device 50 via an in-vehicle network B such as CAN communication.

The in-vehicle device 50 includes a communication section 6 , a control section 7 and a storage section 8 . The communication unit 6 is a communication interface that transmits and receives information to and from the network N. FIG. The control unit 7 can transmit and receive various types of information to and from each other via the communication unit 2 and the network N. FIG.

The control unit 7 includes an acquisition unit 71 , a detection unit 72 , a selection unit 73 and a transmission unit 74 . The control unit 7 includes, for example, a computer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), input/output ports, and various circuits.

The CPU of the computer functions as an acquisition unit 71, a detection unit 72, a selection unit 73, and a transmission unit 74 of the control unit 7 by reading and executing programs stored in the ROM, for example.

At least one or all of the acquisition unit 71, the detection unit 72, the selection unit 73, and the transmission unit 74 of the control unit 7 are implemented by hardware such as ASIC (Application Specific Integrated Circuit) and FPGA (Field Programmable Gate Array). Can also be configured.

Also, the storage unit 8 corresponds to, for example, a RAM or an HDD. The RAM or HDD includes a tag information storage section 81, an actual data storage section 82, and a collection condition storage section 83. FIG. Note that the in-vehicle device 50 may acquire the above-described programs and various information via another computer or portable recording medium connected via a wired or wireless network.

The tag information storage unit 81 will be described. The tag information is data that serves as index data for the corresponding actual data, and is information used by, for example, a user or the like to determine the necessity of confirming the actual data.

Specifically, the date and time data of the trigger (when the collection condition is met), the position data, the data size of the actual data, the value level of the trigger generation cause (for example, if the acceleration value is the trigger, the acceleration value level (less than the threshold value, ~ 2 times the threshold, ~ 3 times the threshold...)). This tag information is generated based on actual data, and the date and time data, position data, etc. are detected values (processing such as rounding of significant digits is performed as necessary), and the level value is processed by a predetermined calculation formula of the detected value. The tag information can be generated by processing using table data of detection values, etc. The tag information generated in this manner is stored in the tag information storage unit 81 .

Since the tag information has a smaller capacity than the actual data, the problem of storage capacity is not so big. It may be erased synchronously with the data.

In addition, since tag information is used for sorting and searching actual data by users, real-time performance is important, so data is collected promptly (as soon as communication is possible) when tag information is generated. It is a process of transmitting to the device 1 .

Furthermore, since the tag information stored in the in-vehicle device 50 and the tag information stored in the data collection device 1 must be the same data, the tag information is updated (newly generated or deleted) on the in-vehicle device 50 side. In this case, it is necessary to promptly transmit the information to the data collecting device 1 and update the tag information on the data collecting device 1 side in synchronization. When the tag information is erased on the data collection device 1 side, the tag information and the corresponding actual data may be erased on the in-vehicle device 50 side if the storage device does not have enough capacity.

The actual data storage unit 82 is a storage unit that stores the actual data (target data) of the collection target type that satisfies the collection condition. The actual data storage unit 82 stores the actual data and the tag information in association with each other. For example, the real data storage unit 82 is a ring buffer type storage medium, and old real data is overwritten with new data as needed.

The collection condition storage unit 83 is a storage unit in which data collection conditions for each in-vehicle device 50 are described. FIG. 8 is a diagram showing an example of the collection condition storage unit 83. As shown in FIG.

As shown in FIG. 8, the collection condition storage unit 83 is divided into multiple areas. Each area of the collection condition storage unit 83 stores collection conditions with different usage purposes.

Specifically, the collection condition storage unit 83 is divided into a service area R1, a required area R2, a development area R3, and an autonomous generation area R4. The service area R1 is, for example, an area for storing collection conditions specified by a service provided for general users by a service provider that provides services for general users or by an administrator of the data collection apparatus 1 .

The required area R2 is an area for storing collection conditions under which data collection is essential. For example, the required area R2 stores collection conditions that affect human life. Specifically, collection conditions for emergency vehicles such as fire trucks and police vehicles are stored in the required area R2. The data collection condition (data type) of the required region R2 is, for example, positional information, and the data collection device 1 can grasp the positional information of each vehicle in real time based on such positional information.

When a fire, traffic accident, or the like occurs in the vicinity of each vehicle, the data collection device 1 transmits a transmission request requesting a camera image to the in-vehicle device 50 located in the vicinity of the scene. By providing the camera image to the emergency vehicle, the data collection device 1 can confirm the state of the scene earlier than the emergency vehicle arrives at the scene.

The development area R3 is an area for storing the collection conditions of the vehicle developer. For example, a vehicle developer can use the actual data collected based on the transmission request to develop an autonomous vehicle.

Further, the autonomous generation area R4 is an area for storing collection conditions generated by the in-vehicle device 50 autonomously. For example, when detecting an abnormality in the vehicle, the in-vehicle device 50 can generate a collection condition related to a phenomenon similar to the abnormality and store it in the autonomous generation area R4.

As a result, for example, the data collection device 1 collects tag information and actual data from each in-vehicle device 50, collects data for identifying the cause of an abnormality, and identifies the cause based on these data. , a countermeasure can be sent to the in-vehicle device 50 .

Returning to the description of FIG. 7, the acquisition unit 71 of the control unit 7 will be described. The acquisition unit 71 acquires the collection condition and the collection request from the data collection device 1 respectively. The acquisition unit 71 updates the collection condition storage unit 83 of the storage unit 8 using the acquired collection conditions. As a result, the collection condition storage unit 83 of the storage unit 8 can be updated (synchronized with the collection conditions stored in the data collection device 1).

The detection unit 72 detects events that satisfy the collection conditions stored in the collection condition storage unit 83 . When detecting an event that satisfies the collection condition stored in the collection condition storage unit 83, the detection unit 72 generates tag information based on the actual data for the event that satisfies the collection condition, and sends the tag information to the selection unit 73 and the transmission unit 74, respectively. Notice.

Further, for example, when an abnormality of the vehicle is detected, the detection unit 72 generates a collection condition based on the abnormality, stores it in the autonomous generation area R4 (see FIG. 8), and collects data via the transmission unit 74. It is also possible to request the device 1 to analyze the abnormality.

The selection unit 73 stores the tag information notified from the detection unit 72 in the actual data storage unit 82 in association with the actual data that satisfies the collection condition. That is, the selection unit 73 can select actual data that satisfies the collection condition and store the actual data in the actual data storage unit 82 .

In addition, when a transmission request is transmitted from the data collection device 1, the selection unit 73 is specified by the transmission request based on the transmission request (specified by the user or the like based on the tag information on the data collection device 1 side). actual data) can be selected from the actual data storage unit 82 and notified to the transmission unit 74 .

The transmission unit 74 transmits the tag information generated by the detection unit 72 to the data collection device 1 and transmits the actual data selected by the selection unit 73 to the data collection device 1 .

As a result, the data collection device 1 can provide each user with the actual data desired by each user and the tag data corresponding to the actual data.

Next, a processing procedure executed by the data collection device 1 according to the embodiment will be described with reference to FIG. 9 . FIG. 9 is a flow chart showing a processing procedure executed by the data collection device 1 according to the embodiment. This process is repeatedly executed while the data collection device 1 is in operation.

First, as shown in FIG. 9, the data collection device 1 determines whether or not a new collection request has been received (step S101). When the data collection device 1 receives a collection request (step S101, Yes), it selects a vehicle that satisfies the collection condition (step S102).

Subsequently, the data collection device 1 updates the collection condition file of the in-vehicle device 50 mounted on the vehicle selected in step S102 by transmitting update data and an update instruction command to the target vehicle (step S103). . Subsequently, the data collection device 1 collects tag information from each in-vehicle device 50 (step S104), and provides the collected tag information to the user (step S105).

Subsequently, the data collection device 1 receives from the user the designation of tag information for collecting actual data (step S106), and transmits a transmission request to the in-vehicle device 50 that has transmitted the designated tag information (step S106). S107).

Thereafter, the data collection device 1 collects actual data from each vehicle-mounted device 50 (step S108), provides the collected actual data to the user (step S109), and ends the process. On the other hand, when the data collection device 1 has not received a new collection condition (step S101, No), the process proceeds to step S104. As described above, when the data collection device 1 selects a target vehicle for a transmission request, the processing of steps S105 and S106 is replaced with "select tag information to be a transmission target of a transmission request". .

Next, a processing procedure executed by the in-vehicle device 50 will be described with reference to FIG. 10 . FIG. 10 is a flowchart showing a processing procedure executed by the in-vehicle device 50. As shown in FIG. This processing is executed when the data collection device 1 issues a data collection request.

As shown in FIG. 10, first, the in-vehicle device 50 determines whether or not an event that satisfies the collection condition is detected (step S201). If an event is detected (step S201, Yes), it is designated by the collection condition file. generated tag information (step S202). Moreover, in the process of step S201, the in-vehicle apparatus 50 transfers to the process of step S204, when an event is not detected (step S201, No).

Subsequently, the in-vehicle device 50 stores actual data corresponding to the tag information, transmits the tag information (step S203), and determines whether or not a transmission request has been obtained from the data collection device 1 (step S204).

When the in-vehicle device 50 acquires a transmission request (step S204, Yes), it selects actual data to be transmitted (step S205). Subsequently, the in-vehicle device 50 transmits the selected actual data to the data collection device 1 (step S206), and determines whether or not there is a termination request to terminate the collection of the actual data (step S207). For example, the termination request includes updating the collection condition file.

Then, if there is an end request (step S207, Yes), the in-vehicle device 50 ends the process. Moreover, the vehicle-mounted apparatus 50 transfers to the process of step S201, when there is no end request (step S207, No).

If the in-vehicle device 50 does not acquire a transmission request (step S204, No), the process proceeds to step S207.

As described above, the data collection device 1 according to the embodiment includes the reception unit 31, the selection unit 32, the selection request transmission unit 33, and the transmission request transmission unit . The reception unit 31 receives a collection request including collection conditions for target data to be collected. The selection unit 32 selects vehicles that satisfy the collection conditions received by the reception unit 31 . The sorting request transmitting unit 33 transmits a sorting request for the data type specified by the collection condition to the in-vehicle device 50 mounted on the vehicle selected by the selecting unit 32 . The transmission request transmitting unit 34 transmits a transmission request for data selected based on the selection request.

By the way, in the above-described embodiment, the case where the data collection device 1 collects data from the in-vehicle device 50 has been described, but the present invention is not limited to this. That is, the data collection device 1 can also collect data from terminal devices such as smartphones and tablet terminals.

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 device 10 user terminal 31 reception unit 32 selection unit 33 selection request transmission unit 34 transmission request transmission unit 35 provision unit 41 vehicle information database 42 collection condition database 43 tag information database 44 actual data database 50 in-vehicle device 71 acquisition unit 72 Detection unit 73 Selection unit 74 Transmission unit 81 Tag information storage unit 82 Actual data storage unit 83 Collection condition storage unit S Data collection system

Claims (9)

a reception unit that receives a collection request including collection conditions for target data to be collected;
a selection unit that selects a vehicle that satisfies the collection condition received by the reception unit;
a selection request transmission unit configured to transmit a selection request for a data type designated based on the collection condition to an in-vehicle device mounted on the vehicle selected by the selection unit;
a transmission request transmitting unit that transmits a transmission request for data selected based on the selection request ,
The transmission request transmission unit,
transmitting a tag information request, which is a request for transmitting tag information corresponding to the target data corresponding to the collection condition, and based on the tag information transmitted from the in-vehicle device according to the tag information request, from the requester of the collection request; Sending specified specified tag information as a target data request to the in-vehicle device that sent the tag information
A data acquisition device characterized by: 2. The apparatus according to claim 1, further comprising a providing unit that provides the target data transmitted from the in-vehicle device to a request source of the collection request based on the transmission request transmitted by the transmission request transmission unit. data collection device. The selection request transmission unit is
3. The data collection device according to claim 2 , wherein the collection conditions are transmitted as a collection condition file, and are synchronized with the collection condition file of the in-vehicle device each time the collection condition file is updated. The providing unit
providing the tag information generated based on the data collected based on the collection condition to the requester of the collection request ;
The transmission request transmission unit,
4. The target data request according to claim 2 or 3 , wherein, among the tag information provided by the providing unit, the target data request is transmitted for the target data corresponding to the tag information specified by the requester of the collection request. data collection device. The providing unit
5. The data collection device according to claim 4 , wherein the tag information is provided by mapping it on a map image based on the position information of the tag information. a tag information receiving unit that receives tag information transmitted from an in-vehicle device;
a tag information storage unit that stores the tag information received by the tag information reception unit;
with
The tag information receiving unit is
By receiving tag update information of the tag information from the in-vehicle device and updating the storage content of the tag information storage unit with the received tag update information, the tag information stored in the in-vehicle device and the tag information storage unit A data collection device according to any one of claims 1 to 5, characterized in that it synchronizes the stored tag information. A data collection device according to any one of claims 1 to 6 ;
and the in-vehicle device that selects the data type and transmits data based on the transmission request transmitted from the data collection device. The in-vehicle device
generating tag information corresponding to the target data collected according to the sorting request and transmitting it to the data collecting device, and sorting target data corresponding to the tag information specified by the source of the collection request according to the transmission request; 8. The data collection system according to claim 7 , wherein the data is transmitted to the data collection device by A computer implemented data collection method comprising:
a receiving step of receiving a collection request including collection conditions for target data to be collected;
a selection step of selecting a vehicle that satisfies the collection condition accepted by the acceptance step;
a sorting request transmission step of transmitting a sorting request for the data type specified by the collection condition to an in-vehicle device mounted on the vehicle selected by the selecting step;
a transmission request transmitting step of transmitting a transmission request for data selected based on the selection request ;
The transmission request transmission step includes:
transmitting a tag information request, which is a request for transmitting tag information corresponding to the target data corresponding to the collection condition, and based on the tag information transmitted from the in-vehicle device according to the tag information request, from the requester of the collection request; Sending specified specified tag information as a target data request to the in-vehicle device that sent the tag information
A data collection method characterized by:

Images