JP7252724B2 - 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 each in-vehicle device may cause congestion of 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-described problems and achieve the object, the data collection device according to the embodiment includes a reception section, a collection condition data generation section, a collection condition setting section, and an acquired data collection section. The reception unit receives a request for collecting data obtained by each vehicle. The collection condition data generation unit generates collection condition data indicating data collection conditions based on the collection request received by the reception unit. The collection condition setting unit transmits the collection condition data generated by the collection condition data generation unit to each vehicle and sets the data in each vehicle. The acquired data collection unit receives data satisfying the collection condition transmitted from each vehicle. Further, the collection condition setting unit can set a plurality of collection conditions, and the acquired data collection unit selects the plurality of collection conditions and collects the acquired data.

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

FIG. 1A is a diagram showing an overview of the data collection method. FIG. 1B is a diagram showing an example of a condition file. 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 connection request. FIG. 7 is a block diagram of an in-vehicle device. FIG. 8 is a flowchart (part 1) showing a processing procedure executed by the data collection device. FIG. 9 is a flowchart (part 2) 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 overview of the data collection method according to the embodiment will be described with reference to FIG. 1A. FIG. 1A 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. 1A.

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. 1A, the 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. 1A, the data collection device 1 first receives a collection request from the 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.

Subsequently, the data collection device 1 selects a vehicle 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 generates a condition file indicating collection conditions for each vehicle (step S3). Here, the condition file is a file classified according to the purpose of use of data. Note that an example of dividing the condition file will be described later with reference to FIG. 1B.

Then, the data collection device 1 transmits the condition file generated for each vehicle to the in-vehicle device 50 of each vehicle, and each in-vehicle device 50 selects data that satisfies the collection conditions indicated in the condition file (step). S4), and transmits the selected data to the data collection device 1 (step S5).

That is, the data collection device 1 sets a plurality of data collection conditions in the in-vehicle device 50 and causes the in-vehicle device 50 to acquire data based on each data collection condition. Then, the data acquired by the in-vehicle device 50 can be selectively collected (the data collection device 1 designates the data type to be collected using the data collection condition data, and the in-vehicle device 50 selectively transmits according to the designation). After that, the data collection device 1 provides the user with the data collected from each in-vehicle device 50 (step S6).

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.

Next, an example of classification of condition files will be described with reference to FIG. 1B. FIG. 1B is a diagram showing an example of division of condition files. As shown in FIG. 1B, the condition file is divided into a plurality of areas, and each area of the condition file stores, for example, data collection conditions for different purposes of use. In the example shown in FIG. 1B, the condition file is divided into a service area R1, a required area R2, a development area R3, and an autonomous generation area R4. In other words, they are differentiated for the purpose of distinguishing the processing form of the acquired data (for example, changing the processing form depending on the purpose of use), such as the necessity and priority of data transmission.

The service area R1 is an area for storing collection conditions for services provided for general users by a service provider that provides services for general users or by an administrator of the data collection apparatus 1 . Collection conditions set by the service provider or the data collection device 1 are assigned to the service area R1.

The required area R2 is an area for storing a collection condition that, when the collection condition is satisfied, transmission of data that satisfies the collection condition is essential. For example, collection conditions set by emergency vehicles such as ambulances and police cars are assigned to the required area R2.

The development area R3 is an area for storing collection requests made by vehicle developers. The collection conditions set by the developer are assigned to the development area R3.

In addition, the autonomous generation area R4 is an area for storing the collection conditions autonomously generated by the in-vehicle device 50 by itself. For example, when detecting an anomaly in the vehicle, the in-vehicle device 50 can generate a data collection condition regarding a phenomenon similar to the anomaly and store it in the autonomous generation area R4. Since the collection conditions are generated on the in-vehicle device 50 side, the in-vehicle device 50 distributes them to the autonomous generation area R4.

Data collected under the collection conditions of the service area R1 are finally provided to general users, and data collected under the collection conditions of the mandatory area R2 are finally provided to emergency vehicles.

In addition, the data collected based on the collection conditions of the development area R3 is finally provided to the developer, and the data collected based on the collection conditions of the autonomous generation area R4 is finally provided to the in-vehicle device 50 or the developer. provided.

That is, the service area R1, the essential area R2, the development area R3, and the autonomous generation area R4 all store collection conditions with different data utilization purposes.

In particular, since the collection conditions for the required region R2 are related to human life, collection conditions for data having urgency are stored. Therefore, the collection conditions for the required area R2 are collected without obtaining the user's approval. On the other hand, the collection conditions for other areas (especially the service area R1) are collected with user approval.

