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

Abstract

To achieve a data collection that has high reliability and a low communication load.SOLUTION: An in-vehicle device is mounted on a vehicle, collects data related to the vehicle and accumulates them, and transmits the data to a higher-level device on the basis of a transmission instruction from the higher-level device. The in-vehicle device includes a determination part and a transfer part. The determination part determines whether the vehicle is located in a specific area with a predetermined communication environment. The transfer part transfers the accumulated data to an external device via the communication environment when the determination part determines that the vehicle is located in the specific area.SELECTED DRAWING: Figure 2A

Description

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

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

Japanese Unexamined Patent Publication No. 2018-055581

  However, the above-described conventional technique has room for further improvement in realizing highly reliable data collection with a small communication load.

  Specifically, in the above-mentioned conventional technique, the in-vehicle device collects necessary data according to the request notification from the center and uploads the data to the center device. However, in-vehicle devices generally have a limited storage capacity, so if data is collected for a long period of time, or if the data to be collected includes image data from a camera, etc., the in-vehicle device will not be able to store the data. It may come off. As a result, the accuracy of information analysis on the side of the center device may be reduced.

  Further, the in-vehicle device generally communicates with the center device through a mobile phone network or the like. However, when it is necessary to upload a large amount of data such as the above-mentioned image data, communication of traffic and cost is performed. It will increase the burden.

  One aspect of the embodiment is made in view of the above, and an object thereof is to provide a vehicle-mounted device, a data collection system, and a data collection method that can realize highly reliable data collection with a small communication load. And

  An on-vehicle device according to an aspect of the embodiment is an on-vehicle device that is mounted on a vehicle, collects and stores data about the vehicle, and transmits the collected data to the upper device based on a transmission instruction from the upper device. , A determination unit and a transfer unit. The determination unit determines whether the vehicle is located in a specific area having a predetermined communication environment. The transfer unit transfers the accumulated data to an external device via the communication environment when the determination unit determines that the vehicle is located in the specific area.

  According to one aspect of the embodiment, it is possible to realize highly reliable data collection with a small communication load.

