JP7271135B2 - In-vehicle device, data collection system and data collection method - Google Patents

Description

The disclosed embodiments relate to an in-vehicle device, a data collection system, and a data collection method.

2. Description of the Related Art Conventionally, a data collection system is known that collects road information from an in-vehicle device mounted on each vehicle. Such a data collection system collects road information of a desired position by selecting vehicles for which road information is to be collected based on the position information of each vehicle (see, for example, Patent Document 1).

JP 2018-055581 A

However, the conventional technology described above has room for further improvement in realizing data collection with high reliability and low communication load.

Specifically, in the conventional technology described above, the vehicle-mounted device collects necessary data according to a request notification from the center and uploads it to the center device. However, in-vehicle equipment generally has a limited storage capacity. Omission may occur. As a result, there is a risk that the accuracy of information analysis on the center device side will drop.

In addition, in-vehicle equipment generally communicates with the center equipment via a mobile phone network or the like. increase the burden.

One aspect of the embodiments has been made in view of the above, and an object thereof is to provide an in-vehicle device, a data collection system, and a data collection method capable of realizing highly reliable data collection with a small communication load. and

An in -vehicle device according to an aspect of an embodiment is an in-vehicle device that records vehicle data and its meta information and transmits the meta information to a host device outside the vehicle , and includes a control unit. When the vehicle enters a communication area in which communication of a predetermined standard is possible, the control unit transfers the vehicle data to an external device outside the vehicle having a larger storage capacity than the on-vehicle device, Upon receiving a command to transmit the vehicle data from the device, the external device is instructed to transmit the vehicle data to the host device .

According to one aspect of the embodiment, data collection with high reliability and low communication load can be realized.

FIG. 1A is a schematic explanatory diagram (part 1) of a data collection method according to an embodiment; FIG. 1B is a schematic explanatory diagram (part 2) of the data collection method according to the embodiment; FIG. 1C is a schematic explanatory diagram (part 3) of the data collection method according to the embodiment; FIG. 1D is a schematic explanatory diagram (part 4) of the data collection method according to the embodiment; FIG. 1E is a schematic explanatory diagram (No. 5) of the data collection method according to the embodiment; FIG. 1F is a schematic explanatory diagram (No. 6) of the data collection method according to the embodiment; FIG. 1G is a schematic explanatory diagram (No. 7) of the data collection method according to the embodiment; FIG. 2A is a block diagram (part 1) illustrating a configuration example of the data collection system according to the embodiment; FIG. 2B is a block diagram (part 2) illustrating a configuration example of the data collection system according to the embodiment; FIG. 3 is a diagram showing a modification when the communication environment in a specific area is not good. FIG. 4 is a diagram showing an example of history information of an in-vehicle device. FIG. 5 is a diagram showing an example of selection of a transfer destination. FIG. 6 is a diagram showing a modification in which processing instructions are added to an upload request. FIG. 7 is a diagram showing an example of history information of the data storage device. FIG. 8 is a diagram illustrating a processing sequence executed by the data collection system according to the embodiment;

Hereinafter, embodiments of an in-vehicle device, a data collection system, and a data collection method disclosed in the present application will be described in detail with reference to the accompanying drawings. In addition, this invention is not limited by embodiment shown below.

First, an overview of the data collection method according to the embodiment will be described with reference to FIGS. 1A to 1G. 1A to 1G are schematic explanatory diagrams (part 1) to (part 7) of the data collection method according to the embodiment. 1A to 1G, the data collection system 1 to which the data collection method according to the embodiment is applied will be described as an example.

As shown in FIG. 1A, the data collection system 1 according to the embodiment includes a data collection device 10 and in-vehicle devices 100-1, 100-2 mounted on vehicles V-1, V-2, V-3, . , 100-3 . . . and the user terminal 200. In the following description, the vehicle in general is referred to as "vehicle V", and the in-vehicle device as a whole is referred to as "in-vehicle device 100".

The data collection device 10 is configured as a cloud server that provides a cloud service via a network N such as the Internet or a mobile phone network, for example. , collects vehicle data from each in-vehicle device 100 and provides it to data users.

The in-vehicle device 100 is, for example, a drive recorder having various sensors such as a camera, an acceleration sensor, and a GPS (Global Positioning System) sensor, a storage device, a microcomputer, and the like. Data is taken from vehicle V.

The in-vehicle device 100 also uploads the collected vehicle data to the data collection device 10 as necessary. By using the drive recorder as the in-vehicle device 100 in this way, the in-vehicle components mounted on the vehicle V can be made more efficient. It should be noted that the in-vehicle device 100 and the drive recorder may be configured separately without using them together.

