Log management device, log management method, and log management program

Abstract

To provide a log management device which records travel log data of a vehicle in a storage device, can record and hold the travel log data from start to completion of travel of the vehicle.SOLUTION: A log management device concerning the present disclosure comprises: a storage device for recording travel log data of a vehicle; and one or more processors, wherein the one or more processors are constituted to execute pieces of processing of: acquiring current idle capacity of the storage device; acquiring a travel plan of the vehicle; calculating a predicted data size of the travel log data which is predicted to be recorded in future in the travel plan; predicting shortage of a capacity of the storage device in the travel plan on the basis of the predicted data size and the current idle capacity of the storage device; and increasing the idle capacity in response to a fact that the shortage of the capacity of the storage device is predicted.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to a technique for recording vehicle driving log data in a storage device. [Background technology]

[0002] In vehicles, driving log data is recorded in a storage device in order to investigate the cause of accidents or breakdowns. In particular, in autonomous vehicles, the system is larger than that of a general vehicle, but it is required to be able to objectively clarify where the responsibility lies, and the amount of driving log data that is desired to be recorded is huge. For this reason, various technologies have been proposed to efficiently record driving log data.

[0003] For example, Patent Document 1 discloses a vehicle recording device equipped with a recording target setting unit that switches information to be recorded according to the driving mode of an autonomous driving ECU. Other documents that show the technical level of this technical field include the following Patent Documents 2 and 3. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2021-174413 A [Patent Document 2] JP 2019-139291 A [Patent Document 3] JP 2010-182148 A Summary of the Invention [Problem to be solved by the invention]

[0005] Considering the purpose, it is desirable that the driving log data recorded from when the vehicle starts traveling be retained at least until the vehicle ends its travel. However, the capacity of the storage device for recording the driving log data is naturally limited. For this reason, there is a risk that the capacity of the storage device will be insufficient between when the vehicle starts traveling and when it ends its travel, making it impossible to record the driving log data or requiring it to be overwritten. In addition, if the storage device is replaced so that the recording of the driving log data can be continued, problems such as reduced convenience due to the need for work and increased personnel costs for the replacement may arise.

[0006] As disclosed in the above patent document, it is possible to avoid a capacity shortage by selecting and recording the driving log data required depending on the situation. However, there is a risk that the system will not be able to properly detect the situation and the required driving log data will not be recorded. In particular, in an autonomous vehicle, it is desirable to record and store all of the driving log data, and a more appropriate means is required.

[0007] In consideration of the above-mentioned problems, one object of the present disclosure is to provide a technology capable of recording and retaining driving log data from the time a vehicle starts traveling to the time it ends traveling. [Means for solving the problem]

[0008] The first disclosure relates to a log management device.

[0009] The log management device of the first disclosure comprises a storage device for recording driving log data of a vehicle, and one or more processors, and the one or more processors are configured to execute the following processes: acquiring current free space in the storage device; acquiring a driving plan for the vehicle; calculating a predicted data size of driving log data predicted to be recorded in the future in the driving plan; predicting a shortage of capacity in the storage device in the driving plan based on the predicted data size and the current free space in the storage device; and increasing the free space in response to the predicted shortage of capacity in the storage device.

[0010] The second disclosure relates to a log management device having the following characteristics in addition to the log management device according to the first disclosure.

[0011] The one or more processors are configured to further execute a process of instructing the vehicle to stop running in response to a predicted capacity shortage in the storage device, and, on the condition that the vehicle has stopped running, execute a process of increasing free space.

[0012] The third disclosure relates to a log management device having the following characteristics in addition to the log management device according to the second disclosure.

[0013] The one or more processors are further configured to execute a process of determining whether the free space of the storage device has increased beyond a required space obtained by subtracting the free space from the predicted data size as a result of execution of the process of increasing the free space, and a process of terminating the process of increasing the free space and instructing the vehicle to resume driving when the free space of the storage device has increased beyond the required space.

[0014] The fourth disclosure relates to a log management device according to any one of the first to third disclosures, further having the following features.

[0015] The process of increasing the free space includes increasing the free space of the storage device by compressing the driving log data recorded in the storage device.

[0016] The fifth disclosure relates to a log management device having the following characteristics in addition to the log management device according to the fourth disclosure.

[0017] The compression process includes obtaining a compression efficiency for each data type of the driving log data, and compressing the driving log data in order of the data type with the highest compression efficiency.

[0018] The sixth disclosure relates to a log management device having the following characteristics in addition to the log management device according to the fourth disclosure.

[0019] The compression process includes compressing the driving log data by selecting a compression method with the shortest compression time from a plurality of compression methods that can increase the free space of the storage device by a predetermined amount or more.

[0020] The seventh disclosure relates to a log management device according to any one of the first to third disclosures, further comprising the following features.

[0021] The process of increasing the free space includes increasing the free space by transmitting the driving log data recorded in the storage device to an external device and deleting the transmitted driving log data.

[0022] The eighth disclosure relates to a log management method executed by one or more processors for recording vehicle travel log data in a storage device.

[0023] The log management method according to the eighth disclosure is characterized in that it includes obtaining current free space in a storage device, obtaining a driving plan for the vehicle, calculating a predicted data size of driving log data predicted to be recorded in the future in the driving plan, predicting a shortage of storage device capacity in the driving plan based on the predicted data size and the current free space in the storage device, and executing a process to increase the free space in response to the predicted shortage of storage device capacity.

[0024] The ninth disclosure relates to a log management method further having the following features with respect to the log management method according to the eighth disclosure.

[0025] The method further includes instructing the vehicle to stop running in response to a predicted capacity shortage of the storage device, and executes a process of increasing free space on condition that the vehicle has stopped running.

[0026] The tenth disclosure relates to a log management method further having the following characteristics with respect to the log management method according to the ninth disclosure.

[0027] The method further includes determining whether the free space of the storage device has increased beyond a required capacity obtained by subtracting the free space from the predicted data size by executing the process of increasing the free space, and, upon determining that the free space of the storage device has increased beyond the required capacity, terminating the process of increasing the free space and instructing the vehicle to resume traveling.

