JP2020166725A - On-vehicle device, log collection system, and log collection method - Google Patents

Abstract

To delete unnecessary logs while holding information density.SOLUTION: An on-vehicle device according to an embodiment is an on-vehicle device mounted on a vehicle to capture and accumulate logs concerning the vehicle, and in a case where a network connection with a host device is established, transmit the accumulated logs to the host device, and the on-vehicle device includes an acquisition unit, a correction unit, and a log deletion unit. The acquisition unit acquires a vehicle status. The correction unit corrects a holding priority of a data item previously set for each data item of the logs in accordance with the vehicle status acquired by the acquisition unit. The log deletion unit deletes logs in order from the lowest holding priority based on the holding priority corrected by the correction unit.SELECTED DRAWING: Figure 2B

Description

Disclosure embodiments relate to in-vehicle devices, log collection systems and log collection methods.

Conventionally, a log collection system that collects logs related to vehicle running from an in-vehicle device mounted on each vehicle is known (see, for example, Patent Document 1).

Such a log collection system has a function of uploading the logs collected and accumulated in the in-vehicle device to the center server via a network such as the Internet. Further, in recent years, in such a log collection system, an in-vehicle device capable of uploading to a center server by using a tethering function possessed by a mobile information terminal such as a smartphone carried by a user has been proposed.

Japanese Unexamined Patent Publication No. 2012-221031

However, the above-mentioned prior art has room for further improvement in deleting unnecessary logs while maintaining the information density.

Specifically, when using the above-mentioned tethering function, the in-vehicle device is not always connected to the center server via the network, so the collected travel logs are accumulated until the next network connection is established and uploading becomes possible. You need to keep doing it.

However, since in-vehicle devices generally have a limited storage capacity, measures may be taken such as deleting old logs and continuing to secure storage capacity for newly collected logs.

However, if these measures are taken, even if the network connection is established and the log is uploaded to the center server next time, the log is missing, and even if the center server analyzes the information based on the log. Useful analysis results may not be obtained.

One aspect of the embodiment is made in view of the above, and an object of the present invention is to provide an in-vehicle device, a log collection system, and a log collection method capable of deleting unnecessary logs while maintaining information density. To do.

The in-vehicle device according to one aspect of the embodiment is mounted on a vehicle, collects and accumulates a log related to the vehicle, and transmits the accumulated log to the higher-level device when a network connection with the higher-level device is established. It is an in-vehicle device that includes an acquisition unit, a correction unit, and a log deletion unit. The acquisition unit acquires the vehicle status of the vehicle. The correction unit corrects the retention priority of the data item set in advance for each data item of the log according to the vehicle condition acquired by the acquisition unit. The log deletion unit deletes the log from the one with the lowest retention priority based on the retention priority corrected by the correction unit.

According to one aspect of the embodiment, unnecessary logs can be deleted while maintaining the information density.

FIG. 1 is a schematic explanatory diagram of a log collection method according to an embodiment. FIG. 2A is a block diagram showing a configuration example of the log collecting device according to the embodiment. FIG. 2B is a block diagram showing a configuration example of the in-vehicle device according to the embodiment. FIG. 3A is a diagram (No. 1) showing a specific example of the retention priority setting information according to the embodiment. FIG. 3B is a diagram (No. 2) showing a specific example of the retention priority setting information according to the embodiment. FIG. 3C is a diagram (No. 3) showing a specific example of the retention priority setting information according to the embodiment. FIG. 3D is a diagram (No. 4) showing a specific example of the retention priority setting information according to the embodiment. FIG. 3E is a diagram (No. 5) showing a specific example of the retention priority setting information according to the embodiment. FIG. 4A is a diagram (No. 1) showing an example of data items for each log type. FIG. 4B is a diagram (No. 2) showing an example of data items for each log type. FIG. 4C is a diagram (No. 3) showing an example of data items for each log type. FIG. 4D is a diagram (No. 4) showing an example of data items for each log type. FIG. 4E is a diagram (No. 5) showing an example of data items for each log type. FIG. 4F is a diagram (No. 6) showing an example of data items for each log type. FIG. 4G is a diagram (No. 7) showing an example of data items for each log type. FIG. 4H is a diagram (No. 8) showing an example of data items for each log type. FIG. 4I is a diagram (No. 9) showing an example of data items for each log type. FIG. 4J is a diagram (No. 10) showing an example of data items for each log type. FIG. 5 is a flowchart showing a processing procedure executed by the in-vehicle device according to the embodiment.