The user terminal 200 is a terminal used by a data user, and is for example a notebook PC (Personal Computer), a desktop PC, a tablet terminal, a PDA (Personal Digital Assistant), a smart phone, an eyeglass type, or a watch type information processing device. Examples include a wearable device, which is a terminal.

A data user is, for example, a developer who develops automatic driving technology based on vehicle data provided from the data collection device 10 . The data collection device 10 provides the data user with a user interface (hereinafter referred to as “UI”) screen that can be accessed via the user terminal 200 .

The data user designates vehicle data collection conditions via the UI screen, as shown in FIG. 1A (step S1). Then, the data collection device 10 that has received this distributes the collection conditions to each vehicle V, for example, in a file format (step S2).

The collection conditions include various parameters related to collection of vehicle data, as shown in FIG. 1B. Various parameters are, for example, "target vehicle", "data type", "collection trigger condition", "collection period", etc., as shown in FIG.

The "target vehicle" is the identification information of the vehicle V to be collected. Further, the "data type" is the type of data to be collected, such as the accelerator opening rate, for example. The "collection trigger condition" is a condition that triggers collection, and is, for example, when the vehicle speed exceeds a predetermined speed.

Then, each in-vehicle device 100 uploads the vehicle data collected in each vehicle V to the data collection device 10 constantly or based on an upload request from the data collection device 10 (step S3), and the data collection device 10 Accumulate (step S4). Then, the data user browses or downloads the vehicle data accumulated in the data collection device 10 via the aforementioned UI screen, for example (step S5), and uses it for analysis for development.

Although not shown in FIG. 1A, the vehicle data uploaded by the in-vehicle device 100 includes tag data T and actual data R. As shown in FIG.

More specifically, a series of flows until vehicle data is provided to data users in the data collection system 1, including this point, will be described with reference to FIGS. 1C to 1E. As shown in FIG. 1C, the data user first designates collection conditions using the user terminal 200 connected to the data collection device 10 .

Also, at this time, the data collecting device 10 generates data for generating tag data T that is added to the actual data R to be collected and has characteristics as index data used for searching the actual data R and for grasping the outline of the actual data R. to generate The data for generating the tag data T is generated based on the operation of the data user while using the program and data for generation stored in the user terminal 200 or the data collection device 10 .

Then, the specified collection conditions and the data for generating the generated tag data T are stored in the data collection device 10, distributed to the vehicle V that is the object of data collection, and also stored in the in-vehicle device 100. be done.

Next, each in-vehicle device 100 monitors the output data of various sensors, and stores the actual data R in the storage device when an event that satisfies the stored collection condition occurs. Further, each in-vehicle device 100 generates and stores tag data T corresponding to the actual data R based on the stored data for generation of the tag data T and the actual data R. FIG.

Note that the tag data T is not data that is a simple excerpt of a part of the actual data R. When a data user refers to the tag data T, he/she can grasp the outline of the actual data R and judge whether the actual data R is necessary or not. It is preferable that the information is converted to meta-information to some extent.

Then, each in-vehicle device 100 uploads the tag data T to the data collection device 10, and the data collection device 10 stores the tag data T. FIG. Note that the actual data R is not uploaded to the data collection device 10 at this time.

Then, when the data user connects to the data collection device 10 to check the data collection status or collect the actual data R using the user terminal 200, meta information based on the tag data T collected by the data collection device 10 is generated. is displayed on the user terminal 200 . At the same time, a UI screen for performing an operation of collecting actual data R corresponding to each tag data T is displayed.

Then, as shown in FIG. 1D, when the data user designates the tag data T corresponding to the actual data R to be collected using the user terminal 200, the actual data is sent to the corresponding on-vehicle device 100 via the data collection device 10. "Instruction data" specifying R is transmitted. In addition, hereinafter, such instruction data may be referred to as an "upload request".

After that, as shown in FIG. 1E, the designated actual data R is uploaded from each in-vehicle device 100 to the data collection device 10 and stored in the data collection device 10 . Then, the data user accesses the actual data R stored in the data collection device 10 using the user terminal 200, and browses or downloads the actual data R. FIG.

From the viewpoint of the storage capacity of the in-vehicle device 100, the actual data R uploaded to the data collection device 10 and the tag data T corresponding thereto are deleted from the in-vehicle device 100 after the upload to the data collection device 10 is completed. is preferred.

However, if the data collection device 10 does not send an upload request, the vehicle data will not be deleted from the in-vehicle device 100 during this period. Then, as shown in FIG. 1F, the storage capacity of the in-vehicle device 100 becomes MAX, and a situation may occur in which "accumulation is not possible". If this happens, even if an upload request is received from the data collection device 10, the vehicle data will be missing, so the upload will not be possible.

Therefore, in the data collection method according to the embodiment, it is determined whether or not the vehicle V has stopped in a specific area having a predetermined communication environment. The vehicle data accumulated in the in-vehicle device 100 is transferred to the data storage device via the communication environment.