[0028] The eleventh disclosure relates to a log management program that causes a computer to execute a process of recording vehicle driving log data in a storage device.

[0029] The log management program of the eleventh disclosure is characterized in that it is configured to cause the computer to further execute the following processes: a process for acquiring the current free space in the storage device; a process for acquiring a driving plan for the vehicle; a process for calculating a predicted data size of driving log data predicted to be recorded in the future in the driving plan; a process for predicting a shortage of capacity in the storage device in the driving plan based on the predicted data size and the current free space in the storage device; and a process for increasing the free space in response to the predicted shortage of capacity in the storage device.

[0030] A twelfth disclosure relates to a log management program having the following characteristics in addition to the log management program according to the eleventh disclosure.

[0031] In response to a predicted capacity shortage in the storage device, the computer is further caused to execute a process of instructing the vehicle to stop traveling, and, on the condition that the vehicle has stopped traveling, the computer is caused to execute a process of increasing free space.

[0032] The thirteenth disclosure relates to a log management program having the following characteristics in addition to the log management program according to the twelfth disclosure.

[0033] The computer is further configured to execute a process of determining whether the free space of the storage device has increased beyond the required space obtained by subtracting the free space from the predicted data size as a result of execution of the process of increasing the free space, and a process of terminating the process of increasing the free space and instructing the vehicle to resume driving when the free space of the storage device has increased beyond the required space. Effect of the Invention

[0034] According to the present disclosure, a predicted data size of driving log data predicted to be recorded in the future in a driving plan is calculated. Then, when a capacity shortage in the storage device in the driving plan is predicted based on the predicted data size and the current free space of the storage device, a process of increasing the free space of the storage device is executed. This allows the free space in the storage device to be increased in a timely manner while the vehicle is driving to the destination according to the driving plan, and prevents the storage device from running out of capacity. In addition, driving log data from when the vehicle starts driving to when it finishes driving can be recorded and stored. [Brief description of the drawings]

[0035] [Figure 1] 1 is a conceptual diagram for explaining an overview of a log management device according to a first embodiment. FIG. [Diagram 2] 2 is a block diagram showing the configuration of a process executed by a processing device in the log management device according to the first embodiment. FIG. [Diagram 3] FIG. 2 is a block diagram illustrating a configuration of a log management device. [Figure 4] 4 is a flowchart showing a process executed by the log management device according to the first embodiment. [Diagram 5] FIG. 11 is a block diagram showing the configuration of a process executed by a processing device in a log management device according to a second embodiment. [Figure 6] 10 is a flowchart showing a process executed by a log management device according to a second embodiment. [Figure 7] FIG. 13 is a conceptual diagram for explaining an overview of a log management device according to a third embodiment. [Figure 8] FIG. 11 is a block diagram showing the configuration of a process executed by a processing device in a log management device according to a third embodiment. [Figure 9] 13 is a flowchart showing a process executed by a log management device according to a third embodiment. [Figure 10] 13 is a flowchart showing a process executed by a log management device according to a third embodiment. [Figure 11] FIG. 13 is a conceptual diagram for explaining an overview of a log management device according to a fourth embodiment. [Figure 12] FIG. 13 is a block diagram showing the configuration of a process executed by a processing device in a log management device according to a fourth embodiment. [Figure 13] 13 is a flowchart showing a process executed by a log management device according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] 1. First embodiment The first embodiment will be described below.

[0037] 1-1. Overview First, an overview of a log management device 100 according to a first embodiment will be described with reference to FIG.

[0038] The log management device 100 provides a function of recording vehicle travel log data. The log management device 100 is configured to be able to communicate with various devices included in the vehicle control system 200, and acquires the travel log data from the vehicle control system 200. For example, the log management device 100 is mounted on a vehicle and connected to an in-vehicle network configured with a CAN (Controller Area Network) or the like.

[0039] Here, the vehicle control system 200 represents the entire system for controlling the vehicle, and various controls of the vehicle are realized by the vehicle control system 200. For example, when the vehicle is an autonomous vehicle, the autonomous driving function of the vehicle is realized by the vehicle control system 200. The vehicle control system 200 is typically configured with one or more sensors 210 that detect the driving environment of the vehicle, one or more communication devices 220 that communicate with devices outside the vehicle to transmit and receive information, one or more ECUs (Electronic Control Units) 230 that execute processes related to various controls based on the information detected by the one or more sensors 210 and the information received by the one or more communication devices 220, and one or more actuators 240 driven by the one or more ECUs 230.

[0040] Examples of the one or more sensors 210 include sensors that detect the surrounding environment of the vehicle (preceding vehicle, white lines, obstacles, etc.), such as a camera, a millimeter wave radar, and a LiDAR, and sensors that detect the running state of the vehicle (vehicle speed, acceleration, yaw rate, etc.), such as a vehicle speed sensor, a G sensor, and a gyro sensor. Examples of the one or more communication devices 220 include a wireless communication device that communicates with infrastructure or surrounding vehicles, a GPS receiver, and a device that connects to the Internet and communicates with a server on the Internet. Examples of the one or more actuators 240 include an actuator related to the operation of a power unit (internal combustion engine, electric motor, etc.), an actuator related to the operation of a brake mechanism, and an actuator related to the operation of a steering mechanism. In addition, when the vehicle is an autonomous vehicle, examples of the one or more ECUs 230 include an ECU (autonomous driving device) that executes processing related to the autonomous driving function.

[0041] Therefore, examples of driving log data acquired from the vehicle control system 200 include time series data of detection information from one or more sensors 210 (driving video, point cloud data, vehicle distance, white line recognition status, detected objects, vehicle speed, acceleration, yaw rate, etc.), time series data of received information from one or more communication devices 220 (map information, road traffic information, GPS position information, etc.), and time series data of control information from one or more ECUs (accelerator opening command value, brake control amount, steering control amount, target driving trajectory, self-position estimation result, etc.).

