JP7340678B2 - Data collection method and data collection device - Google Patents

Description

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

Conventionally, there is a data collection device that collects road information from an on-vehicle device installed in each vehicle. Such a data collection device collects road information at a desired location by selecting vehicles for which road information is to be collected based on the location information of each vehicle (for example, see Patent Document 1).

Japanese Patent Application Publication No. 2018-55581

Furthermore, in recent years, it has become necessary to quickly collect a wide variety of data other than road information from in-vehicle devices. However, collecting a wide variety of data from each in-vehicle device causes congestion on communication lines, so it may take a long time to provide the data.

The present invention has been made in view of the above, and an object of the present invention is to provide a data collection method and a data collection device that can quickly collect data.

In order to solve the above-mentioned problems and achieve the purpose, a data collection method according to an embodiment is a data collection method in which a control unit collects data regarding the vehicle from an on-vehicle device mounted on the vehicle, Accepts a request to collect data obtained from a vehicle, generates collection conditions based on the collection request, and stores the collection conditions by dividing them into corresponding areas of a condition file in which areas each having a different purpose of data use are set. , transmitting the condition file to the in-vehicle device, and receiving from the in-vehicle device data that has been selected and collected according to the collection conditions stored in the condition file.

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

FIG. 1A is a diagram showing an overview of a data collection method. FIG. 1B is a diagram showing an example of a condition file. FIG. 2 is a system overview 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 the in-vehicle device. FIG. 8 is a flowchart (part 1) showing the processing procedure executed by the data collection device. FIG. 9 is a flowchart (Part 2) showing the processing procedure executed by the data collection device. FIG. 10 is a flowchart showing the 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. Note that the present invention is not limited to this embodiment.

First, an overview of the data collection method according to the embodiment will be described using FIG. 1A. FIG. 1A is a diagram showing an overview of a data collection method. Note that this data collection method is realized by performing data communication between the data collection device 1 and the vehicle-mounted 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.

Further, the data collection device 1 provides the collected data to each user. The example shown in FIG. 1A shows a case where the users are a service provider, a developer, and a user. That is, the data collection device 1 collects data desired by these users on behalf of the users, and provides the collected data.

Specifically, as shown in FIG. 1A, first, the data collection device 1 receives a collection request from a user (step S1). Such collection requests include collection conditions specified by each user. Furthermore, the collection conditions include information regarding the data type, information regarding the vehicle 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 has, for example, information regarding each vehicle as a database, and can select vehicles that satisfy the above collection conditions from the 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 data usage. Note that an example of dividing the condition files will be described later using 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 of these data collection conditions. Then, the data acquired by the in-vehicle device 50 can be selectively collected (the data collection device 1 specifies the type of data to be collected using the data collection condition data, and the in-vehicle device 50 selectively transmits the data according to the specification). Thereafter, the data collection device 1 provides the data collected from each in-vehicle device 50 to the user (step S6).

In this way, the data collection device 1 according to the embodiment can reduce the communication capacity of data transmitted from each in-vehicle device 50 by collecting only the data desired by the user from each in-vehicle device 50. Become.

Therefore, according to the data collection device 1 according to the embodiment, data desired by the user can be quickly collected from each in-vehicle device 50. Therefore, the data collection device 1 according to the embodiment can quickly provide data.

Next, an example of dividing condition files will be described using FIG. 1B. FIG. 1B is a diagram showing an example of classification 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, an essential area R2, a development area R3, and an autonomous generation area R4. In other words, the requirements and priorities for data transmission are different, and the processing forms of the acquired data are differentiated (eg, the processing form is changed depending on the purpose of use).

The service area R1 is an area where a service provider providing services for general users or an administrator of the data collection device 1 stores collection conditions for services provided to general users. Collection conditions set by the service provider or the data collection device 1 are distributed to the service area R1.

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

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