Specifically, as shown in FIG. 1G, in the data collection method according to the embodiment, first, the in-vehicle device 100 collects and accumulates vehicle data based on predetermined collection conditions while the vehicle V is running (step S11). At this time, the in-vehicle device 100 always uploads the tag data T (step S12). This can be done because the tag data T has a much smaller data capacity than the actual data.

Also, the in-vehicle device 100 determines whether the vehicle V has stopped in the specific area 500 (step S13). A specific area 500 is an area where a predetermined communication environment, such as a public wireless LAN service such as a so-called Wi-Fi spot, can be used.

Specifically, the in-vehicle device 100 stores data regarding the specific area 500 in advance. The original data is, for example, created by the driver of the vehicle V on a home PC or the like and transferred to the in-vehicle device 100 via communication or a storage medium. "Creating with a home PC or the like" means, for example, downloading communication spot information provided by a data communication company and processing the information to create the information.

Then, when the vehicle V stops in the corresponding area, the in-vehicle device 100 collates the position information of the specific area 500 included in the data about the specific area 500 with the current position information of the vehicle V detected by the GPS sensor. By doing so, it is determined that the vehicle V is located in the specific area 500 .

Further, whether or not the vehicle has stopped at such a position can be determined, for example, whether or not the vehicle speed has continued for a predetermined time or longer, whether or not the engine has stopped, whether or not the parking brake has been turned on, and whether the ignition switch has been turned on. It can be done in various ways, such as whether it is turned off.

Further, whether or not the vehicle V is located in the specific area 500 can be determined based on the connection status when the vehicle V in the specific area 500 tries to establish a communication connection with respect to the position in the specific area 500 . For example, if the vehicle V is connected to the access point P and the connection strength is equal to or greater than a predetermined value, it can be determined that the vehicle V is located in the specific area 500 . Of course, the determination based on the connection status of communication, the determination based on the comparison of the position information described above, and the determination whether or not the vehicle has stopped may be combined in a complex manner.

By such a method, the in-vehicle device 100 transfers at least the actual data R to the data storage device 300 via the access point P in the specific area 500 when it is determined that the vehicle V has stopped in the specific area 500 (step S14). ).

Here, the data storage device 300 is, for example, a home server or the like provided at the home of the driver of the vehicle V and having a storage capacity at least greater than that of the in-vehicle device 100 . Also, "transfer" referred to here means transmitting to the data storage device 300 and deleting from the in-vehicle device 100 after transmission is completed.

As a result, each time the vehicle stops at the specific area 500, the in-vehicle device 100 causes the data storage device 300 to store the actual data R, which has a large capacity burden, among the vehicle data. can be deleted. Therefore, it is possible to reduce the load on the storage capacity of the in-vehicle device 100 and prevent omissions in the accumulated vehicle data. In addition, since a communication environment such as a public wireless LAN service is used, it is possible to contribute to reducing the communication load compared to the case of using a mobile phone network or the like.

Further, in the data collection method according to the embodiment, when the in-vehicle device 100 receives from the data collection device 10 a request for uploading the vehicle data stored in the data storage device 300 (step S15), the request is sent to the data storage device. 300 (step S16). It should be noted that such request transfer does not necessarily have to go through the access point P.

Then, the in-vehicle device 100 uploads the actual data R from the data storage device 300 to the data collection device 10 by such request transfer (step S17). In this manner, the in-vehicle device 100 always accepts an upload request from the data collection device 10, so that the data collection device 10 can always unify the request destination, and the in-vehicle device 100 can upload data to the vehicle on the in-vehicle device 100 side. Whether or not to provide data can be controlled. That is, the in-vehicle device 100 can manage data transmission/reception in the same manner as when uploading the actual data R to the data collection device 10 .

From the viewpoint of such data transmission/reception management, it is preferable that the transfer history transferred from the in-vehicle device 100 to the data storage device 300 is stored in the in-vehicle device 100 . Moreover, it is preferable that the transmission history uploaded from the data storage device 300 to the data collection device 10 is accumulated in the data storage device 300 .

From the viewpoint of the storage capacity of the data storage device 300, it is preferable that the actual data R uploaded from the data storage device 300 to the data collection device 10 be deleted after the transmission is completed. It is not necessary to delete it, depending on the availability of

As described above, in the data collection method according to the embodiment, it is determined whether or not the vehicle V has stopped in a specific area having a predetermined communication environment. In this case, the vehicle data accumulated in the in-vehicle device 100 is transferred to the data storage device 300 via the communication environment.

Therefore, according to the data collection method according to the embodiment, highly reliable data collection with a small communication load is realized. Hereinafter, a configuration example of the data collection system 1 according to the embodiment will be described more specifically.