[0042] The log management device 100 is further configured to acquire a driving plan from the vehicle control system 200. The driving plan is information that specifies the driving of the vehicle to a destination, and typically includes location information of the destination, a driving route to the destination, and an arrival time at the destination.

[0043] Here, in the log management device 100, it is assumed that the destination in the driving plan is a point where the vehicle ends its driving. For example, if the vehicle is a scheduled bus, the destination in the driving plan is a bus stop that is the end point or a garage to which the vehicle will then head. If the vehicle is a taxi or an autonomous vehicle, the destination in the driving plan is a boarding / alighting location designated by a passenger or a garage to which the vehicle will then head. However, the destination in the driving plan may also be a point where the vehicle temporarily ends its driving.

[0044] The driving plan may be information generated in the vehicle control system 200, or may be information acquired by one or more communication devices 220. Alternatively, the driving plan may be predetermined information. For example, if the vehicle is an autonomous vehicle, the driving plan may be generated by the autonomous driving function, and if the vehicle is not an autonomous vehicle, the driving plan may be generated by the car navigation function. Also, if the vehicle is an on-demand bus, the driving plan may be received from a dispatch system, and if the vehicle is a scheduled bus, the driving plan may be predetermined.

[0045] The log management device 100 includes a processing device 110 and a storage device 120. In the log management device 100, driving log data acquired from the vehicle control system 200 is recorded in the storage device 120. In addition, a driving plan acquired from the vehicle control system 200 is transmitted to the processing device 110. Examples of the storage device 120 include an HDD, an SSD, and a flash memory. The processing device 110 is a computer that manages the driving log data recorded in the storage device 120.

[0046] In the log management device 100 according to the first embodiment, the processing performed by the processing device 110 is characteristic. The processing device 110 is configured to acquire the current free space from the storage device 120. Then, the processing device 110 executes a process of compressing the driving log data recorded in the storage device 120 according to the vehicle driving plan and the current free space of the storage device 120. Hereinafter, the function of the log management device 100 realized by the characteristic processing performed by the processing device 110 is also referred to as a "capacity securing function."

[0047] 2 is a block diagram showing the configuration of a characteristic process executed by the processing device 110 in the log management device 100 according to the first embodiment, that is, a process related to a capacity securing function. The process related to the capacity securing function is configured by a travel time prediction processing unit P110, a storage capacity acquisition processing unit P120, a management processing unit P130, and a log compression processing unit P140.

[0048] The travel time prediction processing unit P110 calculates a predicted travel time required for the vehicle to travel from the current location to the destination based on the travel plan acquired by the log management device 100. For example, the travel time prediction processing unit P110 calculates a predicted travel time from the distance of the travel route from the current location to the destination in the travel plan and the average vehicle speed of the vehicle. Furthermore, the travel time prediction processing unit P110 may be configured to calculate a predicted travel time including a predefined error. For example, the travel time prediction processing unit P110 may calculate a predicted travel time within a range of the average value + 3σ.

[0049] Here, in order to calculate the predicted driving time in the driving time prediction processing unit P110, the log management device 100 may be configured to acquire detection information of one or more sensors 210, reception information of one or more communication devices 220, or control information of one or more ECUs 230 from the vehicle control system 200. For example, the driving time prediction processing unit P110 may use position information (GPS position information or self-position estimation information) acquired from the vehicle control system 200 as the current location of the vehicle. Alternatively, the driving time prediction processing unit P110 may be configured to use information acquired as driving log data when calculating the predicted driving time.

[0050] The storage capacity acquisition processing part P120 accesses the storage device 120 and acquires the current free space in the storage device 120.

[0051] The management processing unit P130 executes processing related to management of driving log data to be recorded in the storage device 120, based on the predicted driving time calculated by the driving time prediction processing unit P110 and the free space acquired by the storage capacity acquisition processing unit P120. In particular, the management processing unit P130 is configured to execute a predicted data size calculation process P131 and a free space securing process P132.

[0052] The predicted data size calculation process P131 is a process for calculating the data size of the driving log data predicted to be recorded in the future in the driving plan (hereinafter, also referred to as "predicted data size"). For example, the data size recorded per second is calculated from the change in the free space of the storage device 120, and the predicted data size is calculated from the product of the predicted driving time and the data size recorded per second. Furthermore, in the predicted data size calculation process P131, the management processing unit P130 may calculate the predicted data size including an error. For example, when the driving time prediction processing unit P110 is configured to calculate the predicted driving time within the range of the average value + 3σ, in the predicted data size calculation process P131, the management processing unit P130 may calculate the predicted data size including an error from the product of the predicted driving time calculated within the range of the average value + 3σ and the data size recorded per second.

[0053] The free space allocation process P132 is a process that generates, under specific conditions, an instruction to execute a process to the log compression process P140. The instruction generated by executing the free space allocation process P132 is transmitted from the management process P130 to the log compression process P140.

[0054] At least the free space securing process P132 includes a process of predicting a capacity shortage of the storage device 120 in the travel plan based on the predicted data size calculated by the predicted data size calculation process P131 and the free space acquired by the storage capacity acquisition process P120. Then, the management process P130 is configured to generate an instruction to cause the log compression process P140 to execute processing in response to a prediction of a capacity shortage of the storage device 120 in the free space securing process P132.

[0055] The log compression processor P140 accesses the storage device 120 and executes compression processing of the driving log data recorded in the storage device 120 according to instructions transmitted from the management processing unit P130. In other words, as the log compression processor P140 executes processing, the free space of the storage device 120 increases. The log compression processor P140 also notifies the management processing unit P130 of the execution status of the compression processing. Note that the compression processing executed by the log compression processor P140 may employ a suitable known algorithm.

[0056] As described above, the process related to the capacity securing function is configured. In particular, in the capacity securing function, the processing device 110 executes a process to increase the free space of the storage device 120 in response to a prediction of a shortage of the capacity of the storage device 120 in the driving plan based on the predicted data size and the current free space of the storage device 120.