Hereinafter, embodiments of the in-vehicle device, the log collection system, and the log 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 shown below.

First, an outline of the log collection method according to the embodiment will be described with reference to FIG. FIG. 1 is a schematic explanatory diagram of a log collection method according to an embodiment. In FIG. 1, a log collection system 1 to which the log collection method according to the embodiment is applied will be described as an example.

As shown in FIG. 1, the log collecting system 1 according to the embodiment includes a log collecting device 10 and in-vehicle devices 100-1, 100-2 mounted on vehicles V-1, V-2, V-3, respectively. , 100-3 ..., Smartphones (hereinafter referred to as "smartphones") SP-1, SP-2, SP-3 ... Carried by users of each vehicle, and center terminal 200. In the following, "vehicle V" is used to refer to the vehicle in general, "smartphone SP" is used to refer to the smartphone in general, and "vehicle device 100" is used to refer to the in-vehicle device in general. Describe each.

The log collecting device 10 is a host device for transmitting logs from the vehicle-mounted device 100 via the network N. The log collecting device 10 is configured as a cloud server that provides cloud services via a network N such as the Internet or a mobile phone network, collects traveling logs from each in-vehicle device 100, and provides them to log users on the center side. To do. In the following description, the log collecting device 10 will be described as an example of a higher-level device, but the present invention is not limited to this. The host device may be a device that performs a predetermined operation triggered by transmission of a log from the in-vehicle device 100. The predetermined operation is, for example, an operation of linking with another cloud service such as giving points or posting to an SNS (Social Networking Service).

The log user on the center side analyzes information based on the log collected by the log collecting device 10, and based on the result, for example, the behavior analysis of the vehicle V, the usage status analysis of the in-vehicle device 100, and the driving tendency of the user. It is an engineer who performs analysis, running analysis of vehicle V at accident-prone points, and the like. The log collecting device 10 provides the log user with a user interface (hereinafter, referred to as “UI”) screen that can be accessed via the center terminal 200.

The center terminal 200 is a terminal used by log users on the center side, and is, for example, a notebook PC (Personal Computer), a desktop PC, a tablet terminal, a PDA (Personal Digital Assistant), a smartphone, a glasses type, or a clock type. It is a wearable device that is an information processing terminal.

On the other hand, the in-vehicle device 100 is configured as a drive recorder having, for example, a camera, various sensors such as an acceleration sensor and a GPS (Global Positioning System) sensor, a storage device, a microcomputer, and a car navigation device, and logs related to the running of the vehicle V. Is collected from the vehicle V.

Further, the in-vehicle device 100 uploads the collected log to the log collecting device 10 when the network connection with the log collecting device 10 is established.

The smartphone SP is an example of a mobile information terminal carried by the user of each vehicle V, and has a tethering function. The in-vehicle device 100 can use the tethering function to establish a network connection with the log collecting device 10 via the smartphone SP and upload logs.

However, when such a tethering function is used, the in-vehicle device 100 is not always connected to the log collecting device 10 via a network, and therefore, the collected logs are continuously accumulated until the next network connection is established and uploading becomes possible. There is a need.

However, since the in-vehicle device 100 has a limited storage capacity, it is necessary to continue to secure the storage capacity for newly collected logs by, for example, deleting old logs, but on the other hand, on the center side. It is necessary to maintain the information density required for the analysis when analyzing the information.

Therefore, in the log collection method according to the embodiment, the in-vehicle device 100 acquires the vehicle status and corrects the retention priority of the data item set in advance for each data item of the log according to the acquired vehicle status. , Based on the corrected retention priority, it was decided to delete the log from the one with the lowest retention priority.

Specifically, in the log collection method according to the embodiment, for example, a log user first sets a retention priority for each log data item as shown in FIG. 1 via the above-mentioned UI screen (step S1). ). The retention priority is a priority for retaining the log without deleting it. For example, the larger the value, the higher the degree to be retained, in other words, the higher the utility value.

The log collecting device 10 that has received the retention priority for each data item of the log distributes the retention priority setting information to each vehicle V in, for example, a file format (step S2).