2A and 2B are block diagrams (Part 1) and (Part 2) showing a configuration example of the data collection system 1 according to the embodiment. Note that FIGS. 2A and 2B show only the constituent elements necessary to describe the features of the embodiment, and omit the description of general constituent elements.

In other words, each component illustrated in FIGS. 2A and 2B is functionally conceptual and does not necessarily need to be physically configured as illustrated. For example, the specific form of distribution/integration of each block is not limited to the one shown in the figure. It is possible to integrate and configure.

In addition, in the description using FIGS. 2A and 2B, the description of components that have already been described may be simplified or omitted.

As shown in FIG. 2A, the data collection system 1 according to the embodiment includes a data collection device 10, an in-vehicle device 100, a user terminal 200, and a data storage device 300.

First, the data collection device 10 will be described. The data collection device 10 includes a communication section 11 , a storage section 12 and a control section 13 .

The communication unit 11 is implemented by, for example, a NIC (Network Interface Card) or the like. The communication unit 11 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the in-vehicle device 100 , the user terminal 200 and the data storage device 300 via the network N.

The storage unit 12 is implemented by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. , and the collected data DB 12b.

The collection condition information DB 12a accumulates collection conditions designated by the user terminal 200 and received by the reception unit 13a, which will be described later. In other words, the collection condition information DB 12a includes past records regarding collection conditions.

The collected data DB 12b accumulates collected data collected from each in-vehicle device 100 by a collection unit 13c, which will be described later. That is, the collected data DB 12b includes the past record of collected data. Collected data includes tag data T and actual data R described above.

The control unit 13 is a controller, and various programs stored in a storage device inside the data collection device 10 are stored in the RAM as a work area by, for example, a CPU (Central Processing Unit) or MPU (Micro Processing Unit). It is realized by executing as Also, the control unit 13 can be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 13 includes a reception unit 13a, a distribution unit 13b, a collection unit 13c, and a provision unit 13d, and implements or executes information processing functions and actions described below.

The reception unit 13a receives collection conditions specified by the data user from the user terminal 200 via the communication unit 11, and stores them in the collection condition information DB 12a. Further, the reception unit 13a receives designation of the tag data T from the user terminal 200 and notifies the collection unit 13c. Further, the receiving unit 13a receives, for example, a viewing request or a download request for the actual data R from the user terminal 200, and notifies the providing unit 13d.

The distribution unit 13b distributes the set collection conditions stored in the collection condition information DB 12a to the target vehicle V via the communication unit 11, for example, in a file format.

The collecting unit 13c collects the tag data T uploaded from the in-vehicle device 100 and stores it in the collected data DB 12b. In addition, the collection unit 13c transmits a request for uploading the actual data R corresponding to the tag data T to the in-vehicle device 100 based on the specification of the tag data T notified from the reception unit 13a.

Also, the collection unit 13c collects the actual data R uploaded from the in-vehicle device 100 or the data storage device 300 based on the upload request via the communication unit 11, and accumulates them in the collected data DB 12b.

The providing unit 13d extracts the relevant vehicle data from the collected data DB 12b based on the viewing request or the download request notified from the receiving unit 13a, edits it according to the UI screen as necessary, and distributes it to the user terminal. 200.

Next, the in-vehicle device 100 will be described. The in-vehicle device 100 includes a communication section 101 , a storage section 102 and a control section 103 . In addition, as described above, the in-vehicle device 100 is connected to various sensors 150 such as a camera, an acceleration sensor, and a GPS sensor.

Communication unit 101 is implemented by, for example, a NIC. The communication unit 101 is wirelessly connected to the network N, and transmits and receives information to and from the data collection device 10 via the network N. The communication unit 101 also receives output data from various sensors 150 .

The storage unit 102 is implemented, for example, by a semiconductor memory device such as a RAM and a flash memory, and stores collection condition information 102a, vehicle data information 102b, and history information 102c in the example of FIG. 2A.

The collection condition information 102a is information including the collection conditions distributed from the data collection device 10. FIG. The vehicle data information 102b is information including vehicle data collected by the collecting unit 103c, which will be described later. Vehicle data includes tag data T and actual data R described above.

The history information 102 c is information including a transfer history of transferring the actual data R from the in-vehicle device 100 to the data storage device 300 .

Like the control unit 13, the control unit 103 is a controller, and is realized by, for example, executing various programs stored in a storage device inside the in-vehicle device 100 using a RAM as a work area by a CPU, MPU, or the like. be done. Also, the control unit 103 can be realized by an integrated circuit such as an ASIC or FPGA, for example.

The control unit 103 has an acquisition unit 103a, a detection unit 103b, a collection unit 103c, an upload unit 103d, a determination unit 103e, and a transfer unit 103f, and implements the information processing functions and actions described below. or run.