Furthermore, the autonomous generation area R4 is an area in which the on-vehicle device 50 stores collection conditions autonomously generated by itself. For example, when the vehicle-mounted device 50 detects an abnormality in the vehicle, it can generate data collection conditions regarding a phenomenon similar to the abnormality and store it in the autonomous generation region R4. Note that since such collection conditions are generated on the in-vehicle device 50 side, the in-vehicle device 50 distributes them to the autonomous generation region R4.

The data collected based on the collection conditions of the service area R1 is finally provided to general users, and the data collected based on the collection conditions of the essential area R2 is finally provided to emergency vehicles.

Furthermore, 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 for different purposes of data use.

In particular, regarding the collection conditions for the essential region R2, the collection conditions for data that are urgent because human life is involved are stored. Therefore, the collection conditions for the essential area R2 are collected without obtaining user approval. On the other hand, collection conditions for other areas (particularly service area R1) are collected with user approval.

In this manner, the data collection device 1 distributes the collection conditions to areas for storing them according to the purpose of use of the collection conditions, and then generates a condition file. Thereby, it is possible to appropriately collect data according to the collection conditions. Furthermore, by providing the essential region R2, it is possible to reliably collect highly urgent data.

Next, the configuration of the data collection system according to the embodiment will be described using FIG. 2. FIG. 2 is a diagram showing an example of the configuration of the data collection system. As shown in FIG. 2, the data collection system S includes a data collection device 1, a plurality of user terminals 10, and a plurality of 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 smartphone, a tablet terminal, a PDA, a desktop PC, a notebook PC, or the like. The user can operate the user terminal 10 and send the above collection request to the data collection device 1. Further, the user terminal 10 can also present data provided from the data collection device 1 to the user. Note that it is also possible to use the in-vehicle device 50 as the user terminal 10.

The on-vehicle device 50 is a communication device mounted on each vehicle. The in-vehicle device 50 stores 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 a transmission request sent from the data collection device 1.

Next, a configuration example of the data collection device 1 according to the embodiment will be described using FIG. 3. FIG. 3 is a block diagram of the data collection device 1. 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. The control unit 3 can transmit and receive various information between the communication unit 2 and the network N via the communication unit 2 and the network N.

Next, a configuration example of the data collection device 1 according to the embodiment will be described using FIG. 3. FIG. 3 is a block diagram of the data collection device 1. 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. The control unit 3 can transmit and receive various information between the communication unit 2 and the network N via the communication unit 2 and the network N.

The control unit 3 includes a receiving unit 31, a generating unit 32, a transmitting unit 33, and a providing unit 34. The control unit 3 includes, for example, a computer and various circuits having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an input/output port, and the like.

The CPU of the computer functions as the receiving section 31, the generating section 32, the transmitting section 33, and the providing section 34 of the control section 3, for example, by reading and executing a program stored in the ROM.

Furthermore, at least a part or all of the reception section 31, generation section 32, transmission section 33, and provision section 34 of the control section 3 may be implemented using hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). It can also be configured.

Further, 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-mentioned programs and various information via another computer or a portable recording medium connected via a wired or wireless network.

The vehicle information database 41 has a vehicle information table regarding 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 "vehicle device ID", "owner information", "vehicle type information", "vehicle equipment", etc. are associated with each other.

“In-vehicle device ID” is an identifier that identifies each in-vehicle device 50. “Owner information” is information regarding the owner of the vehicle in which the in-vehicle device 50 is installed. In the example shown in FIG. 4, the name of the owner is shown as the owner information, but the owner information may also include the owner's gender, age, address, occupation, etc.

"Vehicle model information" is information about the model of the vehicle, and includes information about the model name and model year. “In-vehicle equipment” is information regarding the equipment of the vehicle. For example, the vehicle information includes information indicating the presence or absence of a camera, the type of camera, and the like.

Returning to the explanation of FIG. 3, the collection condition database 42 will be explained. 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. Moreover, "collection condition" is information indicating the collection condition of actual data. For example, the collection conditions include "target vehicle conditions," "recording trigger," "collection contents," and the like.