[0057] 1-2.Configuration Next, the configuration of the log management device 100 according to the first embodiment will be described with reference to Fig. 3. As described above, the log management device 100 includes a processing device 110 and a storage device 120. The processing device 110 is configured to be able to access the storage device 120 and process the driving log data recorded in the storage device 120. For example, the processing device 110 is electrically connected to the storage device 120 and is configured to be able to transmit information to and from the storage device 120.

[0058] The processing device 110 is a computer including a memory 111 and a processor 115. The memory 111 is coupled to the processor 115 and stores various data 112 required for executing the processing and a plurality of executable instructions 114. Here, the instructions 114 are provided by a computer program 113 (log management program). Information acquired by the processing device 110 when executing the processing is stored in the memory 111 as data 112.

[0059] The instructions 114 are configured to cause the processor 115 to execute a predetermined process. That is, the predetermined process is realized by the processor 115 operating in accordance with the instructions 114. In particular, the instructions 114 are configured to cause the processor 115 to execute processes related to the running time prediction processing unit P110, the storage capacity acquisition processing unit P120, the management processing unit P130, and the log compression processing unit P140. That is, the processor 115 operates in accordance with the instructions 114, so that the processor 115 functions as the running time prediction processing unit P110, the storage capacity acquisition processing unit P120, the management processing unit P130, and the log compression processing unit P140.

[0060] The processing device 110 may be configured with a plurality of computers. In this case, the processing device 110 may include a plurality of memories 111 and a plurality of processors 115. For example, the processing device 110 may be configured separately from a microcomputer installed in the vehicle and a server configured on the Internet. The plurality of computers may be configured to execute processing in cooperation with each other. For example, the processing related to the running time prediction processing unit P110 may be executed in a server configured on the Internet, and the microcomputer installed in the vehicle may be configured to acquire the predicted running time by communicating with the server and execute other processing.

[0061] 1-3. Processing Next, a process executed by the log management device 100 according to the first embodiment, more specifically, a process executed by the processor 115 will be described. Fig. 4 is a flowchart showing the process executed by the log management device 100 according to the first embodiment. The flowchart shown in Fig. 4 is typically executed repeatedly at predetermined intervals.

[0062] In step S100, the log management device 100 calculates a predicted driving time from the driving plan. The process of step S100 is executed by the driving time prediction processing unit P110. After step S100, the process proceeds to step S110.

[0063] In step S110, the log management device 100 calculates a predicted data size from the predicted driving time calculated in step S100. The process of step S110 is executed by the management process unit P130 as a predicted data size calculation process P131. After step S110, the process proceeds to step S120.

[0064] In step S120, the log management device 100 acquires the current free space of the storage device 120. The process of step S120 is executed by a storage capacity acquisition processing unit P120. After step S120, the process proceeds to step S130.

[0065] In step S130, the log management device 100 determines whether the free space acquired in step S120 is larger than the estimated data size calculated in step S110.

[0066] If the free space is larger than the predicted data size (step S130; Yes), it is determined that a capacity shortage in the storage device 120 in the travel plan is not predicted, and the current process ends without executing the compression process.

[0067] If the free space is equal to or smaller than the predicted data size (step S130; No), a shortage of space in the storage device 120 for the travel plan is predicted, and the process proceeds to step S140.

[0068] In step S140, the log management device 100 predicts the free space (free space after compression) of the storage device 120 that can be secured by executing the compression process. For example, the free space after compression is predicted from the compression method to be adopted and the data size of the driving log data to be compressed. After step S140, the process proceeds to step S150.

[0069] In step S150, the log management device 100 determines whether the free space after compression predicted in step S140 is larger than the predicted data size calculated in step S110. Here, the processes related to steps S130-S150 are executed by the management processing unit P130 as free space securing process P132.

[0070] If the free space after compression is equal to or smaller than the predicted data size (step S150; No), it is determined that the insufficient capacity of the storage device 120 cannot be avoided even by performing the compression process, and a warning is issued (step S170). Examples of the warning include audible or visual notification to passengers in the vehicle, and a notification by communication to the manager of the vehicle (e.g., the bus operating company). By issuing a warning in this manner, it is possible to request a response in the case where the insufficient capacity of the storage device 120 cannot be avoided even by performing the compression process. For example, the bus operating company can take measures such as dispatching personnel to retrieve the storage device 120. This in turn makes it possible to prevent situations in which necessary travel log data is not recorded.

[0071] If the free space after compression is larger than the predicted data size (step S150; Yes), the log management device 100 determines that a capacity shortage in the storage device 120 can be avoided by performing the compression process, and performs the compression process in a predetermined manner (step S160). The process of step S160 is performed by the log compression processing unit P140 in response to an instruction generated by the management processing unit P130 when the free space after compression is larger than the predicted data size (step S150; Yes). After step S160, the log compression processing unit P140 notifies the management processing unit P130 of the completion of the compression process, and the process ends.

[0072] In this manner, the process is executed by the log management device 100 according to the first embodiment. Also, in this manner, the log management device 100 according to the first embodiment realizes a log management method for recording vehicle travel log data in the storage device 120. Alternatively, the log management method can be realized as a log management program that causes a computer to execute the log management method. In this case, the log management program can be provided as an encoded recording medium.

[0073] 1-4.Effects As described above, according to the first embodiment, the predicted data size of the travel log data predicted to be recorded in the future in the travel plan is calculated. Then, when a shortage of the capacity of the storage device 120 in the travel plan is predicted based on the predicted data size and the current free space of the storage device 120, the free space of the storage device 120 is increased by the compression process. This allows the free space of the storage device 120 to be increased in a timely manner while the vehicle travels to the destination according to the travel plan, and prevents the capacity of the storage device 120 from running short. In addition, the travel log data from when the vehicle starts traveling to when it ends traveling can be recorded and stored. In addition, the process of increasing the free space of the storage device 120 (compression process) is executed in response to a prediction of a shortage of the capacity of the storage device 120 in the travel plan, and is not executed unnecessarily. In addition, the free space of the storage device 120 can be increased in a timely manner without excessively increasing the processing load of the log management device 100.