The acquisition unit 103a acquires the collection conditions distributed from the data collection device 10 and stores them in the collection condition information 102a. The detection unit 103b monitors the output data from the various sensors 150 and detects the occurrence of an event that serves as a trigger under the collection conditions.

For example, the detection unit 103b causes the collection unit 103c to collect vehicle data when detecting the occurrence of an event that triggers collection of vehicle data under the collection condition.

The collecting unit 103c collects vehicle data based on the output data of the various sensors 150 and stores the vehicle data in the vehicle data information 102b when the detection unit 103b detects the occurrence of a trigger for collecting vehicle data. Further, the collection unit 103c stops collection of vehicle data when the detection unit 103b detects generation of a trigger for stopping collection of vehicle data.

The upload unit 103d uploads the tag data T to the data collection device 10 all the time. Further, when the upload unit 103d receives an upload request for the actual data R from the data collection device 10 via the communication unit 101, it notifies the transfer unit 103f of this.

The determination unit 103e determines whether or not the vehicle V has stopped in the specific area 500 based on output data from the various sensors 150, for example. Also, the determination unit 103e notifies the transfer unit 103f of the determination result.

The transfer unit 103f transmits the actual data R accumulated in the vehicle data information 102b to the data storage device 300 via the access point P when the determination unit 103e determines that the vehicle V has stopped in the specific area 500. . Further, the transfer unit 103f deletes the actual data R transmitted to the data storage device 300 from the vehicle data information 102b after the transmission is completed.

Further, when the upload unit 103d notifies the transfer unit 103f of the upload request for the actual data R from the data collection device 10, the transfer unit 103f transfers the upload request to the data storage device 300, and transfers the actual data R to the data storage device 300. Send R to the data collection device 10 .

Further, the transfer unit 103f accumulates a transfer history of transferring the actual data R to the data storage device 300 in the history information 102c. In addition, the transfer unit 103f causes the data storage device 300 to accumulate a transmission history in which the data storage device 300 is caused to transmit the actual data R to the data collection device 10 .

Next, the data storage device 300 will be described. As shown in FIG. 2B, the data storage device 300 includes a communication section 301, a storage section 302, and a control section 303.

Communication unit 301 is implemented by, for example, a NIC. The communication unit 11 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the in-vehicle device 100 and the data collection device 10 via the network N.

The storage unit 302 is realized by, for example, a semiconductor memory device such as a RAM or flash memory, or a storage device such as a hard disk or an optical disk, and stores accumulated data DB 302a and history information 302b in the example of FIG. 2B.

The accumulated data DB 302a stores the actual data R transferred from the in-vehicle device 100. FIG. The history information 302b is information including a history of transmission of the actual data R from the data storage device 300 to the data collection device 10. FIG.

The control unit 303 is a controller, and is realized, for example, by executing various programs stored in a storage device inside the data storage apparatus 300 using a RAM as a work area by a CPU, MPU, or the like. Also, the control unit 303 can be implemented by an integrated circuit such as an ASIC or FPGA, for example.

The control unit 303 has a receiving unit 303a, a receiving unit 303b, a processing unit 303c, an uploading unit 303d, and a providing unit 303e, and realizes or executes information processing functions and actions described below.

The reception unit 303a receives a transfer request for the actual data R from the in-vehicle device 100 via the communication unit 301, and notifies the reception unit 303b of the request. The reception unit 303a also receives an upload request transmitted from the data collection device 10 to the in-vehicle device 100 and transferred from the in-vehicle device 100 to the data storage device 300, and notifies the upload unit 303d of this.

The receiving unit 303b receives the actual data R transmitted from the in-vehicle device 100 via the communication unit 301 based on the transfer request notified from the receiving unit 303a, and stores it in the accumulated data DB 302a.

When the actual data R stored in the accumulated data DB 302a requires processing, the processing unit 303c performs such processing and stores the processed data in the accumulated data DB 302a. The processing includes, for example, when the user accesses the data storage device 300 from the in-vehicle device 100, a smartphone, or the like and wants to view the stored data in the accumulated data DB 302a, analysis, tabulation, editing, etc. are performed so as to facilitate viewing. .

The upload unit 303d extracts the corresponding actual data R from the accumulated data DB 302a based on the upload request notified from the reception unit 303a, and transmits it to the data collection device 10. FIG. Also, the upload unit 303d accumulates a transmission history of transmitting the actual data R to the data collection device 10 in the history information 302b.

For example, when there is a request to view the stored data of the accumulated data DB 302a or the history information 302b via the in-vehicle device 100, a smartphone, or the like, the providing unit 303e extracts the relevant data in response to the request, and displays the UI screen or the like. provided to users via