“Target vehicle condition” indicates a condition of a vehicle to be collected, and “recording trigger” indicates a trigger for starting recording of actual data in the in-vehicle device 50. Further, “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 request ID "001" is a vehicle made by "○○ company", the recording trigger is acceleration (>○○G), and the collected contents are position information and acceleration (front and rear three seconds).

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

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

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

Furthermore, as indicated by the request ID "003", it is also possible to set the target vehicles to all vehicles. Furthermore, as shown in request ID "003", it is also possible to eliminate the recording trigger and record at all times.

Returning to the explanation of FIG. 3, the tag information database 43 will be explained. 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, information regarding time, tag information ID, in-vehicle device ID, etc. are added to the tag information for each request ID and stored. Note that the tag information database 43 is an example of a tag information storage section.

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

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

Further, when receiving a collection request from an emergency vehicle manager, the reception unit 31 notifies the generation unit 32 of the collection request. Note that this collection request includes location information such as the accident site. Further, below, in order to distinguish between an emergency vehicle collection request and other collection requests, an emergency vehicle collection request may be referred to as a collection request.

Further, the reception unit 31 functions as an acquired data collection unit that receives data that satisfies the collection conditions and is transmitted from each vehicle. Here, the data accepted by the reception 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 contents 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. Tag information stored in the information database 43 can be synchronized.

Further, the reception unit 31 functions as an actual data reception unit. When receiving actual data from the in-vehicle device 50, the reception 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 accepted by the reception unit 31.

The collection condition data is data that specifies the recording trigger, data type/format, etc. (captured image data (video, still image, etc., audio data, etc.)), data acquisition position conditions, etc. That is, when the in-vehicle device 50 detects an event corresponding to a recording trigger specified by the collection condition data, it can store the data specified by the collection condition data.

Moreover, when the generation unit 32 generates collection condition data, it transmits it to each vehicle via the transmission unit 33 and sets it in each vehicle. At this time, as shown in FIG. 1B, the collection condition data can be transmitted by specifying the area of the collection condition file.

The transmitter 33 transmits the collection condition data generated by the generator 32 to the in-vehicle device 50, and also transmits a request to send actual data to each in-vehicle device 50.

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

Therefore, the transmitter 33 can request connection via the in-vehicle device 50 to a terminal equipped with a camera, such as a smartphone, owned by the user of the vehicle. That is, the transmitter 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 a request to transmit video data regarding the accident site X to the in-vehicle device 50 (step S21). In response to the transmission request, the in-vehicle device 50 connects to the terminal T capable of capturing video data.

For example, the connection request includes an activation signal that activates a short-range wireless communication device such as Wi-Fi (registered trademark) that the in-vehicle device 50 has, and the in-vehicle device 50 uses a short-range wireless communication device based on the activation signal. A wireless communication device 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 to take an image of the accident scene X to the terminal T, and acquires video data of the image of the accident scene X from the terminal T (step S23). In other words, since the terminal T allows the user to freely capture an image at a desired angle of view, it is possible to appropriately capture video data of the accident scene X.

Thereafter, the in-vehicle device 50 transmits the video data to the data collection device 1, so that the data collection device 1 can collect video data of the accident scene (step S24).

In this way, by collecting image data from the terminal T via the in-vehicle device 50, the data collection device 1 can collect video data in which the accident scene X is properly imaged. In this case, 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). It may be.

Returning to the explanation of FIG. 3, the providing unit 34 will be explained. The providing unit 34 provides tag information and actual data to each user. For example, if the user is an administrator of an emergency vehicle, the providing unit 34 maps the tag information on a map and displays it on the user terminal 10 of the emergency vehicle.

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

Thereafter, the providing unit 34 can provide the collected actual data to the user terminal 10 of the emergency vehicle. Thereby, the occupants of the emergency vehicle (for example, a fire brigade, a police officer, etc.) can check the state of the accident site X on the way to the accident site X. Therefore, prompt and appropriate emergency activities can be carried out.

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