[0074] The log management device 100 may be configured to sequentially record the traveling log data acquired from the vehicle control system 200 in the storage device 120 without relying on the processing device 110, or may be configured to select the traveling log data to be recorded by the processing device 110. According to the first embodiment, the free space of the storage device 120 can be increased in a timely manner, so that when the processing device 110 selects the traveling log data to be recorded, a wider range of selected traveling log data can be provided.

[0075] 2. Second embodiment The first embodiment will be described below. However, in the following, differences from the first embodiment will be mainly described in detail, and overlapping contents with the first embodiment will be omitted as appropriate.

[0076] 2-1. Overview First, an overview of a log management device 100 according to the second embodiment will be described.

[0077] The log management device 100 according to the second embodiment is characterized by the processing executed by the management processing unit P130 compared to the first embodiment. FIG. 5 is a block diagram showing the configuration of processing related to the capacity allocation function in the log management device 100 according to the second embodiment. As shown in FIG. 5, compared to the first embodiment (FIG. 2), the management processing unit P130 is configured to further execute a compression method selection process P133. The configuration of the log management device 100 according to the second embodiment may be similar to that of the log management device 100 according to the first embodiment (FIG. 3).

[0078] The compression method selection process P133 is a process for generating an instruction to specify the compression method of the compression process executed by the log compression processing unit P140 or the driving log data to be compressed, based on the free space of the storage device 120 and information on the driving log data recorded in the storage device 120. Here, examples of the information on the driving log data include information on the time when the driving log data was recorded, information on the data type of the driving log data (image, voice, message, numerical value, etc.), and information on the data size for each data type. The management processing unit P130 may be configured to acquire the information on the driving log data from the storage capacity acquisition processing unit P120. In this case, the storage capacity acquisition processing unit P120 acquires or calculates the information on the driving log data by accessing the storage device 120. Alternatively, the management processing unit P130 may be configured to directly access the storage device 120 to acquire or calculate the information on the driving log data.

[0079] The instruction generated by executing the compression method selection process P133 is transmitted from the management process unit P130 to the log compression process unit P140. The log compression process unit P140 executes the compression process according to the instruction specifying the compression method or the driving log data to be compressed transmitted from the management process unit P130.

[0080] There are several possible modes for the compression method selection process P133, which will be described below.

[0081] The first mode is a case where the driving log data to be compressed is specified in the order of oldest recorded time by the compression method selection process P133. In this case, for example, the range of times when the driving log data was recorded is generated as an instruction to specify the driving log data to be compressed by the compression method selection process P133. The time range related to the instruction is given, for example, from the time when the oldest recorded time is included to the time when the driving log data that can increase the free space of the storage device 120 by the compression process by a predetermined capacity or more is included. Here, the predetermined capacity is, for example, the difference between the predicted data size and the current free space. Alternatively, the compression method selection process P133 may simply generate an instruction to perform the compression process in the order of oldest recorded time and a predetermined capacity. Then, the log compression processing unit P140 may be configured to perform the compression process in the order of oldest recorded time and end the compression process when the free space has increased by the predetermined capacity or more.

[0082] The second aspect is a case where the driving log data to be compressed is specified in the order of driving log data with the highest compression efficiency in a specific compression method. In this case, for example, the management processing unit P130 acquires the data type of the driving log data recorded in the storage device 120 and the data size information for each data type as the information of the driving log data. Then, the compression method selection process P133 generates the data type of the driving log data as an instruction to specify the driving log data to be compressed. For example, the data type related to the instruction is given so that the driving log data that can increase the free space of the storage device 120 by the compression process by a predetermined capacity or more is included in the order of the highest compression efficiency. Alternatively, the compression method selection process P133 may simply generate an instruction to perform the compression process in the order of the highest compression efficiency, and the compression efficiency and the predetermined capacity of the driving log data to be recorded. Then, the log compression processing unit P140 may be configured to perform the compression process in the order of the highest compression efficiency, and end the compression process when the free space has increased by the predetermined capacity or more.

[0083] The compression efficiency can be managed by storing it as data 112 in memory 111. Alternatively, it can be provided as a computer program 113. The compression efficiency may be determined based on a prior investigation.

[0084] As an example of such a compression method selection process P133, when the compression efficiency of image data is the highest and the compression efficiency of message data is the lowest, compression processing is started from the image data.

[0085] The third mode is to select and specify the compression method with the shortest compression time from among multiple compression methods that can increase the free space by a specified amount or more. In this case, the log compression processor P140 is configured to be able to execute compression processing using multiple compression methods. Then, an instruction for the compression method is generated by the compression method selection process P133.

[0086] Whether or not the free space can be increased by a predetermined amount or more can be determined from the data size of the driving log data recorded in the storage device 120 and the specifications of the compression method. The compression time for each of the multiple compression methods can be calculated by providing the compression efficiency for each of the multiple compression methods. The compression efficiency for each of the multiple compression methods may be stored as data 112 in the memory 111, or may be provided as a computer program 113.

[0087] In the third aspect, the compression method selection process P133 may generate instructions including a predetermined capacity, a size of the driving log data to be recorded in the storage device 120, and a compression efficiency for each of a plurality of compression methods. The log compression processing unit P140 may be configured to select a compression method with the shortest compression time from a plurality of compression methods that can increase the free space by more than the predetermined capacity, and execute the compression process.

[0088] As an example of such a compression method selection process P133, for example, let us assume that the log compression processor P140 is configured to be able to execute compression processes using three compression methods: method A, method B, and method C. Here, it is assumed that method A has the longest compression time and the highest compression efficiency, in that order. Now, it is assumed that method A can secure free space up to 1TB, method B can secure free space up to 1.6TB, and method C can secure free space up to 2TB. In this case, when attempting to secure free space of 1.5TB or more (predetermined capacity is 1.5TB), method B will be selected.

[0089] The above-described aspects may be combined with one another. For example, a combination of the second and third aspects may be adopted as the compression method selection process P133.

[0090] 2-2. Processing Next, a process executed by the log management device 100 according to the second embodiment will be described. Fig. 6 is a flowchart showing the process executed by the log management device 100 according to the second embodiment. The flowchart shown in Fig. 6 is typically executed repeatedly at predetermined intervals.

