JP7220051B2 - Data collection device, data collection system and data collection method - Google Patents

Description

The disclosed embodiments relate to data collection devices, data collection systems and data collection methods.

2. Description of the Related Art Conventionally, a data collection device is known that collects road information from an in-vehicle device mounted on each vehicle. Such a data collection device collects road information for 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 terms of improving communication efficiency in collecting information about vehicles.

Specifically, in data communication, various data compression techniques are known for improving communication efficiency. One of them is differential compression, but in such differential compression, it is necessary to specify the data size of each of the base value to be transmitted for the first time and the difference value to be transmitted for the second and subsequent times.

However, in collecting information about a vehicle traveling under conditions in which various dynamic factors are intertwined, the combination of information collecting conditions is also diverse, and it is difficult to easily determine the above-mentioned data size that changes according to such collecting conditions. Therefore, it is difficult to improve the above communication efficiency.

One aspect of the embodiments has been made in view of the above, and an object thereof is to provide a data collection device, a data collection system, and a data collection method that can improve communication efficiency in collecting information about vehicles. .

A data collection device according to an aspect of an embodiment includes a control unit that collects vehicle-related data from an in-vehicle device mounted in each vehicle. Further, the control unit receives a designation operation from a user, sets collection conditions including conditions for compression of collected data, and estimates a data size related to compression based on collected past collected data. is calculated, and based on the calculated predicted value, a user interface is provided that guides the user on the data size .

According to one aspect of the embodiment, it is possible to improve communication efficiency in collecting information about vehicles.

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. 1H is a schematic explanatory diagram (No. 8) of the data collection method according to the embodiment; FIG. 2 is a block diagram showing a configuration example of the data collection system according to the embodiment. FIG. 3A is a diagram (Part 1) showing a specific example until guidance information regarding the data size of differential compression is displayed. FIG. 3B is a diagram (part 2) showing a specific example until guidance information regarding the data size of differential compression is displayed. FIG. 3C is a diagram (part 3) showing a specific example until guidance information regarding the data size of differential compression is displayed. FIG. 3D is a diagram (part 4) showing a specific example until guidance information regarding the data size of differential compression is displayed. FIG. 4 is a flowchart illustrating a processing procedure executed by the data collection system according to the embodiment;

Hereinafter, embodiments of a data collection 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 1H. 1A to 1H are schematic explanatory diagrams (part 1) to (part 8) of the data collection method according to the embodiment. 1A to 1H, 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. Various parameters include, for example, "target vehicle", "data type", "collection trigger condition", "collection period", and "presence/absence of differential compression".

The "target vehicle" is the identification information of the vehicle V to be collected. "Data type" is the type of data to be collected, in other words, the type of data collected from various sensors. Examples include accelerator opening, brake pressure, steering angle, SOH (States Of Health), etc. included in CAN (Controller Area Network) information, and images captured by a camera. The "collection trigger condition" is a condition that triggers collection, and is, for example, when the vehicle speed exceeds a predetermined speed.

"With or without differential compression" is an item for specifying whether or not to perform differential compression. For example, as shown in FIG. In this case, it is necessary to set the data size for each of the base value and differential value for differential compression.

As shown in FIG. 1D, the base value is data transmitted for the first time, for example, for different vehicle data in differential compression, and the difference value is data transmitted for the second and subsequent times. If differential compression is "yes", the data size that needs to be specified is the size of each data buffer in which these base values and differential values are stored.