Next, a configuration example of the in-vehicle device 50 will be described using FIG. 7. FIG. 7 is a block diagram of the in-vehicle device 50. Note that FIG. 7 shows a vehicle speed sensor 91 that detects the vehicle speed of the vehicle, a steering angle sensor 92 that detects the steering angle of the vehicle, a G sensor 93 that detects the acceleration of the vehicle, a camera 94 that images the surroundings of the vehicle, and a camera 94 that images the surroundings of the vehicle. A position detection device 95 that detects 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 sends and receives information to and from the network N. The control unit 7 can transmit and receive various information between the communication unit 2 and the network N via the communication unit 2 and the network N.

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 and various circuits having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an input/output port, and the like.

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

Furthermore, at least a part or all of the acquisition section 71, detection section 72, selection section 73, and transmission section 74 of the control section 7 may be implemented using hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). It can also be configured.

Further, 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. Note that the in-vehicle device 50 may acquire the above-described programs and various information via another computer or a portable recording medium connected via a wired or wireless network.

The tag information storage section 81 will be explained. The tag information is data that serves as index data for the corresponding actual data, and is information used by a user, for example, to determine the necessity of checking the actual data.

Specifically, the date and time data of the trigger (when the collection conditions are 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 level of the acceleration value (below the threshold, ~2 times the threshold value, ~3 times the threshold value, etc.)). This tag information is generated based on actual data, and the date/time data, location data, etc. are detected values (processing such as rounding of significant figures is performed as necessary), and the level value is processed using a predetermined formula for the detected values. Tag information can be generated by processing using table data of detected values. The tag information generated in this way is stored in the tag information storage section 81.

Note that since the capacity of tag information is smaller than actual data, the storage capacity problem is not so big. However, as the actual data is deleted, the need for tag information disappears (decreases), so if there is not enough storage capacity, it may not be possible to carry out actual storage. It may be deleted by synchronizing with the data.

In addition, since tag information is used by users to sort and search actual data, real-time performance is important, so when tag information is generated, data is collected immediately (as soon as communication is possible). The process is to send it to 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 collection device 1 and update the tag information on the data collection device 1 side in synchronization. Note that when the tag information is deleted on the data collection device 1 side, the tag information and the corresponding actual data may be deleted on the in-vehicle device 50 side if there is not enough storage capacity.

The actual data storage unit 82 is a storage unit that stores actual data of the collection target type (target actual data) that satisfies collection conditions. The actual data storage unit 82 stores actual data and tag information in association with each other. For example, the real data storage unit 82 is a ring buffer type storage medium, and the oldest 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. Each area of the collection condition storage section 83 stores designated collection condition data.

The acquisition unit 71 of the control unit 7 will be explained. The acquisition unit 71 acquires the collection conditions 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. Thereby, the collection condition storage section 83 of the storage section 8 can be updated to the latest one (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 the detection unit 72 detects an event that satisfies the collection conditions stored in the collection condition storage unit 83, it 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.

For example, when detecting an abnormality in the vehicle, the detecting unit 72 generates a collection condition based on the abnormality, stores it in the autonomous generation region R4 (see FIG. 1B), and collects data via the transmitting unit 74. It is also possible to request the device 1 to analyze the abnormality.

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

In addition, when a transmission request is sent from the data collection device 1, the sorting unit 73 selects the data specified by the transmission request based on the transmission request (designated by the user etc. on the data collection device 1 side based on the tag information). It is also possible to select actual data) from the actual data storage unit 82 and notify the transmitting unit 74.

The transmitting unit 74 transmits the tag information generated by the detecting unit 72 described above to the data collecting device 1 , and also transmits the actual data selected by the selecting unit 73 to the data collecting device 1 .

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