[0091] In the second embodiment, in contrast to the first embodiment (FIG. 4), if the free space after compression is larger than the predicted data size (step S150; Yes), the log management device 100 executes the compression method selection process P133 (step S200). Then, after step S200, the log management device 100 executes the compression process (step S210). The process related to step S210 is executed by the log compression processing unit P140 upon receiving a process execution instruction generated by the management processing unit P130. Here, the log compression processing unit P140 executes the compression process according to the compression method instruction generated by the execution of the compression method selection process P133. After step S210, the log compression processing unit P140 notifies the management processing unit P130 of the completion of the compression process, and the process ends.

[0092] In this manner, the process is executed by the log management device 100 according to the second embodiment. Also, in this manner, the log management device 100 according to the second embodiment realizes a log management method for recording vehicle travel log data in the storage device 120. Alternatively, the log management method can be realized as a log management program that causes a computer to execute the log management method. In this case, the log management program can be provided as an encoded recording medium.

[0093] 2-4.Effects As described above, according to the second embodiment, in addition to the first embodiment, the management process unit P130 further executes a compression method selection process P133. Furthermore, the compression method selection process P133 generates an instruction regarding the compression method of the compression process to be executed by the log compression process unit P140. Then, the log compression process unit P140 executes the compression process in accordance with the instruction regarding the compression method generated by executing the compression method selection process P133.

[0094] This allows for more efficient compression processing to be performed according to the free space of the storage device 120 and the information on the driving log data recorded in the storage device 120. In turn, this prevents unnecessary compression processing from being performed in order to avoid a capacity shortage in the storage device 120, thereby reducing the processing load on the log management device 100.

[0095] 3. Third embodiment The third embodiment will be described below, but in the following, differences from the first embodiment will be mainly described in detail, and overlapping parts with the first embodiment will be omitted as appropriate.

[0096] 3-1. Overview First, an overview of a log management device 100 according to the third embodiment will be described with reference to FIG.

[0097] The log management device 100 according to the third embodiment is characterized in that it issues a driving instruction to the vehicle control system 200. Here, the driving instruction includes an instruction to stop the vehicle from driving, an instruction to start the vehicle from driving, and an instruction to continue the vehicle from driving. The log management device 100 is also configured to acquire the vehicle driving state from the vehicle control system 200. Here, the driving state includes at least information on whether the vehicle is driving or stopped.

[0098] In particular, the log management device 100 according to the third embodiment is configured to instruct the vehicle to stop traveling when a capacity shortage of the storage device 120 in the travel plan is predicted, and then to execute a process (compression process) for increasing the free space of the storage device 120 on the condition that the vehicle has stopped traveling.

[0099] The vehicle control system 200 may be configured to control the vehicle according to a driving instruction. For example, when the vehicle control system 200 realizes an automatic driving function of the vehicle, an ECU (automatic driving device) that executes processing related to the automatic driving function may execute processing to evacuate the vehicle to a safe place and stop the vehicle upon receiving an instruction to stop driving from the log management device 100. At this time, the driving state acquired by the log management device 100 may include information on whether the vehicle is being evacuated. In the following description, it is assumed that the vehicle is an automatic driving vehicle and the automatic driving function is realized by the vehicle control system 200.

[0100] Fig. 8 is a block diagram showing the configuration of processing related to the capacity securing function in the log management device 100 according to the third embodiment. As shown in Fig. 8, in contrast to the first embodiment (Fig. 2), the management processing unit P130 is further configured to give driving instructions to the automatic driving device 231. In addition, the management processing unit P130 acquires the driving state of the vehicle from the automatic driving device 231. Note that the configuration of the log management device 100 according to the third embodiment may be similar to that of the log management device 100 according to the first embodiment (Fig. 3).

[0101] The management processing unit P130 instructs the automatic driving device 231 to drive when the free space securing process P132 is executed. In the log management device 100 according to the third embodiment, the management processing unit P130 is configured to instruct the automatic driving device 231 to stop driving the vehicle when a capacity shortage of the storage device 120 is predicted in the free space securing process P132. Then, the management processing unit P130 is configured to generate an instruction to cause the log compression processing unit P140 to execute processing when the vehicle has stopped driving, based on the driving state acquired from the automatic driving device 231.

[0102] Furthermore, the management processing unit P130 may be configured to instruct the automatic driving device 231 to resume driving upon receiving a notification of the completion of the compression process from the log compression processing unit P140 in the free space securing process P132. In particular, the management processing unit P130 may calculate a required capacity by subtracting the current free space from the predicted data size as the capacity that needs to be increased by the compression process by executing the free space securing process P132. In addition, the management processing unit P130 may be configured to instruct the log compression processing unit P140 of the calculated required capacity. Then, the log compression processing unit P140 may be configured to terminate the compression process and notify the completion of the compression process upon receiving that the free space of the storage device 120 has increased beyond the instructed required capacity.

[0103] 3-2. Processing Next, a process executed by the log management device 100 according to the third embodiment will be described. Figures 9 and 10 are flowcharts showing the process executed by the log management device 100 according to the third embodiment. Here, Figures 9 and 10 are connected at A shown in the figures and show one flowchart. The flowcharts shown in Figures 9 and 10 are typically executed repeatedly at a predetermined cycle.

[0104] In the third embodiment, in contrast to the first embodiment (FIG. 4), when the free space is equal to or smaller than the predicted data size (step S130; No), the log management device 100 instructs the automatic driving device 231 to stop driving the vehicle (step S310). After step S310, the process proceeds to step S320.

[0105] If the available capacity is larger than the predicted data size (step S130; Yes), the log management device 100 instructs the automatic driving device 231 to continue driving the vehicle without performing the compression process (step S300), and the current process ends.

[0106] In step S320, the log management device 100 determines whether or not the vehicle has stopped traveling, based on the traveling state acquired from the automatic driving device 231. When it is determined that the vehicle has stopped traveling (step S320; Yes), the process proceeds to step S140.

