JP2020038405A - Data collector, data collecting system, method for collecting data, and on-vehicle device - Google Patents

Abstract

To rapidly collect data.SOLUTION: The data collector according to an embodiment includes a collection unit, a reception unit, and an instruction data sending unit. The collection unit collects tag information of data acquired by a vehicle from an on-vehicle device of a vehicle. The reception unit receives a request to collect the acquired data. The instruction data sending unit sends, to the on-vehicle device, instruction data for sending the acquired data which satisfies the request of collection received by the reception unit on the basis of the tag information collected by the collection unit to the on-vehicle device.SELECTED DRAWING: Figure 2

Description

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

  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 increases the communication capacity of data communication and causes congestion of a communication line, so that it may take a lot of time to provide 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, a data collection method, and a vehicle-mounted device capable of quickly collecting data.

  In order to solve the above-described problem and achieve the object, a data collection device according to an embodiment includes a collection unit, a reception unit, and an instruction data transmission unit. The collection unit collects tag information of acquired data acquired by a vehicle from an in-vehicle device mounted on the vehicle. The receiving unit receives a request for collecting the acquired data. The instruction data transmitting unit transmits, to the in-vehicle device, instruction data for causing the in-vehicle device to transmit acquired data that satisfies the collection request received by the receiving unit based on the tag information collected by the collection unit. .

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

