JP2020038408A - Data collector, data collecting system, and method for collecting data - Google Patents

Abstract

To rapidly collect data.SOLUTION: The data collector according to an embodiment includes a reception unit, a collection condition data generation unit, a collection condition setting unit, and an acquisition data collection unit. The reception unit receives a request to collect data obtained by each vehicle. The collection condition data generation unit generates collection condition data showing the condition of collecting data on the basis of the collection request received by the reception unit. The collection condition setting unit sends the collection condition data generated by the collection condition data generation unit to each vehicle and sets the data in each vehicle. The acquisition data collection unit receives data which satisfies the collection condition sent from each vehicle. The collection condition setting unit can set a plurality of collection conditions, and the acquisition data collection unit selects a plurality of collection conditions and collects the acquisition data.SELECTED DRAWING: Figure 3

Description

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

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

JP 2018-55581A

  In recent years, in addition to road information, it has been required to quickly collect various types of data from in-vehicle devices. However, collecting various types of data from each in-vehicle device may cause congestion of a communication line, and may require a lot of 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 device, a data collection system, and a data collection method that can quickly collect data.

  In order to solve the above-described problem and achieve the object, a data collection device according to an embodiment includes a reception unit, a collection condition data generation unit, a collection condition setting unit, and an acquisition data collection unit. The receiving unit receives a request to collect data obtained in 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 collection condition data in each vehicle. The acquisition data collection unit receives data that satisfies the collection conditions 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 acquired data.

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