[0107] The processes in steps S140, S150, and S170 may be similar to those in the first embodiment.

[0108] In the third embodiment, if the free space after compression is larger than the predicted data size (step S150; Yes), the log management device 100 calculates the required space by subtracting the free space acquired in step S120 from the predicted data size calculated in step S110 (step S330). After step S330, the process proceeds to step S160.

[0109] In step S160, the log management device 100 starts executing the compression process in a predetermined manner. After that, the log management device 100 determines whether the free space of the storage device 120 has increased beyond the required capacity calculated in step S330 at appropriate times (step S340). Then, the log management device 100 continues executing the compression process until the free space of the storage device 120 has increased beyond the required capacity (step S340; No).

[0110] If the free space of the storage device 120 increases beyond the required capacity as a result of the compression process (step S340; Yes), the log management device 100 ends the compression process (step S350). After that, the log management device 100 instructs the automatic driving device 231 to resume driving (step S360), and the process ends.

[0111] In this manner, the process is executed by the log management device 100 according to the third embodiment. Also, in this manner, the log management device 100 according to the third embodiment realizes a log management method for recording vehicle travel log data in the storage device 120. Alternatively, the log management method can be realized as a log management program that causes a computer to execute the log management method. In this case, the log management program can be provided as an encoded recording medium.

[0112] Effects As described above, according to the third embodiment, in contrast to the first embodiment, the log management device 100 instructs the vehicle control system 200 to drive. In particular, when a shortage of capacity of the storage device 120 in the driving plan is predicted, the log management device 100 instructs the vehicle to stop driving. Then, on the condition that the vehicle has stopped driving, the log management device 100 is configured to execute a compression process of the driving log data recorded in the storage device 120.

[0113] This allows the log management device 100 to execute a process for increasing the free space of the storage device 120 while the control of the vehicle is stopped. That is, the log management device 100 can secure the computational resources and communication resources required in the vehicle control system 200 when executing the compression process. As a result, the log management device 100 can execute the compression process using a method that requires a large amount of computation and provides high compression.

[0114] Furthermore, the log management device 100 according to the third embodiment can be configured to calculate the required capacity by subtracting the free space from the predicted data size, and when the free space of the storage device 120 increases beyond the required capacity, to end the compression process and instruct the vehicle to resume driving. By configuring in this way, it is possible to resume driving of the vehicle immediately after performing the compression process as much as necessary. As a result, it is possible to minimize the downtime caused by performing the compression process.

[0115] The third embodiment may be suitably combined with the second embodiment. In this case, in the third aspect of the compression method selection process P133, a predetermined capacity may be set as the required capacity. In the third embodiment, since the control of the vehicle is stopped when the compression process is performed, the log management device 100 can perform the compression process without considering the processing load of the vehicle control system 200. In other words, the quality of the compression method can be determined by considering only the trade-off balance between compression efficiency and compression time. Therefore, the third aspect of the compression method selection process P133 is particularly effective in the combination of the third embodiment and the second embodiment.

[0116] The effects described above are particularly effective in an autonomous vehicle in which the processing load of the vehicle control system 200 is large, requiring many resources, and the amount of driving log data that is desired to be recorded is enormous. Therefore, the autonomous driving system configured to include the log management device 100 and the autonomous driving device 231 according to the third embodiment can be considered as one useful embodiment having the effects described above.

[0117] 4. Fourth embodiment The fourth embodiment will be described below, but in the following, differences from the first embodiment will be mainly described in detail, and overlapping parts with the first embodiment will be omitted as appropriate.

[0118] 4-1. Overview First, an overview of a log management device 100 according to the fourth embodiment will be described with reference to FIG.

[0119] The log management device 100 according to the fourth embodiment is characterized in that it transmits the driving log data recorded in the storage device 120 to an external device. The transmitted driving log data is then deleted from the storage device 120 to increase the free space of the storage device 120. FIG. 11 shows an external storage 300 as the external device. The external storage 300 is, for example, a data server configured on the Internet. In this case, the log management device 100 is configured to be able to connect to the Internet and perform communication. The configuration of the log management device 100 according to the fourth embodiment may be the same as that of the log management device 100 according to the first embodiment (FIG. 3).

[0120] Fig. 12 is a block diagram showing the configuration of processing related to a capacity securing function in the log management device 100 according to the fourth embodiment. As shown in Fig. 12, compared to the first embodiment (Fig. 2), the processing related to the capacity securing function is configured by a log transmission processing unit P141 instead of the log compression processing unit P140.

[0121] In the fourth embodiment, the management processing unit P130 generates an instruction to execute processing to the log transmission processing unit P141 under predetermined conditions in the free space securing process P132. In particular, the management processing unit P130 is configured to generate an instruction to cause the log transmission processing unit P141 to execute processing in response to a predicted shortage of capacity in the storage device 120 in the free space securing process P132. Here, the instruction to cause the log transmission processing unit P141 to execute processing may include information specifying the driving log data to be transmitted to the external storage 300 and deleted from the storage device 120.

[0122] The log transmission processing unit P141 accesses the storage device 120 and, in accordance with instructions transmitted from the management processing unit P130, executes a process of transmitting the driving log data recorded in the storage device 120 to the external storage 300 and a process of deleting the transmitted driving log data from the storage device 120. In other words, the free space of the storage device 120 increases as the log transmission processing unit P141 executes the processing. The log transmission processing unit P141 also notifies the management processing unit P130 of the execution status of the processing.

[0123] 4-2. Processing Next, a process executed by the log management device 100 according to the fourth embodiment will be described. Fig. 13 is a flowchart showing the process executed by the log management device 100 according to the fourth embodiment. The flowchart shown in Fig. 13 is typically executed repeatedly at predetermined intervals.

[0124] In the fourth embodiment, in contrast to the first embodiment (FIG. 4), if the free space is equal to or smaller than the predicted data size (step S130; No), the log management device 100 executes a process of transmitting the driving log data to be recorded in the storage device 120 to the external storage 300 (step S400). Then, it executes a process of deleting the transmitted driving log data from the storage device 120 (step S410).