Returning to the description of FIG. 1A. Then, as shown in FIG. 1A, each in-vehicle device 100 appropriately uploads vehicle data collected from each vehicle V to the data collection device 10 (step S3), and the data collection device 10 accumulates the data (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 actual data and tag data having characteristics as index data used for searching the actual data and grasping an overview of the actual data.

The tag data has a very small data capacity compared to the actual data. Therefore, each in-vehicle device 100 constantly uploads such tag data to the data collection device 10, for example. Then, for example, the data user can view the tag data through the user terminal 200 and cause the in-vehicle device 100 to upload only the actual data determined to be necessary to the data collection device 10 . This makes it possible to reduce the communication load. It is preferable that the tag data and the actual data that have been uploaded to the data collection device 10 are sequentially deleted from the in-vehicle device 100 .

In the following description, it is assumed that the vehicle data uploaded by the in-vehicle device 100 to the data collection device 10 is actual data.

By the way, if the data size in the above-described differential compression is inappropriate, if the circled data changes by an unexpected amount as shown in FIG. Defects occur. When such an event occurs, as shown in the right diagram of the same figure, it is necessary to supplement with the base value again, which increases the amount of data.

Therefore, in the data collection method according to the embodiment, when the vehicle data collection condition and differential compression are designated as "yes", for example, data collected in the past is collected under the designated collection condition. Based on this simulation, the predicted values of the data sizes of the base value and the difference value under the specified collection conditions were calculated.

Further, in the data collection method according to the embodiment, a UI screen is provided to guide the data size setting operation based on the calculated predicted value.

Specifically, it is assumed that there is a collection condition including a designation of collection at a cycle of 100 msec, and that this is applied to past collected data to execute a data collection simulation. Then, as shown in FIG. 1G, data strings (X ₀ , X ₁ , X ₂ , X ₃ , X ₄ , X ₅ , . . . X _n ) are obtained.

In the data collection method according to the embodiment, predicted values of the data size of each of the base value and the difference value under the specified collection conditions are calculated based on the simulation result. In the example of FIG. 1G, X _max , which is the maximum value of the data string, is calculated as the predicted value of the data size of the base value. Further, the maximum value of the difference string (X ₁ -X ₀ , X ₂ -X ₁ , X ₃ -X ₂ , ... X _n -X _n-1 ) of the data string is used as the predicted value of the data size of the difference value. calculate.

Then, in the data collection method according to the embodiment, as shown in FIG. 1H, guidance information including, for example, the calculated predicted value is displayed on the UI screen of the user terminal 200 to prompt the data user to set the data size. Guidance for operation. As shown in the figure, the predicted values are average values for all vehicles in the past collected data, or average values for a specific vehicle type such as "vehicle type A". good too.

This allows the data user to set the data size while checking the guidance information. Further, since such guidance information is based on past collected data, its accuracy can be guaranteed.

Note that the calculated predicted value may not only be simply presented, but may also be automatically entered in the data size input field. Such a specific example will be described later with reference to FIG. 3B.

As described above, in the data collection method according to the embodiment, when the vehicle data collection condition and differential compression are designated as "yes", for example, the designated collection condition is applied to collected data collected in the past. A simulation of data collection was performed, and based on this, predicted values for the data size of each of the base value and difference value under specified collection conditions were calculated. Also, based on the calculated predicted value, a UI screen is provided to guide the data size setting operation.

Therefore, according to the data collection method according to the embodiment, it is possible to appropriately support the data size setting operation in the differential compression of the data user. And thereby, the communication efficiency in information collection about the vehicle V can be improved. Hereinafter, a configuration example of the data collection system 1 according to the embodiment will be described more specifically.

FIG. 2 is a block diagram showing a configuration example of the data collection system 1 according to the embodiment. It should be noted that FIG. 2 shows only the constituent elements necessary for explaining the features of the embodiment, and omits the description of general constituent elements.

In other words, each component illustrated in FIG. 2 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 FIG. 2, the description of components that have already been described may be simplified or omitted.

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

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 and the user terminal 200 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 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 stores collection conditions specified by the user terminal 200 and set by the collection condition setting unit 13b, which will be described later. In addition, the collection condition information DB 12a includes records of collection conditions used for past data collection.

The collected data DB 12b stores collected data collected from each in-vehicle device 100 by a collection unit 13f, which will be described later. In addition, the collected data DB 12b includes records of collected data collected in past data collection.

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 UI provision unit 13a, a collection condition setting unit 13b, a calculation unit 13c, a guidance generation unit 13d, a distribution unit 13e, and a collection unit 13f, and has information processing functions described below. achieve or perform any action.

The UI providing unit 13 a generates various UI screens related to data collection in addition to the collection condition setting screen, and provides them to the user terminal 200 via the communication unit 11 . A specific example of the UI screen will be described later with reference to FIGS. 3A and 3B. The UI providing unit 13a also provides the UI screen with guidance information generated by the guidance generating unit 13d, which will be described later.

The guidance information includes a data size prediction value based on a simulation in which collection conditions specified by the data user from the user terminal 200 are applied to past collected data in the collected data DB 12b.

The collection condition setting unit 13b receives the collection condition and the presence/absence of differential compression specified by the data user from the user terminal 200 via the communication unit 11. is notified to the calculation unit 13c. Also, the collection condition setting unit 13b stores the collection conditions specified by the data user in the collection condition information DB 12a.

Further, when the collection condition setting unit 13b receives, for example, a changed collection condition from a data user who has been provided with guidance information, the collection condition setting unit 13b updates the corresponding collection condition in the collection condition information DB 12a.

The calculation unit 13c extracts the relevant collection condition accepted by the collection condition setting unit 13b from the collection condition information DB 12a, and executes a data collection simulation by applying this to past collected data in the collection data DB 12b. Further, the calculation unit 13c calculates the predicted value of the data size in differential compression based on the data string obtained as a result of the simulation. Further, the calculation unit 13c notifies the guidance generation unit 13d of the calculated predicted value.

The guidance generation unit 13d generates guidance information regarding the data size in differential compression based on the predicted value notified from the calculation unit 13c, and notifies the UI provision unit 13a of the guidance information. For example, the guidance generation unit 13d may generate an average value of the data size of past collected data for all vehicles, or the past collected data for a specific vehicle type, as shown in FIG. 1H. Generate guidance information so that the average value of the data size is displayed.

Here, a specific example from when the data user sets the collection conditions to when the guidance information regarding the data size of the differential compression is displayed will be described with reference to FIGS. 3A to 3D. 3A to 3D are diagrams (Part 1) to (Part 4) showing specific examples until guidance information regarding the data size of differential compression is displayed.

First, as shown in FIG. 3A, the UI providing unit 13a provides a "collection condition setting screen" to the user terminal 200 as a UI screen. The "collection condition setting screen" has items for specifying a plurality of collection conditions such as "upload condition", "collection condition #1", and so on.

In addition, "upload condition" and "collection condition #1" have a "trigger block" item that allows designation of a conditional expression that triggers the start or end of vehicle data upload or vehicle data collection.

In these items, the "parameter" and "symbol" of the conditional expression can be selected from a drop-down list of the GUI widget or the like. "Threshold" can be specified by direct input, for example, but may be specified by a drop-down list or the like, similar to "parameter" and "symbol".

As shown in the figure, such trigger blocks can be added by pressing the "+" button. When added, an input section for Boolean operators such as "and" and "or" is displayed, and logical conditions can be set (see M0 section in the figure). Therefore, it is possible to detect the occurrence of triggers under complex conditions.

Further, as shown in the same figure, on the "collection condition setting screen", it is possible to specify more detailed conditions for each collection data. For example, "normal" and "meta information" selectable by radio buttons of GUI widgets correspond to the aforementioned actual data and tag data. For the "data type", for example, the accelerator opening rate can be selected from a drop-down list or the like.

Then, as shown in the M1 part of the same figure, the presence or absence of differential compression can be specified with a radio button or the like. Here, if "Yes" is specified, for example, the data size input field shown in the M2 section of the figure becomes valid. For example, when the guidance information shown in FIG. 1H is displayed, the data user can directly input and designate the data size in the M2 section of FIG. 3A while referring to it.

The data size may be automatically input instead of having the data user directly input the data size. Such a case will be described with reference to FIG. 3B. As shown in FIG. 3B, it is assumed that differential compression is specified as "yes" in the M1 part of the figure.

In such a case, for example, the M3 section in the figure becomes effective. In the M3 section, a radio button or the like is used to simulate the calculation of the predicted value of the data size related to differential compression, whether all past data is targeted, or arbitrarily designated data among past collected data is targeted. can be specified.

Here, when "arbitrary designation" is designated, for example, the M4 part in the figure becomes valid. In the M4 part, optional detailed contents can be specified. For example, in "vehicle type", it is possible to designate a specific vehicle type such as "vehicle type A" or "vehicle type B". It should be noted that the vehicle type may be specified in combination.

Further, for example, in the "collection period (msec)", it is possible to specify a specific period such as "100" or "200". Such collection cycles correspond to so-called resolutions, and simulations with different collection cycles enable calculation of data size prediction values corresponding to different resolutions.

As an example, consider the case where "200" is specified. In this case, as a result of the simulation, data strings (X ₀ , X ₂ , X ₄ , X ₆ , X ₈ , X ₁₀ , . . . X _n ) are obtained.

In such a case, the calculator 13c calculates X _max , which is the maximum value of the data string, as a predicted value of the data size of the base value. Further, the maximum value of the difference string (X ₂ -X ₀ , X ₄ -X ₂ , X ₆ -X ₄ , ... X _n -X _n-2 ) of the data string is used as the predicted value of the data size of the difference value. calculate.

Similarly, considering the case where "500" is specified, as a result of the simulation, the data string (X ₀ , X ₅ , X ₁₀ , X ₁₅ , X ₂₀ , X ₂₅ , . . . X _n ) are obtained.

In such a case, the calculator 13c calculates X _max , which is the maximum value of the data string, as a predicted value of the data size of the base value. In addition, the maximum value of the differential sequence (X ₅ −X ₀ , X ₁₀ −X ₅ , _{X 15 −X 10 ,} . calculate.

By the way, the explanation so far is to predict the minimum data size that does not cause the difference value to overflow, so to speak, by simulation. It is more effective to perform a simulation that

Such an example will be described. In the case of data transmission by differential compression, as described above, "data size of base value>data size of differential value". Therefore, as the number of transmissions of the base value increases, the total transmission data volume increases.

Also, if the data size of the difference value is set smaller, the total amount of transmission data of the difference value can be reduced, but this also increases the possibility of the above-described overflow occurring. That is, since it is necessary to supplement with the base value when an overflow occurs (see FIG. 1F), the number of transmissions of the base value tends to increase.

Therefore, it is preferable to set the data sizes of the difference values in a well-balanced manner. Specifically, the data size of the difference value is set to such an extent that overflow does not occur so much, that is, to the extent that the increase in data transmission capacity due to the transmission of the base value due to overflow can be absorbed well by reducing the data size of the difference value. can be said to be preferable.

Therefore, it is preferable to provisionally set the data size of the difference value and actually simulate data transmission using past collected data in that state to calculate the total transmission data volume. That is, a simulation of converting past collected data into transmission data based on a temporary data size and provisionally transmitting the data is executed to predict the transmission data volume. Then, it is preferable to perform such a simulation a plurality of times using data sizes of several temporary difference values, and apply the data size that results in the smallest calculated transmission data volume to actual data transmission.

Specifically, when applied to the example shown in FIG. 3D, for example, the calculation unit 13c calculates the differential sequence (X ₅ −X ₀ , X ₁₀ −X ₅ , X ₁₅ −X ₁₀ , . . . X _n −X _n−5 ) is executed as the first simulation with a data size (M bits) that can set the maximum value. Further, the calculation unit 13c executes the second simulation with a data size smaller by 1 bit than this, and the (m-1)th simulation with a data size smaller by m bits.

After that, the calculation unit 13c calculates the data size when the total transmission data volume is the smallest among the results of the first to (m−1)th simulations as the optimum predicted value.

It should be noted that the number of simulations may be determined as a predetermined number of times with a target of about half the number of bits of the data size containing the maximum set value (maximum value of difference) of the simulation. Alternatively, for example, it may be determined based on the distribution of the differential sequence (X ₅ -X ₀ , X ₁₀ -X ₅ , X ₁₅ -X ₁₀ , . . . X _n -X _n-5 ). In this case, as an example, a determination method may be considered in which the simulation is performed up to the data size containing the difference value corresponding to the upper 3/4 from the largest difference.

Returning to the description of FIG. 3B. In the M4 section of the figure, it is also possible to designate, for example, "driving characteristics". Here, for example, if "rough" is specified, the past collected data from which the driving characteristic of "rough" is estimated becomes the target of the simulation. Also, for example, when "gentle" is specified, past collected data from which a moderate driving characteristic is estimated is subjected to the simulation. Note that these may be specified in combination.

Such driving characteristics can be determined from indicators such as whether or not the accelerator opening, brake pressure, and steering angle change abruptly.

Past collection data to be simulated is narrowed down based on the designations in the M3 and M4 sections. Then, for example, by pressing the "automatic input" button M5, a simulation of data collection is executed with the collection conditions specified in the "collection condition setting screen" of FIG. 3A applied to the collected data that has been narrowed down. be.

As a result, the predicted value calculated by the calculating unit 13c is automatically entered in the data size input field of the M2 unit. The data user may use the automatically input predicted value as the set value as it is, or may modify the predicted value as the set value. The set value is determined by pressing a "determine" button (not shown), for example, in FIG. 3A.

Here, an example is given in which the predicted value calculated by the calculation unit 13c is automatically entered in the data size input field of the M2 copy by pressing the “automatic input” button M5. 13c may be automatically input to the M2 section as it is, without using the "automatic input" button M5 or the like.

Alternatively, the collection condition setting unit 13b may automatically set the predicted value calculated by the calculation unit 13c in the collection condition information DB 12a and automatically distribute it.

Returning to the description of FIG. 2, the distribution unit 13e will be described. The distribution unit 13e distributes the determined 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 collection unit 13f collects the vehicle data uploaded from the in-vehicle device 100 via the communication unit 11 and accumulates them in the collected data DB 12b.

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.

Like the communication unit 11, the 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, like the storage unit 12, 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. Data information 102b is stored.

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.

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 includes an acquisition unit 103a, a detection unit 103b, a collection unit 103c, and an upload unit 103d, and implements or executes information processing functions and actions described below.

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. Further, for example, the detection unit 103b causes the upload unit 103d to upload the vehicle data when detecting the occurrence of an event that serves as a trigger for uploading the vehicle data to the data collection device 10 under the collection conditions.

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 vehicle data stored in the vehicle data information 102b to the data collection device 10 when the detection unit 103b detects the occurrence of a trigger for uploading the vehicle data.

Next, a processing procedure executed by the data collection system 1 according to the embodiment will be described using FIG. FIG. 5 is a flow chart showing a processing procedure executed by the data collection system 1 according to the embodiment.

First, the data user designates collection conditions from the user terminal 200 (step S101). Then, if there is a specification regarding differential compression (step S102, Yes), the calculation unit 13c of the data collection device 10 executes a simulation applying the specified collection condition to past collected data (step S103).

Then, the calculation unit 13c calculates a data size prediction value related to differential compression based on the simulation result (step S104). Then, the guidance generating unit 13d generates guidance information based on the predicted value, and the UI providing unit 13a provides guidance or automatically inputs the data size based on the guidance information (step S105).

Moreover, when there is no specification regarding differential compression in step S102 (step S102, No), it transfers to step S106.

Then, it is determined whether or not the collection conditions have been determined (step S106). When the collection conditions are determined (step S106, Yes), the distribution unit 13e distributes the collection conditions to each in-vehicle device 100 (step S107). Then, the collection unit 13f collects vehicle data based on the distributed collection conditions (step S108).

If the collection conditions have not been determined (step S106, No), the process from step S101 is repeated.

In addition, although the case where the compression method is differential compression was mentioned as an example in the above-described embodiment, the compression method is not limited. Therefore, this embodiment can also be applied to the case of designating the data size related to compression methods other than differential compression.

As described above, the data collection device 10 according to the embodiment includes the collection unit 13f, the collection condition setting unit 13b, and the calculation unit 13c. The collection unit 13f collects data about the vehicle V from the in-vehicle device 100 mounted on each vehicle V. FIG. The collection condition setting unit 13b sets conditions for compression of collected data. The calculation unit 13c calculates a data size prediction value related to the compression based on past collected data collected by the collection unit 13f.

Therefore, according to the data collection device 10 according to the embodiment, communication efficiency in collecting information about the vehicle V can be improved.

In addition, the collection condition setting unit 13b receives a designation operation from a data user (equivalent to an example of a “user”) and sets a collection condition. A providing unit 13a (corresponding to an example of a “providing unit”) is further provided. The UI providing unit 13a provides a UI for guiding the data size to the data user based on the predicted value calculated by the calculating unit 13c.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to improve the operability of specifying the data size.

Also, the collection condition setting unit 13b sets the data size related to compression based on the predicted value calculated by the calculation unit 13c.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to automatically set the predicted value calculated by the calculation unit 13c and then automatically distribute it to the in-vehicle device 100 .

Further, the calculation unit 13c executes a data collection simulation applying the collection conditions set by the collection condition setting unit 13b to past collected data, and calculates a predicted value based on the data obtained as a result of the simulation. do.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to calculate a highly accurate predicted value based on past data collection results.

The calculation unit 13c also performs a simulation of converting past collected data into transmission data based on a temporary data size and temporarily transmitting the transmission data, and predicts the transmission data volume.

Therefore, according to the data collection device 10 according to the embodiment, by predicting not only the data size of the difference value but also the transmission data volume itself, it is possible to improve the accuracy of improving the communication efficiency.

Further, the calculation unit 13c executes a plurality of simulations using a plurality of temporary data sizes.

Therefore, according to the data collection device 10 according to the embodiment, the data size of the difference value is set to the extent that overflow does not occur, that is, the increase in the data transmission capacity due to the transmission of the base value due to the overflow is reduced to the data size of the difference value. It can contribute to well-balanced setting to the extent that it can be well absorbed by reduction.

Further, the calculation unit 13c uses, among the execution results of a plurality of simulations, the temporary data size when the transmission data volume is the smallest as the optimum predicted value.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to optimize the predicted value based on the execution results of a plurality of simulations.

In addition, the UI providing unit 13a provides a UI that can specify parameters for extracting past collected data used for simulation.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to designate a more appropriate data size according to the parameter.

Further, the UI providing unit 13a provides a UI capable of designating at least the model of the vehicle V, the resolution of the data, and the driving characteristics of the vehicle V as parameters.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to designate a more appropriate data size according to at least the vehicle type of the vehicle V, the resolution of the data, and the driving characteristics of the vehicle V. FIG.

Also, the compression is differential compression.

Therefore, according to the data collection device 10 according to the embodiment, it is possible to appropriately set the data size of the base value and the difference value when the differential compression is used as the compression method, thereby improving the communication efficiency in collecting information about the vehicle V. can be done.

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 UI providing unit 13b Collection condition setting unit 13c Calculation unit 13d Guidance generation unit 13e Distribution unit 13f Collection unit 100 In-vehicle device 102a Collection condition information 102b Vehicle data information 103a Acquisition unit 103b Detection unit 103c Collection unit 103d Upload unit 150 Various sensors 200 Use Terminal V Vehicle

Claims (12)

Equipped with a control unit that collects data about the vehicle from the in-vehicle device installed in each vehicle,
The control unit
receive a specified operation from the user and set collection conditions including conditions for compression of collected data;
Calculate a predicted value of the data size related to the compression based on the collected past collected data ,
providing a user interface that guides the user on the data size based on the calculated predicted value;
data collection device. Equipped with a control unit that collects data about the vehicle from the in-vehicle device installed in each vehicle,
The control unit
calculating an estimated data size related to compression of the collected data based on the collected past collected data;
Setting conditions for compression of collected data automatically based on the calculated predicted value or by user's designated operation based on the predicted value;
data collection device. The control unit
Receives the specified operation from the user and sets the collection conditions,
providing a user interface that guides the user on the data size based on the calculated predicted value ;
3. A data collection device according to claim 2 . The control unit
setting a data size for the compression specified by a user provided with the user interface ;
4. A data collection device according to claim 3 . The control unit
Performing a data collection simulation applying the set collection conditions to past collected data , and calculating the predicted value based on the data obtained as a result of the simulation ;
5. A data collection device according to claim 3 or 4 . The control unit
Perform a simulation of converting past collected data into transmission data according to a temporary data size and provisionally transmitting it, and predict the transmission data volume .
A data collection device according to claim 3 , 4 or 5 . The control unit
running multiple simulations with multiple hypothetical data sizes ,
7. A data collection device according to claim 6 . Equipped with an in-vehicle device mounted on each vehicle and a data collection device,
The data collection device is
collecting data about the vehicle from the in-vehicle device;
receive a specified operation from the user and set collection conditions including conditions for compression of collected data;
Calculate a predicted value of the data size related to the compression based on the collected past collected data,
providing a user interface that guides the user on the data size based on the calculated predicted value;
data collection system. Equipped with an in-vehicle device mounted on each vehicle and a data collection device,
The data collection device is
collecting data about the vehicle from the in-vehicle device;
calculating an estimated data size related to compression of the collected data based on the collected past collected data;
Setting conditions for compression of collected data automatically based on the calculated predicted value or by user's designated operation based on the predicted value;
data collection system. A data collection method performed by a data collection device,
Collecting data about the vehicle from an onboard device installed in each vehicle;
setting collection conditions including conditions for compression of collected data in response to a specified operation from a user ;
Calculating an estimated value of the data size related to the compression based on collected past collected data ;
providing a user interface that guides a user on the data size based on the calculated predicted value;
data collection methods , including; A data collection method performed by a data collection device,
Collecting data about the vehicle from an onboard device installed in each vehicle;
Calculating a data size prediction value for compression of collected data based on collected past collected data;
Setting conditions for compression of collected data automatically based on the calculated predicted value or by user's designated operation based on the predicted value;
data collection methods, including; Making the settings includes:
Receives the specified operation from the user and sets the collection conditions,
providing a user interface that guides a user on the data size based on the calculated predicted value;
12. The data collection method of claim 11, further comprising:

Images