FIG. 1 is a diagram showing an outline of a data collection method. FIG. 2 is a system schematic diagram of the data collection system. FIG. 3 is a block diagram of the data collection device. FIG. 4 is a diagram illustrating an example of the vehicle information table. FIG. 5 is a diagram illustrating an example of the collection condition table. FIG. 6A is a diagram (part 1) illustrating an example of a reception screen. FIG. 6B is a diagram (part 2) illustrating an example of the reception screen. FIG. 7 is a block diagram of the vehicle-mounted device. FIG. 8 is a diagram illustrating an example of the collection condition file. FIG. 9 is a flowchart 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, a data collection method, and a vehicle-mounted device 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. FIG. 1 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 shown in FIG.

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

  The example shown in FIG. 1 shows a case where the user is a service provider, a developer, or a general 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. The data collection device 1 can also provide services for general users among users. The general users include users outside the vehicle and users inside the vehicle (for example, drivers).

  Hereinafter, a case will be described in which the service provided by the data collection device 1 is a service that collects video data desired by a general user from each in-vehicle device 50 and provides the collected video data to each general user. .

  Specifically, as shown in FIG. 1, first, the data collection device 1 collects tag information of the acquired data acquired by each vehicle from the in-vehicle device 50 of each vehicle (Step S1).

  Here, the acquired data includes travel data related to travel of the vehicle, video data captured by the vehicle, and the like. The tag information is supplementary information of each data (information indicating the outline and characteristics of each data and suitable for use as index data), and includes meta information, position information, time information, and the like of the data. Including. Further, the data collection device 1 can collect tag information of data that satisfies different collection conditions according to a service provided to a general user in step S1.

  Next, the data collection device 1 receives a data collection request from a general user using a terminal such as a home computer connected to the network (step S2). For example, the data collection device 1 can receive, as a collection request from a general user, video data in a vehicle on which a family rides.

  The data collection device 1 can also receive a collection request from a driver who is a general user via the in-vehicle device 50. For example, the data collection device 1 receives a collection request for video data at a certain point from the driver via the vehicle-mounted device 50.

  Subsequently, the data collection device 1 selects data that satisfies the collection request received in step S2 (step S3). When the data collection device 1 receives the above-described image data in the vehicle as the collection request, the data collection device 1 selects the image data of the vehicle on which the designated family is riding as data satisfying the collection condition.

  When the data collection device 1 receives video data of a certain point as a collection request, the data collection device 1 selects video data captured from a vehicle near the point as data that satisfies the collection condition. That is, the process of step S3 can be said to be a process of selecting a vehicle having data satisfying the collection conditions.

  Subsequently, the data collection device 1 collects the data selected in step S3 (step S4). Specifically, the data collection device 1 transmits instruction data for transmitting data to the vehicle-mounted device 50 of the vehicle holding the data selected in step S3. Thereby, the data collection device 1 can acquire data from the vehicle-mounted device 50.

  Therefore, the data collection device 1 can collect only desired data. That is, the data collection device 1 can reduce the communication load between the data collection device 1 and each of the vehicle-mounted devices 50 by collecting only the data desired by the general user from each of the vehicle-mounted devices 50.

  Thus, the data collection device 1 can quickly collect data. Thereafter, the data collection device 1 provides the data collected from the in-vehicle device 50 to the general user (Step S5).

  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.

  Note that, in the above example, the case where the user is a general user has been described, but the user may be a service provider, a developer, or the like as described above.

  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 travel information of the vehicle in an internal storage medium, sorts the data based on instruction data transmitted from the data collection device 1, and transmits the data to 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.

  The control unit 3 includes a collection unit 31, a reception unit 32, a selection unit 33, an instruction data transmission unit 34, and a provision unit 35. 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 a collection unit 31, a reception unit 32, a selection unit 33, an instruction data transmission unit 34, and a provision unit 35 of the control unit 3 by reading and executing a program stored in the ROM, for example.

  Further, at least a part or all of the collecting unit 31, the receiving unit 32, the selecting unit 33, the instruction data transmitting unit 34, and the providing unit 35 of the control unit 3 may be replaced with an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). ) Can also be used.

  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 collection unit 31 of the control unit 3 collects tag information of the acquired data acquired by each vehicle from the in-vehicle device 50 mounted on each vehicle.

  The collection unit 31 can collect, from each vehicle-mounted device 50, tag information of acquired data that satisfies the collection conditions described in the collection condition file generated for each vehicle-mounted device 50 by the selection unit 33 described later. The collection unit 31 performs a process of storing the collected tag information in the tag information database 43.

  Specifically, the collection 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 data is stored in the in-vehicle device 50. Tag information stored in the tag information database 43 can be synchronized with the tag information stored in the tag information database 43.

  The collection unit 31 can also collect the acquired data transmitted from each of the on-vehicle devices 50, and registers the collected actual data in the actual data database 44.

  The receiving unit 32 receives a request for collecting acquired data from a user. The receiving unit 32 can receive a collection request from a general user inside the vehicle via the in-vehicle device 50 and can also receive a collection request from the general user outside the vehicle via the user terminal 10.

  6A and 6B are diagrams illustrating an example of a reception screen that receives designation of a collection condition. 6A shows a reception screen for a general user inside the vehicle, and FIG. 6B shows a reception screen for a general user outside the vehicle.

  A reception screen for a general user in the vehicle is displayed on a touch panel display (not shown) in the vehicle, and a reception screen for a general user outside the vehicle is displayed on the user terminal 10.

  As shown in FIG. 6A, on a reception screen for a general user in a vehicle, designation of “category”, “data type”, “point” and the like can be received. “Category” indicates a category for the purpose of use of data, and “data type” indicates a type of data to be collected. The “point” indicates a position at which data is collected.

  The example shown in FIG. 6A shows a case where the category is traffic jam information, the data type is camera video, and the point is a 2-chome intersection. That is, in the example illustrated in FIG. 6A, the receiving unit 32 receives the specification of the camera video collection condition at the 2-chome intersection.

  In addition, as shown in FIG. 6B, in the reception screen for a general user outside the vehicle, “in-vehicle device ID” can be specified in addition to the above “category” and “data type”.

  In the example shown in FIG. 6B, “category” is safety confirmation, and the data type is an in-vehicle camera image. In this case, the receiving unit 32 receives the specification of the collection condition of the video data of the in-vehicle camera of the vehicle corresponding to the in-vehicle device ID “0023”. Note that, for example, the in-vehicle device ID illustrated in FIG. 6B can be specified and limited to, for example, the in-vehicle device ID of a vehicle owned by a family of a general user.

  Further, the receiving unit 32 can also receive designation of a collection condition by a voice operation by a general user. In this case, the receiving unit 32 can receive the designation of the collection condition via a voice recognition device (not shown) in the vehicle.

  Returning to the description of FIG. 3, the selection unit 33 will be described. The selection unit 33 selects data that satisfies the collection request received by the reception unit 32 based on the tag information collected by the collection unit 31.

  First, a case where the collection condition is the video data of the above-described 2-chome intersection (hereinafter, referred to as a specific position) will be described. In this case, the selection unit 33 refers to the tag information database 43 and selects a vehicle that has passed the specific position or a vehicle that is to pass the specific position from now.

  For example, as described above, the tag information includes the position information of each vehicle, and the selection unit 33 can obtain the travel route of each vehicle based on the time-series change of the position information.

  By the way, for information that changes dynamically, such as traffic congestion information, data freshness is required. On the other hand, there may be a case where data satisfying a collection request specified by a general user cannot be acquired in real time.

  Specifically, when there is no vehicle passing the specific position for a predetermined time, data on the specific position cannot be collected from the in-vehicle device 50 during the predetermined time.

  In this case, the selection unit 33 may select the video data held by the vehicle that has passed the specific position last or a predetermined number of vehicles from the last as data that satisfies the collection request.

  Subsequently, the selection unit 33 refers to the vehicle information database 41, and determines whether or not a camera (including a recorder) is included in the vehicle-mounted equipment of the vehicle equipped with the vehicle-mounted device 50.

  That is, the selection unit 33 can also select, as the data that satisfies the collection request, of the video data of the vehicle equipped with the camera, out of the vehicle that has passed the specific position or the vehicle that will pass from the specific position.

  Subsequently, a case where the collection condition is video data of an in-vehicle camera of a vehicle (hereinafter, referred to as a designated vehicle) corresponding to the in-vehicle device ID “0023” will be described.

  In this case, since the data to be collected is specified by the above-described collection conditions, the selection unit 33 can select the data to satisfy the data collection conditions specified by the collection conditions.

  As described above, the selection unit 33 can appropriately collect data desired by a general user by selecting a vehicle according to the collection request.

  Then, the selecting unit 33 associates the request ID (see FIG. 5) with the in-vehicle device ID of the vehicle and notifies the instruction data transmitting unit 34 of the request ID. Accordingly, the instruction data transmitting unit 34 described later transmits instruction data for instructing the transmission of the data selected by the selecting unit 33 to the in-vehicle device 50.

  Next, the processing of the selection unit 33 in response to a collection request of a user other than a general user will be described. The selection unit 33 selects a vehicle that satisfies the collection condition. The selection unit 33 refers to the vehicle information database 41 and selects a vehicle satisfying the collection condition from the collection condition database 42. At this time, when one vehicle satisfies a plurality of collection conditions, a plurality of collection conditions are applied to one vehicle.

  Further, the selection unit 33 generates a collection condition file indicating the collection condition corresponding to each vehicle, and transmits the collection condition file to each in-vehicle device 50 via the communication unit 2. Further, when the collection condition database 42 is updated, the selection unit 33 can update the collection condition file.

  When the collection condition file is updated, the selection unit 33 can synchronize the updated collection condition file with the collection condition file stored in each in-vehicle device 50. Therefore, it is possible to collect only target data (actual data: acquired data that is not converted to tag information) required by each user, and it is possible to avoid collecting unnecessary target data.

  The instruction data transmitting unit 34 transmits, to the in-vehicle device 50, instruction data for causing the in-vehicle device 50 to transmit acquired data satisfying the collection request received by the receiving unit 32 based on the tag information collected by the collection unit 31. .

  Specifically, the instruction data transmitting unit 34 transmits the instruction data for transmitting the acquired data to the in-vehicle device 50 that has provided the tag information selected as the acquired data satisfying the collection request by the selecting unit 33. I do. Thereby, the vehicle-mounted device 50 transmits the collected data to the data collection device 1 based on the instruction data.

  The providing unit 35 provides the acquired data collected by the collecting unit 31 to the user terminal 10 or the in-vehicle device 50 of the general user who has made the collection request. At this time, as described above, when data cannot be collected in real time, the providing unit 35 generates acquired data according to a collection request based on past data and provides estimated acquired data.

  When providing the estimated acquisition data, the providing unit 35 may provide the estimated acquisition data after adding reliability to the estimated acquisition data. For example, the providing unit 35 calculates the reliability according to the freshness of the past data used for the estimation. That is, the providing unit 35 can calculate the reliability lower as the past data used for estimation is older data, and can calculate the reliability higher as the past data used for estimation is newer.

  As described above, the providing unit 35 can provide data according to the collection request by estimating the current data from the past data. At this time, by giving the reliability, misunderstanding by the general user can be suppressed in advance.

  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 vehicle speed sensor 91, the steering angle sensor 92, the G sensor 93, the camera 94, and the position detection device 95 are examples of a vehicle state detection unit.

  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. Note that the actual data storage unit 82 is an example of a vehicle situation data storage unit.

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

  As shown in FIG. 8, the collection condition storage unit 83 is divided into a plurality of areas. In each area of the collection condition storage unit 83, collection conditions having different usage purposes are stored.

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

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

  When a fire, a traffic accident, or the like occurs in the vicinity of each vehicle, the data collection device 1 transmits a transmission request for requesting a camera image to the vehicle-mounted device 50 located near the site. Then, by providing the camera image to the emergency vehicle, the data collection device 1 can check the situation of the site earlier than the emergency vehicle arrives at the site.

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

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

  Thereby, for example, the data collection device 1 collects tag information and actual data from each in-vehicle device 50, collects data for specifying the cause of the abnormality, and specifies the cause based on the data. The countermeasure can be transmitted to the in-vehicle device 50.

  Returning to the description of FIG. 7, the acquisition unit 71 of the control unit 7 will be described. The acquisition unit 71 acquires 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). Note that the acquisition unit 71 functions as a vehicle information data input unit.

  The detecting unit 72 detects an event that satisfies the collection condition stored in the collection condition file. When detecting an event that satisfies the collection condition stored in the collection condition file, the detection unit 72 generates tag information corresponding to the collection condition and transmits the tag information to the selection unit 73 and the transmission unit 74, respectively.

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

  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. The transmitting unit 74 is an example of a tag information transmitting unit and a vehicle situation data transmitting unit.

  Next, a processing procedure executed by the data collection device 1 according to the embodiment will be described with reference to FIG. FIG. 9 is a flowchart illustrating a processing procedure executed by the data collection device 1 according to the embodiment. This process is repeatedly performed while the data collection device 1 is operating.

  First, as shown in FIG. 9, the data collection device 1 collects tag information from the vehicle-mounted device 50 of each vehicle (Step S101). Subsequently, the data collection device 1 determines whether a collection request has been received from a general user (Step S102).

  When receiving the collection request (Yes at Step S102), the data collection device 1 selects data that satisfies the collection request based on the tag information (Step S103). Subsequently, the data collection device 1 transmits the instruction data of the data selected in step S104 to the vehicle-mounted device 50 (step S104), provides the collected target data (step S105), and ends the process.

  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 executed when a data collection request is made.

  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 or not the instruction data has been acquired from the data collection device 1 (Step S204).

  When the in-vehicle device 50 has acquired the instruction data (Step S204, Yes), the in-vehicle device 50 selects the acquired data to be transmitted (Step S205). Subsequently, the in-vehicle device 50 transmits the selected acquired data to the data collection device 1 (Step S206), and determines whether or not there is a termination request to terminate the acquisition of the acquired 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 in-vehicle device 50 has not acquired the instruction data (No at Step S204), the process proceeds to Step S207.

  As described above, the data collection device 1 according to the embodiment includes the collection unit 31, the reception unit 32, and the instruction data transmission unit 34. The collection unit 31 collects tag information of data acquired by the vehicle from the in-vehicle device 50 mounted on the vehicle. The receiving unit 32 receives a request for collecting acquired data. The instruction data transmitting unit 34 transmits, to the in-vehicle device 50, instruction data for causing the in-vehicle device 50 to transmit acquired data satisfying the collection request received by the receiving unit 32 based on the tag information collected by the collection unit 31. . Therefore, according to the data collection device 1 according to the embodiment, data can be quickly collected.

  In the above-described embodiment, a case has been described in which the data collection device 1 and the in-vehicle device 50 of the target vehicle directly transmit and receive data via the network N. However, the present invention is not limited to this.

  For example, when a collection request is received for video data in a vehicle, a case where the in-vehicle device 50 of the target vehicle exists outside the communication range of the network N is also assumed.

  In this case, the selecting unit 33 selects another in-vehicle device 50 within the communication range, and the instruction data transmitting unit 34 requests the in-vehicle device 50 to transfer a collection request to the in-vehicle device 50 of the target vehicle. Can be sent.

  The in-vehicle device 50 that has received the transfer request can transmit the collection conditions to the in-vehicle device 50 of the target vehicle using communication means other than the network N, such as inter-vehicle communication. That is, an ad hoc network between vehicles may be used.

  At this time, the transfer request can be transmitted to the in-vehicle device 50 of the target vehicle via the plurality of in-vehicle devices 50. At this time, the in-vehicle device 50 of the target vehicle can transmit the data specified by the collection condition to the data collection device 1 again using inter-vehicle communication.

  As described above, in the data collection system S, when it is not possible to directly communicate with the target vehicle, it is possible to collect data from the target vehicle by using another vehicle-mounted device 50 as an intermediary.

  In addition, for example, the data collection device 1 receives a collection request for position information of a specified designated vehicle from a general user outside the vehicle, but when the vehicle is out of the communication range of the network N, or when the vehicle-mounted device 50 It is also assumed that the power is not turned on.

  In this case, the data collection device 1 can also estimate the current location based on the past position information of the designated vehicle, and request the vehicles around the estimated current location to collect video data. That is, the data collection device 1 can transmit instruction data to vehicles other than the designated vehicle.

  For example, in this case, the data collection device 1 can specify the position information of the designated vehicle by analyzing the video data, and can also provide the position information to the general user.

  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 collection unit 32 reception unit 33 selection unit 34 instruction data transmission unit 35 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 unit 81 tag information storage unit 82 actual data storage unit 83 collection condition storage unit S data collection system