Next, the processing procedure executed by the data collection device 1 according to the embodiment will be described using FIGS. 8 and 9. FIGS. 8 and 9 are flowcharts showing processing procedures executed by the data collection device 1 according to the embodiment. Note that FIG. 8 describes a process related to generation of a collection file, and FIG. 9 describes a process when a collection request is received from an emergency vehicle. Note that 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 a collection request has been received (step S101). When the data collection device 1 receives the collection request (Step S101, Yes), it selects a vehicle that satisfies the collection conditions (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 data collection device 1 ends the process.

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

As shown in FIG. 9, the data collection device 1 determines whether a collection request has been received from an emergency vehicle (step S111). When the data collection device 1 receives the 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, etc. (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). Note that the process of step S115 can also be selected on the data collection device 1 side by selection by the user or selection based on preset conditions.

Subsequently, the data collection device 1 transmits a data collection request to the target vehicle to collect data from the vehicle-mounted device of the target vehicle (step S116). The data collection device 1 then provides the collected data to the emergency vehicle (step S117), and ends the process. Further, if the data collection device 1 has not received a collection request (step S111, No), the data collection device 1 ends the process.

Next, the processing procedure executed by the in-vehicle device 50 will be described using FIG. 10. FIG. 10 is a flowchart showing the processing procedure executed by the in-vehicle device 50. Note that this process is executed when the data collection device 1 makes a data collection request.

As shown in FIG. 10, the in-vehicle device 50 first determines whether or not it has detected an event that satisfies the collection conditions (step S201). If an event has been detected (step S201, Yes), the vehicle-mounted device 50 generated tag information (step S202). Furthermore, if the in-vehicle device 50 does not detect an event in the process of step S201 (step S201, No), the process proceeds to step S204.

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

When the in-vehicle device 50 obtains the 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 there is an end request to end the collection of the actual data (step S207). For example, the termination request includes updating the collection condition file.

Then, when there is a termination request (step S207, Yes), the in-vehicle device 50 terminates the process. Furthermore, if there is no termination request (step S207, No), the in-vehicle device 50 moves to the process of step S201.

Furthermore, when the in-vehicle device 50 does not obtain 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 section 31, the collection condition data generation section, the collection condition setting section, and the acquired data collection section. The receiving unit 31 receives requests for collecting data obtained from 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 it in each vehicle. The reception unit 31 (an example of an acquired data collection unit) receives data that satisfies collection conditions transmitted from each vehicle. Further, the generation unit 32 can set a plurality of collection conditions, and collects acquired data by selecting the plurality of collection conditions.

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

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

1 Data collection device 10 User terminal 31 Reception unit 32 Generation unit 33 Transmission unit 34 Providing 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 Sorting unit 74 Transmission Department S Data collection system

Claims (6)

A data collection method in which a control unit collects data regarding a vehicle from an on-vehicle device installed in the vehicle, the method comprising:
Accepting a request to collect data obtained from the vehicle, generating collection conditions based on the collection request,
storing the collection conditions by dividing them into corresponding areas of a condition file in which areas are set for different purposes of data use, and transmitting the condition file to the in-vehicle device;
A data collection method, comprising receiving data selected and collected according to the collection conditions stored in the condition file from the in-vehicle device. It is possible to set multiple collection conditions regarding tag information, which is an index of data obtained from each vehicle.
The data collection method according to claim 1, further comprising collecting data selected based on the collected tag information. The condition file is
having at least an essential area to which the collection conditions for which the data collection is essential are distributed, and other areas for which the data collection is not essential;
The data collection method according to claim 1, wherein the collection conditions from an emergency vehicle manager are distributed to the required areas. The data collection method according to claim 2, further comprising selecting a vehicle for collecting the data based on the tag information collected based on the condition file, and transmitting a request to transmit the data to an in-vehicle device of the vehicle. 5. The data collection method according to claim 4, further comprising transmitting a connection request to a terminal device having an imaging device to the in-vehicle device when the data type specified by the collection condition is image data. A data collection device that collects data regarding a vehicle from an on-vehicle device installed in the vehicle, the data collection device having a control unit,
The control unit includes:
Accepting a request to collect data obtained from the vehicle, generating collection conditions based on the collection request,
storing the collection conditions by dividing them into corresponding areas of a condition file in which areas are set for different purposes of data use, and transmitting the condition file to the in-vehicle device;
A data collection device that receives data selected and collected according to the collection conditions stored in the condition file from the in-vehicle device.

Images