The setting information includes, for example, a common table for setting the retention priority for each log data item, a driving tendency table for correcting (adding / deducting points) each retention priority according to the driving characteristics of the user, a driving area, and the driving area. It includes an operating environment table for correcting each holding priority according to a time zone and the like, an attribute table for correcting each holding priority according to the attributes (model, delivery destination, etc.) of the in-vehicle device 100, and the like. Specific examples of each of these tables will be described later with reference to FIGS. 3A to 3E.

Further, in the setting information, a condition or the like that serves as a trigger indicating a situation in which the log needs to be deleted is set. Such a trigger is, for example, information such as when the free area of the storage capacity of the in-vehicle device 100 becomes [XXX] MB or less. Further, in the setting information, for example, the log collection timing for each log type is set. Specific examples of such setting information will be shown later in FIGS. 4A to 4J.

Then, each in-vehicle device 100 collects a log in each vehicle V based on the above-mentioned log collection timing and the like (step S3), and accumulates the log. On the other hand, each in-vehicle device 100 corrects the holding priority according to the vehicle condition (step S4). The vehicle status includes the vehicle V, the in-vehicle device 100, static information for each user, and dynamic information that changes from moment to moment.

By correcting the retention priority according to such vehicle conditions, it is possible to maintain the information density enough to obtain useful analysis results by information analysis on the center side even if the log is missing due to deletion. can do.

Then, each in-vehicle device 100 deletes the log based on the corrected retention priority when a situation requiring deletion of the log occurs (step S5). Note that steps S4 and S5 are appropriately repeated while logs are collected and accumulated.

Then, for example, when a network connection with the log collecting device 10 is established via the smartphone SP, each in-vehicle device 100 uploads a log to the log collecting device 10 (step S6), and the log collecting device 10 uploads the log. Collect and accumulate (step S7). Then, the log user on the center side acquires the log accumulated in the log collecting device 10 via, for example, the above-mentioned UI screen, and uses it for information analysis or the like (step S8).

As described above, in the log collecting method according to the embodiment, the in-vehicle device 100 acquires the vehicle status, and according to the acquired vehicle status, the retention priority of the data item set in advance for each data item of the log is set. It was decided to correct and delete the log from the one with the lowest retention priority based on the corrected retention priority.

Therefore, according to the log collection method according to the embodiment, unnecessary logs can be deleted while maintaining the information density. Hereinafter, a configuration example of the log collection system 1 according to the embodiment will be described more specifically.

FIG. 2A is a block diagram showing a configuration example of the log collecting device 10 according to the embodiment. Further, FIG. 2B is a block diagram showing a configuration example of the in-vehicle device 100 according to the embodiment. Note that, in FIGS. 2A and 2B, only the components necessary for explaining the features of the embodiment are shown, and the description of general components is omitted.

In other words, each component shown in FIGS. 2A and 2B is a functional concept and does not necessarily have to be physically configured as shown. For example, the specific form of distribution / integration of each block is not limited to the one shown in the figure, and all or part of it may be functionally or physically distributed 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 described above, as shown in FIG. 2A, the log collection system 1 according to the embodiment includes a log collection device 10, an in-vehicle device 100, a smartphone SP, and a center terminal 200.

First, the log collecting device 10 will be described. The log collecting 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 / receives information to / from the in-vehicle device 100 and the center terminal 200 via the network N.

The storage unit 12 is realized by, for example, a semiconductor memory element 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 disk. In the example of FIG. 2A, the retention priority setting information 12a and the collection log DB12b are stored.

The retention priority setting information 12a is information including the retention priority for each data item of the log, which is designated by the center terminal 200 and set by the setting unit 13a described later. Here, a specific example of the retention priority setting information 12a will be described with reference to FIGS. 3A to 3E. 3A to 3E are diagrams (No. 1) to (No. 5) showing specific examples of the retention priority setting information 12a according to the embodiment.

As shown in FIG. 3A, the retention priority setting information 12a includes a "common table", a "driving tendency table", an "operating environment table", and an "attribute table".

In each of these tables, as shown in FIG. 3B, a "retention priority" is set for each "item" of the log. Here, it is assumed that "10" is set in the item A, "5" is set in the item B, and "3" is set in the item C.

Then, when a situation requiring deletion of the log occurs, as shown in the figure, the items with the lowest priority are basically deleted. Therefore, in the case of the example in the figure, it will be deleted from item C.