In this manner, the data collection device 1 generates a condition file after allocating collection conditions to storage areas according to the purpose of use of the collection conditions. As a result, it is possible to appropriately collect data according to the collection conditions. Moreover, by providing the essential area R2, therefore, it becomes possible to reliably collect highly urgent data.

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.

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 generation unit 32 , a transmission unit 33 and a provision unit 34 . 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 generation unit 32 , the transmission unit 33 and the provision unit 34 of the control unit 3 by reading and executing programs stored in the ROM, for example.

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

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, the tag information is stored with information about time, tag information ID, in-vehicle device ID, etc. 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 receiving unit 31 of the control unit 3 receives from the user terminal 10 a collection request including collection conditions for 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, when receiving a collection request from the administrator of the emergency vehicle, the reception unit 31 notifies the generation unit 32 of the collection request. This collection request includes location information such as the accident site. In the following description, the emergency vehicle collection request may be referred to as a collection request in order to distinguish between the emergency vehicle collection request and other collection requests.

The reception unit 31 also functions as an acquired data collection unit that receives data that satisfies collection conditions and is transmitted from each vehicle. Here, the data received by the receiving unit 31 includes tag data and actual data.

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 generation unit 32 functions as a collection condition data generation unit and a collection condition setting unit. The generation unit 32 generates collection condition data indicating data collection conditions based on the collection request received by the reception unit 31 .

Acquisition condition data is data specifying the recording trigger, data type/format, etc. (captured image data (moving image, still image, etc., audio data, etc.)), data acquisition position condition, and the like. That is, the in-vehicle device 50 can store data specified by the collection condition data when an event corresponding to a recording trigger specified by the collection condition data is detected.

In addition, when the collection condition data is generated, the generation unit 32 transmits it to each vehicle via the transmission unit 33 and sets it in each vehicle. At this time, as shown in FIG. 1B, it is possible to specify the area of the collection condition file and transmit the collection condition data.

The transmission unit 33 transmits the collection condition data generated by the generation unit 32 to the in-vehicle device 50 and also transmits a transmission request for actual data to each in-vehicle device 50 .

By the way, an in-vehicle camera such as a drive recorder is generally fixedly attached to a vehicle. Therefore, it may be difficult to obtain video data with a desired angle of view depending on the vehicle-mounted camera. In other words, the drive recorder may not be able to capture an image of the scene of the accident.

Therefore, the transmission unit 33 can request connection to a camera-equipped terminal, such as a smart phone owned by the user of the vehicle, via the in-vehicle device 50 . That is, the transmission unit 33 can transmit a transmission request after attaching a connection request to the terminal.

FIG. 6 is a diagram showing an example of a connection request. As shown in FIG. 6, the data collection device 1 transmits to the in-vehicle device 50 a transmission request for image data for the accident site X (step S21). The in-vehicle device 50 receives the transmission request and connects to the terminal T capable of capturing the image data.

For example, the connection request includes an activation signal for activating a short-range wireless communication device such as wi-fi (registered trademark) that the in-vehicle device 50 has. A radio can be activated.

The in-vehicle device 50 can be connected to the terminal T via a short-range wireless communication device. Then, the in-vehicle device 50 transmits a request for imaging the accident site X to the terminal T, and acquires image data of the accident site X from the terminal T (step S23). In other words, with the terminal T, the image data of the accident site X can be appropriately captured because the user can freely capture an image at a desired angle of view.

After that, the in-vehicle device 50 transmits the image data to the data collection device 1, so that the data collection device 1 can collect the image data of the accident site (step S24).

In this manner, the data collection device 1 collects image data from the terminal T via the in-vehicle device 50, thereby collecting video data in which the accident site X is properly captured. At this time, the terminal T connected to the in-vehicle device 50 may be owned by the user of the in-vehicle device 50, or may be owned by a person other than the user (for example, a passerby or an onlooker). may be

Returning to the description of FIG. 3, the providing unit 34 will be described. The providing unit 34 provides each user with tag information and actual data. For example, when the user is the administrator of the emergency vehicle, the provision unit 34 maps the tag information on the map and displays it on the user terminal 10 of the emergency vehicle.

The administrator can specify actual data to be collected based on the tag information displayed on the user terminal 10. FIG. As a result, the transmission unit 33 transmits a transmission request for the actual data corresponding to the tag information, and the reception unit 31 collects the actual data from the in-vehicle device 50 .

After that, the providing unit 34 can provide the collected actual data to the user terminal 10 of the emergency vehicle. This allows the crew of the emergency vehicle (for example, fire brigade, police officer, etc.) to check the state of the accident site X on the way to the accident site X. Therefore, quick and appropriate rescue activities can be performed.