Next, a case where the communication environment in the specific area 500 is not good will be described using FIG. FIG. 3 is a diagram showing a modification when the communication environment in the specific area 500 is not good.

As shown in FIG. 3, although the vehicle V has stopped in the specific area 500, there may be cases where the communication environment in the specific area 500 is not good, such as when the access point P has "weak radio wave intensity". If the determination unit 103e of the in-vehicle device 100 can determine such a situation based on the output data of the various sensors 150, the transfer unit 103f makes a transfer reservation to notify the data storage device 300 of the transfer schedule of the actual data R. should only be performed.

If the data storage device 300 stores a history of such notifications, it will be possible to transfer the actual data R at least when the communication environment is not good and the actual data R cannot be transferred, or when the communication environment is improved, the transfer of the actual data R will not be possible. It is possible for the user to grasp what is being done.

Next, an example of the history information 102c of the in-vehicle device 100 will be explained using FIG. FIG. 4 is a diagram showing an example of the history information 102c of the in-vehicle device 100. As shown in FIG.

As shown in FIG. 4, the history information 102c includes, for example, a "data ID" item, a "transfer date and time" item, a "specific area" item, a "transfer destination" item, and an "attribute information" item.

The “data ID” item stores identification information of the actual data R transferred from the in-vehicle device 100 to the data storage device 300 . The "transfer date and time" item stores the respective transfer date and time. Identification information of the specific area 500 is stored in the “specific area” item. The “transfer destination” item stores the identification information of the data storage device 300 that is the transfer destination.

Here, the data storage device 300, which is the “transfer destination”, can be arbitrarily selected by the user from the in-vehicle device 100 or the like. FIG. 5 is a diagram showing an example of selection of a transfer destination. As shown in FIG. 5, for example, the identification information of the data storage device 300, which is the transfer destination, is displayed as a list on the UI screen of the in-vehicle device 100 or the like in a drop-down list or the like, thereby allowing the user to arbitrarily select the transfer destination. is possible.

The transfer destination may be a cloud server, another vehicle X owned by the user, a general storage device, or the like, in addition to the home server or smartphone. Further, such selection may be made at the time of initial setting of the in-vehicle device 100, before the vehicle V is started, etc., or may be made before the vehicle stops in the specific area 500 and the transfer of the actual data R is started. good too.

Returning to the description of FIG. The "attribute information" item stores, for example, content that can be said to be attribute information of the tag data T, for example, content indicating that the data is for "sudden braking" or "steep gradient running".

Each item of the history information 102c is preferably recorded as text data with a small data volume. As a result, it is possible to prevent the storage capacity of the in-vehicle device 100 from being overloaded by the history information 102c.

Next, a case where a processing instruction is added to an upload request from the data collection device 10 will be described with reference to FIG. FIG. 6 is a diagram showing a modification in which processing instructions are added to an upload request.

As shown in FIG. 6, an upload request from the data collection device 10 may be accompanied by a data processing instruction. At this time, if the actual data R corresponding to the in-vehicle device 100 still exists and processing corresponding to the processing instruction cannot be performed due to "insufficient resources" or the like, the transfer unit 103f of the in-vehicle device 100 transfers the actual data R At the same time, the processing instruction and the upload request may be transferred, and the processing unit 303c of the data storage device 300 may be made to perform the processing.

As a result, even if the in-vehicle device 100 cannot process the data, the actual data R processed according to the instruction from the data collection device 10 can be uploaded from the data storage device 300. It becomes possible.

If the in-vehicle device 100 can execute the processing, the real data R processed by the in-vehicle device 100 may be transferred to the data storage device 300 together with an upload request. Further, when receiving an upload request and a processing instruction for the actual data R already transferred to the data storage device 300 , the in-vehicle device 100 may transfer only the upload request and the processing instruction to the data storage device 300 as they are.

Next, an example of the history information 302b of the data storage device 300 will be explained using FIG. FIG. 7 is a diagram showing an example of the history information 302b of the data storage device 300. As shown in FIG.

First, although not shown, the history information 302b includes items such as date and time, which are transmission histories for each data ID, similar to the history information 102c of the in-vehicle device 100. FIG. In addition to this, the history information 302b may include an item indicating "state" for each data ID, as shown in FIG. 7, for example. Here, an example is given in which items indicating the "upload" state and the "delete" state are included.

That is, as shown in FIG. 7, the data storage device 300 may delete the actual data R that has already been uploaded to the data collection device 10 (see data ID "001" in the figure). Further, the data storage device 300 may manage the actual data R before uploading so that it cannot be deleted (see data ID "003" in the figure).