FIG. 1A is a diagram showing an outline of a data collection method. FIG. 1B is a diagram illustrating an example of the 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 illustrating an example of the vehicle information table. FIG. 5 is a diagram illustrating an example of the collection condition table. FIG. 6 is a diagram illustrating an example of the connection request. FIG. 7 is a block diagram of the vehicle-mounted device. FIG. 8 is a flowchart (part 1) illustrating a processing procedure executed by the data collection device. FIG. 9 is a flowchart (part 2) illustrating a processing procedure executed by the data collection device. FIG. 10 is a flowchart illustrating 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 an embodiment will be described in detail with reference to the accompanying drawings. The present invention is not limited by the embodiment.

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

  The data collection device 1 is a data collection server that receives a data collection request from a data user and collects data from the vehicle-mounted device 50 based on the received collection request.

  The data collection device 1 provides the collected data to each user. The example illustrated in FIG. 1A illustrates a case where the user is a service provider, a developer, or a user. 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, first, the data collection device 1 receives a collection request from a user (step S1). Such a collection request includes a collection condition specified by each user. The collection conditions include information on data types, information on 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 has, for example, information on each vehicle as a database, and can select a vehicle that satisfies 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 use of the data. An example of the condition file division 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 vehicle-mounted device 50 of each vehicle, and each vehicle-mounted device 50 selects data that satisfies the collection conditions indicated in the condition file (step S4), transmitting 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 the 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 can selectively transmit the data). Thereafter, the data collection device 1 provides the data collected from each in-vehicle device 50 to the user (Step S6).

  As described above, the data collection device 1 according to the embodiment can reduce the communication capacity of data transmitted from each vehicle-mounted device 50 by collecting only the data desired by the user from each vehicle-mounted 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 division of the condition file will be described with reference to FIG. 1B. FIG. 1B is a diagram illustrating an example of the division of the condition file. 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 having different usage purposes. 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 data transmission mode is made different for the purpose of distinguishing the processing mode of the acquired data (for example, changing the processing mode depending on the purpose of use), such as the indispensability and priority of data transmission.

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

  The essential area R2 is an area for storing, when the collection condition is satisfied, a collection condition in which transmission of data satisfying the collection condition is essential. For example, collection conditions set by an emergency vehicle such as an ambulance or a police car are assigned to the essential region R2.

  The development area R3 is an area for storing a collection request by a developer of the vehicle. The collection condition set by the developer is assigned to the development area R3.

  The autonomous generation area R4 is an area in which the in-vehicle device 50 stores the collection conditions autonomously generated by itself. For example, when detecting an abnormality in the vehicle, the in-vehicle device 50 can generate a data collection condition regarding a phenomenon similar to the abnormality and store the data collection condition in the autonomous generation region R4. Since the collection conditions are generated on the vehicle-mounted device 50 side, the collection conditions are distributed to the autonomous generation region R4 by the vehicle-mounted device 50.

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

  The data collected based on the collection conditions of the development region R3 is finally provided to the developer, and the data collected based on the collection conditions of the autonomous generation region R4 is finally provided to the vehicle-mounted 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 store the collection conditions having different data usage purposes.

  In particular, as for the collection condition of the essential region R2, the collection condition of urgent data is stored because it is related to human life. Therefore, the collection condition of the essential region R2 is collected without obtaining the approval of the user. On the other hand, with respect to the collection conditions of the other areas (particularly, the service area R1), collection is performed with the approval of the user.

  In this manner, the data collection device 1 generates a condition file after allocating the condition to an area for storing the collection condition according to the purpose of use of the collection condition. This makes it possible to appropriately collect data according to the collection conditions. Further, by providing the essential region R2, it is possible to reliably collect data with high urgency.

  Next, the configuration of the data collection system according to the embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a configuration example of a 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 the 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 the user, and is 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 to transmit the above-mentioned collection request to the data collection device 1. Further, the user terminal 10 can also present the data provided from the data collection device 1 to the user. The in-vehicle device 50 can be used as the user terminal 10.

  The in-vehicle device 50 is a communication device mounted on each vehicle. The in-vehicle device 50 stores the data specified by the selection request in the internal storage medium such as the traveling information of the vehicle, 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. 3, the data collection device 1 includes a communication unit 2, a control unit 3, and a storage unit 4.

  The communication unit 2 is a communication interface for transmitting and receiving information to and from the network N. The control unit 3 can transmit and receive various types of information to and from each other 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 with reference to FIG. 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 unit 2, a control unit 3, and a storage unit 4.

  The communication unit 2 is a communication interface for transmitting and receiving information to and from the network N. The control unit 3 can transmit and receive various types of information to and from each other 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 having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), an input / output port, and various circuits.

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

  In addition, at least some or all of the receiving unit 31, the generating unit 32, the transmitting unit 33, and the providing unit 34 of the control unit 3 are implemented by hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). It can also be configured.

  The storage unit 4 corresponds to, for example, a RAM or an HDD. The RAM or HDD includes 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 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 for each vehicle. FIG. 4 is a diagram illustrating an example of the 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”, 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 on the owner of the vehicle on 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 gender, age, address, occupation, and the like of the owner.

  "Vehicle type information" is information on the type of vehicle, and is information on the vehicle type name and year. “In-vehicle equipment” is information on 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 description of FIG. 3, the collection condition database 42 will be described. The collection condition database 42 has a collection condition table relating to collection conditions received from the user terminal 10. FIG. 5 is a diagram illustrating an example of the 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 for identifying a user.

  “Request ID” is an identifier for identifying a collection request. The “collection condition” is information indicating a condition for collecting actual data. For example, the collection conditions include “target vehicle conditions”, “recording trigger”, “collected contents”, and the like.

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

  In the example illustrated in FIG. 5, the target vehicle with the request ID “001” is a vehicle manufactured by “XX Corporation”, the recording trigger is acceleration (> ○○ G), and the collected contents are position information and acceleration (3 Seconds).

  In this case, when the in-vehicle device 50 detects that the acceleration has exceeded XXG, the in-vehicle device 50 records the acceleration data for 3 seconds before and after along with the position information based on the time when the acceleration has exceeded XXG. become.

  The target vehicle of the request ID “002” is a user in his 60s or older, the recording trigger is the brake pressure (> （psi), and the acceleration exceeds ○ psi (for 5 seconds before and after). ).

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

  Further, as shown in the request ID “003”, the target vehicle can be all vehicles. Further, as shown by the request ID “003”, it is possible to eliminate the recording trigger and always record.

  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 the tag information transmitted from each in-vehicle device 50. For example, the tag information database stores the tag information with information about time, a tag information ID, an in-vehicle device ID, and the like 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 vehicle-mounted device 50 based on the 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.

  Subsequently, 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 a collection condition of data to be collected. When receiving the collection condition, the receiving unit 31 adds the request ID to the collection condition and registers the request in the collection condition database 42.

  When receiving a collection request from the emergency vehicle manager, the reception unit 31 notifies the generation unit 32 of the collection request. Note that the collection request includes position information of the accident site and the like. In the following, in order to distinguish an emergency vehicle collection request from another collection request, the emergency vehicle collection request may be described as a collection request.

  In addition, the reception unit 31 functions as an acquisition data collection unit that receives data that satisfies the collection conditions transmitted from each vehicle. Here, the data received by the receiving unit 31 includes tag data and actual data.

  The receiving 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, so that the tag information stored in the in-vehicle device 50 and the tag are updated. Tag information stored in the information database 43 can be synchronized.

  The receiving unit 31 functions as an actual data receiving unit. When receiving the 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.

  The acquisition condition data is data for specifying the above-described recording trigger, data type and format (captured image data (moving image / still image / etc., Audio data, etc.)), data acquisition position conditions, and the like. That is, when detecting the event corresponding to the recording trigger specified by the collection condition data, the in-vehicle device 50 can store the data specified by the collection condition data.

  After generating the collection condition data, the generation unit 32 transmits the collection condition data to each vehicle via the transmission unit 33, and sets the data for each vehicle. At this time, as shown in FIG. 1B, the collection condition data can be transmitted by designating the area of the collection condition file.

  The transmitting unit 33 transmits the collection condition data generated by the generating unit 32 to the in-vehicle devices 50 and transmits a transmission request of actual data to each in-vehicle device 50.

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

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

  FIG. 6 is a diagram illustrating an example of the connection request. As shown in FIG. 6, the data collection device 1 transmits a transmission request for video data to the accident site X to the vehicle-mounted device 50 (Step S21). Upon receiving 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 for activating a short-range wireless communication device such as wi-fi (registered trademark) included in the in-vehicle device 50. The 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 an imaging request of the accident site X to the terminal T and acquires video data of the image of the accident site X from the terminal T (step S23). In other words, if the terminal T is used, it is possible for the user to freely take an image at a desired angle of view, so that the image data of the accident site X can be appropriately taken.

  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 the video data of the accident site (Step S24).

  As described above, the data collection device 1 can collect video data in which the accident site X is appropriately imaged by collecting image data from the terminal T via the on-vehicle device 50. At this time, the terminal T connected to the in-vehicle device 50 may be owned by a user of the in-vehicle device 50, or may be owned by a person other than the user (for example, a passerby or a wild horse). It may be.

  Returning to the description of FIG. 3, the providing unit 34 will be described. The providing unit 34 provides tag information and actual data to each user. For example, when the user is the manager of the emergency vehicle, the providing unit 34 maps the tag information on a map and displays the tag information 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. 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.

  Thereafter, the providing unit 34 can provide the collected actual data to the user terminal 10 of the emergency vehicle. Thereby, an occupant of an emergency vehicle (for example, a fire brigade or a police officer) can check the situation of the accident site X on the way to the accident site X. Therefore, quick and appropriate rescue operations can be performed.

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

  Next, a configuration example of the vehicle-mounted device 50 will be described with reference to FIG. FIG. 7 is a block diagram of the vehicle-mounted device 50. FIG. 7 shows a vehicle speed sensor 91 for detecting the vehicle speed of the vehicle, 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 periphery of the vehicle, and a A position detecting device 95 for detecting a position is also shown.

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

  The in-vehicle device 50 includes a communication unit 6, a control unit 7, and a storage unit 8. The communication unit 6 is a communication interface for transmitting and receiving information to and from the network N. 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.

  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), a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), an input / output port, 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, for example, reading and executing a program stored in the ROM.

  Further, at least some 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 an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). It can also be configured.

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

  The tag information storage unit 81 will be described. The tag information is data having a role as index data of the corresponding real data, and is information used by a user or the like to determine the necessity of confirming the real data.

  Specifically, the date and time data of the trigger (at the time when the collection condition is satisfied), the position data, the data size of the actual data, and the value level of the trigger occurrence cause (for example, when the acceleration value is a trigger, the acceleration value level (less than the threshold value,閾 値 2 times threshold, 倍 3 times threshold...)). The tag information is generated based on the actual data. The date and time data, the position data, and the like are detected values (processing for rounding significant figures is performed as necessary), and the level values are processed by a predetermined calculation formula for the detected values. And tag information can be generated by processing using table data of detection values or the like. The tag information generated in this way is stored in the tag information storage unit 81.

  Since the capacity of tag information is smaller than that of actual data, the problem of storage capacity is not so large. However, the necessity of tag information is eliminated (decreased) as the actual data is erased. The data may be deleted in synchronization with the data.

  In addition, since tag information is used by users to select and search for actual data, real-time processing is important. Therefore, when tag information is generated, data is collected immediately (as soon as communication is possible). This is a process of transmitting to the device 1.

  Further, since the tag information stored in the in-vehicle device 50 and the tag information stored in the data collection device 1 need to be the same data, the tag information is updated (newly created or deleted) on the in-vehicle device 50 side. In this case, the information must be transmitted to the data collection device 1 promptly, and the tag information of the data collection device 1 needs to be updated synchronously. When the data collection device 1 deletes the tag information, the in-vehicle device 50 may delete the tag information and the corresponding actual data if the storage device has no capacity.

  The actual data storage unit 82 is a storage unit that stores actual data (target actual data) of the collection target type that satisfies the 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 storage medium of a ring buffer system, and overwrites old real data with new data at any time in order.

  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 unit 83 stores specified collection condition data.

  The acquisition unit 71 of the control unit 7 will be described. The acquisition unit 71 acquires a collection condition and a 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 unit 83 of the storage unit 8 can be updated to the latest one (synchronization with the collection condition stored in the data collection device 1).

  The detection unit 72 detects an event that satisfies 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 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 a vehicle abnormality, the detection unit 72 generates a collection condition based on the abnormality, stores the condition in the autonomous generation region 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 real data storage unit 82 in association with the real data satisfying the collection condition. That is, the selection unit 73 can select the actual data that satisfies the collection conditions and store the selected data in the actual data storage unit 82.

  In addition, when the 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 (designated by the user or the like based on the tag information on the data collection device 1 side). (The actual data) may 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.

  Thus, 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, 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 FIG. 9 are flowcharts illustrating a processing procedure executed by the data collection device 1 according to the embodiment. Note that FIG. 8 illustrates a process related to generation of a collection file, and FIG. 9 illustrates a process when a collection request is received from an emergency vehicle. These processes are repeatedly performed while the data collection device 1 is operating.

  First, as shown in FIG. 8, the data collection device 1 determines whether a collection request has been received (step S101). When receiving the collection request (Step S101, Yes), the data collection device 1 selects a vehicle that satisfies the collection condition (Step S102).

  Subsequently, the data collection device 1 generates collection condition data (step S103), transmits the collection condition data by designating the area of the collection condition file of the vehicle-mounted device 50 (step S104), 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 data collection device 1 ends the process as it is.

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

  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 receiving the collection request (Yes at Step S111), the data collection device 1 selects a vehicle near the site (Step S112), and transmits collection condition data for acquiring image data or the like at the site (Step S113). .

  Subsequently, the data collection device 1 acquires the tag information transmitted from the in-vehicle device 50 that has transmitted the collection condition data (Step S114), and selects the collection data (Step S115). Note that the processing in step S115 can also be selected on the data collection device 1 side by selection by a user or selection based on a preset condition 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 processing. If the data collection device 1 has not received the collection request (No at Step S111), the process ends.

  Next, a processing procedure executed by the vehicle-mounted device 50 will be described with reference to FIG. FIG. 10 is a flowchart illustrating a processing procedure executed by the in-vehicle device 50. This process is performed when a data collection request is made by the data collection device 1.

  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), the in-vehicle device 50 specifies the event using the collection condition file. The generated tag information is generated (step S202). If no event is detected in step S201 (step S201, No), the in-vehicle device 50 proceeds to step S204.

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

  When acquiring the transmission request (Yes at Step S204), the in-vehicle device 50 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 end the collection of the actual data (Step S207). For example, the termination request includes an update of the collection condition file.

  Then, when there is an end request (step S207, Yes), the in-vehicle device 50 ends the processing. When there is no end request (No at Step S207), the in-vehicle device 50 proceeds to the process at Step S201.

  If the transmission request has not been acquired (No at Step S204), the in-vehicle device 50 proceeds to the process at 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 acquisition 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 a data collection condition based on the collection request received by the reception unit 31. The generating unit 32 (an example of a collecting condition setting unit) transmits the collecting condition data generated by the collecting condition data generating unit to each vehicle and sets the collecting condition data for each vehicle. The reception unit 31 (an example of an acquisition data collection unit) receives data that satisfies the 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, 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. Thus, the broader aspects of the present invention are not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and equivalents thereof.