Claims (11)

A collection unit that collects tag information of acquired data acquired by the vehicle from an in-vehicle device mounted on the vehicle,
A receiving unit that receives a request to collect the acquired data,
An instruction data transmitting unit configured to transmit, to the in-vehicle device, instruction data for causing the in-vehicle device to transmit acquired data satisfying the collection request received by the receiving unit based on the tag information collected by the collection unit. A data collection device, characterized in that: The data collection device according to claim 1, further comprising a providing unit configured to provide a collection request source of the acquired data collected from the on-vehicle device. The providing unit,
When the acquired data that matches the collection request received by the reception unit is not collected from the in-vehicle device, generates estimated acquisition data according to the collection request based on past acquisition data, and generates the estimated acquisition data. The data collection device according to claim 2, wherein the data collection device is provided. The providing unit,
The data collection device according to claim 3, wherein a reliability of the estimated acquired data is calculated, and the estimated acquired data is provided in association with the reliability. The tag information is
Including location information of the vehicle,
The instruction data transmitting unit,
The data collection device according to any one of claims 1 to 4, wherein instruction data for transmitting the acquired data at a specific position is transmitted to the on-vehicle device based on the position information of the vehicle. . The instruction data transmitting unit,
The data collection device according to any one of claims 1 to 4, wherein instruction data for transmitting acquisition data of the vehicle specified by the collection request is transmitted to a vehicle-mounted device of the vehicle. The collecting unit,
The tag information or the acquisition data about the said vehicle is collected from the in-vehicle device of the vehicle around the said vehicle, when tag information or acquisition data cannot be collected from the said designated vehicle. The data collection of Claim 6 characterized by the above-mentioned. apparatus. A data collection device according to any one of claims 1 to 7,
A data collection system comprising: the on-vehicle device. The in-vehicle device,
The data collection system according to claim 8, wherein when the tag information or the acquired data cannot be transmitted to the data collection device, the data is transmitted / received via another communication device. A collection step of collecting tag information of acquired data acquired by the vehicle from an in-vehicle device mounted on the vehicle,
A receiving step of receiving a request for collecting the acquired data,
An instruction data transmitting step of transmitting, to the in-vehicle device, instruction data for causing the in-vehicle device to transmit acquired data satisfying the collection request received in the receiving process based on the tag information collected in the collection process. A data collection method characterized in that: A vehicle status data input unit for inputting vehicle status data relating to the vehicle from various vehicle status detection means provided in the vehicle,
Based on a collection request from a data collection device, a vehicle situation data storage unit that stores the vehicle situation data input by the vehicle situation data input unit,
Based on a collection request from a data collection device, a tag information generation unit that generates tag information of vehicle situation data stored in the vehicle situation data storage unit,
A tag information transmitting unit that transmits the tag information generated by the tag information generating unit to the data collection device,
Vehicle status data transmission that extracts vehicle status data that satisfies the transmission instruction data from the vehicle status data storage unit based on the transmission instruction data and transmits the vehicle status data based on the tag information from the data collection device to the data collection device. An in-vehicle device comprising:

Images