Further, the data storage device 300 may not necessarily delete the actual data R uploaded to the data collection device 10 after uploading, for example, if there is a surplus storage capacity (see data ID "002" in the figure). . In addition, it is possible to give priority to the actual data R by designation from the data collection device 10, the in-vehicle device 100, etc., and the data storage device 300 determines whether deletion is possible and the order according to the priority. You may do so.

Next, a processing sequence executed by the data collection system 1 according to the embodiment will be described using FIG. FIG. 8 is a diagram showing a processing sequence executed by the data collection system 1 according to the embodiment. It should be noted that the processing sequence shown in FIG.

First, the in-vehicle device 100 collects actual data R based on the distributed collection conditions (step S101). Tag data T is generated based on the actual data R, and the in-vehicle device 100 constantly transmits the tag data T to the data collection device 10 (step S102). Then, the data collection device 10 accumulates such tag data T (step S103).

While such steps S101 to S103 are repeated, the in-vehicle device 100 detects that the vehicle V has stopped in the specific area 500 (step S104). Then, the in-vehicle device 100 transmits the actual data R to the data storage device 300 via the access point P of the specific area 500 (step S105), and deletes the actual data R after the transmission is completed (step S106). The data storage device 300 also accumulates the actual data R transmitted from the in-vehicle device 100 (step S107).

While steps S101 to S107 are repeated, the data collection device 10 transmits an upload request for the actual data R to the in-vehicle device 100, for example, based on an instruction from the user terminal 200 (step S108).

Then, the in-vehicle device 100 transfers the upload request to the data storage device 300 (step S109). The data storage device 300 that has received such an upload request extracts the actual data R according to the request and transmits it to the data collection device 10 (step S110). Then, the data collection device 10 accumulates the actual data R (step S111).