[0125] The processes of steps S400 and S410 are executed by the log transmission processing unit P141 in response to an instruction generated by the management processing unit P130 when the free space is equal to or less than the predicted data size (step S130; No). After step S410, the log transmission processing unit P141 notifies the management processing unit P130 of the completion of the process, thereby ending the process.

[0126] In this manner, the process is executed by the log management device 100 according to the fourth embodiment. Also, in this manner, the log management device 100 according to the fourth embodiment realizes a log management method for recording vehicle travel log data in the storage device 120. Alternatively, the log management method can be realized as a log management program that causes a computer to execute the log management method. In this case, the log management program can be provided as an encoded recording medium.

[0127] Effects As described above, according to the fourth embodiment, when a capacity shortage of the memory device 120 in a driving plan is predicted based on the predicted data size and the current free space of the memory device 120, the driving log data to be recorded in the memory device 120 is transmitted to the external storage 300, and the transmitted driving log data is deleted from the memory device 120, thereby increasing the free space of the memory device 120.

[0128] By adopting the fourth embodiment in this way, it is possible to achieve the same effect as the first embodiment. In particular, in the fourth embodiment, since the free space is increased by deleting the driving log data from the storage device 120, it is possible to reliably avoid a shortage of the capacity of the storage device 120 by executing the process. On the other hand, generally, transmitting the driving log data requires higher computational resources and communication resources than the compression process. Therefore, it is also possible to consider a combination of the fourth embodiment with the first embodiment or the second embodiment. In this case, for example, when the shortage of the capacity of the storage device 120 cannot be avoided even by executing the compression process (step S150 in FIG. 6; No), the process by the log transmission processing unit P141 can be configured to be executed. In addition, since transmitting the driving log data requires higher computational resources and communication resources than the compression process, the second embodiment is also effective in combination with the third embodiment. [Explanation of symbols]

[0129] 100 Log management device 110 Processing equipment 111 Memory 113 Log Management Program 115 Processors 120 Storage device 200 Vehicle Control System 300 External Storage

Claims

1. A storage device for recording vehicle travel log data; one or more processors; Equipped with The one or more processors: A process of acquiring a current free space of the storage device; A process of acquiring a driving plan for the vehicle; A process of calculating a predicted data size of the travel log data predicted to be recorded in the future in the travel plan; A process of predicting a shortage of capacity of the storage device in the travel plan based on the predicted data size and the free space; a process of increasing the free space of the storage device in response to a predicted capacity shortage; It is configured to run A log management device comprising:

2. 2. The log management device according to claim 1, The one or more processors: In response to the prediction of a capacity shortage of the storage device, a process of instructing the vehicle to stop traveling is further executed; On condition that the vehicle has stopped traveling, a process for increasing the available space is executed. It is configured as follows: A log management device comprising:

3. 3. The log management device according to claim 2, The one or more processors: a process of determining whether the free space has increased beyond a required capacity obtained by subtracting the free space from the predicted data size as a result of execution of the process of increasing the free space; a process of terminating the process of increasing the available capacity and instructing the vehicle to resume traveling when the available capacity has increased beyond the required capacity; is configured to further A log management device comprising:

4. 4. The log management device according to claim 1, The process of increasing the free space includes increasing the free space by compressing the driving log data recorded in the storage device. A log management device comprising:

5. 5. The log management device according to claim 4, The compression process includes: Obtaining a compression efficiency for each data type of the driving log data; compressing the driving log data in the order of the data type with the highest compression efficiency; Includes A log management device comprising:

6. 5. The log management device according to claim 4, The compression process includes compressing the driving log data by selecting a compression method that has the shortest compression time from a plurality of compression methods that can increase the free space by a predetermined amount or more. A log management device comprising:

7. 4. The log management device according to claim 1, The process of increasing the free space includes transmitting the driving log data recorded in the storage device to an external device, and deleting the transmitted driving log data to increase the free space. A log management device comprising:

8. A log management method for recording vehicle travel log data in a storage device, the method being executed by one or more processors, comprising: Obtaining a current free space in the storage device; Obtaining a driving plan for the vehicle; Calculating a predicted data size of the travel log data predicted to be recorded in the future in the travel plan; predicting a capacity shortage of the storage device in the travel plan based on the predicted data size and the free space; In response to a predicted capacity shortage of the storage device, executing a process to increase the free space; Includes A log management method comprising:

9. 9. The log management method according to claim 8, and instructing the vehicle to stop traveling in response to a predicted insufficient capacity of the storage device; On condition that the vehicle has stopped traveling, a process for increasing the available space is executed. A log management method comprising:

10. 10. The log management method according to claim 9, determining whether the free space has increased beyond a required capacity obtained by subtracting the free space from the predicted data size as a result of execution of the process of increasing the free space; In response to the fact that the available capacity has increased to be greater than the required capacity, ending the process of increasing the available capacity and instructing the vehicle to resume traveling; Also includes A log management method comprising:

11. A log management program for causing a computer to execute a process of recording vehicle travel log data in a storage device, A process of acquiring a current free space of the storage device; A process of acquiring a driving plan for the vehicle; A process of calculating a predicted data size of the travel log data predicted to be recorded in the future in the travel plan; A process of predicting a shortage of capacity of the storage device in the travel plan based on the predicted data size and the free space; a process of increasing the free space of the storage device in response to a predicted capacity shortage; and further configured to cause the computer to execute: A log management program comprising:

12. 12. The log management program according to claim 11, In response to the prediction of a capacity shortage of the storage device, the computer further executes a process of instructing the vehicle to stop traveling; causing the computer to execute a process for increasing the available space on condition that the vehicle has stopped traveling; It was configured as A log management program comprising:

13. 13. The log management program according to claim 12, a process of determining whether the free space has increased beyond a required capacity obtained by subtracting the free space from the predicted data size as a result of execution of the process of increasing the free space; a process of terminating the process of increasing the available capacity and instructing the vehicle to resume traveling when the available capacity has increased beyond the required capacity; and further configured to cause the computer to execute: A log management program comprising:

Images