FIG. 1A is a schematic explanatory diagram (part 1) of the data collection method according to the 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 (5) of the data collection method according to the embodiment. FIG. 1F is a schematic explanatory view (No. 6) of the data collection method according to the embodiment. FIG. 1G is a schematic explanatory view (No. 7) of the data collection method according to the embodiment. FIG. 2A is a block diagram (No. 1) showing a configuration example of the data collection system according to the embodiment. FIG. 2B is a block diagram (No. 2) showing a configuration example of the data collection system according to the embodiment. FIG. 3 is a diagram showing a modified example when the communication environment in the 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 illustrating an example of selecting a transfer destination. FIG. 6 is a diagram showing a modified example in which a processing instruction is added to the upload request. FIG. 7 is a diagram showing an example of history information of the data storage device. FIG. 8 is a diagram showing 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. The present invention is not limited to the embodiments described below.

  First, the outline 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 (No. 1) to (No. 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, a data collection system 1 according to an embodiment includes a data collection device 10 and vehicle-mounted devices 100-1 and 100-2 mounted on vehicles V-1, V-2, V-3, ... , 100-3 ... And the user terminal 200. In the following, the term "vehicle V" is used to refer to the whole vehicle, and the term "vehicle apparatus 100" is used to refer to the in-vehicle device in general.

  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, receives a vehicle data collection request from a data user, and based on the received collection request. , Collects vehicle data from each in-vehicle device 100 and provides it to the data user.

  The vehicle-mounted device 100 is a drive recorder having various sensors such as a camera, an acceleration sensor, a GPS (Global Positioning System) sensor, a storage device, and a microcomputer, and is a vehicle that responds to a collection request received by the data collection device 10. Data is collected from vehicle V.

  Further, the in-vehicle device 100 uploads the collected vehicle data to the data collection device 10 as needed. By using the drive recorder also as the in-vehicle device 100 in this way, the in-vehicle components mounted on the vehicle V can be made efficient. Note that the in-vehicle device 100 and the drive recorder may be separately configured without being shared.

  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 smartphone, glasses-type or clock-type information processing. For example, a wearable device that is a terminal.

  Further, the data user is, for example, a developer who develops an automatic driving technique based on vehicle data provided from the data collection device 10. The data collection device 10 provides such a data user with a user interface (hereinafter referred to as “UI”) screen accessible via the user terminal 200.

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

  As shown in FIG. 1B, the collection condition includes various parameters regarding collection of vehicle data. The various parameters are, for example, “target vehicle”, “data type”, “collection trigger condition”, “collection period”, etc., as shown in FIG.

  The "target vehicle" is identification information of the vehicle V to be collected. Further, the “data type” is the type of data to be collected, for example, the accelerator opening rate. The “collection trigger condition” is a condition that triggers collection, and is, for example, a case where 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 in response to an upload request from the data collection device 10 (step S3), and the data collection device 10 stores the data. It is accumulated (step S4). Then, the data user browses or downloads the vehicle data accumulated in the data collection device 10 through, for example, the above-mentioned UI screen (step S5) and uses it for analysis for development or the like.

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

  Including this point, more specifically, a series of flow until the vehicle data is provided to the data user in the data collection system 1 will be described with reference to FIGS. 1C to 1E. As shown in FIG. 1C, first, the data user specifies the collection condition by the user terminal 200 connected to the data collection device 10.

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

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

  Next, each in-vehicle apparatus 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 conditions occurs. Further, each in-vehicle device 100 generates and stores the tag data T corresponding to the actual data R based on the stored generation data of the tag data T and the actual data R.

  Note that the tag data T is not data obtained by simply extracting a part of the actual data R, but when the data user refers to the outline of the actual data R, the necessity of the actual data R can be determined. It is preferably meta-informationized 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. At this time, the actual data R is not uploaded to the data collection device 10.

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

  Then, as shown in FIG. 1D, when the data user specifies the tag data T corresponding to the actual data R to be collected by the user terminal 200, the actual data is sent to the in-vehicle device 100 via the data collecting device 10. "Instruction data" designating R is transmitted. In the following, such instruction data may be referred to as “upload request”.

  Thereafter, as shown in FIG. 1E, the designated actual data R is uploaded from each in-vehicle device 100 to the data collecting device 10 and stored in the data collecting device 10. Then, the data user uses the user terminal 200 to access the actual data R stored in the data collection device 10 to browse or download the actual data R.

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

  However, when the upload request is not transmitted from the data collection device 10, the vehicle data is not deleted from the vehicle-mounted device 100 during this period. Then, as shown in FIG. 1F, the storage capacity of the in-vehicle apparatus 100 becomes MAX, and a situation in which “storage is impossible” may occur. If this happens, even if an upload request comes from the data collection device 10, the vehicle data is missing, so uploading is also impossible.

  Therefore, in the data collection method according to the embodiment, it is determined whether the vehicle V has stopped in a specific area having a predetermined communication environment, and as a result, when it is determined that the vehicle V has stopped in the specific area, The vehicle data accumulated in the vehicle-mounted 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 a predetermined collection condition while the vehicle V is traveling (step). S11). At this time, the in-vehicle apparatus 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.

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

  Specifically, the in-vehicle device 100 stores in advance data regarding the specific area 500. The original data is, for example, created by the driver of the vehicle V using a home PC or the like, and transferred to the vehicle-mounted apparatus 100 via communication or a storage medium. “Created by a home PC or the like” means, for example, downloading and processing communication spot information or the like provided by a data communication company and processing 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 regarding 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 is stopped at such a position is determined by, for example, whether or not the vehicle speed is 0 for a predetermined time or more, whether or not the engine has stopped, whether or not the parking brake is on, and the ignition switch. It can be performed by various methods such as whether or not it is turned off.

  Further, whether or not the vehicle V is located in the specific area 500 can also be determined by the connection status of the vehicle V in the specific area 500 trying to connect 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 higher 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 the communication, the determination based on the collation of the position information described above, and the determination whether or not the vehicle has stopped may be combined in combination.

  By such a method, the in-vehicle apparatus 100 transfers at least the actual data R to the data storage apparatus 300 via the access point P of 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 that is provided at the driver's home of the vehicle V and has a storage capacity that is at least larger than that of the vehicle-mounted device 100. Further, the “transfer” referred to here is transmission to the data storage device 300 and deletion from the vehicle-mounted device 100 after the transmission is completed.

  As a result, the in-vehicle device 100 causes the data storage device 300 to store the actual data R, which has a large capacity load, of the vehicle data each time the vehicle stops at the specific area 500, and the in-vehicle device 100 itself stores the transmitted actual data R. Can be deleted. Therefore, it is possible to reduce the load on the storage capacity of the in-vehicle apparatus 100 and prevent the omission of the accumulated amount of 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 as compared with the case where a mobile telephone network or the like is used.

  Moreover, in the data collection method according to the embodiment, when the vehicle-mounted device 100 receives the upload request for the vehicle data stored in the data storage device 300 from the data collection device 10 (step S15), the request is stored in the data storage device. Transfer to 300 (step S16). The 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 the request transfer (step S17). As described above, the in-vehicle device 100 always accepts the upload request from the data collecting device 10, so that the data collecting device 10 can always unify the request destinations, and the in-vehicle device 100 can make the vehicle on the side of the in-vehicle device 100. Data availability can be controlled. That is, the in-vehicle device 100 can manage data transmission / reception in the same manner as when the actual data R is uploaded 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 vehicle-mounted device 100 to the data storage device 300 is stored in the vehicle-mounted device 100. Further, the transmission history uploaded from the data storage device 300 to the data collection device 10 is preferably accumulated in the data storage device 300.

  From the viewpoint of the storage capacity of the data archiving apparatus 300, it is preferable that the actual data R uploaded from the data archiving apparatus 300 to the data collecting apparatus 10 be deleted after the transmission is completed. It may not necessarily be deleted depending on the availability of the.

  As described above, in the data collection method according to the embodiment, it is determined whether the vehicle V has stopped in the specific area having a predetermined communication environment, and as a result, it has been determined that the vehicle V has stopped in the specific area 500. In this case, the vehicle data stored in the vehicle-mounted device 100 is transferred to the data storage device 300 via the communication environment.

  Therefore, according to the data collection method of 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 (No. 1) and (No. 2) showing a configuration example of the data collection system 1 according to the embodiment. Note that FIGS. 2A and 2B show only the components necessary for explaining the features of the embodiment, and the description of general components is omitted.

  In other words, the components illustrated in FIGS. 2A and 2B are functionally conceptual, and do not necessarily have to be physically configured as illustrated. For example, the specific form of distribution / integration of each block is not limited to that shown in the figure, and all or part of the block may be functionally or physically distributed / arranged in arbitrary units according to various loads and usage conditions. It can be integrated and configured.

  Further, in the description using FIGS. 2A and 2B, the description of the components already 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 unit 11, a storage unit 12, and a control unit 13.

  The communication unit 11 is realized 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 vehicle-mounted device 100, the user terminal 200, and the data storage device 300 via the network N.

  The storage unit 12 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory (Flash Memory), or a storage device such as a hard disk or an optical disc. In the example of FIG. , And the collection data DB 12b.

  The collection condition information DB 12a stores the collection conditions specified by the user terminal 200 and accepted by the accepting unit 13a described later. That is, the collection condition information DB 12a includes past results regarding collection conditions.

  The collected data DB 12b stores collected data collected from each in-vehicle device 100 by the collecting unit 13c described later. That is, the collected data DB 12b includes past records of collected data. The collected data includes the tag data T and the 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 a RAM as a work area by, for example, a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). It is realized by being executed as. Further, the control unit 13 can be realized 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 the information processing functions and actions described below.

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

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

  The collection unit 13c collects the tag data T uploaded from the in-vehicle apparatus 100 and stores it in the collection data DB 12b. Further, the collection unit 13c transmits an upload request for the actual data R corresponding to the tag data T to the vehicle-mounted apparatus 100 based on the designation of the tag data T notified from the reception unit 13a.

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

  The providing unit 13d extracts the corresponding vehicle data from the collected data DB 12b based on the browsing request or the download request notified from the receiving unit 13a, and edits the UI data according to the above-described UI screen as necessary to make the user terminal. To 200.

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

  The communication unit 101 is realized by, for example, a NIC or the like. 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 the various sensors 150.

  The storage unit 102 is realized by, for example, a semiconductor memory device such as a RAM or a flash memory, and stores the collection condition information 102a, the vehicle data information 102b, and the 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. The vehicle data information 102b is information including vehicle data collected by the collecting unit 103c described later. The vehicle data includes the tag data T and the actual data R described above.

  The history information 102c is information including a transfer history of transferring the actual data R from the vehicle-mounted 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, a CPU, an MPU, or the like executing various programs stored in a storage device inside the vehicle-mounted apparatus 100 using a RAM as a work area. To be done. Further, the control unit 103 can be realized by, for example, an integrated circuit such as an ASIC or FPGA.

  The control unit 103 includes 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 realizes information processing functions and actions described below. Or run.

  The acquisition unit 103a acquires the collection condition distributed from the data collection device 10 and stores it 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 triggers in the collection condition.

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

  The collection unit 103c collects the 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 the trigger for collecting the vehicle data. Further, the collection unit 103c stops the collection of vehicle data when the detection unit 103b detects the occurrence of the trigger for stopping the collection of vehicle data.

  The upload unit 103d constantly uploads the tag data T to the data collection device 10. In addition, 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, the upload unit 103d notifies the transfer unit 103f of this request.

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

  When the determination unit 103e determines that the vehicle V has stopped in the specific area 500, the transfer unit 103f transmits the actual data R stored in the vehicle data information 102b to the data storage device 300 via the access point P. .. In addition, 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 upload unit 103d of an 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 the actual data is stored in the data storage device 300. R is transmitted to the data collection device 10.

  Further, the transfer unit 103f stores the transfer history of the transfer of the actual data R to the data archiving device 300 in the history information 102c. In addition, the transfer unit 103f causes the data archiving apparatus 300 to store a transmission history in which the data archiving apparatus 300 has transmitted the actual data R to the data collection apparatus 10.

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

  The communication unit 301 is realized by, for example, a NIC 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 vehicle-mounted 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 a flash memory, or a storage device such as a hard disk or an optical disk, and stores the accumulated data DB 302a and the history information 302b in the example of FIG. 2B.

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

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

  The control unit 303 includes 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 the information processing function and operation described below.

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

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

  When the actual data R stored in the accumulated data DB 302a needs to be processed, the processing unit 303c performs such processing and stores it in the accumulated data DB 302a. The processing includes, for example, a case where a user accesses the data storage device 300 from the vehicle-mounted device 100, a smartphone, or the like to browse the stored data in the accumulated data DB 302a, and performs analysis, tabulation, editing, and the like to facilitate the browsing. ..

  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 the actual data R to the data collection device 10. Further, the upload unit 303d accumulates the transmission history of transmitting the actual data R to the data collection device 10 in the history information 302b.

  When there is a request for browsing the stored data in the accumulated data DB 302a or the history information 302b via the vehicle-mounted device 100, the smartphone, or the like, the providing unit 303e extracts the corresponding data according to the request and displays the UI screen or the like. To the user via

  Next, a case where the communication environment in the specific area 500 is not good will be described with reference to FIG. FIG. 3 is a diagram showing a modified example when the communication environment of the specific area 500 is not good.

  As shown in FIG. 3, although the vehicle V has stopped in the specific area 500, the communication environment in the specific area 500 may not be good, such as “the radio field intensity is weak” at the access point P. If the determination unit 103e of the in-vehicle apparatus 100 can determine such a situation based on the output data of the various sensors 150, the transfer unit 103f notifies the data storage device 300 of the transfer schedule of the actual data R. Only do it.

  If the data storage device 300 leaves a history of such notification, at least the communication environment is not good and the real data R cannot be transferred, or the real data R is transferred as soon as the communication environment becomes good. It becomes possible for the user to understand what is to be done.

  Next, an example of the history information 102c of the in-vehicle apparatus 100 will be described with reference to FIG. FIG. 4 is a diagram showing an example of history information 102c of the in-vehicle apparatus 100.

  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 the identification information of the actual data R transferred from the vehicle-mounted device 100 to the data storage device 300. The “transfer date and time” item stores each transfer date and time. The “specific area” item stores identification information of the specific area 500. The “transfer destination” item stores the identification information of the data storage device 300 that is the transfer destination.

  Here, the user can arbitrarily select the data storage device 300 as the “transfer destination” from the vehicle-mounted device 100 or the like. FIG. 5 is a diagram illustrating an example of selecting a transfer destination. As shown in FIG. 5, for example, a UI screen of the vehicle-mounted device 100 or the like displays a list of identification information of the data storage device 300 to be the transfer destination by 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 home server, a smartphone, a cloud server, another vehicle X owned by the user, a general storage device, or the like. Further, such selection may be performed at the time of initial setting of the in-vehicle apparatus 100, before the start of the vehicle V, or before the vehicle is stopped in the specific area 500 and the transfer of the actual data R is started. Good.

  Returning to the explanation of FIG. The "attribute information" item stores, for example, contents that can be said to be the attribute information of the tag data T, for example, contents that are known to be data at the time of "abrupt braking" or "steep slope running".

  It is preferable that each item of the history information 102c is recorded as text data having a small data capacity. As a result, the history information 102c can prevent the storage capacity of the vehicle-mounted apparatus 100 from being overloaded.

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

  As shown in FIG. 6, a data processing instruction may be added to the upload request from the data collection device 10. At this time, if the actual data R corresponding to the in-vehicle apparatus 100 is still present and the processing corresponding to the processing instruction is impossible due to "resource shortage" or the like, the transfer unit 103f of the in-vehicle apparatus 100 determines that the actual data R At the same time, the processing instruction and the upload request may be transferred to the processing unit 303c of the data storage device 300 to perform the processing.

  As a result, even when 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 will be possible.

  If the vehicle-mounted device 100 can execute the processing, the actual data R processed by the vehicle-mounted device 100 may be transferred to the data storage device 300 together with the upload request. When the upload request and the processing instruction for the actual data R that have been transferred to the data storage device 300 are received, 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 described with reference to FIG. FIG. 7 is a diagram showing an example of the history information 302b of the data storage device 300.

  First, although not shown, the history information 302b includes items similar to the history information 102c of the vehicle-mounted apparatus 100, such as the date and time of the transmission history for each data ID. In addition to this, the history information 302b may include an item indicating the “state” for each data ID, as shown in FIG. 7, for example. Here, the case where the items including the “upload” state and the “delete” state are included is taken as an example.

  That is, as shown in FIG. 7, the data archiving apparatus 300 may delete the actual data R that has been uploaded to the data collecting apparatus 10 after uploading (see data ID “001” in the figure). Further, the data archiving device 300 may manage the real data R before uploading so that it cannot be deleted (see the data ID “003” in the figure).

  Further, the data archiving device 300 does not necessarily delete the actual data R uploaded to the data collecting device 10 after uploading, if the storage capacity has sufficient capacity (see data ID “002” in the figure). .. Further, it is possible to give a priority to the actual data R by designation from the data collection device 10 or the in-vehicle device 100, and the data archiving device 300 determines whether or not deletion is possible and the order according to the priority. You may do it.

  Next, a processing sequence executed by the data collection system 1 according to the embodiment will be described with reference to FIG. FIG. 8 is a diagram showing a processing sequence executed by the data collection system 1 according to the embodiment. The processing sequence shown in FIG. 8 is after the collection condition is distributed to the in-vehicle apparatus 100.

  First, the in-vehicle apparatus 100 collects the actual data R based on the distributed collection condition (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 the tag data T (step S103).

  While 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 in the specific area 500 (step S105), and deletes the actual data R after the transmission is completed (step S106). Further, the data storage device 300 stores the actual data R transmitted from the vehicle-mounted device 100 (step S107).

  While the steps S101 to S107 are repeated, the data collection device 10 transmits an upload request for the actual data R to the vehicle-mounted device 100 based on, for example, 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). Then, the data archiving apparatus 300 that has received the upload request extracts the actual data R corresponding to the request and transmits it to the data collecting apparatus 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 on the vehicle V, collects and accumulates the actual data R data (corresponding to an example of “data about the vehicle”), and the data collection device 10 (“ An in-vehicle device 100 that transmits actual data R to the data collection device 10 based on an upload request (corresponding to an example of “upper device”) (corresponding to an example of “transmission instruction”), and includes a determination unit 103e and a transfer unit. 103f. The determination unit 103e determines whether the vehicle V is located in the 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 transmits the accumulated actual data R via the communication environment to the data storage device 300 (corresponding to an example of “external device”). ) To.

  Therefore, according to the in-vehicle apparatus 100 according to the embodiment, it is possible to realize highly reliable data collection with a small communication load.

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

  Therefore, according to the in-vehicle device 100 according to the embodiment, the actual data R having a large capacity burden can be stored in the data storage device 300, 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 apparatus 100 and prevent the omission of the accumulated amount of vehicle data.

  In addition, when the transfer unit 103f receives an upload request for the actual data R transferred to the data archiving device 300 from the data collection device 10, the transfer unit 103f transfers the upload request to the data archiving device 300 and sends the upload request to the data archiving device 300. The data R is transmitted to the data collection device 10.

  Therefore, according to the in-vehicle device 100 according to the embodiment, the data collection device 10 can always unify the request destinations, and the in-vehicle device 100 can control the availability of vehicle data on the in-vehicle device 100 side. That is, the in-vehicle device 100 can manage data transmission / reception in the same manner as when the actual data R is uploaded to the data collection device 10.

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

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

  In addition, the transfer unit 103f causes the data archiving apparatus 300 to store a transmission history in which the data archiving apparatus 300 has transmitted the actual data R to the data collection apparatus 10.

  Therefore, according to the vehicle-mounted device 100 according to the embodiment, the data archiving device 300 can centrally manage which situation the actual data R was uploaded from the data archiving device 300 to the data collecting device 10.

  In addition, the transfer unit 103f adds the processing instruction of the actual data R to the upload request from the data collection apparatus 10 and, when the processing processing corresponding to the processing instruction in the in-vehicle apparatus 100 is impossible, the data storage apparatus 300. A processing instruction is transferred together with an upload request to the data storage device 300 to process the actual data R, and then the data storage device 300 is caused to transmit the actual data R to the data collection device 10.

  Therefore, according to the vehicle-mounted apparatus 100 according to the embodiment, even when the vehicle-mounted apparatus 100 cannot perform the processing, the actual data R processed according to the instruction from the data collection apparatus 10 is processed. It is possible to upload from the data storage device 300.

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

  For example, the data collection device 10 can request an immediate upload of the actual data R that is needed immediately from the vehicle-mounted device 100, and when the vehicle-mounted device 100 accepts such a request, it does not concern the specific area 500. The corresponding 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 apparatus 100 after the completion.

  Further, in the above-described embodiment, the data user is the developer of the autonomous driving technology, but it is an example of the user, and is, for example, a corporate user such as a service provider or a general individual user. Good.

  Further effects and modifications can be easily derived by those skilled in the art. As such, 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 defined by the appended claims and their equivalents.

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 vehicle-mounted 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 users Terminal 300 data storage device 302a accumulated data DB
302b History information 303a Reception part 303b Reception part 303c Processing part 303d Upload part 303e Providing part 500 Specific area R Actual data T Tag data V Vehicle