As described above, the in-vehicle device 100 according to the embodiment is mounted in the vehicle V, collects and accumulates actual data R data (corresponding to an example of "data related to the vehicle"), and also collects and accumulates the data collection device 10 (" A vehicle-mounted device 100 that transmits actual data R to a data collection device 10 based on an upload request (equivalent to an example of a “transmission instruction”) from a “higher-level device”), and includes a determination unit 103e and a transfer unit. 103f. Determining unit 103e determines whether or not vehicle V is located in specific area 500 having a predetermined communication environment. When the determination unit 103e determines that the vehicle V is located in the specific area 500, the transfer unit 103f transfers the accumulated actual data R to the data storage device 300 (an example of an “external device”) via the communication environment. ).

Therefore, according to the in-vehicle device 100 according to the embodiment, data collection with high reliability and low communication load can be realized.

Further, the transfer unit 103f transmits the accumulated actual data R to the data storage device 300, and deletes it after the transmission is completed.

Therefore, according to the in-vehicle device 100 according to the embodiment, the data storage device 300 stores the actual data R having a large capacity load, and the in-vehicle device 100 itself can delete the transmitted actual data R. Therefore, it is possible to reduce the load on the storage capacity of the in-vehicle device 100 and prevent omissions in the accumulated vehicle data.

Further, when the transfer unit 103f receives an upload request for the actual data R transferred to the data storage device 300 from the data collection device 10, the transfer unit 103f transfers the upload request to the data storage device 300 and executes it on the data storage device 300. Data R is sent to the data collection device 10 .

Therefore, according to the in-vehicle device 100 according to the embodiment, the request destination can always be unified for the data collection device 10, and the in-vehicle device 100 can control whether or not to provide vehicle data. That is, the in-vehicle device 100 can manage data transmission/reception in the same manner as when uploading the actual data R to the data collection device 10 .

In addition, the transfer unit 103f causes the in-vehicle device 100 to store a transfer history of transferring the actual data R to the data storage device 300 .

Therefore, according to the in-vehicle device 100 according to the embodiment, the in-vehicle device 100 can centrally manage the status of which actual data R is stored in which data storage device 300 .

In addition, the transfer unit 103f causes the data storage device 300 to accumulate a transmission history in which the data storage device 300 is caused to transmit the actual data R to the data collection device 10 .

Therefore, according to the in-vehicle device 100 according to the embodiment, the data storage device 300 can centrally manage the status of which actual data R was uploaded from the data storage device 300 to the data collection device 10 and when.

Further, the transfer unit 103f, when a processing instruction for the actual data R is added to the upload request from the data collection device 10 and processing corresponding to the processing instruction in the in-vehicle device 100 is impossible, the data storage device 300 After transferring the processing instruction together with the upload request to the data storage device 300 to process the actual data R, the data storage device 300 is caused to transmit the actual data R to the data collection device 10 .

Therefore, according to the in-vehicle device 100 according to the embodiment, even if the in-vehicle device 100 cannot perform the processing, the actual data R processed according to the instruction from the data collection device 10 can be obtained. , can be uploaded from the data storage device 300 .

In the above-described embodiment, the case where the actual data R is transferred from the in-vehicle device 100 to the data storage device 300 and exclusively uploaded from the data storage device 300 to the data collection device 10 is taken as an example. Device 100 may upload actual data R to data collection device 10 .

For example, the data collection device 10 can request immediate uploading of actual data R directly from the in-vehicle device 100, and when the in-vehicle device 100 accepts such a request, the data collection device 10 can perform the upload without involving the specific area 500. , the actual data R may be uploaded to the data collection device 10 . Of course, the actual data R may be deleted from the in-vehicle device 100 after the completion.

Further, in the above-described embodiment, the data user is assumed to be a developer of automatic driving technology, etc., but it is an example of a user, such as a corporate user such as a service provider, or a general individual user. good too.

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

1 data collection system 10 data collection device 12a collection condition information DB
12b Collected data DB
13a reception unit 13b distribution unit 13c collection unit 13d provision unit 100 in-vehicle device 102a collection condition information 102b vehicle data information 102c history information 103a acquisition unit 103b detection unit 103c collection unit 103d upload unit 103e determination unit 103f transfer unit 150 various sensors 200 use person Terminal 300 Data storage device 302a Accumulated data DB
302b history information 303a reception unit 303b reception unit 303c processing unit 303d upload unit 303e provision unit 500 specific area R actual data T tag data V vehicle

Claims (10)

An in-vehicle device that records vehicle data and its meta information and transmits the meta information to a host device outside the vehicle ,
transferring the vehicle data to an external device outside the vehicle having a larger storage capacity than the in-vehicle device when the vehicle enters a communication area in which communication of a predetermined standard is possible;
a control unit that instructs the external device to transmit the vehicle data to the host device when receiving a command to transmit the vehicle data from the host device based on the meta information;
In-vehicle device. The control unit
transmitting the recorded data to the external device and deleting it after transmission is completed;
The in-vehicle device according to claim 1 . The control unit
When a transmission command for data transferred to the external device is received from the host device, the transmission command is transferred to the external device and causes the external device to transmit the data to the host device;
The in-vehicle device according to claim 1 or 2. The control unit
Accumulating a transfer history of transferring data to the external device in the in-vehicle device;
The in-vehicle device according to claim 1, 2 or 3. The control unit
allowing the external device to accumulate a transmission history of causing the external device to transmit data to the host device;
The in-vehicle device according to any one of claims 1 to 4. The control unit
When a data processing instruction is added to the transmission instruction from the host device and the processing corresponding to the processing instruction in the on-vehicle device is impossible, the processing instruction is transferred to the external device together with the transmission instruction. causing the device to process the data and then causing the external device to transmit the data to the host device;
The in-vehicle device according to any one of claims 1 to 5. An in-vehicle device that records vehicle data and its meta information and transmits the meta information to a host device outside the vehicle, the host device, and an external device outside the vehicle that has a larger storage capacity than the in-vehicle device,
The in-vehicle device
transferring the vehicle data to the external device when the vehicle enters a communication area in which predetermined standard communication is possible;
Upon receiving a command to transmit the vehicle data from the host device based on the meta information, instructing the external device to transmit the vehicle data to the host device;
data collection system. A data collection method executed by an in-vehicle device that records vehicle data and its meta information and transmits the meta information to a host device outside the vehicle,
transferring the vehicle data to an external device outside the vehicle having a storage capacity larger than that of the in-vehicle device when the vehicle enters a communication area in which predetermined standard communication is possible;
instructing the external device to transmit the vehicle data to the host device upon receiving a command to transmit the vehicle data from the host device based on the meta information;
data collection methods, including; An in-vehicle device mounted on a vehicle for collecting and accumulating data related to the vehicle and transmitting the collected data to the host device based on a transmission instruction from the host device,
determining whether the vehicle is located in a specific area having a predetermined communication environment;
transferring the accumulated data to an external device via the communication environment when it is determined that the vehicle is located in a specific area;
a control unit that, when a transmission command for data transferred to the external device is received from the host device, transfers the transmission command to the external device and causes the external device to transmit data to the host device;
In-vehicle device. An in-vehicle device mounted on a vehicle for collecting and accumulating data related to the vehicle and transmitting the collected data to the host device based on a transmission instruction from the host device,
determining whether the vehicle is located in a specific area having a predetermined communication environment;
transferring the accumulated data to an external device via the communication environment when it is determined that the vehicle is located in a specific area;
When a data processing instruction is added to the transmission instruction from the host device, and processing corresponding to the processing instruction in the on-vehicle device is impossible, the processing instruction is transferred to the external device together with the transmission instruction, and the processing instruction is transferred to the external device. Having a control unit that causes the external device to transmit the data to the host device after causing the device to process the data,
In-vehicle device.

Images