Here, the "common table" is, for example, a table in which the retention priority common to all the in-vehicle devices 100 is defined in advance in the log collection device 10. In the common table, for example, in the log, among the driving data related to the running of the vehicle V and the operation data related to the user's operation, the retention priority of the data items that are basically considered to have high utility value is set high. There is.

Further, the "driving tendency table" is a table in which the retention priority of a specific data item according to the driving tendency diagnosis result of the user is set among the data items defined in the common table. The driving tendency diagnosis is performed by, for example, the correction unit 103b of the in-vehicle device 100 described later, and the result is compared with the driving tendency table to extract the correction amount of the corresponding item. Then, the correction unit 103b corrects the holding priority of the driving tendency table.

For example, it is assumed that the driving tendency of the user is diagnosed as dangerous driving degree a as a result of the driving tendency diagnosis. In such a case, the correction unit 103b illuminates the result with the driving tendency table, and extracts the correction amount of each of the items A, B, C ... that match the dangerous driving degree a as shown in FIG. 3C.

Then, the correction unit 103b corrects each preset holding priority according to the extracted correction amount (see the portion surrounded by the closed curve of the broken line in the figure). Here, the correction unit 103b of the in-vehicle device 100 performs the driving tendency diagnosis, but for example, the log collecting device 10 may perform the diagnosis.

Further, the "operating environment table" is a table in which the retention priority of a specific data item according to the operating environment is set among the data items defined in the common table. In the driving environment table, as shown in FIG. 3D, the retention priority for each data item is set on the condition of a specific area, a specific time, or both, such as a point p and a time zone q.

The specific area referred to here is, for example, a place where driving is likely to be disturbed (a point where many driving disturbances occur from the driving tendency diagnosis of all users or a specific user, a point where many accidents occur, a point where traffic congestion occurs frequently, etc.) and analysis. Refers to places where you want to strengthen (such as designated areas on the ground such as municipalities or between rivers, administrative areas of local governments, specific population density areas, specific traffic volume areas, etc.).

In addition, the specific time referred to here refers to, for example, a time zone for commuting to work or school, a time zone in which accidents occur frequently, and the like. In addition, both are the combination of accident-prone points and accident-prone time zones, the combination of specific population density areas and time zones, the combination of specific traffic volume areas and time zones and days of the week, and the center side. It refers to a combination of areas and time zones where the data collection status is not good.

As for the driving environment table, as in the case of the driving tendency table shown in FIG. 3C, the retention priority of the corresponding data item is given according to the driving environment in which the moving vehicle V is actually placed, that is, the vehicle condition. The degree will be corrected as appropriate.

Further, the "attribute table" is a table in which the retention priority of a specific data item according to the attribute of the in-vehicle device 100 is set among the data items defined in the common table. As shown in FIG. 3E, the attribute table is a log for each model of the in-vehicle device 100 such as model x, delivery destination y, and product serial # z, for each delivery destination (for example, a specific car rental company), and for each product serial number. The retention priority is set for each data item according to the content you want to analyze or when you want to strengthen the collection of.

In such an attribute table as well, as in the case of the driving tendency table shown in FIG. 3C, the retention priority of the corresponding data item is appropriately corrected according to the attribute actually corresponding to the in-vehicle device 100, that is, the vehicle condition. It will be.

Here, for reference, in the retention priority setting information 12a, the log collection timing set for each log type such as in-vehicle device identification information, in-vehicle device attachment information, and driving information, and other information in a predetermined vehicle condition. FIGS. 4A to 4J show an example of each item which has a higher retention priority than the data item and is likely to be set (it is likely to be regarded as having high utility value).

4A to 4J are diagrams (No. 1) to (No. 10) showing an example of data items for each log type. In FIGS. 4A to 4J, the data items in which the retention priority is set higher than the others in each table are marked with a circle.

To give an easy-to-understand example, in the traveling information of FIG. 4D, for example, each item marked with a circle in the common table is likely to be set with a higher retention priority than other data items. In addition, the same items in the driving tendency table and the driving environment table are also likely to be corrected so as to have a higher holding priority accordingly. On the other hand, the attribute table tends to be set with a relatively low retention priority for travel information. Therefore, when deleting the log, the travel information is likely to be deleted from the data items of the attribute table.