Claims (8)

An in-vehicle device that is mounted on a vehicle, collects and stores data about the vehicle, and transmits the collected data to the upper device based on a transmission instruction from the upper device,
A determination unit that determines whether the vehicle is located in a specific area having a predetermined communication environment,
And a transfer unit that transfers the accumulated data to an external device via the communication environment when the determination unit determines that the vehicle is located in the specific area. The transfer unit is
The in-vehicle device according to claim 1, wherein the accumulated data is transmitted to the external device and deleted after the transmission is completed. The transfer unit is
When the transmission instruction of the data transferred to the external device is received from the host device, the transmission instruction is transferred to the external device and the external device is caused to transmit the data to the host device. The in-vehicle device according to 1 or 2. The transfer unit is
The in-vehicle device according to claim 1, 2 or 3, wherein a transfer history of data transferred to the external device is accumulated in the in-vehicle device. The transfer unit is
The vehicle-mounted device according to any one of claims 1 to 4, wherein a transmission history of the external device transmitting data to the host device is accumulated in the external device. The transfer unit is
When the data processing instruction is added to the transmission instruction from the host device and the processing corresponding to the processing instruction in the in-vehicle device is impossible, the processing instruction is transmitted to the external device together with the transmission instruction, and the external device transmits the processing instruction. The vehicle-mounted device according to any one of claims 1 to 5, wherein the external device transmits the data to the higher-level device after the device processes the data. An in-vehicle device according to any one of claims 1 to 6,
The host device,
A data collection system comprising: the external device. A data collection method using an in-vehicle device, which is mounted on a vehicle, collects and stores data on a vehicle, and transmits collected data to the higher-level device based on a transmission instruction from the higher-level device,
A determination step of determining whether the vehicle is located in a specific area having a predetermined communication environment,
And a transfer step of transferring the accumulated data to an external device via the communication environment when it is determined by the determining step that the vehicle is located in the specific area.

Images