The providing unit 34 can also provide other users with the data collected based on the collection conditions specified by each user.

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). It 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 in synchronization 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 actual data) of the collection target type that satisfies the collection conditions. 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 divided into a plurality of areas as shown in FIG. 1B. Specified collection condition data is stored in each area of the collection condition storage unit 83 .

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. 1B), 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 FIGS. 8 and 9. FIG. 8 and 9 are flowcharts showing the processing procedures executed by the data collection device 1 according to the embodiment. Note that FIG. 8 will explain processing related to generation of a collection file, and FIG. 9 will explain processing when a collection request is received from an emergency vehicle. These processes are repeatedly executed while the data collection device 1 is in operation.

First, as shown in FIG. 8, the data collection device 1 determines whether or not a 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 generates collection condition data (step S103), specifies the area of the collection condition file of the in-vehicle device 50, transmits the collection condition data (step S104), and ends the process. On the other hand, if the data collection device 1 has not received a new collection condition (step S101, No), the process ends.

Next, the processing of the data collection device 1 when receiving a collection request from an emergency vehicle will be described with reference to FIG.

As shown in FIG. 9, the data collection device 1 determines whether or not a collection request has been received from an emergency vehicle (step S111). When the data collection device 1 receives a collection request (step S111, Yes), it selects a vehicle near the site (step S112), and transmits collection condition data for acquiring image data of the site (step S113). .

Subsequently, the data collection device 1 acquires the tag information transmitted from the in-vehicle device 50 that transmitted the collection condition data (step S114), and selects collection data (step S115). It should be noted that the processing of step S115 can also be selected on the data collecting apparatus 1 side by selection by the user or selection based on preset conditions or the like.

Subsequently, the data collection device 1 collects data from the in-vehicle device of the vehicle by transmitting a data collection request to the target vehicle (step S116). Then, the data collection device 1 provides the collected data to the emergency vehicle (step S117), and ends the process. If the data collection device 1 has not received a collection request (step S111, No), the process ends.

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 collection condition data generation unit, the collection condition setting unit, and the acquired data collection unit. The receiving unit 31 receives a request for collecting data obtained by each vehicle. The generation unit 32 (an example of a collection condition data generation unit) generates collection condition data indicating data collection conditions based on the collection request received by the reception unit 31 . The generation unit 32 (an example of a collection condition setting unit) transmits the collection condition data generated by the collection condition data generation unit to each vehicle and sets the data in each vehicle. The reception unit 31 (an example of an acquired data collection unit) receives data that satisfies collection conditions and is transmitted from each vehicle. In addition, the generation unit 32 can set a plurality of collection conditions, selects the plurality of collection conditions, and collects the acquired data.

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 generation unit 33 transmission unit 34 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 Part S Data collection system

Claims (7)

a reception unit that receives a request for collecting data obtained by each vehicle;
a collection condition data generation unit that generates collection condition data indicating data collection conditions based on the collection request received by the reception unit;
a collection condition setting unit that transmits the collection condition data generated by the collection condition data generation unit to each vehicle and sets the collection condition data in each vehicle;
an acquisition data collection unit that receives data that satisfies the collection conditions transmitted from each vehicle,
The collection condition setting unit
It is possible to set multiple collection conditions for tag information, which is an index summarizing the content of data obtained from each vehicle,
The acquired data collection unit
A data collection device that collects acquired data selected based on the collected tag information. The collection condition setting unit
dividing and storing the collection condition data in corresponding areas of a condition file in which areas for different purposes of data use are set, and transmitting the condition file to an in-vehicle device of each vehicle;
The acquired data collection unit
2. The data collection device according to claim 1, wherein the data is selected and collected based on the collection conditions stored in the condition file. The condition file is
having at least an essential area to which the collection conditions for which the data collection is essential are allocated and other areas where the data collection is not essential;
The collection condition setting unit
3. The data collection device according to claim 2, wherein the collection conditions from the manager of the emergency vehicle are distributed to the required areas. 4. A transmission unit that selects a vehicle for collecting the data based on the tag information collected based on the condition file and transmits a transmission request for the data to an in-vehicle device of the vehicle. The data collection device according to . The transmission unit
5. The data collection device according to claim 4, wherein, when the data type specified by the collection condition is image data, a connection request to a terminal device having an imaging device is transmitted to the in-vehicle device. A data collection device according to any one of claims 1 to 5;
and an in-vehicle device mounted on the vehicle. a receiving step of receiving a request for collecting data obtained by each vehicle;
a collection condition data generation step of generating collection condition data indicating data collection conditions based on the collection request received by the reception step;
a collection condition setting step of transmitting the collection condition data generated in the collection condition data generation step to each vehicle and setting the collection condition data in each vehicle;
an acquired data collection step of receiving acquired data that satisfies the collection conditions transmitted from each vehicle;
The collection condition setting step includes:
It is possible to set multiple collection conditions for tag information, which is an index summarizing the content of data obtained from each vehicle,
The acquired data collection step includes:
A data collection method characterized by collecting acquired data selected based on the collected tag information.

Images