Further, as shown by the item "rapid acceleration / deceleration flag" in the figure, for example, when a sudden acceleration / deceleration operation is observed in the driving operation of the user, the holding priority of the angular velocity and the acceleration of the driving tendency table is corresponding to the sudden acceleration / deceleration operation. Is easy to set high. In this way, the retention priority of each item for each log type is appropriately corrected according to the predetermined vehicle condition.

Returning to the description of FIG. 2A. The collection log DB 12b is a database in which logs collected from each in-vehicle device 100 by the collection unit 13c described later are stored.

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

The control unit 13 has a setting unit 13a, a distribution unit 13b, a collection unit 13c, and an analysis unit 13d, and realizes or executes an information processing function or operation described below.

The setting unit 13a receives various settings related to deletion of the log specified from the center terminal 200 by the log user via the communication unit 11 and sets them in the retention priority setting information 12a.

The distribution unit 13b distributes the holding priority setting information 12a to the vehicle V to be distributed via the communication unit 11.

The collection unit 13c collects the logs uploaded from the in-vehicle device 100 for which the network connection has been established, and stores them in the collection log DB 12b.

The analysis unit 13d executes an analysis process related to the log designated from the center terminal 200 by the log user, and returns the analysis result to the center terminal 200 via the communication unit 11. Further, the analysis unit 13d can also cause the setting unit 13a to automatically set the retention priority setting information 12a that reflects the collection result in the collection log DB 12b and the analysis result based on the collection result.

Next, the in-vehicle device 100 will be described. As shown in FIG. 2B, the in-vehicle device 100 includes a communication unit 101, a storage unit 102, and a control unit 103. Further, 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.

The communication unit 101 communicates between the network N and various sensors 150 and the in-vehicle device 100. The communication unit 101 realizes communication with the network N by a wireless communication interface. For the wireless communication interface, for example, WiFi (Wireless Fidelity) or Bluetooth (registered trademark) may be used. The wireless communication interface is wirelessly connected to the network N by using, for example, the tethering function of the smartphone SP. The communication unit 101 transmits / receives information to / from the log collection device 10 via the network N.

In addition, the communication unit 101 communicates with various sensors 150. The communication unit 101 realizes communication with various sensors 150 by a CAN (Controller Area Network) bus. The communication unit 101 receives the output data of the various sensors 150. Communication with the various sensors 150 may be performed by another protocol of CAN. It may also be performed wirelessly.

The storage unit 102 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, and in the example of FIG. 2B, the storage priority setting information 102a downloaded from the log collection device 10 is stored. In addition, the storage unit 102 stores the accumulation log 102b. In the accumulation log 102b, the log collected by the log collection unit 103d, which will be described later, is accumulated.

The control unit 103 is a controller like the control unit 13, and is realized by, for example, executing various programs stored in the storage device inside the in-vehicle device 100 by the CPU, MPU, or the like using the RAM as a work area. Will 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 a download unit 103a, a correction unit 103b, an acquisition unit 103c, a log collection unit 103d, a log deletion unit 103e, and an upload unit 103f, and has information processing functions and operations described below. To realize or execute.

The download unit 103a acquires the retention priority setting information 102a distributed from the log collection device 10 and stores it in the storage unit 102.

The retention priority setting information 102a is version-controlled on the log collection device 10 side, for example, and when a network connection is established, the version of the retention priority setting information 102a is matched between the log collection device 10 and the in-vehicle device 100. Will be. Therefore, if it is confirmed that the retention priority setting information 102a has already been downloaded, the download unit 103a does not download the retention priority setting information 102a.

The correction unit 103b derives a correction amount of the holding priority of each item of the holding priority setting information 102a according to the vehicle condition acquired by the acquisition unit 103c described later, and sets the holding priority based on the correction amount. Correct as appropriate.

The acquisition unit 103c receives output data from various sensors 150, and based on this, acquires a dynamic vehicle condition that changes from moment to moment. In addition, the acquisition unit 103c acquires a dynamic vehicle status based on static information held by the in-vehicle device 100 and the like.

For example, when the acquired vehicle status is the log collection timing of a predetermined log type, the acquisition unit 103c causes the log collection unit 103d to collect the log of the corresponding log type. Further, for example, when the acquired vehicle status indicates a situation in which the log needs to be deleted, the acquisition unit 103c deletes the log from the one having the lowest retention priority in the log deletion unit 103e based on the retention priority setting information 102a. Let me.