Reference Signs List 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 selection unit 74 transmission Section S Data collection system

Claims (7)

A receiving unit that receives a request to collect data obtained from 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;
Collection condition data generated by the collection condition data generation unit, a collection condition setting unit that transmits to each vehicle and sets 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,
The acquisition data collection unit,
A data collection device characterized by selecting a plurality of collection conditions and collecting acquired data. The collection condition setting unit,
The collection condition data is divided into condition files and stored, and the condition file is transmitted to the in-vehicle device of each vehicle,
The acquisition data collection unit,
The data collection apparatus according to claim 1, wherein data based on the collection conditions stored in the condition file is selected and collected. The condition file is
Having at least an indispensable area in which the collection conditions in which collection of the data is indispensable,
The collection condition setting unit,
The data collection device according to claim 2, wherein the collection condition from an emergency vehicle manager is allocated to the essential area. The condition file is
Indicating the collection conditions of the tag information related to the data,
A transmission unit that selects a vehicle from which the data is to be collected based on the tag information collected based on the condition file, and transmits a transmission request for the data to a vehicle-mounted device of the vehicle. 2. A data collection device according to claim 1. The transmission unit,
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,
A data collection system comprising: a vehicle-mounted device mounted on the vehicle. A receiving step of receiving a request to collect 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,
The collection condition data generated in the collection condition data generation step, a collection condition setting step of transmitting to each vehicle and setting each vehicle,
An acquisition data collection step of receiving acquisition data satisfying the collection condition transmitted from each vehicle,
The collection condition setting step,
It is possible to set multiple collection conditions,
The acquisition data collection step,
A data collection method characterized by collecting acquired data by selecting a plurality of collection conditions.

Images