When the acquisition unit 103c detects the collection timing of a log of a predetermined log type, the log collection unit 103d collects the corresponding log based on the output data of various sensors 150 and stores it in the storage log 102b. The log collection unit 103d can stop the log collection when the acquisition unit 103c detects the occurrence of a trigger to stop the log collection.

When the acquisition unit 103c acquires the vehicle status requiring the deletion of the log, the log deletion unit 103e deletes the log from the one with the lowest retention priority based on the retention priority setting information 102a, and thins out the accumulated log 102b. To do.

When the network connection between the in-vehicle device 100 and the log collection device 10 is established, the upload unit 103f transmits the logs accumulated in the storage log 102b while being thinned out by the log deletion unit 103e via the communication unit 101. And upload it to the log collection device 10. In addition, the upload unit 103f deletes the uploaded log from the accumulated log 102b.

Next, the processing procedure executed by the in-vehicle device 100 according to the embodiment will be described with reference to FIG. FIG. 5 is a flowchart showing a processing procedure executed by the in-vehicle device 100 according to the embodiment.

As a premise of the processing procedure shown in FIG. 5, the in-vehicle device 100 has already downloaded the latest version of the retention priority setting information 102a, and at least the ACC power is turned on so that the log related to the vehicle V can be collected. It shall be in a state.

First, the acquisition unit 103c acquires the vehicle status of the vehicle V (step S101). Then, the correction unit 103b corrects the holding priority of each item of the holding priority setting information 102a according to the acquired vehicle condition (step S102).

Further, in parallel with step S102, the log collecting unit 103d collects a log based on the vehicle condition acquired by the acquisition unit 103c (step S103).

Then, it is determined whether or not the situation requires deletion of the log (step S104). The situation requiring the deletion of the log may be related to the remaining storage capacity of the in-vehicle device 100 as described above, and also related to, for example, the mileage since the previous upload, the number of elapsed days, and the like. It may be a thing.

Then, if it is necessary to delete the log here (step S104, Yes), the log deletion unit 103e deletes the log based on the corrected retention priority (step S105).

Further, if the situation does not require deletion of the log (step S104, No), the process from step S101 is repeated.

As described above, the in-vehicle device 100 according to the embodiment is mounted on the vehicle V, collects and accumulates logs related to the vehicle V, and has a network with the log collecting device 10 (corresponding to an example of the “upper device”). An in-vehicle device 100 that transmits a log accumulated in the log collecting device 10 when a connection is established, and includes an acquisition unit 103c, a correction unit 103b, and a log deletion unit 103e. The acquisition unit 103c acquires the vehicle status. The correction unit 103b corrects the retention priority of the data item set in advance for each data item of the log according to the vehicle condition acquired by the acquisition unit 103c. The log deletion unit 103e deletes the log from the one with the lowest retention priority based on the retention priority corrected by the correction unit 103b.

Therefore, according to the in-vehicle device 100 according to the embodiment, unnecessary logs can be deleted while maintaining the information density.

Further, the log deletion unit 103e deletes the log based on the retention priority when the vehicle status indicates a predetermined situation requiring the deletion of the log.

Therefore, according to the in-vehicle device 100 according to the embodiment, the log is not continuously deleted unnecessarily. This can contribute to maintaining the information density.

Further, the retention priority is set in advance in the log collecting device 10 based on a predetermined priority setting.

Therefore, according to the in-vehicle device 100 according to the embodiment, the log that is considered to have high utility value in advance on the log collecting device 10 side can be left with priority, and the log with low priority can be deleted. You can delete unnecessary logs while retaining them.

Further, the correction unit 103b corrects the holding priority based on the driving tendency of the user of the vehicle V indicated by the vehicle condition.

Therefore, according to the in-vehicle device 100 according to the embodiment, the logs that are predicted to be useful according to the driving tendency of the user can be left with priority, and the logs with low priority can be deleted. You can delete unnecessary logs while preserving.

Further, the correction unit 103b corrects the holding priority based on the driving environment of the vehicle V indicated by the vehicle condition.

Therefore, according to the in-vehicle device 100 according to the embodiment, the log that is predicted to be useful according to the driving environment such as a specific area, a specific time zone, or a combination thereof is left with priority, and the priority is given. Since logs with a low density can be deleted, unnecessary logs can be deleted while maintaining the information density.

Further, the correction unit 103b corrects the holding priority based on the attribute of the in-vehicle device 100 indicated by the vehicle condition.

Therefore, according to the in-vehicle device 100 according to the embodiment, the log that is predicted to be useful according to the model, delivery destination, product serial number, etc. of the in-vehicle device 100 is left with priority, and the log has a lower priority. Can be deleted, so unnecessary logs can be deleted while maintaining the information density.

In the above-described embodiment, the attribute table is a table in which the retention priority of specific data items mainly according to the attributes of the in-vehicle device 100 is set, but the vehicle V is owned or used. It may include data items according to the attributes of the user. The attributes of the user referred to here are, for example, gender and age group.

Further, in response to this, for example, the correction unit 103b of the in-vehicle device 100 may add the attribute of the user as an element necessary for the calculation in the driving tendency diagnosis.

Further, when the correction unit 103b corrects the holding priority, the log amount accumulated in the storage log 102b during a predetermined elapsed time or a predetermined mileage, for example, based on the holding priority of each item after the correction. May be simulated. Then, as a result of such calculation, if it is found that logs exceeding a predetermined upper limit value are accumulated for the storage capacity of the in-vehicle device 100, for example, the correction unit 103b corrects the correction amount itself of the holding priority. The retention priority may be reviewed.

Further, in the above-described embodiment, the log user is, for example, an engineer who analyzes the behavior of the vehicle V, analyzes the usage status of the in-vehicle device 100, analyzes the driving tendency of the user, analyzes the running of the vehicle V at the accident-prone point, and the like. However, the present invention is not limited to this, and may be, for example, a corporate user such as a service provider or a general individual user who uses a cloud service.

Further effects and variations can be easily derived by those skilled in the art. For this reason, the broader aspects of the invention are not limited to the particular details and representative embodiments expressed and described as described above. Therefore, various modifications can be made without departing from the spirit or scope of the general concept of the invention as defined by the appended claims and their equivalents.

1 Log collection system 10 Log collection device 12a Retention priority setting information 12b Collection log DB
13a Setting unit 13b Distribution unit 13c Collection unit 13d Analysis unit 100 In-vehicle device 102a Holding priority setting information 102b Accumulation log 103a Download unit 103b Correction unit 103c Acquisition unit 103d Log collection unit 103e Log deletion unit 103f Upload unit 150 Various sensors 200 Center terminal SP smartphone V vehicle

Claims (8)

An in-vehicle device mounted on a vehicle that collects and accumulates logs related to the vehicle and transmits the logs accumulated in the higher-level device when a network connection with the higher-level device is established.
The acquisition unit that acquires the vehicle status of the vehicle and
A correction unit that corrects the retention priority of the data item, which is set in advance for each data item of the log, according to the vehicle condition acquired by the acquisition unit.
An in-vehicle device including a log deleting unit that deletes the log from the one having the lowest holding priority based on the holding priority corrected by the correction unit. The log deletion unit
The vehicle-mounted device according to claim 1, wherein when the vehicle situation indicates a predetermined situation requiring the deletion of the log, the log is deleted based on the retention priority. The vehicle-mounted device according to claim 1 or 2, wherein the holding priority is set in advance in the higher-level device based on a predetermined priority setting. The correction unit
The vehicle-mounted device according to claim 1, 2 or 3, wherein the holding priority is corrected based on the driving tendency of the user of the vehicle indicated by the vehicle condition. The correction unit
The vehicle-mounted device according to any one of claims 1 to 4, wherein the holding priority is corrected based on the driving environment of the vehicle indicated by the vehicle condition. The correction unit
The vehicle-mounted device according to any one of claims 1 to 5, wherein the holding priority is corrected based on the attributes of the vehicle-mounted device indicated by the vehicle condition. The in-vehicle device according to any one of claims 1 to 6,
A log collection system including the higher-level device. It is a log collection method using an in-vehicle device that is mounted on a vehicle, collects and accumulates logs related to the vehicle, and transmits the logs accumulated in the higher-level device when a network connection with the higher-level device is established. hand,
The acquisition process for acquiring the vehicle status of the vehicle and
A calculation step of correcting the retention priority of the data item set in advance for each data item of the log according to the vehicle condition acquired by the acquisition process, and a calculation step.
A log collection method comprising a log deletion step of deleting the log from the one having the lowest retention priority based on the retention priority corrected by the calculation step.

Images